Clarification on Fine-Tuning with Special Tokens (e.g., ) in Evo Model

Hello,
In the paper, it states: "During pretraining, Evo uses an effective vocabulary of four tokens, one per base, from a total vocabulary of 512 characters. We use the additional characters to enable prompting with special tokens during generation with fine-tuned models."
I wanted to clarify the fine-tuning approach, particularly for the CRISPR-Cas application. Did you append prompt tokens like  or  to their respective sequences, e.g., ATAGCA...? If so, were the prompt tokens (e.g., <, c, a, s, 9, >) already part of the 512-character vocabulary, or did you need to expand or retrain the model to include these new tokens?
I’m also curious whether the model would need to learn how to handle these characters during fine-tuning, since they were not part of the sequences used in pretraining.
Thank you!

We prepended a special token already in the vocab during finetuning. For cas, these are:
CAS_ID_TO_START_TOKEN = {
    'Cas9': '`',
    'Cas12': '!',
    'Cas13': '@',
}

The model did not see these during pretraining but did see them (only in the first char position) during finetuning!


Error occurs during quantization usingTFLiteConvert.

1. System information

Linux Ubunut 20.04
pip install tensorflow==2.6.0
pip install tensorflow_model_optimization==0.7.0

2. Code
https://colab.research.google.com/drive/1kOgZevD3dkM0hxehTh8vNOW_1zXW4VDE?usp=sharing
3. Failure after conversion
error: 'tfl.max_pool_2d' op quantization parameters violate the same scale constraint: !quant.uniform<i8:f32, 0.010792325524722828> vs. !quant.uniform<i8:f32, 0.0039215686274509803:-128>
(failure on converting)
5. (optional) Any other info / logs
I build two very similar models, but one is successfully converted to quantized model, while other is failed.
Same with avgpool instead of maxpool
There was a  similar issue  #46754 (https://github.com/tensorflow/tensorflow/issues/46754),
but I think concat isn't problem because one of my model including concat works.
Thank you

Hi @jooho-enerzai! This issue is replicating in TF 2.5 and 2.6 , but seems to be resolved in Nightly version. Thanks!


[FLINK-34324][test] Makes all s3 related operations being declared and called in a single location

What is the purpose of the change

Fixes error message in test execution
unifies S3-related code in one location

Brief change log

Moves the entire s3-related logic into the if block

Verifying this change
This change is a trivial rework / code cleanup without any test coverage.
Does this pull request potentially affect one of the following parts:

Dependencies (does it add or upgrade a dependency): no
The public API, i.e., is any changed class annotated with @Public(Evolving): no
The serializers: no
The runtime per-record code paths (performance sensitive): no
Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Kubernetes/Yarn, ZooKeeper: no
The S3 file system connector: no

Documentation

Does this pull request introduce a new feature? no
If yes, how is the feature documented? not applicable

@flinkbot run azure

Closing this one becaue there are still issues.


[Snyk] Security upgrade fast-xml-parser from 4.2.7 to 4.4.1

Snyk has created this PR to fix 1 vulnerabilities in the npm dependencies of this project.
Snyk changed the following file(s):

package.json
package-lock.json

Vulnerabilities that will be fixed with an upgrade:

Issue
Score

Regular Expression Denial of Service (ReDoS) SNYK-JS-FASTXMLPARSER-7573289
  631

[!IMPORTANT]

Check the changes in this PR to ensure they won't cause issues with your project.
Max score is 1000. Note that the real score may have changed since the PR was raised.
This PR was automatically created by Snyk using the credentials of a real user.

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.
For more information:
🧐 View latest project report
📜 Customise PR templates
🛠 Adjust project settings
📚 Read about Snyk's upgrade logic

Learn how to fix vulnerabilities with free interactive lessons:
🦉 Regular Expression Denial of Service (ReDoS)

 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.You have signed the CLA already but the status is still pending? Let us recheck it.

fixed in #120, recommend this PR be closed!


Add a setting controller

In the setting controller, users are able to make changes regarding the position and size of the model as well as the background color. These information, RGB value of the background color, position and size of the model will also be displayed in the same controller for reference.
These changes will be saved automatically. Closing and reopening the App will not clear the last changing result.

pretty nice🔊🥰 thank you🌷


Integrate GMU and other boundaries into the tool as map layers?

Can we overlay GMUs or other boundaries into the app in an elegant way?
Alternatively, what about integrating GMUs and other boundaries from our GVV here, so it's more complete (like NCR)?

More notes from Micah:

I am trying to think from the perspective of a user -- like someone who is trying to see what the smoke outlook looks like in the GMU they were thinking of going to or deciding if they want to get a harvest ticket in this or that GMU based on fire and smoke activity.  In that same vein, adding in the ability to search for other boundaries like in NCR would be great.  I'm thinking of people trying to plan a backpacking/packrafting trip in Gates of the Arctic and they have a couple different areas they could hit based on where the smoke isn't as bad.


NWO: All version numbers should be tagged (automatically or manually)

Proposal: All version numbers should be tagged
Author: Felix fontein <@felixfontein>
Date: 2020-05-21

Status: New
Proposal type: NWO, process
Targeted release: 2.10
Associated PR: automatic tagging for version_added in ansible/ansible#69631, full PR implementing this proposal on ansible-base side in ansible/ansible#69680
Estimated time to implement: 1-2 weeks
(less if the main changes to ansible-base are meant, more when the time needed to adjust all collections is counted)

Motivation
In the NWO, both ansible-base (ansible.builtin) and collections have version numbers. If a feature is added, deprecated, or removed, it should be clear in which version of which collection this happen(s/ed).
Example 1: module test in collection foo.bar uses files doc fragment. Option attributes (from files) says version_added: 2.3, while foo.bar has version 1.0.0. Users reading this in the docs are confused.
Example 2: doc fragment in module_utils in foo.bar deprecates an existing option baz, to be removed in version 2.0.0 of foo.bar. The module stuff from foo.fancy uses the doc fragment and module_utils from foo.bar. When a user runs foo.facy.stuff with this option, a deprecation warning This option will be removed in version 2.0.0 will be printed. Since foo.fancy has version 2.5.1, the user is confused.
Problems
Make it clear to users in documentation and deprecation warnings which collection is talked about. The user does not know that option attributes of foo.bar.test comes from ansible.builtin, or that the option in foo.fancy.stuff is deprecated because it comes from the foo.bar collection.
A more detailled writeup: https://github.com/ansible/community/wiki/Version-numbers-for-documentation-deprecation-removal-in-the-collection-world
Solution proposal

All versions shown to the user should either belong to the current collection where the module/plugin/... belongs to, or should indicate which collection the version number belongs to.
The condensed output (ansible-doc) would be ansible.builtin:2.10 or community.general:1.3.0; the HTML docs output could be Added in Ansible-base 2.10 or Added in community.general 1.3.0.
For version_added, the collection name can be tracked automatically: version_added is added in plugin or module docs, and in doc fragments. Since Ansible knows where each fragment is loaded from, the loading code can tag all version_added values.

new_option:
    description: '...'
    version_added: 1.3.0  # no need to tag, Ansible knows this is in collection foo.bar

Deprecations for plugin options are done in documentation and doc fragments as well. These should also be tagged automatically.
All deprecation version numbers (except plugin/module deprecation) that are handled in code - that is display.deprecated() calls, module.deprecate() calls, removed_in_version and deprecated_aliases.version in module argument spec - must be passed explicitly tagged version numbers:

argument_spec = dict(
    old_option=dict(type='str', removed_in_version='foo.bar:2.0.0'),
    option_with_old_alias(type='str', aliases=['optionwitholdalias'],
                          deprecated_aliases=[dict(name='optionwitholdalias', version='foo.bar:3.0.0')]),
)
module.deprecate('Passing rabbits is deprecated', version='foo.baz:4.0.0')
display.deprecated('This will stop working', version='ansible.builtin:2.13')

This labelling in code has to be done in ansible-base (ansible.builtin) and in all collections.

Testing (optional)
ansible-test can validate some of these:

In validate-modules, it can ensure that version numbers use the correct format if they appear in the documentation or in the module argument spec. I.e. it can check whether the tag is there, and when the tag is there, make sure that collection versions follow the semantic versioning version number definition, and for Ansible versions that they are parsable by StrictVersion.
A pylint plugin can check all module.deprecate() and display.deprecation() calls, and ensure that they add the correct tags and that the verison number is correct (assuming that the version is passed as a literal in the call).

Documentation (optional)
This requires updating the dev guide, so that people know how to tag version numbers, and it should be announced in ansible/community#346 and ansible-collections/overview#45 so that module/plugin and collection maintainers know about this.
Anything else?
Q: Why not label all version numbers (i.e. also the ones appearing in documentation and doc fragments)?
A: For two reasons:

Most version numbers which are used are version_added. Deprecations do not happen very often. So the task that happens most (adding version_added) is not complicated unnecessarily, while the task that is made more complicated doesn't happen very often.
I would prefer all versions to be tagged automatically, but unfortunately for deprecation done by code this is not feasible. So let's automatically tag as much as possible.

Q: Isn't this a lot of work (to tag all version numbers in code)?
A: I think it is not that much work:

Deprecation doesn't happen that often.
Currently existing deprecations outside ansible-base have to be adjusted anyway, since these currently in most cases still use Ansible version numbers (due to migration). If this proposal is through before everyone updated these version numbers, it will be almost no extra work.
I'm volunteering to do the work for community.general and community.network. That's probably the largest batch. :)

Q: Isn't this making forking collections (copying them and releasing them under a new name) more complicated?
A: Not much: right now you already have to adjust many places where the collection name is imprinted, and usually a global search-and-replace with some manual post-processing (verify all changes) does the job fine. Since deprecations don't happen too often, this should not increase the amount of work by much.

I've updated the PR (ansible/ansible#69680) to also require that removed_at_date and deprecated_aliaes.date are tagged (these are also generated by code). These date-based deprecations have been added in ansible/ansible#68177.

ansible/ansible#69680 has been merged, so this now works.

Was the intention for the version_added to allow for specifying the collection? For example:
    ask_inventory:
      description:
        - Prompt user for inventory on launch.
      type: bool
      version_added: "ansible.builtin:2.9"

The collection didn't introduce the option, it was carried over from Ansible 2.9. Likewise, if someone did fork a collection, the version numbers would be wrong unless the new collection backdated version or something, which would be meaningless anyway.
Right now this gets the invalid semantic version error, saying it got awx.awx:ansible.builtin:2.9, so it appends the collection name onto the front.

No, that's not intended. version_added always refers to the collection it is part of. In this case, version_added should not be there, because the option was there when the module was introduced to the collection.
(During migration all version_added's were removed anyway, unfortunately even the ones with 2.10 as the value, which IMO should be there so the ACD docs will be more helpful.)

ansible/ansible#69926 has been merged, which changes the implementation away from tagged version numbes/dates to extra fields for the collection name.

@AlanCoding with the current implementation (now in 2.10 beta 1, so it shouldn't change again) you can explicitly specify the collection name. You might need to add ignore.txt entries in some cases, though.

Closing this proposal, since a better system has been now implemented.


Feature request: custom font on menus

Right now, I'm able to set the font of the title string via titleFontFamily in the theme, but it doesn't seem to affect the font of the menus.
It would be good to be able to set the font of both title and all menu strings to my application font.

I agree, this would be a nice addition. With the option to not define any specific font (let the application decide).
Since I had the need to support aliased (jaggy) system fonts for my electron application, I had to come up with a workaround. It's simple enough: wrap your  in an element which include a css class (e.g. 'my-titlebar'), and, in your stylesheet, specify a rule such as the following
.my-titlebar>div{
  font-family: "Segoe UI" !important;
}


Add debug representation for MarkerTree

Summary
Adds a simple Debug representation for MarkerTree based on the underlying decision diagram. For example, python_version == '3.7' and os_name == 'Linux') or os_name == 'Windows' is displayed as:
python_version<3.7 | >3.7 ->
  os_name<Windows | >Windows -> false
  os_name==Windows -> true
python_version==3.7 ->
  os_name<Linux | >Linux, <Windows | >Windows -> false
  os_name==Linux | ==Windows -> true

I'm not sure we want to use this form for our debug logs because it could be confusing to users but we've also run into issues where markers looked equal when simplified despite being represented slightly differently..

We should probably add a separate method display_maybe_empty for user facing output.

but we've also run into issues where markers looked equal when simplified despite being represented slightly differently..

Can you show an example? I really like how our Debug implementation works today, especially since it fits on one line. (Although that does break down for larger markers.)


Batch processing best practice

Hi, I made a windows service to resize some images in batch; I tried the ImageFactory loading the image source path like this:
using (var imageFactory = new ImageFactory(true))
{
	imageFactory
		.Load(source)
		.AutoRotate()
		.Resize(new ResizeLayer(
			new Size(width, height),
			ResizeMode.Crop
		));

	if (quality.HasValue)
	{
		imageFactory.Quality(quality.Value);
	}

	imageFactory.Save(source);
}

and then I tried to read all image's bytes first and then using a MemoryStream:
var photoBytes = File.ReadAllBytes(source);

using (var inStream = new MemoryStream(photoBytes))
{
	using (var outStream = new FileStream(
		source,
		FileMode.OpenOrCreate))
	{
		using (var imageFactory = new ImageFactory(true))
		{
			imageFactory
				.Load(inStream)
				.AutoRotate() //takes care of ex-if
				.Resize(new ResizeLayer(
					new Size(width, height),
					ResizeMode.Crop
				));

			if (quality.HasValue)
			{
				imageFactory.Quality(quality.Value);
			}

			imageFactory.Save(outStream);
		}
	}
}

I saw that using the source path directly the service doesn't release the loaded memory, instead the Stream version use less memory... what is the difference and is it correct to read all bytes first?
Thanks

Hi @valse Sorry for the slow reply.
Using the source path directly mean that System.Drawing keeps a lock on the input file memory until the everything has been disposed. Reading all the bytes and creating a new memory stream means that memory can be released by the GC once the ImageFactory has copied the data into an internal stream.
I think the approach you are using loading up the bytes is the best approach. By passing the byte array directly the memorystream does not allocate extra data since it knows the length of the input byte array.


how do you start signalhub after install

Do I need to start signalhub after install ?
I m going to install on a sub domain....is there any configuration that needs to be done after install ?

signalhub listen -p 8080 # starts a signalhub server on 8080
This is how you run it. Make sure you are using a node server (heroku allows this) or droplets from oceanServer. Take your pick one is free one is more robust. Also make sure it's GLOBALLY installed, 'npm install -g ...'


Refactoring & Cleanup

I'm creating this to keep track. Thanks a ton @motorina0 , that's really nice!

This issue is ready to be merged.

thank you!
will review & merge today in conjunction with some UI work

is here anything open @chris-aeviator? I think to prevent conflicts (and PRs that branch off of this one) we should get this into master.


Is send button wrongly enabled for ERC721/1155 on watched wallet?

These lines:
        switch (type, session.account.type) {
        case (.send, .real), (.request, _):
            makeCoordinatorReadOnlyIfNotSupportedByOpenSeaERC721(coordinator: tokensCardCoordinator, token: token)
        case (.send, .watch):
            tokensCardCoordinator.isReadOnly = true
        }

were replaced by:
tokensCardCoordinator.makeCoordinatorReadOnlyIfNotSupportedByOpenSeaERC721(type: type)

in the PR https://github.com/AlphaWallet/alpha-wallet-ios/pull/3164/files for SingleChainTokenCoordinator.
Do you think that's wrong? It seems like if the user taps an ERC721 (or 1155) token on a watched wallet, the Send button will be enabled when it shouldn't be.

hmm, that strange, i just moved code from SingleChainTokenCoordinator  to related coordinator

Could just be git doing it when resolving merge/conflicts. Can you help restore those few lines if it is wrong?


how to update users information

am building a social app with angular and i want users to be able to update their information from their profiles
any ideas about this
thanks

@nelsonwilliam11 the official repositories issues are for logging bug, discussing issues and feature request.
Please address how-to related questions in the community channels where you will receive answers to similar problems.
Great place to ask similar question is https://discourse.nativescript.org/
or SO with tag [nativescript]


MFA is not working when Server default Language is not English

Hello,
we are using a self hostet passbolt instance with MFA TOTP activated.
When i issue ~/go/bin/go-passbolt-cli command with different options set i always get the following  error
Error: Logging in: Getting CSRF Token: Error API JSON Response Status: Message: MFA-Authentifizierung ist erforderlich., Body: {"mfa_providers":["totp"],"providers":{"totp":"https:\/\/#########\/mfa\/verify\/totp.json"}}

The following commands i've tried
with non interactive
~/go/bin/go-passbolt-cli list folder --serverAddress https://######### --userPrivateKeyFile ~/.config/passbolt/my_private_passbolt.key --mfaMode noninteractive-totp --totpToken ############################################

with interactive mode, but i get no prompt for totp
~/go/bin/go-passbolt-cli list folder --serverAddress https://######### --userPrivateKeyFile ~/.config/passbolt/my_private_passbolt.key --mfaMode interactive-totp

Below is the output if i set the --debug flag. I needed to mask some stuff. sorry for that
Loading Private Key from File: /home/####/.config/passbolt/my_private_passbolt.key
Enter Password:
[go-passbolt] Request URL: https://#########/auth/login.json?api-version=v2
[go-passbolt] Raw Request: {"gpg_auth":{"keyid":"9a84f0a95d89e6f648677a9ef09ee4c10122aa27"}}
[go-passbolt] Raw Response: {"header":{"id":"1fb367da-30cf-4612-8ae9-2ff8ad62893c","status":"error","servertime":1649318386,"action":"a3c19ad2-8920-5395-86d0-8567cb34f382","message":"The authentication failed.","url":"\/auth\/login.json?api-version=v2","code":200},"body":null}
[go-passbolt] Got Encrypted Auth Token: -----BEGIN\+PGP\+MESSAGE-----####MASKED####-----END\+PGP\+MESSAGE-----%0A
[go-passbolt] Decrypted Auth Token: gpgauthv1.3.0|36|9f2aa6d2-0677-4f98-aae0-52e51126c37b|gpgauthv1.3.0
[go-passbolt] Request URL: https://#########/auth/login.json?api-version=v2
[go-passbolt] Raw Request: {"gpg_auth":{"keyid":"9a84f0a95d89e6f648677a9ef09ee4c10122aa27","user_token_result":"gpgauthv1.3.0|36|9f2aa6d2-0677-4f98-aae0-52e51126c37b|gpgauthv1.3.0"}}
[go-passbolt] Raw Response: {"header":{"id":"c29daf78-d5dc-4651-9770-24e860ee15c9","status":"success","servertime":1649318386,"action":"a3c19ad2-8920-5395-86d0-8567cb34f382","message":"Sie sind erfolgreich angemeldet.","url":"\/auth\/login.json?api-version=v2","code":200},"body":{"id":"b022137f-cb59-448b-8652-a8ec454b46c6","role_id":"113e7b9f-2932-44de-8e0e-6d51526bf7e3","username":"###MASKED###","active":true,"deleted":false,"created":"2018-11-26T16:38:54+00:00","modified":"2018-11-29T08:57:19+00:00","groups_users":[{"id":"52a77434-d538-463f-a130-0d84575518d5","group_id":"3e195d2c-25d0-49a1-b792-923b3bd7b350","user_id":"b022137f-cb59-448b-8652-a8ec454b46c6","is_admin":true,"created":"2018-11-29T11:11:50+00:00"},{"id":"9ef332f0-9ad9-4d0e-8ed5-8deb41a89c56","group_id":"a1c05340-7d5c-4ff5-9024-1534bfaf8d1a","user_id":"b022137f-cb59-448b-8652-a8ec454b46c6","is_admin":true,"created":"2018-11-29T09:36:12+00:00"}],"profile":{"id":"d7890c19-22c2-478c-bbd8-fd11c475f5b2","user_id":"b022137f-cb59-448b-8652-a8ec454b46c6","first_name":"#####","last_name":"#####","created":"2018-11-26T16:38:54+00:00","modified":"2018-11-26T17:48:27+00:00","avatar":{"url":{"medium":"https:\/\/#########\/img\/avatar\/user_medium.png","small":"https:\/\/#########\/img\/avatar\/user.png"}}},"gpgkey":{"id":"6e7ff95c-57ab-44cd-85f8-d44fd9e3133b","user_id":"b022137f-cb59-448b-8652-a8ec454b46c6","armored_key":"-----BEGIN PGP PUBLIC KEY BLOCK-----\r\nVersion: OpenPGP.js v4.2.0\r\nComment: https:\/\/openpgpjs.org\r\n\r\nxsBNBFv\/qc0BCADIFZbHhHIVR4MPwlFegy85EyyobrzLez2U9tY2MeeLXuHe\r\nMg\/zbv0jJhHMga6MrEGkJSNgofeyZGq4NZd0PT72QhtViOtIjykIUij+Idol\r\nLK6B+TXzkfRQv9OV2HF+RVi01F8y2IDzm8+EUA4zWO3uw2jor9WgwkbbEmFu\r\nGBoyVfz\/6kDLTbF\/jCUlIM1ousXBr2xs94S4JjxDSMdxr+Yz4GdzmtvrzBu8\r\nOcnHhXZkFYoe83TkYDVqRSdlYwzQiIZhp0j2Hxy45bVpLYNKCU6lwWAnuJ0V\r\ne6CaD91e0\/4rnj5leJQ19++F9gfdEIyBLh4LpxhhRZ0+ThSeWcBs321xABEB\r\nAAHNIyJNaWNoYWVsIEdyYcOfIiA8Z3Jhc3NAZGlvbmVyYS5jb20+wsB1BBAB\r\nCAAfBQJb\/6nNBgsJBwgDAgQVCAoCAxYCAQIZAQIbAwIeAQAKCRDwnuTBASKq\r\nJ\/kgB\/9mW2Y1QEg1KHg88nUzi+zgTepy4aXjJwI1SRk7PHEuW0V1AjfJfp5J\r\nBK\/8d+DmbIUvB74JGrW+9GH4jZjEiO0ZDhyXk8g0B8y\/dhiO6IVJmxixpAIr\r\nj\/aD\/SK4lF7w277kGmCqYeR8sZV6rw9OV7b2TiuNoCv928lP6oT9pqGiLdFP\r\nWowsYWS6qT2y2ZqR9Mg6tZzlIdgsMnuLmGSiWQHtxSDjbnoh1GXZfWfOYmCa\r\nMpls3uQIBjYihO4nMH2KOFbPBJv2JmEFDivXAjmafNYxt48N7Rv\/jRvbJAnG\r\n1otBq1uJTmn91enE0DZcyhZmIdBFvPxlNGJ75sl2lAVkPFz3zsBNBFv\/qc0B\r\nCAD3h4Ww0VNqBljPlLkv7+WvJEh66igSOpIMKpfpTCqI9k\/bOIPSzOraCYTy\r\n06sz44iwCRu89+RPjvOEuv0RAkyIGZsRQfz5k\/SRZVnIvJrmSyP7Ao+BDv2K\r\n6rdm91ZFB\/iVjHDdMVDiCob+FPVi0FTCfVklCN\/VCoYdQ4D1GlPOo3e0Ir8r\r\nlIBmvSy+D9mbdYvQ8w8StEuLfdHpUtzvfBXxe2QC9z8iYdEnT6qgQNuNhT1Z\r\nwsq3VXD90r9Bxsdrf4W94mHBdCoP4RerXfbIc+pOMYIy\/0jqRo0WIE0b44Eg\r\nAAYyWbMl+g5O1fGIOkmh08wa6UZpI8O24rAtTSoNQ4LXABEBAAHCwF8EGAEI\r\nAAkFAlv\/qc0CGwwACgkQ8J7kwQEiqieaswf\/TmuDoBkdfyiERVJehkNbsAT0\r\nO4AKB1xpoCCOmh19aQtGBYgI28oj95+Md8YocxUCqccvkhYZ00r4xLUCzSaS\r\nnShFvZbB7YXt3QbJcwmT8D8PaB+dXbzoZMEVfl3frD4wZGdsx9Yivq6s3r33\r\nTwzOD2kAmOs5v6I1mGZ5kzgElYJbeYpKR\/FR\/gqexnXYGv+eZ++M6oGDpqRO\r\nS3T2eR+SqJZpZDiwyj6IKzGaHua+s1bbHYrFUp5Y8W9a5X8B79av1xqfEif7\r\nW+\/wm92XdBWdftjOcXUvurZVXAQoUzjz5qEfmrr9\/VxCi8HAiObnZFnM0S0T\r\nsFg3RAqwADvR2hCbog==\r\n=jEY\/\r\n-----END PGP PUBLIC KEY BLOCK-----\r\n","bits":2048,"uid":"\u0022#####\u0022 \u003C#####\u003E","key_id":"F09EE4C10122AA27","fingerprint":"9A84F0A95D89E6F648677A9EF09EE4C10122AA27","type":"RSA","expires":null,"key_created":"2018-11-29T08:56:45+00:00","deleted":false,"created":"2018-11-29T08:57:19+00:00","modified":"2018-11-29T08:57:19+00:00"},"role":{"id":"113e7b9f-2932-44de-8e0e-6d51526bf7e3","name":"admin","description":"Organization administrator","created":"2012-07-04T13:39:25+00:00","modified":"2012-07-04T13:39:25+00:00"},"is_mfa_enabled":true,"last_logged_in":null}}
[go-passbolt] Got Cookies: [passbolt_session=pijiqu1fj8sa24pjt01gv9t71t; Path=/; HttpOnly; Secure; SameSite=Lax]
[go-passbolt] Request URL: https://#########/users/me.json?api-version=v2
[go-passbolt] Raw Response: {"header":{"id":"e47de27e-f5f5-43fa-a209-74c364a09805","status":"error","servertime":1649318386,"action":"af9aa2c6-7355-514d-a4a0-3e74de4c0fdb","message":"MFA-Authentifizierung ist erforderlich.","url":"\/mfa\/verify\/error.json","code":403},"body":{"mfa_providers":["totp"],"providers":{"totp":"https:\/\/#########\/mfa\/verify\/totp.json"}}}
Error: Logging in: Getting CSRF Token: Error API JSON Response Status: Message: MFA-Authentifizierung ist erforderlich., Body: {"mfa_providers":["totp"],"providers":{"totp":"https:\/\/#########\/mfa\/verify\/totp.json"}}

Hi,
your idea was almost correct. it was not the language of my profile, it was the default language of the passbolt instance.
When i switched it to english then everything was working.

Ah, I see. go-passbolt (the underlying library to go-passbolt-cli) checks if the error it gets during an API Call to the Passbolt server indicates that it needs to Complete an MFA Challange First before making that Original Call and then Attempts to solve that challenge. I was unaware that API Error Messages get Translated Based on the Server's Default Language...
The Problematic line is Here:
https://github.com/passbolt/go-passbolt/blob/69221b3a244efadec75ccfbf1a0b817554396dc8/api/api.go#L65
I'll talk to the Passbolt team about this since besides the Message (that I can't use anymore) all I get is Code 403 which means Forbidden and not necessarily that MFA is required.
Thanks for bringing this to my attention.

I have been Informed that I use the URL Field in the Error Request header instead of the Message Field until I get around to rewriting the Authentication to use the new JWT System which provides MFA information during the Login Stage.
A Fix is on its way.

that sounds good. thanks

I just released  v0.1.8 can you try MFA again using the Original Language Settings?

i tried it, and it is working now with my language. many thanks for the fast fix

Good to hear.


Contact for python project is developer email list

Replace (similar to ctapipe, gammapy) authors by the developer email list.
Note that author attribution is in CITATION.cff, this is the pypi contact.

Did you get my test e-mails?

Yes, you didn't?


Linebreaks after '>' continue to insert an additional '>' on every line

Tested using Vim 8+ and NVIM 0.4.3
Completely empty .vimrc except for the yats.vim plugin (Using vim-plug to enable)

If a *.ts or *.tsx file contains a >, any linebreaks that are inserted after that line will automatically append another >
This doesn't happen with self closing tags (/>) or if the line includes anything other than >

Looks like the issue is the ftplugin/typescriptreact.vim file with this line:
setlocal formatoptions-=t formatoptions+=croql which seems to be used to format code comments.
Reading up on it but > should probably be removed from the comment options since it's unused in TypeScript.


Error when testing

Hi,
I get the following when running the Lambda test. Can someone please offer some help.
{
"errorMessage": "In strict mode code, functions can only be declared at top level or immediately within another function.",
"errorType": "SyntaxError",
"stackTrace": [
"Module._compile (module.js:439:25)",
"Object.Module._extensions..js (module.js:474:10)",
"Module.load (module.js:356:32)",
"Function.Module._load (module.js:312:12)",
"Module.require (module.js:364:17)",
"require (module.js:380:17)"
]
}

I get the same issues.  Trying to set this up for the UK delivery of Dots tommorow.

Just fixed this, try changing to node.js 4.3 despite what the instructions say.

@castlesi I'm Interested to know if you got this working in the UK? i'm having issues. Alexa won't recognise the sonos skill iv made. I'm thinking it might be because its a US skill and I need to make the UK language variant however the AMAZON.LITERAL slot type is not supported by the English (UK) and German (Deutsch) Alexa languages. They also plan to deprecate this slot type in English (US).

See #55  "Try replacing all instances of AMAZON.LITERAL with LITERAL. I had the same issue the evening and it seems to work with this tweak."

I tried to add the UK language to my existing skill that had the US language but it refused to let me add the custom slot types without filling in the intent schema which I cant do without the custom slot types.

Thanks @thosirl that worked perfectly :)
@castlesi I had the same issue, just put anything to satisfy the linter I used the example from here then replace it once you have added the slots

The link in @MatthewAlner's last comment doesn't work, but I made up some random stuff to satisfy the linter and thought I'd add it here.
Intent Schema:
{   "intents": [     {       "intent": "TellMeAJokeIntent"     }   ] }
Sample Utterances:
TellMeAJokeIntent tell me a joke

I had similar problem, but the trick was to put in a reduced intent schema  without calling any custom slots, then add the custom slots, and then go back and add the full intent schema.

On 21 Oct 2016, at 21:03, castlesi<EMAIL_ADDRESS>wrote:
I tried to add the UK language to my existing skill that had the US language but it refused to let me add the custom slot types without filling in the intent schema which I cant do without the custom slot types.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.


WinHvPlatform.dll crashes Obliteration when pressing Start on any game.

Faulting application name: Obliteration.exe, version: <IP_ADDRESS>, time stamp: 0x66aa766c
Faulting module name: WinHvPlatform.dll, version: 10.0.22621.3672, time stamp: 0xb628bb33
Exception code: 0xc0000005
Fault offset: 0x00000000000076d7
Faulting application path: C:\Users\ghost\Downloads\obliteration-win-x64\Obliteration.exe
Faulting module path: C:\WINDOWS\SYSTEM32\WinHvPlatform.dll

This will be a joy to debug :skull:

And I can't help but feel like Ultima removed the log file being in appdata...

This will be a joy to debug 💀

(bac.3048): Access violation - code c0000005 (first chance)
First chance exceptions are reported before any exception handling.
This exception may be expected and handled.
WinHvPlatform!WHvApi::Hypercall::SetVpRegisters+0x1df:
00007ffc`12d976d7 410f280402      movaps  xmm0,xmmword ptr [r10+rax] ds:0000007d`18affb38=0000000000000000ffffffff8240c000

Can you identify which line that cause this error?

Can you identify which line that cause this error?

No because your VSCode kernel run is well, screwed. Compilation is as well for Windows XD

@ultimaweapon GOTCHA
    fn states(&mut self) -> Result<Self::States<'_>, Self::GetStatesErr> {
        let mut values: [WHV_REGISTER_VALUE; REGISTERS] = unsafe { zeroed() };
        let status = unsafe {
            WHvGetVirtualProcessorRegisters(
                self.part,
                self.index,
                WhpStates::NAMES.as_ptr(),
                REGISTERS as _,
                values.as_mut_ptr(),
            )
        };

Here;
            WHvGetVirtualProcessorRegisters(

I have no idea what causing segmentation fault here. We probably need someone with Windows to fix this.

Deduction here:
self.part, unless cloned, println!'d, or otherwise affected before being used by WHvGetVirtualProcessorRegisters... Will be free'd before WHvGetVirtualProcessorRegisters can use it, causing a Memory Access Violation.

That makes no sense I think

That makes no sense I think

It's what happens, however... The value is getting dropped for SOME reason unless I use something to make it active in the function before WHvGetVirtualProcessorRegisters uses it...

But that doesn't make sense. You can't 'drop' an int.

That why we need to figure out why it is crashing because your fix does not make sense.

That why we need to figure out why it is crashing because your fix does not make sense.

Welllll, have fun with Miri https://github.com/rust-lang/miri

@VocalFan you can set a breakpoint on that line and view its assembly once the breakpoint are hit to see how it calls the function?

@VocalFan you can set a breakpoint on that line and view its assembly once the breakpoint are hit to see how it calls the function?

{part:2517404947584, index:0}

This is for self.part and self.index

Error point.

rip: 0x00007FF76F742C27
rsp: 0x000000FED0DFD690
eax: 0xD0DFD470

No idea what wrong here since everything looks okay.

No idea what wrong here since everything looks okay.

Maybe a bug with windows-sys?

Everything here looks correctly so no. Seems like I need to set up a Windows machine to figure out.

Gonna see if this magically got fixed

I mean, it's new.

.next_multiple_of(Ram::VM_PAGE_SIZE) a very temporary thing of this on p_vaddr, and guess what came back?
Stop reason: Exception 0xc0000005 encountered at address 0x7ffc2bef39c6: Access violation reading location 0xffffffffffffffff

But I think that might be a hint, the unaligned address.


Add HEADERMEMBER opcode to AVM transpiler & simulator (discuss spec - it's probably wrong!)

We've decided to deprioritize this one for a while.


Tinting layers enable/disable

TintingColor can be enabled/disabled when load the map, can be changed in runtime.

issue solved


Bootstrap SCSS on NPM does not generate bg-dark classes

Prerequisites

[X] I have searched for duplicate or closed issues
[X] I have validated any HTML to avoid common problems
[X] I have read the contributing guidelines

Describe the issue
I'm tryna customize bootstrap for a website I'm building but I've came accross an issue:
When I import bootstrap's CSS normally, downloading or from a CDN I can use the .bg-dark class, but when I use SCSS and import bootstrap's SCSS, the bg-dark class isn't created.
That makes a big issue on my website as my navbar is using this class.
I've searched in my generated css (ctrl+f) "bg-dark" and did not found the class.
Here is the scss part where I import bootstrap:
@import "../node_modules/bootstrap/scss/functions";

$gold: #ffcc00;
$red: #e72020;
$yellow: #c99e12;
$blue: #1e90ff;
$dark-blue: #093085;
$hestia-blue: #3b4776;
$lighty-hestia-blue: #b2d3fa;
$green: #288509;
$greeny: #9BA841;

$theme-colors: (
    "primary": $gold,
    "secondary": $hestia-blue,
    "tertiary": $lighty-hestia-blue,
    "success": $green,
    "info": $blue,
    "warning": $yellow,
    "danger": $red,
    "blue": $blue,
    "red": $red,
    "yellow": $yellow,
    "gold": $gold,
    "hestia-blue": $hestia-blue,
    "light-hes-blue": $lighty-hestia-blue,
    "green": $green,
    "greeny": $greeny,
    "dark-blue": $dark-blue,
);

@import "../node_modules/bootstrap/scss/variables";
@import "../node_modules/bootstrap/scss/variables-dark";

@import "../node_modules/bootstrap/scss/bootstrap";
@import "../node_modules/bootstrap/scss/utilities";

// rest of customization after those statements

Reduced test cases
I cannot do a reduced test case as I cannot seem to make bootstrap work with customization with SCSS on codepen and don't know how to make one that works either.
What operating system(s) are you seeing the problem on?
Windows
What browser(s) are you seeing the problem on?
Chrome
What version of Bootstrap are you using?
5.3.3

I found a workaround using bg-secondary-subtle to do the same thing, but it'll be better if the bg-dark class worked.


roots and jeet

Hi, I've tried to add jeet to roots. I've followed instruction video, and managed to install without problem
http://prntscr.com/3hm53n
however, jeet is not being loaded in browser.
http://prntscr.com/3hm6h1
any ideas?
Thx

i am having issues with jeet. i had it working in my express env, but switching over to roots is proving problematic.
jeet 6.1.2 is visible in my node modules and package.json
in my express env, i require jeet by calling @require 'jeet' in the /stylesheets/index.styl file. i can't find an equivalent in roots.
any ideas?


Multiple Starting Values for a specific Workflow

Can a workflow have multiple starting options? In other words, can one StateField have more than one starting value, so the same stateField now is assigned to different workflows?

Hi @rupin. That is against finite-state-machines. Every FSM should have it's one and only initial state. Different workflows should have different state fields. What is it that you are trying to achieve?

Thanks for the response. I am modelling a generic workflow engine which can be deployed as a solution for simple use cases.
https://github.com/rupin/WorkflowEngine


How to set timeout on a redis cluster client

hiredis-vip : master
date : 2019-11-25
hiredis version in hircluster.h : 1.0.0
In my code, I got a redisClusterContext,
I called
struct timeval tv = { _timeout_ms / 1000, (_timeout_ms % 1000) * 1000};
_context = redisClusterConnectWithTimeout(_host.c_str(), tv, HIRCLUSTER_FLAG_NULL);
if (redisClusterSetOptionTimeout(_context,tv) != REDIS_OK) {      /* log on error */  }
Why it won't work, if I set _timeout_ms=10 , my redis command timer still get a number bigger than 10, say 29 maybe...

Also happen to me:
Doesn't timeout properly when server is unreachable.
when you will fix it ?

Also happen to me:
Doesn't timeout properly when server is unreachable.
when you will fix it ?

Also happen to me: Doesn't timeout properly when server is unreachable. when you will fix it ?

how do you solve this pro?

how do you solve this pro?

how do you solve this pro?

hiredis-vip : master date : 2019-11-25 hiredis version in hircluster.h : 1.0.0
In my code, I got a redisClusterContext, I called struct timeval tv = { _timeout_ms / 1000, (_timeout_ms % 1000) * 1000}; _context = redisClusterConnectWithTimeout(_host.c_str(), tv, HIRCLUSTER_FLAG_NULL); if (redisClusterSetOptionTimeout(_context,tv) != REDIS_OK) { /* log on error */ }
Why it won't work, if I set _timeout_ms=10 , my redis command timer still get a number bigger than 10, say 29 maybe...

how do you solve this pro?


audit: fix suggested GitHub pull request URLs

:+1:

Heh. This explains the typo someone made in a PR a while ago that made me wonder how they managed to mistype it when most people just copy/paste the URL bar.


upgrade dependencies, move to type script

This PR has no functional changes.
The main goals are to:

upgrade dependencies to latest versions (secp256k1 v3 particularly)

this small lib was forcing the user to carry some heavy dependecies

migrate to TypeScript (both the lib and the tests) - this makes it easier to check the code and understand the public interface
prepare for decoupling this lib from secp256k1 and move to injectable tiny-secp256k1

after this is issue is implemented: https://github.com/bitcoinjs/tiny-secp256k1/issues/68

Regarding this comment:
https://github.com/bitcoinjs/tiny-secp256k1/issues/68#issuecomment-996828894

To be honest... bitcoin-message should be archived. At this point any "updates" to it would be meaningless back-end optimizations and arguing minutiae about why we should adopt format X over format Y or how we could make it backwards compatible with format Z (where X Y Z are all different wallet apps that put their own spin on message signing)

This PR is not trying to do any functional updates.
Allowing to have a custom ecc lib instead of hardcoded dependency to secp256k1 makes this lib much lighter.
Then it can be archived :)

Perhaps we should also move from travis to github actions.

Updates:

[x] change from Travis to GitHub Actions
[x] update README and CHANGELOG

[x] replace "secp256k1": "^4.0.2 with  tiny-secp256k1": "^2.2.0
Commit: https://github.com/bitcoinjs/bitcoinjs-message/pull/38/commits/e4840bbbf51e40f9bcf05bc1e85a8e5c69d5eab3

@motorina0 @junderw any updates on this PR? ran into a build issue today related to an older version of secp256k1

Am mentioned here, it is not clear if this library should be maintained or just archived.
You can advocate here for keeping it alive.
Also tiny-secp256k does not work out of the box on some environments.

I'm willing to merge this.

bump major version
Add line at top of README about archiving this. Mention that if any bugs are found in the latest major version try using the last major version. Severe security vulnerabilities we might put out a patch.
I'll merge, publish, and archive.

Maybe we should also mention BIP322.
I've been thinking about how to implement BIP322, but since it requires a script interpreter, I think maybe we should make it generic with a function parameter that solves the script and returns true or false... then we can offer defaults for p2pkh, p2wpkh, p2sh-p2wpkh, and encourage others to submit solvers for other script types. (but anyone can pass in their own solver function)...

Oh no! I totally missed this one 🤦♂
I'm closing PR https://github.com/bitcoinjs/bitcoinjs-message/pull/47


docs: fix the anchor link on README for TypeScript dependency table

Thanks for the great library!

PR Checklist

[x] Addresses an existing open issue: related to #000

Because fixing a minor typo on README, this change is not related to any issues

[x] Steps in Contributing were taken

Overview

In the install section on README, the anchor link for TypeScript dependency table is not working because some words are capitalized.
So I fixed it correctly.
You can also check the fix with the following videos.
AFTER
https://github.com/ts-essentials/ts-essentials/assets/50320710/39416b1e-b273-4e70-88ee-baa604c6d034
BEFORE (CURRENT)
https://github.com/ts-essentials/ts-essentials/assets/50320710/96146d2d-8168-494a-ae63-e244a8f96a7c

This works as expected now. I don't know why this didn't work for me at a time.
Anyways, I close this issue.


Docstring is obscured by other cells on hover

Describe the bug
Setup: empty notebook.

In the first cell, call some function that has documentation. Hover over the function name. Docstring is shown in a floating view.
Create multiple one-line cells beneath.
Click one of these other cells to put the cursor there and select the cell.
Hover over the function from the first cell.

Result: the floating view with the docstring is shown beneath the other cells, so the docstring is obscured.

Expected: docstring should be on top of all cells.
Environment
{
  "marimo": "0.2.1",
  "OS": "Darwin",
  "OS Version": "22.6.0",
  "Processor": "i386",
  "Python Version": "3.12.1",
  "Binaries": {
    "Chrome": "--",
    "Node": "--"
  },
  "Requirements": {
    "black": "23.12.1",
    "click": "8.1.7",
    "jedi": "0.19.1",
    "pymdown-extensions": "10.7",
    "starlette": "0.37.0",
    "tomlkit": "0.12.3",
    "typing_extensions": "4.9.0",
    "uvicorn": "0.27.0"
  }
}

Code to reproduce
No response

Thanks for catching this. I had some z-index logic for the focused cell, but its still possible get a tooltip without being focused on the cell. I have fixed this in https://github.com/marimo-team/marimo/pull/741

Ah I understand why this is happening. I'll see if there is a simple solution, I will re-open this for now.

this was fixed a while back - but i may have forgot to link the PR, closing this now


NOS-730 Add concurrent test for GitManager

Seems the git add/delete needs some level of the lock to avoid concurrent opers

retest this please


Convert use of KML to WKT

Convert KML polygons to WKT
Standardize volcano site names to harmonize with orderFreshRCMImagery.sh
- Example: A4202_Volcano_Garbld.kml should be expanded to A4202_Volcano_Garibaldi.wkt
Consider ways to reduce code replication in orderFreshRCMImagery.sh

the cli code is still using kml. Since we will be moving to VRRC-API I think we can close with a 'Closed as not planned'

Entire eodms-cli will be depricated by VRRC-API


Releasing a new rc version of apex?

Hi TJ, when are you planning on a new rc release of apex? We're relying on support of this PR from May. Thanks!

Closed by 7c1d44b04d0de6807484c167484e65773ecd55cb . Thanks!

Nevermind, not published to https://github.com/apex/apex/releases

v1.0.0-rc4 should be ok now sorry for the delay there!

Hi TJ, I'm not sure if you pushed the latest version to the GitHub releases, as the latest version is still v1.0.0-rc3.


Inconsistent msgctxt Value

See these examples:
#: Portal.Web\Localization\CommonStrings.cs:11
#. public string SaveChanges => S["Save Changes"];
msgctxt "Portal.Web.Localization."
msgid "Save Changes"
msgstr ""

#: Portal.Web\Pages\Picos\LoadManagement\Multilevel\MultilevelErrorMapper.cs:63
#. return S["Not found"];
msgctxt "Portal.Web.Pages.Picos.LoadManagement.Multilevel.MultilevelErrorMapper"
msgid "Not found"
msgstr ""

#: Portal.Web\Shared\CultureSelector.razor:11
#. Label="@S["Language"]" Placeholder="@S["Please Select"]"
msgctxt "Portal.Web.Shared.CultureSelector.razor"
msgid "Language"
msgstr ""

You can see that the first does not include the class name in the msgctxt while the second does.
The third one has the class name + ".razor" suffix.
I suspect that the msgctxt is generated from the filename/file path, not the actual type name?
Note that passing -t "razor" or leaving it out does not change anything about the generated *.pot file.

CommonStrings.cs
public class CommonStrings(
    IStringLocalizer<CommonStrings> s)
{
    // ReSharper disable once InconsistentNaming required by OrchardCoreContrib
    readonly IStringLocalizer S = s;

    public string Ok => S["OK"];
    public string SaveChanges => S["Save Changes"];
    public string Cancel => S["Cancel"];
}

MultilevelErrorMapper.cs
public class MultilevelErrorMapper
{
    // ReSharper disable once InconsistentNaming required by PoExtractor
    readonly IStringLocalizer S;

    public MultilevelErrorMapper(
        IStringLocalizer<MultilevelErrorMapper> s)
    {
        S = s;
    }

    LocalizedString MapNotFound(
        NotFound _)
    {
        return S["Not found"];
    }
}

CultureSelector.razor
@using Microsoft.Extensions.Localization
@using System.Globalization
@using Domain
@inject IStringLocalizer<CultureSelector> S

<MudSelect ValueChanged="SetCulture"
           T="CultureInfo"
           Value="CultureInfo.CurrentUICulture"
           Label="@S["Language"]" Placeholder="@S["Please Select"]"
<EMAIL_ADDRESS>           Style="width:200px; margin-left:10px;">
    @foreach (var culture in SupportedUiLanguages.Cultures)
    {
        <MudSelectItem Value="@culture" <EMAIL_ADDRESS>    }
</MudSelect>

Is this still a valid bug?

Is this still a valid bug? or this one #85?

Yes, I'm experiencing both with the latest version 1.0.1 released on 24.01.2023.
Or do you mean I should try out the version from the develop branch?

@hishamco
on develop, the first problem with the missing class name is fixed.
Texts in the razor templates are still reported with a msgctxt of ....razor. Tomorrow I'll verify if this actually is a problem and OrchardCore.Localization uses a different msgctxt - or not.

I'm waiting, otherwise please write a failing unit test, so I can fix the issue

For completeness sake here a copy of the original post, where I thought there was more problems - but actually 2 out of 3 are resolved in the upcoming .net 8 based version:

See these examples:
#: Portal.Web\Localization\CommonStrings.cs:11
#. public string SaveChanges => S["Save Changes"];
msgctxt "Portal.Web.Localization."
msgid "Save Changes"
msgstr ""

#: Portal.Web\Pages\Picos\LoadManagement\Multilevel\MultilevelErrorMapper.cs:63
#. return S["Not found"];
msgctxt "Portal.Web.Pages.Picos.LoadManagement.Multilevel.MultilevelErrorMapper"
msgid "Not found"
msgstr ""

#: Portal.Web\Shared\CultureSelector.razor:11
#. Label="@S["Language"]" Placeholder="@S["Please Select"]"
msgctxt "Portal.Web.Shared.CultureSelector.razor"
msgid "Language"
msgstr ""

You can see that the first does not include the class name in the msgctxt while the second does.
The third one has the class name + ".razor" suffix.
I suspect that the msgctxt is generated from the filename/file path, not the actual type name?
Note that passing -t "razor" or leaving it out does not change anything about the generated *.pot file.

CommonStrings.cs
public class CommonStrings(
    IStringLocalizer<CommonStrings> s)
{
    // ReSharper disable once InconsistentNaming required by OrchardCoreContrib
    readonly IStringLocalizer S = s;

    public string Ok => S["OK"];
    public string SaveChanges => S["Save Changes"];
    public string Cancel => S["Cancel"];
}

MultilevelErrorMapper.cs
public class MultilevelErrorMapper
{
    // ReSharper disable once InconsistentNaming required by PoExtractor
    readonly IStringLocalizer S;

    public MultilevelErrorMapper(
        IStringLocalizer<MultilevelErrorMapper> s)
    {
        S = s;
    }

    LocalizedString MapNotFound(
        NotFound _)
    {
        return S["Not found"];
    }
}

CultureSelector.razor
@using Microsoft.Extensions.Localization
@using System.Globalization
@using Domain
@inject IStringLocalizer<CultureSelector> S

<MudSelect ValueChanged="SetCulture"
           T="CultureInfo"
           Value="CultureInfo.CurrentUICulture"
           Label="@S["Language"]" Placeholder="@S["Please Select"]"
<EMAIL_ADDRESS>           Style="width:200px; margin-left:10px;">
    @foreach (var culture in SupportedUiLanguages.Cultures)
    {
        <MudSelectItem Value="@culture" <EMAIL_ADDRESS>    }
</MudSelect>

@hishamco
Sorry for the delay - I was super busy at work.
I have now investigate the issue and it's just the fact that Razor support is broken when the razor file does not have a file ending of .cshtml. I have updated the issue entry (first post) to reflect that and have given more information there, including steps to reproduce. The issue should be rather trivial to fix.
If you want me to, I can provide a PR, but would like to request guidance from you as to which solution to choose.
Like I wrote in the opening post I see two easy solutions:

replace .cshtml and .razor with string.empty. This one is safe, but of course, if another extension is used, it doesn't work.
replace any file extension, no matter what it is. This one stops working when the file has a name of foo.bar but .bar is not supposed to be an extension... so I think it's safe, too, and simpler, too. So I would propose to use this.

IMHO supporting .razor makes sense to me


Python

I wish this was in python...

 I have this as part of my larger simulation package (on PyPI, but woefully undocumented). Yes, I am calling it "py a-la-mode"
https://github.com/mccullerlp/phasor/tree/master/phasor/alm
From example notebooks you can largely get it to work. It cannot currently do the combinatoric search that a-la-mode does, but using foreward/backward propagation plots to find where the beam widths cross, and the diopters-distance between beam ROCs you can more methodically design telescopes which don't rely on short focal length combinations.
https://git.ligo.org/LASTI-Squeezing/filter-cavity/wikis/layouts/FC_table/mode_matching/laser_SQZ_LO

ah, nice. @Haocun was also working on this years ago, but now you can also answer my question over at ask.ligo.org !


Converting circular structure to JSON

Hello @kahmali !
I'm trying to filtering result of get endpoind, but receive error.
I have enabled useDefaultAuth and get Id and token after successful authorisation.
// REST API configuration

var Api = new Restivus({
    useDefaultAuth: true,
    prettyJson: true
});

Api.addRoute('workouts', {authRequired: true}, {
    get: {
    |   authRequired: true,
    |   action: function() {
    |   |   var workouts = Workouts.find({
    |   |   |   $or: [{
    |   |   |   |   createdBy: this.userId,
    |   |   |   |   isPrivate: true
    |   |   |   }, {
    |   |   |   |   isPrivate: false
    |   |   |   }],
    |   |   |   $and: [{
    |   |   |   |   isDeleted: false
    |   |   |   }]
    |   |   });
    |   |   return {status: 'success', data: workouts};
    |   }
    }
});

Before access to data I have to authorize
[andrey@smartworkout:~]% curl http://smartworkout.ru:3000/api/login -d<EMAIL_ADDRESS>{
  "status": "success",
  "data": {
    "authToken": "W3SJbBG2gFP4KCyNJRP5ptbFq9sjuzW1S_zuk6YKH-Z",
    "userId": "QhKCfojmdC3Ep2oSz"
  }
}%

and after try to get data but get an error
[andrey@smartworkout:~]% curl -H "X-Auth-Token: W3SJbBG2gFP4KCyNJRP5ptbFq9sjuzW1S_zuk6YKH-Z" -H "X-User-Id: QhKCfojmdC3Ep2oSz" http://smartworkout.ru:3000/api/workouts/
TypeError: Converting circular structure to JSON
    at Object.stringify (native)
    at Object.stringify (/home/andrey/.meteor/packages/ecmascript-runtime/.<IP_ADDRESS>sx0wk++os+web.browser+web.cordova/npm/node_modules/meteor-ecmascript-runtime/node_modules/core-js/modules/es6.symbol.js:127:21)
    at Route.share.Route.Route._respond (packages/nimble_restivus/lib/route.coffee:227:21)
    at packages/nimble_restivus/lib/route.coffee:79:18
    at packages/simple_json-routes/json-routes.js:76:1

Could you help me understand why?
If I try to simplify task and try to get data using standard endpoint it works fine.
Api.addCollection(Workouts, {
    routeOptions: {
    |   authRequired: true
    }
});

I have read all issues regarding filterind endpoint data and didn't find any good example how to accomplish it. Is it possible to get data filtered for example by creation user or document status etc.?

Ok. I found the cause of problem. It was in my request which return cursor instead of array. To get the array I have to add fetch() to my request.
Finally it should looks like:
Api.addRoute('workouts', {authRequired: true}, {
    get: {
    |   authRequired: true,
    |   action: function() {
    |   |   var workouts = Workouts.find({
    |   |   |   $or: [{
    |   |   |   |   createdBy: this.userId,
    |   |   |   |   isPrivate: true
    |   |   |   }, {
    |   |   |   |   isPrivate: false
    |   |   |   }],
    |   |   |   $and: [{
    |   |   |   |   isDeleted: false
    |   |   |   }]
    |   |   }).fetch();  // here the convert cursor to array
    |   |   return {status: 'success', data: workouts};
    |   }
    }
});


Add work remotely option in Create Post and Filter Page

What does this pull request aim to achieve? 💯
Add work remotely option in Create Post and in Filter on feed Page.
Please be concise and link any related issue(s):
adding a feature resolves issue #2180

[x] I have checked that no one else is working on similar changes.
[x] I have read the latest README and understand the development workflow.
[x] The name of this branch is: feature/<branch_name>, or hotfix/<branch_name> if this is a hotfix, where <branch_name> briefly describes the issue(s) resolved and is prefixed with the issue number(s) (e.g. 1127-1130-update-git-branching-model). The branch is created in a cloned version of this repo, not a forked repo.
[x] This branch is rebased/merged with the latest staging (or the latest production if it is a hotfix).
[x] There are no merge conflicts.
[x] There are no console warnings and errors.
[x] On the right hand side of this PR, I have linked the appropriate issue(s) under "Issues" and added a project progress under "Projects".
[x] The title describes the issue(s) being addressed using format: <issue_numbers> - <brief_issue_description> (e.g. #1127/#1130 - Update Git Branching Model)

@rabbi08 here is the build URL: https://featureadd-remote-createpostandfilter-pa.fightpandemics.xyz/

@rabbi08 here is the build URL: https://featureadd-remote-createpostandfilter-pa.fightpandemics.xyz/

thanks @aditilamkhede
below are few observations for this feature:

Please update label of 'Remote' as 'Remote Work' on Filters page.

The size, color and font of 'Remote option's "TEXT and ICON" should match with 'Share my location' option
Also great if we can align this option with 'Share my location' Please see below screenshot from desktop:

Search is performed when user click on 'Remote' option only. User should be able to select the checkbox and click on 'Apply Filters' to see the search results, just like for other filter options. This is to keep the search filters in sync, so that user can combine more than one filters.

After 'Remote' filter is applied and user is directed to help board, the 'applied filter option-remote' should be displayed to indicate the user that remote filter is in place, similar to other filter options.

Please see below video for issue# 2 & 3:
https://user-images.githubusercontent.com/67168400/106177295-51b05080-6166-11eb-8885-81b86148714e.movPlease refer above video.

Filter: Existing post having tag as 'Remote Work' are NOT displayed in the search. Please see below video:

https://user-images.githubusercontent.com/67168400/106180275-17e14900-616a-11eb-9503-a2d20c2ee628.mov

Filtered Results: the post having no 'Remote work' tag is displayed. Please see below video:

https://user-images.githubusercontent.com/67168400/106181073-22e8a900-616b-11eb-9429-7e29e927bc2f.mov

thanks @aditilamkhede
below are few observations for this feature:

Please update label of 'Remote' as 'Remote Work' on Filters page.

The size, color and font of 'Remote option's "TEXT and ICON" should match with 'Share my location' option
Also great if we can align this option with 'Share my location' Please see below screenshot from desktop:

Search is performed when user click on 'Remote' option only. User should be able to select the checkbox and click on 'Apply Filters' to see the search results, just like for other filter options. This is to keep the search filters in sync, so that user can combine more than one filters.

After 'Remote' filter is applied and user is directed to help board, the 'applied filter option-remote' should be displayed to indicate the user that remote filter is in place, similar to other filter options.

Please see below video for issue# 2 & 3:
https://user-images.githubusercontent.com/67168400/106177295-51b05080-6166-11eb-8885-81b86148714e.movPlease refer above video.

Filter: Existing post having tag as 'Remote Work' are NOT displayed in the search. Please see below video:

https://user-images.githubusercontent.com/67168400/106180275-17e14900-616a-11eb-9503-a2d20c2ee628.mov

Filtered Results: the post having no 'Remote work' tag is displayed. Please see below video:

https://user-images.githubusercontent.com/67168400/106181073-22e8a900-616b-11eb-9429-7e29e927bc2f.mov

@rabbi08 I just have to work on 4th from above and then I will be done. 5 and 6are related to update data for old records. I will create script for old records and send it to @ddveloper.

@rabbi08 Ready for testing.
Here is the build url: https://featureadd-remote-createpostandfilter-pa.fightpandemics.xyz/feed

@rabbi08 in addition to the 3rd observation from above,I believe we should remove "Remote Work" tag from "Types" filters as well on HelpBoard

@rabbi08 in addition to the 3rd observation from above,I believe we should remove "Remote Work" tag from "Types" filters as well on HelpBoard

Yes plz
great catch @aditilamkhede
Thanks

@rabbi08 ready for review.

@aditilamkhede The question in the Create Post pop up modal window on the build  does not match the Feature description given on Notion.

Create Post pop up modal window on the build.

@aditilamkhede The question in the Create Post pop up modal window on the build does not match the Feature description given on Notion.

Create Post pop up modal window on the build.

@SinghRomika you are right, but notion needs to be updated. Notion is old. In current scenario there will be 3 options as you see currently.

@aditilamkhede  while reviewing the PR #2165 (new post fulfillment option in 'create post' and 'filter' page).
When i clicked the search my Location( Under Location). The location captured by the application was different than my original location.
(Location captured by the application)

(The difference between the Actual location vs what the application shows)

@aditilamkhede while reviewing the PR #2165 (new post fulfillment option in 'create post' and 'filter' page).
When i clicked the search my Location( Under Location). The location captured by the application was different than my original location.
(Location captured by the application)

(The difference between the Actual location vs what the application shows)

Hi @SinghRomika not part of this PR. So, may be you want to file a bug. Also check the same on Staging before filing a bug.
@rabbi08 ?

@aditilamkhede I added this comment by mistake, please ignore it Thx!!

@aditilamkhede Reviewed PR #2165 for now there seems to be no issue in the PR. Thanks!

Thanks @aditilamkhede
The features looks great, the functionality is working as expected in Create post and 'filter' page.
I have an observation on mobile view:

When user EDIT the post and have remote options value as both i.e. 'Remote & In-Person' the UI get distorted for the post i.e. the ellipses gets overlapped and the 'edited' text moved on the user profile icon. Please see below GIF and screenshot.

Thanks @aditilamkhede
The features looks great, the functionality is working as expected in Create post and 'filter' page.
I have an observation on mobile view:

When user EDIT the post and have remote options value as both i.e. 'Remote & In-Person' the UI get distorted for the post i.e. the ellipses gets overlapped and the 'edited' text moved on the user profile icon. Please see below GIF and screenshot.

@rabbi08 I will see what I can do. If there isn't any space available are we ok to trim some text or any other suggestions like decreasing font size?

Thanks @aditilamkhede
The features looks great, the functionality is working as expected in Create post and 'filter' page.
I have an observation on mobile view:

When user EDIT the post and have remote options value as both i.e. 'Remote & In-Person' the UI get distorted for the post i.e. the ellipses gets overlapped and the 'edited' text moved on the user profile icon. Please see below GIF and screenshot.

@rabbi08 I will see what I can do. If there isn't any space available are we ok to trim some text or any other suggestions like decreasing font size?

Yes @aditilamkhede  we can trim for small size screens, if that work
Trim date can be like -
"Remote/In-pers" if that works
Thanks


Lab 01: Challenging on LOD/Skillable to create users

Module: 01
Lab/Demo: 01
Task: 00
Step: 00
Description of issue
In Lab1: Creating users and activiting P1/P2 licenses is not available to students on LOD/Skillable.
Better start with Lab 4,  create a new tenant, and then try to finish Lab 1.
The solution to create a E5 trial is not working. From the hosted lab, students can't create this new tenant.
Better to do it like lab 4 or like Lab 6 in the AZ-204 course were is works now on LOD.
Repro steps:

Also in the flow of the theory in Module 1 it seems better to start with Lab 4 instead of Lab 1.

MOC-Labs-Review did not encounter this Issue while running the course.

MOC-Labs-Review did not encounter this Issue while running the course.


Add algorithm_globals to utils

Summary
Fixes #21
Details and comments

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.10 out of 23 committers have signed the CLA.:white_check_mark: mtreinish:white_check_mark: Cryoris:white_check_mark: kdk:white_check_mark: nkanazawa1989:white_check_mark: TheGupta2012:white_check_mark: 1ucian0:white_check_mark: ikkoham:white_check_mark: kevinhartman:white_check_mark: ElePT:white_check_mark: Eric-Arellano:x: manoelmarques:x: levbishop:x: molar-volume:x: hhorii:x: stefan-woerner:x: iuliazidaru:x: jakelishman:x: enavarro51:x: eggerdj:x: doichanj:x: renier:x: wshanks:x: jlapeyreYou have signed the CLA already but the status is still pending? Let us recheck it.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

43 of 58 (74.14%)  changed or added relevant lines in 2 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.1%) to 89.666%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

qiskit_algorithms/utils/algorithm_globals.py
40
55
72.73%

Totals

Change from base Build<PHONE_NUMBER>:
-0.1%

Covered Lines:
6421

Relevant Lines:
7161

💛  - Coveralls

We may want to start with a fresh copy of this tailored/cu-down/refactored to allow it to interoperate with the qiskit.utils algorithms_globals to allow a transition. I think for this any history is not important. Maybe this is adding the history for the whole of the utils module too - the list of people seems to far exceed any I would have expected to have done anything with this. Its been pretty much unchanged from Aqua I think.

Closing and starting from scratch (and yes I think that filter-repo got all of the history of the utils module)


JWT Issue

I'm using JSON Web Token to auth my API. When trying to set auth: 'jwt' in the plugin options for hapi-swagger, I get the following error: Unknown authentication strategy jwt in /swagger.json

I'm also interested in knowing how to set up JWT (e.g. with hapi-auth-jwt2) using hapi-swagger.

Hi I will have a look at this early next week, once I have cleared one or two other pressing issue for people.

Hi  I have just given this a go with the hapi-auth-jwt2 plug-in and the short answer is that you need to setup both the securityDefinitions and security options as below
let swaggerOptions = {
    info: {
        'title': 'Test API Documentation',
        'description': 'This is a sample example of API documentation.',
    },
    securityDefinitions: {
        'jwt': {
            'type': 'apiKey',
            'name': 'Authorization',
            'in': 'header'
        }
    },
    security: [{ 'jwt': [] }],
};

then add the auth property to your routes as normal
{
        method: 'GET',
        path: '/restricted',
        config: {
            auth: 'jwt',
            tags: ['api'],
            handler: function(request, reply) {
            reply({text: 'You used a Token! ' + request.auth.credentials.name })
                .header("Authorization", request.headers.authorization);
            }
        }
      }

This will cause the swagger UI to provide a input box in the top right hand corner of the page where you can paste in your token. This will give you the most basic functionality of using token with swaggerui.
I think what I need to do is provide a sample app with login, token generation and documentation all working together.

HI. I have tried your suggestion, but I don't see the input. Not sure if I'm doing something wrong:
Code snippet of my server:
server.register([{
    register: require('blipp'),
    options: {showStart:false,showAuth:true}
  },{
    register: require('inert')
  },{
    register: require('vision')
  },{
    register: require('hapi-swagger'),
    options: {
      info: {title:'takealot.com Admin REST API documentation',description:'Swagger 2.0 documentation for the takealot.com Admin REST API'},
      securityDefinitions: {
        'jwt': {
          'type': 'apiKey',
          'name': 'Authorization',
          'in': 'header'
        }
      },
      security: [{ 'jwt': [] }]
    }
  },{
    register: require('hapi-auth-jwt2')
  }, {
    register: require('bassmaster'),
    options: {
      auth: false
    }
  }, {
    register: require('hapi-api-version'),
    options: {
      validVersions: JSON.parse("[" + process.env.API_VERSION_VALID + "]"),
      defaultVersion: Number(process.env.API_VERSION_LATEST),
      vendorName: process.env.API_VERSION_VENDOR
    }
  }
  ], (err) => {
    if (err) {
      console.log('ERROR:', 'Failed loading plugins!');
    };
    /* Loading auth strategy */
    server.auth.strategy('jwt', 'jwt',{
      key: process.env.API_KEY,
      validateFunc: validateToken,
      verifyOptions: {ignoreExpiration:true,algorithms:['HS256']}
    });
    server.auth.default('jwt');

Here's a screenshot:

Okay, I upgraded to 5.0, and I can now see the input. Thanks!

Hi I have built a full demo with JWT and a customised version of the swagger-ui that works with tokens. The changes to the html are small but I think you will like the layout.
Demo: https://hapi-token-docs.herokuapp.com/
Code: https://github.com/glennjones/hapi-token-docs/
I needed a reference piece for when people ask about token etc, but thought it would help you as well
Enjoy

@glennjones I have done what you suggested in your comment above and I can see the input field in the header, however, when I type something and press the "enter" key, the page returns an error:
fetching resource list: undefined; Please wait.
I am using latest versions of hapi and hapi-swagger (v6.1.0)
Do you know what could be wrong?
Thanks

Hi,
after trying different solutions I solved it by adding headers specification with Joi in the server routes that I want to accept the Authorization header. Here I show you a GET endpoint that required JWT authentication:
'use strict';
const Joi = require('joi');

exports.register = (server, options, next) => {
  server.route({
    method: 'GET',
    path: '/users/me',
    config: {
      description: 'Get the current user information details - [ Authentication required ]',
      tags: ['meta', 'users', 'api'],
      validate: {
        headers:
          Joi.object().keys({
            'authorization': Joi.string().required().description('Authorization header containing the JSON Web Token'),
            'host': Joi.string().optional(),
            'accept-encoding': Joi.string().optional(),
            'connection': Joi.string().optional(),
            'accept': Joi.string().optional(),
            'user-agent': Joi.string().optional(),
            'referer': Joi.string().optional(),
            'accept-language': Joi.string().optional()
          })
      }
    },
    handler(request, reply) {

      reply(request.auth.credentials);
    }
  });

  return next();
};

exports.register.attributes = {
  name: 'me'
};


Update sbt to 1.2.8

Updates org.scala-sbt:sbt from 1.1.5 to 1.2.8.
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention @scala-steward in the comments below.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [{ groupId = "org.scala-sbt", artifactId = "sbt" }]

labels: semver-minor

Replaced by #40.


[Feature Request]: [Go SDK] Encode Keys once for combiner lifting.

What would you like to happen?
The Go SDK's combiner lifting currently encodes keys twice for caching. First it encodes values into a hash function, and then it repeats it to get the []byte for byte by byte comparisons in the cache.
https://github.com/apache/beam/blob/master/sdks/go/pkg/beam/core/runtime/exec/combine.go#L469
https://github.com/apache/beam/blob/master/sdks/go/pkg/beam/core/runtime/exec/combine.go#L483
For expensive keys, this can become very expensive without additional caching schemes.
Ideally this encoding happens once, instead of twice for each key being looked up.
Note: Windowed byte equality is important to use for final lookups because that's the only way to ensure equivalence to runners. Beam Model GBKs use byte equality for keys as their basis.
Issue Priority
Priority: 2
Issue Component
Component: sdk-go

A solution would be to encode to a []byte, wrap it in a bytes.Reader, then use that for the hash, and then the raw bytes for the byte by byte lookup comparison (as we do now). I'm not sure if we can change enough of the hash APIs to use byte.Reader directly keep everything stack based though.
This would be good to have a benchmark written and then a Before/After comparison of the change (even if the benchmark is new with the PR) to validate.


upcoming: [M3-8848] - Update Kubernetes version Autocomplete to filter on LKE-E versions

Description 📝
When a user selects LKE-Enterprise as their cluster type, we will need to ensure the Kubernetes versions for the enterprise tier are displayed and the versions for the standard tier are not.
Note: UX has noted that there is a potential drop off at the version field in LKE during cluster creation. Potential helper text/tooltip may be added. Update: this will be done in M3-8992, dependent on what docs we link (and where) to help.
Changes  🔄

Fixed a missing return in the useKubernetesTieredVersionsQuery hook
Used this hook in the Create Cluster flow to fetch tiered ('standard' and 'enterprise') versions
Updated the logic for the Kubernetes Version autocomplete selection to use tiered versions with the LKE-E feature enabled
Updated the payload with a tier if the LKE-E feature is enabled so that the enterprise cluster can be created
Updated test coverage in lke-create.spec.ts

Preview 📷
https://github.com/user-attachments/assets/85635d2b-02cd-4fa2-bae6-a26c593546c1
How to test 🧪
Prerequisites
(How to setup test environment)

Have LKE-E customer tag on your account (see Project Tracker)

Verification steps
(How to verify changes)

[ ] Go to http://localhost:3000/kubernetes/create
[ ] Confirm the following with the feature flag ON:

[ ] The version select shows the latest standard LKE version by default (e.g. 1.31)
[ ] When the user selects LKE Enterprise as their cluster type, the version select shows only LKE-E versions
[ ] The user can toggle back to standard versions by selecting LKE as the cluster type
[ ] The user can create an enterprise cluster by selecting a region in which LKE-E is available (e.g. Chicago), a current enterprise k8 version, and submitting the form
[ ] The user can create a standard cluster by selection any region, a current standard k8 version, and submitting the form

[ ] Confirm the following with the feature flag OFF:

[ ] No regressions to the version select and the existing endpoint (/versions) is used
[ ] No regressions to the user's ability to create an LKE cluster

[ ] Confirm test coverage passes:

yarn cy:run -s "cypress/e2e/core/kubernetes/lke-create.spec.ts"

 Author Checklists
As an Author, to speed up the review process, I considered 🤔
👀 Doing a self review
❔ Our contribution guidelines
🤏 Splitting feature into small PRs
➕ Adding a changeset
🧪 Providing/improving test coverage
🔐 Removing all sensitive information from the code and PR description
🚩 Using a feature flag to protect the release
👣 Providing comprehensive reproduction steps
📑 Providing or updating our documentation
🕛 Scheduling a pair reviewing session
📱 Providing mobile support
♿  Providing accessibility support

[x] I have read and considered all applicable items listed above.

As an Author, before moving this PR from Draft to Open, I confirmed ✅

[x] All unit tests are passing
[x] TypeScript compilation succeeded without errors
[x] Code passes all linting rules

Tests looking stable and any further UX enhancements saved (M3-8922) until we have a better idea of any versioning API updates coming from the backend, this PR is good for re-review as is.


Updatable inference lens

Implemented the updateable inference lens and the progressive update trait, testing for short and longer updating, added model manager to update models in a background thread. The model manager will have a background thread that repeatedly checks each model with the update trait if that model is updated. If it hasn't completed updating, this thread calls the model to update itself.

I will also note that likely the sanity checker should be scheduled for nightly testing, if possible.


spec-char-escape gives invalid line/col numbers

Hi,
When using the defaults for spec-char-escape rule I am getting the error but the line and column numbers are incorrect. As an example I have this error (&) in my file, on line 75, column 182, but the reporter is giving me:
line 1  col 8   text contains improperly escaped characters: &  (E023)
However if I escape this character only and re-run the error goes away.

Line/column numbers are another thing that should be tested...


Scalability tests failing on Jenkins due to non starting pods

There were a lot of failures in our scalability tests during last day (more than 50%). There seem to be two main reasons:

timeouts while waiting for deleting the previous namespace - this should be fixed by #10225
some pods not starting

I started looking deeper into those non-starting pods. Here is an example that contributed to the failure:

Jenkins scalability run 1539 - Density test
we are looking only on pods from "e2e-tests-density-xyfx4" namespace
look at the node "e2e-scalability-minion-k2n5"
scheduler scheduled 10 pods onto that node
it seems that at most 7 pods were actually started (7 logs "Need to restart pod infra container ...")
then there is a log: "GET /healthz: (928.173627ms) 500"
after that all the pods from that node were killed: "killing unwanted pod"

Links to logs:

Jenkins: http://kubekins.dls.corp.google.com/job/kubernetes-e2e-gce-scalability/1539/consoleFull
kubelet logs: https://storage.googleapis.com/kubernetes-jenkins/logs/kubernetes-e2e-gce-scalability/1539/_artifacts/<IP_ADDRESS>%3A22-kubelet.log
scheduler logs: https://storage.googleapis.com/kubernetes-jenkins/logs/kubernetes-e2e-gce-scalability/1539/_artifacts/<IP_ADDRESS>%3A22-kube-scheduler.log

To summarize, my hypothesis is that:

Kubelet syncPods seems to hang in this example
then I don't see any log saying that Kubelet was restarted, but it again starts to process thing
however, due to the reason I don't understand it kills all the pods that were running there

I think that if the Kubelet didn't kill all the pods after again syncing pods, this wouldn't cause test failures. But anyway - there seem to be some problem here.
@dchen1107 @yujuhong - can you please explain what exactly is happening there? I think that this is similar to what was observed in #9895, but I don't understand why all the pods are being killed.
cc @fgrzadkowski @piosz @davidopp @bprashanth

The nodecontroller killed the pods:
I0623 19:14:12.023381       5 nodecontroller.go:388] Adding pods to evict2: 2015-06-23 19:14:12.023366352 +0000 UTC is later than 2015-06-23 19:14:12.02335977 +0000 UTC + 4m20s
I0623 19:14:12.109886       5 podevictor.go:110] PodEvictor is evicting Pods on Node: e2e-scalability-minion-k2n5
I0623 19:14:12.109932       5 nodecontroller.go:427] Delete all pods from e2e-scalability-minion-k2n5

You also see in the kubelet logs:
I0623 18:53:39.083844    3176 kubelet.go:1886] Recording NodeReady event message for node e2e-scalability-minion-k2n5
...

I0623 19:16:01.729467    3176 kubelet.go:1886] Recording NodeReady event message for node e2e-scalability-minion-k2n5

Which is too spaced out for node heartbeats.
As you noted there was a 500 on healthz, this might've led to monit restarting the kubelet though I don't see it in the logs. It seems like there were also memory issues on the node just before the 500 (note the du failure below):
I0623 19:15:59.168733    3176 server.go:608] POST /stats/container/: (6m5.701087699s) 0 [[Go 1.1 package http] <IP_ADDRESS>:54251]
I0623 19:16:00.255319    3176 container.go:369] Failed to update stats for container "/3078d60a22bddaf3852ee52f7a9f1b36df184a3557fa4482abce167f4473bebc": du command failed on /var/lib/docker/aufs/diff/3078d60a22bddaf3852ee52f7a9f1b36df184a3557fa4482abce167f4473bebc with output  - fork/exec /usr/bin/du: cannot allocate memory, continuing to push stats
I0623 19:16:00.465821    3176 server.go:608] POST /stats/container/: (916.691646ms) 0 [[Go 1.1 package http] <IP_ADDRESS>:34666]
E0623 19:16:00.693160    3176 reflector.go:183] watch of *api.Service ended with: 401: The event in requested index is outdated and cleared (the requested history has been cleared [48787/7621]) [49786]
I0623 19:16:00.750086    3176 server.go:608] GET /healthz: (928.173627ms) 500
goroutine 4066 [running]:

I see errors indicating SyncPods is killing containers while the podworker is creating pods (this is normal if you delete as the pods are coming up):
I0623 19:16:03.062023    3176 manager.go:1114] Killing container with id "1554c76fdb2e75b76a7ee49c89871825063b5d33a5e7ef38a174086a7e12f0ea"
...
E0623 19:16:04.047491    3176 manager.go:1533]
Error running pod "density3000-04eebfdf-19db-11e5-bf18-42010af01555-vjjpb_e2e-tests-density-xyfx4" container "density3000-04eebfdf-19db-11e5-bf18-42010af01555": API error (500): Cannot start container 63f1044d574ce513180ae6cb7f6e2c3bbe905145d02b0331fce4df215cb6690a: cannot join network of a non running container: 1554c76fdb2e75b76a7ee49c89871825063b5d33a5e7ef38a174086a7e12f0ea

The pod in the example (density3000-04eebfdf-19db-11e5-bf18-42010af01555-vjjpb) had this happen:

scheduler assigned (19:08:53)
Kubelet picked up (19:08:54)
Node controller deletes (19:14:14)
suspicious 500 (19:16)
kuelet restarts mentioned above (19:16)

Just for my edification, what are the circumstances under which pods can be killed?

explicit user request
kubelet failing healthcheck for longer than the node controller threshold (5 min or whatever it is)
any others? i thought some other issue implied that restarting kubelet kills pods -- but that is not true, is it?

i thought some other issue implied that restarting kubelet kills pods -- but that is not true, is it?

In theory it shouldn't, we should skip deletion till all our sources are ready (need to convince myself that there isn't a race that could lead to container restarts here).

any others?

Containers die with docker restarts and OOMKill. The kubelet won't meddle with the pods in the apiserver directly, if it ends up killing some by mistake it'll notice the next time it syncs and start them.

I didn't observe any such failure in last few days. Are we just lucky or was it fixed? If so - can someone point me to the PR fixing that?

This will still happen if a node goes into the NotReady state at the wrong time. The most common case of this occurrence
is a cluster addon hogging resources. Setting limits should help https://github.com/GoogleCloudPlatform/kubernetes/pull/10260, but I think that pr got reverted.

@bprashanth Is there a dedicated issue for it? If not, maybe we should rename this one (i.e. scalability tests are no longer failing because of that particular reason).

Yes - this is still an issue. The failure with exactly the same logs just happened tonight:
http://kubekins.dls.corp.google.com/job/kubernetes-e2e-gce-scalability/1649/consoleFull
For the reference:

the node that had problems: e2e-scalability-minion-bv49 (<IP_ADDRESS>-22-kubelet.log in GCS)

again there are logs like this:
  2814 I0701 05:44:17.407515   18374 container.go:369] Failed to update stats for container "/2e20533074fb351801e684c5393474f9005f4ba8b450bb664c421e5837d19216": du command failed on /var/lib/do     cker/aufs/diff/2e20533074fb351801e684c5393474f9005f4ba8b450bb664c421e5837d19216 with output  - fork/exec /usr/bin/du: cannot allocate memory, continuing to push stats

This just happened again.
@bprashanth @lavalamp @davidopp
do you think that we should be reporting it as an error in scalability tests? If the Kubelet is dead and node controller is deleting the pods running on that node, ReplicationController will recreate them and they will be scheduled somewhere else. So maybe we should just log it and wait until all of them are running instead of failing the whole test in that situation? Thoughts?

cc @dchen1107
on the other hand, setting limits for addons may also solve this issue

The feeling I got from https://github.com/GoogleCloudPlatform/kubernetes/issues/9788 was, when something starts hogging memory (eg: heapster without cgroup limits) we wait for it to get oom killed. We increase the chances that the oom killer kills the right things by setting oom score. In theory, this should ensure that we never kill a system daemon and the node should not flip into NotReady.
If we somehow end up using 95% memory without hitting the oom limit for 5m, the kubelet will be too slow to update its status and the node controller will kill the pods. The most likely reason to hit this situation is a misbehaving cluster addon. There are other reasons the kubelet might not have updated status in 5m though, eg: goroutine leak leading to cpu starvation, monit restart loop etc. I think the way to handle this is by detecting NotReady up front and dumping information about what was on the node just before it went down (https://github.com/GoogleCloudPlatform/kubernetes/pull/10329, https://github.com/GoogleCloudPlatform/kubernetes/issues/10306).
We could do this in an independent soak test, but I think it indicates system instability.

@dchen1107 this is your hobby horse, I think.
@wojtek-t I'm guessing that setting limits for addons will resolve this, so let's wait for that and see?

@lavalamp

@wojtek-t I'm guessing that setting limits for addons will resolve this, so let's wait for that and see?
I'm fine with waiting - those failures are relatively rare so it's not a big problem to look into them from time to time to check whether it's again the same problem or a new regression.

It seems that setting limits for addongs - #10653 fixed the main issue here (there wasn't such failure since merging that PR).
Currently the only failures are are because of too high latency metrics.

Great -- please close the issue unless you think there is something left to do here. (Other than investigate the latency failures, which is unrelated to this issue.)


Add panels H,L

I've tried to add the code for panels H,L, deducing the names for the data from preceding panels.
However, it appears, the panel labels are mixed up (F with J), perhaps due to some restructuring of the figure.

I changed the figure labels F and J


Implement Frequently Asked Questions (FAQ) Section

Issue Description
As Compressy gains more users, it's essential to provide a comprehensive Frequently Asked Questions (FAQ) section on the website. This will help users find quick answers to common queries and enhance their overall experience.
Tasks

Design and implement a dedicated section on the website for Frequently Asked Questions.
Populate the section with relevant questions and answers.
Ensure the FAQ section is easily accessible and well-integrated into the website's user interface.

Additional Information

Consider the current website design and theme while implementing the FAQ section.
Collaborate with the design team, if needed, to ensure a seamless integration of the FAQ section.

This enhancement will contribute to better user support and engagement.
@0ME9A

some questions on top of my mind, feel free to refine or rephrase the Q/A or add anything else you would like..

Are the files submitted for compression saved anywhere?

No, the submitted files and the generated files do not go to any server. The conversion happens completely in browser.

Does this site use cookies?

Yes, this site uses cookies for statistical and personalisation purposes. Refer to Terms and privacy to know more.

Is this website open sourced?

Yes, it is. The code is publicly available on GitHub at link. Contributions are welcome.

👋 Hi @kishore881,
Thank you for your prompt response and for proactively contributing to the FAQ section! Your questions are excellent, and I appreciate the clarity they bring to potential user inquiries.
I've added a couple more questions to cover various aspects:

How secure is the compression process?

Compressy employs client-side processing, ensuring that your files are compressed locally without being sent to a server. This approach prioritizes user privacy and data security.

Can I compress multiple images at once?

This feature is currently under development. Check out the related issue for updates on implementing bulk image compression.

Feel free to refine or rephrase any questions and answers. Your input is valuable, and I'm excited about the collaborative effort to enhance user support on Compressy.
Best regards,
@0ME9A


CLI: Refactor EventStore & Tests

After moving the CLI to typescript, there are some things which are broken. This is one of them.

@eolszewski I'm assigning this to you, so you can get the feel for using the framework in the CLI and also writing node tests in typescript.
I consider having these tests and command line tools working as pre-alpha blocker.


Files incorrectly parsed as llanfair

It seems that all binary files are being detected as llanfair regardless of if they are actually valid files or not.  One example is a file of all null bytes (cryze thinks this might be a livesplit upload bug but the point still stands) and another will be linked below.
e3315c3e-fc77-455b-866b-7c4e891561be.zip

It's there any magic word, or specific file structure we could look for?

I believe all files should start with the following hex values aced 0005 7372 0016 6f72 672e 6665 6e69 782e 6c6c 616e 6661 6972 2e52 756e

i guess it could be worth checking the whole file for 6f72 672e 6665 6e69 782e 6c6c 616e 6661 6972 2e52 756e (org.fenix.llanfair.Run) but i feel that would be a bit excessive if it's just at the beginning.

You could always just trying slicing the string at 100 or so bytes and then just check that for the header stuff if you didn't want to check the whole file.

So, it appears that the original llanfair just directly serializes the Run object. So in every test I've done it's always started with AC ED 00 05 73 72 00 16 6F 72 67 2E 66 65 6E 69 78 2E 6C 6C 61 6E 66 61 69 72 2E 52 75 6E which evaluates to ¬í..sr..org.fenix.llanfair.Run, so i believe that checking based on that array of bites should be sufficient.

https://docs.oracle.com/javase/7/docs/platform/serialization/spec/protocol.html
stream:
    magic: AC ED
    version: 00 05
    contents -> content -> object -> newObject:
        TC_OBJECT: 73
        classDesc -> newClassDesc:
            TC_CLASSDESC: 72
            className -> (utf):
                len: 00 16
                value: org.fenix.llanfair.Run
            ...

I didn't think there would be such an in depth spec on serialization.  Maybe exporting for llanfair might be possible now :O


Camp Harmony report: linens

Linens requested:
Total number requested for Village 1, 5, 6 and 7 & Wellness center
Total requested for Village 2 (because these are queen sheets, I need them separated out)

Partially complete:
https://harmonyreg.sffmc.org/admin/organization/1/event/1/reports?reportId=7

@bloomingbooks please review the current report and let me know if I can close this issue.

Looks great -- ok to close this ticket.


Conversion error for std::map<int, std::string>

Hi,
I'm trying to save a std::map<int, std::string> into a json, and then the json is saved in a file.
nlohmann::json db;
db = mymap;
std::ofstream output_file(filename);
output_file << std::setw(4) << db << std::endl;

The problem is the result of the json:
I'm expecting this kind of output:
{ 1 : "one", 2 : "two"}
However, the result is:
[ [1, "one"], [2, "two"]]
So, when in other program I'm trying to read that file and try to save it in a json for doing the conversion to std::map again, I'm having the next error:
error: ambiguous overload for ‘operator=’ (operand types are ‘std::map<int, std::__cxx11::basic_string<char> >’ and ‘nlohmann::json {aka nlohmann::basic_json<>}’)

I've been looking in similar errors like #607, but I don't find a solution.
I've tried to build the map manually but the output is the same. Maybe I'm missing something.
Thanks in advance

Keys of JSON objects must be strings:

The library does not convert the keys of the std::map to strings automatically, and under the hood a list of pairs is the closest we can get inside JSON. You need to make the conversion yourself, e.g. with code like
for (auto it = mymap.begin(); it != mymap.end(); ++it)
{
  db[std::to_string(it->first)] = it->second;
}

Thanks,
Now it's working :)

I'm actually ok with  [ [1, "one"], [2, "two"]] but I cant make it work: https://github.com/nlohmann/json/discussions/2378. Any ideas on why?

Nothing broken here:
    std::map<int, std::string> m;
    m[1] = "one";
    m[2] = "two";
    std::cout << json(m) << std::endl;

Output:
[[1,"one"],[2,"two"]]


installation fails for tensorflow-gpu

When attempting to install from pip I get this error:
Could not find a version that satisfies the requirement tensorflow-cpu>=2.7.0 (from tensorflow-gnn) (from versions: 2.8.0rc0)

Admittedly, I have tensorflow-gpu installed. Is this library supposed to be specific to the cpu version?

Have you tried with Python 3.9 version?
When I read "setup.py" code, it looks like required Python 3.9 or up. This may be due to Tensorflow 2.7 supported only Python 2.9 and up.

I am also having this problem on an m1 mac:

Requirement already satisfied: six in /opt/homebrew/Caskroom/miniforge/base/envs/tf_mac/lib/python3.9/site-packages (from tensorflow-gnn==0.1.0) (1.15.0)
ERROR: Could not find a version that satisfies the requirement tensorflow-cpu>=2.7.0 (from tensorflow-gnn) (from versions: none)
ERROR: No matching distribution found for tensorflow-cpu>=2.7.0

This should be fixed with the 0.2.0 upload to PyPI. Please open another issue if you encounter further problems with pip install tensorflow_gnn


Fix logger undefined

Fixes #4412
When loggerOptions is explicitly set to undefined, it leads to "Cannot read options of undefined" error which breaks the application. This PR makes loggerOptions optional to address this.

Codecov Report

Merging #5355 (6587ce1) into dev (0596334) will decrease coverage by 0.03%.
The diff coverage is 69.23%.

Flag
Coverage Δ

*Carryforward flag

msal-angular
96.50% <ø> (ø)

Carriedforward from 0596334

msal-browser
86.47% <100.00%> (ø)

Carriedforward from 0596334

msal-common
85.45% <100.00%> (ø)

Carriedforward from 0596334

msal-core
82.84% <100.00%> (ø)

Carriedforward from 0596334

msal-node
82.48% <0.00%> (-0.43%)
:arrow_down:

msal-node-extensions
76.03% <ø> (ø)

Carriedforward from 0596334

msal-react
94.50% <ø> (ø)

Carriedforward from 0596334

node-token-validation
88.88% <100.00%> (ø)

Carriedforward from 0596334

*This pull request uses carry forward flags. Click here to find out more.

Impacted Files
Coverage Δ

...rc/interaction_client/StandardInteractionClient.ts
97.00% <ø> (ø)

lib/msal-node/src/client/ClientApplication.ts
70.79% <0.00%> (-2.84%)
:arrow_down:

lib/msal-browser/src/app/ClientApplication.ts
95.01% <100.00%> (ø)

lib/msal-common/src/logger/Logger.ts
94.02% <100.00%> (ø)

lib/msal-core/src/UserAgentApplication.ts
72.61% <100.00%> (ø)

...ib/node-token-validation/src/api/TokenValidator.ts
98.51% <100.00%> (ø)


[Bug] display of contentWidget is forcefully set to display none

Reproducible in vscode.dev or in VS Code Desktop?

[X] Not reproducible in vscode.dev or VS Code Desktop

Reproducible in the monaco editor playground?

[X] Not reproducible in the monaco editor playground

Since updating our Monaco Editor from 28.0 to 33.0 the content widget does no longer display. It has a style property set to display: none.
Is there anything that might causes this? Or is it preventable.
Reproduction Steps
It is not reproducible without including our 1000+ line editor.
Actual (Problematic) Behavior
The content widget initial state is set to display: none.
Expected Behavior
The content widget should not be hidden, or an error explaining why it is not showing correctly should be added.
Additional Context
No response

Unfortunately we only have resources to provide support for bugs we can reproduce with the standalone monaco editor. Feel free to create a new issue with steps on how to reproduce!

That's the problem I do not know what is causing the issue. Thus I do not have an example to show you guys.


Fix unpaid items are counted

Fix this:
https://github.com/user-attachments/assets/2c6ecc00-5b8e-4401-841c-fab7b57be939
Tested with anon and logged in. Also tested with items that were paid with fee credits (invoiceActionState IS NULL).

I just searched for models.item.count and also fixed it for ncomments. I also noticed that auctionPosition also calls models.item.count but it already uses item.status which is enough afaict.


How to recover Back-up

Hi
This is a very interesting project and I would like to use it to back-up some ZFS dataset, the installation manual make pretty clear on how to push to S3-Glacier (zfs send)
But I don't see in the instructions (and in the source-code neither) on how to retrive a back-up
Thankfully I don't need to retrive it (yet)
What should be the restore/recover procedure?
Thanks,
Luca

Sorry about the lack of reply on this, I did go through that process, but I have since switched to btrfs solely to avoid licensing issues. So I am no longer investing in this project.

It's however just zfs snapshots dumped on s3, so recovery would follow the same process as if you did that manually. It's intentionally quite dumb.


Slider

Element UI version
2.2.0
OS/Browsers version
safari
Vue version
2.5.13
Reproduction Link
jsfiddle.com/idonthave
Steps to reproduce
other-1e4bc.firebaseapp.com
What is Expected?
Slider like other.
What is actually happening?
don't slide good.

Issues without a valid reproduction link will be closed directly.


add: unit test of translate / setting

run unit test
// package.json
{
  "scripts": {
    // ...
    "unit_test": "yarn run jest"
  },
}

You can try edit translation (like:bundle.l10n.pt-br.json), and run the unit test , to see unit test result

other scripts, you can refer my pack
https://github.com/CoffeeChaton/vscode-autohotkey-NekoHelp/blob/ecc03a1722351ad0eefd1ea6ea0fc9e65b3b41a0/package.json#L26-L48

Hi! Thank you for contributing to this project, unfortunately when I started this project, it had three rules:

The extension will not use React, Tailwind or similar libs to render the UI.
The extension need to be light.
The extension will not have unity tests.

The first two are definitives. The last one isn't, but for now I will keep it. So, I will close this PR for now, but maybe I re-open it in the future.

ok


Match Rating display on Battle page

May or may not explode, combust, detonate, or release cockroaches in the server room

I've had a chance to look at the code, you were very close. It was actually @modoptions not @tags. If you make that change I'll be happy to merge the PR :)

Will test on integration server :)


Why does the toast needs the view and the context?

You can just get the context from the view.

Thanks for the good suggestion, I have modified the api in @e9b26c5 and released 1.1.3.