feat: report a user friendly error message on data plane failed states

Description
https://issues.redhat.com/browse/MGDSTRM-6982 - report a user friendly error message on data plane failed states
Checklist (Definition of Done)

[X] All acceptance criteria specified in JIRA have been completed
[X] Unit and integration tests added that prove the fix is effective or the feature works (tested against emulated and non-emulated OCM environment)
[ ] Documentation added for the feature
[X] CI and all relevant tests are passing
[ ] Code Review completed
[ ] Verified independently by reviewer
[ ] All PR comments are resolved either by addressing them or creating follow up tasks
[ ] Required metrics/dashboards/alerts have been added (or PR created).
[ ] Required Standard Operating Procedure (SOP) is added.
[ ] JIRA has been created for changes required on the client side

My understanding is that the issue is that the FailedReason attribute of the Kafka request ends up being shown in the UI side, and sometimes we show information that might be sensitive or not really relevant to the end user.
This could be the case when information about a Secret is shown but that's not the only case. For that reason I think the set of changes should be more generic instead of checking a specific error message content.
I would take the approach in the following way:
In the setKafkaClusterFailed set FailedReason to a literal string like "Kafka  status reported as failed from the data plane" and then log with the logger the real error message.

cc @davidffrench to confirm if what I wrote in my previous comment (https://github.com/bf2fc6cc711aee1a0c2a/kas-fleet-manager/pull/1174#issuecomment-1178847859) matches the expectations of the original issue.
The implication is that the end-user will not see nor be able to see details on why it failed when the data plane reports the kafka with the ready condition to value error

I also observed that in the PR there are several commits but they seem to all be related to the same functionality. Please squash them once the functionality is ready. Thanks.

My understanding is that the issue is that the FailedReason attribute of the Kafka request ends up being shown in the UI side, and sometimes we show information that might be sensitive or not really relevant to the end user. This could be the case when information about a Secret is shown but that's not the only case. For that reason I think the set of changes should be more generic instead of checking a specific error message content.
I would take the approach in the following way: In the setKafkaClusterFailed set FailedReason to a literal string like "Kafka status reported as failed from the data plane" and then log with the logger the real error message.

+1

Thanks @miguelsorianod @machi1990 ! Just added the changes.

Thanks @valeriiashapoval. It seems like the tests are failing for a related change in this PR. Can you have a look?


Exception in OTransactionOptimistic (v.2.0)

Hi i m inserting a new Object and give this exception
throw new OSchemaException("Record saved into cluster " + iClusterName + " should be saved with class "
+ clusterIdClass + " but saved with class " + recordClass);
Seeing runtime in debug :
Class has  2 cluster : 3 and 22 .
Default cluster for class is 22.
The problem is rid.clusterId contains 3 not 22. When code call  getClassByClusterId(3) give another class.
I think is a bug in 2.0 cause in the previous i havent this error.
final ORecordSchemaAwareAbstract recordSchemaAware = (ORecordSchemaAwareAbstract) iRecord;
final OClass recordClass = recordSchemaAware.getSchemaClass();
final OClass clusterIdClass = database.getMetadata().getSchema().getClassByClusterId(rid.clusterId);
if (recordClass == null && clusterIdClass != null || clusterIdClass == null && recordClass != null
|| (recordClass != null && !recordClass.equals(clusterIdClass)))
throw new OSchemaException("Record saved into cluster " + iClusterName + " should be saved with class "
+ clusterIdClass + " but saved with class " + recordClass);

@publicocean0 Could you please retry with a more recent version of OrientDB, like 2.1.2?

this problem i remember.... I  solved with a little trick : i moved the position in the code where i put setAbstract .... in this way i had no more problems. Anyway the problem in orientdb was in a block of code where you set Abstract .... inside the function there was a bug.

@publicocean0 do you remember what king of bug?

It was a previous version surely .... I remember  that when you set abstract inside the function was not reinitiealized all the data structure  correctly  so when you call this function in particular  moments you create a inconsistent state. For this reason there was a error as
"The problem is rid.clusterId contains 3 not 22".

the cluster selection is evolved a lot since 1.7.*, this should be already fixed by the various refactor, i'll close it, if happen again we can reopen it.


Implement iCEM

There is a newer version of CEM that uses colored noise, which is correlated in time. This paper describes the method, along with several additional improvements. Having this as a new agent (or a modified version of CEMAgent) would be a great addition.

Hi @luisenp. I have been working on an implementation of iCEM but have run into an issue when using GaussianMLP ensembles. iCEM uses a decaying population size, but this results in the population batch size to not be a multiple of the number of models in the ensemble. What's the reason for the batch size to be a multiple of ensemble size? Can you think of a workaround? Thanks

Hi @sradicwebster, thanks for the interest! The reason for this restriction is due to an optimization in the ensemble propagation of GaussianMLP, as described here, and implemented here. This makes the code about 2X faster than the approaches I tried for sampling and indexing the models independently.
For testing iCEM you could use BasicEnsemble (see example), and also try it for control with ground truth dynamics (extending this script).
For GaussianMLP, we could try adding an option to always round up population size to a multiple of the ensemble. If it performs similarly on our other tests, it might be a good compromise.

Thanks for your reply. I've been a little busy, but have been able to put some more time to this.
I have done what you suggested for Gaussian MLP Ensemble and rounded the population size up to a multiple of the ensemble size. Running quick tests on cartpole shows better performance for a smaller population for iCEM vs CEM (although the runtime is longer). I have limited compute resources, so am unable to perform many experiments or do hyperparameter tuning.
I have some issues running iCEM with the ground trust dynamics using the control_env script due to the multiprocessing, would you be able to have a look for me?
Is the best thing now for me to submit a pull request?

Hi @sradicwebster. That's great! Yes, a pull request would be ideal. I can then take a look at the code, run your examples and do bigger tests.


Add a test for slice(None) to RawIO testing

We test for slice(None) in SpikeInterface which according to the docstring of get_analogsignal_chunk should be an acceptable channel_indexes type. I changed BiocamRawIO in a non-compliant way, but the tests missed this. We should add some quick test for giving slice(None) to make sure our RawIO's accept this (based on SpikeInterface testing I think most should already be fine)

@h-mayorquin, this way we don't forget to add this to testing :)


Update discord_integration.py

Please check if the PR fulfills these requirements

[ ] Tests have been conducted on the PR
[ ] Docs have been added / updated

What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
A fix for the discord_integration.py file so it works.

What is the current behavior? (You can also link to an open issue here)
Discord_integration.py is out of date

What is the new behavior (if this is a feature change)?
Discord_integration.py is now fixed to work with latest version of d.py

Does this PR introduce a breaking change? (What changes might users need to make in their application due to this PR?)
No

Other information:

youve included your credentials in this pull request. I would suggest deauthorizing that token

youve included your credentials in this pull request. I would suggest deauthorizing that token

Fixed and it's revoked, thanks.

Fixed and it's revoked, thanks.

outdated


Issues in Agent

[x] When user opens the Details popup for an existing agent and then clicks in Add Agent button, the popup opened in non-edit mode. User needs to click on button Edit to start adding data to the popup

[x] If user tries to type text in any disable input field while the New Agent popup is in edit mode, the validators appear. If the inputs are disable, validators will not be displayed.

[x] Delete one or more agents from the list and then create a new one. When opening the edit or details popup of the new created Agent, the information in the popup corresponds to one of the deleted agents

Tested and it's working as expected

Tested and it's working as expected


Fix #48

@mattiascibien Here is the new syntax, but with everything squashed in a single commit, so as not to pollute the commit history too much.

Merged


pull request for e2e test at 12/04/2016 02:26:03

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


fix: Installer improvements and bug fixes

- What I did

Made the tar unpacking less verbose so the installer is cleaner
added logrotation to the non-tmux installation option which closes #175
merged updater into installer

Checks if the service type is cron, and adds a logrotate line to crontab if it is
Checks to see if there was an existing cron entry for this service before trying to start sshnpd (i.e. only start if it is truly the first install)
closes #203

- How I did it
- How to verify it
- Description for the changelog
fix: Installer improvements and bug fixes

@JeremyTubongbanua I've removed the mandatory tag

From what I've seen it called:
flags = no value after (--help, -u) are flags
options = value after (-c, -d, -n) are options


[Q] ExcelJS version ES5 clear format of template

💬 Questions and Help
Hi,
Thanks for your wonderful package ExcelJS. In my personnal computer with NodeJS v10, output file works like a charm. But in my PC at work with NodeJS v8, I have to require ExcelJS version ES5, always with the same template, output file lost all format and I cannot add tables, images to worksheet.
Any help? Thanks in advance.
P/S: my navigator is Microsoft Edge version 81.0.416.53; NodeJS v8.11.3; Typescript v3.9.6
I have import ExcelJS as below:
require('core-js/modules/es.promise');
require('core-js/modules/es.string.includes');
require('core-js/modules/es.object.assign');
require('core-js/modules/es.object.keys');
require('core-js/modules/es.symbol');
require('core-js/modules/es.symbol.async-iterator');
require('regenerator-runtime/runtime');
const Excel = require('exceljs/dist/es5');
const workbook = new Excel.Workbook();

When I make npm install exceljs, I found that I didn't have these packages in my PC. So is that the cause?
npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none is installed. You must install peer dependencies yourself.
npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none is installed. You must install peer dependencies yourself.


Generated Images are 512x512 using  stable-diffusion-v1-4, how can I generate higher res?

We have super resolution running on device. Does an excellent job of enlarging - reduces noise, sharper lines while increasing resolution.

Also SD 2 has weights trained at 768, so I suppose you could use that model and increase the output shape to 768 in the convert to coreml script. But, that means inference time and RAM requirements will double.

Hi @3DTOPO, have you managed to use huggingface.co/stabilityai/stable-diffusion-2? I got a runtime error below.
Traceback (most recent call last):
  File "/opt/homebrew/anaconda3/envs/coreml_stable_diffusion/lib/python3.8/runpy.py", line 194, in _run_module_as_main
    return _run_code(code, main_globals, None,
  File "/opt/homebrew/anaconda3/envs/coreml_stable_diffusion/lib/python3.8/runpy.py", line 87, in _run_code
    exec(code, run_globals)
  File "/Users/coder/hub/ml-stable-diffusion/python_coreml_stable_diffusion/pipeline.py", line 534, in <module>
    main(args)
  File "/Users/coder/hub/ml-stable-diffusion/python_coreml_stable_diffusion/pipeline.py", line 478, in main
    image = coreml_pipe(
  File "/Users/coder/hub/ml-stable-diffusion/python_coreml_stable_diffusion/pipeline.py", line 354, in __call__
    image = self.decode_latents(latents)
  File "/Users/coder/hub/ml-stable-diffusion/python_coreml_stable_diffusion/pipeline.py", line 200, in decode_latents
    image = self.vae_decoder(z=latents.astype(np.float16))["image"]
  File "/Users/coder/hub/ml-stable-diffusion/python_coreml_stable_diffusion/coreml_model.py", line 79, in __call__
    return self.model.predict(kwargs)
  File "/opt/homebrew/anaconda3/envs/coreml_stable_diffusion/lib/python3.8/site-packages/coremltools/models/model.py", line 509, in predict
    return self.__proxy__.predict(data)
RuntimeError: {
    NSLocalizedDescription = "Error computing NN outputs.";
}

I got exactly the same error as @dreampuf trying to run SD V2 on Python 3.10.6

I got the same error when I used a CoreML model I converted myself. When I used a pre-converted model from Apple's repo on HuggingFace, SD2base successfully ran in Python using Terminal.
I don't know how to make SD2.1 work, how to increase resolution to 768, or how to upscale


Enhancement Request: cache speech snippets

It is expensive to call gTTS() for each speech snippet: requests are made over-the-net, and can take many seconds each to generate. Oftentimes a specific snippet has already been generated, so blindly calling out to gTTS() each time can be bypassed.
=> Implement a caching mechanism by which each line of the text file's resultant snippet gets saved locally with a unique filename, and if that specific snippet already exists, just re-use it instead of calling gTTS() all over again.
Q: What filename extension to use for filetype? mp3?
Q: Are there any limitations on the filename, if we just base it on the exact contents of the speech phrase? E.g., "Hi, my name is Duane." would become Hi, my name is Duane..mp3.

Implemented rudimentary caching system in commit

Early profiling indicates the calls to gTTS() are not the bottleneck. It looks like the call to stictch everything together is what is taking so much time.


Select Multiple height when initially loaded vs. populated

I have an interface that loads preselected options inside a multi-select box. When react is loading the element, the height seems to be determined on an empty select box, which then renders other elements on top or below the select box. When I do anything to either element, react re-renders them, and then they look fine. Any ideas?
This is wrong...

This is right!

Hmm. I'm not sure exactly what's going on here, but I've seen similar artifacts happen as a result of the autosized input. See if you still experience the issue if you set
autosize={false}

If it is autosize-related, try passing in
inputProps={{onAutosize: this.forceUpdate}}

Closing this out. Please reopen if you can create an example I can replicate.

@tsnevillecom Are you using flexbox for positioning by any chance?

@FranDias Yes. Sorry for the delay.


refactor: define detailed error types

A clearer interface exposed by service.
RPC state machine is removed and generated by macros now.

A part of #307 and #349.

PTAL @cutecutecat


Add ability to swap distro

Adds input for swappable disto.

Please also add a signed-off-by line, which can be done using:

git commit --amend --signoff
git push -f

Thanks for your feedback, changes added.

Implemented slightly differently, in https://github.com/tailscale/github-action/pull/72


Update README.md (Some small spelling stuffs)

Same small spelling stuffs.

And thus ist also better:
Using pugixml

Merge first, thanks


Optional yaml definitions

When resolving YAML, if missing the definitions for one of the languages that are being generated a descriptive error message will be printed. For instance, when running djinni with --cppcli-out, if any of the keys for cs are missing the generation will fail with the following error:
/path/to/file.yaml (1.1): missing 'cs' definitions

That was achieved by making most fields of MExtern optional, requiring a call to get to be able to access their values; the check that generates the error message above ensures that any Option[...] field will have Some(value) (i.e. not None) by the time we call get on it.
In order to have the command line parameters available when resolving the YAML definitions I had to shuffle some code in Main.scala, causing a few lines that were originally in the "generation" phase to be executed during the "resolving" phase.
Fixes https://github.com/cross-language-cpp/djinni-generator/issues/48.

Support lib tests pass with this code (C# wasn't tested).

Awesome @jothepro! Really appreciate the feedback and suggested improvements.


Using jwt as django auth backend?

it's related to https://github.com/davesque/django-rest-framework-simplejwt/issues/130
I'm wondering if I could use single jwt auth backend for DRF and django views
(asked in SO as well https://stackoverflow.com/questions/57646299/django-jwt-authentication-in-django-view-not-just-drf/57646409#57646409)
In our app, we have webview and native android httpclient, and react-native.
If we have to use cookie session-id for django-view and jwt-token for drf, we have to sync cookie and jwt-token among webview/android/react-native.
It will be much easier for us just sync jwt-tokens but not sure if its possible or it is something not advised?

There’s a PR for SPAs at #157 which can help. I’m not for it because I’m still skeptical of security vulnerabilities (typically, if you want JWT tokens for desktop, go with OAuth protocol too instead of only JWT).
There are plenty of articles that differentiate when you use only JWT tokens and when to use JWT tokens with OAuth protocol.


Introduce remote-process bash completion

When working with the parameter-framework,
the remote-process command is very handy.
Nevertheless it has long commands and it is easy to make mistakes.
Add a bash completion script to complete:

hostnames
frequently used port
commands and arguments based on the remote usage (help command)

:+1:

:+1:


[PAR-443] fix: update HyperLink component

PAR-443
Update HyperLink component to use Paragon icon Launch instead of loading icon from font-awesome library.
HyperLink component (after change)

Coverage remained the same at 89.788% when pulling d6beaccc6536c0e1842834e90ff2239dccb08a42 on saad/PAR-443 into 9cd6650575ed907efdaf93361712dbc00df29b4d on master.

FYI -- @abutterworth


Adding root url

Add functionality to enable prefixed url location with rails into angularJS coffescript.
Also, fix a bug to allow 100 projects max rather than just 20.

:+1:


Install: Adapters Detect Existing Mesh

Description
Whether a user is running Meshery in or out of a cluster, it does not require users to configure connections to its adapters. In the same fashion that Meshery is cognizant of its own adapters, establishes connection to them and verifies their status, so too, should Meshery use its adapters to detect the presence of a previously deployed service mesh. To facilitate time-to-value in using Meshery, adapters automatically detect existing service mesh deployments.
Behavior

[ ] After v0.3.0, Meshery users can click on an adapter to verify connectivity between Meshery and the adapter. Users also need to ability to click on an adapter to detect the presence of an existing service mesh deployment (each adapter will look for its specific type of service mesh).
[ ] Users should be able to invoke an ad-hoc detection operation using each or any adapter.

Implementation and Related Challenges
Each adapter will implement detection in a manner that is specific to its type of service mesh. Support for this functionality will be tracked under each individual adapter's repository.

[ ]  Create a new operation in Meshery UI.
[ ] Set Meshery to automatically run this operation upon registration of / connection to an adapter.

This is related to #321, just realized it.

Duplicated by #781

Completed


Nillable collections + HashSet Type + Typos corrections

Hi !
I propose some modifications :

Prevent initialization of collections in constructor when the element is marked as nillable (null is different from empty)
Adding HashSet as a possible collection type
Corrected various typos in the code

Updated the package version
corrected the comments generation that was buggy

Does it work, and don't mess up any tests?

All tests are ok except the DVD one (that was already not working)
Although we may need strong tests with comparison with target code generation (for now, tests only check that the generated code compiles)


auto-complete does not set work items to be complete

For a repository with a branch policy that requires a work item be attached to the pull request, I would expect that if work items are supplied via --work-item then they would be completed.
git pr create --auto-complete --delete-source-branch --work-item 331 --open
However, the PR displays the following status:
Changes will be merged into master. Branch blahblahblah will be deleted. Work items will be unchanged.
If that's not the case, then do we need another command line option to indicate that should happen?

@flcdrg  Thanks for pointing this out.  Yes, we should definitively add that.

Fixed in dev branch: #171

The fix is now available in VSTS-CLI 0.1.2


Support modifiers for generated traits

e.g. private[package], sealed, etc.

CI is a bit flaky, seems like there is some sort of race condition.

Thanks!
CompileSpec requires the files generated by GeneratorSpec. The order of platforms is set correctly when running tests from the root project, but I think the problem is that writeToFile does not wait for the file to be written to disk before returning (apparently flushing the stream is not enough?). I've addressed that, let's hope this fixes it.


What happens if an auto-import fails (due to misconfiguration or bug)? Silent failure or something clearer?

investigate the behavior. there are rumors things work well already

for this
println("before")
import o1._
import o1.tra in._
println("after")
sys.props("user.dir")

the results are

eventually, the message still contains the names of the imported modules (even if they are not), also, a problem is, that the file is invisible for the user by default, but making that visible conditionally is something that I do not like

good enough according to stakeholders, reopen if becomes an issue


New version: ArbNumerics v0.6.9

Registering package: ArbNumerics
Repository: https://github.com/JeffreySarnoff/ArbNumerics.jl
Created by: @JeffreySarnoff
Version: v0.6.9
Commit: 7e70589bfb21406bdf8a09ca03eeed9d40e78596
Reviewed by: @JeffreySarnoff
Reference: https://github.com/JeffreySarnoff/ArbNumerics.jl/commit/7e70589bfb21406bdf8a09ca03eeed9d40e78596#commitcomment-35637471

Your new version pull request does not meet all of the guidelines for automatic merging.
Specifically, your pull request does not meet the following guidelines:

The following dependencies do not have a compat entry that has an upper bound: Readables

If you want to prevent this pull request from being auto-merged, simply leave a comment.
(If you want to post a comment without blocking auto-merging, you must include the text [noblock] in your comment.)

It is important to note that if your pull request does not meet the guidelines for automatic merging, this does not mean that your pull request will never be merged. It just means that your pull request will require manual review by a human.

These guidelines are intended not as requirements for packages but as very conservative guidelines, which, if your new package or new version of a package meets them, it may be automatically merged.

On a separate note, I see that you are registering a release with a version number of the form v0.X.Y.
Does your package have a stable public API? If so, then it's time for you to register version v1.0.0 of your package. (This is not a requirement. It's just a recommendation.)
If your package does not yet have a stable public API, then of course you are not yet ready to release version v1.0.0.

[noblock]

Your new version pull request met all of the guidelines for automatic merging.
I will automatically merge this pull request during the next cron job.
If you want to prevent this pull request from being auto-merged, simply leave a comment.
(If you want to post a comment without blocking auto-merging, you must include the text [noblock] in your comment.)

On a separate note, I see that you are registering a release with a version number of the form v0.X.Y.
Does your package have a stable public API? If so, then it's time for you to register version v1.0.0 of your package. (This is not a requirement. It's just a recommendation.)
If your package does not yet have a stable public API, then of course you are not yet ready to release version v1.0.0.

[noblock]

Your new version pull request met all of the guidelines for automatic merging.
I will automatically merge this pull request during the next cron job.
If you want to prevent this pull request from being auto-merged, simply leave a comment.
(If you want to post a comment without blocking auto-merging, you must include the text [noblock] in your comment.)

On a separate note, I see that you are registering a release with a version number of the form v0.X.Y.
Does your package have a stable public API? If so, then it's time for you to register version v1.0.0 of your package. (This is not a requirement. It's just a recommendation.)
If your package does not yet have a stable public API, then of course you are not yet ready to release version v1.0.0.

[noblock]


Add a config key to support script-specific locales

Issue: You can not set "Simplified Chinese" or "Traditional Chinese" for multilingual section.
Chinese people living in mainland China uses Simplified Chinese, and people living in outside of the mainland (e.g. Hong-kong, Taiwan, Macau) uses Traditional Chinese. It's a very important difference. So, let's make it enable to choose these type of locale. I tested the multilingual sections with "Simplified Chinese" and "Traditional Chinese", and there's no problem.
Q. Why script-specific languages originally excluded?
A. There was no reason. See:
https://github.com/concrete5/concrete5/commit/a66e1507d4784d9f777cfac031ff74dd8efe246c#commitcomment-35135337

FYI @hissy this broke installation completely so I have reverted it.

@aembler Could you tell me how it broke your site completely? It is already working for my client's website.

It didn’t break the site - it broke installation. I couldn’t install the release candidate with it applied
Sent from my iPhone

On Sep 23, 2019, at 7:19 PM, Takuro Hishikawa<EMAIL_ADDRESS>wrote:

@aembler Could you tell me how it broke your site completely? It is already working for my client's website.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

Alright, I'll test installation.

@aembler I've pushed the fix for installation page, but should I create a new pull request?

Sure let's add another pull request with everything – since I reverted the entire original pull request


Support --pip-version 24.1 and Python 3.13.

Pex has been testing against Python 3.13 alpha and then beta releases
for a while now using a patched Pip with Python 3.13 support. Those
patches have made it into the Pip 24.1 release; so now Pex can
officially support Python 3.13.
The Pip 24.1 release notes: https://pip.pypa.io/en/stable/news/#v24-1
Closes #2406

I do thing it's interesting/confusing that pex has a vendored packaging and uses the packaging vendored in pip as well. I know their usecases/needs are different but I wonder if this might cause issues down the road.

Agreed. One thing I started on in 2020 but never finished since its somewhat frivolous and self-defeating, is a massive re-structure of Pex modules to clearly delineate code needed at PEX runtime from code needed by the Pex tool at build time. The vendored Pip is only in the latter set and does not get included in a PEX files .bootstrap/ code, but the PEX bootstrap does need to evaluate both markers and specifiers, which it relies on packaging for. So this is the origin of the need for a a separate vendoring. It could be done differently though. Perhaps Pex could pluck out Pip's vendored packaging and re-vendor just that portion of Pip in the PEX .bootstrap/... except that PEX files can support Python 2.7 ~through 3.13 and no packaging works with all those versions; so currently you'll find this perhaps surprising thing:
;: pex -o empty.pex

:; zipinfo -1 empty.pex | grep packaging
.bootstrap/pex/vendor/_vendored/packaging_20_9/
.bootstrap/pex/vendor/_vendored/packaging_20_9/__init__.py
.bootstrap/pex/vendor/_vendored/packaging_20_9/packaging/
.bootstrap/pex/vendor/_vendored/packaging_20_9/packaging/__about__.py
.bootstrap/pex/vendor/_vendored/packaging_20_9/packaging/__init__.py
.bootstrap/pex/vendor/_vendored/packaging_20_9/packaging/_compat.py
.bootstrap/pex/vendor/_vendored/packaging_20_9/packaging/_structures.py
.bootstrap/pex/vendor/_vendored/packaging_20_9/packaging/_typing.py
.bootstrap/pex/vendor/_vendored/packaging_20_9/packaging/markers.py
.bootstrap/pex/vendor/_vendored/packaging_20_9/packaging/py.typed
.bootstrap/pex/vendor/_vendored/packaging_20_9/packaging/requirements.py
.bootstrap/pex/vendor/_vendored/packaging_20_9/packaging/specifiers.py
.bootstrap/pex/vendor/_vendored/packaging_20_9/packaging/tags.py
.bootstrap/pex/vendor/_vendored/packaging_20_9/packaging/utils.py
.bootstrap/pex/vendor/_vendored/packaging_20_9/packaging/version.py
.bootstrap/pex/vendor/_vendored/packaging_20_9/pyparsing.py
.bootstrap/pex/vendor/_vendored/packaging_21_3/
.bootstrap/pex/vendor/_vendored/packaging_21_3/__init__.py
.bootstrap/pex/vendor/_vendored/packaging_21_3/packaging/
.bootstrap/pex/vendor/_vendored/packaging_21_3/packaging/__about__.py
.bootstrap/pex/vendor/_vendored/packaging_21_3/packaging/__init__.py
.bootstrap/pex/vendor/_vendored/packaging_21_3/packaging/_manylinux.py
.bootstrap/pex/vendor/_vendored/packaging_21_3/packaging/_musllinux.py
.bootstrap/pex/vendor/_vendored/packaging_21_3/packaging/_structures.py
.bootstrap/pex/vendor/_vendored/packaging_21_3/packaging/markers.py
.bootstrap/pex/vendor/_vendored/packaging_21_3/packaging/py.typed
.bootstrap/pex/vendor/_vendored/packaging_21_3/packaging/requirements.py
.bootstrap/pex/vendor/_vendored/packaging_21_3/packaging/specifiers.py
.bootstrap/pex/vendor/_vendored/packaging_21_3/packaging/tags.py
.bootstrap/pex/vendor/_vendored/packaging_21_3/packaging/utils.py
.bootstrap/pex/vendor/_vendored/packaging_21_3/packaging/version.py
.bootstrap/pex/vendor/_vendored/packaging_21_3/pyparsing.py
.bootstrap/pex/vendor/_vendored/packaging_23_1/
.bootstrap/pex/vendor/_vendored/packaging_23_1/__init__.py
.bootstrap/pex/vendor/_vendored/packaging_23_1/packaging/
.bootstrap/pex/vendor/_vendored/packaging_23_1/packaging/__init__.py
.bootstrap/pex/vendor/_vendored/packaging_23_1/packaging/_elffile.py
.bootstrap/pex/vendor/_vendored/packaging_23_1/packaging/_manylinux.py
.bootstrap/pex/vendor/_vendored/packaging_23_1/packaging/_musllinux.py
.bootstrap/pex/vendor/_vendored/packaging_23_1/packaging/_parser.py
.bootstrap/pex/vendor/_vendored/packaging_23_1/packaging/_structures.py
.bootstrap/pex/vendor/_vendored/packaging_23_1/packaging/_tokenizer.py
.bootstrap/pex/vendor/_vendored/packaging_23_1/packaging/markers.py
.bootstrap/pex/vendor/_vendored/packaging_23_1/packaging/metadata.py
.bootstrap/pex/vendor/_vendored/packaging_23_1/packaging/py.typed
.bootstrap/pex/vendor/_vendored/packaging_23_1/packaging/requirements.py
.bootstrap/pex/vendor/_vendored/packaging_23_1/packaging/specifiers.py
.bootstrap/pex/vendor/_vendored/packaging_23_1/packaging/tags.py
.bootstrap/pex/vendor/_vendored/packaging_23_1/packaging/utils.py
.bootstrap/pex/vendor/_vendored/packaging_23_1/packaging/version.py
.bootstrap/pex/vendor/_vendored/setuptools/pkg_resources/_vendor/packaging/
.bootstrap/pex/vendor/_vendored/setuptools/pkg_resources/_vendor/packaging/__about__.py
.bootstrap/pex/vendor/_vendored/setuptools/pkg_resources/_vendor/packaging/__init__.py
.bootstrap/pex/vendor/_vendored/setuptools/pkg_resources/_vendor/packaging/_compat.py
.bootstrap/pex/vendor/_vendored/setuptools/pkg_resources/_vendor/packaging/_structures.py
.bootstrap/pex/vendor/_vendored/setuptools/pkg_resources/_vendor/packaging/markers.py
.bootstrap/pex/vendor/_vendored/setuptools/pkg_resources/_vendor/packaging/requirements.py
.bootstrap/pex/vendor/_vendored/setuptools/pkg_resources/_vendor/packaging/specifiers.py
.bootstrap/pex/vendor/_vendored/setuptools/pkg_resources/_vendor/packaging/utils.py
.bootstrap/pex/vendor/_vendored/setuptools/pkg_resources/_vendor/packaging/version.py

So its worse than you thought, but required to ensure the PEX can boot under various pythons and not choke on syntax errors in the packaging code it needs to run.


Update example for nhc_check of chronyd

https://github.com/CSC-IT-Center-for-Science/fgci-ansible/commit/54377214f1cced65ac071f654c1c864cb09da1f9#commitcomment-20759236

From Ivan:

What differs are "System time" and "RMS offset", they should be
something like 0.000xxxx and if any larger, then there is a problem.

[root@opt51 ~]# chronyc tracking
Reference ID    : <IP_ADDRESS> (admin2.int.triton.aalto.fi)
Stratum         : 4
Ref time (UTC)  : Wed Feb  8 11:36:58 2017
System time     : 16042.547851562 seconds fast of NTP time
Last offset     : +0.000022398 seconds
RMS offset      : 4569.594238281 seconds
Frequency       : 14.935 ppm slow
Residual freq   : +0.109 ppm
Skew            : 0.550 ppm
Root delay      : 0.001550 seconds
Root dispersion : 0.019479 seconds
Update interval : 70.5 seconds
Leap status     : Normal

From the nhc mailing list:
* || check_cmd_output -t 2 -m '!/: [0-9]{3,}\.[0-9]+ seconds [a-z]+ of NTP time/' chronyc tracking

This command seems to work on my test system - it doesn't drain the node if time is in sync. Have asked reporter via other channels if the check above drains a node where the clock is off.


N27: Release

Part of #818
Netlify preview (a6d3c5f): https://sharp-aryabhata-9cc78b.netlify.app/news/027

FYI the youtube link to the recording of the Rust Gamedev meetup leads to a private video
(https://youtu.be/ta2HY4lD3iM)

FYI the youtube link to the recording of the Rust Gamedev meetup leads to a private video (https://youtu.be/ta2HY4lD3iM)

True, let me go fix that

:+1: Merging in ~1 hour if no objections.


"Unbreakable" nodes are TNT-able

This is an easy fix (add on_blast = function() end to the definitions), but I wanted to check to see if this was perhaps the intended behaviour. I can create a PR if someone else thinks it's a problem.

I think it is a very big problem. If i am a host of a TNT server, if i want to protect some place (such as spawn), i can't do it because this bug.

@fluxionary @Emojigit Feel free to open a pull request to make them non-TNT-able :slightly_smiling_face:

OK, I'll get to this today.


How to use the App to download torrents (+more)

I installed this script and in CentOS and run it get me:
[Server] [Info] Server listening at port 8080
You have the latest version of lunik-torrent (current: 2.18.2)

and I registered new account and entered it but I found that what I can only do is creating folder and access it there is no any thing in the torrent tab.
also there is 2 errors in the console :
http://xx.xxx.xxx.xx:8080/%7B%7B%20info.poster%20%7D%7D Failed to load resource: the server responded with a status of 404 (Not Found)
http://xx.xxx.xxx.xx:8080/%7B%7B%20e.cover%20%7D%7D Failed to load resource: the server responded with a status of 404 (Not Found)

How can I fix this ?

Everything seems normal.
The torrent tab only show active torrents.
To download torrent, you need to put a magnet or a torrent link in this input .
Then the search button should switch to start
Then it should appear in the torrent tab. Once finished you will find the file in the direcoty tab.
The two errors that your are showing come from index.html#L103 and index#121
{{ e.cover }} is a variable that is replaced by Vue.js
But sometimes the page load faster than Vue.js and this error can appear.
Nothing to worry (I will fix it someday...)
I hope I was clear :)

Yes very clear, thanks.
Now I have a new problem when I put magnet or a torrent link in that input.
I got an error 500 (Internal Server Error) and that in the ssh
TypeError: Object function Object() { [native code] } has no method 'assign at CPBAPI.Search .....'

Humm I see, did the button switch from search to start before you click on it ?
If no, this is a very old bug ! The button didn't update on copy/paste.
Add and remove space it should work.
Your error show that the client send search request instead of start request :/

yes that was it, it worked now and in the ssh  show download torrent and and Start.
But after that I got another error :D
buffer.js:705throw TypeError('value is out of bounds');
and It shutdown the site
npm ERR! weird error 8
npm ERR! not ok code 0

Oooh this seems bad ! But I can't do anything :/
It seems to come from a dependency webtorrent I gess.

ah I see ,
Okay thank you for your help and the nice script.

You're welcome :)


Make push functional

This (rather large) pull request adds a typed map called Env which makes it possible to define #push as a total function. As a result, we can reduce the identity claim to a single claim with a generalized environment and no requires clauses!

this doesn't seem to be needed. Closing for now


⚠ Bofrost.at has degraded performance

In c6f7400, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 2136 ms

Resolved: Bofrost.at performance has improved in 39fa633 after 6 minutes.


⚠ api.piste.gouv.fr healthcheck has degraded performance

In 22253bd, api.piste.gouv.fr healthcheck (https://api.piste.gouv.fr/cassation/judilibre/v1.0/healthcheck) experienced degraded performance:

HTTP code: 200
Response time: 2787 ms

Resolved: api.piste.gouv.fr healthcheck performance has improved in 97fb9a3.


Add /content endpoints

This PR adds two new API endpoints.
GET /content?link=/vehicle-tax
Will return the search result from our content indexes with the specified link.
DELETE /content?link=/vehicle-tax
Will delete the search result from the index.
These endpoints are meant to be used by search-admin first, to:

Display the data for a link in elasticsearch, usefull to debug what is in indexable_content
Manually delete search results from the indices. Removal of search results is currently done manually, which is taking up developer time.

Notes:

There is already a get "/?:index?/documents/*" route to fetch the document from elasticsearch. However, this endpoint does not support multiple indexes. The difference between our four "content" indexes (mainstream, government, detailed, service-manual) is no longer relevant and users may not even know in which index the document lives. The new GET route works on all content indexes.
get "/?:index?/documents/*" doesn't work for some document formats because of the way it calculates the document type when searching (see this for details). The new endpoint works for all documents that can turn up in the results.
delete "/?:index?/documents/*" needs the type and index of the result to delete. This is difficult to find, especially since get "/?:index?/documents/*" doesn't work. Our new endpoint doesn't need the type.
A third endpoint delete "/?:index?/documents" can also be deprecated.

Notes about implementation:

We chose to add a new file in lib/routes for these endpoints, to keep app.rb from growing even bigger.
The URL would be nicer in the form of GET /content/:id. But this would be confusing because of the double slash the URL would contain (a problem with the endpoints mentioned above).
Added documentation to /docs/api.md.

Trello
https://trello.com/c/dvzAnQ80/272-remove-passport-extension-page-from-search
https://trello.com/c/0Jybv3yh/276-remove-item-from-search-index
Paired with @jackscotti on this one :+1:

I've only read the description so far, but I'm wondering if using /content?link=/vehicle-tax will conflict with the similar usage that exists in Content Store. Would it be worth making the two of these consistent or choosing a path other than /content ?

/content is the same as the content store public URI. Does that matter?
On Wed, 5 Aug 2015 at 16:31 Tijmen Brommet<EMAIL_ADDRESS>wrote:

This PR adds two new API endpoints.
GET /content?link=/vehicle-tax
Will return the search result from our content indexes with the specified
link.
DELETE /content?link=/vehicle-tax
Will delete the search result from the index.
These endpoints are meant to be used by search-admin
https://github.com/alphagov/search-admin first, to:

Display the data for a link in elasticsearch, usefull to debug what
is in indexable_content
Manually delete search results from the indices. Removal of search
results is currently done manually, which is taking up developer time.

Notes:

There is already a get "/?:index?/documents/*" route to fetch the
document from elasticsearch. However, this endpoint does not support
multiple indexes. The difference between our four "content" indexes
(mainstream, government, detailed, service-manual) is no longer relevant
and users may not even know in which index the document lives. The new
GET route works on all content indexes.
get "/?:index?/documents/*" doesn't work for some document formats
because of the way it calculates the document type when searching (see
this
https://github.com/alphagov/rummager/blob/9b2a1e1748808bdedbc7cbf974c32c1159582e1a/lib/elasticsearch/index.rb#L334
for details). The new endpoint works for all documents that can turn up in
the results.
delete "/?:index?/documents/" needs the type and index of the
result to delete. This is difficult to find, especially since get
"/?:index?/documents/" doesn't work. Our new endpoint doesn't need
the type.
A third endpoint delete "/?:index?/documents" can also be deprecated.

Notes about implementation:

We chose to add a new file in lib/routes for these endpoints, to
keep app.rb from growing even bigger.
The URL would be nicer in the form of GET /content/:id. But this
would be confusing because of the double slash the URL would contain (a
problem with the endpoints mentioned above).
Added documentation to /docs/api.md.

Trello
https://trello.com/c/dvzAnQ80/272-remove-passport-extension-page-from-search
https://trello.com/c/0Jybv3yh/276-remove-item-from-search-index
You can view, comment on, or merge this pull request online at:
https://github.com/alphagov/rummager/pull/475
Commit Summary

Clean up integration tests
Provide a clearer error message for invalid index names
Extract functionality for index name stripping
Add /content endpoints

File Changes

M app.rb
https://github.com/alphagov/rummager/pull/475/files#diff-0 (2)
A docs/api.md
https://github.com/alphagov/rummager/pull/475/files#diff-1 (55)
M lib/elasticsearch/index.rb
https://github.com/alphagov/rummager/pull/475/files#diff-2 (8)
M lib/elasticsearch/search_server.rb
https://github.com/alphagov/rummager/pull/475/files#diff-3 (17)
M lib/result_presenter.rb
https://github.com/alphagov/rummager/pull/475/files#diff-4 (6)
A lib/routes/content.rb
https://github.com/alphagov/rummager/pull/475/files#diff-5 (31)
A test/functional/content_endpoints_test.rb
https://github.com/alphagov/rummager/pull/475/files#diff-6 (71)
M test/integration/bulk_loader_test.rb
https://github.com/alphagov/rummager/pull/475/files#diff-7 (2)
M test/integration/elasticsearch_advanced_search_test.rb
https://github.com/alphagov/rummager/pull/475/files#diff-8 (3)
M test/integration/elasticsearch_amendment_test.rb
https://github.com/alphagov/rummager/pull/475/files#diff-9 (3)
M test/integration/elasticsearch_deletion_test.rb
https://github.com/alphagov/rummager/pull/475/files#diff-10 (2)
M test/integration/elasticsearch_indexing_test.rb
https://github.com/alphagov/rummager/pull/475/files#diff-11 (2)
M test/integration/elasticsearch_migration_test.rb
https://github.com/alphagov/rummager/pull/475/files#diff-12 (11)
M test/integration/multi_index_test.rb
https://github.com/alphagov/rummager/pull/475/files#diff-13 (4)
M test/integration_test_helper.rb
https://github.com/alphagov/rummager/pull/475/files#diff-14 (4)

Patch Links:

https://github.com/alphagov/rummager/pull/475.patch
https://github.com/alphagov/rummager/pull/475.diff

—
Reply to this email directly or view it on GitHub
https://github.com/alphagov/rummager/pull/475.

Won't conflict, but still a good point to avoid confusion.
I meant for the /content namespace only to operate on rummager-documents that can turn up in search (mainstream, government, detailed, service-manual indexes, not page-traffic and metasearch). How about /search-results?link=/vehicle-tax?

Closed until we have more clarity about when indexes are locked.

I've not looked at the code, but I like the addition of these endpoints - they make semantic sense.  I'd suggest using /document instead of /content, since that's more the terminology used in elasticsearch and other search systems, but I don't think /content is actually problematic.
Though the ?link= form of the URL is a bit ugly, it has the advantages mentioned in the PR description, and would also support changing the unique identifier in search without breaking things (eg, we could support ?id= if identifiers became distinct from the link field, such as if we started using content-IDs as identifiers).
I'm not sure what the issue about indexes being locked is.  If you describe in more detail I may be able to help.  Indexes in elasticsearch should only be locked in two cases:

when a migration is in progress.
when a bulk import is in progress.

Slack discussion w/ richard: index locks are temporary. I'll amend the commit to handle locking errors gracefully.
As for the naming, I would prefer it to have document refer to any elasticsearch document. A thing from /content or /search-results then refers only to things that can be returned as a search result, and not metadata that is also kept in ES, such as the popularity data, best bets. A possible future endpoint /document would also return those. Does that make sense?

The logic for calling it /content makes sense, particularly since we have a "content-index-names" config variable to refer to those indexes.

Updated PR with the lock handling.


Downloading the Windows version says "Virus Detected"

I'm trying to download the Windows version, but everytime I do, my computer thinks its a virus. Can you fix that?

Sadly no, you'll need to either install Python 3 and use the Python version or just disable your antivirus temporarily. Most virus checkers for Windows just automatically flag any Python script made into a standalone exe as a virus, regardless of what it actually does.

I also get that problem, tried downloading the win version on Linux, as soon as I boot into windows, it auto deletes it.
When I try to run the python version on Linux it does nothing, but I'm also a Linux NOOB. On Windows the python file wants the module certifi.
On windows 7 it's missing a .dll File.

The thing it's detecting is called "Trojan:Win32/Casdet!rfn"

COMMUNITY
Ad-Aware
Gen:Variant.Graftor.905509
ALYac
Gen:Variant.Graftor.905509
Antiy-AVL
Trojan[PSW]/Python.Agent
SecureAge APEX
Malicious
Avast
FileRepMalware
AVG
FileRepMalware
BitDefender
Gen:Variant.Graftor.905509
CAT-QuickHeal
Trojan.IGENERIC
Cylance
Unsafe
Cynet
Malicious (score: 100)
Cyren
W32/Trojan.RLSW-7979
eGambit
Unsafe.AI_Score_99%
Emsisoft
Gen:Variant.Graftor.905509 (B)
eScan
Gen:Variant.Graftor.905509
FireEye
Gen:Variant.Graftor.905509
Fortinet
W32/PossibleThreat
GData
Gen:Variant.Graftor.905509
Jiangmin
Trojan.PSW.Python.ab
K7AntiVirus
Trojan ( 0056ae631 )
K7GW
Trojan ( 0056ae631 )
Malwarebytes
Generic.Trojan.Malicious.DDS
MAX
Malware (ai Score=85)
McAfee
Artemis!28B224416F75
McAfee-GW-Edition
BehavesLike.Win32.Dropper.rc
Microsoft
Trojan:Win32/Ymacco.AAE3
NANO-Antivirus
Trojan.Win32.Mlw.iiswaj
Palo Alto Networks
Generic.ml
Panda
Trj/CI.A
Sangfor Engine Zero
Trojan.Win32.Save.a
Sophos
Mal/Generic-S
Symantec
ML.Attribute.HighConfidence
TrendMicro-HouseCall
TROJ_GEN.R011H09AS21
VBA32
TrojanPSW.Python
ViRobot
Trojan.Win32.Z.Graftor.8875868
Webroot
W32.Trojan.Gen
Zillya
Trojan.Agent.Win32.1678576

The source code is in the repo and the builds are even automatically made by Actions so like feel free to look for malicious code in there, as I said above it's just cause it's a PyInstaller executable and antiviruses hate that, you can feel free to use the python script directly, we just provide the exe for convenience as most people don't have Python installed.
I'm just leaving this one issue open so that if anyone has suggestions on how to fix this they can be left here

The source code is in the repo and the builds are even automatically made by Actions so like feel free to look for malicious code in there, as I said above it's just cause it's a PyInstaller executable and antiviruses hate that, you can feel free to use the python script directly, we just provide the exe for convenience as most people don't have Python installed.
I'm just leaving this one issue open so that if anyone has suggestions on how to fix this they can be left here

Try to set python-version: '3.7' for Windows on make-dist.yml file.
PyInstaller3.6 will be used when using python3.7.x, this will make "Virus Detected" less.
It's a test build's VirScan report ("PyInstaller3.6+Python3.7.9(x86)")
https://r.virscan.org/language/en-us/report/061caf9db018fdf3ca5f8d018fd69891

Welp, @urmum-69 still had this detected as a virus so I'll open this back up.
(screenshot from Discord)

sadly, "protecting" the zipfile with a simple password like 0000 will be your best bet for this.

I'm still getting this issue on May 16th

Yep, same for me on Windows 10.

It says it is a trojan

I think an older version of windows might work

You just need to temporarily disable your antivirus or install Python 3 and use the Python version directly. (The windows version is just the Python version converted to a single EXE)


Add note to documentation explaining CORS

Briefly explained use case of a CORS proxy and gave links to further reading to resolve issue #110.

Coverage remained the same at 100.0% when pulling 322b7b9ba78a79bf25cc41db2f3b4c98a1f7647d on 92Eli:92Eli-cors-documentation into a0309e6c475036b4ba2a04372f8d5b6462bd4825 on Rob--W:master.


pydantic.v1.error_wrappers.ValidationError

I'v got an error:
Error: 1 validation error for Trace
children -> 0 -> transaction -> out_msgs -> 1 -> init -> library
field required (type=value_error.missing) on tx 6fa11e0361f5a981724dc44de172464884746d7d1d72f25a5fe3e251b7727658

One of out_msgs field didn't have an field init at all but usually does (for example in  a4a644cad11d72a8b6a9fc1537488e7d5d9c11aec6f18e17a43d6d96ea4c925c init just null)

@AveZorgen, I'm not entirely sure what the error is. I tried running the tonapi.traces.get_trace method with the identifier a4a644cad11d72a8b6a9fc1537488e7d5d9c11aec6f18e17a43d6d96ea4c925c and didn't encounter any issues.

fixed this bug:
class Message(BaseModel): ---->    init: Optional[StateInit]

@AveZorgen
Understood the issue. Previously, the StateInit schema included the following fields:
class StateInit(BaseModel):
    code: Optional[str]
    data: Optional[str]
    library: Dict[str, str]

Now it has changed and includes only one field:
class StateInit(BaseModel):
    boc: str

Updated in version 0.2.9


Component - Search

Design review: 4.5-Input: https://www.figma.com/file/eOUqz887O5EKZwIJhJQ13U/SubWallet-UI-Base?node-id=68%3A1291&t=Io7xuX68iDDjrWCs-4
URL test: https://ui-preview.subwallet.app/?path=/story/form-search--default

Design review: 4.5-Input
Please check:

[ ] Add the Closeable control to clear search key
[ ] Update format place holder when it is long

[ ] Confirm: Search box have status? disable?

Confirming "clear keyword" design

@lw-cdm The design is already available: https://www.figma.com/file/eOUqz887O5EKZwIJhJQ13U/SubWallet-UI-Base?node-id=1551%3A10268&t=FPAfgCVBcWQtUJz0-4
Please update the search box with cleard keyword button

[ ] Add filter icon and onClick of filter icon


chore: Further simplify the PR template

Description
Removes mutual exclusive items by conflating them. Hopefully this will further reduce the busy work filling out the template while keeping the reminding value.
It also reshapes the comment sections to cater for folks working from laptops.
User-facing documentation
(must be 2 items and both must be checked)

[x] CHANGELOG update is not needed
[x] Documentation is not needed

Testing

[ ] ~inspected CI results~

Automated testing
(must be at least 1 item and all items must be checked)

[x] contributed no automated tests: not a functional change

How I validated my change

Verified that the template renders as I envision.

Context thread: https://redhat-internal.slack.com/archives/C3W3U0RGW/p1720631653214219


Total Monthly Goals keeps going to scientific e-notation

Name of Defective Feature

Total Monthly Goals

System Settings (Required)

ToolKit Version: 2.8.7
Operating System (Mac/Windows/Etc): MacOs Sierra 10.12.6
Browser (Chrome/Firefox/Safari): Chrome
Browser Version: Version 68.0.3440.106 (Official Build) (64-bit)
Other Extensions: AdBlocker, Honey, OneTab

Export of Toolkit Settings (Bottom Left of Settings Page)

Settings Export
[{"key":"AccountsDisplayDensity","value":"1"},{"key":"AccountsEmphasizedOutflows","value":false},{"key":"AccountsStripedRows","value":false},{"key":"AdjustableColumnWidths","value":false},{"key":"AutoDistributeSplits","value":false},{"key":"BetterScrollbars","value":"0"},{"key":"BudgetCategoryFeatures","value":true},{"key":"BudgetProgressBars","value":"both"},{"key":"BudgetQuickSwitch","value":false},{"key":"CalendarFirstDay","value":"0"},{"key":"CategoryActivityCopy","value":false},{"key":"CategoryActivityPopupWidth","value":"0"},{"key":"ChangeEnterBehavior","value":true},{"key":"CheckCreditBalances","value":true},{"key":"CheckNumbers","value":false},{"key":"ClearSelection","value":false},{"key":"CollapseSideMenu","value":false},{"key":"ColourBlindMode","value":false},{"key":"CompactIncomeVsExpense","value":false},{"key":"CreditCardEmoji","value":false},{"key":"CurrentMonthIndicator","value":false},{"key":"CustomFlagNames","value":false},{"key":"DaysOfBuffering","value":true},{"key":"DaysOfBufferingHistoryLookup","value":"6"},{"key":"DisableToolkit","value":false},{"key":"DisplayTargetGoalAmount","value":"0"},{"key":"DisplayTotalMonthlyGoals","value":true},{"key":"DisplayUpcomingAmount","value":false},{"key":"EasyTransactionApproval","value":false},{"key":"EditAccountButton","value":"0"},{"key":"EnlargeCategoriesDropdown","value":true},{"key":"EnterToMove","value":false},{"key":"GoalIndicator","value":true},{"key":"GoalWarningColor","value":false},{"key":"GoogleFontsSelector","value":"0"},{"key":"HideAccountBalancesType","value":"0"},{"key":"HideAgeOfMoney","value":false},{"key":"HideHelp","value":false},{"key":"HideReferralBanner","value":false},{"key":"HighlightNegatives","value":false},{"key":"ImportNotification","value":"0"},{"key":"IncomeFromLastMonth","value":"0"},{"key":"IncomeVsExpenseHoverHighlight","value":true},{"key":"LargerClickableIcons","value":false},{"key":"MonthlyNotesPopupWidth","value":"0"},{"key":"NavDisplayDensity","value":"0"},{"key":"Pacing","value":"0"},{"key":"PrintingImprovements","value":true},{"key":"PrivacyMode","value":"0"},{"key":"QuickBudgetWarning","value":false},{"key":"ReconciledTextColor","value":"0"},{"key":"RemovePositiveHighlight","value":false},{"key":"RemoveZeroCategories","value":false},{"key":"ResizeInspector","value":false},{"key":"RightClickToEdit","value":true},{"key":"RowHeight","value":"0"},{"key":"RowsHeight","value":"0"},{"key":"RunningBalance","value":"0"},{"key":"SeamlessBudgetHeader","value":false},{"key":"ShowCategoryBalance","value":false},{"key":"ShowIntercom","value":true},{"key":"SpareChange","value":false},{"key":"SplitKeyboardShortcut","value":true},{"key":"SplitTransactionAutoAdjust","value":false},{"key":"SquareNegativeMode","value":true},{"key":"StealingFromFuture","value":true},{"key":"SwapClearedFlagged","value":false},{"key":"TargetBalanceWarning","value":false},{"key":"ToBeBudgetedWarning","value":false},{"key":"ToggleMasterCategories","value":false},{"key":"ToggleSplits","value":false},{"key":"ToggleTransactionFilters","value":"0"},{"key":"TransactionGridFeatures","value":true},{"key":"ViewZeroAsEmpty","value":false},{"key":"l10n","value":"0"},{"key":"reports","value":true}]

Steps to Reproduce the Behavior

Load YNAB.  Total monthly goals shows 7,201.76.
Change any goal.  I increased my grocery budget goal by $50 for this example.
Go to reports then back to budget to see the overview again.

Expected Behavior

I expect Total Monthly Goals to stay in normal notation always.
Actual Behavior

Total monthly goals has changed to $1.342500750000937e+187.
Refresh the page, goals has returned to standard notation

No errors or any logs from YNAB or YNAB toolkit, only some entries from AdBlocker.  Repeated scenario with AdBlocker disabled, same result.

Hey @mspitalnik the fix for this should be in our current release! If you notice the issue still exists and you're definitely running the newest version of the toolkit, please reopen! Thanks!
Please note, all browser can take up to an hour to provide updates to all users. You can force an update if it's available for you by going to chrome://extensions and clicking the "Update" button. Firefox users can go to about:addons, click the setting cog, and click "Check for updates...".

Thank you!  Just got the 2.9.0 release, and it hasn't recurred.  Awesome
work!!
-Meredith Spitalnik
Architect
Zilker Technology
(401) 374-1853
www.ztech.io
On Wed, Oct 10, 2018 at 11:55 AM Josh Madewell<EMAIL_ADDRESS>wrote:

Closed #1435
https://github.com/toolkit-for-ynab/toolkit-for-ynab/issues/1435.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/toolkit-for-ynab/toolkit-for-ynab/issues/1435#event-1895942487,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AbaJoo9UXocI3CmjnC3FYZwk82eeluyDks5ujhh9gaJpZM4XI00g
.


(I think) SurrealDB db exported as a global var is leaking User's session!

Hi @oskar-gmerek ! Great setup, however, recently I've been digging into global vars in SvelteKit leaking state. I tested parts of your code in my own test repo and find that the exported db leaks the last session/auth that was signed into by anyone using the app.
I'm running the SvelteKit app on localhost.;
logged in 2 separate users on a Brave browser tab and a Chrome browser tab;
and have I have an sdb query to get the $auth or $session. Whenever I run this, despite each user/browser tab having a unique Token in the cookies, they return the session or auth of the last authenticated user.
I presume this is the same issue identified by Huntabyte and others for SvelteKit because of SSR.
Have you already encountered this, and have you got a good way around this for SurrealDB?

Ahh I think I found my issue: I was triggering my query from an endpoint that was NOT under a "(user)"  folder.
Therefore
if (token && secureRoute) {

		const authenticated = await db
			.authenticate(token)
			```
in hooks.server was not triggered.


Track and test dependencies' 'next' branch

parsec depends on several repositories under the parallaxsecond organization.
Currently, when testing the main branch of parsec, fixed versions of the latest released crates of those repositories are being used.
A problem may arise when there is a change introduced in the main/'next' branch of those repositories that would break parsec when updating/incorporating that change. This is currently not being tested in our CI.
As parsec release is dependent on having published the dependencies' crates, there are issues that will not be caught until the publishing of said crates.

Add nightly jobs that use ci.sh --next-branch-tracking to test the
next release branches of parallaxsecond repositories and spot
issues before release. These jobs make use of previously defined
re-usable actions and utils/release_tracking.py

Please check the added tests in my fork:

Will generate a follow up PR creating a utils/cargo-commands.py after this , as well as simplifying the re-usable actions

https://github.com/tgonzalezorlandoarm/parsec/actions/runs/6786709261 new test on my fork after these changes

https://github.com/tgonzalezorlandoarm/parsec/actions/runs/6786705099

https://github.com/tgonzalezorlandoarm/parsec/actions/runs/6800846830 New CI run

https://github.com/tgonzalezorlandoarm/parsec/actions/runs/6853736203


Not backwards compatable with plan files

Which version of the AzCopy was used?
Note: The version is visible when running AzCopy without any argument
10.5.1
Which platform are you using? (ex: Windows, Mac, Linux)
Linux
What command did you run?
Note: Please remove the SAS to avoid exposing your credentials. If you cannot remember the exact command, please retrieve it from the beginning of the log file.
az jobs list
What problem was encountered?
Old jobs are not displayed
How can we reproduce the problem in the simplest way?
Have a plan file from an older version of azcopy and run azcopy jobs list and the old job will not display.
Have you found a mitigation/solution?
Must use older binary to read older .steV## plan files.
Looking through the code it looks like the DataSchemaVersion must match between the binary and the plan files.  If it does not match, the files are not read (in my case .steV10 files cannot be read by azcopy 10.5.1 which expects .steV14 files).  Renaming the files does not work and causes azcopy to crash (as expected) due to the files being the wrong format/schema.
azcopy should be backwards compatible with plan files to enable users to upgrade their binary and be able to read old plan files via azcopy jobs list.

@LRomandine Thanks for reaching us! This is by design and the user is expected to complete the older jobs  using a older version. We do not have plans to remove this restriction.


Add CheckboxGroup component

Description
Component that groups checkboxes into a multiple choice view.
Related Issue(s)

#142

Verification

[x] Your code builds clean without any errors or warnings
[x] Manual testing done (required)
[x] Relevant automated test added (if you find this hard, leave it and we'll help out)
[x] All tests run green

Documentation

[ ] User documentation is updated with a separate linked PR in altinn-studio-docs. (if applicable)

Codecov Report
Base: 97.04% // Head: 97.39% // Increases project coverage by +0.35% :tada:

Coverage data is based on head (27db726) compared to base (eef09f1).
Patch coverage: 100.00% of modified lines in pull request are covered.

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #143      +/-   ##
==========================================
+ Coverage   97.04%   97.39%   +0.35%
==========================================
  Files          32       48      +16
  Lines         406      499      +93
  Branches      103      124      +21
==========================================
+ Hits          394      486      +92
- Misses         12       13       +1

Impacted Files
Coverage Δ

src/components/Checkbox/Checkbox.tsx
100.00% <100.00%> (ø)

src/components/CheckboxGroup/CheckboxGroup.tsx
100.00% <100.00%> (ø)

src/components/CheckboxGroup/index.ts
100.00% <100.00%> (ø)

src/components/index.ts
100.00% <100.00%> (ø)

src/components/Button/index.ts
100.00% <0.00%> (ø)

src/components/Accordion/index.ts
100.00% <0.00%> (ø)

src/components/CircularProgress/index.ts
100.00% <0.00%> (ø)

src/components/TextArea/index.ts
100.00% <0.00%> (ø)

src/components/Map/index.ts
100.00% <0.00%> (ø)

src/components/Checkbox/index.ts
100.00% <0.00%> (ø)

... and 8 more

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

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

@haakemon, I have improved all the issues except from the problem with app-frontend. I think maybe adding an isValid prop is the cleanest solution, especially with regards to this particular case. What do you think?


Create new dialog fixes

@blink1073 - here are a few fixes to get the example working. I also rewrote some of the code to make it easier for me to understand the logic.

Thanks!


python310Packages.immutables: 0.16 -> 0.17

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for python310Packages.immutables is: "An immutable mapping type for Python"
meta.homepage for python310Packages.immutables is: "https://github.com/MagicStack/immutables"
meta.changelog for python310Packages.immutables is: ""
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS

Warning: a test defined in passthru.tests did not pass

0 of 0 passed binary check by having a zero exit code.

0 of 0 passed binary check by having the new version present in output.

found 0.17 with grep in /nix/store/b2hcn1hd0hyl00w0gafarnmh3v36vr7d-python3.10-immutables-0.17

found 0.17 in filename of file in /nix/store/b2hcn1hd0hyl00w0gafarnmh3v36vr7d-python3.10-immutables-0.17

Rebuild report (if merged into master) (click to expand)

45 total rebuild path(s)

23 package rebuild(s)

23 x86_64-linux rebuild(s)
22 x86_64-darwin rebuild(s)

First fifty rebuilds by attrpath
apache-airflow
cryptop
home-assistant-component-tests.bsblan
mnamer
python310Packages.apache-airflow
python310Packages.bsblan
python310Packages.cattrs
python310Packages.immutables
python310Packages.pysychonaut
python310Packages.requests-cache
python310Packages.statmake
python310Packages.tvdb_api
python310Packages.typed-settings
python39Packages.apache-airflow
python39Packages.bsblan
python39Packages.cattrs
python39Packages.immutables
python39Packages.pysychonaut
python39Packages.requests-cache
python39Packages.statmake
python39Packages.tvdb_api
python39Packages.typed-settings
tvnamer

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/b2hcn1hd0hyl00w0gafarnmh3v36vr7d-python3.10-immutables-0.17 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A python310Packages.immutables https://github.com/r-ryantm/nixpkgs/archive/7700251b8e75fd87a3eae9b0c0b0d9bb5aa97fe9.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/b2hcn1hd0hyl00w0gafarnmh3v36vr7d-python3.10-immutables-0.17
ls -la /nix/store/b2hcn1hd0hyl00w0gafarnmh3v36vr7d-python3.10-immutables-0.17/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

4 packages marked as broken and skipped:

python310Packages.statmake
python310Packages.tvdb_api
python39Packages.tvdb_api
tvnamer

2 packages failed to build:

apache-airflow (python39Packages.apache-airflow)
python310Packages.apache-airflow

16 packages built:

cryptop
home-assistant-component-tests.bsblan
mnamer
python310Packages.bsblan
python310Packages.cattrs
python310Packages.immutables
python310Packages.pysychonaut
python310Packages.requests-cache
python310Packages.typed-settings
python39Packages.bsblan
python39Packages.cattrs
python39Packages.immutables
python39Packages.pysychonaut
python39Packages.requests-cache
python39Packages.statmake
python39Packages.typed-settings

Maintainer pings
cc @catern for testing.

Result of nixpkgs-review pr 165934 run on x86_64-linux 1

4 packages marked as broken and skipped:

python310Packages.statmake
python310Packages.tvdb_api
python39Packages.tvdb_api
tvnamer

2 packages failed to build:

apache-airflow (python39Packages.apache-airflow)
python310Packages.apache-airflow

16 packages built:

cryptop
home-assistant-component-tests.bsblan
mnamer
python310Packages.bsblan
python310Packages.cattrs
python310Packages.immutables
python310Packages.pysychonaut
python310Packages.requests-cache
python310Packages.typed-settings
python39Packages.bsblan
python39Packages.cattrs
python39Packages.immutables
python39Packages.pysychonaut
python39Packages.requests-cache
python39Packages.statmake
python39Packages.typed-settings


formula_creator: commented examples for ruby dependencies

[x] Have you followed the guidelines in our Contributing document?
[x] Have you checked to ensure there aren't other open Pull Requests for the same change?
[ ] Have you added an explanation of what your changes do and why you'd like us to include them?
[ ] Have you written new tests for your changes? Here's an example.
[ ] Have you successfully run brew style with your changes locally?
[ ] Have you successfully run brew typecheck with your changes locally?
[ ] Have you successfully run brew tests with your changes locally?

Also update documentation as original command is deprecated (https://bundler.io/v2.5/man/bundle-install.1.html#OPTIONS).

Close for now as I need to think about this a little more and compare different installation commands (perhaps comparing different language approaches to see if there is a better middle-ground).


Cannot delete after fill up all the mask Android Chrome browser Jsfiddle

https://jsfiddle.net/b02gd4fh/1/
After filling up the mask, i try to delete and re-input the value, it seems I'm unable to do it.
The cursor are keep jumping to right whenever i try to delete the filled value.
Thanks

@NightsDream if you haven't read the Android Readme, please do at https://github.com/RobinHerbots/Inputmask/blob/4.x/README_android.md

@NightsDream ,  @BrainClot ,
This is a valid issue.  I already added it to the unittests.  I will have a look why.

Anyway, I have revert back to old version. Old version working well for my case on android and desktop.
https://jsfiddle.net/b02gd4fh/3/

@NightsDream ,
Version 3.x is the latest.  The 4.x is new development, there is no 4.x released yet.

@RobinHerbots,
Oh, I thought 4.X is the latest version,
thx for telling me and the great plugin :)


Add documentation for nats jetstream based state store

What content needs to be created or modified?
Add documentation for jetstream based state store
The associated pull request from dapr/dapr, dapr/components-contrib, or other Dapr code repos
https://github.com/dapr/components-contrib/pull/1501
Additional context

!assign

resolved


Add tests section as part of software invocation

Right now they are ignored, and they are not annotated.

Example of a test file that is not currently detected as a test:
Chowlk/tests/test_finding.py
Note: In the latest "test" classification, we removed the use of the file_name ( e.g. that contains "test" in the filename).
We should ( in the test classification) check if the file has "unnitest" (or other test libraries, e.g. "doctest") inside the dependencies.  Right now,  "unittest" and "doctest" (they might be more test libraries) are only checked if they are included as strings inside the main_function (e.g. unnitest.main()).

I've followed my own advice and now we check the dependencies list , since I needed for doing more tests.
NOTE: This test classification will need further investigation - this is just a quick improvement from the original implementation.
Regarding with Chowlk - now it does the expected behaviour.

I have now separated tests as a different category.
In software invocation each element of the list has a unique type.


Fix variable naming error in BooleanSwitch

The variables are named thru, thru0, and thru1, but when used they are named out, thru1, thru2

Nice catch, thanks!


FEATURE: support Chat with AI Persona via a DM

Add support for chat with AI personas

Allow enabling chat for AI personas that have an associated user
Add new setting allow_chat to AI persona to enable/disable chat
When a message is created in a DM channel with an allowed AI persona user, schedule a reply job
AI replies to chat messages using the persona's max_context_posts setting to determine context
Store tool calls and custom prompts used to generate a chat reply on the ChatMessageCustomPrompt table
Add tests for AI chat replies with tools and context

At the moment unlike posts we do not carry tool calls in the context.
No @mention support yet for ai personas in channels, this is future work

I  gave this a try locally sam, few notes.
1 - I got this error in logs when starting to discuss:
/Users/joffreyjaffeux/Code/discourse-ai/app/jobs/regular/create_ai_chat_reply.rb:18:in `execute'
/Users/joffreyjaffeux/Code/pr-discourse/app/jobs/base.rb:305:in `block (2 levels) in perform'
rails_multisite-6.0.0/lib/rails_multisite/connection_management/null_instance.rb:49:in `with_connection'
rails_multisite-6.0.0/lib/rails_multisite/connection_management.rb:21:in `with_connection'

I figured out it was related to me not choosing a Default Language Model on my persona, but we should probably show an error if you save without having one? Bare minimum the error in logs should be clearer.
2 - After fixing default language model, I tried to discuss again and got this:
activerecord-<IP_ADDRESS>/lib/active_record/core.rb:284:in `find'
/Users/joffreyjaffeux/Code/discourse-ai/app/jobs/regular/create_ai_chat_reply.rb:20:in `execute'

Looking at my DB I see this:

And the query was actually looking for gpt-4-turbo at id -113, I suspect than when I changed my default llm, the new user for this llm has not been created? I changed my default language model to gpt-3.5-turbo and that fixed it. But something doesn't look right here.

Yikes will add some validations on Monday
On Fri, 3 May 2024 at 8:45 PM, Joffrey JAFFEUX @.***>
wrote:

I gave this a try locally sam, few notes.
1 - I got this error in logs when starting to discuss:
/Users/joffreyjaffeux/Code/discourse-ai/app/jobs/regular/create_ai_chat_reply.rb:18:in execute' /Users/joffreyjaffeux/Code/pr-discourse/app/jobs/base.rb:305:in block (2 levels) in perform'
rails_multisite-6.0.0/lib/rails_multisite/connection_management/null_instance.rb:49:in with_connection' rails_multisite-6.0.0/lib/rails_multisite/connection_management.rb:21:in with_connection'
I figured out it was related to me not choosing a Default Language Model
on my persona, but we should probably show an error if you save without
having one? Bare minimum the error in logs should be clearer.
2 - After fixing default language model, I tried to discuss again and got
this:
activerecord-<IP_ADDRESS>/lib/active_record/core.rb:284:in find' /Users/joffreyjaffeux/Code/discourse-ai/app/jobs/regular/create_ai_chat_reply.rb:20:in execute'
Looking at my DB I see this:
Screenshot.2024-05-03.at.12.33.14.png (view on web)
https://github.com/discourse/discourse-ai/assets/339945/c70091e5-22f8-4ed2-a6bf-6d9c033ddaec
And the query was actually looking for gpt-4-turbo at id -113, I suspect
than when I changed my default llm, the new user for this llm has not been
created? I changed my default language model to gpt-3.5-turbo and that
fixed it. But something doesn't look right here.
—
Reply to this email directly, view it on GitHub
https://github.com/discourse/discourse-ai/pull/488#issuecomment-2092754412,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAABIXJSCDZNHHYLZBDVOYLZANTELAVCNFSM6AAAAABD3JZSXCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAOJSG42TINBRGI
.
You are receiving this because you authored the thread.Message ID:
@.***>

both are fixed @jjaffeux


update e2e versions

What this PR does / why we need it:
Which issue(s) this PR fixes

closes https://github.com/vmware-tanzu/sonobuoy/issues/1975
closes https://github.com/vmware-tanzu/sonobuoy/issues/1972
closes https://github.com/vmware-tanzu/sonobuoy/issues/1970
closes https://github.com/vmware-tanzu/sonobuoy/issues/1969
closes https://github.com/vmware-tanzu/sonobuoy/issues/1965
closes https://github.com/vmware-tanzu/sonobuoy/issues/1964
closes https://github.com/vmware-tanzu/sonobuoy/issues/1959
closes https://github.com/vmware-tanzu/sonobuoy/issues/1955
closes https://github.com/vmware-tanzu/sonobuoy/issues/1953
closes https://github.com/vmware-tanzu/sonobuoy/issues/1951
closes https://github.com/vmware-tanzu/sonobuoy/issues/1947

Special notes for your reviewer:
Release note:
updated e2e command to include most recent Kubernetes versions

I ran gather_e2e_data.sh and committed.
However, I did not check the contents of the file.

@franknstyle Could you please review it ?

Can you please rebase this branch

Can you please rebase this branch

rebased !


Arduino Library...?

hi Max,
I really like your Modbus library, as it just does the jobs, no frills...  :-)   To increase visibility, have you considered making it available as an Arduino library?
PS: my STM8 port of your library can be found here. Thanks again!

Hi Georg,
thx for your message. Highly appreciated. I have been asked several times to bring the lib to Arduino but I never really use Arduino so this is extremely low on my list. So low in fact that I will probably never do it. If someone else did it I would be more than happy.
Thanks for pointing me to your STM8 port. Very nicely done. I will probably use it. I've been thinking about porting to STM for a while :-)
Best,
Max

Hi Max,
:-)  On 2nd thought porting yaMBSiavr to Arduino would probably be pretty awkward, because the Arduino framework does not support to attach functions to Uart interrupts out of the box. While lib NeoHWSerial adds this for the 8-bit AVR boards, this is not possible for the newer 32-bit ARM, e.g. Due (see this discussion), let alone the plethora of "Arduino-like" boards.
I believe that your implementation is correct, and that handling Modbus via polling is not the way to go. However, I did find  several Arduino libraries which seem to do a pretty good job if the protocol handler is called every 1ms or so. So please ignore my proposal, and let's keep your lib as it is, i.e. for bare-metal programmers.
As for my STM8 port, please feel free to use it! How about you add a "port" folder to your repo for different kinds of controllers?
In any case thanks again for your effort! Well done...
Regards, Georg

Hi,
sorry for the late response. Thx for pointing me to your STM8 port! :-)
Best regards,
Max


Expose Godot signals to map editors

Use the same property types that drive Quake's target/targetname setup? Need to expand it to arbitrary signals and slots if possible, but the FGD spec makes it sound like it's designed around a 1:1 target/targetname relationship a-la Quake.
Could use target/targetname to determine entity relationship, plus additional properties for defining multiple signal/slot pairs?

A somewhat advanced version of this is implemented in the latest commit.
Unfortunately TrenchBroom doesn't support target_destination and target_source in a general manner- it's hardcoded to use the Quake-style target and targetname keys for entity link visualization.
So for usability's sake, signals and slots are represented as point entities that store signal and slot names respectively, and form a target -> targetname chain from the entity broadcasting the signal to the entity/entities receiving it in a slot. Each step in this chain can be one-to-many, so the emitter can target several signal objects that share a targetname, which in turn can target several slot objects that share a targetname, which finally can target several entities that share a targetname.
This signal/slot relationship is fixed up during build by QodotMap, and the signal/slot entities are then deleted since they're marked as transient in their FGD definitions.
This works very well, but is a bit complicated for simpler Quake-style workflows that have a universal 'trigger' and 'use' setup. Need to add a type check to connect_signals that falls back to a simpler 'connect the trigger signal to the use slot' behavior to cover this.

A simple trigger -> use signal/slot connection has been implemented in the latest commits.
If an entity has a valid target field and a signal called trigger, it will be connected to the use slot in its target entity during build.


WIP: Implement getCacheKey to invalidate jest cache when tsconfig changes

Resolves #231

[x] Implement getCacheKey
[ ] Add tests

@GeeWee @bcruddy @bhouser can you folks review the getCacheKey function implemented in this PR?

Love the types.
lgtm, this should work both with tsconfig set through through tsconfig.json and TS_CONFIG - As soon as we get some tests, I think we should merge this baby in.
(For others: This is the example of the cache key creation function from relay: https://github.com/facebook/fbjs/blob/master/packages/fbjs-scripts/jest/createCacheKeyFunction.js )

I took a quick look and everything seems solid. I'll put it down to do a more extensive review after lunch.

That's +2 but the PR is still marked as "WIP". On top of that - what are the guidelines for merging (just create a merge commit, squash and merge, etc). If we're going with squash and merge (my preference), what should the commit message look like?

I usually just merge it straight in. There's been no release process or changelogs so far!

@kulshekhar cool - I prefer the squash and merge for open source modules like this because it keeps a squeaky clean git history (no more 'fixed test' with no context in the git log) and each commit references a pull request if you want to dig deeper into the specific change. no-slash and searchkit. Personally I prefer the stricter "everything must be a pull request" methodology but I think it might be stockholm syndrome from doing it at work. This also lets your git history become your change log.
As far as when to actually merge though, is it just a +2 thing or would you prefer to do the merging?

@bcruddy I don't work on projects that are released publicly so I have no experience with release processes. I like the sound of what you've said. Squash and merge it is then, from now on.
As for when to merge, it isn't anything hard and fast. In this case, I just wanted someone to check if I've done something wrong.
In general, I don't have any issues with any of the collaborators merging PRs in. So if you see something and think it's good enough to go in, by all means merge it. On the other hand, if you think a review is needed, tag us (or any other users) and merge it after you're satisfied

This all sounds good to me.


optimize Thread.current and Thread.current[:constant_sym]

Motivation

This PR builds on #4645 to change things so that Thread.current doesn't implement a slow path and always directly calls rb_thread_current.  The current code would eventually do the same, but at the cost of having a slow path that would be optimized out by LLVM.  This change means that we can meaningfully assert that Thread.current returns a Thread, which in turns means that Thread.current[:foo] doesn't do type checks anymore.
But wait, there's more!  Our implementation of Thread#[] checks at runtime for ID-ness of its argument.  But if we have Thread.current[:foo], then we know at compile time that our argument is guaranteed to be convertible to an ID.  So we can check for a constant symbol argument to Thread#[] (resp. Thread#[]=) and eliminate some runtime checking.  We also need to make rb_id2sym const so that the symbol for :foo, which is now unused, never actually gets materialized at runtime.
The benefits can be see in test/testdata/ruby_benchmarks/stripe/lspace.rb.  Before:
froydnj@pyro:~/src/sorbet$ ./tools/scripts/run_benchmarks.sh -b test/testdata/ruby_benchmark/stripe/while_10_000_000.rb -f test/testdata/ruby_benchmark/stripe/lspace.rb
...
source  interpreted     compiled
stripe/while_10_000_000.rb      .230    .101
stripe/lspace.rb        .897    .602
stripe/lspace.rb - baseline     .667    .501

After:
froydnj@pyro:~/src/sorbet$ ./tools/scripts/run_benchmarks.sh -b test/testdata/ruby_benchmark/stripe/while_10_000_000.rb -f test/testdata/ruby_benchmark/stripe/lspace.rb
...
source  interpreted     compiled
stripe/while_10_000_000.rb      .224    .099
stripe/lspace.rb        .880    .549
stripe/lspace.rb - baseline     .656    .450

Roughly 10% faster than before.
This could probably be improved further by combining interrupt checks in a single basic block; for Thread.current[:foo] we'll wind up with a basic block that looks like:
current = sorbet_Thread_current(...)
sorbet_afterIntrinsic()
val = sorbet_Thread_square_br_symarg(current, id_for_foo)
sorbet_afterIntrinsic()

and I think we could get away with combining the first sorbet_afterIntrinsic with the second, so long as we make sure to check for interrupts somewhere.  But that is a separate patch.
Test plan

See included automated tests.

We have a policy of testing changes to Sorbet against Stripe's codebase before
merging them. I've kicked off a test run for the current PR.  When the build
finishes, I'll share with you whether or how it failed. Thanks!
Stripe employees can see the build results here:
→ https://go/builds/bui_KJKT2BTffmjASL
→ https://go/builds/bui_KJKTgvGlORrG8B


[BS-511] Add key checks to Join areUniqueColumns check

Updates the uniqueness tests for join to include handling the other half of an inner join if it is a common equality condition. This is used to safely increase the size of the checked columns, which can match on additional primary keys.

Relevant Proof: https://bodo.atlassian.net/wiki/spaces/BodoSQL/pages/1101332481/Join+areColumnsUnique+Calcite+Rule+Extension+Proof


Tag -selectElementWithMatcher: with NS_WARN_UNUSED_RESULT

We often run into a human error, when an element is selected by not asserted on or acted upon. With the unused result attribute, the person writing a test would get a nag that no action was performed on the element.

Will port to eg2 as well.


Deploy docs: GitHub Action triggered by release

How would this feature be useful?

It would be cool if new documentation could automatically run whenever we make a release.
Implementing this action might help us gain experience and confidence to implement and Action to automatically publish to PyPI in the future.
Describe the solution you'd like

I've started investigating GitHub Actions, and this Issue is to track figuring out how to make an Action that would build the site using mkdocs and deploy, triggered by a Release.
Describe alternatives you've considered

The current way of generating and publishing the docs is fine, but it's another thing that needs to be remembered and executed properly each time.  Triggering automatically on release would remove one more thing to do by hand, hopefully ensuring it's done consistently and accurately.

My experiment repo is here:
https://github.com/itsayellow/action-test
The Action that shows up when you search the GitHub actions "marketplace" for mkdocs is:
https://github.com/marketplace/actions/deploy-mkdocs
However (at least currently) there's some issue with GitHub Actions that prevents pushing using this Action from successfully generating a new GitHub page:
https://github.community/t5/GitHub-Actions/Github-action-not-triggering-gh-pages-upon-push/m-p/26869/highlight/true#M301
Which led me to this Action, which seems to be far more actively developed, and also has a workaround for the above issue.
https://github.com/marketplace/actions/github-pages-action
https://github.com/peaceiris/actions-gh-pages

Looks like mkdocs-deploy-gh-pages just fixed their deploy problem, and now it should properly trigger deployment of pages from the branch
https://github.com/mhausenblas/mkdocs-deploy-gh-pages/pull/4

Another interesting method is to use the workflow_dispatch trigger, which can trigger from github web ui, and even accept arguments from the web ui!
https://github.blog/changelog/2020-07-06-github-actions-manual-triggers-with-workflow_dispatch/
https://docs.github.com/en/actions/configuring-and-managing-workflows/configuring-a-workflow#manually-running-a-workflow

This is great, thank you for taking the initiative on this.


Issue with screengrab

After the 5th question, it seems that the screenshot isn't adapted anymore because of the apparition of a new line (please look at the screenshot). Is there anything I can modify in the program to avoid this issue ?
thanks a lot

The best way to screenshot is to screenshot like in the attached photo, it gets rid of any potential variable on screen assets and isolates the text and answers. Screenshotted this way should do the trick!!

@Taratata92 hey how did you set the bot up?


Error with registry_name

Now I have the same error I had yesterday:

@frarin the error was in the helm chart name, it does not accept special characters like "_"
we have now introduced a transformation to remove these characters.


Couple perf improvements for MST and integration with the driver

Follow up to #624.

Adds ability to run MST using DBSCAN driver
Increases the number of neighbors used to set upper bound for a component to 2
This gives about 5-10% improvement for HACC problem
Uses lower bound
This seems to only help in serial, not for GPU. For HACC problem, it is about 25% faster in serial (300 vs 225 on AMD EPYC).

Split them up

Into 2 or 3?


Using TPM on genes instead of transcripts?

Hi,
I have some bulk RNA seq data that I would like to normalize. I've used your package RNAnorm to do so, which works great! However, my bulk RNA originally contained information per transcript, but has been summed to gene level (i.e., raw counts per gene). Can i still use TPM to normalize my data? Or is it not correct if you have your data on gene-level rather than transcript-level?
Kind Regards,
Celine

Hi @Celine-075!
Yes, It is OK to sum the transcript-level count data to the gene-level before the normalization.
Best,
Janez

Great! I've uses a regular human genome gtf file, thats still correct then right?

It should be, yes. What was the quantification method/tool?

I ran this code:
from rnanorm import TPM

#read in gtf file with TPM function from rnanorm
tpm = TPM(gtf="D:/scIntegrate_py/.spyproject/ref_data/Homo_sapiens.GRCh38.111.gtf").set_output(transform="pandas")
#and apply to the counts_matrix_bulk_filt
counts_TPM = tpm.fit_transform(counts_matrix_bulk_filt)

I mean what was the quantification method used to obtain the transcript-level counts that were the input to the rnanorm functions? This is an important consideration, since some tools are suitable for transcript-level analysis (RSEM, Salmon, etc.) while tools like featureCounts or HTSeq-count are only suitable for gene-level analysis.

Ah I see. We have received the bulk data in the summed version. I will need to check that with the people who summed it and come back to it later. Thank you for informing me on this.

so we have used HT-seq. So then CPM would be a better way to normalize?

Compared to TPM, the CPM doesn't normalize for gene length, which is preferred in certain scenarios. However, the normalization choice would not matter much if the input read counts are biased to begin with. Please see this discussion on why count-based methods (HT-seq, featureCounts) are not suitable for transcript-level analysis/reporting: https://www.biostars.org/p/424242/#424343

I'm suggesting that the normalization type choice (which depends on the library preparation type and/or planned downstream data processing) cannot fix issues introduced by the potentially inappropriate usage of the upstream gene quantification tool(s). Beyond that, I can't give further advice.

Alright, thanks for your help!


release fixup

Summary
Merging the last release PR didn't trigger a publish. Hoping that merging this will cause changeset to detect that the current version hasn't been published.

Trying to figure out what went wrong here. Checking this successful publish: https://github.com/sigstore/sigstore-js/actions/runs/4754341887/jobs/8447049392
This one says No changesets found, attempting to publish any unpublished packages to npm
The one that failed: https://github.com/sigstore/sigstore-js/actions/runs/4759623510/jobs/8459576890
Says All changesets are empty; not creating PR
I think the issue is actually that there is still an empty changeset on main: https://github.com/sigstore/sigstore-js/blob/main/.changeset/wild-rings-brake.md
This is strange, because the empty changeset was merged in 17 hours ago and the release that failed was merged in 11 hours ago, I would have expected it to be deleted in the version pr.
Digging further, it seems like these dependabot PRs, when merged into main don't trigger builds.
Pretty sure this is because github actions comitted the change using the GITHUB_TOKEN which won't trigger additional workflow runs.
--
TL'DR: When GH actions automerges dependabot prs, these don't get included in Version Packages Pull Requests that are already open, so don't get deleted, and when left on main prevent a new release from going out.
Possible solutions:

Use a PAT instead of GITHUB_TOKEN  to do the auto merging
Stop doing auto-merging with GH?
Maybe others I haven't thought of

@bdehamer I think the short term fix here is to delete the changeset on main


How to console log results from additional fb permissions (eg user_birthday)?

Sorry if this is a noob question but once i log in how do i see the results for additional fb data (e.g user_birthday) in the console.
I can successfully log in and see profile information in the console. I have also created a test user account via fb to ensure i have access to the permissions such as user_birthday. Now, when i am logging into the app it tells me that the app wants permission to see my birthday and I click okay. However i cant work out how to see this data.

Take a look at the following component in the examples, it retrieves the user profile photo.
https://github.com/magus/react-native-facebook-login/blob/master/example/components/Login.js#L86
You can make Facebook Graph API calls for that information assuming you have permissions for it.


[Feature Request]: Add Function library to UDJE and Java Filter

What would you like to happen?
Add a formula editor and formulas with examples to the UDJE and Java Filter transforms
Issue Priority
Priority: 3
Issue Component
Component: Transforms

.take-issue


Fix NullPointerException IgluAdapter

@chuwy I added better unit testing. Given that the raw query string is parsed inside a Loader of enrich, I created a Thrift payload as the one created in SSC to use as input of the test. This logic opens the way to stronger unit testing in enrich.

Looks awesome!


Feautre/extend sys meta

Describe your changes
Collect additional informations from peers

List of IP addresses and MAC addresses
System serial number
System manufacturer
System product name

Issue ticket number and link
Checklist

[ ] Is it a bug fix
[ ] Is a typo/documentation fix
[x] Is a feature enhancement
[ ] It is a refactor
[ ] Created tests that fail without the change (if possible)
[ ] Extended the README / documentation, if necessary

@pappz @pascal-fischer lets postpone merging until https://github.com/netbirdio/netbird/pull/1540 is ready


🐛 Bug Report: Realtime subscribe creates two websocket connections

👟 Reproduction steps
I use this code to connect:
class _MyChatPageState extends State<ChatPage> {
  AuthState? _state;
  late final Client client = Client();
  late final Realtime realtime;
  late final RealtimeSubscription _chat;
  final String chatCollectionId = "61346bcfbd96e";

  @override
  void initState() {
    super.initState();
    client.setEndpoint(Constants.endPoint).setProject(Constants.projectId);
    realtime = Realtime(client);
    subscribeChat();
  }

  @override
  void deactivate() {
    _chat.close();
    super.deactivate();
  }

  subscribeChat() {
    try {
      _chat = realtime.subscribe(['collections.$chatCollectionId.documents']);
    } on AppwriteException catch (error) {
      print(error.message);
    }
    _chat.stream.listen((data) {
      if (data.payload.isNotEmpty) {
        switch (data.event) {
          case "database.documents.create":
            print(data.payload);
            break;
          default:
            break;
        }
      }
    });
  }
}

i think it tries to create a reconnect after first connect.. the second one can be closed on dispose, but the first one can not be closed

👍 Expected behavior
1 connection for 1 subscribe :)
👎 Actual Behavior
2 connections for 1 subscribe :)
🎲 Appwrite version
Version 2.0.x
💻 Operating system
Linux
🧱 Your Environment
No response
👀 Have you spent some time to check if this issue has been raised before?

[X] I checked and didn't find similar issue

🏢 Have you read the Code of Conduct?

[X] I have read the Code of Conduct

@lohanidamodar any news on this one?

https://github.com/appwrite/sdk-generator/pull/314


Technical Acceptance Criteria: - Review

Check on below:
Application links all function correctly.
The application's CSS selectors and properties are consolidated and organized to follow a semantic structure.
The application's CSS file is properly commented.

additional comments added - css divided into logical section