Not able get static routes

Description of Issue/Question
When using salt-stack to grab a static route from a junos router, I get an error about it being a NoneType
Did you follow the steps from https://github.com/napalm-automation/napalm#faq

[x] Yes
[ ] No

Setup
napalm-junos version
(Paste verbatim output from pip freeze | grep napalm-junos between quotes below)
napalm-junos==0.4.3

JunOS version
(Paste verbatim output from show version and haiku between quotes below)
Hostname: myrouter
Model: mx5-t
Junos: 13.3R6.5
JUNOS Base OS boot [13.3R6.5]
JUNOS Base OS Software Suite [13.3R6.5]
JUNOS Kernel Software Suite [13.3R6.5]
JUNOS Crypto Software Suite [13.3R6.5]
JUNOS Packet Forwarding Engine Support (MX80) [13.3R6.5]
JUNOS Online Documentation [13.3R6.5]
JUNOS Services Application Level Gateways [13.3R6.5]
JUNOS Services Jflow Container package [13.3R6.5]
JUNOS Services Stateful Firewall [13.3R6.5]
JUNOS Services NAT [13.3R6.5]
JUNOS Services RPM [13.3R6.5]
JUNOS Services Crypto [13.3R6.5]
JUNOS Services SSL [13.3R6.5]
JUNOS Services IPSec [13.3R6.5]
JUNOS Routing Software Suite [13.3R6.5]

        Help me, Obi-Wan
        I just saw Episode Two
        You're my only hope

Steps to Reproduce the Issue
Error Traceback
(Paste the complete traceback of the exception between quotes below)
salt myrouter route.show <IP_ADDRESS>/8 static
myrouter:
    ----------
    comment:
        Cannot execute "get_route_to" on myrouter as user. Reason: argument of type 'NoneType' is not iterable!
    out:
        ----------
    result:
        False
    traceback:
        Traceback (most recent call last):
          File "/var/cache/salt/minion/extmods/proxy/napalm.py", line 284, in call
            out = getattr(NETWORK_DEVICE.get('DRIVER'), method)(**params)  # calls the method with the specified parameters
          File "/opt/rh/python27/root/usr/lib/python2.7/site-packages/napalm_junos/junos.py", line 1061, in get_route_to
            key: value for key, value in all_protocol_attributes.iteritems()
          File "/opt/rh/python27/root/usr/lib/python2.7/site-packages/napalm_junos/junos.py", line 1062, in <dictcomp>
            if key in _PROTOCOL_SPECIFIC_FIELDS_.get(protocol)
        TypeError: argument of type 'NoneType' is not iterable

Here are the statics configured on the routers default instance
user@myrouter> show configuration routing-options
static {
    route <IP_ADDRESS>/8 next-hop <IP_ADDRESS>;
    route <IP_ADDRESS>/16 next-hop <IP_ADDRESS>;
    route <IP_ADDRESS>/12 next-hop <IP_ADDRESS>;
}

A stupid bug... :(
_PROTOCOL_SPECIFIC_FIELDS_ should have one more key static having [] as value.

            ],
            'static' : []
      }

Added that in and restarted the salt-proxy for that juniper and can confirm it returned the routes I expected to see


Visiblity add in has refresh issue

Reproduce:
1 .Add a surface to ArcMap
2. Change the name of the surface in table of contents
3. attempt to collect observer points from the LLOS tab.  Collection will fail.
4. switch to the RLOS tab
5.  The surface will refresh to the new name and now allow points to be collected.

@NatalieCampos this issue has been fixed.  Ready for testing once the code is merged.

this is fine as is.


Fix_Issue406

Motivation

Solution

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.daidong seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.

Hello, you need to sign the cla and we can merge this. @SuperD-dd

谢谢提醒，我已经操作好了
该邮件从移动设备发送

------------------ 原始邮件 ------------------
发件人:                                                                                "cloudwego/volo"                                                                                @.>;
发送时间: 2024年4月8日(星期一) 晚上11:12
@.>;
<EMAIL_ADDRESS>主题: Re: [cloudwego/volo] Fix_Issue406 (PR #407)
Hello, you need to sign the cla and we can merge this. @SuperD-dd
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you were mentioned.Message ID: @.***>

@SuperD-dd 你好，看着 cla 检测状态仍然没有通过，是否是你签署 cla 的邮箱和 github 的不一致？


Python 3.8/9/10 Support

Are there plans to support the most recent versions of Python? Right now the only supported version of Python that hasn't reached it's end-of-life  is 3.7. If these plans exist, is there a timeline? What sort of work needs to be done to enable support for more recent versions of Python?
Opening this thread both as a question and a place for discussion.

@Sbacon017 great question.  A plan does not exist and I'm not entirely sure how much additional work will be required to get this working if our current suite of tests do not pass.  That being said I will go ahead and start incrementing the python versions + running our current test suite to see what fails.

Using python 3.10 the basic shipment example was able to retrieve rates.
The import unittest2 failed so the python setup.py test threw an exception.
In order to get the test suite working you'll need to ensure that the local env variable SHIPPO_API_KEY is set and being used:
$ export SHIPPO_API_KEY="shippo_live_<shippo live token>"

@jfriedr Thanks for getting back to me! This is great news, I'm not whether or not you take this to mean you officially support up to Python 3.10, but it seems like it will be enough to unblock us from upgrading.

There does appear to be some problems with the 'async' keyword that was introduced into latter python versions.  Not sure if there are any plans for this or not.

There does appear to be some problems with the new async keyword that was introduced into latter python versions. This only seems to happen when the code is using async APIs i.e. async=True Not sure if there are any plans for this or not. I would suggest that this is kind of important to python implementations that need to be performant.

I have the same problem with python 3.8.5.
How can we eliminate this problem?


Correction for raw affiliation Micalis Institute, INRAE, AgroParisTech, University Paris-Saclay, Jouy-en-Josas, France

Correction needed for raw affiliation Micalis Institute, INRAE, AgroParisTech, University Paris-Saclay, Jouy-en-Josas, France
raw_affiliation_name: Micalis Institute, INRAE, AgroParisTech, University Paris-Saclay, Jouy-en-Josas, France
new_rors: 0471cyx86;02kbmgc12;003vg9w96;03xjwb503
previous_rors: 0471cyx86;02kbmgc12;003vg9w96
works_examples: W4353034940
contact: 441c1f6a5247a5034eb3d8c097be151d:a7a71524599ca0d7325a1ffbe383a11c4af5 @ agroparistech.fr

This issue was accepted and ingested by the OpenAlex team on 2024-12-19. The new affiliations should be visible within the next 7 days.


Can't use model.contrasts with categorical variables

This is solved by reordering categories to have both control and case in the model matrix

Fixed by https://github.com/emdann/milopy/pull/15


Fix the spell fault of DEFAULT_OTBR_INTERFACE in otbr_start.sh

The DEFAULT_OTBR_INTERFACE is being wrongly used as DEAFULT_OTBR_INTERFACE， if need to change the OTBR interface, it can not work.
Same fix as in https://github.com/project-chip/certification-tool/pull/244 but this time on the correct location

This fix will be done in your other PR: https://github.com/project-chip/certification-tool-backend/pull/127


Filemagic keywords v2

Previous PR: #1125
Describe Changes:

Update README file
Add test for file.data prefilter keyword.

followed by #1130


Character sheet CSS doesn't respect "routePrefix" options

Opening a Actor sheet return a 404 because the CSS doesn't respect the routePrefix specified in options.json
file: dnd5e.css
Culprit:
.dnd5e2.sheet.actor.character.minimized {
  background: url("/ui/denim075.png");
  border: unset;
}

I can work on this.


Assets missing after running make using file-loader

Pre-flight checklist

[X] I have read the contribution documentation for this project.
[X] I agree to follow the code of conduct that this project uses.
[X] I have searched the issue tracker for a bug that matches the one I want to file, without success.

Electron Forge version
"6.0.0-beta.61",
Electron version
"15.0.0"
Operating system
windows 10 x64
Last known working Electron Forge version
No response
Expected behavior
Assets are present after packaging using file-loader.
Actual behavior
Assets are missing after packaging using file-loader.
Given the file structure :
src
  |- assets
    |- someImage.jpg
  |- main.js
  |- renderer.js
index.html
webpack.main.config.js

webpack.renderer.config.js:
const path = require('path');
const rules = require('./webpack.rules');
const CopyWebpackPlugin = require('copy-webpack-plugin');

rules.push({
  test: /\.css$/,
  use: [{ loader: 'style-loader' }, { loader: 'css-loader' }],
});

module.exports = {
  module: {
    rules: [
      ...rules,
    ],
  },
  plugins: [
    new CopyWebpackPlugin({
      patterns: [
        { from: path.join("src", "assets"), to: "assets" }
      ]
    }),
  ]
};

webpack.rules.js :
...
  {
    test: /\.(png|jpe?g|gif)$/i,

    use: [
      {
        loader: 'file-loader',
        options: {
          name: '[path][name].[ext]',
          publicPath: '..',
          context: "src"
        },
      }
    ]

  },

];

and generally going by this solution here :https://github.com/electron-userland/electron-forge/issues/1196
I still cannot load assets in production but i can load them in dev.
Steps to reproduce
run yarn make with the configuration mentioned above
Additional information
Assets are not available in production. 404 error file not found.

I've added a paragraph or two about this to the Webpack plugin documentation.
If you need more assistance, please use one of the community forums, including the Electron Discord server.


Enable null hive partitions with pyarrow parquet engine

This PR makes the necessary changes for null "hive" partitions to be handled correctly in to_parquet and read_parquet for engine="pyarrow". On the read side, users will need to specify the necessary pyarrow.dataset.partitioning  options via dataset= (e.g. dataset={"partitioning": {"flavor": "hive", "schema": pa.schema([("id", pa.int64())])}}).
~Reason we need a new partitioning_options argument: Unfortunately, PyArrow cannot properly handle null hive partitions unless the user specifies an explicit schema for the hive-partitioned column(s). Although it is possible for the user to initialize their own pyarrow.dataset.HivePartitioning object, and then pass it through to PyArrow using the dataset argument (e.g. dataset={"partitioning": <HivePartitioning>}), the initialized HivePartitioning object cannot by serialized in Python. This means that Dask must make it possible to delay the initialization of these objects to enable execution on distributed clusters.  The easiest way to support/document this behavior is with a top-level read_parquet option.~

[x] Addresses https://github.com/dask/dask/issues/9911 and https://github.com/dask/dask/issues/9435 (for engine="pyarrow")
[x] Tests added / passed
[x] Passes pre-commit run --all-files

@jrbourbeau - I have several Parquet-related PRs up (as usual). However, this is probably the highest-priority for RAPIDS (we tried to resolve the problem for dask-cudf in https://github.com/rapidsai/cudf/pull/12866, but weren't aware of the PyArrow serialization problem).

Update: This PR no-longer introduces a new top-level partitioning-options argument (since it should be rare for users to need such an option)

@rjzamora could you merge main? That will resolve unrelated failures popping up here


Fix search

I removed a lot of duplicate queries in lib/tilex/posts.ex, fixed some wallaby deprecations and fixed the search post feature.
TODO: Currently we can't paginate query responses because of a few reasons. 1 being that channels have no knowledge of conn. I think its an easy fix of just appending the page and query to the URL using the sockets response and then figuring out an elegant way to set request_path to the right URL for the _pagination.html.eex template. Either way searching currently works and pagination can be added at a later date.

Nice! Thank you! 👍


problem when debug apollo using vscode

System information

** Linux Ubuntu 16.04
Apollo version 3.0:

Steps to reproduce the issue:
when i use vscode debug apollo project ,i meet some problem.
after press F5,get some problrm like this:
Unable to start debugging. Program path '/home/zlab-apollo/apollo/bazel-bin/modules/planning/planning' is missing or invalid.
GDB failed with message: /home/zlab-apollo/apollo/bazel-bin/modules/planning/planning: 没有那个文件或目录.
This may occur if the process's executable was changed after the process was started, such as when installing an update. Try re-launching the application or restarting the machine.
i look for the path,and  i found that in apollo files,there is a  soft link name bazel-bin,but when i click it ,it erro:
无法使用此链接，因为其目标
“/root/.cache/bazel/_bazel_root/540135163923dd7d5820f3ee4b306b32/execroot/apollo/bazel-out/local-dbg/bin”不存在。

Supporting materials (screenshots, command lines, code/script snippets):

@sunnyguanguanguan have you tried following the steps mentioned in this guide

@sunnyguanguanguan have you tried following the steps mentioned in this guide

actually,i install docker-ce using  /apollo/docker/setup_host/install_docker.sh,then i can pull images and open dreamviwer successfully  .
And,i can open Apollo project and build successfully in vscode.

@sunnyguanguanguan so was your build successful?

Closing this issue as it appears to be resolved. Feel free to reopen if you have additional questions. Thanks!

The same problem as you show, and i wonder if you solve it and how?

The same problem as you show, and make a soft link mauually.
I wonder that how you solve it.
Thanks

I encountered the same problem, how did you solve it?

I also ncountered the same problem, how did you solve it?

How did you solved it? I met the same trouble.

@sunnyguanguanguan have you tried following the steps mentioned in this guide

I'm sorry that this link is invalid, have you solved this problem?


OpenStack & Rackspace drivers

Generic OpenStack driver and Rackspace specific driver based on the generic one.
To-do list :

[x] Floating IP allocation and assignation
[x] Allow user to provide names or id instead only id for

[x] Flavor
[x] Image
[x] Network

[x] Call to driver.AddPublicKeyToAuthorizedHosts() is missing
[x] Some info level should be at debug level or maybe not present at all
[x] If tenant name and tenant id are both provided the driver should not fail
[x] Reimplement docker installation and upgrade to target only ubuntu
[x] Rackspace driver

@ehazlett I have updated docker to use 1.4.1 identity build like you did in the others drivers. Otherwise, fixes for the rackspace driver from @smashwilson have been merged.

@ggiamarchi @smashwilson Thanks for your great work on this.
A few things:

Could we set a default region? Or at least a better error... this is the error when no region is specified for rackspace:

FATA[0002] Discovered 4 matching endpoints: []tokens.Endpoint{tokens.Endpoint{TenantID:"942776", PublicURL:"https://iad.servers.api.rackspacecloud.com/v2/942776", InternalURL:"", AdminURL:"", Region:"IAD", VersionID:"2", VersionInfo:"https://iad.servers.api.rackspacecloud.com/v2", VersionList:"https://iad.servers.api.rackspacecloud.com/"}, tokens.Endpoint{TenantID:"942776", PublicURL:"https://hkg.servers.api.rackspacecloud.com/v2/942776", InternalURL:"", AdminURL:"", Region:"HKG", VersionID:"2", VersionInfo:"https://hkg.servers.api.rackspacecloud.com/v2", VersionList:"https://hkg.servers.api.rackspacecloud.com/"}, tokens.Endpoint{TenantID:"942776", PublicURL:"https://dfw.servers.api.rackspacecloud.com/v2/942776", InternalURL:"", AdminURL:"", Region:"DFW", VersionID:"2", VersionInfo:"https://dfw.servers.api.rackspacecloud.com/v2", VersionList:"https://dfw.servers.api.rackspacecloud.com/"}, tokens.Endpoint{TenantID:"942776", PublicURL:"https://syd.servers.api.rackspacecloud.com/v2/942776", InternalURL:"", AdminURL:"", Region:"SYD", VersionID:"2", VersionInfo:"https://syd.servers.api.rackspacecloud.com/v2", VersionList:"https://syd.servers.api.rackspacecloud.com/"}}

No output is displayed until a rackspace hosts has been created, so the command looks like it hung. Could we get a "Creating server..." log message or something?
Any chance the commits could be squashed a bit?

Also some debugging output is displayed when creating:
± % machine create -d rackspace rackspace                                                                          !371

+ [ https://get.docker.com/ = https://get.docker.com/ ]
+ sh -c apt-key adv --keyserver hkp://keyserver.ubuntu.com:80 --recv-keys 36A1D7869245C8950F966E92D8576A8BA88D21E9
gpg: requesting key A88D21E9 from hkp server keyserver.ubuntu.com
gpg: key A88D21E9: public key "Docker Release Tool (releasedocker<EMAIL_ADDRESS>imported
gpg: Total number processed: 1
gpg:               imported: 1  (RSA: 1)
+ sh -c echo deb https://get.docker.com/ubuntu docker main > /etc/apt/sources.list.d/docker.list
+ sh -c sleep 3; apt-get update; apt-get install -y -q lxc-docker
+ sh -c docker version
INFO[0078] "rackspace" has been created and is now the active machine. To point Docker at this machine, run: export DOCKER_HOST=$(machine url) DOCKER_AUTH=identity

@bfirsh If I can chime in here, the reason that @smashwilson probably didn't specify a region is for geographic liability. As an example, the Rackspace SDKs no longer support a default region in case someone is required to only have their data in Australia, Hong Kong, etc.

So, that means the parameter --rackspace-region should be mandatory i guess ? In that case we should just print a clear error message.

@bfirsh If I can chime in here, the reason that @smashwilson probably didn't specify a region is for geographic liability. As an example, the Rackspace SDKs no longer support a default region in case someone is required to only have their data in Australia, Hong Kong, etc.

Yep yep, this is correct. (Thanks for stepping in, @rgbkrk, I was fighting off a bout of the flu.)

So, that means the parameter --rackspace-region should be mandatory i guess ? In that case we should just print a clear error message.

Indeed. I'll get a PR to your PR today :smile:

@bfirsh: Okay, ggiamarchi/machine#5 and ggiamarchi/machine#6 submitted. Once those are in:

Could we set a default region? Or at least a better error... this is the error when no region is specified for rackspace:

A missing region is now treated like the other mandatory parameters:
# OS_USERNAME and OS_API_KEY exported

ashl6947@MMN1F3FD58 ~/code/machine (better-region-error=) $ machine create --driver=rackspace regionless
FATA[0000] Region must be specified either using the environment variable OS_REGION_NAME or the CLI option --rackspace-region

No output is displayed until a rackspace hosts has been created, so the command looks like it hung. Could we get a "Creating server..." log message or something?

OpenStack server creation has an Info-level message:
ashl6947@MMN1F3FD58 ~/code/machine (creating-server=) $ machine create --driver=rackspace --rackspace-region="DFW" morelogs
INFO[0001] Creating server...                            Name=docker-host-6c81d6b9a12e860b24fe98130c1dcc10fe14bad77aadb61bf21faad59063ca89
INFO[0082] "morelogs" has been created and is now the active machine. To point Docker at this machine, run: export DOCKER_HOST=$(machine url) DOCKER_AUTH=identity

Also some debugging output is displayed when creating:

I've shunted that off to /var/log/docker-install.log. It's odd that it was appearing with debugging disabled anyway; the docker installation script must write output to stderr instead of stdout for some reason.
On a related note, I've also made it so that a failing docker installation won't prevent the host from being usable to machine as well. You can now use machine ssh or machine rm to correct the situation even if the install failed.
Before:
ashl6947@MMN1F3FD58 ~/code/machine ((8f3502d...) *) $ machine create --driver=rackspace --rackspace-region="DFW" before
INFO[0002] Creating server...                            Name=docker-host-b3ec793bca8e90496ea4c2aaf796b36b7c8a7d91c768facc3b3770e04e4f9d7c
dockery: unrecognized service
ERRO[0076] Docker installation failed
ERRO[0076] The driver assume your instance is running Ubuntu. If this is not the case, you should use the option --openstack-docker-install=false when creating the machine and then install manually
FATA[0076] exit status 1
ashl6947@MMN1F3FD58 ~/code/machine ((8f3502d...) *) $ machine ls
NAME     ACTIVE   DRIVER      STATE   URL
before            rackspace
ashl6947@MMN1F3FD58 ~/code/machine ((8f3502d...) *) $ machine rm before
INFO[0000] Deleting OpenStack instance...                MachineId=
ERRO[0000] Error removing machine before: Expected HTTP response code [204] when accessing URL(https://dfw.servers.api.rackspacecloud.com/v2/864477/servers/); got 404 instead with the following body:
404 Not Found

The resource could not be found.

FATA[0000] There was an error removing a machine. To force remove it, pass the -f option. Warning: this might leave it running on the provider.

After:
ashl6947@MMN1F3FD58 ~/code/machine (creating-server *=) $ machine create --driver=rackspace --rackspace-region="DFW" betterfail
INFO[0001] Creating server...                            Name=docker-host-f5ed15c28ba15ecee340ffdceb3e5fdc70855ee70e9a82a569121d2c1e125b9c
ERRO[0045] The docker installation failed.
ERRO[0045] The driver assumes that your instance is running Ubuntu. If this is not the case, you should use the option --openstack-docker-install=false (or --{provider}-docker-install=false) when creating a machine, and then install and configure docker manually.
ERRO[0045] Also, you can use "machine ssh" to manually configure docker on this host.
INFO[0045] "betterfail" has been created and is now the active machine. To point Docker at this machine, run: export DOCKER_HOST=$(machine url) DOCKER_AUTH=identity
ashl6947@MMN1F3FD58 ~/code/machine (creating-server *=) $ machine ls
NAME         ACTIVE   DRIVER      STATE     URL
betterfail   *        rackspace   Running   tcp://<IP_ADDRESS>:2376
ashl6947@MMN1F3FD58 ~/code/machine (creating-server *=) $ machine ssh betterfail
Welcome to Ubuntu 14.04.1 LTS (GNU/Linux 3.13.0-37-generic x86_64)

 * Documentation:  https://help.ubuntu.com/
Last login: Thu Jan  1 00:00:10 1970
root@docker-host-f5ed15c28ba15ecee340ffdceb3e5fdc70855ee70e9a82a5691:~# exit
logout
ashl6947@MMN1F3FD58 ~/code/machine (creating-server *=) $ machine rm betterfail
INFO[0000] Deleting OpenStack instance...                MachineId=a62dd2cf-4209-4d02-8e99-c19cf0726509
INFO[0001] Deleting Key Pair...                          Name=docker-host-f5ed15c28ba15ecee340ffdceb3e5fdc70855ee70e9a82a569121d2c1e125b9c

Looking great, I'm excited to use this!

LGTM

@ggiamarchi this is getting really close :)  Do you think you could squash some of the commits?

@ehazlett I have squashed commits when it was relevant and not annoying to read and understand the history. Finally, we came from 50 to 24 commits in the PR.

@ggiamarchi awesome - thanks!

@bfirsh and @ehazlett : Can you please take a moment to outline what needs to be done to overcome the merge conflict on this PR, and get it in? We are really interested in getting this merged. Please advise.

It's a small merge conflict in the README, related to another PR landing before this one. Surprised it doesn't merge well. I did the rebase locally just fine. I'm guessing @ggiamarchi will be able to handle it just fine but I could make a PR to fix it up.
It would be nice if this was merged with the amount of functionality it has now. The Rackspace portion of this PR has existed as far back as https://github.com/bfirsh/docker/pull/10 and https://github.com/docker/machine/pull/18.

Rebased

@ggiamarchi could you do one more rebase?  there was a hostname update to set the name of the machine.  after this we should be good to merge.  thanks!

I have just rebased and made necessary changes to match the new NewDriver signature 9d91f45

Thanks the work all!

Awesome ! :sunglasses:

:metal: It's great to see this. Thanks, everyone!

:tada: Yay, thanks!


[Remote Store] Change remote_store setting validation message to make it more clear

Signed-off-by: Sachin Kale<EMAIL_ADDRESS>Description

Currently, if we try to enable index.remote_store.enabled without setting replication type to SEGMENT, we get following error:

{
  "error" : {
    "root_cause" : [
      {
        "type" : "illegal_argument_exception",
        "reason" : "Settings index.remote_store.enabled cannot be enabled when index.replication.type is set to DOCUMENT"
      }
    ],
    "type" : "illegal_argument_exception",
    "reason" : "Settings index.remote_store.enabled cannot be enabled when index.replication.type is set to DOCUMENT"
  },
  "status" : 400
}

But this does not make the dependency of segment replication clear. With this change, we are changing the error message to:

{
  "error" : {
    "root_cause" : [
      {
        "type" : "illegal_argument_exception",
        "reason" : "To enable index.remote_store.enabled, index.replication.type should be set to SEGMENT"
      }
    ],
    "type" : "illegal_argument_exception",
    "reason" : "To enable index.remote_store.enabled, index.replication.type should be set to SEGMENT"
  },
  "status" : 400
}

Check List

[ ] New functionality includes testing.

[ ] All tests pass

[ ] New functionality has been documented.

[ ] New functionality has javadoc added

[X] Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Thanks for adding this!
Please could you help update the unit tests as well for this change?

Please could you help update the unit tests as well for this change?

Forgot to update UTs. Thanks @BhumikaSaini-Amazon

Looks good to me 👍
Please link the respective Issue to this PR and strike off the PR checklist items
Thanks!

Looks good to me 👍 Please link the respective Issue to this PR and strike off the PR checklist items Thanks!

@BhumikaSaini-Amazon Added issue link and updated PR checklist.


settings: Build a better UI for choosing language

This will be a bit complex to build, and I think right now we have a number of equally complex areas of UI work to do that will be higher-value. (Most users will only ever touch this screen either zero or one times.) But I'm getting down some thoughts now, since I was looking into this thanks to #2610.
Our screen for choosing the UI language looks like this:

Apart from some small layout issues (those are #2610) which shouldn't be hard to fix, there are a few problems with this:

It uses national (more or less) flags to represent languages. This is confused about the world (many languages are spoken widely in several countries, and many countries have several primary languages), and isn't super helpful anyway.
It names all the languages in English only.
It's a long list, in an unavoidably arbitrary order (it can't be in the order of the user's own language, because the point of the screen is we don't know that yet), with no search.

Good language selectors I see in mobile apps:

don't use flags
name each language in the current UI language, and in itself
provide a search box -- which searches through both those names for each language

The Wikipedia app (the official one from Wikimedia) does an excellent job of this. It's actually significantly different in details between their Android and iOS apps, but both are good models.

@zulipbot claim
Hi, I am new to Zulip repo and looking for an issue to get started. This one looks doable. I'll follow Wikipedia's language screen on Android and make a WIP PR soon.

The PR is ready for review.

Now done, with #3231. Thanks again @anh2111 !


Removed needless DOM query

cached body element in local variable to avoid multiple DOM queries on the same element

Thanks.


Watch Later Playlist videos not marked as watched and not removed

I mark couple videos to watch later.

I watch all the videos in the play list in their entirety.
I click on Watch Later playlist again to see the list of videos.
I click on "Remove Watched" button, expecting all of them to disappear but they stay/remain in the playlist.
I just watched them all. Why are they staying in the playlist and not being removed when I click Remove Watched button?
This is a bug.

Does this still happen with YTC disabled? Lots of other users reported a very similar -if not the same- problem in the google forums which has nothing to do with YouTube Center.

My apologies. You are correct. Regardless of YTC enabled or disabled, watching videos from "Watch Later" playlist does not mark them as watched and thus they do not get removed when clicking the "Remove Watched" button.
Not a bug.
But could this be something that YTC can address? Maybe a Feature in the upcoming update of YTC?
I'd gladly help with testing the development or anything else that you might need help with. The fact that it's not working is driving me bananas.
Thanks for your time.
You're doing fantastic work!

It depends on what the addon author thinks about adding a fix that YouTube should/will fix.

I will keep it open for now.


stdenv: add shopt inherit_errexit

Motivation for this change
nullglob behavior will not return the glob pattern in case of a failed glob
inherit_errexit will not ignore exit code from a subshell (except if local is used before the subshell).
(happy to details those further in case those are not clear, ref)
This will probably need to go through a hydra evaluation. (I will group it with other changes)
@andersk in case you are not busy, you might have some input.
Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
21.11 Release Notes (or backporting 21.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

Is nullglob really a good default for us? I would imagine it might lead to real problems being ignored at build time. Why not failglob instead?

you're right here of course, let me change that.

It looks like fail glob will not be as straightforward as I thought.

The following code snippet in standard library trigger a failure with failglob
    for f in "${!outputDev}"/{lib,share}/pkgconfig/*.pc; do
        echo "Patching '$f' includedir to output ${!outputInclude}"
        sed -i "/^includedir=/s,=\${prefix},=${!outputInclude}," "$f"
    done

it is a little surprising to me that stdenv includes a failglob. As fas as I know it means that the pattern with the * will be used as the variable.
The fact that people want to match files optionaly could be solved in the following way
    for dir in "${!outputDev}"/{lib,share}/pkgconfig; do
       ! [ -d $dir ] && continue
       for f in "$dir"/*.pc; do
          echo "Patching '$f' includedir to output ${!outputInclude}"
          sed -i "/^includedir=/s,=\${prefix},=${!outputInclude}," "$f"
       done
    done

Not really sure it's an improvement over the status quo. I'll give this some more thoughts and will try again later.

hydra is passing on aarch64 this PR is going to staging.

NOTE: This breaks bash v4 compatibility, see #155706


Scam Attacks

Scam Attacks Post

Intentionally left various grammar and style issues to debug spell checker

/qualitycheck

/articlecheck

@JediFaust I think "scam" is a wide category of attacks that often have blurry definitions. I would either publish separate articles on each and hold off until we have a good number of them.

/articlecheck


Training notebook does not work

The training notebook has an issue with this statement:
`%tensorflow_version 1.x
import tensorflow as tf`
Info is:
Your notebook should be updated to use Tensorflow 2.
See the guide at https://www.tensorflow.org/guide/migrate#migrate-from-tensorflow-1x-to-tensorflow-2.

https://github.com/tensorflow/tflite-micro/issues/1821
https://github.com/tensorflow/tflite-micro/issues/1690
https://github.com/tensorflow/tflite-micro/issues/1603


My image isn't responsive and the img-fluid class doesn't seem to work!!!

I'm sure my problem is painfully simple but I'm trying to make my image responsive in bootstrap 4.6.  I tried img-fluid as advised on the getbootstrap.com site but it doesn't work.  I do hope you can help.
My code:
<!doctype html>

	<title>Test</title>

	<meta charset="utf-8>

    <meta name="viewport" content="width=device-width, initial-scale=1" />

	<meta http-equiv="x-ua-compatible" content="ie=edge">

	<link rel="stylesheet"<EMAIL_ADDRESS>integrity="sha384-B0vP5xmATw1+K9KRQjQERJvTumQW0nPEzvF6L/Z6nronJ3oUOFUFpCjEUQouq2+l" crossorigin="anonymous">

	<link rel="stylesheet" type="text/css" href="restless-inc.css">

Thanks for any help you might be able to offer.
Regards
Nick

There must be something else going on for you because the code works in our docs. https://getbootstrap.com/docs/4.6/content/images/

If it has been closed does that mean I can't respond?

Not at all, feel free to elaborate if you need.

I fear I owe you an apology.  I thought when you had closed the question I was unable to respond, I thought that a little rude. So you have my apologies.  I am new to all this and am finding my way somewhat.  I raised another question as I thought I couldn't answer this one so please bare with me, I'm sure I'll get there in the end.  I think I managed to solve my problem.  It was the max-width statement that was the problem.  When I changed it to width:100% the picture was more responsive.
Thank you for your indulgence.
Regards
Nick

I think the issue you might be describing—you want the image to be 100% wide at all times. Our .img-fluid class only ensures the image doesn't break out of the parent element on smaller devices. It doesn't enlarge an image, it prevents it from being too wide.

Thanks for the response.  So is there a class that is more suitable for my needs.
Regards
Nick

@glosnick You should find what you need in our docs ' sizing utilities page, mostly .w-100 if I understood your need.


Request to publish the extension onto the Open VSX Registry

Haven't seen any mentions of this elsewhere, and hope I am not asking in the wrong place.
I am wondering if it would be possible to publish the previous iteration of the vscode extension (and eventually this one) on the Open VSX Registry. This will allow users to install it through the alternative marketplace, which is useful when the Microsoft one cannot be used.

Thanks! Most versions uploaded & pending namespace claim at EclipseFdn/open-vsx.org#760.


How to use query parameters in an array with string keys?

How to describe the structure of the following sort [user_id] = "asc" sort [created_at] = "desc" ???

If you want the parameter name to be [user_id], you'd have to set your parameter that way. Not sure what the question is here.


update journal quill icon position

update quill icon left position as it was over the text
Before:

After:

@bradp we need to revert this. after 0.33 update it looks out of place:

Seems like there was a general styling issue affecting this.


MunkiReport 5.x, PHP and MariaDB/MySQL

I currently (still) run MunkiReport 4.01 with it connected to a separate MariaDB server and using SSL encryption for the SQL traffic. This is working fine and using PHP 7.1.33
I am starting to try and upgrade to MunkiReport 5.x and as sadly typical when moving to a major version change hitting issues. I am sure a lot of this is my fault.
Could you clarify what dependencies I need to install first to get 5.x to use MariaDB (or MySQL)?
I believe MunkiReport 5.x uses PHP 7.3 so will need new libraries.
I seem to have gotten as far as via git installing the new version, and successfully running composer.
I have a sneaking suspicion the issue is down to the use of SSL for MariaDB/MySQL as this is what was a problem last time.

@bochoven
Ok, I turned off SSL for my MariaDB connection temporarily and was then able to do the php database/migrate.php this appears to have run successfully as below.
php database/migrate.php
Migrating: 2018_02_06_000001_mdm_status_initialize
Migrated:  2018_02_06_000001_mdm_status_initialize (0.17 seconds)
Migrating: 2018_02_08_000001_fan_temps_add_smc_columns
Migrated:  2018_02_08_000001_fan_temps_add_smc_columns (0.57 seconds)
Migrating: 2018_02_08_000001_timemachine_apfs_snapshots
Migrated:  2018_02_08_000001_timemachine_apfs_snapshots (0.21 seconds)
Migrating: 2018_02_20_000001_network_add_dns
Migrated:  2018_02_20_000001_network_add_dns (0.57 seconds)
Migrating: 2019_02_07_000001_filevault_status_add_more_columns
Migrated:  2019_02_07_000001_filevault_status_add_more_columns (0.85 seconds)
Migrating: 2019_02_11_144341_ibridge_add_version_column
Migrated:  2019_02_11_144341_ibridge_add_version_column (0.11 seconds)
Migrating: 2019_02_22_000001_softwareupdate_rewrite_columns
Migrated:  2019_02_22_000001_softwareupdate_rewrite_columns (1.55 seconds)
Migrating: 2019_03_11_000003_fan_temps_json_rewrite
Migrated:  2019_03_11_000003_fan_temps_json_rewrite (4.65 seconds)
Migrating: 2019_03_18_000001_network_rewrite
Migrated:  2019_03_18_000001_network_rewrite (2.7 seconds)

With SSL still disabled for MariaDB/MySQL I can then login. If however I re-enable SSL when I try logging in to Munkireport afterwards it still immediately redirects to the Admin -> Upgrade database page. If I force it to go the Dashboard I get the following error.
Request Failed: parsererror, SyntaxError: JSON Parse error: Unrecognized token '<'
It seems therefore that currently (my) MunkiReport-PHP <IP_ADDRESS>19 does not work with SSL for MariaDB/MySQL. The entries I had in my .env for this are still present but I suspect the MR 5.x code is not utilising them.
This is what I was expecting so I am hoping we can work together to resolve this. For what it's worth my relevant setting in my .env are as follows. It would be the later section that seems most relevant. My guess is that the standard code is not utilising these settings.
CONNECTION_DRIVER="mysql"
CONNECTION_HOST="it-db.domain.com"
CONNECTION_PORT="3306"
CONNECTION_DATABASE="munkireport"
CONNECTION_USERNAME="munkireport"
CONNECTION_PASSWORD="munkipassword"
CONNECTION_CHARSET="utf8mb4"
CONNECTION_COLLATION="utf8mb4_unicode_ci"
CONNECTION_STRICT=TRUE
CONNECTION_ENGINE="InnoDB"

CONNECTION_SSL_ENABLED='true'
CONNECTION_SSL_KEY='/etc/mysql/ssl/munki.domain.com.key'
CONNECTION_SSL_CERT='/etc/mysql/ssl/munki.domain.com.crt'
CONNECTION_SSL_CA='/etc/mysql/ssl/CompanyCA.crt'
CONNECTION_SSL_CAPATH='/etc/ssl/certs'
CONNECTION_SSL_CIPHER='DHE-RSA-AES256-SHA:AES128-SHA'

I see that your settings should be used:
https://github.com/munkireport/munkireport-php/blob/0e64b470a8f185327ad59c061b6b947450569e93/app/config/db.php#L14
and
https://github.com/munkireport/munkireport-php/blob/0e64b470a8f185327ad59c061b6b947450569e93/app/helpers/site_helper.php#L147
I don’t have a server with ssl so cannot reproduce the issue.

As my db.php and site_helper.php are the ones included with MR 5.x they do have those lines. However I think I have found the issue.
I had when I originally added SSL support to my MR config for 4.x used variable names matching those used in another PHP project called Snipe-IT so as per my post above the variables are called CONNECTION_SSL_KEY etc.
I think your code is looking for SSL_KEY etc. that is without the prefix CONNECTION_
I added duplicate copies without the CONNECTION_ prefix and it appears to be working. I will leave it running a little longer to test further and if it stays working I will close this issue.

I’m pretty sure the code requires the CONNECTION_ prefix.
     'ssl_key' => env('CONNECTION_SSL_KEY'),

Yes your right (I had left both in). Further testing shows the real problem and triggered my memory from way back when I originally got MR 4.x working.
The problem is that one of your files probably site_helper.php is not correctly processing logic based on CONNECTION_SSL_ENABLED as a result it then does not choose to read the options and therefore does not do a valid SSL connection. I confirmed this by temporarily editing site_helper.php to force it to always in effect be true as follows.
  //if($conn['ssl_enabled']){
    foreach(['key', 'cert', 'ca', 'capath', 'cipher'] as $ssl_opt){
      if($conn['ssl_'. $ssl_opt]){
        $conn['options'][constant('PDO::MYSQL_ATTR_SSL_'.strtoupper($ssl_opt))] = $conn['ssl_'. $ssl_opt];
      }
    }
  //}

The above will always therefore be true.
I obviously did find the logic error and fix it originally in 4.x and will try and do so again but you might want to have a look yourself as currently it would always regards it as being false.
Ah! I think I have found it, your standard …/app/config/db.php contains the following line
     'ssl_enabled' => env('CONNECTION_SSL_ENABLED', false),
This is hard coding the value to be false regardless of what the .env contains. My old MR 4.x db.php contain the line
     'ssl_enabled' => env('CONNECTION_SSL_ENABLED'),
I therefore think this is the cause and you need to adjust (for the future) your db.php file to remove the hardcoding to false.
This looks good from my testing.

Could you try removing the quotes around ‘true’ in your config?

That looks promising. I have edited my .env as requested to =TRUE and reverted my db.php
It seems to be working correctly. I will update you tomorrow to give it a longer test.

@AaronBurchfield
Yes that seems to have been the problem and is of course now fixed. Many thanks for your assistance. I am now closing this issue.


Change UI display of availability card if item is in cart

It is common for multiple plates of the same strain to be ordered, so having a quantity dropdown is still useful.
However, if the item is currently in the cart then the UI display should update to say so.

Move the quantity selection to the order form.

f7f176c085cefbc58bd9143e774cc253cb4cc2ea


Switch to coffeescript package

Switch to coffeescript package instead of deprecated coffee-script:
npm WARN deprecated<EMAIL_ADDRESS>CoffeeScript on NPM has moved to "coffeescript" (no hyphen)

Thanks @lutangar!


Run Cookbooks On Up?

Hi,
I was curious if it is possible to run specific cookbooks on a vagrant up. These would be tasks that are required to run every time a machine is brought up, not just on a provision.

Hi!
Not sure if this plugin is the best choice for what you want to achieve, probably you should use two different provision blocks and play with the run: always option. Here some docs:
https://docs.vagrantup.com/v2/provisioning/basic_usage.html


API - Get Note By Id Endpoint

Goal: Implement an API endpoint to fetch a note by ID.
Background: This endpoint is important for allowing the client to view the note.
Tasks:

[ ]  Design and implement a new API endpoint
[ ]  The endpoint should return the list of notes.
[ ]  Implement error handling to cover cases like server errors, unauthorised request etc.
[ ]  Write tests for the new endpoint

This task is required for the completion of user story:

TrueSparrowSystems/AI-SalesBridge-iOS-App#5
TrueSparrowSystems/AI-SalesBridge-iOS-App#6


Turn TUF spec into a well formatted RFC

This PR is so, so, so not ready for a merge, but I wanted to show you what I've been working on today to get input.
My motivation for doing this is that a huge amount of the spec thus far isn't actually "spec" but discussion. Such discussion should be moved to a separate document. Second, there was a lot of inconsistency in how things were phrased, and a seemingly large amount of mushiness on what needs to be done (i.e., is it a MUST, MAY, or SHOULD?). Third, this is probably going to be turned into an RFC eventually, so here's a head start on that. Fourth, oh god it's so much more beautiful this way.
Also, sorry to all y'all authors of this that I didn't cite correctly. I figure that's something you'd want to put in yourselves.

Coverage remained the same at 97.936% when pulling 77584d16a5a3128c694f36050437324ba8366dd5 on heartsucker:tuf-rfc into c1e72e0fdd092c5d71d52ffa345893b4a8013a25 on theupdateframework:develop.

Coverage remained the same at 97.936% when pulling e8a6ce48790416eef6c642820fe435b76ad0bd6b on heartsucker:tuf-rfc into c1e72e0fdd092c5d71d52ffa345893b4a8013a25 on theupdateframework:develop.

Coverage remained the same at 97.936% when pulling 2612ab46ca683630b090a1c2564ccceb1b4dcaaa on heartsucker:tuf-rfc into 8ddc62c43ff05fee53776e54985071bf83a00c89 on theupdateframework:develop.

Also, furthering my motivation on this. There were both contradictions as well as significant amounts of undefined behavior. I have mostly reconciled them, but there are a number of TODOs where the behavior was not clear enough for me to feel confident in asserting what was meant by the previous spec.

Also, furthering my motivation on this. There were both contradictions as well as significant amounts of undefined behavior. I have mostly reconciled them, but there are a number of TODOs where the behavior was not clear enough for me to feel confident in asserting what was meant by the previous spec.

Should there be a separate pull request for these issues?  One pull request that resolves the undefined behavior and contradictions, and another one just for the RFC-formatted text?

Coverage remained the same at 97.936% when pulling 78f2ce0cc23b08012023e6afafda371483623f2e on heartsucker:tuf-rfc into 8ddc62c43ff05fee53776e54985071bf83a00c89 on theupdateframework:develop.

Coverage remained the same at 97.936% when pulling 78f2ce0cc23b08012023e6afafda371483623f2e on heartsucker:tuf-rfc into 8ddc62c43ff05fee53776e54985071bf83a00c89 on theupdateframework:develop.

Coverage remained the same at 97.936% when pulling 78f2ce0cc23b08012023e6afafda371483623f2e on heartsucker:tuf-rfc into 8ddc62c43ff05fee53776e54985071bf83a00c89 on theupdateframework:develop.

I think that would lead to the case of trying to maintain (even temporarily) two sets of documentation, and if tuf-spec.txt wasn't removed, we've have two semi-authoritative documents, and I feel like it's better to cut and switch hard all at once.
It's also been hard for us here to read the current spec as it is because there is (in my opinion) too much discussion in the spec for engineers who just want to focus on the "how" of implementing TUF. I find that things like "Detect a Freeze Attack" are somewhat noisy phrases that add cognitive load and should wholly be replaced by simple directives like "ensure expires is after the current time". I think explanatory phrases like this belong in an ancillary design document, not a specification.
Think it would be best to take this PR and say:

Does it match the old spec (or improve where it must)?
Is it less ambiguous than the old spec?

And if yes to both, we make the switch.
I think keeping a single source for the specification will make it easier on implementors. Unless there's a compelling case to maintain the tuf-spec.txt that I'm not seeing, I think this document will be more useful than the document it replaces.

Coverage remained the same at 97.936% when pulling a31cb57e2b178c034829be499000bcfecba0038e on heartsucker:tuf-rfc into 8ddc62c43ff05fee53776e54985071bf83a00c89 on theupdateframework:develop.

Noting an additional case of lack of clarity on the TUF spec as evidence that this change might be a good thing. https://github.com/theupdateframework/taps/issues/36#issuecomment-308178031

As discussed via email, we decided to use Markdown to format the specification.  See pull request #477.


--disable-updates is a huge quality of life feature for Docker installs and it's seemingly an unrecognized option.

docker logs -f visual_visual.1.c9ws9k6xup3e0uhu720k7kqm7
Unknown option --disable-updates

It seems like kind of a bummer to have to repeatedly dismiss the update notification when the update function has no control over the container itself.  So ideally can we have this back or have the code-server --help updated to refer to the new flag?

Even more useful deprecation notices in the code would be awesome when it comes to launch flags because randomly the code-server just gives up existing because a flag got removed almost overnight and this is like the 6th time I've had to re-assess the launch flags since adopting code-server in my workflow.
Amazing work by the way :)

@Leopere Automatic updates have been completely removed so you shouldn't see that notification anymore at all.
I agree, next time we'll just allow the flag to go through for something simple like this being removed.
Sorry for the trouble and glad you're enjoying it <3

Like I definitely understand the mentality of "if we're not certain then don't" because it may put secure code at risk if the launch flags change without much notification.
I'm running the latest code-server image image: codercom/code-server:latest and I was getting this notification is this a new update you'd just pushed that I've got to wait for the docker hub to build before I can pull?

Was pushed days ago. What does code-server --version report?

I get image: codercom/code-server:latest which seems to not be bothering me for updates now that you ask.  By now it would've been bothering me.

Again wonderful work I'm looking forward to deploying this software in a stack for our web dev team in our personal development environments I'm stitching together.

Awesome, thanks, glad it's all working out well!

Let me know if you need anything else :)


Refactor/extend depstatus

The depstatus command needs to work with our dev dependency pattern of having dev libraries under lib/.
It should be refactored like so:
dep status #current functionality
dep pull #tries to pull all dependency directories
dep gn-django ... #proxies git commands to a dependency directory (dependencies are autocomplete-able)

Bonus thought: Maybe there could be an optional .deprc file in the root of project repos which contains an array of git URLs representing dev dependencies.  dep init could go through and clone these libraries in to lib/

This is done in it's own library: https://github.com/gamernetwork/depstatus


Pod Installation Issue

I'm using pod to install the library and I got this error

Can you re-upload the screenshot, please?

@kevin-hirsch  done

That's strange! Did you try to remove the /Pods folder and to redo pod install?

@kevin-hirsch  NO I can't remove pod folder I got some other pods any other solutions

Doing pod install will re-install the Pods folder ;)

I got some modified file in pod this why I can't delete all pods

Then you can just delete KVNProgress folder inside Pods folder and do pod install ;)

Than's I solved it, it there's was another var named successColor this way

Okay, great!


Adds delay parameter do dismiss call

The default delay is zero, as it used to be.

With this, tooltips can be dismissed after a delay, without the need for interaction.

Thanks, but I think this would sit better in an extension.


NodeJs Server does not see the request as "post" request on my upload specified Url.

When I try to submit data on the specified URL in the upload config. The server responds with a bad request and sees the request as a GET request. I have also supplied method: 'POST' in the config. But still I get the same issue.
I am using Multer Middleware with Express.
Can anyone suggest what I might be doing wrong or what am I missing.??

Closed due to inactivity. Assuming you have solved it already.


fedora 35 firewall

reloading firewalld removes wireguard rich rule.

more details would be nice 🙏

After install i cant log in on SERVER, but if i enter on VNC and stop the wg service, i can log in on ssh.


Process Tag in background

📒 Description
This PR will introduce the fix for the UI Freeze if there is a huge number of tags.
🕶 Types of changes
Bug fix (non-breaking change which fixes an issue)
🤯 List of changes

[x] Process the tag in background

👫 Relationships
Close #2787
🔎 Review hints
Replace void GUI::DisplayTags(const std::vector<view::Generic> list) with the following code
void GUI::DisplayTags(const std::vector<view::Generic> list) {
    logger().debug("DisplayTags");

//    TogglGenericView *first = generic_to_view_item_list(list);
    TogglGenericView *first = nullptr;
    for (int i=0; i < 10000; i++) {
        for (std::vector<toggl::view::Generic>::const_iterator
                it = list.begin();
                it != list.end();
                it++) {
            TogglGenericView *item = generic_to_view_item(*it);
            item->Next = first;
            first = item;
        }
    }

    on_display_tags_(first);
    view_item_clear(first);
}

It will 10x your current tags. Make sure you have 5-6, so the result is 50k or 100k.

Start the app, and search through the tag
Observe if the app is freeze when opening the TE -> If it's smooth -> 💯
Searching could cause the freeze a bit but it's reasonable.
Check RAM. If it's around 100-200Mb -> Good to go 💯

Nice, no freezing UI and the background tags loading is done before the user manages to start adding tags. For the users it just feels fast.


Failed to connect to Jupyter notebook after upgrading the newest vscode

Bug: Notebook Editor, Interactive Window, Editor cells
Steps to cause the bug to occur

It said below after I updated to the newest vscode.

'Failed to connect to Jupyter notebook.
http://localhost:8888/
Error: Kernel {0} is not usable. Check the Jupyter output tab for more information.'

Your Jupyter and/or Python environment
I am using version 1.43 under Ubuntu 18.04. anaconda version is version 1.7.2
Microsoft Data Science for VS Code Engineering Team: @rchiodo, @IanMatthewHuff, @DavidKutu, @DonJayamanne, @greazer

Hi @lixin6135. Could you please share a your console on the developer tools? The error should show up there.

Hi @lixin6135. Could you please share a your console on the developer tools? The error should show up there.

Sorry, I am quite new to vscode. Did I show the right part you need??

No problem, here's how to do it:

Open your notebook or the interactive window
Press ctrl + shift + P
Look for 'Developer: Open Webview Developer Tools' and open it

And that's it, please share the console tab.

No problem, here's how to do it:

Open your notebook or the interactive window
Press ctrl + shift + P
Look for 'Developer: Open Webview Developer Tools' and open it

And that's it, please share the console tab.

Here it is. Thanks.

Hey @lixin6135, sorry to bother you again, but it looks like the error should show up on the other developer tools, can you please send a screenshot of that instead?
You can find it in "Help | Toggle Developer Tools".

Hey @lixin6135, sorry to bother you again, but it looks like the error should show up on the other developer tools, can you please send a screenshot of that instead?
You can find it in "Help | Toggle Developer Tools".

No problem. Check this now, it should be good.

That looks like the extension is having trouble finding your kernel. Could you upload the whole thing? (last upload, I promise). Just on that, do right click, save as and send the whole thing.
Thanks in advance.

That looks like the extension is having trouble finding your kernel. Could you upload the whole thing? (last upload, I promise). Just on that, do right click, save as and send the whole thing.
Thanks in advance.

Thank you so much for help. I have uploaded the whole thing.
-1585615568710.log

And thank you for providing everything. So it look like the python version in your anaconda is 2.7. Could you try to upgrade to 3.6 or 3.7? If I remember correctly, we no longer support python 2.

And thank you for providing everything. So it look like the python version in your anaconda is 2.7. Could you try to upgrade to 3.6 or 3.7? If I remember correctly, we no longer support python 2.

oh, really??? Is there any way that I can still use 2.7 sometimes. Because I am using other's software in my own research, so it has to be 2.7......

Try to run the the "Select Interpreter to start Jupyter server" (after ctrl+shift+P) and see if it works for any of the interpreters on your machine.
If that doesn't work, you could use an older version of the extension. In the Extensions menu, right click over the extension you want to change and select 'Install another version'.

Given the state of Python 2.7 in the community and that the usage of Python 2.7 kernels in our notebook support is known to be very low (around 2%), our internal team has decided the cost of continuing to support Python 2.7 kernel outweighs the need. If a notebook backed by a Python 2.7 kernel has worked for you in the past, you can likely regain that level of support by loading a previous version of the extension from the VS Code Extensions panel. Here is a link that describes how to do this: https://code.visualstudio.com/updates/v1_30#_install-previous-versions.
Any version of the extension with a number of 2020.2.* or prior should provide the support you originally had working.
We realize that for some of you this solution is not ideal. So we are specifically keeping this issue open so as to make it easier and more likely to receive additional user feedback.


[#4558] Add gRPC for Collector

#4558

Codecov Report

Merging #5283 into master will decrease coverage by 0.24%.
The diff coverage is 4.44%.

@@            Coverage Diff             @@
##           master    #5283      +/-   ##
==========================================
- Coverage   40.08%   39.84%   -0.25%
==========================================
  Files        2697     2715      +18
  Lines       81574    82191     +617
  Branches    10924    10990      +66
==========================================
+ Hits        32700    32748      +48
- Misses      45950    46516     +566
- Partials     2924     2927       +3

Impacted Files
Coverage Δ

...or/receiver/thrift/DispatchHandlerFactoryBean.java
0% <ø> (ø)
:arrow_up:

...ver/thrift/tcp/DefaultTCPPacketHandlerFactory.java
70% <ø> (ø)
:arrow_up:

...npoint/collector/receiver/SpanDispatchHandler.java
0% <ø> (ø)

...npoint/collector/receiver/StatDispatchHandler.java
0% <ø> (ø)

...oint/flink/receiver/FlinkPacketHandlerFactory.java
0% <ø> (ø)
:arrow_up:

...r/receiver/thrift/tcp/DefaultTCPPacketHandler.java
67.39% <ø> (ø)
:arrow_up:

...rp/pinpoint/flink/receiver/TcpDispatchHandler.java
0% <ø> (ø)
:arrow_up:

...rofiler/context/compress/SpanProcessorProtoV2.java
0% <ø> (ø)
:arrow_up:

...tor/receiver/thrift/udp/BaseUDPHandlerFactory.java
56.09% <ø> (ø)
:arrow_up:

...int/collector/receiver/thrift/TCPReceiverBean.java
79.48% <ø> (ø)
:arrow_up:

... and 85 more

Continue to review full report at Codecov.

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


openssl: 3.0.7 -> 3.0.8

Description of changes
Testing right now, trying to find release notes, etc.

Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
23.05 Release Notes (or backporting 22.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[ ] Fits CONTRIBUTING.md.

@ofBorg build openssl

Major changes between OpenSSL 3.0.7 and OpenSSL 3.0.8 [7 Feb 2023]

Fixed NULL dereference during PKCS7 data verification ([CVE-2023-0401])
Fixed X.400 address type confusion in X.509 GeneralName ([CVE-2023-0286])
Fixed NULL dereference validating DSA public key ([CVE-2023-0217])
Fixed Invalid pointer dereference in d2i_PKCS7 functions ([CVE-2023-0216])
Fixed Use-after-free following BIO_new_NDEF ([CVE-2023-0215])
Fixed Double free after calling PEM_read_bio_ex ([CVE-2022-4450])
Fixed Timing Oracle in RSA Decryption ([CVE-2022-4304])
Fixed X.509 Name Constraints Read Buffer Overflow ([CVE-2022-4203])
Fixed X.509 Policy Constraints Double Locking ([CVE-2022-3996])

Same for aarch64-darwin, currently trying to complete the stdenv through llvm-11.1.0.


[Avro] Support Union types in Avro Schemas with Schema registry

Is your feature request related to a problem? Please describe.
When decoding messages, that use a union type within the Avro Schema, RW fails to decode these as currently only 1 Type is supported per field.
This requires, that Schemas need to get simplified, e.g. use only string types, which decreases the ability to use strong schemas.
Describe the solution you'd like
ksql introduced an ability to support union types inside avro schemas by creating a 'struct' for this field, that can hold potentially all different types.
E.g. a union type of [null, boolean, double, string] becomes --> STRUCT<BOOLEAN BOOLEAN, DOUBLE DOUBLE, STRING VARCHAR(STRING)>
In addition a wildcard struct operator was introduced, to access the struct without knowing the exact field sinside
See: https://www.confluent.io/blog/announcing-ksqldb-0-27-1/#multi-schema-protobuf-avro-topics
This solution would also work for 'oneOf' types in Protobuf and JSON schemas.
Describe alternatives you've considered
A possible alternative is, to cast union types simply into 'strings'.
Probably easier to implement, but this will again loosen the strong typing approach.
Additional context
No response

It may take some time to reach a consensus on whether it is the desired behavior for RisingWave.

Just as a reference:
KSQL creates automatically this table schemas using this provided Avro Schema:
{
    "namespace": "com.***.***.mqtt",
    "name": "als.DataMessage",
    "type": "record",
    "fields": [
        {
            "name": "metrics",
            "type": {
                "type": "array",
                "items": {
                    "name": "als_data_metric",
                    "type": "record",
                    "fields": [
                        {
                            "name": "id",
                            "type": "string",
                        },
                        {
                            "name": "name",
                            "type": "string",
                        },
                        {
                            "name": "norm_name",
                            "type": [
                                "null",
                                "string"
                            ],
                            "default": null,
                        },
                        {
                            "name": "uom",
                            "type": [
                                "null",
                                "string"
                            ],
                            "default": null,
                        },
                        {
                            "name": "data",
                            "type": {
                                "type": "array",
                                "items": {
                                    "name": "dataItem",
                                    "type": "record",
                                    "fields": [
                                        {
                                            "name": "ts",
                                            "type": "string",
                                            "doc": "Timestamp of the metric."
                                        },
                                        {
                                            "name": "value",
                                            "type": [
                                                "null",
                                                "boolean",
                                                "double",
                                                "string"
                                            ],
                                            "doc": "Value of the metric."
                                        }
                                    ]
                                }
                            },
                            "doc": "The data message"
                        }
                    ],
                    "doc": "A metric object"
                }
            },
            "doc": "A list of metrics."
        }
    ]
}

KSQL Table
METRICS | ARRAY<STRUCT<ID VARCHAR(STRING), NAME VARCHAR(STRING), NORM_NAME VARCHAR(STRING), UOM VARCHAR(STRING), DATA ARRAY<STRUCT<TS VARCHAR(STRING), VALUE STRUCT<BOOLEAN BOOLEAN, DOUBLE DOUBLE, STRING VARCHAR(STRING)>>>>>

Any updates on this? This is the only reason blocking us from migrating away from KSQL

Also, IIUC, union with null in Avro schema basically means nullable. For example,

Avro: union[null, string] -> RW: varchar rather than struct
Avro: union[null, string, long] -> RW: struct<string, long>

as a result, union might be more frequently used in Avro compared with Protobuf's oneof.

This might be wrong. Post the comments from @xiangjinwu here:

Disagree with this. It was controversial (2015, 2018) until confluent uses it to represent multiple schemas in a single topic in 2020, which is then added in ksql in 2022 (2 years later). My experience here may be limited though.
It is already mid-2024 and I am not against supporting it. But the design space is still quite open compared to other more common data types. I will try to list down the details I am concerning before the end of next week.

Similar to map #13387 we considered several ways to support it:

A native union data type
jsonb
struct with one field for each nonnull member, as proposed above
struct with 1+N fields, with an additional explicit tag

However, the interface and semantic of a native union is not as universal as map across databases or programming languages. To avoid committing to a premature design, we will not do it right now. Out of the workarounds:

jsonb is weak in typing and has no advantage of O(logn) lookup as in map workaround
struct without tag field will be treated as a struct regarding input / output / ordering / casting
struct with tag field can get union-specific treatment but that makes it an awkward non-native union-like type

So we will follow the original struct design without tag for the initial version. To elaborate on its abilities and restrictions:

Testing active variant can be done via IS NOT NULL, thanks to the fact that avro does not allow inner member to be active but still equals null. (This does not hold for protobuf oneof.)
"Downcast" to a specific variant type can be done via struct field access.
"Upcast" or construct from a specific variant will have to be verbose and position-based (rather than name-based): row(null, null, variant_c, null)
Casting from a subset to a superset is impossible. Because we cannot cast from a struct with less fields to a struct with more fields.


Add logger from commons

Closes https://github.com/api3dao/airseeker-v2/issues/8
Rationale
Adds the logger from @api3/commons.The logger accepts some configuration and I've opted in configuration from ENVs. Alternative would be to put the logger configuration to config.json, but it creates a wierd dependency of not being able to use logger until the config is loaded (similarly, if config fails to load you can't log it).
The implementation is very similar to pusher.

I found it odd that the imports in src/env/env.ts are separated by new lines, but that's super minor.

That is part of ESLint. It takes care of grouping imports and each group is separated by new line.


parse data from a form

I have reviewed your example:
express.use("/city/:name", .POST) { request, response in
    guard let cityName: String = request.getParameter("name") else { return true }

    print("Creating city with name: \(cityName)")
    citiesLock.lock(); defer { citiesLock.unlock() }
    cities.append(cityName)
    response.send("\(cities)")
    return false
}

but I am wondering how can I parse fields of an html form with POST ?  request.getParameter is the :name in the url but I can't figure out how to parse post parameters.

POST parameters should be in body of the request. But there is no build in parser for that.

@diejmon thank you for your reply. as a work around I will try to send the form data as json! (I tried to parse request.body but all I get is some bytes)

You can try use json method on Request to parse body to Decodable type. Or just convert Data to string and to anything with it. :)

do you mean like this ?

struct Form: Codable {
  let name: String
  let email: String
  let message: String
}

express.use("/form", .POST) { request, response in

    let article = try! request.json(Form.self);

    print (article)

    print("article is : \(article)")

    response.send("post done")
    return false
}

I am now trying to get the form to send JSON to /form so it can be parsed (and then added to the database). If is not too much trouble can you show me how you would do it ? 👍

okay here is my full workaround:

first you need a form sending JSON data

<form id="myform" method="post" action="/form">
      Name: <input type="text" name="name" value="david">

      email: <input type="text" name="email" value="">

      message: <input type="text" name="message" value="this is a message ">

       <input type="submit" value="Submit">
      </form>

then the struct and  route

struct Form: Codable {
  let name: String
  let email: String
  let message: String
}

express.use("/form", .POST) { request, response in

    let article = try! request.json(Form.self);

    print (article.name)

    print("article is : \(article)")

    response.send("post done")
    return false
}

all working :) so now can add the single post elements to the database.

Nice! Closing the issue.


fix: cardList size + elevation

:tada: This PR is included in version 1.1.13 :tada:
The release is available on:

GitHub release
1.1.13
npm package (@latest dist-tag)

Your semantic-release bot :package::rocket:


Latest Entry/value

Hello everyone,
First of all, thank you so much for this awesome work. Im using it with my Thermostat Plugin. Everything works fine.
So i wanted to create something new in regard of the Motion Sensors. And therefore i wanted to know if its possible to get the latest Entry (time, Status value) from Fakegato history

It’s not a supported functionality, but you should be able to access the latest entry with something like fakegato.history[fakegato.lastEntry]. Why do you need it? You should alredy know which is the last entry you added.

Hey, thanks, i already solved the Problem :)

Hi, fakegato.history[fakegato.lastEntry] does not do the job after wrap-around.
The solution is fakegato.history[fakegato.lastEntry % fakegato.memorySize]

Hi,
I'm currently using a homebrdige service on rp3 with homebridge-Xiaomi-plant care plugin.
Works fine, it's working with fakegato-history too.
https://github.com/honkmaster/homebridge-mi-flower-care
But, I would like to display the lastest time on records
Do you have an idea ?
Thanks


Fix issue with optional chaining and type inference in type guard

Fixes #34974

@typescript-bot test top100
@typescript-bot user test this
@typescript-bot run dt
@typescript-bot perf test this

It must be getting too close to spooky season because I read the issue title as "Fix issue with ... type gourd" 🎃


Adding m == 0 shortcut to mbedtls_ecp_mul_shortcuts()

Description
Resolves: #1792
Short issue #1792 description:
"ECDSA verification (mbedtls_ecdsa_verify or mbedtls_ecdsa_read_signature) returns MBEDTLS_ERR_ECP_INVALID_KEY when the payload (which should be a hash) is all-bits zero. The curve is a short Weierstrass curve."
root cause: ecp_mul_restartable() function is very strict and don't handle situation like that.
Fix: There was a new shortcut added to the mbedtls_ecp_mul_shortcuts() It is a shortcut for a situation when m == 0.
Status
READY
Requires Backporting
Rather NO (fix for 3.0)
Migrations
NO
Todos

[ ] Tests
[ ] Documentation
[ ] Changelog updated

Steps to test or reproduce
Please check: #1792

You've made the PR against the wrong branch (which is why it has so many unrelated commits): this should go to development, not to the 3.0 branch.


Add required object to date and time pickers

So i am using react-toolbox components in some of my forms and let me say I like it a lot. The one thing I am missing though is the ability to add a required prop to the date and time pickers to match the other input components in my forms.
Could I get some help on how I would do this manually or can I put in a feature request to have this added to the default component?

Thanks! There is an [spread] of additional properties over the Input component so you should be able to pass a required field and any other one not listed in the DatePicker properties but present for the Input component. It should work, if it doesn't please let me know to reopen the issue and check it out again :)

Hi @javivelasco, I tried above and it doesn't seem to work. The component source code looks right to me, so I'm not sure where the bug is coming from. Will let you know if I find a fix.

Ok so I've verified that DatePicker input does get added "required" prop correctly, but does not go through validation fully. See attached screenshot.


Clicking failed mocha test file (via VSC debug) doesn't open the file.

VSCode Version: 1.7.1
OS Version: macOS 10.12.1

Steps to Reproduce:
See project: https://github.com/vlod/hello-test

Click the debug icon in the left sidebar, make sure 'Test' is selected and hit run
Clicking on the failed error: 'hello-test.js:7:24' should open the file.

Above github project has screenshots.

@vlod thanks you for the great reproducable steps, however can you please try this in latest vscode insiders since we have improved our relative link detection.
fyi @felixfbecker

Oh.. I didn't realize you had a beta-version of the VSC.
Trying it with Version 1.8.0-insider, I can confirm that my test case doesn't fail any more.
Fabulous.. thanks for all your hard work!

@vlod great! You can thank @felixfbecker


Server statistics

[x] monthly/~yearly~ server statistics
[x] filter by user handle
[x] most contests given by users
[x] ~most upsolving done by users~

Have verified

;serverstat
;serverstat jul-20
;serverstat jan-20 fangahawk


Anonymous predicate function

I think this should be possible:
declare function filter<T, P: $Pred<1>>(arr: Array<T>, p: P): Array<$Refine<T,P,1>>;
filter(arr, x => x);

Currently you get Function is incompatible with abstract predicate function and it seems that the only way to make a function a predicate is to use function declaration.

Never mind, this works: filter(x, (x): %checks => x). But it would be nice if Flow could infer %checks

That's the plan, ideally. Predicate support was started by @panagosg7 as an intern, and @avikchaudhuri has some follow-up work to land still. Stay tuned!
Ref #34

Closing since I believe this has been resolved.

Well, my original example doesn't work.


Remove daemon RPC dependency

By removing the RPC dependency we can allow easier unit testing and perhaps improve the general sync rate
https://github.com/dloa/media-protocol/blob/c61eb029789f6afcbdd1978e7704d09749917a93/utility/util.go#L18
https://github.com/dloa/media-protocol/blob/c61eb029789f6afcbdd1978e7704d09749917a93/utility/util_test.go#L27

Done by 34588f7de0c4de57247fc15bceed69629a6624d9