latency when a document is opened

Type: Bug
It takes ~2 seconds to open any file, even without extensions.
Same files opens instantly in sublim text or notepad.
I have a pretty beefy machine, it's absurd ^^
repro step: save a text file with a few characters, close document, open document...
What is going on ? Is there a way to profile that ?
VS Code version: Code 1.70.2 (e4503b30fc78200f846c62cf8091b76ff5547662, 2022-08-16T05:35:13.448Z)
OS version: Windows_NT x64 10.0.19042
Modes:

System Info

Item
Value

CPUs
AMD Ryzen Threadripper PRO 3995WX 64-Cores      (64 x 2695)

GPU Status
2d_canvas: enabledcanvas_oop_rasterization: disabled_offdirect_rendering_display_compositor: disabled_off_okgpu_compositing: enabledmultiple_raster_threads: enabled_onopengl: enabled_onrasterization: enabledraw_draw: disabled_off_okskia_renderer: enabled_onvideo_decode: enabledvideo_encode: enabledvulkan: disabled_offwebgl: enabledwebgl2: enabled

Load (avg)
undefined

Memory (System)
255.84GB (226.77GB free)

Process Argv
--crash-reporter-id 2176f31e-8a8a-41e0-a575-d97182f0e184

Screen Reader
no

VM
0%

Extensions (4)

Extension
Author (truncated)
Version

vscode-todo-plus
fab
4.18.4

csharp
ms-
1.25.0

python
ms-
2022.14.0

binary-viewer
Qia
1.1.1

A/B Experiments
vsliv368:30146709
vsreu685:30147344
python383:30185418
vspor879:30202332
vspor708:30202333
vspor363:30204092
vstes627:30244334
vslsvsres303:30308271
pythonvspyl392:30443607
vserr242cf:30382550
pythontb:30283811
vsjup518:30340749
pythonptprofiler:30281270
vshan820:30294714
vstes263:30335439
vscorecescf:30445987
pythondataviewer:30285071
vscod805:30301674
binariesv615:30325510
bridge0708:30335490
bridge0723:30353136
cmake_vspar411:30557514
vsaa593:30376534
pythonvs932:30410667
cppdebug:30492333
vscaat:30438848
pylanb8912:30545647
vsclangdc:30486549
c4g48928:30535728
hb751961:30553087
dsvsc012cf:30540253
azure-dev_surveyonecf:30548226
2144e591:30553903

Thanks for creating this issue! It looks like you may be using an old version of VS Code, the latest stable release is 1.71.0. Please try upgrading to the latest version and checking whether this issue remains.
Happy Coding!

Profile-20220912T125043.zip
I've opened a file at ~1.7 second, it shows at around 3.7s.
(text file of 38 bytes....)

Got the same issue. It loads for a few seconds before showing the content of the file.

Can you try to reproduce with our nightly insider builds? You can give our preview releases a try from: https://code.visualstudio.com/insiders/

Confirmed resolved on the 1.72.2 public release (d045a5e)
feels great =)
Thanks !


Many to One in API Seems Obfuscated Now

My colleague @WillBaldwin and I contacted a member of the Entity Framework team and they encouraged me to talk here about the recent change from beta3 to beta4 api. Specifically, I feel the following change as shown below is not necessarily for the best.
Previous
builder.Entity<Room>().HasMany(a => a.Books);
New
modelBuilder.Entity<Book>().Collection(c=>c.Books).InverseReference(o=>o.Room).ForeignKey(o => o.RoomId);
I understand that the team wishes to remove magic and to make a clean break with the EF6 api. However, I humbly suggest this is not it. In my very humble opinion, the new way to implement many to one is obfuscated. This is because the code first approach does not standardize itself with the common nomenclature used in standard relational database design. It also does not flow as well.
If you have specific reasons for changing this, I would like to know, but at least understand that the additional syntax, in my humble opinion, obfuscates and complicates what used to be straightforward.
I thank you for your time. I am a huge fan of your team and open source approach.

@heathyates :+1:

One vote for the new names here. I always found the relational modelling language mixed into the entity modelling code a bit hard to follow.
Not sure if you intended it, but your example implies beta4 requires both ends of the relationship and the foreign key to be specified explicitly, whereas beta3 did not and thus had much more concise syntax. I don't think that is the case? The InverseReference and ForeignKey parts are optional just as they were in beta3.

Hey All,
There are varying opinions on our team about the best way to tackle the relationship API and so we decided to try out the current API and see what feedback we get. Thank you for your feedback and we'll continue to monitor this issue and other places to see what folks think.
BTW one of the reasons we liked Reference/Collection was that it's consistent with the ChangeTracker API.
~Rowan


host popup menu: "leave game" should be "end the game"

Fixed via https://github.com/microsoft/pxt/pull/9186


Deadlock in BSpline

BSpline ICurve.GetPlanarState can cause a deadlock if Model.RecalcGeoObject is running at the same time.

As locking to This is not a good practice this should be fixed first.
But I'm not sure that this will solve the problem.
https://github.com/SOFAgh/CADability/blob/32a5dff18809b32c43002fb8e307838b57d1598e/CADability/BSpline.cs#L2901C9-L2906
Any suggestions are welcome.

Thanks for the reply.

Changing lock(this) and lock(typeof(...)) accross the entire codebase to dedicated lock(varThatIsOnlyUsedHere) will definitly reduce chances of deadlocks.

Within BSpline.cs lock (this) is used 4x.
I guess the original intention was to "protect" the object from being modified while running the lock section.
Would you rather change this so that every lock statement has it's own object? Or do they need to share a common object?

Would you rather change this so that every lock statement has it's own object?

The best answer for this is "it depends".
From outside it is a good practice to lock the object you are working on (like Model.RecalcGeoObject does) so you can avoid having multiple threads manipulating the same object. That applies if the object is not thread safe.
In general the best way to do locking would be
a) don't look the object from outside and make sure the object itself is thread safe
or
b) lock the object from outside everytime you use it in a multithreaded way. The object itself doesn't need locking internally (unless it starts it's own threads of cource)
Since CADability uses locking inside most external locks shouldn't be needed but the lock statements should not use lock(this) to avoid conflicts with external locks.
Back to the question

Would you rather change this so that every lock statement has it's own object?

I propably would vote for having fewer lock objects.
If there is not already a specific lock but a lock(this) I would replace these with a lock(lockVar) that is used by other lock(this) statements as well since there are many cases where code that runs inside a lock will call code that uses a lock itself. If they use different lock objects that might lead to some rare bugs where the data is inconsistant or an exception occures.
This example would cause a race condition while using the same lockVar would not.
public void MyMethod()
{
    lock(lockVar1)
    {
        if (this.isInitialized)
        {
             Initialize();
         }
    }
}

public void MyMethods2()
{
    lock(lockVar2)
    {
        if (this.isInitialized)
        {
             Initialize();
         }
    }
}

public void Initialize()
{
    lock(lockVar2)
    {
       this.dict.Add("key", "value");
    }
}

On the other hand you could get better performance with more specific locks but that would require some deep analysis of each lock statement so I think the shared lockVar with a possible performance tradeoff would be the better approach for now.
TLDR:
Replacing lock(this) with lock(lockVar) globally and adding a lockVar instance to each object would be easy to implement.
I can create a PR for this this since I have a lot of unit tests in my internal project that run in parallel so I would directly notice any issues.

I think in BSpline we already have two objects for the locking mechanism: "lockApproximationRecalc" and "planeLock". When in PlanarState ICurve.GetPlanarState() { lock (this) we change "this" into "planeLock" the special case would be solved (and the intention of the locking in GetPlanarState is exactly to avoid multiple recalculation of the plane).
Actually looking at this (old) code, I think we should change GetPlane() into
          if (plane.HasValue) return plane.Value;
          lock (planeLock)
           {
               double MaxDist;
               bool isLinear;
               Plane res = Plane.FromPoints(poles, out MaxDist, out isLinear);
               if (MaxDist < Precision.eps)
               {
                  plane = res;
                  return res;
               }

But I don't have time to test this at the moment.

Thank you for taking the time to look into this.
I created a commit d7eb93c that includes the suggested changes.
The other lock (this) statements are replaced by lock (bSplineLock) for now.
Moving if (plane.HasValue) return plane.Value; to the outside of the lock is a good idea.
But you still have to performe the check inside the lock too. Because the value could change between the check and the release of the lock.
I found an interesting site about this topic here:
https://www.pluralsight.com/guides/lock-statement-best-practices
I would appreciate if @Steinblock you could run your tests with this commit.

Closed #161


Problems while linking Swedish language support to Rasa?

Rasa NLU version: 0.13.6
OS: MacOS
Content of model configuration file:
language: 'sv'
pipeline:
  - name: "nlp_spacy"
  - name: "tokenizer_spacy"
  - name: "intent_entity_featurizer_regex"
  - name: "intent_featurizer_spacy"
  - name: "ner_spacy"
  - name: "ner_crf"
  - name: "ner_synonyms"
  - name: "intent_classifier_sklearn"
  - name: "ner_duckling"
    url: "http://<IP_ADDRESS>:8000"
    locale: "en_UK"
    dimensions: ["time"]
    timezone: "UK/London"

Issue:
How can I add Swedish language support to Rasa's NLU module? I installed this Swedish model as follows:
user:~$ pip3 install sv_model-0.0.0.tar.gz && python3 -m spacy link sv_model sv
Then, when I train Rasa's model:
 user:~/duckling/migration_2/rasa-assistant$ python3 -m rasa_nlu.train -c config.yml --data data/swedish_dev/ -o models --project current --verbose
I get the following error:

/usr/local/lib/python3.6/site-packages/h5py/__init__.py:36: FutureWarning: Conversion of the second argument of issubdtype from `float` to `np.floating` is deprecated. In future, it will be treated as `np.float64 == np.dtype(float).type`.
  from ._conv import register_converters as _register_converters
2018-10-15 15:43:52 INFO     rasa_nlu.utils.spacy_utils  - Trying to load spacy model with name 'sv'
2018-10-15 15:43:54 INFO     rasa_nlu.components  - Added 'nlp_spacy' to component cache. Key 'nlp_spacy-sv'.
Traceback (most recent call last):
  File "/usr/local/lib/python3.6/site-packages/rasa_nlu/extractors/duckling_extractor.py", line 108, in create_duckling_wrapper
    return DucklingWrapper(language=language)
  File "/usr/local/lib/python3.6/site-packages/duckling/wrapper.py", line 30, in __init__
    self.language = Language.convert_to_duckling_language_id(language)
  File "/usr/local/lib/python3.6/site-packages/duckling/language.py", line 60, in convert_to_duckling_language_id
    lang, ", ".join(cls.SUPPORTED_LANGUAGES)))
ValueError: Unsupported language 'sv'. Supported languages: ko$core, pt$core, da$core, fr$core, et$core, en$core, ar$core, de$core, ru$core, ja$core, id$core, zh$core, vi$core, uk$core, es$core, ga$core, it$core

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/local/Cellar/python/3.6.5_1/Frameworks/Python.framework/Versions/3.6/lib/python3.6/runpy.py", line 193, in _run_module_as_main
    "__main__", mod_spec)
  File "/usr/local/Cellar/python/3.6.5_1/Frameworks/Python.framework/Versions/3.6/lib/python3.6/runpy.py", line 85, in _run_code
    exec(code, run_globals)
  File "/usr/local/lib/python3.6/site-packages/rasa_nlu/train.py", line 184, in <module>
    num_threads=cmdline_args.num_threads)
  File "/usr/local/lib/python3.6/site-packages/rasa_nlu/train.py", line 148, in do_train
    trainer = Trainer(cfg, component_builder)
  File "/usr/local/lib/python3.6/site-packages/rasa_nlu/model.py", line 155, in __init__
    self.pipeline = self._build_pipeline(cfg, component_builder)
  File "/usr/local/lib/python3.6/site-packages/rasa_nlu/model.py", line 166, in _build_pipeline
    component_name, cfg)
  File "/usr/local/lib/python3.6/site-packages/rasa_nlu/components.py", line 441, in create_component
    cfg)
  File "/usr/local/lib/python3.6/site-packages/rasa_nlu/registry.py", line 143, in create_component_by_name
    return component_clz.create(config)
  File "/usr/local/lib/python3.6/site-packages/rasa_nlu/extractors/duckling_extractor.py", line 128, in create
    wrapper = cls.create_duckling_wrapper(config["language"])
  File "/usr/local/lib/python3.6/site-packages/rasa_nlu/extractors/duckling_extractor.py", line 110, in create_duckling_wrapper
    raise Exception("Duckling error. {}".format(e))
Exception: Duckling error. Unsupported language 'sv'. Supported languages: ko$core, pt$core, da$core, fr$core, et$core, en$core, ar$core, de$core, ru$core, ja$core, id$core, zh$core, vi$core, uk$core, es$core, ga$core, it$core

I even tried to modify Language.py:
class Language(object):
    """Helper class containing all supported languages
    """

    ARABIC = 'ar$core'
    DANISH = 'da$core'
    GERMAN = 'de$core'
    ENGLISH = 'en$core'
    SPANISH = 'es$core'
    ESTONIAN = 'et$core'
    FRENCH = 'fr$core'
    IRISH = 'ga$core'
    INDONESIAN = 'id$core'
    ITALIAN = 'it$core'
    JAPANESE = 'ja$core'
    KOREAN = 'ko$core'
    PORTUGUESE = 'pt$core'
    RUSSIAN = 'ru$core'
    UKRAINIAN = 'uk$core'
    VIETNAMESE = 'vi$core'
    CHINESE = 'zh$core'
    sv = 'sv$core'

    SUPPORTED_LANGUAGES = {
        ARABIC,
        DANISH,
        GERMAN,
        ENGLISH,
        SPANISH,
        ESTONIAN,
        FRENCH,
        IRISH,
        INDONESIAN,
        ITALIAN,
        JAPANESE,
        KOREAN,
        PORTUGUESE,
        RUSSIAN,
        UKRAINIAN,
        VIETNAMESE,
        CHINESE,
        sv
    }

But it is not working. Any idea of how to link and use spacy swedish language model with rasa?

It seems the pypi package for duckling hasn't been updated to support swedish yet. I just took a look and duckling does support it, just that package hasn't been updated yet. Not sure there's much we can do about that at the moment.

Actually sorry, that python package is no longer maintained and neither is the clojure duckling version. The recommended component to use is ner_duckling_http https://rasa.com/docs/nlu/components/#ner-duckling-http


Add constants for smi values within the int class

This issue was originally filed by<EMAIL_ADDRESS>
Keeping values within the smi range is important to the performance of numeric computation in Dart but the min and max values for smi on 32 bit and 64 bit architectures are not present within the SDK.
Would be great to have the int class contain constants for these values at https://www.dartlang.org/articles/numeric-computation/#integers, similar to how the double class contains constants for things such as infinity.

There are no plans to add constants for SMIs.

Has anything changed in Dart 2 to make this worthy of reconsideration?
I would like constants not for performance reasons but to test if an arithmetic operation would result in overflow. (I acknowledge that it's not quite as necessary in Dart since int overflow behavior is well-defined, unlike in C where it's UB.)

There is not change in the evaluation. A "smi" is an implementation detail, and leaking that will make it harder for implementations to optimize, not easier.
If you want to be relatively safe, you can probably assume that 31 bit signed integers are efficient everywhere.


ImprovementImprove show analyze performance.

The origin show analyze code would traverse the task id to task map for each job to get all the tasks for this job, which is very slow.
This pr keep the task ids for each job in the job info class, so that we can get the tasks by task ids directly.
To show 1100+ jobs with 11000+ tasks, the time costing is reduced from 0.14s to 0.01s.

Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

run buildall

run buildall

(From new machine)TeamCity pipeline, clickbench performance test result:
the sum of best hot time: 45.31 seconds
stream load tsv:          512 seconds loaded<PHONE_NUMBER>9 Bytes, about 139 MB/s
stream load json:         20 seconds loaded<PHONE_NUMBER> Bytes, about 112 MB/s
stream load orc:          65 seconds loaded<PHONE_NUMBER> Bytes, about 16 MB/s
stream load parquet:          31 seconds loaded 861443392 Bytes, about 26 MB/s
insert into select:          29.5 seconds inserted 10000000 Rows, about 338K ops/s
storage size:<PHONE_NUMBER>4 Bytes

LGTM


verifier, tenant: make payload for agent completely optional

This now allows an agent to be added without using the payload feature.
Note that then also no U/V key is sent to the agent on successful attestation.

Given we are "changing" the column v on verifier's database , don't we need an alembic migration?

We don't because this is the default. I just wanted to make it explicit that we are intending to put null in there.

Note that then also no U/V key is sent to the agent on successful attestation.

What are the consequences of this?

Note that then also no U/V key is sent to the agent on successful attestation.

What are the consequences of this?

The consequence of this is that the agent has no idea if it passed initial attestation at some point and that the /v2.1/keys/verify interface wont work.  So the --verify in the tenant won't work.

Note that then also no U/V key is sent to the agent on successful attestation.

What are the consequences of this?

The consequence of this is that the agent has no idea if it passed initial attestation at some point and that the /v2.1/keys/verify interface wont work. So the --verify in the tenant won't work.

I  tested this. It works for me.
I hadn't used --verify before. When not passing -f <file> and passing --verify on -c add then we get an error. I think we should be able to catch this case and error out telling the user that --verify requires -f <file>. -c update' also supports --verifybut there I am not sure how to handle this other than having-f described as a prerequisite for--verify` in the help screen.

@stefanberger yes will add better error handling for this case.

@stefanberger @kkaarreell now updated the tenant to include a better error message when no payload is specified, but verify is set.

LGTM


Configure a secure connection

Hello,
First off, thanks for this project! It makes developing cloudworkers much easier.
Is there a way to configure a secure connection?
Thanks,
Chad Shryock

PR #87 should do the trick once it lands on master. Thanks!


Put formData in store

Done:

added viz, formData into store with same structure as bootstrapData.viz and form_data
rewrite reducers and action creators for new structured store
Added SelectArray component
Todo:
do this for other vizTypes
rewrite tests for reducers

will merge this first and modify PRs for other viz types
needs-review @ascott

Emailed codeclimate's support team for the syntax error

nice PR! 🚢 💯


Add Support For Decoding To Vec For JSON Columns

PR Info

Closes #1517

New Features

[x] Add ability to decode to concrete Vec types for JSON[] columns.

Changes

[x] Add ActiveEnumOfJson trait that is implemented by ActiveEnum and JSON types.
[x] Auto implement TryGetable for any T where T implements ActiveEnumOfJson.
[x] Auto implement TryGetable for any Vec<T> where T implements ActiveEnumOfJson, when array feature is enabled.
[x] Add conditional clause in FromJsonQueryResult macro to implement the NotU8 trait for the target struct/enum when postgres-arrays feature is enabled.
[x] Update DeriveActiveEnum macro to implement ActiveEnumOfJson for ActiveEnums.
[x] Add ActiveEnumOfJson implementation for JSON type.
[x] Add tests

Thank you for the effort! I also need some time to wrap my head around it.

Thanks again for your effort. I am glad to see a proof of concept here. I got a slightly different idea, so let me try on it.

Thanks @tyt2y3, Reworked changes look so much better :D

Closing in favour of #189


mypy compatibility

[ ] Closes #xxxx
[x] Tests added / passed
[x] Passes pre-commit run --all-files

This mostly ignore remaining complex typing situations to get mypy passing so that we can enable it and start enforcing going forward.
Builds off of https://github.com/dask/dask/pull/8706

Can one of the admins verify this patch?

Before we start requiring mypy in CI I think that we should raise that as a discussion in https://github.com/dask/community (unless there was already a decision on this).

Before we start requiring mypy in CI I think that we should raise that as a discussion in https://github.com/dask/community (unless there was already a decision on this).

I believe there was consensus at the maintainers weekly meeting

I'm a bit swarmed right now with PyConDE and Easter coming up, so I'm afraid I won't be able to continue the review before April 19th

Took a stab at addressing a few more comments (the easily ones, of course).
Currently getting the following failures locally
unit tests
_______________________________________________ test_store_nocompute_regions _______________________________________________
dask/array/tests/test_array_core.py:2020: in test_store_nocompute_regions
    d1 = da.store(x, y, regions=(0,), compute=False)
dask/array/core.py:1092: in store
    raise ValueError(
E   ValueError: Different number of sources [1] and targets [2]
_____________________________________________________ test_store_locks _____________________________________________________
dask/array/tests/test_array_core.py:2091: in test_store_locks
    assert store(a, at, scheduler="threads", num_workers=10) is None
dask/array/core.py:1091: in store
    if len(sources) != len(targets):
E   TypeError: object of type 'NonthreadSafeStore' has no len()

pre-commit (mypy)
dask/array/core.py:1098: error: List item 0 has incompatible type "Union[Tuple[slice, ...], Tuple[Any, ...], None]"; expected "Tuple[slice, ...]"
dask/array/core.py:1168: error: Incompatible types in assignment (expression has type "Dict[Tuple[Any, ...], Any]", variable has type "Union[HighLevelGraph, Dict[Hashable, Any]]")

Final code review at https://github.com/phobson/dask/pull/2

Failed Mac build(s) appear to be related to GHA issues.

Thank you!

Woo! Thanks @phobson and @crusaderky!

Thanks @crusaderky and @ian-r-rose  for the patience and guidance!


[iOS][Rendering] There's no way to get additional properties from ACOAdaptiveCard

Platform
What platform is your issue or question related to? (Delete other platforms).

[ ] iOS

Author or host
Host
Version of SDK
2.4.6
Details
We have a need to override some properties at the card level that are normally at the host config level. For example our host config file might contain:
    "mycompany.contentLightColor": "FFFFFFFF",
    "mycompany.contentDarkColor": "00263EFF",

But for some cards, we want to override those with different colors. In the rendering hooks for the UI elements we can get a reference to the ACOAdaptiveCard via ACRView.card but the problem is that ACOAdaptiveCard doesn't expose any of the properties that we've included at the top level of the card.

I had thought that ACOAdaptiveCard.inputs would give me this data, but it's always empty.
(lldb) po String(data:rootView!.card()!.inputs(), encoding: .utf8)
▿ Optional<String>
  - some : "{\n\n}"

I had thought that ACOAdaptiveCard.inputs would give me this data, but it's always empty.
(lldb) po String(data:rootView!.card()!.inputs(), encoding: .utf8)
▿ Optional<String>
  - some : "{\n\n}"

@jwoo-msft Can you answer what the expected behavior here is? Is this a bug or something that's missing from the API? Thanks!

@jwoo-msft Can you answer what the expected behavior here is? Is this a bug or something that's missing from the API? Thanks!

@jscalo, thanks for reporting this issue.

@jscalo, thanks for reporting this issue.

This is about additional properties on the card level which is available on some platforms but not all, and should be available everywhere.

@jwoo-msft What is the status of this bug?

@RebeccaAnne, I re-assigned the issue to me.


Gradio version not supported

Following error on python bark_webui.py;
AttributeError: module 'gradio.components' has no attribute 'Form'
Possible hotfix: pip install gradio==3.34.0 on your activated env

All set, if you update with just
git pull it should work on newer Gradio now.


steps-app-gallery-deploy v1.0.0

What to do if the build fails?
At the moment contributors do not have access to the CI workflow triggered by StepLib PRs. In case of a failed build, we ask for your patience. Maintainers of Bitrise Steplib will sort it out for you or inform you if any further action is needed.
New Pull Request Checklist
Please mark the points which you did / accept.

[x] I will not move an already shared step version's tag to another commit
[x] I read the Step Development Guideline
[x] I have a test for my Step, which can be run with bitrise run test (in the step's repository)
[x] I did run bitrise run audit-this-step (in the step's repository - note, if you don't have this workflow in your bitrise.yml, you can copy it from the step template.)
[x] I read and accept the Abandoned Step policy

Hi @ferPrieto !
I found some problems with this PR:

There is already an app-gallery-deploy step shared: https://github.com/bitrise-io/bitrise-steplib/tree/master/steps/app-gallery-deploy with multiple versions.
This version looks like using a different step ID originally it was app-gallery-deploy -> and now appgallery-deploy.
Also the issuer is different: https://github.com/FutureMind/bitrise-step-huawei-app-gallery-apk-distribution.git (originally)
This step.yml was not shared with out stepman. Please follow the guide: https://devcenter.bitrise.io/contributors/sharing-steps-with-all-bitrise-users/

Hi @ferPrieto !
I found some problems with this PR:

There is already an app-gallery-deploy step shared: https://github.com/bitrise-io/bitrise-steplib/tree/master/steps/app-gallery-deploy with multiple versions.
This version looks like using a different step ID originally it was app-gallery-deploy -> and now appgallery-deploy.
Also the issuer is different: https://github.com/FutureMind/bitrise-step-huawei-app-gallery-apk-distribution.git (originally)
This step.yml was not shared with out stepman. Please follow the guide: https://devcenter.bitrise.io/contributors/sharing-steps-with-all-bitrise-users/

@trapacska this app-gallery-deploy step is the verified one (official Huawei step), hence it's got different ID, different issuer and so force.
The step.yml was shared with out stepman.
Can you double check and discuss it with your colleagues?

@trapacska this app-gallery-deploy step is the verified one (official Huawei step), hence it's got different ID, different issuer and so force.
The step.yml was shared with out stepman.
Can you double check and discuss it with your colleagues?

@ferPrieto if you compare the two files: https://github.com/bitrise-io/bitrise-steplib/pull/2857/files#diff-52e5526231d842346761fc6353d084d733e32be0f3a057d49c7af5d46567ef95 (from this PR) and the one from the step repo: https://github.com/ferPrieto/steps-app-gallery-deploy/blob/main/step.yml then you can see the files are identical.
When you release it with stepman(https://devcenter.bitrise.io/contributors/sharing-steps-with-all-bitrise-users/#sharing-with-the-bitrise-share-command) then a slightly modified version of step.yml will be committed to this PR. It will have source object for example, like here: https://github.com/bitrise-io/bitrise-steplib/blob/master/steps/amazon-s3-deploy/3.1.1/step.yml#L13-L15
The reason I closed this PR because the share with stepman requires a new PR. (will be on different branch)

@ferPrieto if you compare the two files: https://github.com/bitrise-io/bitrise-steplib/pull/2857/files#diff-52e5526231d842346761fc6353d084d733e32be0f3a057d49c7af5d46567ef95 (from this PR) and the one from the step repo: https://github.com/ferPrieto/steps-app-gallery-deploy/blob/main/step.yml then you can see the files are identical.
When you release it with stepman(https://devcenter.bitrise.io/contributors/sharing-steps-with-all-bitrise-users/#sharing-with-the-bitrise-share-command) then a slightly modified version of step.yml will be committed to this PR. It will have source object for example, like here: https://github.com/bitrise-io/bitrise-steplib/blob/master/steps/amazon-s3-deploy/3.1.1/step.yml#L13-L15
The reason I closed this PR because the share with stepman requires a new PR. (will be on different branch)

Apologies for the misunderstanding @trapacska
Last time I used the stepman I ended up skipping the last step because github did not recognise my credentials when I executed. I had to change my local configuration and it seems to work now 👍
I've raised a new PR. Thanks for the support!

Apologies for the misunderstanding @trapacska
Last time I used the stepman I ended up skipping the last step because github did not recognise my credentials when I executed. I had to change my local configuration and it seems to work now 👍
I've raised a new PR. Thanks for the support!


[luci-app-fwknopd] Remove usage of dynamic tag.

Also adds NAT-DNS as a default setting, and enables a QR-code per access.conf entry
Signed-off-by: Jonathan Bennett<EMAIL_ADDRESS>

This commit can close #828

Hi,
im also getting error like above, under service asteriks dialplan in LEDE GUI..
/usr/lib/lua/luci/dispatcher.lua:478: Failed to execute cbi dispatcher target for entry '/admin/services/asterisk/dialplans'.
The called action terminated with an exception:
/usr/lib/lua/luci/template.lua:97: Failed to execute template 'cbi/map'.
A runtime error occured: /usr/lib/lua/luci/template.lua:97: Failed to execute template 'cbi/tsection'.
A runtime error occured: /usr/lib/lua/luci/template.lua:97: Failed to execute template 'cbi/ucisection'.
A runtime error occured: [string "/usr/lib/lua/luci/view/cbi/ucisection.htm"]:15: attempt to call field 'json_encode' (a nil value)
stack traceback:
[C]: in function 'assert'
/usr/lib/lua/luci/dispatcher.lua:478: in function 'dispatch'
/usr/lib/lua/luci/dispatcher.lua:121: in function
please help me out..where im doing wrong?

@ammudaiwik I'm not sure if it's the same issue.  The dynamic tag has been broken for a while.  Assuming you're able to reproduce the problem with the latest LEDE release,  I suggest opening a new bug report for the issue you're seeing.  This pull request isn't the best place to try to get help. =)


chore(deps): update dependency containernetworking/plugins to v1.4.0

This PR contains the following updates:

Package
Update
Change

containernetworking/plugins
minor
1.3.0 -> 1.4.0

Release Notes

containernetworking/plugins (containernetworking/plugins)
v1.4.0: CNI Plugins v1.4.0
Compare Source
New features:

(#832). tap: allow for a tap device to be created as a bridge port
(#914). [tuning] add ability to set tx queue len

Improvements:

(#969). Add CNI_NETNS_OVERRIDE
(#979). Add ndisc_notify in ipvlan for ipv6 ndp
(#974). macvlan: enable ipv6 ndisc_notify
(#950). Create IPAM files with 0600 permissions
(#924). More efficient iptables usage.
(#902). spoofcheck: Make use of go-nft's ApplyConfigEcho(). This is much faster
(#874). Add routes propagation for VRF plugin

Build:

(#982). Bump to golang:1.21-alpine
(#948). build: Use POSIX sh for shell scripts

Bug fixes:

(#954). macvlan cmdDel: handle deletion when master has been deleted
(#927). vrf: fix route filter to use output iface

Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.

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

This PR has been generated by Renovate Bot.

Edited/Blocked Notification
Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.
You can manually request rebase by checking the rebase/retry box above.
⚠ Warning: custom changes will be lost.


Core: New split path algo

Core: New split path algo
Description
Current split paths are slow and don't 100% work.
This algo does some smart pruning.
It only looks at a single path in a split at a time.

Fixes # (issue)
Checklist
Please read and execute the following:

[ ] My code follows the coding guidelines of this project
[ ] My PR title is following the contribution guidelines
[ ] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation (if applicable)
[ ] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works (if applicable)
[ ] New and existing unit tests pass locally with my changes
[ ] Any dependent changes have been merged and published in downstream modules
[ ] I ran Black to format my code

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

[ ] I agree to follow this project's Code of Conduct

Superseded by https://github.com/atopile/atopile/pull/523


Add Deck tests using headless-gl

Change List

Add node tests for the Deck class

Coverage increased (+2.2%) to 74.41% when pulling f043e62ac094968e624b68735efdbdbc67f05b6e on x/tests-node into 11e8c8e6e8a852c10245237e0fcc259b2cdf7447 on master.


Fixed issue with custom simple_form date input

Use the natural simple_form process for setting initial value to avoid making assumptions about the data type. Aligned method signature with latest simple_form spec. Bumped version.
Simple_form avoids modifying the values in components. Doing the same saves us from a world of hurt. This puts the responsibility to correctly format the input data onto the developer. This change does not affect how the component is used.

@synth I'd like to merge this in - provides a fix for hr_performance.


APEXCORE-585 #resolve do not try to calculate latency if the first wi…

…ndow has not complete
@vrozov please review and merge

@vrozov thanks for the review. There was actually a bug in the original code that was uncovered by this intermittent unit test failure. it's fixed.


feat(package): brew support

Motivation
Allowing the use of more features of testinfra on macOS (darwin) hosts.
Changes

Added HomebrewPackage

Notes

Linux hosts with homebrew installed might also work (though untested). Can easily be limited to only darwin hosts, leaving this decision up to maintainers' discretion.

Merged, thanks!


Mast: Watch hayalsohbet.net

Mast requests the watch of the watch_keyword hayalsohbet\.net. See the MS search here and the Stack Exchange search in text, in URLs, and in code.

hayalsohbet\.net has been seen in 3 true positives, 0 false positives, and 0 NAAs.

Approved by Makyen in Charcoal HQ


Hex color widget

Instead of having 5 colors for rectangles background let's have one default color (yellow one):

and text input near to it to change to any color: [] #7d26cd

I would like to signup for this!

Created a fork and a new branch in https://github.com/GnanaGanesh1999/velo

Seems like not much progress on this issue, I close it for now. This can be re-opened if someone wants to work on it.


feat: Add PostgreSQL guide

Description
Added PostgreSQL builder guide.
Related Issue(s)
Closes #80

deployed docs: https://input-output-hk.github.io/catalyst-ci/branch/feat_sql_guides/guides/languages/postgresql/


Client-sided Invalid Loadout Index Crash

Calling stuff like RequestPilotLoadout 10923 or RequestTitanLoadout 19230 triggers a crash on next persistent load.

Closing this as its fixed with #762 and #764


Add a ttgir pass to convert tt.load/tt.store to buffer operations

This is part 3 of the redesign stemmed from #4716 (which I am closing) . Instead of rebasing that PR, I opened a new one, since the differences were significant.
This PR is only introducing a ttgir pass to convert tt.load/tt.store to amdgpu.buffer_load/amdgpu.buffer_load, when this is possible : this means we need to check for 3 conditions:

The pointer arithmetic has been canonicalized (scalarPtr->splat->addptr->load/store)
The offsets are 32-bits
The offsets are non-negative. We use a mix of analysis and assumptions to verify this condition

cc @ThomasRaoux @antiagainst

I rebased and removed the temporary enablement of the conversion pass


Add opensds controller api spec validation

Signed-off-by: leonwanghui<EMAIL_ADDRESS>
What this PR does / why we need it:
Add opensds controller api spec validation step in CI envrionment.
Which issue this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close that issue when PR gets merged): fixes #
Special notes for your reviewer:
Release note:

Coverage remained the same at 28.708% when pulling f0417a9578006598a83a86f564c3606b8c71c47b on leonwanghui:api-update into 18d1fb11d835fbac9ba6991402f88a47ba92e089 on opensds:development.

Coverage remained the same at 28.708% when pulling f0417a9578006598a83a86f564c3606b8c71c47b on leonwanghui:api-update into 18d1fb11d835fbac9ba6991402f88a47ba92e089 on opensds:development.


Added issuerId to the schema and cred_def anoncreds objects

Partially closes #34

Adds IssuerId property to the Schema and CredentialDefinition.

This is reflects the PR for adding the issuerId to anoncreds objects.
(revocation needs to be done but is omitted here for conflicts with #37.
Signed-off-by: blu3beri<EMAIL_ADDRESS>

@blu3beri on the last WG call we came to the conclusion that:

Only legacy indy identifiers can use _did for backwards compatiblity
All other identifier types (qualified indy, but also other methods) MUST use _id
They can't be used at the same time

That means we need to support both in this library, and that we need to verify the above rules

They can't be used at the same time

Do you mean they can't be used in the same proof request of for s specific group within the request?

Do you mean they can't be used in the same proof request of for s specific group within the request?

Hm. If you're using the new syntax anywhere in the proof request, you could just as well use it everywhere. But that's probalby more complex to verify?


Added multiple artifact support + fixes a bunch of bugs

Sorry about the large PR.  I'll try and document below.
New Features

Added support for multiple artifacts.  Previously the plugin seemed to only deal with the primary build.  Work Items and commits are pulled in for all artifacts now.

Fundamental Changes

I really struggled to add the multiple artifact support using the callback architecture.  I swapped it out for async/await.
Added a bunch more logging
Converted code to be async/await compatible (eg. remove forEach)

Fixes

TFVC changesets were not being pulled through because the changesets were prefixed with "C"
TFVC changesets were being limited to 100.  I have changed this limit to 1000.
TFVC changeset comments were truncated.
Line endings were not working correct when trying to use the output variable in an email.
If a checkin comment contained a line ending, this would break the plugin.
Fixed an issue where the extension would crash if no workitems were returned.

I am testing this out, but not well at present to not getting much community work done, I will get there

Sorry it took a while, tested this and all seems good,  I have published it as 1.2.2
I added a few bits to the typescript/vscode config to make local debug easier


Added typescript and update old dependencies to React v.18

Thanks alot for doing this <3

Any chance this could be reviewed and merged in?

@seveibar any chance you can look at this?

Hey guys, taking a look

Would it be possible to toss this in a branch as-in and add a note in the README saying experimental React 18 support is a work in progress?

If anyone need package with this pull, i deploy it npm.js
https://www.npmjs.com/package/@idapgroup/react-image-annotate

Would it be possible to toss this in a branch as-is and add a note in the README saying experimental React 18 support is a work in progress?

I'm eager to merge this, but I think my comments are pretty reasonable, for a project this old its good to make sure you don't lose testing surface area, and some of the other changes would misdirect the user, eg the README wouldn't link to user to the npm package published by this repo.
To clarify: I'm very eager to merge and make people maintainers


Responsive slides

Feature request is related to

[x] embla-carousel (core package)
[ ] embla-carousel-react
[ ] embla-carousel-vue
[ ] embla-carousel-svelte
[ ] embla-carousel-autoplay
[ ] embla-carousel-auto-height
[ ] embla-carousel-class-names
[ ] embla-carousel-docs (documentation)
[ ] embla-carousel-docs (generator)

Is your feature request related to an issue?
I'd like to display some slide only on mobile or desktop
Describe the solution you'd like
I have been trying to show / hide slides using CSS (display: none) but it seems to impact the slider and I end up between two slides when sliding between slides. The CSS option might not be the best one or might require some additional thoughts / guidance.

Hi @ccanete,
Use the slides option together with breakpoints and make sure the slides you don’t want to show don’t have any sizes. For example you can hide them with display: none;.
Best,
David

Thanks a lot @davidjerleke for the prompt answer and sorry for the wrong channel. I'll go for discussions next time.
And great job with Embla, it's fantastic to use.


Confused message from spacedrop

Hi.  A few weeks ago I restarted my Keybase account because I lost the papers and my phone.  After restarting it and adding devices again, I had lost the airdrop and had a message from spacedrop that says what is in the photo.  Does it mean that I will not receive the next airdrop?  If so, can I delete the account and create a new one to join the airdrop?  Or what does that message mean?

Anyone who can help me?


[release-1.26] Nodes joined with kubeadm-style bootstrap tokens cannot automatically rejoin when the node object is deleted

https://github.com/k3s-io/k3s/issues/7797 backport

Validated on release-1.26 branch using commit a7373f94d5b038110b9debbea64f3fa4a2a01b62
Docs: https://docs.k3s.io/cli/token#bootstrap
Environment Details
Infrastructure
Cloud EC2 instance
Node(s) CPU architecture, OS, and Version:
Ubuntu 22.04
Cluster Configuration:
1 server, 1 agent
Replication results using k3s v1.26.6+k3s1

$ k3s token create --ttl 24h
<TOKEN>

Used the token generated to join the agent node

$ kubectl get nodes
NAME               STATUS   ROLES                       AGE    VERSION
ip-172-31-18-144   Ready    control-plane,etcd,master   3m7s   v1.26.6+k3s1
ip-172-31-18-194   Ready    <none>                      18s    v1.26.6+k3s1

Stop k3s-agent service and delete agent node

ubuntu@ip-172-31-18-144:~$ kubectl delete node ip-172-31-18-194
node "ip-172-31-18-194" deleted
ubuntu@ip-172-31-18-144:~$ kubectl get nodes
NAME               STATUS   ROLES                       AGE   VERSION
ip-172-31-18-144   Ready    control-plane,etcd,master   12m   v1.26.6+k3s1

Deleted password file on agent node

sudo rm -rf /etc/rancher/node/

After starting the agent service now, agent refuses to join the cluster with below logs
On server
Jul 14 00:26:11 ip-172-31-18-144 k3s[18645]: time="2023-07-14T00:26:11Z" level=error msg="Sending HTTP 401 response to <IP_ADDRESS>:54866: unable to verify node identity: nodes \"ip-172-31-18-194\" not found"

On Agent
Jul 14 00:26:11 ip-172-31-18-194 k3s[5203]: time="2023-07-14T00:26:11Z" level=info msg="Waiting to retrieve agent configuration; server is not ready: https://<IP_ADDRESS>:6444/v1-k3s/serving-kubelet.crt: 401 Unauthorized"

Workaround as described after removing the client-kubelet.crt and client-kubelet.key and password file, agent was able to join the cluster

$ kubectl get nodes
NAME               STATUS   ROLES                       AGE   VERSION
ip-172-31-18-144   Ready    control-plane,etcd,master   18m   v1.26.6+k3s1
ip-172-31-18-194   Ready    <none>                      10s   v1.26.6+k3s1

Validation results using commit a7373f94d5b038110b9debbea64f3fa4a2a01b62

Following the above steps, agent successfully joined the cluster after restarting the service without workaround

$ k3s -v
k3s version v1.26.6+k3s-a7373f94 (a7373f94)
go version go1.19.10

$ k3s token create --ttl 24h
<TOKEN>

Use the token to join agent node to the cluster

$ kubectl get nodes
NAME               STATUS     ROLES                       AGE     VERSION
ip-172-31-18-144   Ready      control-plane,etcd,master   2m27s   v1.26.6+k3s-a7373f94
ip-172-31-18-194   NotReady   <none>                      77s     v1.26.6+k3s-a7373f94

Stop k3s-agent on agent node and delete agent node from server

$ kubectl delete node ip-172-31-18-194
node "ip-172-31-18-194" deleted

Restart agent node

$ kubectl get nodes
NAME               STATUS   ROLES                       AGE     VERSION
ip-172-31-18-144   Ready    control-plane,etcd,master   3m16s   v1.26.6+k3s-a7373f94
ip-172-31-18-194   Ready    <none>                      6s      v1.26.6+k3s-a7373f94

No error observed on agent node,  but observed the error below in server log

Jul 14 00:42:44 ip-172-31-18-144 k3s[24475]: time="2023-07-14T00:42:44Z" level=error msg="Sending HTTP 401 response to <IP_ADDRESS>:48798: unable to verify node identity: nodes \"ip-172-31-18-194\" not found"
Jul 14 00:42:45 ip-172-31-18-144 k3s[24475]: time="2023-07-14T00:42:45Z" level=error msg="Sending HTTP 401 response to <IP_ADDRESS>:48814: unable to verify node identity: nodes \"ip-172-31-18-194\" not found"


"Dictionary index must be less than base vector's size. Index: {}

Bug description
NA
https://app.circleci.com/pipelines/github/facebookincubator/velox/32465/workflows/165388c8-f523-4d8d-b436-17525c2f86c2/jobs/208163
System information
NA
Relevant logs
No response

this is duplicate


Persian Language support

I'm sorry to write back so late, @omidp .
Could you update the PR (merge/rebase to master) and fix emerging issues, please?
You can run gradlew check to be sure that the checks pass.
I look forward merging your contribution.


toot.jeena.net doesn't look like a Mastodon instance

I have my own Mastodon instance but when I try to set it up in bridgy I only get this error message:

toot.jeena.net doesn't look like a Mastodon instance.

Which is wrong. Any idea why and what I can do to be able to set it up?

Hey, yes! Looks like your Mastodon instance is a bit unhappy, it's returning 500 to GET requests (unauthenticated) to https://toot.jeena.net/api/v1/instance, which is the first Mastodon API endpoint Bridgy hits, to confirm that it's Mastodon and grab a bit of metadata. Background: https://docs.joinmastodon.org/methods/instance/

Looks like it's not just that API endpoint, other user-facing URLs are unhappy too, eg https://toot.jeena.net/about/more

Aah damn. Thanks then it has nothing to do with Bridgy, I'll close this one, thanks for pointing it out!


Ignition Settings Dropdown

Hey - I love the new ignition, it is awesome!
Just one thing I spotted though, on Chrome, in dark mode, when selecting an IDE in the ignition settings, the text colour seems to be the same as the dropdown background making it a bit hard to see the other options.

Thanks for reporting, we'll fix this soon!

Thanks for reporting, we'll fix this soon!

No worries! :) - really really great job with this.


Address withdraw from privatekey changes and merge into sundai branch

This addresses the change proposals by @sunify in #33.
I haven't gotten around to testing these changes yet. Will convert from draft to PR once I've done that.
What to do with #33 now?
I think it would make sense to leave #33 open as it is applicable for the master branch of leapdao/burner-wallet. I'll cherry pick the changes made here into that branch.

Why not add this commit into #33 and cherry-pick commit from sunDai branch? Then merge it into master and rebase sunDai

Why not add this commit into #33 and cherry-pick commit from sunDai branch? Then merge it into master and rebase sunDai

OK will try. Closing this.

OK will try. Closing this.

Actually it's not as easy as git cherry-pick 9d09791 as there are other variables added to App.js in other commits of branch sunDai that are expected by 9d09791.  Will hence simply reopen this PR and let go #33 go unmaintained for now.


Bold, Italics, Underline not active when clicked

Information
Browser version: Microsoft Edge 41, Google Chrome 64, Firefox 58, IE 11
OS: Windows 10
Screen resolution: All
How to reproduce the bug?
Click the bold/italics/underline button and it should stay active. They should function similar to the way the justify and list buttons currently work.
Thanks

Nope, I can't do that, sorry. Already closed thousands of time :/


libxft-bgra-git orphaned

I recently installed a slightly modified version of Luke's dwm, and every time I sign in, I receive a message saying I need to install libxft-bgra-git from the AUR. However, this package has been orphaned.
Thankfully, I can simply run 'startx' and use my system without any issues (including rendering color emojis), so I assume that libxft takes care of everything on its own now.
What do I need to do so I can get rid this persistent message?

I had installed libxft-git which replaced libxft-bgra-git. Getting same issue at login as OP. Now later package is not showing in aur. HELP!!!

Just remove the message and check from the .zprofile. It's long obsolete now. The normal libxft should be sufficient now as it has been updated. No AUR needed.


Disable default browser scrolling while in game area

Adding
window.addEventListener("keydown", function(input) {
    // key codes for space, up, down respectively
    if([32, 38, 40].includes(input.keyCode)) {
        input.preventDefault();
    }
}, false);

to the iframe for the simulator of the games will prevent the default page scrolling action for the up/down arrow keys and space, so that when users try to use the arrow keys and space bar to play the games, they do not accidentally end up scrolling up and down in the area. This issue is primarily present in laptops, and generally when the 'explorer' drop down menu is open.
(Specifically, adding it to apply only to the trg-arcade.userpxt.io/---simulator iframe that is loaded, so that it only applies when the user selects the simulator itself / so they can scroll normally otherwise)

Is this dupe of https://github.com/Microsoft/pxt-arcade/issues/39?

This is the same issue / fix described in #39, yes.


compatibility with V8 greater than v7.6 (patch for building)

Hello @theturtle32,
please take a look at my compatibility patch here : 47d16204fce6311447388adb0191a59f882612ac
It fixes the build with the latest release of node v12 :
make: Entering directory '/root/WebSocket-Node/build'
  CXX(target) Release/obj.target/bufferutil/src/bufferutil.o
../src/bufferutil.cc: In static member function 'static Nan::NAN_METHOD_RETURN_TYPE BufferUtil::Merge(Nan::NAN_METHOD_ARGS_TYPE)':
../src/bufferutil.cc:57:59: warning: 'v8::Local<v8::Value> v8::Object::Get(uint32_t)' is deprecated: Use maybe version [-Wdeprecated-declarations]
       Local<Object> src = Nan::To<v8::Object>(array->Get(i)).ToLocalChecked();
                                                           ^
In file included from /root/.cache/node-gyp/12.13.0/include/node/v8-internal.h:14:0,
                 from /root/.cache/node-gyp/12.13.0/include/node/v8.h:25,
                 from ../src/bufferutil.cc:8:
/root/.cache/node-gyp/12.13.0/include/node/v8.h:3461:51: note: declared here
   V8_DEPRECATED("Use maybe version", Local<Value> Get(uint32_t index));
                                                   ^
/root/.cache/node-gyp/12.13.0/include/node/v8config.h:311:3: note: in definition of macro 'V8_DEPRECATED'
   declarator __attribute__((deprecated(message)))
   ^~~~~~~~~~
  SOLINK_MODULE(target) Release/obj.target/bufferutil.node
  COPY Release/bufferutil.node
  CXX(target) Release/obj.target/validation/src/validation.o
  SOLINK_MODULE(target) Release/obj.target/validation.node
  COPY Release/validation.node
make: Leaving directory '/root/WebSocket-Node/build'

this is the output of :
$ node-gyp rebuild

I need to fix this deprecation warning and then I'm done. Would you mind giving me some pointers about it ? The NAN entry to fix is this one :
Local<Object> src = Nan::To<v8::Object>(array->Get(i)).ToLocalChecked();

Kind Regards

@theturtle32 this should fix the latest deprecation warning:
Local<Object> src = Nan::To<v8::Object>(Nan::Get(array, Nan::New(i)).ToLocalChecked()).ToLocalChecked();

I am ready to submit a pull request if you want. Please double check my final code...

Fixed in release v1.0.31 on npm.


some ideas

lovely, short written, cool menu, i love it and i love that there is no jquery involved:)
some ideas if you dont mind

ability to select where the menu you will show relative to the element, maybe left to it, above it or on top of it, etc..
the scroll demo is cool, but the scroll bars are so large and the menu it self is so narrow

all the best and thanks again for simple awesome work :)

Thanks for the suggestions! :)

I will add some padding to the box if scroll bars are visible. I think that's a good idea.
You can pass custom coordinates to basicContext, but that's currently not documented. The ability to select where the menu shows (e.g. above, left or right) isn't planned.

[ ] Padding when scrollbars visible
[ ] Demo for custom coordinates

:+1:


overrides: adjust custom css

closes https://github.com/inveniosoftware/invenio-communities/issues/929

could you add screenshots ?


Safari Datetime Input Spacing

Space should be even on both sides.

Turns out this was just a design choice that didn't hold up in browsers other than chrome.


Arm's AndroidNN driver does not build for 20.02

Operating System:
Android
Problem description:
AndroidNN driver for Arm that can be found here cannot be built for 20.02 alongside Compute Library.
This is due to a missing build file that should be present in Compute Library's repository.
A maintenance release is in progress as 20.02.1 for Compute Library to include this file and unblock usage of the driver.

Release is out as Maintenance Release 20.02.1
More information can be found here:
https://github.com/ARM-software/ComputeLibrary/releases/tag/v20.02.1


Nested object properties reported as invalid even though parent object is optional.

Note: I'm using tcomb-json-schema to convert a JSON schema to a tcomb object.
Consider an example JSON object describing a person.
{
  "type": "object",
  "properties": {
    "name": {
      "type": "object",
      "required": [ "first", "last" ],
      "properties": {
        "first": {
          "type": "string"
        },
        "middle": {
          "type": "string"
        },
        "last": {
          "type": "string"
        }
      }
    }
  }
}

The name property is optional, but it's first and last properties are required.
Observed behaviour
If first, middle, last are all null, name is reported as
{
  "first": null,
  "middle": null,
  "last": null
}

and it's first and last properties do not pass the validation test (because they are required and null).
Expected behaviour
If first, middle, last are all null, name should pass the validation test (because it's optional).
It is possible to support this kind of behaviour? Where should I start looking into implementing this?

It is possible to support this kind of behaviour?

Optional structs are not supported. The simplest workaround I can think of is using a subtype:
function isValidName(x) {
  return (!t.Nil.is(x.first) && !t.Nil.is(x.last)) || (t.Nil.is(x.first) && t.Nil.is(x.last) && t.Nil.is(x.middle));
}

const Name = t.subtype(t.struct({
  first: t.maybe(t.String),
  middle: t.maybe(t.String),
  last: t.maybe(t.String)
}), isValidName);

const Foo = t.struct({
  name: Name
}, 'Person');

var options = {
  fields: {
    name: {
      error: 'my error message here'
    }
  }
};

Thanks, that looks quite simple.
Does tcomb-json-schema support subtypes and custom validators?

Does tcomb-json-schema support subtypes and custom validators?

No, AFAIK there's not standard for that, but I can be wrong.

@gcanti can you explain a little bit why optional Structs aren't supported?

@VinSpee because of a simple reason: till now I didn't come up with a good idea on how to handle them. Let's talk about this topic, I'm quite interested https://github.com/gcanti/tcomb-form/issues/236


GET request returning all columns but one from my Postgres DB

I'm using $sailsSocket to make my GET and POST requests. My POST request looks like this;
$sailsSocket.post('/schedules/toDateObj',
    { jobSchedObj:
        { repair_shop_equipment_id: response.config.data.schedEquip.rsrcId,
          repair_history_id: response.data.id,
          technician_id: response.data.technician_id,
          allotted_time: response.data.allotted_time,
          times: timeObj,
          repair_shop_id: $localstorage.get('shopId')
          }
      })
      .success(function(){
          $location.path('/app/checkin');
      })
      .error(function (response){
          console.log(response);
      });

And here is the table it saves to...

Everything saves fine I even threw a console.log in my ScheduleController to check what was being inserted in the database with my POST request. Here is the output;

The problem is when I make a GET request to the Schedule table it comes back with everything except repair_shop_equipment_id. Here is the get request;
 var firstDay = scope.getJobsFor[0];
                      var lowerBound = firstDay.open_time;
                      var lastDay = scope.getJobsFor[scope.getJobsFor.length - 1];
                      var upperBound = lastDay.close_time;
                      $sailsSocket.get("/schedules", {params:
                        {where: {
                          repair_shop_id: scope.shopId,
                          technician_id: scope.schedTech.id,
                          repair_shop_equipment_id: scope.schedEquip.rsrcId,
                          scheduled_start_time:{ date: {'>':lowerBound, '<':upperBound}}
                          }
                        }
                      })
                      .success(function (response){

And this is the response...

Here is a link to a Gist with my associated Sails models and the schedule controller;
https://gist.github.com/bmwertman/c9a426674a6e4767cd35
Is there something wrong with one of my model configurations? Thanks.

I've found a way to retrieve the repair_shop_equipment_id with the GET request to '/schedules'. Although it makes zero sense as to why it actually works. I'll explain why;
if I change my GET request as follows it would make at least a bit more sense that repair_shop_equipment_id gets returned with the response;
 var firstDay = scope.getJobsFor[0];
                      var lowerBound = firstDay.open_time;
                      var lastDay = scope.getJobsFor[scope.getJobsFor.length - 1];
                      var upperBound = lastDay.close_time;
                      $sailsSocket.get("/schedules/?populate=repair_shop_equipment_id", {params:
                        {where: {
                          repair_shop_id: scope.shopId,
                          technician_id: scope.schedTech.id,
                          repair_shop_equipment_id: scope.schedEquip.rsrcId,
                          scheduled_start_time:{ date: {'>':lowerBound, '<':upperBound}}
                          }
                        }
                      })
                      .success(function (response){

But when I do this I get this...

...Notice the technician_id changed from an object with property id to simply the value of id and the repair_shop_equipment_id is still not included.
If I make the request like this though;
 var firstDay = scope.getJobsFor[0];
                      var lowerBound = firstDay.open_time;
                      var lastDay = scope.getJobsFor[scope.getJobsFor.length - 1];
                      var upperBound = lastDay.close_time;
                      $sailsSocket.get("/schedules/?populate=technician_id", {params:
                        {where: {
                          repair_shop_id: scope.shopId,
                          technician_id: scope.schedTech.id,
                          repair_shop_equipment_id: scope.schedEquip.rsrcId,
                          scheduled_start_time:{ date: {'>':lowerBound, '<':upperBound}}
                          }
                        }
                      })
                      .success(function (response){

...Notice I'm now asking it to populate with the technician_id
I get back what I wanted all along. And it looks like this;

...See repair_shop_equipment _id is in the response.
But why did I have to ask it to populate technician_id to get repair_shop_equipment_id to come back with the response? Better yet why do I have to pass anything additional with the request to get the entire table row back?


Development deployment does not display images and files

The development deployment does not show speaker images, header images etc. and no files.
Compare: https://wikimania-dev.eventyay.com/wikimania-test/schedule/v/0.4/

fixed by setup read permission for docker volumns folder: chmod 755 /var/lib/docker


Add WPF vs UWP Document

Summary
There are various differences between WPF and UWP when it comes to XAML.
After a session i had just today and digging around someone created a nice list of differences which i updated
a litle bit. This would be some nice content to have in the docs. W

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.:x: DeeJayTC sign nowYou have signed the CLA already but the status is still pending? Let us recheck it.

Thank you for this submission! There are some things to fix which the linter has pointed out. Also, the table content is generally formatted in markdown. I'll contact some UWP folks for review and also put this article through editing. Thanks again!

@DeeJayTC I believe this submission violates rule #3 in the CLA you signed:

Originality of Work. You represent that each of Your Submissions is entirely Your original work. Should You wish to Submit materials that are not Your original work, You may Submit them separately to the Project if You (a) retain all copyright and license information that was in the materials as You received them, (b) in the description accompanying Your Submission, include the phrase "Submission containing materials of a third party:" followed by the names of the third party and any licenses or other restrictions of which You are aware, and (c) follow any other instructions in the Project’s written guidelines concerning Submissions.

@sonnemaf I just noticed that you're the original author on this content submitted by a user. I was erroneously thinking that they were the author. If you're interested in having your list of differences processed and added to the WPF XAML documentation, please let me know and open up a PR.
I'm going to close this PR.

Yea accidently removed the source and license details, had them in my first commit. Never meant to sell it as my own work but really think its useful for a lot of people and should be in docs. :)

No worries!


CentOS 7 has reached EOL, some yum repo sites are offline.

Bug Report
we should update the script to update the yum repo files to workaround the problem.

/label ?

/severity minor


Add logging to dataloading

Currently there is quite some time between the start of the first train_step and first train_inner log update. This is due to the time it takes for the different processes for each gpu to start. Also it takes some time for each of these processes to completely fill their streaming buffer of training examples. This makes it difficult to debug when something hangs or if there are issues with the data loaders.
To solve this I added some logging to the following:

once each process starts filling their buffers (this and starting workers takes the most time)
print out the first batch on the first rank before it enters the model (First point in https://github.com/facebookresearch/metaseq/issues/277)
Start and finish of the first the forward and backward pass.

This is an example log:
2022-10-24 19:19:23 | INFO | metaseq.trainer | nvidia-smi stats: {'gpu_0_mem_used_gb': 16.06640625, 'gpu_1_mem_used_gb': 16.64453125, 'gpu_2_mem_used_gb': 16.62890625, 'gpu_3_mem_used_gb': 3.9892578125}
2022-10-24 19:19:23 | INFO | metaseq.utils | ***********************CUDA enviroments for all 4 workers***********************
2022-10-24 19:19:23 | INFO | metaseq.utils | rank   0: capabilities =  8.0  ; total memory = 39.409 GB ; name = NVIDIA A100-SXM4-40GB
2022-10-24 19:19:23 | INFO | metaseq.utils | rank   1: capabilities =  8.0  ; total memory = 39.409 GB ; name = NVIDIA A100-SXM4-40GB
2022-10-24 19:19:23 | INFO | metaseq.utils | rank   2: capabilities =  8.0  ; total memory = 39.409 GB ; name = NVIDIA A100-SXM4-40GB
2022-10-24 19:19:23 | INFO | metaseq.utils | rank   3: capabilities =  8.0  ; total memory = 39.409 GB ; name = NVIDIA A100-SXM4-40GB
2022-10-24 19:19:23 | INFO | metaseq.utils | ***********************CUDA enviroments for all 4 workers***********************
2022-10-24 19:19:23 | INFO | metaseq.cli.train | training on 4 devices (GPUs/TPUs)
2022-10-24 19:19:23 | INFO | metaseq.cli.train | max tokens per GPU = None and batch size per GPU = 32
2022-10-24 19:19:23 | WARNING | metaseq.checkpoint_utils | Proceeding without metaseq-internal installed! Please check if you need this!
2022-10-24 19:19:23 | INFO | metaseq.cli.train | nvidia-smi stats: {'gpu_0_mem_used_gb': 16.06640625, 'gpu_1_mem_used_gb': 16.64453125, 'gpu_2_mem_used_gb': 16.62890625, 'gpu_3_mem_used_gb': 3.9892578125}
2022-10-24 19:19:23 | WARNING | metaseq.checkpoint_utils | Proceeding without metaseq-internal installed! Please check if you need this!
2022-10-24 19:19:23 | INFO | metaseq.checkpoint_utils | attempting to load checkpoint from: ./test-checkpoint/train.8m.bm_none.gpt2.me_fp16.fsdp.zero2.relu.transformer_lm_megatron.nlay4.emb128.lrnpos.0emb_scale.tps2048.adam.b2_0.95.eps1e-08.cl1.0.lr0.001.endlr0.0001.wu2861.dr0.1.atdr0.1.0emb_dr.wd0.1.ms32.uf1.mu1000.s1.me100.ngpu4/checkpoint_last-model_part-0-shard0.pt
2022-10-24 19:19:23 | WARNING | metaseq.checkpoint_utils | Proceeding without metaseq-internal installed! Please check if you need this!
2022-10-24 19:19:23 | WARNING | metaseq.checkpoint_utils | Proceeding without metaseq-internal installed! Please check if you need this!
2022-10-24 19:19:23 | INFO | metaseq.trainer | No existing checkpoint found ./test-checkpoint/train.8m.bm_none.gpt2.me_fp16.fsdp.zero2.relu.transformer_lm_megatron.nlay4.emb128.lrnpos.0emb_scale.tps2048.adam.b2_0.95.eps1e-08.cl1.0.lr0.001.endlr0.0001.wu2861.dr0.1.atdr0.1.0emb_dr.wd0.1.ms32.uf1.mu1000.s1.me100.ngpu4/checkpoint_last-model_part-0-shard0.pt
2022-10-24 19:19:23 | INFO | metaseq.trainer | loading train data for epoch 1
2022-10-24 19:19:23 | INFO | metaseq.data.jsonl_dataset | Loading up cache: /data/home/peteralbert/repos/sor/metaseq/gpu_tests/circleci/corpus_dedup_10_10_1_0.05_exp29/train/00/BookCorpusFair.jsonl.fairseq.idx.npy
2022-10-24 19:19:23 | INFO | metaseq.tasks.streaming_language_modeling | setting shuffle buffer size to 640
2022-10-24 19:19:23 | INFO | metaseq.trainer | finished creating batch iterator
2022-10-24 19:19:23 | INFO | metaseq.optim.adam | using FusedAdam
2022-10-24 19:19:23 | INFO | metaseq.optim.dynamic_loss_scaler | *** SCALE_WINDOW: 256, loss scale: 4 ***
/fsx/users/peteralbert/conda/envs/sor/lib/python3.8/site-packages/torch/utils/data/dataloader.py:487: UserWarning: This DataLoader will create 4 worker processes in total. Our suggested max number of worker in current system is 1, which is smaller than what this DataLoader is going to create. Please be aware that excessive worker creation might get DataLoader running slow or even freeze, lower the worker number to avoid potential slowness/freeze if necessary.
  warnings.warn(_create_warning_msg(
/fsx/users/peteralbert/conda/envs/sor/lib/python3.8/site-packages/torch/utils/data/dataloader.py:487: UserWarning: This DataLoader will create 4 worker processes in total. Our suggested max number of worker in current system is 1, which is smaller than what this DataLoader is going to create. Please be aware that excessive worker creation might get DataLoader running slow or even freeze, lower the worker number to avoid potential slowness/freeze if necessary.
  warnings.warn(_create_warning_msg(
/fsx/users/peteralbert/conda/envs/sor/lib/python3.8/site-packages/torch/utils/data/dataloader.py:487: UserWarning: This DataLoader will create 4 worker processes in total. Our suggested max number of worker in current system is 1, which is smaller than what this DataLoader is going to create. Please be aware that excessive worker creation might get DataLoader running slow or even freeze, lower the worker number to avoid potential slowness/freeze if necessary.
  warnings.warn(_create_warning_msg(
/fsx/users/peteralbert/conda/envs/sor/lib/python3.8/site-packages/torch/utils/data/dataloader.py:487: UserWarning: This DataLoader will create 4 worker processes in total. Our suggested max number of worker in current system is 1, which is smaller than what this DataLoader is going to create. Please be aware that excessive worker creation might get DataLoader running slow or even freeze, lower the worker number to avoid potential slowness/freeze if necessary.
  warnings.warn(_create_warning_msg(
2022-10-24 19:19:24 | INFO | metaseq.data.document_to_sequence | Begin filling streaming dataset buffer for each worker
2022-10-24 19:19:24 | INFO | metaseq.trainer | begin training epoch 1
2022-10-24 19:19:24 | INFO | metaseq.cli.train | Start iterating over samples
2022-10-24 19:19:36 | INFO | metaseq.trainer | First batch on first rank:
{'id': tensor([192, 400, 417, 370, 468, 483, 259, 407, 405, 369, 463, 239, 434, 253,
        241, 449, 342, 132, 488,  17, 401,  63, 225,  37]), 'net_input': {'src_tokens': tensor([[  212,   282,   449,  ...,  6316, 37653,  1343],
        [  181,   506, 35905,  ..., 10668,  2348,   856],
        [40577,    52,   642,  ...,   605,   939,   219],
        ...,
        [  992,   571,  4122,  ...,  9169,   295, 11483],
        [  267,  2231,    29,  ...,   784,   338,   329],
        [  821, 46106,   462,  ...,   992,   428,  4791]])}, 'target': tensor([[  282,   449,  8628,  ..., 37653,  1343,   605],
        [  506, 35905,   784,  ...,  2348,   856,   438],
        [   52,   642,  1343,  ...,   939,   219,  3662],
        ...,
        [  571,  4122,   910,  ...,   295, 11483,   417],
        [ 2231,    29,   329,  ...,   338,   329,   417],
        [46106,   462,  3988,  ...,   428,  4791, 30461]]), 'nsentences': 32, 'ntokens': tensor(65536)}
2022-10-24 19:19:36 | INFO | metaseq.tasks.base_task | Starting first forward pass and waiting for dataloader in other ranks
2022-10-24 19:20:32 | INFO | metaseq.data.document_to_sequence | Begin filling streaming dataset buffer for each worker
2022-10-24 19:20:32 | INFO | metaseq.data.document_to_sequence | Begin filling streaming dataset buffer for each worker
2022-10-24 19:20:32 | INFO | metaseq.data.document_to_sequence | Begin filling streaming dataset buffer for each worker
2022-10-24 19:21:07 | INFO | metaseq.tasks.base_task | Starting backward pass
2022-10-24 19:21:07 | INFO | metaseq.tasks.base_task | Finished first backward pass
2022-10-24 19:21:08 | INFO | metaseq.logging.progress_bar.base_progress_bar | Setting tensorboard directory to ./test-checkpoint/train.8m.bm_none.gpt2.me_fp16.fsdp.zero2.relu.transformer_lm_megatron.nlay4.emb128.lrnpos.0emb_scale.tps2048.adam.b2_0.95.eps1e-08.cl1.0.lr0.001.endlr0.0001.wu2861.dr0.1.atdr0.1.0emb_dr.wd0.1.ms32.uf1.mu1000.s1.me100.ngpu4/train_inner
2022-10-24 19:21:08 | INFO | train_inner | {"epoch": 1, "actv_norm": "0.109", "pos_norm": "0.068", "tok_norm": "0.096", "emb_norm": "0", "docsperex": "1.78", "loss": "15.623", "ppl": "50462.5", "wps": "0", "ups": "0", "wpb": "131072", "bsz": "64", "num_updates": "1", "lr": "3.49528e-07", "gnorm": "2.969", "clip": "100", "loss_scale": "4", "scale_window": "256", "train_wall": "92", "cuda_gb_allocated": "9.3", "cuda_gb_reserved": "10.6", "cuda_gb_free": "30.1", "wall": "105"}
2022-10-24 19:21:10 | INFO | train_inner | {"epoch": 1, "actv_norm": "0.109", "pos_norm": "0.068", "tok_norm": "0.096", "emb_norm": "0", "docsperex": "1.78", "loss": "15.623", "ppl": "50464.2", "wps": "91888.3", "ups": "0.69", "wpb": "131072", "bsz": "64", "num_updates": "2", "lr": "6.99056e-07", "gnorm": "2.968", "clip": "100", "loss_scale": "4", "scale_window": "256", "train_wall": "1", "cuda_gb_allocated": "9.3", "cuda_gb_reserved": "10.6", "cuda_gb_free": "30.1", "wall": "107"}
2022-10-24 19:21:12 | INFO | train_inner | {"epoch": 1, "actv_norm": "0.109", "pos_norm": "0.068", "tok_norm": "0.096", "emb_norm": "0", "docsperex": "1.78", "loss": "15.623", "ppl": "50462.4", "wps": "94660.1", "ups": "0.72", "wpb": "131072", "bsz": "64", "num_updates": "3", "lr": "1.04858e-06", "gnorm": "2.969", "clip": "100", "loss_scale": "4", "scale_window": "256", "train_wall": "1", "cuda_gb_allocated": "9.3", "cuda_gb_reserved": "10.6", "cuda_gb_free": "30.1", "wall": "109"}
2022-10-24 19:21:13 | INFO | train_inner | {"epoch": 1, "actv_norm": "0.109", "pos_norm": "0.068", "tok_norm": "0.096", "emb_norm": "0", "docsperex": "1.78", "loss": "15.623", "ppl": "50448.4", "wps": "94391.2", "ups": "0.72", "wpb": "131072", "bsz": "64", "num_updates": "4", "lr": "1.39811e-06", "gnorm": "2.968", "clip": "100", "loss_scale": "4", "scale_window": "256", "train_wall": "1", "cuda_gb_allocated": "9.3", "cuda_gb_reserved": "10.6", "cuda_gb_free": "30.1", "wall": "110"}
2022-10-24 19:21:15 | INFO | train_inner | {"epoch": 1, "actv_norm": "0.109", "pos_norm": "0.068", "tok_norm": "0.096", "emb_norm": "0", "docsperex": "1.77", "loss": "15.622", "ppl": "50418.5", "wps": "95332.7", "ups": "0.73", "wpb": "131072", "bsz": "64", "num_updates": "5", "lr": "1.74764e-06", "gnorm": "2.98", "clip": "100", "loss_scale": "4", "scale_window": "256", "train_wall": "1", "cuda_gb_allocated": "9.3", "cuda_gb_reserved": "10.6", "cuda_gb_free": "30.1", "wall": "112"}
2022-10-24 19:21:17 | INFO | train_inner | {"epoch": 1, "actv_norm": "0.109", "pos_norm": "0.068", "tok_norm": "0.096", "emb_norm": "0", "docsperex": "1.77", "loss": "15.621", "ppl": "50387.8", "wps": "96668.7", "ups": "0.74", "wpb": "131072", "bsz": "64", "num_updates": "6", "lr": "2.09717e-06", "gnorm": "2.98", "clip": "100", "loss_scale": "4", "scale_window": "256", "train_wall": "1", "cuda_gb_allocated": "9.3", "cuda_gb_reserved": "10.6", "cuda_gb_free": "30.1", "wall": "114"}

Yay logging!
Curious: what's going on between
2022-10-24 19:19:24 | INFO | metaseq.data.document_to_sequence | Begin filling streaming dataset buffer for each worker
...

and the following few:
2022-10-24 19:20:32 | INFO | metaseq.data.document_to_sequence | Begin filling streaming dataset buffer for each worker
2022-10-24 19:20:32 | INFO | metaseq.data.document_to_sequence | Begin filling streaming dataset buffer for each worker
2022-10-24 19:20:32 | INFO | metaseq.data.document_to_sequence | Begin filling streaming dataset buffer for each worker

Either way, more logs == more weirdness to dig into 😅

Yay logging!
Curious: what's going on between
2022-10-24 19:19:24 | INFO | metaseq.data.document_to_sequence | Begin filling streaming dataset buffer for each worker
...

and the following few:
2022-10-24 19:20:32 | INFO | metaseq.data.document_to_sequence | Begin filling streaming dataset buffer for each worker
2022-10-24 19:20:32 | INFO | metaseq.data.document_to_sequence | Begin filling streaming dataset buffer for each worker
2022-10-24 19:20:32 | INFO | metaseq.data.document_to_sequence | Begin filling streaming dataset buffer for each worker

Either way, more logs == more weirdness to dig into 😅

😅 So I think these are the data loaders for each gpu. The first one should run on the main process and the others are therefore a bit delayed, so I think it's useful to see them as well. You are right that repeating the same message is confusing. I added their rank, which makes it clearer.
2022-10-24 20:38:00 | INFO | metaseq.data.document_to_sequence | Begin filling streaming dataset buffer for each worker on rank 0
2022-10-24 20:38:00 | INFO | metaseq.trainer | begin training epoch 1
2022-10-24 20:38:00 | INFO | metaseq.cli.train | Start iterating over samples
2022-10-24 20:38:14 | INFO | metaseq.trainer | First batch on first rank: {'id': tensor([192, 400, 417, 370, 468, 483, 259, 407, 405, 369, 463, 239, 434, 253,
        241, 449, 342, 132, 488,  17, 401,  63, 225,  37]), 'net_input': {'src_tokens': tensor([[  212,   282,   449,  ...,  6316, 37653,  1343],
        [  181,   506, 35905,  ..., 10668,  2348,   856],
        [40577,    52,   642,  ...,   605,   939,   219],
        ...,
        [  992,   571,  4122,  ...,  9169,   295, 11483],
        [  267,  2231,    29,  ...,   784,   338,   329],
        [  821, 46106,   462,  ...,   992,   428,  4791]])}, 'target': tensor([[  282,   449,  8628,  ..., 37653,  1343,   605],
        [  506, 35905,   784,  ...,  2348,   856,   438],
        [   52,   642,  1343,  ...,   939,   219,  3662],
        ...,
        [  571,  4122,   910,  ...,   295, 11483,   417],
        [ 2231,    29,   329,  ...,   338,   329,   417],
        [46106,   462,  3988,  ...,   428,  4791, 30461]]), 'nsentences': 32, 'ntokens': tensor(65536)}
2022-10-24 20:38:14 | INFO | metaseq.tasks.base_task | Starting first forward pass and waiting for dataloader in other ranks
2022-10-24 20:39:24 | INFO | metaseq.data.document_to_sequence | Begin filling streaming dataset buffer for each worker on rank 3
2022-10-24 20:39:24 | INFO | metaseq.data.document_to_sequence | Begin filling streaming dataset buffer for each worker on rank 1
2022-10-24 20:39:24 | INFO | metaseq.data.document_to_sequence | Begin filling streaming dataset buffer for each worker on rank 2
2022-10-24 20:40:04 | INFO | metaseq.tasks.base_task | Starting backward pass
2022-10-24 20:40:04 | INFO | metaseq.tasks.base_task | Finished first backward pass


Add capability to send collapsed groups (isExpanded=false flag, for dxDataGrid)

Also, remote grouping enabled in Sample site
/cc @IlyaKhD

:shipit:


Measure serializer does not include target_date

Added to Serializer but Codeship Failed
https://github.com/dumparkltd/hr-nmrf-server/pull/215


Use Lograge for flipper logs

I have my rails logger configured with lograge JSON output which plays nicely with Datadog. However, my flipper logs are still showing up in the default format, e,g.:
[1mFlipper feature(my_flag) enabled? true (0.0ms)  [ actors=[#<Flipper::Types::Actor:0x01107f8711517018 @actor=#<MyValidation::Foo:0x00107187111f3110<EMAIL_ADDRESS><EMAIL_ADDRESS>gate_name=boolean ]

While all my controller logs show up nicely in JSON. I tried configuring flipper to use the Rails logger in config/production.rb:
  # Use the rails logger in flipper
  config.flipper.logger = Rails.logger

I think you'll need to turn logging off (source). You can do this in config/application.rb:
config.flipper.log = false

Then, you'll need a new log subscriber like our default one (just copy and tweak it to output json instead of default stuff).
If you wanted to make a json one I'd be happy to merge it in flipper proper. Once that is done, you'll just need to attach it like we do (here and here) with the default one.

Thanks @jnunemaker! I'll try this out.


CI does not test OpenCL builds on Windows

appveyor.yml does not set the config option OPENCL when configuring the builds and since the MSVC build pays attention to it, CI Windows compiles will never test the OpenCL code. Due to #289 OpenCL code is tested on non-MSVC platforms.

Got it - will fix. Thanks!


fix(BDropdownItem): add attrs when no to props is present

fixes #1048

I thought it was a bit suspicious that an attribute wouldn't just fall through :thinking:


Add cv.tomy.me

This PR is:

[x] Adding a new domain
[ ] Updating existing domain size
[ ] Changing domain name
[ ] Removing existing domain from list
[ ] Website code changes (512kb.club site)
[ ] Other not listed

[x] I used the uncompressed size of the site
[x] I have included a link to the Cloudflare report
[x] This site is not an ultra lightweight site
[x] The following information is filled identical to the data file

I confirm that I have read the FAQ section, particularly the two red items around minimal pages and inappropriate content and I attest that this site is neither of these things.

[x] Check to confirm

- domain: cv.tomy.me
  url: https://cv.tomy.me
  size: 55
  last_checked: 2024-01-24

Cloudflare Report: https://radar.cloudflare.com/scan/07c3e42f-4b2b-495b-8192-b449d8775c72/summary

Thanks!


Added model.eval() and torch.no_grad() to disable dropout/gradient calculation during inference

Referencing #13
Simply put, I was getting different predictions for the same SMILE input, turns out this additional resolved that issue.

Had to undo the other changes to put a PR for 1 change at a time.

I did not re-train the model as we changed our focus for now... but during
inference there was a +/- difference of 0.3-0.4 on the single ESOL
predictions. I'll report back once I get on this.
On Wed, Nov 30, 2022 at 6:55 PM Esben Jannik Bjerrum <
@.***> wrote:

Nice find. How bad did it affect the overall metrics? e.g. R2, RMSE?
—
Reply to this email directly, view it on GitHub
https://github.com/MolecularAI/Chemformer/pull/17#issuecomment-1332150749,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AHRKOA7YPUOJSYVO2OUDTK3WK5IVHANCNFSM6AAAAAASIEB77U
.
You are receiving this because you authored the thread.Message ID:
@.***>


Fixed # fixed string concatation in loop.

Motivation
String is immutable objects and will affect performance when connected in a loop.

Did you see some measurable improvement?
I am saying this because recently JVM handle string concatenation better that using StringBuilder in same cases and forcing a concatenation strategy sometimes it is not the best option.
That said I am not against this change, but I just want to know if this is the result of some static code analysis or it is fixing a real problem. You know the motto 'don't fix things that are not broken

Thanks for your suggestion, Could you provide me with some material on how the JVM improves the performance of string concatenation? I didn't find it~

Did you see some measurable improvement?
I am saying this because recently JVM handle string concatenation better that using StringBuilder in same cases and forcing a concatenation strategy sometimes it is not the best option.
That said I am not against this change, but I just want to know if this is the result of some static code analysis or it is fixing a real problem. You know the motto 'don't fix things that are not broken

Yes, I test it in a small example. when you use a string connection inline, the JVM will translate it to StringBuilder and invoke the append method to handle it.
the bytecode is as follows:
 L0     LINENUMBER 6 L0     LDC "abc"     ASTORE 1    L1     LINENUMBER 7 L1     NEW java/lang/StringBuilder     DUP     INVOKESPECIAL java/lang/StringBuilder.<init> ()V     ALOAD 1     INVOKEVIRTUAL java/lang/StringBuilder.append (Ljava/lang/String;)Ljava/lang/StringBuilder;     LDC "d"     INVOKEVIRTUAL java/lang/StringBuilder.append (Ljava/lang/String;)Ljava/lang/StringBuilder;     INVOKEVIRTUAL java/lang/StringBuilder.toString ()Ljava/lang/String;     ASTORE 1    L2     LINENUMBER 10 L2     GETSTATIC java/lang/System.out : Ljava/io/PrintStream;     ALOAD 1     INVOKEVIRTUAL java/io/PrintStream.println (Ljava/lang/String;)V    L3     LINENUMBER 11 L3     RETURN    L4     LOCALVARIABLE args [Ljava/lang/String; L0 L4 0     LOCALVARIABLE a Ljava/lang/String; L1 L4 1     MAXSTACK = 2     MAXLOCALS = 2

Did you see some measurable improvement?
I am saying this because recently JVM handle string concatenation better that using StringBuilder in same cases and forcing a concatenation strategy sometimes it is not the best option.
That said I am not against this change, but I just want to know if this is the result of some static code analysis or it is fixing a real problem. You know the motto 'don't fix things that are not broken

But if you try to connect String in a loop, they will create a lot of StringBuilder Object.
the bytecode is as follows:
 L0
    LINENUMBER 6 L0
    LDC "abc"
    ASTORE 1
   L1
    LINENUMBER 7 L1
    ICONST_0
    ISTORE 2
   L2
   FRAME APPEND [java/lang/String I]
    ILOAD 2
    BIPUSH 10
    IF_ICMPGE L3
   L4
    LINENUMBER 8 L4
    NEW java/lang/StringBuilder
    DUP
    INVOKESPECIAL java/lang/StringBuilder.<init> ()V
    ALOAD 1
    INVOKEVIRTUAL java/lang/StringBuilder.append (Ljava/lang/String;)Ljava/lang/StringBuilder;
    LDC "d"
    INVOKEVIRTUAL java/lang/StringBuilder.append (Ljava/lang/String;)Ljava/lang/StringBuilder;
    INVOKEVIRTUAL java/lang/StringBuilder.toString ()Ljava/lang/String;
    ASTORE 1
   L5
    LINENUMBER 7 L5
    IINC 2 1
    GOTO L2
   L3
    LINENUMBER 10 L3
   FRAME CHOP 1
    GETSTATIC java/lang/System.out : Ljava/io/PrintStream;
    ALOAD 1
    INVOKEVIRTUAL java/io/PrintStream.println (Ljava/lang/String;)V
   L6
    LINENUMBER 11 L6
    RETURN
   L7
    LOCALVARIABLE i I L2 L3 2
    LOCALVARIABLE args [Ljava/lang/String; L0 L7 0
    LOCALVARIABLE a Ljava/lang/String; L1 L7 1
    MAXSTACK = 2
    MAXLOCALS = 3

@mattisonchao I am pretty sure that this code is not for JDK11.
when you build this code with JDK11 with target = 11 the result will be very different.
btw we are still building Pulsar for JDK8, so the change is good for me

@mattisonchao I am pretty sure that this code is not for JDK11.
when you build this code with JDK11 with target = 11 the result will be very different.
btw we are still building Pulsar for JDK8, so the change is good for me

Sorry, It's my mistake.
I re-run the code using Java 15 and its bytecode is as follows.
// class version 59.0 (59)
// access flags 0x21
public class Test {

  // compiled from: Test.java
  // access flags 0x19
  public final static INNERCLASS java/lang/invoke/MethodHandles$Lookup java/lang/invoke/MethodHandles Lookup

  // access flags 0x1
  public <init>()V
   L0
    LINENUMBER 1 L0
    ALOAD 0
    INVOKESPECIAL java/lang/Object.<init> ()V
    RETURN
   L1
    LOCALVARIABLE this LTest; L0 L1 0
    MAXSTACK = 1
    MAXLOCALS = 1

  // access flags 0x9
  public static main([Ljava/lang/String;)V
   L0
    LINENUMBER 3 L0
    LDC "abc"
    ASTORE 1
   L1
    LINENUMBER 4 L1
    ICONST_0
    ISTORE 2
   L2
   FRAME APPEND [java/lang/String I]
    ILOAD 2
    BIPUSH 8
    IF_ICMPGE L3
   L4
    LINENUMBER 5 L4
    ALOAD 1
    INVOKEDYNAMIC makeConcatWithConstants(Ljava/lang/String;)Ljava/lang/String; [
      // handle kind 0x6 : INVOKESTATIC
      java/lang/invoke/StringConcatFactory.makeConcatWithConstants(Ljava/lang/invoke/MethodHandles$Lookup;Ljava/lang/String;Ljava/lang/invoke/MethodType;Ljava/lang/String;[Ljava/lang/Object;)Ljava/lang/invoke/CallSite;
      // arguments:
      "\u0001d"
    ]
    ASTORE 1
   L5
    LINENUMBER 4 L5
    IINC 2 1
    GOTO L2
   L3
    LINENUMBER 7 L3
   FRAME CHOP 1
    RETURN
   L6
    LOCALVARIABLE i I L2 L3 2
    LOCALVARIABLE args [Ljava/lang/String; L0 L6 0
    LOCALVARIABLE str Ljava/lang/String; L1 L6 1
    MAXSTACK = 2
    MAXLOCALS = 3
}

@mattisonchao I am pretty sure that this code is not for JDK11.
when you build this code with JDK11 with target = 11 the result will be very different.
btw we are still building Pulsar for JDK8, so the change is good for me

You are right. The JVM handles string concatenation better than using StringBuilder in some cases.
The doc is here: https://docs.oracle.com/javase/9/docs/api/java/lang/invoke/StringConcatFactory.html#makeConcat-java.lang.invoke.MethodHandles.Lookup-java.lang.String-java.lang.invoke.MethodType-

Finally, thank you for your suggestions. My friend ~ @eolivelli   👍


Implement JWT Authentication

Description:
Considering the growing security concerns and the need for scalability, it's imperative to implement JSON Web Token (JWT) authentication.
Objective:
The primary objective of this issue is to enhance the security, scalability, and user experience by implementing JWT as a main authentication method.
Benefits of JWT Authentication:

Enhanced Security: JWTs provide digital signature ensuring data integrity and authenticity, mitigating risks associated with common security threats like CSRF and XSS.
Scalability: JWTs being stateless eliminate the need for server-side session management, improving scalability, crucial for a rapidly growing platform.
Improved Performance: JWTs being self-contained and compact can be transmitted efficiently over network requests, reducing latency and improving overall performance.

Implementation Plan:

Integration with Authentication Service: Integrate AutoEye with an authentication service capable of issuing JWTs upon successful authentication, supporting industry-standard algorithms for token signing and verification.
Token Generation and Validation Middleware: Implement middleware to generate JWTs upon user authentication and validate incoming JWTs for protected routes, enforcing token expiration, signature verification, and other security checks.
Secure Token Storage: Ensure secure storage of JWTs on the client-side, using HttpOnly cookies for web applications and secure keychain storage for mobile applications. Implement mechanisms for token revocation and renewal to mitigate token misuse.

Acceptance Criteria:

JWT authentication is successfully implemented across all components of AutoEye.
Integration with the chosen authentication service is seamless, and JWTs are issued upon user authentication.
Middleware for token generation and validation enforcement is functioning correctly.
Secure storage mechanisms for JWTs are implemented and tested.

Additional Information:

This issue is critical for ensuring the security and scalability of AutoEye.


Design Tweaks to Bundles

This PR also adds an option to drag bundle items across bundles!
This PR is a draft

@yaichenbaum ready for review!


remove FnBox since it's deprecated

FnBox is deprecated since 1.35(#28796)
Just removed FnBox instances.

Thanks @rajasekarv!


RedisLocalChannelLayer ipc layer configuration

There is no possibility to pass "message_memory" and "group_memory" settings to internally used ipc layer when using RedisLocalChannelLayer

You're very right, there is not - it's probably the case that the local layer should take a dict to pass down to the IPC layer for its config.

LocalLayer is now gone as of version 2.0, so closing.


vsr: state sync performance improvements

Summary
This PR improves the performance of state sync (specifically, the syncing of table blocks) using non-intrusive optimizations and configuration changes. Using some simple observations, we were able to improve the time that it takes to sync a ~86G data file from 13095 seconds (~218 minutes) → 869s (~14.5 minutes).
These numbers are from running the following simple experiment on a 3-node TB cluster on t2.large AWS instances:

Start R1, R2, but not R0
Run tigerbeetle benchmark with transfer_count=150,000,000, wait for it to finish
Start R0, measure time taken to sync all the content with R1 & R2's help

Optimizations
Here are the optimizations that we implemented:

Commit pipeline (and thereby compaction) paused till content is synced: The motivation behind pausing the commit pipeline (and thereby compaction) is that we observed a lot of error(grid): 0: invalid_checksum: expected address=X checksum=Y, found address=0 checksum=0 while table blocks were being synced. This is because compaction tries to read index/data blocks, finds them empty, and queues the block(s) for repair. During state sync, reading a block (and incurring extraneous IO) is a rather roundabout way to to discover that a block needs to synced, when in fact sync_enqueue_tables is already doing the same without incurring IO.
Proactive request_blocks: Inspired by  this optimization that we have for request_prepares), we now proactively send request_blocks before the next timeout, in case the syncing replica has enough write iops.
Increasing grid_missing_tables_max from 3 → 6: Increases the # of tables that are concurrently synced

Here is the performance improvement that each of the aforementioned optimizations brings:
No optimizations
ubuntu@ip-172-31-3-11:~/tigerbeetle$ cat replica0.vopr | grep "sync: ops\|sync_enqueue_tables\|lagging"
warning(replica): 0: on_start_view: start sync; lagging behind cluster (op_prepare_max=999 quorum_head=18420)
info(replica): 0: sync: ops=0..18271
info(replica): 0: sync_enqueue_tables: all tables synced (commit=0..18271) in 13095s

Compaction Freeze:
ubuntu@ip-172-31-3-11:~/tigerbeetle$ cat replica0.vopr | grep "sync: ops\|sync_enqueue_tables: \|lagging"
warning(replica): 0: on_start_view: start sync; lagging behind cluster (op_prepare_max=999 quorum_head=18420)
info(replica): 0: sync: ops=0..18271
info(replica): 0: sync_enqueue_tables: all tables synced (commit=0..18271) in 11034s

Compaction Freeze + Proactive request_blocks
ubuntu@ip-172-31-3-11:~/tigerbeetle$ cat replica0.vopr | grep "sync: ops\|sync_enqueue_tables: \|lagging"
warning(replica): 0: on_start_view: start sync; lagging behind cluster (op_prepare_max=999 quorum_head=18420)
info(replica): 0: sync: ops=0..18271
info(replica): 0: sync_enqueue_tables: all tables synced (commit=0..18271) in 1054s

Compaction Freeze + Proactive request_blocks + grid_missing_tables_max: 3 → 6
ubuntu@ip-172-31-3-11:~/tigerbeetle$ cat replica0.vopr | grep "sync: ops\|sync_enqueue_tables\|lagging"
warning(replica): 0: on_start_view: start sync; lagging behind cluster (op_prepare_max=999 quorum_head=18420)
info(replica): 0: sync: ops=0..18271
info(replica): 0: sync_enqueue_tables: all tables synced (commit=0..18271) in 869s

From https://github.com/tigerbeetle/tigerbeetle/actions/runs/10362913189/job/28685691012?pr=2207, realized that a few replica tests which test state sync assert that the syncing replica is also able to commit while tables are being synced. We changed this in https://github.com/tigerbeetle/tigerbeetle/pull/2207/commits/971090d9cd790abdd52be75306b832661325717f, wherein we pause then commit pipeline before tables are synced. Before changing all replica tests to reflect this new behaviour, I want to do one more experiment, where we don't pause the commit pipeline, but we do apply the other two optimizations (Proactive request_blocks + grid_missing_tables_max: 3 → 6). If the effect of pausing commit pipeline is negligible in the presence of the other two optimizations, we can get away with not changing this behavior at all.

Re https://github.com/tigerbeetle/tigerbeetle/pull/2207#issuecomment-2285271858: Hunch confirmed! The benefits of pausing the commit pipeline are indeed diminished by the other two optimizations. We're still able to sync in 806s. So, we can get continue to embrace the concurrency here! I will remove https://github.com/tigerbeetle/tigerbeetle/pull/2207/commits/971090d9cd790abdd52be75306b832661325717f.
ubuntu@ip-172-31-3-11:~/tigerbeetle$ cat replica0.vopr | grep "sync: ops\|sync_enqueue_tables: \|lagging"
info(replica): 0: sync: ops=0..18271
warning(replica): 0: on_repair_sync_timeout: request sync; lagging behind cluster (op_head=18320 commit_min=18239 commit_max=18320 commit_stage=idle)
info(replica): 0: sync_enqueue_tables: all tables synced (commit=0..18271) in 806s

cc: @matklad @jorangreef

To get a feel of whether we're close to line rate (the global maxima for the performance we can achieve), we compare our performance with rsync. cc: @jorangreef
Result
To sync ~52.5G worth of data blocks, state sync takes 806 seconds (https://github.com/tigerbeetle/tigerbeetle/pull/2207#issuecomment-2286193309), while rsync takes 628.89 seconds.
Details
In the process of syncing a ~86G data file, the syncing replica repaired a total of 107432 blocks, i.e. ~52.5G worth of blocks. This takes 806 seconds (https://github.com/tigerbeetle/tigerbeetle/pull/2207#issuecomment-2286193309).
ubuntu@ip-172-31-3-11:~/tigerbeetle$ cat replica0.vopr | grep "on_block" | wc -l
107432

rsync-ing the ~56G data file from R1 → R2, where R2 doesn't have any data file takes 640 seconds (628.89 seconds if we extrapolate the bandwidth rsync gets to ~52.5G):
ubuntu@ip-172-31-3-127:~/tigerbeetle$ rsync -avmPz -e "ssh -i chaitanyabhandari.pem" data.tigerbeetle ubuntu@<IP_ADDRESS>:/home/ubuntu/tigerbeetle/data.tigerbeetle
building file list ...
1 file to consider
data.tigerbeetle
 56,074,723,328 100%   83.48MB/s    0:10:40 (xfr#1, to-chk=0/1)

sent 17,954,925,730 bytes  received 35 bytes  27,988,972.35 bytes/sec
total size is 56,074,723,328  speedup is 3.12

To get a feel of whether we're close to line rate (the global maxima for the performance we can achieve), we compare our performance with iperf:
Result
To sync ~52.5G worth of data blocks, state sync takes 806 seconds (https://github.com/tigerbeetle/tigerbeetle/pull/2207#issuecomment-2286193309), while rsync takes 701 seconds.
Machine Specifications
These experiments were conducted on t2.large instances with 8G RAM and 2 cores:
ubuntu@ip-172-31-3-127:~/tigerbeetle$ free -mh
               total        used        free      shared  buff/cache   available
Mem:           7.8Gi       3.6Gi       167Mi       940Ki       4.3Gi       4.2Gi
Swap:             0B          0B          0B

ubuntu@ip-172-31-3-127:~/tigerbeetle$ lscpu
Architecture:             x86_64
  CPU op-mode(s):         32-bit, 64-bit
  Address sizes:          46 bits physical, 48 bits
                          virtual
  Byte Order:             Little Endian
CPU(s):                   2
  On-line CPU(s) list:    0,1
Vendor ID:                GenuineIntel
  Model name:             Intel(R) Xeon(R) CPU E5-26
                          86 v4 @ 2.30GHz
    CPU family:           6
    Model:                79
    Thread(s) per core:   1
    Core(s) per socket:   2

Details
In the process of syncing a ~86G data file, the syncing replica repaired a total of 107432 blocks, i.e. ~52.5G worth of blocks.