API issue

Hey, I am new to deck.gl but having some issues.Whenever i try to use API as data like I am trying to use the following api
data: 'https://envirocar.org/api/stable/measurements'

but it doesn't work or if i put api's data in a json file and put that in my current working
directory it doesn't work for example:
data:'../data_file.json'

even .csv files doesn't work but when I use data in a array form like following it works.I don't why if anybody knows please help me.
data: [
   {
      "type": "Feature",
      "geometry": {
         "type": "Point",
         "coordinates": [
            6.4847174678758375,
            51.22546715521443
         ]
      }
]

<--------------------------------------------------------------------------------------------------------------------------------->
I am talking about the data in _renderLayers()
import React, {Component} from 'react';
import {render} from 'react-dom';
import {StaticMap} from 'react-map-gl';
import DeckGL from<EMAIL_ADDRESS>import {ScatterplotLayer} from<EMAIL_ADDRESS>
const MAPBOX_TOKEN = process.env.MapboxAccessToken;
const INITIAL_VIEW_STATE = {
  longitude: 6.4847174678758375,
  latitude: 51.22546715521443,
  zoom: 11,
  maxZoom: 16,
  pitch: 0,
  bearing: 0
};

export default class App extends Component {
  _renderLayers() {
    return [
      new ScatterplotLayer({
        id: 'scatter-plot',
        data: 'https://envirocar.org/api/stable/measurements',
        radiusScale: 10,
        radiusMinPixels: 0.25,
        getPosition: d => (d.features.geometry.coordinates),
        getFillColor: [255,0,255],
      })
    ];
  }

  render() {
    const mapStyle = 'mapbox://styles/mapbox/light-v9';

    return (
      <DeckGL layers={this._renderLayers()} initialViewState={INITIAL_VIEW_STATE} controller={true}>
        <StaticMap
          reuseMaps
          mapStyle={mapStyle}
          preventStyleDiffing={true}
          mapboxApiAccessToken={MAPBOX_TOKEN}
        />
      </DeckGL>
    );
  }
}

export function renderToDOM(container) {
  render(<App />, container);
}

The absolute URL you pass to data must have an extension for Deck to know what format it is.
The relative URL must be relative to the execution path during runtime, not the source code.
CSV files are not supported out of the box, you can add it by
import {registerLoaders} from<EMAIL_ADDRESS>import CSVLoader from<EMAIL_ADDRESS>
registerLoaders(CSVLoader)


Question: Can we miss usages data if sampleRate is less than 1.0?

Question: Can we miss usages data if sampleRate is less than 1.0?
I see that we can set a sampleRate here: https://the-guild.dev/graphql/mesh/docs/guides/hive

sampleRate (type: Float) - Sample rate to determine sampling. 0.0 = 0% chance of being sent 1.0 = 100% chance of being sent Default: 1.0

Does this mean that we can be missing some data for low usage fields if the sample rate is less than 100%?
For example,

field_1 is used 100 times in 1 day
field_2 is used 1 time
samepleRate: 0.8

Is there a 20% chance that we have no usages for field_2?

yes

Here’s a whole chapter about sampling
https://the-guild.dev/graphql/hive/docs/api-reference/client#sampling
There are more sampling possibilities than the one you mentioned. In your case the At Least Once Sampling is a good choice.
Basic sampling
With sampleRate option, you're able to control the sampling rate of the usage reporting. Setting it to 0.5 will result in 50% of the operations being sent to Hive. There is no guarantee that every operation will be reported at least once (see atLeastOnceSampler).
Dynamic sampling
GraphQL Hive client accepts a function that returns a number between 0 and 1. This allows you to implement dynamic sampling based on the operation's context.
At-least-once sampling
If you want to make sure that every operation is reported at least once, you can use the atLeastOnceSampler. Every operation is reported at least once, but every next occurrence is decided by the sampler.

Hi @amanb014 !
As @kamilkisiela said, you have full control over sampling strategy. If you want to ensure you collect each operation at least once, you should use the atLeastOnceSampler.


pathlib.Path support for keras

this adds pathlib support to keras functions taking paths as arguments, see #37357

I think we should mostly do the conversion just before calling the filesystem layer (e.g., in tf.io.gfile.... methods).
For the cases where those methods are not used and developers used the natural Python functions, I think we should first attempt a conversion to the wrapped ones. Only if this conversion does not make sense should we try to convert path-like objects to string in the other cases.
The utility can reside in TF proper, might need a public tf. name (via tf_export decorator).
We should also get a review from the API owners

I have added a commit that should add (partial) support for python 3.4/3.5. I have made the import to os unconditional, since I expect this to be fast (lookup, since this will be loaded elsewhere), and put the pathlib import for the 3.4/3.5 implementation into the function, so that this does not affect import times.

@ngc92 Can you please address Ubuntu Sanity errors? Thanks!

I found that tensorflow offers a public API function tf.compat.path_to_str which mostly does the same thing my function does, only completely bypassing the python standard library.
Should I remove my function in favour of the function that is already there?
I think the compat implementation does not support pathlib for python versions older than the fspath protocol, though (so 3.4 and 3.5).
The implementation there is simply
if hasattr(path, '__fspath__'):
    path = as_str_any(path.__fspath__())
return path

I think that if we find a difference between the two function we can decide then which one to support and which one to deprecate.
If, however, both functions behave the same then we should use the existing one.

there should only be a difference for python 3.4/3.5, because the __fspath__() attribute does not exist there.
apart from that, the question is whether it is cleaner to do things with python standard library functions instead of recoding them, i.e. the relevant documentation is
os.fspath(path)
    Return the file system representation of the path.
    If str or bytes is passed in, it is returned unchanged. Otherwise __fspath__() is called and its value is returned as long as it is a str or bytes object. In all other cases, TypeError is raised.
    New in version 3.6.

class os.PathLike
    An abstract base class for objects representing a file system path, e.g. pathlib.PurePath.
    New in version 3.6.
    abstractmethod __fspath__()
        Return the file system path representation of the object.
        The method should only return a str or bytes object, with the preference being for str.

The only problem is python 3.5 compatibility.

Let's keep both for now as we still release 3.5 pips. Once we can deprecate python 3.5 pips we will deduplicate.


LibWeb: Use a default XML namespace for HTML tag

If no xmlns is provided for an HTML tag, we should assume it's in the HTML namespace.
There's probably a better way to do this but for now, this should fix a bunch of WPT tests.

Closing this since it was implemented by @alimpfard in https://github.com/LadybirdBrowser/ladybird/pull/1751


Language selection

Describe the solution you'd like
I'm looking for a way to add support for a few languages. The way I imagine that is that you can see the flag icon in the header and after clicking it, you can see other flags that will convert the webpage to another language.
There are a few problems with the fact that not all the strings in the page come from config/index.json. However the real problem for me is that I don't know how o dynamically change the content of the config/index.js, so that the correct language is reloaded. Should I add another field in the config/index.js or create something like config/index-nl.js?
I'm not experienced frontend developer so I don't really know the conventions.
Thanks

This https://react.i18next.com/ could be a really good solution to your problem! Then you would have as many versions of the index.json as you have languages, and would need to change from using index.json data directly to using something like useTranslation or translate() which are utils that i18n-react gives!
I hadn't planned on adding multilinguel support for now, but if i get the time I'll try adding it to the template!

Thank you for the hint. I'll try to add it, I think adding it to the template would make this great code more close to the ultimate solution.


Test Errors don't match Figure 1

Making a note here of what might be causing this problem:

momentum and learning rate have not been tuned (particularly mometum, as ADAM shouldn't require tuning)
seeds are not explicitly changed between runs (runs appeared to be stochastic anyway, so didn't fix it right away)
dropout implementation may not match paper due to ambiguities detail in #2 or mistakes
experiment may not match because we don't know which type of adaptivity to use: #4

Don't have the code used in the paper to reproduce it, but variational dropout A is still outperforming the others, so the code is probably good enough.


Build  model_pruning for bug

Hi,
bazel build -c opt examples/cifar10:cifar10_{train,val}
EERROR: Skipping 'examples/cifar10:cifar10_train': no such package 'tensorflow/contrib/examples/cifar10': BUILD file not found on package path
ERROR: no such package 'tensorflow/contrib/examples/cifar10': BUILD file not found on package path
Thank you for your help!

It looks like you haven't used a template to create this issue. Please resubmit your issue using a template from here. We ask users to use the template because it reduces overall time to resolve a new issue by avoiding extra communication to get to the root of the issue. We will close this issue in lieu of the new one you will create from the template. Thank you for your cooperation.


Add credit card icons to StripeForm

Impact: minor
Type: fix
Adds credit card icons in SVG format.

🚀 Preview deployed
Built with commit 2e94d30b5f7fa285c88ed9b9dc4f2837db7e64f4
https://deploy-preview-225--stoic-hodgkin-c0179e.netlify.com

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Add host and port to broadcasting

[X] Changes have been thoroughly tested to not break existing functionality.
[ ] New functionality has been documented or existing documentation has been updated to reflect changes.
[ ] Visual changes are explained in the PR description using a screenshot/recording of before and after.

I don't think documentation has to be changed for this, if so, I'm happy to sync. :)
The reason for adding wsHost + wsPort/wssPort, is when someone uses a Nginx proxy for sockets (like we do).
It could also be someone using the docker container host and listening on a different url.

Thanks


1V1 environmnet

Hi ,
Thank you very much for giving such a nice tool. I just have one problem, will you offer some compatible 1v1 environments in the future? For example, in current Pong and droidfish chess, we can train an rl-agent against built-in bots. But you know, we need the help of selfplay to get a stronger rl-agent.
Besides, will you also consider environments that need two ro more players to coorparate?
Thanks.

Regards,
Shenghan

Hello @sheng-han-zhang!
When we run multiplayer environments, we usually introduce a layer above the actual environment to coordinate the process. This layer usually prepares the observation for each player, receives their actions and forwards them to the environment. We currently don't have this for AndroidEnv and are not working on it, but we are generally not against the idea. The bots in the current tasks are actually already challenging for most agents, and we'd like to tackle those first before thinking of going way beyond them. ;)
I hope this helps,
Cheers,
Daniel

Hi Daniel,
Thank you very much for your detailed reply.
You are right the current tasks are already challenging enough. Hope can hear more good news from you in the future.
Best,
Shenghan


Fixes bug where multiple no citations were found if searching by mult…

…iple municipalities

@ctwoolsey This branch is all messed up. You have all the commits from a different branch in here. One of your commits says: "Merge branch 'courtMuniRelationship' into fix-mulit-muni-citation-search". Why did you merge that branch into this branch? Could this be why you've had some branch problems in the past?

That is not why the other branches have had problems.  This is the first time I did a merge.  This branch depends on the new court/muni changes in order to work and be tested.  So I started this branch made the changes and realized I needed the other branches changes to test it, so I merged those changes into this branch and was able to test.


added wss to the pm2 config

@heckj @RackHD/corecommitters
Discovered that the pm2 config was missing the websocket server, so posting this quick fix.
-DJ

@yyscamper I think the CI should use a different config specifically for testing essential RackHD components. Though it may be a good idea to include on-wss in the tests despite it being non-essential.

@DavidjohnBlodgett @rolandpoulter : How about changing this PR to create a new pm2 config file? this config file will run on-wss, user can choose to run this or that, and meanwhile the current CI doesn't need any change.

@yyscamper I think the CI should use a custom pm2 config. Generally that is how I would expect it to work. Ideally on-wss is running when people test out RackHD incase they want to use the UI

This PR appears to have gone stale.   Please reopen if ready to move forward.


Unit Testing style guide

We should have a Unit Testing Style Guide for the project to ensure all Unit tests are written in a uniform, consistent and clear manner.

Closed via #321


test/k8s/manifests: bump test-verifier image to latest version

This will pull in Go 1.18 and will allow commit ee2e83f352c6 ("ip: Add
helpers to assist net -> netip transition") to be applied again without
breaking the K8sVerifier test in CI.

/test-1.24-net-next --focus=K8sVerifier


Seems that explicitly releasing the staging repository is not necessary

I need to read documentation with more concentration ...

This pull request is now managed with CodeReviewHub. Refresh.


First page of the carousel doesn't display when page is refreshed on smaller view-ports

I have started to experience an issue when adjusting the slides to mobile. If I refresh the page of the highest width, it will work fine but if I simulate a smaller view-port and refresh the page, it will not display the first page of the slide, and when clicking on an arrow, it will skip the first page and just straight to the second page.
Desktop:

Any smaller view-port:

I have a component that holds the slider with the following settings:
const settings = {
  dots: true,
  infinite: false,
  draggable: false,
  slidesToShow: 8,
  slidesToScroll: 8,
  initialSlide: 0,
  lazyLoad: 'progressive',
  nextArrow: (
    <SlickArrow>
      <ChevronRight />
    </SlickArrow>
  ),
  prevArrow: (
    <SlickArrow>
      <ChevronLeft />
    </SlickArrow>
  ),
  responsive,
}

The responsive is passed via props, and it's as follows:
export default [
  {
    breakpoint: 1920,
    settings: {
      slidesToShow: 8,
      slidesToScroll: 8
    }
  },
  {
    breakpoint: 1792,
    settings: {
      slidesToShow: 7,
      slidesToScroll: 7
    }
  },
  {
    breakpoint: 1492,
    settings: {
      slidesToShow: 6,
      slidesToScroll: 6
    }
  },
  {
    breakpoint: 1280,
    settings: {
      slidesToShow: 5,
      slidesToScroll: 5
    }
  },
  {
    breakpoint: 1080,
    settings: {
      slidesToShow: 4,
      slidesToScroll: 4
    }
  },
  {
    breakpoint: 720,
    settings: {
      slidesToShow: 3,
      slidesToScroll: 3
    }
  },
  {
    breakpoint: 560,
    settings: {
      slidesToShow: 2,
      slidesToScroll: 2,
    }
  }
];

If the responsive array has only one object, it will not occur, but as soon as there are two, it will.

I made some adjustments and it seems that some breakpoints value are causing the issue. Is there a list of valid breakpoints?

Hi,
I have the same problem, which occurs when I add a responsive array in the config, have you found a solution ?


PR for issues #30 and #13

Submit Implement Clos topology in Distrinet again
Fix the error in distrinet deployment： The unauthenticated git protocol on port 9418 is no longer supported.

Two modifications have passed local tests.


Syncing charts with diferent datetime xaxis

Hello,
I want to sync two graphs which I want to have the same dates in datetime xaxis. But there are not values for both graphs at all days so I tried this:
  labels: {
    minWidth:120,
    format: 'dd/MM',
  },

but still I get something like that:

How could I do it to have the same x-axis?
Thank you

Try setting xaxis.min and xaxis.max in both the graphs to the same values.

@junedchhipa thx for answering but for me xaxis.min and xaxis.max can't give any effect.
do you have any other solution?


ACME CA certificate  request is failing with externalAccountBinding error ...

Using the documentation, I was able to create ACME CA with the URL provided by Sectigo. Then when I tried sample cert request it failed with the following error:
acme.messages.Error: urn:ietf:params:acme:error:externalAccountRequired :: The server requires external account binding :: The request must include a value for the "externalAccountBinding" field
2020-09-09 00:49:01,065 DEBUG: {'function': 'lemur.common.celery.sync_source_destination', 'message': 'syncing AWS destinations and sources', 'task_id': 'ef39db61-def1-4d8c-9210-86559f4e1c63'} [in /opt/app/lemur/lemur/common/celery.py:582]
I am using /opt/app/lemur as installation folder.
I understand, I may have to have the CONFIG details for EAB ID and EAB Key for External Account Binding.
What I need help is to how to pass these values in lemur.conf.py or other location? I do not see these options when ACME accounts are created. How do we handle multiple ACME providers and their configurations.

I tried the following:
Pass EAB HMAC key for ACME_PRIVATE_KEY and
ACME_REGR = '{"body": {}, "uri": "https://acme.sectigo.com/v2/InCommonRSAOV/acct/EAB_KID"}'
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/opt/app/lemur/lemur/certificates/service.py", line 348, in create
cert_body, private_key, cert_chain, external_id, csr = mint(**kwargs)
File "/opt/app/lemur/lemur/certificates/service.py", line 298, in mint
cert_body, cert_chain, external_id = issuer.create_certificate(csr, kwargs)
File "/opt/app/lemur/lemur/plugins/lemur_acme/plugin.py", line 637, in create_certificate
acme_client, registration = self.acme.setup_acme_client(authority)
File "/opt/app/lemur/lib/python3.6/site-packages/retrying.py", line 49, in wrapped_f
return Retrying(*dargs, **dkw).call(f, *args, **kw)
File "/opt/app/lemur/lib/python3.6/site-packages/retrying.py", line 212, in call
raise attempt.get()
File "/opt/app/lemur/lib/python3.6/site-packages/retrying.py", line 247, in get
six.reraise(self.value[0], self.value[1], self.value[2])
File "/opt/app/lemur/lib/python3.6/site-packages/six.py", line 703, in reraise
raise value
File "/opt/app/lemur/lib/python3.6/site-packages/retrying.py", line 200, in call
attempt = Attempt(fn(*args, **kwargs), attempt_number, False)
File "/opt/app/lemur/lemur/plugins/lemur_acme/plugin.py", line 244, in setup_acme_client
key = jose.JWK.json_loads(existing_key)
File "/opt/app/lemur/lib/python3.6/site-packages/josepy/interfaces.py", line 182, in json_loads
raise errors.DeserializationError(error)
josepy.errors.DeserializationError: Deserialization error: Expecting value: line 1 column 1 (char 0)
2020-09-11 16:18:12,439 ERROR: Exception minting certificate [in /opt/app/lemur/lemur/certificates/service.py:350]
Traceback (most recent call last):
File "/opt/app/lemur/lib/python3.6/site-packages/josepy/interfaces.py", line 180, in json_loads
loads = json.loads(json_string)
File "/usr/lib/python3.6/json/init.py", line 354, in loads
return _default_decoder.decode(s)
File "/usr/lib/python3.6/json/decoder.py", line 339, in decode
obj, end = self.raw_decode(s, idx=_w(s, 0).end())
File "/usr/lib/python3.6/json/decoder.py", line 357, in raw_decode
raise JSONDecodeError("Expecting value", s, err.value) from None
json.decoder.JSONDecodeError: Expecting value: line 1 column 1 (char 0)
I am also checking with my CA support on the correct URI to pass.

When I register with certbot client, it registers with the following information:
{"body": {}, "uri": "https://acme.sectigo.com/v2/InCommonRSAOV/account/EAB_KID"}
Where EAB_KID is my account ID. I tried recreating the Authority by passing this URL. I still get above Python error. Now, I believe, passing ACME_PRIVATE_KEY in lemur.conf.py resolved externalAccountBinding error.
Next battle is with this Python error..

ACME_PRIVATE_KEY needs to be in the JWK format (e.g. similar to this)
{
    "kty": "RSA",
    "n": "yr1qBwHizA7ME_iV32bY10ILp.....",
    "e": "AQAB",
    "d": "llBlYhil3I.....",
    "p": "-5LW2Lewogo.........",
    "q": "zk6dHqHfHksd.........",
    "dp": "qfe9fFIu3mu.......",
    "dq": "cXFO-loeOyU.......",
    "qi": "AfK1sh0_8sLTb..........."
}

Using python-jwt this can be done with a simple script
import python_jwt as jwt, jwcrypto.jwk as jwk, datetime

priv_key = jwk.JWK.from_pem(b"""-----BEGIN RSA PRIVATE KEY-----
.......
-----END RSA PRIVATE KEY-----""")

print(priv_key.export())

I have certbot client installed on the same machine. When I registered Sectigo ACME server it created private key json file.
It is in this format:
{
"n": "PwIOkViO ......",
"e": "AQAB",
"d": "NWX .... ",
"p": "6-x3 ... ",
"q": "3j- .....",
"dp": "HhXQfDWRLIE ....",
"dq": "3kj43ZTzvsE ....",
"qi": "AlLaMQBcky8 ....",
"kty": "RSA"
}
After using this I got ill formatted URL for
ACME_REGR = '{"body": {}, "uri": "https://acme.sectigo.com/v2/InCommonRSAOV/acct/EAB_KID"}'
Then I changed this to
ACME_REGR = '{"body": {}, "uri": "https://acme.sectigo.com/v2/InCommonRSAOV"}'
and
{
"n": "PwIOkViO ......",
"e": "AQAB",
"d": "NWX .... ",
"p": "6-x3 ... ",
"q": "3j- .....",
"dp": "HhXQfDWRLIE ....",
"dq": "3kj43ZTzvsE ....",
"qi": "AlLaMQBcky8 ....",
"kid": "pW4 ...",
"kty": "RSA"
}
Passing EAB_KID in JWK format. I still get error:
acme.messages.Error: urn:ietf:params:acme:error:externalAccountRequired :: The server requires external account binding :: The request must include a value for the "externalAccountBinding" field
ACME_REGR = '{"body": {}, "uri": "https://acme.sectigo.com/v2/InCommonRSAOV/acct/EAB_KID"}' is giving ill format error

It looks like acme.sectigo.com is using the externalAccountBinding described in the acme spec 7.3.4.  External Account Binding, but LetsEncrypt doesn't use it, and the current implementation of the acme plugin, doesn't support it either.
I would check with sectigo.com, which account uri that needs to be used. Normally you should be able to get the account details (including the account uri), when trying to create a new account, using the existing private key.
I've used ansible to do that, and get the account uri
    - name: get acme account info
      acme_account_info:
        acme_version: 2
        acme_directory: https://acme-staging-v02.api.letsencrypt.org/directory
        account_key_src: ./acme.key
      register: account_data

    - name: display account information
      debug:
        var: account_data

You would need to replace the acme_directory parameter with the directory provided by sectigo.
Or you can implement it, in lemur/lemur/plugins/lemur_acme/plugin.py
https://github.com/Netflix/lemur/blob/772894c414baca916c44ce1f91fb3fe6b33c88f1/lemur/plugins/lemur_acme/plugin.py#L260-L265
You would need to add an externalAccountBinding to the from_data call, which seems to support this parameter according to the acme-python documentation

When I register with Certbot against InCommon with EAB KID and EAB Key, it provides the ACME_PRIVATE_KEY in JWK format. I then used those details along with regr.json info for ACME_REGR. Finally, by using InCommon ACME URL for ACME_DIRECTORY_URL I am not getting malformed URL error.
Now, I get the following error:
raise Exception("Unable to determine DNS challenges from authorizations")
Exception: Unable to determine DNS challenges from authorizations
2020-09-24 19:46:44,388 ERROR: {'function': 'lemur.common.celery.fetch_acme_cert', 'message': 'Pending certificate creation failure', 'task_id': '84b6997f-1729-464e-be42-bbdad5b24436', 'id': 3, 'pending_cert_id': 3, 'last_error': Exception('Unable to determine DNS challenges from authorizations',), 'cn': 'Servername'} [in /opt/app/lemur/lemur/common/celery.py:320]
What I observed is that InCommon ACME does not do DNS validations as long as EAB Kid and Key are matching. This looks like another enhancement to make DNS validation as optional for externalAccountBinding ACME providers :-)


Terminal cursor broken

Does this issue occur when all extensions are disabled?: Yes

VS Code Version: Newest stable build (not insiders)
OS Version: Linux

Steps to Reproduce:

Press alt-click
Watch it spazz out
https://user-images.githubusercontent.com/71727937/146626370-ebddc8b0-c02f-4580-9723-743ae6541e20.mp4

can you share your settings.json? I can't reproduce the problem

can you share your settings.json? I can't reproduce the problem

{
    "terminal.integrated.commandsToSkipShell": [
        "language-julia.interrupt"
    ],
    "julia.enableTelemetry": true,
    "workbench.colorTheme": "Default Light+",
    "julia.NumThreads": 12,
    "git.autofetch": true,
    "terminal.integrated.tabs.enabled": false,
    "git.confirmSync": false,
    "julia.enableCrashReporter": true,
    "juliaFormatter.alwaysForIn": true,
    "juliaFormatter.alwaysUseReturn": true,
    "juliaFormatter.conditionalToIf": true,
    "juliaFormatter.formatDocstrings": true,
    "juliaFormatter.shortToLongFunctionDef": true,
    "[julia]": {
        "editor.defaultFormatter": "singularitti.vscode-julia-formatter"
    },
    "juliaFormatter.style": "blue",
    "formatContextMenu.closeAfterSave": true,
    "files.associations": {
        "*.rmd": "markdown"
    },
    "juliaFormatter.whitespaceInKwargs": false,
    "editor.hover.delay": 200,
    "editor.rulers": [
    80,92,104
    ],
    "julia.focusPlotNavigator": true,
    "julia.completionmode": "qualify",
    "juliaFormatter.pipeToFunctionCall": false,
    "juliaFormatter.overwriteFlags": true,
    "julia.lint.disabledDirs": [
        "docs",
        "test"
    ],
    "editor.minimap.enabled": false,
    "juliaFormatter.whitespaceTypedefs": true,
    "juliaFormatter.whitespaceOpsInIndices": true,
    "terminal.integrated.cursorStyle": "line",
    "terminal.integrated.cursorBlinking": true,
    "julia.symbolCacheDownload": true,
    "workbench.panel.defaultLocation": "right",
    "julia.additionalArgs": [

    ],
    "julia.execution.resultType": "REPL",
    "julia.execution.codeInREPL": true,
    "julia.notebookController": true,
    "julia.executablePath": "/usr/bin/julia",
    "breadcrumbs.enabled": false,
    "notebook.lineNumbers": "on",
    "notebook.consolidatedRunButton": true,
    "notebook.undoRedoPerCell": false,
    "latex-workshop.bibtex-format.tab": "tab",
    "local-history.path": ".vscode",
    "julia.runtimeCompletions": true,
    "terminal.integrated.scrollback": 10000,
    "editor.unicodeHighlight.allowedCharacters": {
        "ρ": true,
        "σ": true
    },
    "editor.unicodeHighlight.ambiguousCharacters": false,
    "window.enableMenuBarMnemonics": false,
    "window.customMenuBarAltFocus": false
}

thanks, can repro with your settings.

seems like some recursion is going on, the log with keybinding troubleshoot:
AltLeft, keyCode: 6 ('Alt')
[2021-12-28 18:55:16.048] [renderer1] [info] [KeybindingService]: \ Keyboard event cannot be dispatched in keydown phase.
[2021-12-28 18:55:16.083] [renderer1] [info] [KeybindingService]: / Received  keydown event - modifiers: [alt], code: AltLeft, keyCode: 18, key: Alt
[2021-12-28 18:55:16.084] [renderer1] [info] [KeybindingService]: | Converted keydown event - modifiers: [alt], code: AltLeft, keyCode: 6 ('Alt')
[2021-12-28 18:55:16.084] [renderer1] [info] [KeybindingService]: \ Keyboard event cannot be dispatched in keydown phase.
[2021-12-28 18:55:16.113] [renderer1] [info] [KeybindingService]: / Received  keydown event - modifiers: [alt], code: AltLeft, keyCode: 18, key: Alt
[2021-12-28 18:55:16.115] [renderer1] [info] [KeybindingService]: | Converted keydown event - modifiers: [alt], code: AltLeft, keyCode: 6 ('Alt')
[2021-12-28 18:55:16.115] [renderer1] [info] [KeybindingService]: \ Keyboard event cannot be dispatched in keydown phase.
[2021-12-28 18:55:16.147] [renderer1] [info] [KeybindingService]: / Received  keydown event - modifiers: [alt], code: AltLeft, keyCode: 18, key: Alt
[2021-12-28 18:55:16.148] [renderer1] [info] [KeybindingService]: | Converted keydown event - modifiers: [alt], code: AltLeft, keyCode: 6 ('Alt')
[2021-12-28 18:55:16.148] [renderer1] [info] [KeybindingService]: \ Keyboard event cannot be dispatched in keydown phase.
[2021-12-28 18:55:16.174] [renderer1] [info] [KeybindingService]: / Received  keydown event - modifiers: [alt], code: AltLeft, keyCode: 18, key: Alt
[2021-12-28 18:55:16.175] [renderer1] [info] [KeybindingService]: | Converted keydown event - modifiers: [alt], code: AltLeft, keyCode: 6 ('Alt')
[2021-12-28 18:55:16.176] [renderer1] [info] [KeybindingService]: \ Keyboard event cannot be dispatched in keydown phase.
[2021-12-28 18:55:16.210] [renderer1] [info] [KeybindingService]: / Received  keydown event - modifiers: [alt], code: AltLeft, keyCode: 18, key: Alt
[2021-12-28 18:55:16.211] [renderer1] [info] [KeybindingService]: | Converted keydown event - modifiers: [alt], code: AltLeft, keyCode: 6 ('Alt')
[2021-12-28 18:55:16.211] [renderer1] [info] [KeybindingService]: \ Keyboard event cannot be dispatched in keydown phase.
[2021-12-28 18:55:16.245] [renderer1] [info] [KeybindingService]: / Received  keydown event - modifiers: [alt], code: AltLeft, keyCode: 18, key: Alt
[2021-12-28 18:55:16.246] [renderer1] [info] [KeybindingService]: | Converted keydown event - modifiers: [alt], code: AltLeft, keyCode: 6 ('Alt')
[2021-12-28 18:55:16.247] [renderer1] [info] [KeybindingService]: \ Keyboard event cannot be dispatched in keydown phase.
[2021-12-28 18:55:16.276] [renderer1] [info] [KeybindingService]: / Received  keydown event - modifiers: [alt], code: AltLeft, keyCode: 18, key: Alt
[2021-12-28 18:55:16.277] [renderer1] [info] [KeybindingService]: | Converted keydown event - modifiers: [alt], code: AltLeft, keyCode: 6 ('Alt')
[2021-12-28 18:55:16.277] [renderer1] [info] [KeybindingService]: \ Keyboard event cannot be dispatched in keydown phase.
[2021-12-28 18:55:16.305] [renderer1] [info] [KeybindingService]: / Received  keydown event - modifiers: [alt], code: AltLeft, keyCode: 18, key: Alt
[2021-12-28 18:55:16.306] [renderer1] [info] [KeybindingService]: | Converted keydown event - modifiers: [alt], code: AltLeft, keyCode: 6 ('Alt')
[2021-12-28 18:55:16.306] [renderer1] [info] [KeybindingService]: \ Keyboard event cannot be dispatched in keydown phase.
[2021-12-28 18:55:16.338] [renderer1] [info] [KeybindingService]: + Storing single modifier for possible chord alt.
[2021-12-28 18:55:16.641] [renderer1] [info] [KeybindingService]: + Clearing single modifier due to 300ms elapsed.

related to #101136
you can set terminal.integrated.altClickMovesCursor:false to fix this

In that case I wouldn't be able to move the cursor with alt-click; the problem isn't that the cursor moves when I alt-click, it's that it doesn't move to the location I clicked.

Unfortunately this feature in inherently unreliable and currently just does a best effort at moving the cursor. We can't improve this as far as we can tell.


add stealthwave#0001

You'll have to resubmit this with only the index.tsx change as I don't want any package changes, and very obviously don't want npm's package lock in here either as this repository uses yarn.


Use pip-compile for requirements?

I think it might be a good idea to use pip-compile from pip-tool's future branch to maintain the requirements files.
This would mean to have *.in files (where no pinning would be used in general), and then a make task to build the *.txt from there via pip-compile, where the current versions (for unpinned inputs) would be used for pinning.
While this is good for maintaining the files in the cookiecutter project by itself, it's also good practice for the generated projects.
Sadly pip-tools has a few issues currently (e.g. it does not handle VCS URLs), but there a PRs for this.
Another issue would be to not resolve the -r includes maybe (https://github.com/nvie/pip-tools/issues/174), and the template wrappers for {% if cookiecutter.use_whitenoise == 'y' -%} etc need to get addressed (which is relevant for cookiecutter-django, not the generated project).

My concern with some of the more awesome pip tools is their Windows support is sometimes not as solid as pip itself. There are a lot of Windows users for this project, so using the tool might exclude them.

@pydanny
Even when pip-compile was not working well on Windows, it could still be used to manage the Repo's own requirements?!

Ah... I see. We could use Linux/OSX with pip-compile to maintain the requirements versions, which then could go anywhere. Is that correct?

Yep.


Update empty state content

The Chore
Update copy for empty states across block explorer so that you're never left with nothing on the screen and nowhere to go / reason why.
Tasks

[x] Define empty state content for:

[x] - Governance proposals
[x] - Markets
[x] - Oracles
[x] - Transactions
[x] - Parties
[x] - Blocks
[x] - Assets

[x] Review with stakeholders (Edd)
[ ] Design template for empty state messages
[ ] Review with team
[ ] Implement

Additional details / background info

There will never be 0 instances of, validators, genesis parameters, or network parameters

Recapping a chat thread:
We’re thinking about empty states for various pages
Which of these could be legitimately empty, and which should always have some content? For example, I assume there will never be 0 blocks in the chain. I’ve done a quick sort based on my assumptions:
There could be 0 instances of:

Governance proposals
Markets
Oracles

It’s very unlikely there will be 0 instances of:

Transactions
Parties
Blocks
Assets

There should never be 0 instances of:

Validators
Genesis parameters
Network parameters

See attached the chosen direction: a generic skeleton placeholder under each page title and some empty state text. Each of the pages has been mapped out in the Figma file here. I've used Transactions as the template to demonstrate how it would behave on the XSM breakpoint.


SQLite syntax error near "returning" on Android

Working on IOS

Not working on Android

It might be related to this issue

Thanks! Now migrations-plugin don't use returning *. I think android using older version of native SQLite 🤔 Good to know

It's working =)
Thanks !


[PECO-840] Port staging ingestion behaviour to new UC Volumes

⚠ Note to reviewers: this will be easiest to review commit-by-commit as each change is small and logical. All these tests are copied from the original staging locations feature and only lightly augmented to support UC volumes.
Description
Last year we introduced staging locations, a feature which is being phased out with UC volumes instead. No change is needed to the connector except to update our e2e tests to use the new UC volumes syntax. Which is what this pull request implements. I originally wrote this change in July 2023, as the feature was first rolling out and we didn't have a server to test against. We now have that server and I have verified that all our tests pass.
Related Tickets & Documents
This is a reopen of #234 and #167

I synced with main to fix the merge conflict warning.


AppArmor: update rules to allow self-upgrade, again.

With these changes applied before the upgrade, I could successfully upgrade from
6.0.1 to 6.0.2. Let's hope it will be enough for other situations as well.
This is a follow-up to https://github.com/micahflee/torbrowser-launcher/issues/227.

Thanks @intrigeri


travis testing against 0.12, 2, 4

Setting up travis. @matthewloring PTAL.

The failure against Node 4.x will be fixed by #21.

LGTM once #21 is landed (just to confirm the fix)


Is there any update now?

@brainwatcher : Unfortunately, there are no updates planned at this time.


tasks:disable/enable cli command

See https://github.com/lonnieezell/codeigniter4-tasks/blob/develop/docs/vision.md
If you want to work on this, assign the card to yourself and ask any questions here.

Implemented an initial version of these in https://github.com/lonnieezell/codeigniter4-tasks/pull/19


Unable to initialize the probes

What happened:
Deployment in Openshift, httpProbe in pod-delete expirement.
Error:
time="2022-03-20T13:03:51Z" level=error msg="Unable to initialize the probes, err: unable to Get the chaosengine, err: v1alpha1.ChaosEngine.Spec: v1alpha1.ChaosEngineSpec.Experiments: []v1alpha1.ExperimentList: v1alpha1.ExperimentList.Spec: v1alpha1.ExperimentAttributes.Probe: []v1alpha1.ProbeAttributes: v1alpha1.ProbeAttributes.CmdProbeInputs: v1alpha1.CmdProbeInputs.Source: ReadString: expects \" or n, but found {, error found in #10 byte of ...|\"source\":{}},\"httpPr|..., bigger context ...|e\":[{\"cmdProbe/inputs\":{\"comparator\":{},\"source\":{}},\"httpProbe/inputs\":{\"insecureSkipVerify\":true,\"|..."
What you expected to happen:
Probe test success.
How to reproduce it (as minimally and precisely as possible):
Litmus version: 2.4.0/2.6.0/2.7.0 (tried all 3 version, no change)
Deployment on
Openshift 4.8.15 (Kubernetes version v1.21.1+a620f50)
File for deployment:
https://litmuschaos.github.io/litmus/2.6.0/litmus-2.6.0.yaml
Workflow:
kind: Workflow
apiVersion: argoproj.io/v1alpha1
metadata:
  name: custom-chaos-workflow-1647760231
  namespace: litmus
  creationTimestamp: null
  labels:
    cluster_id: d7087210-5aee-4220-a7be-c3914038da91
    subject: custom-chaos-workflow_litmus
    workflow_id: 287dfc50-ae1f-491f-8bed-72d10e09bd0e
    workflows.argoproj.io/controller-instanceid: d7087210-5aee-4220-a7be-c3914038da91
spec:
  templates:
    - name: custom-chaos
      inputs: {}
      outputs: {}
      metadata: {}
      steps:
        - - name: install-chaos-experiments
            template: install-chaos-experiments
            arguments: {}
        - - name: pod-delete
            template: pod-delete
            arguments: {}
        - - name: revert-chaos
            template: revert-chaos
            arguments: {}
    - name: install-chaos-experiments
      inputs:
        artifacts:
          - name: pod-delete
            path: /tmp/pod-delete.yaml
            raw:
              data: >
                apiVersion: litmuschaos.io/v1alpha1

                description:
                  message: |
                    Deletes a pod belonging to a deployment/statefulset/daemonset
                kind: ChaosExperiment

                metadata:
                  name: pod-delete
                  labels:
                    name: pod-delete
                    app.kubernetes.io/part-of: litmus
                    app.kubernetes.io/component: chaosexperiment
                    app.kubernetes.io/version: latest
                spec:
                  definition:
                    scope: Namespaced
                    permissions:
                      - apiGroups:
                          - ""
                        resources:
                          - pods
                        verbs:
                          - create
                          - delete
                          - get
                          - list
                          - patch
                          - update
                          - deletecollection
                      - apiGroups:
                          - ""
                        resources:
                          - events
                        verbs:
                          - create
                          - get
                          - list
                          - patch
                          - update
                      - apiGroups:
                          - ""
                        resources:
                          - configmaps
                        verbs:
                          - get
                          - list
                      - apiGroups:
                          - ""
                        resources:
                          - pods/log
                        verbs:
                          - get
                          - list
                          - watch
                      - apiGroups:
                          - ""
                        resources:
                          - pods/exec
                        verbs:
                          - get
                          - list
                          - create
                      - apiGroups:
                          - apps
                        resources:
                          - deployments
                          - statefulsets
                          - replicasets
                          - daemonsets
                        verbs:
                          - list
                          - get
                      - apiGroups:
                          - apps.openshift.io
                        resources:
                          - deploymentconfigs
                        verbs:
                          - list
                          - get
                      - apiGroups:
                          - ""
                        resources:
                          - replicationcontrollers
                        verbs:
                          - get
                          - list
                      - apiGroups:
                          - argoproj.io
                        resources:
                          - rollouts
                        verbs:
                          - list
                          - get
                      - apiGroups:
                          - batch
                        resources:
                          - jobs
                        verbs:
                          - create
                          - list
                          - get
                          - delete
                          - deletecollection
                      - apiGroups:
                          - litmuschaos.io
                        resources:
                          - chaosengines
                          - chaosexperiments
                          - chaosresults
                        verbs:
                          - create
                          - list
                          - get
                          - patch
                          - update
                          - delete
                    image: litmuschaos/go-runner:latest
                    imagePullPolicy: Always
                    args:
                      - -c
                      - ./experiments -name pod-delete
                    command:
                      - /bin/bash
                    env:
                      - name: TOTAL_CHAOS_DURATION
                        value: "15"
                      - name: RAMP_TIME
                        value: ""
                      - name: FORCE
                        value: "true"
                      - name: CHAOS_INTERVAL
                        value: "5"
                      - name: PODS_AFFECTED_PERC
                        value: ""
                      - name: LIB
                        value: litmus
                      - name: TARGET_PODS
                        value: ""
                      - name: SEQUENCE
                        value: parallel
                    labels:
                      name: pod-delete
                      app.kubernetes.io/part-of: litmus
                      app.kubernetes.io/component: experiment-job
                      app.kubernetes.io/version: latest
      outputs: {}
      metadata: {}
      container:
        name: ""
        image: litmuschaos/k8s:latest
        command:
          - sh
          - -c
        args:
          - kubectl apply -f /tmp/pod-delete.yaml -n
            {{workflow.parameters.adminModeNamespace}} |  sleep 30
        resources: {}
    - name: pod-delete
      inputs:
        artifacts:
          - name: pod-delete
            path: /tmp/chaosengine-pod-delete.yaml
            raw:
              data: >
                apiVersion: litmuschaos.io/v1alpha1

                kind: ChaosEngine

                metadata:
                  namespace: "{{workflow.parameters.adminModeNamespace}}"
                  generateName: pod-delete
                  labels:
                    instance_id: 2a373566-d3a0-447a-98b4-171a8d9a67a3
                    context: pod-delete_litmus
                    workflow_name: custom-chaos-workflow-1647760231
                spec:
                  appinfo:
                    appns: cloudia
                    applabel: app=event-exporter
                    appkind: deployment
                  engineState: active
                  chaosServiceAccount: litmus-admin
                  experiments:
                    - name: pod-delete
                      spec:
                        components:
                          env:
                            - name: TOTAL_CHAOS_DURATION
                              value: "30"
                            - name: CHAOS_INTERVAL
                              value: "10"
                            - name: FORCE
                              value: "false"
                            - name: PODS_AFFECTED_PERC
                              value: ""
                        probe:
                          - name: event-exporter
                            type: httpProbe
                            mode: SOT
                            runProperties:
                              probeTimeout: 15
                              retry: 5
                              interval: 5
                              initialDelaySeconds: 120
                              stopOnFailure: false
                            httpProbe/inputs:
                              url: https://test1.test.local/metrics
                              insecureSkipVerify: true
                              responseTimeout: 120
                              method:
                                get:
                                  criteria: ==
                                  responseCode: "200"
                  annotationCheck: "false"
      outputs: {}
      metadata:
        labels:
          weight: "10"
      container:
        name: ""
        image: litmuschaos/litmus-checker:latest
        args:
          - -file=/tmp/chaosengine-pod-delete.yaml
          - -saveName=/tmp/engine-name
        resources: {}
    - name: revert-chaos
      inputs: {}
      outputs: {}
      metadata: {}
      container:
        name: ""
        image: litmuschaos/k8s:latest
        command:
          - sh
          - -c
        args:
          - "kubectl delete chaosengine -l 'instance_id in
            (2a373566-d3a0-447a-98b4-171a8d9a67a3, )' -n
            {{workflow.parameters.adminModeNamespace}} "
        resources: {}
  entrypoint: custom-chaos
  arguments:
    parameters:
      - name: adminModeNamespace
        value: litmus
  serviceAccountName: argo-chaos
  podGC:
    strategy: OnWorkflowCompletion
  securityContext:
    runAsUser: 1000
    runAsNonRoot: true

Chaos engine:
apiVersion: litmuschaos.io/v1alpha1
kind: ChaosEngine
metadata:
  generateName: pod-delete
  resourceVersion: '376947944'
  name: pod-deletez5x6b
  uid: d3223370-a53d-4e25-8b55-8c743d650bad
  creationTimestamp: '2022-03-20T11:07:59Z'
  generation: 6
  managedFields:
    - apiVersion: litmuschaos.io/v1alpha1
      fieldsType: FieldsV1
      fieldsV1:
        'f:metadata':
          'f:generateName': {}
          'f:labels':
            .: {}
            'f:context': {}
            'f:instance_id': {}
            'f:workflow_name': {}
        'f:spec':
          .: {}
          'f:annotationCheck': {}
          'f:appinfo':
            .: {}
            'f:appkind': {}
            'f:applabel': {}
            'f:appns': {}
          'f:chaosServiceAccount': {}
      manager: checker
      operation: Update
      time: '2022-03-20T11:07:59Z'
    - apiVersion: litmuschaos.io/v1alpha1
      fieldsType: FieldsV1
      fieldsV1:
        'f:status':
          'f:experiments': {}
      manager: chaos-runner
      operation: Update
      time: '2022-03-20T11:08:05Z'
    - apiVersion: litmuschaos.io/v1alpha1
      fieldsType: FieldsV1
      fieldsV1:
        'f:metadata':
          'f:finalizers':
            .: {}
            'v:"chaosengine.litmuschaos.io/finalizer"': {}
        'f:spec':
          'f:components':
            .: {}
            'f:runner':
              .: {}
              'f:image': {}
              'f:resources': {}
          'f:engineState': {}
          'f:experiments': {}
        'f:status':
          .: {}
          'f:engineStatus': {}
      manager: chaos-operator
      operation: Update
      time: '2022-03-20T11:09:52Z'
  namespace: litmus
  finalizers:
    - chaosengine.litmuschaos.io/finalizer
  labels:
    context: pod-delete_litmus
    instance_id: 91ebc5f2-653e-4b9f-90ba-94f9769d41b6
    workflow_name: custom-workflow-1647774249
spec:
  annotationCheck: 'false'
  appinfo:
    appkind: deployment
    applabel: app=event-exporter
    appns: event-exporter
  chaosServiceAccount: litmus-admin
  components:
    runner:
      image: 'litmuschaos/chaos-runner:2.3.0'
      resources: {}
  engineState: stop
  experiments:
    - name: pod-delete
      spec:
        components:
          env:
            - name: TOTAL_CHAOS_DURATION
              value: '30'
            - name: CHAOS_INTERVAL
              value: '1'
            - name: FORCE
              value: 'false'
            - name: PODS_AFFECTED_PERC
          resources: {}
          statusCheckTimeouts: {}
        probe:
          - cmdProbe/inputs:
              comparator: {}
              source: {}
            httpProbe/inputs:
              insecureSkipVerify: true
              method:
                get:
                  criteria: ==
                  responseCode: '200'
                post: {}
              url: >-
                https://test1.test.local/metrics
            k8sProbe/inputs: {}
            mode: Edge
            name: check-route
            promProbe/inputs:
              comparator: {}
            runProperties:
              interval: 10
              probeTimeout: 60
              retry: 2
            type: httpProbe
status:
  engineStatus: completed
  experiments:
    - experimentPod: pod-delete-roqrf7-kgf6k
      lastUpdateTime: '2022-03-20T11:09:49Z'
      name: pod-delete
      runner: pod-deletez5x6b-runner
      status: Running
      verdict: Awaited

Hi, were you able to resolve this? Can you try with any of the newer LitmusChaos versions? It seems like the cause is incorrectly formatted Workflow manifest, but still you can confirm.

Getting the same issue on latest litmus   3.0.0-beta3 .
Any help appreciated
container:
name: ""
image: litmuschaos/litmus-checker:3.0.0-beta3
args:
- -file=/tmp/chaosengine-pod-delete-8fw.yaml
- -saveName=/tmp/engine-name
resources: {}

Hi!
Gettint the same issue on litmus 3.0.0-beta6 and  3.0.0-beta8.
After a lengthy investigation into the source code, I have found that starting from version 3.0.0-beta6 of the chaos-operator, the Runproperty Interval and ProbeTimeout types are changed to string (chaos-operator:3.0.0.-beta6). In the erlier versions both field types were still integers (chaos-operator:3.0.0.-beta5).
However, on the chaos-center side, even in the latest version, the types of these two fields are integers.
Therefore, when using the chaos-operator, you should use a version prior to 3.0.0-beta6, and ensure that when creating a chaos scenario in the chaos experiments the version of the "litmuschaos/go-runner" image matches the version of the chaos-operator.
So, in the example mentioned above, the solution would be not to use the following image in the ChaosExperiment: "image: litmuschaos/go-runner:latest", but instead use an image that matches the version of the chaos-operator.
In my case, I had to modify the image in the chaosExperiment from "litmuschaos/go-runner:latest" to "litmuschaos/go-runner:3.0.0-beta3".
This configuration works for me with the following versions:
chaos-center: 3.0.0-beta6
chaos-operator: 3.0.0-beta3
go-runner/litmus-go: 3.0.0-beta3
I hope these pieces of information will also help others.


After some hours running, the transactions screens become really slow

After some time running whith the bot, I always take a look how thing are running.
I noticed when I click the "transactions menu" and click over "Unconfirmed", incoming or outgoing, it does not respond as fast as it should. After some time thinking, there is an thrown error:

The client is running noonstop.
The harvested blocks interface also get slow. When you scroll down to see historical transactions, and sometime there is another error:

I can notice sometimes, also, the pop-up message from MOM ( the program that makes the NIs boot and start NCC on the system bar) informing "Nis is runing and completely synced and Ncc is
running", like if they just got restarted. This last one (pop up message) Im not so sure if its a bug.
Edit: Happend just after I click post the issu here, whith not many transactions on blocks:

Edit: On linux mint macnhine, the historical transaction is really fast. It shown everything OK whith no error.
The force be with you yong Skywalker!!!!
=)
Edit: I restarted it, after a coulpe hours ruuning like this, and the interface got really fast. Everything are shown as expected and working!

I don't see this any longer since the performance was increased a lot.
Close?


Enhancement: Warn on dimension discrepancy

Developers may find subtle glitches in their Web applications when users submit a single string field entry where the form POST receiving endpoint expects an array of strings entry. This can happen when the developer makes a mistake in the dimensionality of their OPTION (e.g. omitting the [] suffix for the name attribute when using multiple="multiple", or supplying the [] suffix when not using multiple="multiple").
Could select2 present a warning for this erroneous configuration in the JS console?

Could select2 present a warning for this erroneous configuration in the JS console?

Unfortunately the [] convention is limited to like 2 languages and isn't a standard, so there isn't much Select2 can do here.


[rest] Add create-offer endpoint for credentials

Should work with the oob create invitation and oob create legacy invitation endpoints
The current API doesn't provide a create-offer endpoint. The create-offer allows to send a credential without first creating a connection. The flow for creating a credential offer is as follows:

Create credential offer by calling /credentials/create-offer. The API for this should exactly match the send-offer API endpoint, EXCEPT for the connectionId, this can be left out. This method should intenrally call create-offer and return the message + record.
Call /oob/create-invitation and provide the returned message in the messages array.
2.b (alternative) Call /oob/create-legacy-connectionless-invitation and provide  the recordId + message + domain

This invitation / invitation url can then be used by agent to receive a credential without first creating a connection.
Endpoint:
POST /credentials/create-offer

Input: input from send-offer without connectionId
Output:
{
  "message": <json message>,
  "record": <json of record>
}

You can get the json of the message / record by calling toJSON() on them.
Checlist:

[ ] Create create-offer endpoint
[ ] Add tests for the create-offer endpoint in credential.test.ts
[ ] Also add a test by first calling create-offer and then oob/create-invitation
[ ] Also add a test by first calling create-offer and then oob/create-legacy-connectionless-invitation
[ ] Make sure the endpoint shows up with the correct input/output documentation in the swagger ui

For the 3rd item in the checklist, would that be a test for the createOffer and createInvitation endpoints, or the methods (functions)?

The endpoints. The methods have been tested as part of AFJ, so this test is mostly to assure the encoding between json and data classes works correctly when calling these endpoints

Got it

Also if use use the createInvitation method for the create-offer endpoint, there would be no need for the create-legacy-connectionless-invitation test, correct?

Also if I use the createInvitation method for the create-offer endpoint, there would be no need for the create-legacy-connectionless-invitation test, correct?

See my comment on the PR. We don't want to call create invitation from the create offer endpoint. This is two separate steps
For the user


hide out of stock items from homepage

items which inventory gets 0 should automatically get hidden from the homepage

i recommend to make this optional, some stores will work with backorders

i recommend to make this optional, some stores will work with backorders

@ghermans
Agree! there should be a configuration to allow/disallow out of stock items on the homepage.

@ghermans
Agree! there should be a configuration to allow/disallow out of stock items on the homepage.

Hi @ghermans  @vaishaliwebkul
I think, when backorders will be enable , it will show all product without quantity restrictions otherwise not .
What do you suggest ?

Hi @ghermans  @vaishaliwebkul
I think, when backorders will be enable , it will show all product without quantity restrictions otherwise not .
What do you suggest ?

@rahulshukla-webkul
implement this for velocity theme also.

@rahulshukla-webkul
implement this for velocity theme also.


Secretless homepage talks about rotation

secretless.io is updated to talk about rotation being one of the key benefits of the project.

Closing, since we have decided not to make this update at this time (not a priority of PM/PMM)


Don't Merge! PR real time test for webhook case

Docs Build status updates of commit 4493156:
:clock10: Pending: waiting for processors (22 builds ahead of you)
:warning: Docs Build is busy, currently there are 22 builds ahead of this one, for more information you can view the Build queue graph on the Docs Portal.

Docs Build status updates of commit 4493156:
:clock10: Full build: the average full build time is 6 min(s) 20 sec(s), this is based on the last 30 build(s) for this repository.

Docs Build status updates of commit 4493156:
:warning: Validation status: warnings

File
Status
Preview URL
Details

docs-ref-conceptual/testing.md
:warning:Warning
View (azure-cli-latest) View (azure-cli-2017-03-09-profile) View (azure-cli-2018-03-01-hybrid)
Details

docs-ref-conceptual/testing.md

[Warning] Missing attribute: either ms.prod or ms.service is required. Use ms.prod for on-premise products, or ms.service for cloud services.
[Warning] Missing attribute: title.
[Warning] Missing attribute: either ms.prod or ms.service is required. Use ms.prod for on-premise products, or ms.service for cloud services.
[Warning] Missing attribute: title.
[Warning] Missing attribute: either ms.prod or ms.service is required. Use ms.prod for on-premise products, or ms.service for cloud services.
[Warning] Missing attribute: title.

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Allow to enable raw_affects_selection

As it allows to significantly reduce apm. However, with this option human can't control units while bot playing. This could be not a huge issue, but seems that we should allow to disable the option.

I coded it yesterday, but forgot to push so I can't submit a pull request atm. And since it can mess with the debugging process by selecting different units, I chose to set it to false in debug and true otherwise.

Fixed in #38


toBeInTheDocument and toContainElement throws error if element is null

jest-dom version: 1.10.0
node version: 10.5.0
npm (or yarn) version: 6.2.0

Relevant code or config:
// downshift/src/__tests__/portal-support.js
const {getByTestId, queryByTestId} = render(
  <MyPortalAutocomplete />,
)
expect(queryByTestId('menu')).not.toBeInTheDocument()
getByTestId('button').click()
expect(getByTestId('menu')).toBeInTheDocument()

What you did:
Tried replacing toBeInDOM with any of the new suggested ways (toBeInTheDocument/ toContainElement )

What happened:
Both throws an error then the element is null

Reproduction:
↑ See relevant code or the Downshift repo https://github.com/paypal/downshift/blob/master/src/tests/portal-support.js#L57-L60

Problem description:
As far as I can tell there is no way to replace the current usage of toBeInTheDOM with the other functions. But I might be missing something?

Suggested solution:
I think they should accept falsy (or at least null) values and just return false if that's the case

See https://github.com/gnapse/jest-dom/issues/34
The recommended approach for testing the existence of elements retrieved via queryBy* is to use toBeNull or toBeTruthy (or even better, toBeInstanceOf(HTMLElement).

Ah I see, I did read through that thread but don't know how i missed that! 😅  It might be a good idea to add that to the readme as well imo
Thanks!

@alexandernanberg you're right. I just updated the README section about this deprecated matcher to be more clear about why this was done and what the alternatives are. Thanks for the tip.

:tada: This issue has been resolved in version 1.11.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


bug: didn't work at all for javascriptreact and typescriptreact filetype

Did you check docs and existing issues?

[X] I have read all the ts-comments.nvim docs
[X] I have searched the existing issues of ts-comments.nvim
[X] I have searched the existing issues of plugins related to this issue

Neovim version (nvim -v)
v0.10.0
Operating system/version
Mac OS 14.4.1 (23E224)
Describe the bug
I've verified with Lazy and the plugin is installed properly. However, when I use it inside my tsx and jsx files, they don't work at all. All the element comments just added // %s. I used the command :set filetype? to and and they returns javascriptreact and typescriptreact as the filetype instead, so I suspect that this is the issue.
Steps To Reproduce

Install folke/ts-comments.nvim
Open a tsx file and check :set filetype? if it is typescriptreact
Go to a React element and toggle comment

Expected Behavior
Go to a React element and toggle comment should respect {/* %s */} format
Repro
-- DO NOT change the paths and don't remove the colorscheme
local root = vim.fn.fnamemodify("./.repro", ":p")

-- set stdpaths to use .repro
for _, name in ipairs({ "config", "data", "state", "cache" }) do
  vim.env[("XDG_%s_HOME"):format(name:upper())] = root .. "/" .. name
end

-- bootstrap lazy
local lazypath = root .. "/plugins/lazy.nvim"
if not vim.loop.fs_stat(lazypath) then
  vim.fn.system({ "git", "clone", "--filter=blob:none", "https://github.com/folke/lazy.nvim.git", lazypath, })
end
vim.opt.runtimepath:prepend(lazypath)

-- install plugins
local plugins = {
  "folke/tokyonight.nvim",
  { "folke/ts-comments.nvim", opts = {
lang = {
         tsx = {
          "// %s",                   -- default commentstring when no treesitter node matches
          "/* %s */",
          call_expression = "// %s", -- specific commentstring for call_expression
          jsx_attribute = "// %s",
          jsx_element = "{/* %s */}",
          jsx_fragment = "{/* %s */}",
          spread_element = "// %s",
          statement_block = "// %s",
        },
        typescriptreact = {
          -- "// %s",                   -- default commentstring when no treesitter node matches
          -- "/* %s /",
          call_expression = "// %s", -- specific commentstring for call_expression
          jsx_attribute = "// %s",
          jsx_element = "{/* %s */}",
          jsx_fragment = "{/* %s */}",
          spread_element = "// %s",
          statement_block = "// %s",
        },

}
} },
    {
    -- Highlight, edit, and navigate code
    'nvim-treesitter/nvim-treesitter',
    dependencies = {
      'nvim-treesitter/nvim-treesitter-textobjects',
      {
        -- Rainbow brackets
        "HiPhish/rainbow-delimiters.nvim",
        config = function()
          vim.api.nvim_create_user_command("RainbowDelimitersToggle", function()
            require("rainbow-delimiters").toggle(0)
          end, { desc = "Toggle Rainbow Delimiters" })

          vim.g.rainbow_delimiters = {
            -- log = {
            --   level = vim.log.levels.TRACE,
            -- },
            blacklist = { "html", "lua", "json" },
          }
        end,
      },
    },
    build = ':TSUpdate',
    config = function()
      -- Defer Treesitter setup after first render to improve startup time of 'nvim {filename}'
      vim.defer_fn(function()
        require('nvim-treesitter.configs').setup {
          -- Autoinstall languages that are not installed. Defaults to false (but you can change for yourself!)
          auto_install = true,
          -- Install languages synchronously (only applied to `ensure_installed`)
          sync_install = true,
          -- List of parsers to ignore installing
          ignore_install = {},
          -- You can specify additional Treesitter modules here: -- For example: -- playground = {--enable = true,-- },
          modules = {},

          ensure_installed = {
            'javascript',
            'typescript',
            'tsx',
            'liquid',
          },
        }
      end, 0)
    end
  },
}
require("lazy").setup(plugins, {
  root = root .. "/plugins",
})

vim.cmd.colorscheme("tokyonight")
-- add anything else here

This issue may be related: https://github.com/neovim/neovim/issues/24531

Can't reproduce this. Your repro is also far from minimal and setup ts-comments twice

@folke I apologize for the minimal code, I overlooked it and the existing ts-comment.
I have recorded my issue here. You can see the file type in the bottom right lualine.
https://github.com/folke/ts-comments.nvim/assets/14198542/27df4a37-db5a-402e-a845-e38c118ad3b7

$ nvim -u repro.lua foo.tsx

Steps:

go to line 5
gcc
commented line is correct

repro.lua
-- DO NOT change the paths and don't remove the colorscheme
local root = vim.fn.fnamemodify("./.repro", ":p")

-- set stdpaths to use .repro
for _, name in ipairs({ "config", "data", "state", "cache" }) do
  vim.env[("XDG_%s_HOME"):format(name:upper())] = root .. "/" .. name
end

-- bootstrap lazy
local lazypath = root .. "/plugins/lazy.nvim"
if not vim.loop.fs_stat(lazypath) then
  vim.fn.system({ "git", "clone", "--filter=blob:none", "https://github.com/folke/lazy.nvim.git", lazypath })
end
vim.opt.runtimepath:prepend(lazypath)

-- install plugins
local plugins = {
  "folke/tokyonight.nvim",
  {
    "folke/ts-comments.nvim",
    opts = {},
  },
  {
    -- Highlight, edit, and navigate code
    "nvim-treesitter/nvim-treesitter",
    build = ":TSUpdate",
    config = function()
      require("nvim-treesitter.configs").setup({
        ensure_installed = {
          "javascript",
          "typescript",
          "tsx",
        },
      })
    end,
  },
}
require("lazy").setup(plugins, {
  root = root .. "/plugins",
})

vim.cmd.colorscheme("tokyonight")
-- add anything else here

foo.tsx
import type { Component, ParentProps } from "solid-js";

export const Content: Component<ParentProps> = (props) => {
  return (

        {props.children}

  );
};

Since the repro works just fine, there's something else wrong with your installation.
Are you using either stable or a recent nightly?

Thanks @folke! I use the stable version from homebrew
NVIM v0.10.0
Build type: Release
LuaJIT 2.1.1716656478
Run "nvim -V1 -v" for more info

I ran the repro as you showed and it worked correctly on my machine too, so I bet tha my installation is the problem. The repro filetype is also typescript react. Hmm, weird! Anything on top of your mind that you can think of?

 I had been using comment.nvim prior to 0.10.0 for commenting. Then I upgraded to the latest version and using ts-comment while forgetting to delete comment.nvim. Now I deleted and it works perfectly. Thank you for your help and the awesome plugin @folke.


[WIP] Move "Motivation" to "Overview" section

Move the Motivation section ("Why Go?") from the "Motivation & Demo"
section into the "History and Overview" section. It fits better there
thematically, and also provides a good point to switch presenters to
present the demo.
Closes #72
Deployed at http://pr73-dot-gotraining-testing.appspot.com/

It's still WIP. I want to add back the empty "demo" title slide, but lunch beckoned.


is CodeSandbox down?

Hello there. I was looking for example for my project but the sandbox shows the following
Not Found
We could not find the sandbox you're looking for.

It's not down, just this example is no longer valid.

Seems like all the examples are down


implement batch verification

Description

implement batch verification for unique keys and unique messages.

The API resembles the rust zebra API. An alternative approach would be to have the VerifyBatch function accept arrays of the needed information. If this is preferred I can make the needed changes

Closes #5

Codecov Report

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

@@           Coverage Diff           @@
##             main       #7   +/-   ##
=======================================
  Coverage        ?   71.42%
=======================================
  Files           ?        2
  Lines           ?       77
  Branches        ?        0
=======================================
  Hits            ?       55
  Misses          ?       11
  Partials        ?       11

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 1057171...bb2ba02. Read the comment docs.

Thanks for implementing this! It looks really good.  I left a few inline review comments, but they are mostly about the API naming and documentation, the core functionality looks great.

Thanks for implementing this! It looks really good.  I left a few inline review comments, but they are mostly about the API naming and documentation, the core functionality looks great.


Bump browserify-sign to address CVE-2023-46234

Description
Bump browserify-sign to address CVE-2023-46234
Issues Resolved
[List any issues this PR will resolve]
Check List

[ ] New functionality includes testing.

[ ] All tests pass, including unit test, integration test and doctest

[ ] New functionality has been documented.

[ ] New functionality has javadoc added
[ ] New functionality has user manual doc added

[ ] 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.

backported here: https://github.com/opensearch-project/dashboards-reporting/pull/242
Removing Backport failed label.


changes the chief engineer's belt to remove the lv wires (they take up a lot of space and are easy to get anyways) in exchange for some more useful tools

About the PR

changed the ce belt to have some different added tools instead of the stack of lvs.
Why / Balance
 the lv wires were a huge usage of space that isn't great, if you want the lv cables just go to a youtool. the holofan isnt given to ce on all stations and i believe it should be, the rest are just for convenience (t-ray & gas analyzer), so you don't have to go to the youtool every time.
Technical details

removes lv, replaces with aforementioned tools.
Media

[x ] I have added screenshots/videos to this PR showcasing its changes ingame, or this PR does not require an ingame showcase

Breaking changes

Changelog

 the items inside the chief engineers toolbelt have been tweaked.

Changelog
the items inside the chief engineers toolbelt have been tweaked.

I love it, but name of the PR is way too long, and I believe, that the changelog line is added automatically to the game, so you've kinda screwed it's required shape a bit.

My bad, first pr is I kinda messed up the title, I’ll edit it shortly


Aligned .env.example to README.md

A few changes and example documentation in the README have not been ported into the .env.example file. This PR resolves this

@mintopia for review plx


Make ownership boxes all the same size

Signed-off-by: Andre Wanlin<EMAIL_ADDRESS>Hey, I just made a Pull Request!
This tiny PR makes all the ownership boxes the same size, picture show it best:
Before:

After:

:heavy_check_mark: Checklist

[x] A changeset describing the change and affected packages. (more info)
[ ] Added or updated documentation
[ ] Tests for new functionality and regression tests for bug fixes
[x] Screenshots attached (for UI changes)
[x] All your commits have a Signed-off-by line in the message. (more info)

Thanks @djamaile and @freben! 🚀


include glsl in ray tracing shader error

Hello @maierfelix !
my code is:
rchit glsl:
#version 460
#extension GL_NV_ray_tracing : require
#extension GL_GOOGLE_include_directive : enable
#pragma shader_stage(closest)

#include "wavefront.glsl"

...

wavefront.glsl:
struct sceneDesc
{
  int  objId;
  int  txtOffset;
  mat4 transfo;
  mat4 transfoIT;
};

when run the code, it error:
error: '#include' : #error unexpected include directive for header name: wavefront.glsl

How to include glsl???
Thanks very much!!!

The included glsl compiler doesn't handle includes, it's up to the application. You have to recursively lookup the content of the included file and inline it. This is how I do it in my projects - see here.
Alternatively you can use the nvk-essentials package which contains a GLSL compiler and support for includes.

Thanks for your reply!!!
Yes, I can use "include" by import your "loadShaderFile"(created from your project).
But it has a little bug:
inliner.mjs
import fs from "fs";
//should add this line!
import path from "path";

...

So the complete code to support include is:
index.mjs
//should move inliner.mjs to my project

import { loadShaderFile } from "./inliner.mjs";
...
  // rasterization shaders
  let vertexShaderModule = device.createShaderModule({
    code: loadShaderFile(`${baseShaderPath}/screen.vert`)
  });
  let fragmentShaderModule = device.createShaderModule({
    code: loadShaderFile(`${baseShaderPath}/screen.frag`)
  });

  // ray-tracing shaders
  let rayGenShaderModule = device.createShaderModule({
    code: loadShaderFile(`${baseShaderPath}/ray-generation.rgen`)
  });
  let rayCHitShaderModule = device.createShaderModule({
    code: loadShaderFile(`${baseShaderPath}/ray-closest-hit.rchit`)
  });
  let rayMissShaderModule = device.createShaderModule({
    code: loadShaderFile(`${baseShaderPath}/ray-miss.rmiss`)
  });

ray-closest-hit.rchit
#version 460
...
#extension GL_GOOGLE_include_directive : enable
#pragma shader_stage(closest)

#include "wavefront.glsl"

wavefront.glsl
//define the export code like:
struct Data1
{
  float objId;
};

int getData2(){
  return 1;
}


Support for VirtualDSM

Description
Hello,
i wanted to install this promising package onto my VirtualDSM (BareMetal Host is a DS918+).
my use case: i use my VirtualDSM to connect to VPN as i don't want my physical NAS connected on any VPN.
Installation fail on the VirtualDSM with "this package is not supported on the platform of VirtualDSM" with package
WireGuard-apollolake-1.0.20200729.spk
or
WireGuard-x86-1.0.20200729.spk (it may be normal, but i saw x86 and told myself "why not ?")

EDIT: I'm not sure, but it seems that the VirtualDSM arch is kvmx64.
i am not a dev at all, but i'm willing to help if you need a labrat/tester  👍
Thanks a lot for your time ! :)
NB: it's not urgent at all, i'm just really intersted in this package !
Synology NAS model
VirtualDSM (Host is a DS918+)

As you have noticed, VirtualDSM architecture is kvmx64. pkgscripts-ng supports this architecture, and according to the platforms file kvmx64 uses kernel linux-3.10.x, so it is supported by Wireguard.
In this case you just need to compile the package according to the instructions in the Compiling section.

I built it for VirtualDSM version 7.0-41222, using sudo docker run --rm --privileged --env PACKAGE_ARCH=kvmx64 --env DSM_VER=7.0 -v /volume1/homes/myusername:/result_spk synobuild and the other steps fund on https://github.com/runfalk/synology-wireguard/pull/71
I can install it, but it gives me an error: 'Failed to start "WireGuard". Please try again later or contact the package developer.' with the option for a Repair. Trying that gives a failed to run.
I don't know how to parse the resulting file (WireGuard-kvmx64-1.0.20210219.spk) to check the parameters, but I think they're fine.
Here's a link: https://file.io/2184vzNFjLa2

@jelbo I think you have not read the updated installation instruction from #71. Follow this instruction, pay attention to step 4 (this step is probably missing in your case).

@Matige thanks, I indeed missed that. I now have a WireGuard has been successfully started Thanks a lot!


Game Suggestion

Could you please add these games?
AI: The Somnium Files
AI: THE SOMNIUM FILES - nirvanA Initiative

I have added the game(s) you requested in the most recent release: https://github.com/hobby-grade/Nintendo-Switch-Discord-Status/releases/tag/v1.1.4
Thank you for checking out the project, reach out if you have any more suggestions!


EIP-1271 fuzzing

Motivation

Solution

Codecov Report
Patch and project coverage have no change.

Comparison is base (86a319a) 100.00% compared to head (681c36b) 100.00%.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
Additional details and impacted files
@@             Coverage Diff             @@
##               1.5     #1127     +/-   ##
===========================================
  Coverage   100.00%   100.00%
===========================================
  Files           46        21     -25
  Lines         2652      1230   -1422
  Branches       396       220    -176
===========================================
- Hits          2652      1230   -1422

Flag
Coverage Δ

foundry
?

production
?

reference
100.00% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.
see 35 files with indirect coverage changes
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

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


Make DA monitor handling more generic (part 2)

Description
These changes improve the handling of DA monitor data.  The dimensions and coordinates in use (as specified in the DA monitor control file) are now dynamic lists instead of string literals.  Parsing these lists is now done by dictionaries instead of if|elif|else syntax.
Tests have been successfully completed using RadMon time files (2 dimensions), RadMon angle files (3 dimensions), and OznMon time files (1 or 2 dimensions).
Please don't close issue #85 yet though.  I think there still may be some work to do to handle batch plots.  I'd like to get this reviewed and merged before exploring that (potential) complication.
Dependencies
None
Impact
None
Ref #85

Hmmm.  Not sure why the Notebook tests decided to fail:
ImportError: cannot import name 'ImportedStyleSheet' from 'bokeh.models' (/home/runner/.local/lib/python3.10/site-packages/bokeh/models/__init__.py)

@EdwardSafford-NOAA you're not alone here, this is also in #102 , so it seems like a GitHub actions issue.

Note, don't worry about the Eva Notebook Tests failure, that will be fixed in #102


[bug] <rh-tab> long text content should be constrained to 200px

When we converted from a shadow button to a div internally we lost inherent styles that came with button.  This wasn't caught  outside of use case for long text content.
adding the following to #button in tab.css fixes the problem
box-sizing: border-box;  /* [slot] { box-sizing: border-box; } instead maybe? */
text-align: center;

@zeroedin was this fixed by #1904 ?

Closed by #1904


”Valea Marcului”, ”Varodia”, ”Vlădica” are listed in the drop-down menu

Description:
When user writes ”Valea Marcului”, ”Varodia”, ”Vlădica” the locations appear in the drop-down menu next to the comune and the county which is a part according to the law.
Precondition:
The website is up an running.

Step 1
Write in the search bar "Valea Marcului"

Expected results
The location appears in the drop-down menu as "Sat Valea Marcului, MEHEDINȚI (Dumbrava)".

Step 2
Press "x" button.

Expected results
The location was deleted from the search bar.

Step 3
Write in the search bar "Varodia"

Expected results
The location appears in the drop-down menu as "Sat Varodia, MEHEDINȚI (Dumbrava)".

Step 4
Press "x" button.

Expected results
The location was deleted from the search bar.

Step 5
Write in the search bar "Vlădica"

Expected results
The location appears in the drop-down menu as "Sat Vlădica, MEHEDINȚI (Dumbrava)".


Add dependency parsing grammar for gateway allowlist

Summary
Part of #369
This PR adds the dependency specification grammar from PEP
508 (https://peps.python.org/pep-0508/) to use when validating
dependencies via the allowlist.
As a temporary measure, it also simplifies the check to only consider
the dependency and not a specific version. As such, it has dropped the
test for related to dependency version.
Future work should be done to convert the allowlist file from JSON to
the standard requirements.txt format, which would allow for easier
version checking.
Details and comments

The gateway pod seems to be restarting in the k8s test, not sure why yet

ok, bumping the resource limits on the gateway fixed the issue

Good to know because we had the same problem with the scheduler Wed 😂

Add it on-hold tag until we can work together on this 😄


Issue with color in rename mode

Hi!
Could you please fix colors in rename mode?
In picture below, i was pressed rename function name and cannot see what text is selected or not.
(spoiler: it is selected)

Hi!
Here I cannot see what I've just choose

Hi! Here I cannot see what I've just choose

Are you referring to the backdrop of the rename window? The functionality of where that window displays has nothing to do with the theme

I thought maybe the whole background could be more lighter, like #4A4D6A
It would be like this

Also, I see this problem with files which were influenced by gitignore

You can override any highlights or colors you want with on_colors or on_highlights functions in the confg for theme. I do agree that specific instance does look better you can open a PR and I can check it out

Could you give me, please, a hint where those settings is?
I never changed themes before

You'd have to check what highlight group that code rename action window iis in nvim, then you can find it in
https://github.com/eldritch-theme/eldritch.nvim/blob/master/lua/eldritch/groups   if it exists , if not you'll have to add an override line there for the highlight group name

Thanks a lot!
I will try to figure it out and I'll try to make a PR when I get some free time

@whitewolf185

This is what I see btw


chore(deps): remove babel-jest

babel-jest is jest's dependency. jest takes care to install and makes sure to pick correct version. It is not possible to know in advance if user has Jest v26 or v27.
Might be there is no harm to declare babel-jest as a dependency, but there is no need or gain too. This library does not import from babel-jest.
PS At first I though that this PR is missing yarn.lock, but it did not change. jest is still installed and because of that babel-jest is left in place. This simply proofs what I try to explain above.

Hi @mrazauskas
We need this dependency in https://github.com/nuxt/test-utils/blob/main/jest-preset.js#L6

@ricardogobbosouza Yes, it is included in the preset, but the preset will be loaded by a copy of Jest installed by the user. If the user picks Jest v26, babel-jest v26 will be needed. Jest will be always better in managing its dependencies.
Don’t know how to explain it better.

We are testing other transpilers as babel is taking too long.
#145


[pkg] update package-lock

I received a "Security alert" so I deleted my node modules and re-ran npm install.

Coverage remained the same at 88.528% when pulling<PHONE_NUMBER>a3eb61f14764ac5c64b471cd54b324 on security into 194e64daff528b1661ba3eb4ac723fa01ae7674b on develop.


[WIP] Spike: retrain node2vec on additional user data

Investigate usability for identifying related Brexit content

What pages do d7bdaee2-8ea5-460e-b00d-6e9382eb6b61|d6c2de5d-ef90-45d1-82d4-5f2438369eea|58adb819-5a65-4897-a790-5b7925c567e7|06e2928c-57b1-4b8d-a06e-3dde9ce63a6f correspond to?

bq_quick_pagehit_journey_brexit.ipynb gets only those user journeys that include brexit pages,
saves them as pageseq_user_journey_brexit_mar_02_mar_30.csv.gz, and dropping one-offs to save as pageseq_user_journey_brexit_mar_02_mar_30_doo.csv.gz. Number of pageviews for each page saved down in pageviews_brexit_mar_02_mar_30.csv.gz
check_n2v_for_existing_brexit_content.ipynb uses merged_edges_struct_funct.csv.gz to get lookup dictionaries for node IDs to content IDs and URLs, and a lookup dictionary of URLS to node IDs. It then loads up a previous node2vec model n2v.model and using the loookup dictionaries, generates the top 10 recs for each of the top 250 pages from Brexit-related documents - Brexit docs.tsv which I assume is the output found in the "Brexit related links from original n2v model (557/1381 pages predicted for)" doc.

merge_orig_dataset_with_brexit.ipynb gets the BQ pagesequence data generated by bq_quick_pagehit_journey_brexit.ipynb, neatens it up and saves it as pageseq_user_journey_brexit_feb19_mar_30.csv.gz. It then reads from a Brexit edges file feb19_mar30_nos_edges.csv.gz, drops all the weight 1 edges, and combines this with the existing node2vec edges file  from merged_edges_struct_funct.csv.gz (adding new URLs as new nodes in the url_nid dictionary, to get merged_edges_struct_funct_w_brexit.csv.gz. Also saves  the Brexit edges that aren't in the existing edge file as funct_only_brexit_1902_3003.csv.gz also
Where did you create feb19_mar30_nos_edges.csv.gz?/

Did you manage to get retrain_n2v_model_with_brexit.ipynb to work? Your trello card  suggested not

@suganya-s  https://github.com/alphagov/govuk-network-data/blob/collapse-search-nodes/src/data/make_network_data.py

I did, finished a couple of hours ago, will push and update trello

All looked good and made sense, let me know if you push new changes and want me to review :)


Remove wtfismyip.com due to its shutdown

https://twitter.com/wtfismyip/status/778232861472067585

Thanks!


Feature/storage adlsmerge

ADLSgen2 PR has been reviewed before but blocked by service readyness, now bring it back.

Will send another PR to add span tracking for new added APIs.

type DirectoryProperties = { [key: string]: string };

should DirectoryProperties be exported too since it is used in a public function?

Refers to: sdk/storage/storage-blob/src/DirectoryClient.ts:30 in 4cf0b2d. [](commit_id = 4cf0b2d8afc7ac4248aa3f31922d8f3d34e46610, deletion_comment = False)

marker?: string,

I think we want to add async iterator for operations that retrieve data but not operations that perform some actions.  /cc @bterlson.  For example, we didn't add async iterator for closing handles.

Refers to: sdk/storage/storage-blob/src/DirectoryClient.ts:589 in 4cf0b2d. [](commit_id = 4cf0b2d8afc7ac4248aa3f31922d8f3d34e46610, deletion_comment = False)

import { AbortSignalLike } from "@azure/core-http";

license header

Refers to: sdk/storage/storage-blob/src/ContextAborter.ts:1 in 4cf0b2d. [](commit_id = 4cf0b2d8afc7ac4248aa3f31922d8f3d34e46610, deletion_comment = False)

import { RestError } from "@azure/core-http";

nit: why removing blank line after header?

Refers to: sdk/storage/storage-blob/src/index.browser.ts:3 in 4cf0b2d. [](commit_id = 4cf0b2d8afc7ac4248aa3f31922d8f3d34e46610, deletion_comment = False)

      if (host.endsWith(replacement[0])) {

would casing matter? not sure whether users would pass the host name in upper case but just asking.

Refers to: sdk/storage/storage-blob/src/policies/DfsPolicy.ts:61 in 4cf0b2d. [](commit_id = 4cf0b2d8afc7ac4248aa3f31922d8f3d34e46610, deletion_comment = False)

@XiaoningLiu Is this PR still relevant?
@jeremymeng Do we need the feature/storage branch anymore?


Remove Host API from module SDK codegen.

🔥 Update Instructions for Breaking Changes
Modules that use the Host API to read source files
(using go syntax below, but same idea applies to all SDKs)
Previously, module containers set their working directory to the directory containing the module's source code. You could then read files from that directory with calls like dag.Host().File("./some/file.txt").
Now, module containers are set to an initially empty scratch directory, so those calls will not work anymore.
To use files/directories from the module source code, you can instead:

Directories - dag.CurrentModule().Source().Directory("some/subdir")
Files - dag.CurrentModule().Source().File("some/file.txt")

Additionally, it used to technically be possible to use files/directories from anywhere in the root dir loaded for a module in the case where "root" was configured in dagger.json. This is no longer possible; instead anything you need to use from outside the module's source code directory should be accepted as an argument to a function or the module constructor.
One final use case to mention: if you need to create new files/directories and then load them into the dagger API during module execution, this is still possible.

Directories - dag.CurrentModule().Workdir("./some/dir")
Files - dag.CurrentModule().WorkdirFile("./some/file.txt")

The new dag.CurrentModule() API replaces the need for the Host API and gives more controlled functionality that is specific to modules.
Fixes https://github.com/dagger/dagger/issues/6312
More details on the new API in this PR description (specifically CurrentModule API).
TODO:

[x] Update release notes with details on breaking change

If we're removing the host api entirely, it's now not possible to tunnel/reverse-tunnel a service from the module container?
I quite liked this feature, and I'm not sure if we should remove it - though maybe it does genuinely belong somewhere else (e.g. under Local as in https://github.com/dagger/dagger/pull/6408).

(rebased to fix merge conflicts against main)

Removed the changelog entry, following the same logic as in #6546


Setting DISABLE_ASM to ON breaks Visual Studio 2008 and lower builds

When building using Visual Studio 2008 or lower, ASM is required. See cpu.cpp:59.

I'm not the one who disabled it so I'll have to ask why. The problem is still there even with my fix.

@MarcelRaad, @abdes,
Can one of you check on this problem and advise?
I'd like to clear this issue if possible (before tagging the CRYPTOPP_8_0_0 release).

As VS 2008 doesn't support inline assembly in 64-bit mode and obviously doesn't provide the required intrinsic, I don't think there's anything that can be done about that. Except maybe rejecting DISABLE_ASM for 64-bit with a nicer error message. To be clear, the problem doesn't exist when compiling in 32-bit mode as inline assembly is used then.

As VS 2008 doesn't support inline assembly in 64-bit mode and obviously doesn't provide the required intrinsic, I don't think there's anything that can be done about that.

Right, but we don't have the issue on VS2010 or above. Or I don't believe we do. Here's what I see when using MSBuild (I don't have a CMake machine for this test):
C:\Users\Jeff\cryptopp>msbuild /t:Build /p:Configuration=Debug;Platform=x64 cryptlib.vcxproj
Microsoft (R) Build Engine version 4.7.3062.0
[Microsoft .NET Framework, version 4.0.30319.42000]
Copyright (C) Microsoft Corporation. All rights reserved.

Build started 12/28/2018 10:03:16 AM.
Project "C:\Users\Jeff\Desktop\cryptopp\cryptlib.vcxproj" on node 1 (Build targ
et(s)).
PrepareForBuild:
  Creating directory "x64\cryptlib\Debug\".
  Creating directory "x64\Output\Debug\".
...

  cryptlib.vcxproj -> C:\Users\Jeff\cryptopp\x64\Output\Debug\cryptlib.
  lib
FinalizeBuildStatus:
  Deleting file "x64\cryptlib\Debug\cryptlib.unsuccessfulbuild".
  Touching "x64\cryptlib\Debug\cryptlib.lastbuildstate".
Done Building Project "C:\Users\Jeff\cryptopp\cryptlib.vcxproj" (Build target(s)).

Build succeeded.
    0 Warning(s)
    0 Error(s)

Time Elapsed 00:00:51.07

I don't see any cross-pollination of inline ASM.

I'm not sure I understand the problem, but with DISABLE_ASM, neither x64dll.asm nor MASM are used:
https://github.com/noloader/cryptopp-cmake/blob/b97d72f083fefa249e46ae3c15a2c294e615fca2/CMakeLists.txt#L567
This leads to linker errors about missing ExtendedControlRegister definition.

I'm not sure I understand the problem

Yeah, me too.
@SamuelEnglard, we need the command that is producing the error, and the exact error message. We can revisit this if you can provide it.

@MarcelRaad summed up the issue perfectly. If DISABLE_ASM is set for a 64bit build you get linking errors for ExtendedControlRegister. I honestly don't think there is a way to really fix this on Cryptopp's side. I think the CMake just needs to not allow the combination of DISABLE_ASM when using the Visual Studio 9 2008 generator targeting x64. It's simply an invalid configuration.


Adding _TZE200_gubdgai2 TS0601

Adding _TZE200_gubdgai2 TS0601 one more MOES cover / blind controller.
Closing: https://github.com/zigpy/zha-device-handlers/issues/934

Codecov Report

Merging #985 (44264e4) into dev (21af086) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##              dev     #985   +/-   ##
=======================================
  Coverage   82.55%   82.55%
=======================================
  Files         189      189
  Lines        4798     4798
=======================================
  Hits         3961     3961
  Misses        837      837

Impacted Files
Coverage Δ

zhaquirks/tuya/__init__.py
72.74% <ø> (ø)

zhaquirks/tuya/ts0601.py
100.00% <ø> (ø)

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 21af086...44264e4. Read the comment docs.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 82.555%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
3961

Relevant Lines:
4798

💛  - Coveralls

Needs a rebase

Rebasing was not working OK so closing and making on new PR


fix(date-time-picker): wait until finished typing to parse dates

Closes #2771
Summary

DateTimePicker wasn't waiting until the user had finished typing to parse times, so it was throwing invalid dates.

Change List (commits, features, bugs, etc)

don't parse absolute times until 5 characters have been typed.

Acceptance Test (how to verify the PR)

Open DateTimePicker default story
Click Custom Range
click Absolute
Click two dates (same and different)
Click the Start time input
Backspace to clear the box and type a time
tab to the End time input
type an end time
click apply
The correct chosen date should be visible

Regression Test (how to make sure this PR doesn't break old functionality)

no adverse side-effects for absolute dates.

Things to look for during review

[ ] Make sure all references to iot or bx class prefix is using the prefix variable
[ ] (React) All major areas have a data-testid attribute. New test ids should have test written to ensure they are not changed or removed.
[ ] UI should be checked in RTL mode to ensure the proper handling of layout and text.
[ ] All strings should be translatable.
[ ] The code should pass a11y scans (The storybook a11y knob should show no violations). New components should have a11y test written.
[ ] Unit test should be written and should have a coverage of 90% or higher in all areas.
[ ] All components should be passing visual regression test. For new styles or components either a visual regression test should be written for all permutations or the base image updated.
[ ] Changes or new components should either write new or update existing documentation.
[ ] PR should link and close out an existing issue

@sls-ca I believe there was a reason we had to wait for 5 chars, @kevinsperrine try typing 11:30 into one of the fields, I think the widget choked on strings like that because it will try and set the time to 11:03.


Implement Parameter support for stack create/update

fixes #6

Coverage increased (+0.02%) to 99.625% when pulling 2c91d337208caf6ded6745c954f9450142e1dce1 on feature/parameter-option into 50b6474db98c300ffa9bbb2836a05c3650c35bd0 on master.


Update Composer dependencies (2023-12-08-00-12)

Visual regression test passed!
View the visual regression test report