Implementing profile-type

Type of change

[ ] Refactor
[x] New feature
[ ] Bug fix
[ ] Optimization
[x] Documentation Update

Description
Implementing profile-type to allow specifying the type of metrics profile to use in a single run
Related Tickets & Documents

Related Issue #
Closes #479

Checklist before requesting a review

[x] I have performed a self-review of my code.
[x] If it is a core feature, I have added thorough tests.

I'm not very convinced of the naming of the new flag --profile-type but I'm out of ideas today, open to suggestions :)

As I said previously, I'm not a big fan of this change, the initial intention of creating a "report" metrics profile was to reduce the overall number of indexed documents in periodic runs (cpt) and use the "regular" profiles for debugging/troubleshooting purposes when needed
Using both by default,  goes against that philosophy 🤷🏽♂

Using both by default, goes against that philosophy

I am not confident we can rely solely on the metrics report. Running both allows us to build confidence and close any gaps in the metrics-report without losing more data that would require us to re-run.
It's a step towards enabling reporting-only mode. We will get there. :)

Looks like we need to add/modify CI tests for this new use case too.

As I said previously, I'm not a big fan of this change, the initial intention of creating a "report" metrics profile was to reduce the overall number of indexed documents in periodic runs (cpt) and use the "regular" profiles for manual runs and/or debugging/troubleshooting purposes when needed

ack - understand the reasoning behind the report.

Using both by default, goes against that philosophy 🤷🏽♂

True. However, I don't think it makes sense to go cold-turkey (ie flip the bit before we get confidence).
With Prow, we could eventually just depend on the must-gather to collect the promdump -- but that even isn't a 100% foolproof method.

As I said previously, I'm not a big fan of this change, the initial intention of creating a "report" metrics profile was to reduce the overall number of indexed documents in periodic runs (cpt) and use the "regular" profiles for manual runs and/or debugging/troubleshooting purposes when needed

ack - understand the reasoning behind the report.

Using both by default, goes against that philosophy 🤷🏽♂

True. However, I don't think it makes sense to go cold-turkey (ie flip the bit before we get confidence).
With Prow, we could eventually just depend on the must-gather to collect the promdump -- but that even isn't a 100% foolproof method.

100%, let's try to make a soft transition :)


Projects task2 Radha93M

Install Task Capture from
https://vajrang.sharepoint.com/:u:/r/sites/UiPathProjects/Shared Documents/General/Softwares/task-capture-setup.exe?csf=1&web=1&e=cOXO3D

Hi  Team,
Completed the assigned task .Please review my code.
Here is the  #1803 for the same.
Thank you.


Using project reference

Referencing project instead of nuget

Do you mean to add neo as a submodule? Only reference neo with your local machine's relative path won't work in others machine.

I prefer with submodules too

it works but is a little bit weird, i think that submodules will be better here


Add checkbox for dietary requirements notice

What this PR does / Why we need it
It adds the dietary checkbox for legal purposes.
Some questions

[X] I have read the contributing guidelines
[X] I abide by this repository Code of Conduct
[X] I understand that my PR won't be merged until Travis gives a "green light"

Seems fine to me :smile:.


Sounds on Android

Hy,
When I execute an hexi game on Android I got the following Error:
Script Error: Failed to execute decodeAudioDataon AudioContext: parameter 1 is not of type ArrayBuffer
Regards

Thanks for reporting that!
Only Chrome 50+ for Android support the WebAudio API, which Hexi uses for its sound module
http://caniuse.com/#feat=audio-api
Which Android browser version are you testing?

I have forgotten to tell you that I have created an apk package with DroidScript.
So the html is rendered in Android Webview.

Interesting! 😄
These are not technologies that I'm familiar with.
Do you know whether the Android Webview is compatible with the WebAudio API?
My reading of this document implies that it isn't:
https://developer.chrome.com/multidevice/webview/overview
If this is correct, it means Android WebView is running Chrome v30, which doesn't support the WebAudio API.
Is this a deal-breaker?
If so, I recommend a workaround by using the Howler.js library to handle playing your game sounds:
https://github.com/goldfire/howler.js/
It has a fallback on HTML5 audio.

Howler is awesome
Thank you very much

Great, hope that helps!


NOISSUE - Fix opc-ua adapter

What type of PR is this?
This is a bug fix because it fixes the opc-ua adapter and makes it fully functional.
What does this do?
Rectifies the node-id parsing, modifies event handling to sync with things service events to allow the adapter to work as expected.
Which issue(s) does this PR fix/relate to?
Resolves #2037
Have you included tests for your changes?
No
Did you document any new/modified feature?
Yes, documentation is updated.
Notes

@arvindh123 and @rodneyosodo please review this PR


Update SCTP (w/ delayed ack and writeLoop)

Description
No changes in webrtc code. This simply updates datachannel, sctp and transport modules.
Reference issue
Relates to pion/sctp#40

Nice work!
I am happy to merge, would you mind creating new tags for each of the deps (so we aren't pinning against SHA1s)
You should have access to create tags, just bump each minor number.
thanks @enobufs

Let me make sure if I understood correctly. You'd want me to.

Tag transport, sctp and datachannel before merging
You would merge them all, then tag webrtc
Correct?

@enobufs exactly! after you create the tag you can do go get -u github.com/pion/transport && go mod tidy and should pull the new version and clear out the older ones.

@Sean-Der, all dependencies tagged:

<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>


Fixed map center

Is there a way to make the center of a map fixed? I need to be able to zoom in and out without changing the map's center regardless the position of the mouse. Can't seem to get this to work.

You asked this in https://stackoverflow.com/questions/36828519/leafletjs-lock-map-center/36836741. As stated in the CONTRIBUTING.md file, do not use the issue tracker for asking questions.


Rework splitCoin to splitCoins

Description
Describe the changes or additions included in this PR.
Test Plan
How did you test the new or updated feature?

If your changes are not user-facing and not a breaking change, you can skip the following section. Otherwise, please indicate what changed, and then add to the Release Notes section as highlighted during the release process.
Type of Change (Check all that apply)

[ ] user-visible impact
[ ] breaking change for a client SDKs
[ ] breaking change for FNs (FN binary must upgrade)
[ ] breaking change for validators or node operators (must upgrade binaries)
[ ] breaking change for on-chain data layout
[ ] necessitate either a data wipe or data migration

Release notes

added some comments offline that needs to be resolved before merging this


Improvement: HTML mails

Hi,
I'm using this lib in a project and I found myself having the need to send mails with html body. so I was thinking what do you think if I add the setting to this and make the PR?
Regards

@chrux  +1

@chrux sure. that would be great.


Support for "doas" become_method

Howdy!
I've hacked up a first-pass at basic support for the doas become_method, which is working for me on FreeBSD.
I haven't added any unit tests yet, as I'm not familiar with how the tests are laid out here.
Cheers,
Mike

Champion! The structure of the connection plug-ins will drastically change for asynchronous connect when that arrives, so right now what you have is perfect -- a little cutpaste it's all I've been doing too :P
Eventually these will be converted to a small set of state machine classes, and the most important thing to capture are the expected strings and general behaviour.
I need to write better stub test implementations for a bunch of stuff, including su, so I will add doas to the list.
Also the "mitogen" Travis jobs are failing right now due to the child process reaping issue -- don't worry about those either.

Glorious!
Thanks so much again for all your work with mitogen.  It's on master now, I hope to cut another release in the coming week once a few more tickets are closed


Update sql-server-linux-setup-machine-learning-sql-2022.md

Creating a branch for Linux updates to add Centos support and simplify download instructions

Docs Build status updates of commit 9b62148:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/linux/sql-server-linux-setup-machine-learning-sql-2022.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit 7bed8d6:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/linux/sql-server-linux-setup-machine-learning-sql-2022.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit f45a553:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/linux/sql-server-linux-setup-machine-learning-sql-2022.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Replaced with https://github.com/MicrosoftDocs/sql-docs-pr/pull/24335


Tunable CCL global settings at the Python-level

This PR decouples the (otherwise connected at the C level) CCL accuracy parameters from Cosmology objects, at the Python level.
In a new module parameters.py I have implemented the class CCLParameters which wraps the SWIG-generated classes for the spline parameters, the GSL parameters, and the physical constants.
In the spirit of making Cosmology objects truly immutable (which they ought to be) I have deprecated the option to mutate the accuracy parameters of any instantiated Cosmology: all new instances are populated with the global parameters at the time they are created.
Users can access (and set) the global parameters using ccl.gsl_params, ccl.spline_params, and ccl.physical_constants.
To do this I removed the const type definition of the C-level spline and GSL parameters, so they are added in ccllib.cvar by SWIG. Physical constants were already mutable (because T_CMB is temporarily mutated in Cosmology).
This feature comes with the advantage that we can remove all dummy cosmologies from the codebase. Every time we need one just to look up the accuracy parameters, we can just peek at the parameters at the time of instantiation, if a Cosmology is not provided.
Maybe it's also worth considering having something like ccl.spline_params.set_accuracy("high" | "medium" | "low") with pre-made parameter sets. High accuracy would be what is expected from LSST-like analyses with slower computation, while low accuracy will give a considerable increase in speed. This is one of the things mentioned in #588.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

59 of 67 (88.06%)  changed or added relevant lines in 3 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.1%) to 96.916%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

pyccl/constants.py
55
63
87.3%

Totals

Change from base Build<PHONE_NUMBER>:
-0.1%

Covered Lines:
4462

Relevant Lines:
4604

💛  - Coveralls

@nikfilippas Do you want to rebase/merge master and I then rewrite the warning to match the new gsl_params setup?

@tilmantroester okay, merged and adjusted the warning as required. Have you managed to have a look? Would you like to review this?

@damonge back to you. I agree with your overall comment. CCL has to be re-written in C++ like @tilmantroester has suggested, but changing the entire internal structure will require a lot of work. This PR does the job in what I believe is an elegant way, but at some point how CCL handles the parameters needs to change.

@tilmantroester @nikfilippas are we happy to leave C-level modifications for a future PR and merge this one? If so, I can approve.

@damonge I think there is consensus now.

@nikfilippas can you resolve the conflicts? I'll approve then when the tests pass.

@damonge Done.


PopupService.ts should be renamed

Hi,
when using a case sensitive file system, the import of popupService in grid.ts fails, because the PopupService.ts should be renamed popupService.ts

thanks!

fixed.

@ceolter thanks. Any plan for releasing a new version ?

yes. next two days. i've a few cleanup issues since the last release, including this.


See notifications ?

Hey ! I've strated using your twitter go app, and i have a a questions : ) Is it possible to see my notifications ? I can't find it in the doc.
Thanks for your work !

Hey @edi0th ! I think you mean by notifications whether someone mentioned you or retweetet something?
You can use t timeline [mentions/retweets] to see if there is anything new.
What there isn't, however, is something like a collected list of both. Maybe that would be something for a new feature, but that's not possible at the moment.
Cheers!

Yes, sorry it wasn't very clear, but your partially answered.
When i'm on the «ringbell» tab on twitter website, the list shows me a collected list of :
Tweets I made people liked, Tweets where I'm mentionned, Rewteets and new people who just followed me.
But with you answer, i understand it'es not possible at the moment : )


Response status code was unacceptable: 404

Issue Description
ios-app get error Response status code was unacceptable: 404
Steps to reproduce
Hello
I'm migrating ios-app.to sakura-server
my app can't load resources from Parse-Server
ios-app returns error below
Response status code was unacceptable: 404 (Code: 1, Version: 1.14.2)
but server using --verbose options, outputs correct resources name.
Actual Outcome
verbose: {
"response": {
"results": [
{
"objectId": "XXXXXX",
"file": {
"__type": "File",
"name": "XXXXXXX.zip",
"url": "http://XXXXXXXX:1337/parse/files/XXXXXXXXXX/XXXXXXX.zip"
},....
Environment Setup
parse-sdk 1.14.2
MongoDB shell version: 2.6.12
node v6.3.0
parse-server ==parse-json@2.2.0??
(using npm update -g parse-server i can't find version disp)
sakura-internet

I think server returns url is wrong or access setting is wrong.
Is anybody know about this?

I found couse of error.
DB don't have resource.
I have to re-import resources...
migration tool db copy is imcomplete..


Fix some typos in tests

Just a few typos I found while running tests.

Changes Unknown when pulling fcad80a3f93dba3df419922225a40bf071ad9219 on KarboniteKream:typo into ** on MarshallOfSound:master**.


Release since 2.7.2?

/cc @petergoldstein @mperham
There appears to be a large number of commits since the last official/gem release of Dalli. Can we push a new gem sometime soon?
We're specifically looking for https://github.com/mperham/dalli/pull/492 which was merged ~6 months ago.
Thank you!

@tpitale I don't currently have the ability to publish new Dalli gems, but if @mperham wants to approve me I'm happy to publish an updated version this weekend.

Ack, I never gave @petergoldstein push rights.  What's your Rubygems email?

@mperham<EMAIL_ADDRESS>

Done!

@mperham Thanks.  I'll publish a version this weekend.

Thank you so much!

I just pushed 2.7.3.

Thanks @petergoldstein!


[BUG]: docker 启动报错 TypeError: 'type' object is not subscriptable

 * Starting MySQL database server mysqld
su: warning: cannot change directory to /nonexistent: No such file or directory
   ...done.
execute sql file: /docker-entrypoint-initdb.d/case_1_student_manager.sql
mysql: [Warning] Using a password on the command line interface can be insecure.
execute sql file: /docker-entrypoint-initdb.d/case_2_ecom.sql
mysql: [Warning] Using a password on the command line interface can be insecure.
execute sql file: /docker-entrypoint-initdb.d/init.sql
mysql: [Warning] Using a password on the command line interface can be insecure.
execute sql file: /docker-entrypoint-initdb.d/knowledge_management.sql
mysql: [Warning] Using a password on the command line interface can be insecure.
execute sql file: /docker-entrypoint-initdb.d/test_case_info.sql
mysql: [Warning] Using a password on the command line interface can be insecure.
execute sql file: /docker-entrypoint-initdb.d/user_config.sql
mysql: [Warning] Using a password on the command line interface can be insecure.
mysql: [Warning] Using a password on the command line interface can be insecure.
playsound is relying on another python subprocess. Please use `pip install pygobject` if you want playsound to run more efficiently.
Traceback (most recent call last):
  File "pilot/server/dbgpt_server.py", line 11, in <module>
    from pilot.configs.config import Config
  File "/app/pilot/__init__.py", line 1, in <module>
    from pilot.embedding_engine import SourceEmbedding, register
  File "/app/pilot/embedding_engine/__init__.py", line 1, in <module>
    from pilot.embedding_engine.source_embedding import SourceEmbedding, register
  File "/app/pilot/embedding_engine/source_embedding.py", line 9, in <module>
    from pilot.vector_store.connector import VectorStoreConnector
  File "/app/pilot/vector_store/connector.py", line 1, in <module>
    from pilot.vector_store.chroma_store import ChromaStore
  File "/app/pilot/vector_store/chroma_store.py", line 4, in <module>
    from pilot.logs import logger
  File "/app/pilot/logs.py", line 13, in <module>
    from pilot.speech import say_text
  File "/app/pilot/speech/__init__.py", line 1, in <module>
    from pilot.speech.say import say_text
  File "/app/pilot/speech/say.py", line 34, in <module>
    def _get_voice_engine(config: Config) -> tuple[VoiceBase, VoiceBase]:
TypeError: 'type' object is not subscriptable

@dubaoquan404  Which version of python are you using.
You can run the following command to show.
$ docker run --rm db-gpt python3 --version

The output like following:
==========
== CUDA ==
==========

CUDA Version 11.8.0

Container image Copyright (c) 2016-2023, NVIDIA CORPORATION & AFFILIATES. All rights reserved.

This container image and its contents are governed by the NVIDIA Deep Learning Container License.
By pulling and using the container, you accept the terms and conditions of this license:
https://developer.nvidia.com/ngc/nvidia-deep-learning-container-license

A copy of this license is made available in this container at /NGC-DL-CONTAINER-LICENSE for your convenience.

WARNING: The NVIDIA Driver was not detected.  GPU functionality will not be available.
   Use the NVIDIA Container Toolkit to start this container with GPU support; see
   https://docs.nvidia.com/datacenter/cloud-native/ .

Python 3.10.12

@dubaoquan404 Which version of python are you using.
You can run the following command to show.
$ docker run --rm db-gpt python3 --version

The output like following:
==========
== CUDA ==
==========

CUDA Version 11.8.0

Container image Copyright (c) 2016-2023, NVIDIA CORPORATION & AFFILIATES. All rights reserved.

This container image and its contents are governed by the NVIDIA Deep Learning Container License.
By pulling and using the container, you accept the terms and conditions of this license:
https://developer.nvidia.com/ngc/nvidia-deep-learning-container-license

A copy of this license is made available in this container at /NGC-DL-CONTAINER-LICENSE for your convenience.

WARNING: The NVIDIA Driver was not detected.  GPU functionality will not be available.
   Use the NVIDIA Container Toolkit to start this container with GPU support; see
   https://docs.nvidia.com/datacenter/cloud-native/ .

Python 3.10.12

@fangyinc
==========
== CUDA ==
==========

CUDA Version 11.7.1

Container image Copyright (c) 2016-2022, NVIDIA CORPORATION & AFFILIATES. All rights reserved.

This container image and its contents are governed by the NVIDIA Deep Learning Container License.
By pulling and using the container, you accept the terms and conditions of this license:
https://developer.nvidia.com/ngc/nvidia-deep-learning-container-license

A copy of this license is made available in this container at /NGC-DL-CONTAINER-LICENSE for your convenience.

WARNING: The NVIDIA Driver was not detected.  GPU functionality will not be available.
   Use the NVIDIA Container Toolkit to start this container with GPU support; see
   https://docs.nvidia.com/datacenter/cloud-native/ .

Python 3.8.10


Draft: Fail if mons in quorum are less than expected

Jira: https://issues.redhat.com/browse/OSPRH-2540

(Still a draft? If so we should probably convert it to a draft PR.)

(Still a draft? If so we should probably convert it to a draft PR.)

Yes, sorry, I think it deserves a few more CI runs. I'll resume this one after pto

I'll turn to draft and unblock when I have a full green run in CI via teatproject

recheck

recheck

This patch is getting bigger, and I'm worried to lose the scope the more I work with the CI integration.
Before adding an extra patch on top related to network and IP migration (which seems still problematic in CI), I'd like to merge the changes proposed here because I had a green execution from a testproject.

This patch is getting bigger, and I'm worried to lose the scope the more I work with the CI integration. Before adding an extra patch on top related to network and IP migration (which seems still problematic in CI), I'd like to merge the changes proposed here because I had a green execution from a testproject.

@cescgina @marios I'm wondering if we can land this patch so I don't risk to diverge from the topic of this PR. Still the job is not executed, but I'm refining the procedure more to deal with upstream multinode CI other than IR (that won't be used for this purpose).

@cescgina thank you!


Support overflow_action in v14 api

I found that implementing buffer_queue_full_action in v0.14 requires change of internal API of Buffer.
This pull-request does:

merge Buffer#emit and Buffer#emit_bulk to Buffer#write
fix Buffer#write to get a set of metadata and its data (as a hash) to control commit/rollback as a transaction

This change is based on #912

This fix changes more code than expected: details are in commit comment here:
https://github.com/fluent/fluentd/pull/943/commits/c3489d798415d736349134a0b9cf3527a8cbe9fd

I confirmed that CI is green now.


Discard entity not being removed from collection

I'm not sure what I'm doing wrong with either my entity class or my projection policy but I can't get my discard event to remove that entity from the collection.
A simplified version of my entity class looks like this:
class User(WithReflexiveMutator, AggregateRoot):
    """Aggregate root for user.
    A user is a namespace for accessing all workflow platform resources.
    """
    def __init__(self, user_id, name, password, email, default_domain, **kwargs):
        super(User, self).__init__(**kwargs)
        self.user_id = self._validate_user_id(user_id)
        self.default_domain = self._validate_domain(default_domain)
        self.domains = set()

    class Created(Event, AggregateRoot.Created):
        """Published when a user is created."""

        @property
        def user_id(self):
            return self.__dict__['user_id']

        @property
        def name(self):
            return self.__dict__['name']

        @property
        def password(self):
            return self.__dict__['password']

        @property
        def email(self):
            return self.__dict__['email']

        @property
        def default_domain(self):
            return self.__dict__['default_domain']

        def mutate(self, cls):
            entity = cls(**self.__dict__)
            entity.domains.add(self.default_domain)
            entity.increment_version()
            return entity

    class Discarded(Event, AggregateRoot.Discarded):
        """Published when a user is discarded."""

        @property
        def domain_namespace(self):
            return self.__dict__['domain_namespace']

        def mutate(self, entity):
            entity._is_discarded = True
            return None

    @staticmethod
    def create(name, password, email, default_domain, **kwargs):
        """Creates a new user."""
        user_id = uuid4()
        event = User.Created(
            originator_id=user_id,
            user_id=user_id,
            default_domain=default_domain,
            **kwargs
        )
        entity = event.mutate(cls=User)
        publish(event)
        return entity

    def discard(self):
        self._apply_and_publish(
            self._construct_event(
                User.Discarded,
                domain_namespace=self.default_domain
            )
        )

Here's my projection policy:
class UserProjectionPolicy:
    """Updates user collection whenever a user is created or discarded.
    """

    def __init__(self, user_collections):
        self.user_collections = user_collections
        subscribe(self.add_user_to_collection, self.is_user_created)
        subscribe(self.remove_user_from_collection, self.is_user_discarded)

    def close(self):
        unsubscribe(self.add_user_to_collection, self.is_user_created)
        unsubscribe(self.remove_user_from_collection, self.is_user_discarded)

    def is_user_created(self, event):
        if isinstance(event, (list, tuple)):
            return all(map(self.is_user_created, event))
        return isinstance(event, User.Created)

    def is_user_discarded(self, event):
        if isinstance(event, (list, tuple)):
            return all(map(self.is_user_discarded, event))
        return isinstance(event, User.Discarded)

    def add_user_to_collection(self, event):
        assert isinstance(event, User.Created), event
        domain_namespace = event.default_domain
        collection_id = make_user_collection_id(domain_namespace)
        try:
            collection = self.user_collections[collection_id]
        except KeyError:
            collection = register_new_collection(collection_id=collection_id)

        assert isinstance(collection, Collection)
        collection.add_item(event.originator_id)

    def remove_user_from_collection(self, event):
        if isinstance(event, (list, tuple)):
            return map(self.remove_user_from_collection, event)
        assert isinstance(event, User.Discarded), event
        domain_namespace = event.domain_namespace
        collection_id = make_user_collection_id(domain_namespace)
        try:
            collection = self.user_collections[collection_id]
        except KeyError:
            pass
        else:
            assert isinstance(collection, Collection)
            collection.remove_item(event.originator_id)

I can verify that when I use User.create the user is instantiated and added to the collection.

Does it go through the pass statement in remove_user_from_collection()?
If not, the event isn't getting published, which might be because you need to call save() and discard()? If that feels weird to you, it feels weird to me. Maybe the class AggregateRoot should extend the inherited discard() method, by calling save().
Alternatively, if the pass statement is reached, then the ID isn't matching. I don't know what value you are passing for domain_namespace, but any value should work if there is only one user, so long as the event.default_domain in add_user_to_collection() is the same value as event.domain_namespace in remove_user_from_collection()? Looking at the code, I believe the value will be the same.
So I would check if the remove_user_from_collection() is actually being called, and if it isn't, then maybe calling user.save() after user.discard() would help? If that doesn't help, you'll have to push your code to a branch in your repo, so I can what's actually happening ;-)

Or, alternative to avoiding save() after discard(), to make everything consistent, maybe the create() method should just append the Created event to the new entity's list of  _pending_events, so that if you create() the you also have to save()? I don't know which you would prefer :-)

@johnbywater thanks for the input. I  was using the save and I agree that it would be nice to have save handled a little more intuitively.
I was able to debug the remove_user_from_collection method with the following change:
    def remove_user_from_collection(self, event):
        if isinstance(event, (list, tuple)) and len(event) < 1:
            # this line does not seem to be doing what's intended because an empty event ends up being processed
            # return map(self.remove_user_from_collection, event)
            return None
        elif isinstance(event, (list, tuple)):
            event = event.pop()
        assert isinstance(event, User.Discarded), event
        domain_namespace = event.domain_namespace
        collection_id = make_user_collection_id(domain_namespace)
        try:
            collection = self.user_collections[collection_id]
        except KeyError:
            pass
        else:
            assert isinstance(collection, Collection)
            collection.remove_item(event.originator_id)

Great you fixed it! Why didn't it work as expected? What was actually happening?


Convert to f-strings

Codecov Report

Merging #415 into master will increase coverage by 0.08%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master     #415      +/-   ##
==========================================
+ Coverage   90.66%   90.75%   +0.08%
==========================================
  Files          43       43
  Lines        2926     2930       +4
==========================================
+ Hits         2653     2659       +6
+ Misses        273      271       -2

Continue to review full report at Codecov.

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

Codecov Report

Merging #415 into master will increase coverage by 0.08%.
The diff coverage is 95.34%.

@@            Coverage Diff             @@
##           master     #415      +/-   ##
==========================================
+ Coverage   90.66%   90.75%   +0.08%
==========================================
  Files          43       43
  Lines        2926     2930       +4
==========================================
+ Hits         2653     2659       +6
+ Misses        273      271       -2

Impacted Files
Coverage Δ

django_q/signals.py
100% <100%> (+8.33%)
:arrow_up:

django_q/brokers/orm.py
97.95% <100%> (ø)
:arrow_up:

django_q/brokers/mongo.py
100% <100%> (ø)
:arrow_up:

django_q/management/commands/qinfo.py
95.45% <100%> (ø)
:arrow_up:

django_q/brokers/redis_broker.py
95.91% <100%> (ø)
:arrow_up:

django_q/tests/tasks.py
92.3% <100%> (ø)
:arrow_up:

django_q/status.py
97.5% <100%> (ø)
:arrow_up:

django_q/monitor.py
83.33% <85%> (ø)
:arrow_up:

django_q/cluster.py
91.99% <93.47%> (+0.07%)
:arrow_up:

django_q/brokers/disque.py
98% <94.73%> (ø)
:arrow_up:

... and 3 more

Continue to review full report at Codecov.

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


Counting_sort in Cpp, C, python, Js

Here is the code for Counting sort in C, Cpp, Python, and JavaScript along with a readme file with a brief explanation about counting sort.

Can you please delete the python file we already have that

Can you please delete the python file we already have that

ok.. but please tell me that do I need to re-commit the PR...becoz I am new to github

yes

yes

done!

Does it have any problem?
please tell me if there are some!
or do I need to do something extra!

Add driver code in js file . I mentioned previously as well.

Now I think it's done! I resolved all the problems. Sorry for the inconvenience.


luarocks is not executable

Following the guide for install neorg with lazy.nvim. There is error during building.
Error executing vim.schedule lua callback: Vim:E475: Invalid value for argument cmd: '/home/x/.local/share/nvim/lazy/luarocks.nvim/.rocks/bin/luarocks' is not executable
stack traceback:
        [C]: in function 'system'
        ...hare/nvim/lazy/luarocks.nvim/lua/luarocks-nvim/rocks.lua:39: in function 'ensure'
        /home/x/.local/share/nvim/lazy/neorg/build.lua:14: in function </home/x/.local/share/nvim/lazy/neorg/build.lua:9>

Similar error on windows:
..\nvim-data\lazy\luarocks.nvim.rocks\bin\luarocks.bat' is not executable
There is no directory called ".rocks" inside luarocks.nvim\

Figure this out, need to rebuild luarocks.nvim
sudo apt install liblua5.1-dev

# open nvim
:Lazy build luarocks.nvim

Indeed, on windows too, it was silently failing with error code 0 because it could not find the lua.h file
However, there are a few more issues that popped up afterward, like:

the .rocks directory being saved to %appdata%/temp instead of to the plugin directory
the luarocks.bat file being located inside the .rocks/ folder instead of .rocks/bin/
etc..
I'll keep looking but it might also be because of my setup, using scoop as a command-line installer for windows.

I'm on windows, too. Using luajit (https://github.com/DevelopersCommunity/cmake-luajit) via winget and Neovim v0.9.5
So I guess at least it's not a scoop problem, @0x546F6D 😃
There is no bin directory inside .rocks after installation. I've copied the .bat files from .rocks into a newly created bin directory and neorg builds again.
After reopening neovim, another error appears for me:
Unable to load the luarocks package loader. Try re-running the build stage (`:Lazy build luarocks.nvim`). Full trace: module 'luarocks.loader' not found:
	no field package.preload['luarocks.loader']
cache_loader: module luarocks.loader not found
cache_loader_lib: module luarocks.loader not found
	no file '.\luarocks\loader.lua'
	no file 'C:\Program Files\Neovim\bin\lua\luarocks\loader.lua'
	no file 'C:\Program Files\Neovim\bin\lua\luarocks\loader\init.lua'
	no file 'C:\Users\...\AppData\Local\nvim-data\lazy\luarocks.nvim\.rocks\share\lua\5.1\luarocks\loader.lua'
	no file 'C:\Users\...\AppData\Local\nvim-data\lazy\luarocks.nvim\.rocks\share\lua\5.1\luarocks\loader\init.lua'
	no file '.\luarocks\loader.dll'
	no file 'C:\Program Files\Neovim\bin\luarocks\loader.dll'
	no file 'C:\Program Files\Neovim\bin\loadall.dll'
	no file 'C:\Users\...\AppData\Local\nvim-data\lazy\luarocks.nvim\.rocks\lib\lua\5.1\luarocks\loader.dll'
	no file '.\luarocks.dll'
	no file 'C:\Program Files\Neovim\bin\luarocks.dll'
	no file 'C:\Program Files\Neovim\bin\loadall.dll'
	no file 'C:\Users\...\AppData\Local\nvim-data\lazy\luarocks.nvim\.rocks\lib\lua\5.1\luarocks.dll'

I'm no lua expert at all but it seems that module paths on windows are different maybe?

What I did after copying the .rocks folder from AppData/Local/Temp/nvim.0/ to nvim-data/lazy/luarocks.nvim, was:

copy the whole content of the .rocks directory inside .rocks/bin
copy the whole content of .rocks/lua/luarocks inside .rocks/share/lua/5.1/luarocks

And it seems to work right now.. But yes, right now I am not trying to fix it, just trying to understand what is happening.

That does indeed get rid of error messages, Neorg doesn't want to start, though. I'll look into that. 😃

Thanks for all of your testing. This should be fixed now on the latest update as part of #17! Let me know if it solves anything :)

@vhyrro I've reinstalled (clean + install) luarocks.nvim and neorg and now it works like a charm! 👍
Thanks a lot! ❤

So how does one install the Lua header files on Windows (I'm using scoop for current neovim/lua stuffs)? I'm still not getting a .rocks directory in the plugin path, which is a bummer because

I found it easier to scoop install lua+luarocks then install neorg through luarocks and add the luarocks path to Neovim's package path.
package.path = package.path .. ";" .. vim.fn.expand("$HOME") .. "/scoop/persist/luarocks/rocks/share/lua/5.1/?/init.lua;"
package.path = package.path .. ";" .. vim.fn.expand("$HOME") .. "/scoop/persist/luarocks/rocks/share/lua/5.1/?.lua;"

No longer works (even after removing the change in Neorg that explicitly tries to use luarocks.nvim). I get same issue as https://github.com/nvim-neorg/neorg/issues/1363 when installing dependencies through system luarocks.

I also had a similar issue. Seeing the previous comments, I tried performing a :Lazy build luarocks.nvim at which point the error message said that Lua couldn't be found on my system. Re-installing the latest version of Lua via choco install lua resolved that issue, at which point I could :Lazy build luarocks.nvim and :Lazy build neorg. Everything is working fine now!

I'm getting this error on a new macbook (arm version). I have Lua 5.4.6 installed via homebrew. I could not get 5.1 because homebrew says its deprecated. :Lazy build luarocks.nvim fails with the following
  Performing luarocks `./configure` if Unix systems
...hare/nvim/lazy/luarocks.nvim/lua/luarocks-nvim/build.lua:137: Failed to install luarocks:
Configuring LuaRocks version dev...

Lua 5.1 interpreter not found in $PATH
You may want to use the flags --with-lua, --with-lua-bin and/or --lua-version
Run ./configure --help for details.

configure failed.


Inconsistent Tokenizer Padding Behavior in Unsloth

I've encountered an issue with inconsistent Gemma tokenizer padding in Unsloth.
As you can see in this code snippet:

I have three tokenizers for the Gemma model.  tokenizer and tokenizer_4bit (loaded from the Hugging Face library) exhibit left padding, while tokenizer_FastLanguageModel (loaded from Unsloth) has right padding.
I believe this inconsistency indicates a potential issue within the Unsloth library.

@JhonDan1999 The padding side of "right" is for training only - this is not a bug. For inference, one must use padding "left" or else you'll get wrong results.

thank you for the response Danial.
But I'm still confused could you please explain why there is a difference between the padding side used during training ("right") versus inference ("left")? The documentation doesn't seem to cover this, so additional context would be really helpful.
Another point I've noticed that the LLM's behavior changes significantly depending on whether padding is included or not. When I don't include padding, the model generates nonsensical text. But if I add padding (even when it may not be necessary), the model generates the desired output. Do you have any insights into why the presence or absence of padding has such a drastic effect on the model's behavior?

@JhonDan1999 Yes so left is only used for generation. If you use right, you'll get gibberish.
This only is important for batched decoding, and not single decoding.

I auto change the padding side to fix this issue


Hi, question about using this code

We are building a open marketplace DAO at www.screensaver.world. Can we use this code please?

Uses MIT license.
So yes, you can.


Add Computer Vision

{Computer Vision - Convolutional Neural Networks for Visual Recognition.}
{This is a course provided by Stanford.edu, In this tutorial students can get complete information of the course (Convolutional Neural Networks for Visual Recognition) along with notes, code snippets and a complete youtube playlist of the course.}

By submitting this pull request I confirm I've read and complied with the below requirements.
Failure to properly do so will just result in the pull request being closed and everyone's time wasted.

[x] I have read the Contribution guidelines and made sure my pull request follows it, specifically the part about promotions and markdown format.
[x] Any resources I am adding in this PR have been used by me and I can personally vouch for their quality.
[x] This pull request has a descriptive title. For example, Add [Resource Name] or Add [Topic Name], not Added new entries or update.
[x] I have double checked that I have only updated the minimum files that are required by this PR.

Closing because #31 merged


cordova ios 6.1.0 wkwebview all xhr POST requests are converting as blob request.

Hi,
I have migrated the Cordova app from UIWebview to WKWebview.I have a native scanner screen that is invoked from the webpage and to invoke this I am using the "cordova-plugin-wkwebview-file-xhr" and "cordova-plugin-wkwebviewxhrfix" plugins.
Which is working fine by launching a scanner. But on the same page, the other ajax post calls are getting failed and they are converted as blob requests.
I tried removing the "cordova-plugin-wkwebview-file-xhr" plugin post that all the post ajax call works perfectly. But Scanner will not be invoked without xhr plugin.
All the calls are getting invoked using xhr-polyfill.js file where the post calls are failing.
Can someone please help me to fix this issue?

Hi,
Can someone please help me in solving the above issue?
Is there any alternate plugin that is available to serve the same purpose as "cordova-plugin-wkwebview-file-xhr"?

@knkavya Any specific reason for using "cordova-plugin-wkwebviewxhrfix" plugin along with this plugin?

@manish2788 To provide local file access in our app I am using "cordova-plugin-wkwebviewxhrfix" plugin.

@knkavya Does that plugin do anything different from our plugin "cordova-plugin-wkwebviewxhr". Reason I am asking is to ensure the other plugin is not causing any conflict.

@manish2788 Yes. I am having a json file with json data which is kept in some server location and I am reading it as XMLHttpRequest(). Only by using "cordova-plugin-wkwebview-file-xhr" plugin, I was not able to read the json file. After installing "cordova-plugin-wkwebviewxhrfix" plugin along with this plugin I was able to read the json data properly in my app.
But this plugin is used only to read that json file and nowhere else it is used. In all the places only the "cordova-plugin-wkwebview-file-xhr" plugin is used.
Whenever the POST-call enters into xhr-polyfill.js send request my calls are getting failed and they are converted as blob request.

I'm having the same problem that my requests are showing up as blobs.   I don't know how big of deal that is except makes it harder to debug requests.
I was pointed to this plugin to help with ios 14 and cross sites cookies being saved correctly.
Also confused on what this plugin is actually doing.  Seems like XMLHttpRequest is a javascript funtion.
Probably wonder off and not sure if this has to do with the blob problem but my login call and cookies I can see.  Seems like the next two or three apis also have cookie and work correctly but then everything breaks down.  Hard to debug.

Is anyone having an update on the fix for this issue or any alternate solution for this?

Is anyone having an update on the fix for this issue or any alternate solution for this?

I got things working this way.
https://forum.ionicframework.com/t/ionic-3-wkwebview-ios-14-itp-best-options/201628/2?u=helpmelearn
I removed this plugin and other cookie plugins to fix this ios 14 issue.
I'm on ionic 3.20  with ionic-ios 5.1.1.

Is anyone having an update on the fix for this issue or any alternate solution for this?

I got things working this way.
https://forum.ionicframework.com/t/ionic-3-wkwebview-ios-14-itp-best-options/201628/2?u=helpmelearn
I removed this plugin and other cookie plugins to fix this ios 14 issue.
I'm on ionic 3.20 with ionic-ios 5.1.1.

I am using cordova 6.1.0 now if I downgrade the version to 5.1.1 which still having some of the references to UIWebview, So not sure whether Apple will approve the app or not.
Cordova version 5.1.1 for WKWebview is internally having "cordova-plugin-wkwebview-file-xhr" plugin installed with file xhr-polyfill.js and where the issue still exists.

Hi Team,
Any update on this issue fix?

Hi Team,
Any update on this issue fix?

@knkavya We are looking into the issue by validating the same over different platform version. We will provide the updates soon.

@knkavya We are looking into the issue by validating the same over different platform version. We will provide the updates soon.

@manish2788 Thank you for the update.
I am not getting any response for the post request which are converted as blob requests.
These requests were working fine in UIWebview where post requests and responses were fine.
Not sure is there anything that needs to be modified in the request or response handling for WKWebview.
Can you please provide more updates on this?

@manish2788 Thank you for the update.
I am not getting any response for the post request which are converted as blob requests.
These requests were working fine in UIWebview where post requests and responses were fine.
Not sure is there anything that needs to be modified in the request or response handling for WKWebview.
Can you please provide more updates on this?

@knkavya We cannot comment upon you are not getting the response but I would recommend you to create a basic starter cordova app, try adding an ajax request and observe the behaviour on same.

@knkavya We cannot comment upon you are not getting the response but I would recommend you to create a basic starter cordova app, try adding an ajax request and observe the behaviour on same.

@manish2788 Problem occurs only for the post request.
Below are the details of my request
Whenever my POST call enters performNativeXHR method inside CDVWKWebViewFileXhr below are the request data
requestId : b684.0000000008-0.2cdd62334e5df8
callbackFunction : nativeXHRResponse
urlString : https://store.*****.grp/shop/getAccountBalance
method : post
request :
<NSMutableURLRequest: 0x6000000052d0> { URL: https://store..grp/shop/getAccountBalance }
{
body = "c3RvcmVJZD0xOTc1MyZhZGRySWQ9MDAwMDEyMDA2OQ==";
callback = nativeXHRResponse;
headers =     {
accept = "application/json, text/javascript, /; q=0.01";
"content-type" = "application/x-www-form-urlencoded; charset=UTF-8";
"x-requested-with" = XMLHttpRequest;
};
id = "b684.0000000008-0.2cdd62334e5df8";
method = POST;
url = "https://store..grp/shop/getAccountBalance";
}
When the request enters a method
NSURLSessionDataTask *task = [self.urlSession dataTaskWithRequest:request completionHandler:^(NSData * _Nullable data, NSURLResponse * _Nullable response, NSError * _Nullable error)
Gives me security issue for the request as
Task .<6> finished with error [-1202] Error Domain=NSURLErrorDomain Code=-1202 "The certificate for this server is invalid. You might be connecting to a server that is pretending to be “store...” which could put your confidential information at risk."
and it is converting the request as a blob request.
Whereas for other calls I am not getting any security issue like this.
I have tried adding transport security exceptions to ignore invalid certificates, but the issue is still the same.

@manish2788 Problem occurs only for the post request.
Below are the details of my request
Whenever my POST call enters performNativeXHR method inside CDVWKWebViewFileXhr below are the request data
requestId : b684.0000000008-0.2cdd62334e5df8
callbackFunction : nativeXHRResponse
urlString : https://store.*****.grp/shop/getAccountBalance
method : post
request :
<NSMutableURLRequest: 0x6000000052d0> { URL: https://store..grp/shop/getAccountBalance }
{
body = "c3RvcmVJZD0xOTc1MyZhZGRySWQ9MDAwMDEyMDA2OQ==";
callback = nativeXHRResponse;
headers =     {
accept = "application/json, text/javascript, /; q=0.01";
"content-type" = "application/x-www-form-urlencoded; charset=UTF-8";
"x-requested-with" = XMLHttpRequest;
};
id = "b684.0000000008-0.2cdd62334e5df8";
method = POST;
url = "https://store..grp/shop/getAccountBalance";
}
When the request enters a method
NSURLSessionDataTask *task = [self.urlSession dataTaskWithRequest:request completionHandler:^(NSData * _Nullable data, NSURLResponse * _Nullable response, NSError * _Nullable error)
Gives me security issue for the request as
Task .<6> finished with error [-1202] Error Domain=NSURLErrorDomain Code=-1202 "The certificate for this server is invalid. You might be connecting to a server that is pretending to be “store...” which could put your confidential information at risk."
and it is converting the request as a blob request.
Whereas for other calls I am not getting any security issue like this.
I have tried adding transport security exceptions to ignore invalid certificates, but the issue is still the same.

@knkavya Issue doesn't seems to be related with plugin. Closing the same as conversion to blob request is expected behaviour of this plugin.

@knkavya Issue doesn't seems to be related with plugin. Closing the same as conversion to blob request is expected behaviour of this plugin.


Document running tests in parallel inside a dev environment

What was the end-user problem that led to this PR?
We do not have any documentation for running the test suite in parallel. Developers working on Bundler may be unaware that the test suite can be executed in parallel to help speed up the time needed to run tests.
What is your fix for the problem, implemented in this PR?
Document how to run the parallel Bundler test suit in the Contributing docs.

Thanks @colby-swandale :)
@bundlerbot merge


Documentation incorrect for creating Jiva backups

Description
The Jiva User Guide states the following command can be used to create a backup manually:
velero backup create <backup_name> --selector '!openebs.io/controller,!openebs.io/replica'

However, the labels used by the --selector are not present on the Jiva replica or controller pods. These pods actually use the label openebs.io/component with a value of either jiva-controller or jiva-replica.
Possible Solution
I suggest the documentation be updated as follows:
velero backup create <backup_name> --selector 'openebs.io/component notin (jiva-controller, jiva-replica)'

Screenshots

In the latest version of documentation, not even the "bad" documentation exists.


Requests being blocked after commit c21a3a6.

API requests are being blocked by Cloudfare after the recent commit. I have double checked my username, user ID and auth token (called 'X-AUTH' token internally). Any ideas?

Unfortunately I can check or fix this as all my IPs have been banned on Aniwatch and i don't have a VPN or a proxy.

 Are they IP banning people for trying to access their APIs? Are you able to use the site? If yes, then I might be banned too because I can access the site but my API reqs are being blocked (I don't even know if that is something that can happen). I made some changes to the API (locally ofcource) and wrote a script to download episodes since they no longer support downloads.

I leaked my username to the developer by an accident and all the IPs I ever used on that account got banned like this: https://i.kawaii.sh/2SK1N8B.png

I am reasonably comfortable with python, its just this reverse engineering web API stuff that goes over my head. If you had to guess, what would say the reason is for the requests being blocked. Do you reckon we are missing some header/cookies. Also, they changed some things (around the same time they introduced the reCaptcha on the login page) regarding their chat stuff.

P.S
If you don't want to continue to work on this, I totally understand, just tell me and I won't bother you again :)

Seems like it was just cloudflare blocking the requests fixed in this Commit


Rundeck 3.x support

When are we going to see rundeck 3.x support? The rundeck 3.x binaries has a different naming convention which is not backwards compatible.

Hi there!
We would happily accept a pull request to resolve this issue. If you need help or guidance on submitting, please don't hesitate to ask!
If you need help, or just wish to talk through issue please join the Chef Community Slack and look for the #sous-chefs channel.
Thanks,
Sous-Chefs

I'm installing 3.x currently and getting the proper profile, rundeck-config, and jaas configuration changes up to date.  I will have a PR for these changes in the next day or two.  We are also planning a major rewrite to simplify this cookbook if you'd like to throw into the ring on it.

@josephholsten Sorry I will not be able to create a PR at this moment. But if @ev0ldave is already working on this I would be more than happy


The merging process can change the number of solids causing errors

When the method merge_surfaces operation is used this can in cases cause volumes to be split in two. This process needs to be handled since otherwise the materials will be assigned wrongly.

and apparently the MSRE with individual stringers

Reworking the algorithm for similarity fixed this #44


deps: update metrics to v0.22

Update metrics and use the new APIs:

{increment,decrement}_gauge!() → gauge!().{increment,decrement}
increment_counter!() → counter!().increment()
histogram!() → histogram!().record()

Thanks!
We have pub use metrics actually, so technically it's a minor version upgrade for us too, but I'd like to hold the new release off for a bit. Is that okay for you to use the main branch until then?

I'm only using this in a personal side project, so no problem to wait a bit :)

Just released 0.6.0 that includes this update.


RabbitMQ Module

Hi there!
Great work bringing Testcontainers to Ruby!
I'm unable to start a RabbitMQ container using the RabbitMQ container module in an RSpec test suite. When invoking container.start, Testcontainers times out waiting for the container to become healthy. The specific error message is:
Testcontainers::TimeoutError:
       Timed out waiting for health check to be healthy

However, if I use Testcontainers::DockerContainer("rabbitmq:latest), this error doesn't occur.
For context, here's the code where container.start is called:
require 'rails_helper'
require 'testcontainers/rabbitmq'
require 'bunny'

RSpec.describe "Books", type: :request do

  rabbit = Testcontainers::RabbitmqContainer.new

  before(:all) do
    puts "Starting container"
    rabbit.start
    puts "Started container"
  end

For reference, the puts "Started container" line is never reached.

Note that the rabbitmqctl node_health_check healthcheck option has been deprecated by RabbitMQ.
After copying the contents of https://github.com/testcontainers/testcontainers-ruby/blob/main/rabbitmq/lib/testcontainers/rabbitmq.rb and modifying it locally, I now have a Testcontainer instance starting up. Instead of using a health-check on startup, I used a wait_for_logs strategy instead.

@mlk-kc do you mind sending a PR with the change? if the healthcheck option is deprecated is better to stop using it even in old versions of the images.

Hi @guilleiguaran : I'll make one now if that's cool? Apologies, I haven't been in work since last Wednesday!

@guilleiguaran : I've just attempted to push my local issue-20 branch but I don't think I have the rights to do this? Some console output which might help:
ERROR: Permission to testcontainers/testcontainers-ruby.git denied to mlk-kc.
fatal: Could not read from remote repository.

Please make sure you have the correct access rights
and the repository exists.

@mlk-kc you can create a fork of the project, push the branch to the fork, and open a pull request.
This guide describes the process: https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request

Apologies @guilleiguaran , its been a year or two since I used GitHub in this way 😅 ! Just opened the following PR for the changes; thank you for your assistance on setting the PR up!
https://github.com/testcontainers/testcontainers-ruby/pull/28


Possible Exploit

User devestk scored 1284 wpm with 100% accuracy. Never seen a wpm nearly that high.

Thanks for reporting, yes I will add a ban for this specific user!


A reverse RDP attack on Neutrinordp: code execution on the RDP client

Hi.
Please refer to the content of this link.(https://research.checkpoint.com/2019/reverse-rdp-attack-code-execution-on-rdp-clients/)
Whether Neutrinordp would optimize this vulnerability？

@SvenDowideit


docker-compose won't run correctly before database creation

File: compose/rails.md, CC @londoncalling
FATAL:  database "kms_production" does not exist

First step before docker-compose up should be database creation and then running containers

Hi @GarPit , thanks for your feedback
I've re-tested this just to be sure, and if you follow the sample as written, it should work. I'm not sure where you got database "kms_production", as it is not a part of the sample. It might be possible that in making some changes, you changed other things.
That said, when I got your feedback, I walked through it again several times myself and found that there were some problems with my documentation. Some steps weren't clearly called out as necessary, sample output was misleading, etc. I've corrected the issues I've found.
Some things to be aware of, that may not have been clear in the previous version of the sample docs:

After you run docker-compose run web rails new . --force --database=postgresql, you then have to run docker-compose build. This rebuilds the Docker image based on the newly-created Gemfile.

Make sure that you modify the config/database.yml by replacing its contents with the given configuration as shown in the first part of the "Connect the database" step.

One more caveat. If you happen to be on Docker 1.17.06, some of the command output in your shell will render misaligned. It's a known issue in that release, and should be addressed soon. This should not affect actually building or running the sample.
Please re-try the sample, following the steps (maybe using the new version from the referenced PR #3517 ) and creating the content as written. Please let me know how it goes.
cc: @dnephin @shin-

Hi guys, I'm going to merge this since it LGTM and I want to get the fixes published. Feel free to comment / correct and I'll update as needed.

I'm launching my project in production mode. Maybe this is the case?


Add render target example

This example also demonstrates the use of geometry shaders, and manual creation of resources when there is no suitable method on Factory. Unfortunately, I am not familiar with HLSL, so I did not add shaders for it.
Fixes #1512

bors r+


Local function debug fails with timeout when calling appsync endpoint

Hi,
Context:
I'm working in a project which includes a react ui part with an api graphql, and another part in the same project with a lambda function. I want to reuse the api graphql to call the dynamodb using the same queries, etc. In order to use AWS AppSync in lambda functions, after try a lot of ways and appsync client libraries, I'm finally following this great tutorial at:
https://janhesters.com/how-to-use-aws-appsync-in-lambda-functions/
Problem:
I have configured my local VSC to debug locally my lambda function and it launch a command:
amplify function invoke myfunction
It runs ok, but when I hit my API using Postman, it reach a line in my code which calls the remote appsync endpoint:
data = await client.query({ query });
and hangs as follows:
Promise {  }
and after some minutes it fails with a TIMEOUT:
'request to https://xxxxxx.appsync-api.eu-central-1.amazonaws.com/graphql failed, reason: connect ETIMEDOUT <IP_ADDRESS>:443'
On the other hand, I'm using cntlm local proxy on localhost 3128, with Ubuntu 14.04, and behind a corporative proxy. I have no problems with amplify init, or any other tool, in fact all my local tools points to cntlm to avoid configurate the company proxy on each one.
I have my proxy variables well configured, and I added also them to the launch.json as follows just in case, but with the same result:
{   "version": "0.2.0",     "configurations": [       {         "type": "node",         "request": "launch",         "name": "Launch myfunction",         "program": "/usr/local/bin/amplify",         "args": [           "function",           "invoke",           "myfunction"         ],         "env": {           "ENV": "dev",           "REGION": "xxxx",           "AUTH_SOSAUTH_USERPOOLID": "xxxx",           "ANALYTICS_SOSANALYTICS_ID": "xxxx",           "ANALYTICS_SOSANALYTICS_REGION": "xxxx",           "API_SOSWEBCONSOLEAPI_GRAPHQLAPIIDOUTPUT": "xxxx",           "API_SOSWEBCONSOLEAPI_GRAPHQLAPIENDPOINTOUTPUT": "https://xxxxxx.appsync-api.eu-central-1.amazonaws.com/graphql",           "API_KEY": "",           "HTTP_PROXY": "http://localhost:3128",           "HTTPS_PROXY": "http://localhost:3128",           "http_proxy": "http://localhost:3128",           "https_proxy": "http://localhost:3128"         },         "console": "integratedTerminal"       }     ] }
More info:
amplify: 3.10.0
node: v10.16.0
npm: 6.9.0
So, I tryied a lot of things but I dont know why it does work,
Please help I getting crazy!

I bet you the reason it doesn't work is because the actual graphql endpoint you have configured by the time it runs
data = await client.query({ query });
is not a valid endpoint.
Due to lambda pulling in the graphql endpoint from environment variables, and automatically generating the names of the variables, it is quite easy to get the endpoint wrong because it changed the name of an environment variable.
Cheers.

mm I dont understand your point. The error say 'request to https://xxxxxx.appsync-api.eu-central-1.amazonaws.com/graphql failed, reason: connect ETIMEDOUT <IP_ADDRESS>:443'
that means the URL is ok, and if I try in a curl in the same VSC debug console, I get...
curl https://xxxxxx.appsync-api.eu-central-1.amazonaws.com/graphql
{
"errors" : [ {
"errorType" : "UnauthorizedException",
"message" : "Valid authorization header not provided."
} ]
}
It means there is connectivity from console to this endpoint, but not from amplify invoke command which hangs some minutes and then raise a TIMEOUT error...
Have you some trick to set the proxy settings on amplify?

True, well you'll probably need to make a public repo to demonstrate the issue and send me link, because I can attest it does work if configured properly.

More info about my investigation:

After review the stacktrace it seems that my function calls --> aws-appsync --> apollo-client --> isomorphic-fetch and on this point it fails. It seems like proxy is not taken in consideration.

I review similar problems and may be it requires to use ProxyAgent similar to: https://github.com/apollographql/apollo-tooling/issues/523

I found a similar problem with amplify-cli at https://github.com/aws-amplify/amplify-cli/issues/459

Full stacktrace:

/home/user/.nvm/versions/node/v10.16.0/bin/node --inspect-brk=44994 ../../../../../../../usr/local/bin/amplify function invoke sosApiFunction
[lrcc@lrcc-VirtualBox]:~/projects/aws/sos-project/src/sos (develop) $ /home/user/.nvm/versions/node/v10.16.0/bin/node --inspect-brk=44994 ../../../../../../../usr/local/bin/amplify function invoke sosApiFunction
Debugger listening on ws://<IP_ADDRESS>:44994/3f9f8fdf-2d88-4d61-9918-31ea83ac0f51
For help, see: https://nodejs.org/en/docs/inspector
Debugger attached.
Using service: Lambda, provided by: awscloudformation
? Provide the name of the script file that contains your handler function: index.js
? Provide the name of the handler function to invoke: handler
? Provide the relative path to the event: event.json
Testing function locally
EVENT: {"httpMethod":"POST","body":"{"name": "Amplify"}","path":"/securityStatus","resource":"/{proxy+}","queryStringParameters":{}}
App started
Success!  Message:
{"statusCode":200,"body":"{"success":"post securitystatus call succeed!","url":"/securityStatus","status":[{"statusCode":"OK"}]}","headers":{"x-powered-by":"Express","access-control-allow-origin":"*","access-control-allow-headers":"Origin, X-Requested-With, Content-Type, Accept","content-type":"application/json; charset=utf-8","content-length":"102","etag":"W/"66-i/N5I15byOX+ljlIp+yWRnOERS4"","date":"Sat, 28 Sep 2019 18:35:51 GMT","connection":"close"},"isBase64Encoded":false}
Missing x-apigateway-event or x-apigateway-context header(s)
Promise {  }
{ Error: Network error: request to https://xxxx.appsync-api.eu-central-1.amazonaws.com/graphql failed, reason: connect ETIMEDOUT <IP_ADDRESS>:443
at new ApolloError (/home/user/projects/aws/sos-project/src/sos/amplify/backend/function/sosApiFunction/src/node_modules/aws-appsync/node_modules/apollo-client/bundle.umd.js:85:32)
at /home/user/projects/aws/sos-project/src/sos/amplify/backend/function/sosApiFunction/src/node_modules/aws-appsync/node_modules/apollo-client/bundle.umd.js:1039:45
at /home/user/projects/aws/sos-project/src/sos/amplify/backend/function/sosApiFunction/src/node_modules/aws-appsync/node_modules/apollo-client/bundle.umd.js:1411:21
at Array.forEach ()
at /home/user/projects/aws/sos-project/src/sos/amplify/backend/function/sosApiFunction/src/node_modules/aws-appsync/node_modules/apollo-client/bundle.umd.js:1410:22
at Map.forEach ()
at QueryManager.broadcastQueries (/home/user/projects/aws/sos-project/src/sos/amplify/backend/function/sosApiFunction/src/node_modules/aws-appsync/node_modules/apollo-client/bundle.umd.js:1405:26)
at /home/user/projects/aws/sos-project/src/sos/amplify/backend/function/sosApiFunction/src/node_modules/aws-appsync/node_modules/apollo-client/bundle.umd.js:988:35
at process._tickCallback (internal/process/next_tick.js:68:7)
graphQLErrors: [],
networkError:
{ FetchError: request to https://xxxx.appsync-api.eu-central-1.amazonaws.com/graphql failed, reason: connect ETIMEDOUT <IP_ADDRESS>:443
at ClientRequest. (/home/user/projects/aws/sos-project/src/sos/amplify/backend/function/sosApiFunction/src/node_modules/isomorphic-fetch/node_modules/node-fetch/index.js:133:11)
at ClientRequest.emit (events.js:198:13)
at ClientRequest.EventEmitter.emit (domain.js:448:20)
at TLSSocket.socketErrorListener (_http_client.js:392:9)
at TLSSocket.emit (events.js:198:13)
at TLSSocket.EventEmitter.emit (domain.js:448:20)
at emitErrorNT (internal/streams/destroy.js:91:8)
at emitErrorAndCloseNT (internal/streams/destroy.js:59:3)
at process._tickCallback (internal/process/next_tick.js:63:19)
name: 'FetchError',
message:
'request to https://xxxx.appsync-api.eu-central-1.amazonaws.com/graphql failed, reason: connect ETIMEDOUT <IP_ADDRESS>:443',
type: 'system',
errno: 'ETIMEDOUT',
code: 'ETIMEDOUT' },
message:
'Network error: request to https://xxxx.appsync-api.eu-central-1.amazonaws.com/graphql failed, reason: connect ETIMEDOUT <IP_ADDRESS>:443',

Is it possible aws-appsync needs to include the proxy-agent in some way?

Thank you for your help!, I need to unblock this problem, any help or idea is welcome!

Hi again,
After modified /home/user/projects/aws/sos-project/src/sos/amplify/backend/function/sosApiFunction/src/node_modules/isomorphic-fetch/node_modules/node-fetch/index.js file to include:
At the begining of the file
// Add proxy support
import proxyAgent from 'http-proxy-agent';
and harcoding proxy for test (near line 120)...
...
// http.request only support string as host header, this hack make custom host header possible
if (options.headers.host) {
options.headers.host = options.headers.host[0];
}
// Add proxy support
options.agent = new proxyAgent('http://localhost:3128');
// send request
var req = send(options);
var reqTimeout;
...
then go to the isomorphic-fetch module main folder (in my case: /home/user/projects/aws/sos-project/src/sos/amplify/backend/function/sosApiFunction/src/node_modules/isomorphic-fetch) and run to install the dependency.
sudo npm i http-proxy-agent
After that,
It seems the calls go out and reached the endpoint !, it does not hangs (with timeout) on "promise call" anymore, it is called immediately through my local cntlm proxy.
Unfortunately, I'm facing other error reponsed by the cloudfront endpoint 400 bad request, maybe caused by permissions or something else that I have to review now.
But the important point here is that isomorphic-fetch apparently does not support run behind a local proxy !
Any idea about how to implement it in a more elegant way?
thank you,

Finally, I use the agent in my lambda to add the proxy programatically using the library const https = require('https'); and forgetting the example of apollo.
Then in the lambda code:
.....
const req = new AWS.HttpRequest(appsyncUrl, region);
req.method = "POST";
req.headers.host = endpoint;
req.headers["Content-Type"] = "application/json";
req.body = JSON.stringify({
query: graphqlQuery,
operationName: "[your grapthql operation e.g. ListTodos]"
});
// Add proxy support
const localProxy =  process.env.LOCAL_PROXY;
if(localProxy) {
var proxyAgent = require('proxy-agent');
var proxy = new proxyAgent(localProxy);
AWS.config.update({
httpOptions: { agent: proxy }
});
req.agent = proxy;
}
....
That's all.
BTW: I've followed the full example at https://aws-amplify.github.io/docs/cli-toolchain/quickstart#graphql-from-lambda, but adding the proxy as above to run it in my local, nad it works now.
We can close this ticket I think.
thank you


All files showing up as weird polygons only

Hi there, I wasn't able to find any answers to this online or in the previous questions, but perhaps I missed something.
TLDR: I've updated Java, I've tried multiple different files, but each and every one has a blank black field under the "print layer " tab and a weird geometric figure in the preview tab.

Has there been any fix to this issue? I am getting the same problem.

for validation and fix try UVTools by Sn4k3 instead
for 3D visualization use the 3D viewer from photonsters.org or just open
the sliced file on chitubox
No dia sábado, 8 de agosto de 2020, JYGomer<EMAIL_ADDRESS>escreveu:

Has there been any fix to this issue? I am getting the same problem.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/Photonsters/PhotonFileValidator/issues/81#issuecomment-670918842,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ACUR56X5GWEADQ3XCK5CU2LR7U2KVANCNFSM4O3DRKSA
.

--
Com os melhores cumprimentos,
Vinicius Silva

PHOTON FILE VIEWER IS NO LONGER MANTAINED OR DEVELOPED!
Use UVTools by Master Photonster Tiago Conceição instead


Move _variables.scss to child

Got to replace its instances with manual code, such as container width etc.

Simply moving it should be enough no?
As the variables are set as default overriding them in the child should be easy.


Add disable_required_check! and make disable the check in help

In Thor 0.19.2 it was added a new class method disable_class_options.
It was added to disable the check for required options in the help command. This new method disabled the option parser for help, so it is not possible to pass option to that command anymore.
That change introduced a regression and it is fixing the problem at the wrong level. What we want is to disable the required check not the option parsing.
So, we reverted the disable_class_options change and added a new method disable_required_check! to disable the required check in the commands we want.
Theoretically this is a breaking change but the disable_class_options introduction was also a breaking change so it is better to revert it and fix the problem at the correct place.
Related with #462 and #363.
See https://github.com/bundler/bundler/pull/5221

👍


Optionally have infinite water in ocean and river biomes

Hey this is a cool idea!

@SFort New version is live on curseforge


TagBot trigger issue

This issue is used to trigger TagBot; feel free to unsubscribe.
If you haven't already, you should update your TagBot.yml to include issue comment triggers.
Please see this post on Discourse for instructions and more details.
If you'd like for me to do this for you, comment TagBot fix on this issue.
I'll open a PR within a few hours, please be patient!

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/107928

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/108081

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/108845

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/109108

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/109136

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/109463

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/111941

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/116304


Clarify SSL plugin requirements

The SSL plugin is required only for Kong versions < 0.10.0.
Additionally, the specified configuration of the SSL plugin is required only when SSL is not being terminated downstream.

How will merging this into the master branch affect the merge of the release/0.10 branch?

oh shoot, I should have PR'ed this against release/0.10 branch? I could easily be doing it wrong.

I don't actually know? @thibaultcha might have some good input, just not sure if this will result in a merge conflict.

Just switched the base branch to release/0.10 instead.

(I will rebase this)

Taken care of by 8f8bb56 with the proper format we use for notes.


WIP: Fix 1805

Based on https://github.com/biocore/qiita/pull/2059, so merge that one first.
The idea is, as defined in the issue, to download all file paths from the BIOM artifacts that the user has access to via nginx zip.
ToDo:

[x] figure out how to test failures, place holders in place
[ ] test/tweak in the test-env until it actually works as expected

The new button is show here:

Coverage increased (+0.07%) to 91.611% when pulling 1626859cca8c196a63ee2ee0b5849358524161db on antgonza:fix-1805 into 4e380e04488c353a741c0766bf478778aa30ffbc on biocore:master.

Coverage increased (+0.08%) to 91.625% when pulling ade8cbe7844e47dcbee8f1123936b65f5d62f583 on antgonza:fix-1805 into 4e380e04488c353a741c0766bf478778aa30ffbc on biocore:master.

Coverage increased (+0.06%) to 91.64% when pulling 890d465779da653b9f332c3f15e993b4b7e6f07f on antgonza:fix-1805 into 27950465f44a5e945bf4001ddb40bde805789f8d on biocore:master.

Closing in favor of https://github.com/biocore/qiita/pull/2087


General: Move plugins register and discover

Brief description
Move plugins register and discover logic from avalon-core repository.
Description
Discovery and register of plugins was moved to openpype/pipeline/plugin_discover.py and is used at all places where register and discover plugins is used. Added register and discover function into create plugins.
Changes

implemented PluginDiscoverContext - it's object can be used to register and discover plugins

added object of PluginDiscoverContext for global access
discover method returns DiscoverResult which holds all discovered, crashed, ignored, duplicated and abstract plugins

added register/deregister and discover functions into create plugins
discover of legacy creators and loader will trigger set_plugin_attributes_from_settings

this was added to discover_loader_plugins and discover_legacy_creator_plugins

function classes_from_module does not check inheritance by class names

Testing notes:

pre/post launch hooks must work as did

affected by change of dynamic import functions

all plugins (create, load, inventory, launcher action, thumbnail) must be discovered properly

Related to PR https://github.com/pypeclub/avalon-core/pull/436

I feel we're once again increasing complexity where we don't need it. Making it much harder to maintain the code over time and have anyone go through the code and grasp what exactly is going o

Current avalon's approach is based on singleton access. It is NOT possible to have registered multiple paths for different contexts which would be now possible. It's not used that way yet but until it's possible it will never be.

To me personally it makes just as much sense if python_module_tools and plugins_discover would be in a single file in openpype/pipeline/plugins.py.

Content of python_module_tools is usabled (and used) at many different places. It is more like a python module adding some functionality that can be used elsewhere. Not just in discovery of pipeline plugins.
Also I've kept the plugins in function names to keep backwards compatibility but the register and discovery is not just for plugins but also for actions and thumbnail resolvers.

Additionally the new classes (e.g. GlobalDiscover acting as a singleton) provide no docstrings or documentation and feel less python than just storing the registered paths directly.

Will add a docstring. All it does is that it gives ability to use it the same way as was in avalon.

Also having discover not just return the plug-ins but a "DiscoverResult" just so we can print a report and list "duplicate" plug-ins feels like redundant complexity.

Because it's not used yet doesn't mean it will not be used. Many many times we wanted to show in UI some report that something went wrong and give artist ability to send it to us. That few steps away so current usage just print it out. I can modify the logic that it will not return the result object but plugins by default and will return the result only when requested.

I'm additionally worried that I might need to alter any scripts/tools I have in place that actually run discover().

We want to add ability to have a context wrapper around the actions and plugins and add them some initialization to add more abilities we're lacking right now. Again not used that way now but it must be prepared to be able do it that way so the PRs are reviewable.
One example is current applying of settings on loaders and creators. That's something what should be done during initialization and both of them should be usable to load/create multiple times using the same object but it is not possible right now.

Having things be "simple yet effective" is much better, no? We should only make things more complex if we absolutely need to. A pipeline is complex enough by itself.

It's getting more and more complicated to have it "simple". We're hacking a lot because it is done that way and we will never stop hack it until we make small steps heading to make it usable without hacks. It looks simple when you see just those functions but it is much more complicated when we're bending it to make it work as we need. Also there is so much we can't do because of that...
For example easily switch Qt UI for any other UI (detached from the host process).

It's not used that way yet but until it's possible it will never be.

I do feel that might be the wrong approach. We should implement the features that we need - not expose functionality that we might never be used. It's much more likely that 'errors' will go by unnoticed.
E.g. likely it won't work with the current implementation either since it still relies on having the global singleton everywhere? In essence that part doesn't behave much different than before?

Content of python_module_tools is usabled (and used) at many different places. It is more like a python module adding some functionality that can be used elsewhere. Not just in discovery of pipeline plugins.

Agreed that it's relatively generic - but I have the same approach as the above. We might want to only break out the things that we know will be used. Having it separated or exposing it as some sort of "API" or 'use it wherever you see fit' means we should be much less inclined to ever changing the logic/results of the functions in the future. Since we don't know what users/teams/studios might have been using it for elsewhere.
Currently it isn't actually used anywhere else. I'm fine with having it separated. It just makes it appear bigger than I felt it needs to be.

Because it's not used yet doesn't mean it will not be used. Many many times we wanted to show in UI some report that something went wrong and give artist ability to send it to us. That is few steps away so current usage just print it out. I can modify the logic that it will not return the result object but plugins by default and will return the result only when requested.

I'd much prefer actually to have that feature added - so we know it actually works the way we intend it to work. Additionally we should implement tests that the feature keeps working as we ever intended it to be.

In short, it'd help a lot if the decision making process about making these things more complicated is much clearer. Currently I can't accurately and actively feedback the code as to decide whether it does what it should which means I could only say "this errors".
Anyway, thanks for the thorough input.

I do feel that might be the wrong approach. We should implement the features that we need - not expose functionality that we might never be used. It's much more likely that 'errors' will go by unnoticed.

It is "a piece of logic" which contains some functions and attributes that do some logic. All I did is to put them in class so it is visible what are the logic boundries and what functions and attributes that logic has. Which might never be used as I described but it is at least visible what is affecting what.

I'd much prefer actually to have that feature added - so we know it actually works the way we intend it to work.

We just can't do everything in one run. We have limited time to do features. When we have one simple feature to do but the feature requires to rewrite the core function used everywhere it will never happen because it will take too much time and too much risk. Preparing it slowly is the only way I can see we could do it. At this moment we have ability to prepare it as much close to what we need as possible.

Currently it isn't actually used anywhere else. I'm fine with having it separated. It just makes it appear bigger than I felt it needs to be.

The functions were there before this PR. It is used in openpype modules, application and getting of openpype version.
One of refactor steps will be to remove all pipeline specific code from openpype/lib to openpype/pipeline. Main reason is that most of them are needed only for pipeline specific cases but not for application as it is. OpenPype is not just a pipeline anymore but an application that contain pipeline. When we need just handle application version or connection to server, we should not touch the pipeline part at all because it has high ability of application failure.

Currently I can't accurately and actively feedback the code as to decide whether it does what it should which means I could only say "this errors".

Currently the code does exactly the same like did in avalon. Only the core logic was wrapped into class and some hacks were removed from places where were not needed.

same problem in Blender 3.0
Traceback (most recent call last):
  File "E:\projects\openpype\3x\openpype\tools\loader\app.py", line 307, in _assetschanged
    self._thumbnail_widget.set_thumbnail(asset_ids)
  File "E:\projects\openpype\3x\openpype\tools\loader\widgets.py", line 870, in set_thumbnail
    thumbnail_bin = get_thumbnail_binary(
  File "E:\projects\openpype\3x\openpype\pipeline\thumbnail.py", line 17, in get_thumbnail_binary
    resolvers = discover_thumbnail_resolvers()
  File "E:\projects\openpype\3x\openpype\pipeline\thumbnail.py", line 134, in discover_thumbnail_resolvers
    return discover(ThumbnailResolver).plugins
AttributeError: 'list' object has no attribute 'plugins'

It is failing in Houdini 19.0.498:

Should be fixed now


Coremod ThaumcraftLoader: Unable to class load

I keep getting this coremod complaint when loading Thaumcraft with other mods, Agricraft and WTF Expedition seems to trigger it, something to do dynamically generated textures, but I have not been able to pin down why.
Here is the coremod error: https://pastebin.com/PeWwkFfK
The crash which is listed as the cause is a seemly random failure to generate an atlas texture.
When I see another crash I will provide it. The crash has been rather sporadic but becomes blocking (game won't load) once it occurs, changing mods being loaded eventually fixes it (then it will load with the same mods as was crashing before...).

This is caused by turning clothing off.
 # Enable Tech-Visor, Camo Pants, and other Clothing Items [default: true] B:ENABLED=false

The coremod class is currently not enabled which is why the error is occuring, but it should not be gamebreaking - MC just ignores it and goes on.
It will be the first error you see in the log, but should not be the cause of the issues. Could you see if anything else is listed in the log?

Yeah that makes sense since it doesn't seem to be directly related to whatever is causing the model & texture stitching issues.
Looking back in my logs, the only guess I have as to why this was happening was Surge and FoamFix having issues implementing and copying the model loader.
I don't see any crash reports that list thaumcraft as the first error- besides optifine- which doesn't count.
I'll close this, thanks for clearing up that the coremod error should not be a blocking issue!


Extension throws error if prettier v3 plugins array is used

Prettier Config:
module.exports = {
  printWidth: 80,
  semi: true,
  importOrderSeparation: true,
  importOrderSortSpecifiers: true,
  plugins: ["@trivago/prettier-plugin-sort-imports"],
};

Eslint Output:
[Error - 9:55:48 AM] An unexpected error occurred:
[Error - 9:55:48 AM] Error: Cannot find package '@trivago/prettier-plugin-sort-imports' imported from <redacted>/noop.js
    at new NodeError (file:///<redacted>/node_modules/prettier/index.mjs:18723:5)
    at packageResolve (file:///<redacted>/node_modules/prettier/index.mjs:19668:9)
    at moduleResolve (file:///<redacted>/node_modules/prettier/index.mjs:19700:20)

One of the solutions is to use require, i.e.
module.exports = {
  printWidth: 80,
  semi: true,
  importOrderSeparation: true,
  importOrderSortSpecifiers: true,
  plugins: [require("@trivago/prettier-plugin-sort-imports")],
};

But then this breaks prettier extension instead.
Eslint extension version: 2.4.2
Prettier extension version: 10.1.0
VSCode version: 1.83.1
Prettier version: 3.0.1
Eslint version: 8.46.0

Does the validation happen correctly when you use eslint in the terminal. If this is the case can you please provide me with a GitHub repository I can clone that demos what you are experiencing.

Yes, the validation happens correctly when eslint is used in the terminal.
I tried a few different workarounds and I was able to make the eslint extension error go away by using require.resolve in prettier's plugins array.
module.exports = {
  printWidth: 80,
  semi: true,
  importOrderSeparation: true,
  importOrderSortSpecifiers: true,
  plugins: [require.resolve("@trivago/prettier-plugin-sort-imports")],
};

However, I think the extension might need to be updated to be compatible with prettier v3's plugins array (if not already).

Yes, the validation happens correctly when eslint is used in the terminal.
I tried a few different workarounds and I was able to make the eslint extension error go away by using require.resolve in prettier's plugins array.
module.exports = {
  printWidth: 80,
  semi: true,
  importOrderSeparation: true,
  importOrderSortSpecifiers: true,
  plugins: [require.resolve("@trivago/prettier-plugin-sort-imports")],
};

However, I think the extension might need to be updated to be compatible with prettier v3's plugins array (if not already).

Thanks @sagargurtu for pointing me to the right direction!
I had to tweak my prettier.config.cjs as well, to get ESLint in VSCode back working:
/* eslint-env es6 */

/** @type {import("prettier").Config} */
const config = {
  // ...
  // plugins: ['prettier-plugin-tailwindcss'],
  plugins: [require.resolve('prettier-plugin-tailwindcss')],
};

module.exports = config;


Taipy inside watermark

Is it possible to remove 'Taipy inside' watermark in the dashboard?

@orangeluc Does this fix your issue ?

The ticket has been handled. Closed for lack of an answer.


[apps/genpkey] exit status should not be 0 on output errors

TL;DR
If the key is to be serialized or printed as text and the framework returns an error, the app should signal the failure to the user using a non-zero exit status.
History
From 1.1.1-stable (this snippet did not change in master, only shifted by a few lines):
https://github.com/openssl/openssl/blob/7bdf1ee8ccb69a743e29e3d1a72194c30e8583ae/apps/genpkey.c#L180-L199
The code above has been unchanged (apart from formatting) for the last 14 years.
In case of an error writing the key to a file or in textual form to the terminal, the exit status of the command is still reset to 0.
Branches
This should be fixed both in master and in 1.1.1

@mattcaswell this command has been "misbehaving" this way for a very long time and across releases.
Yet I don't think these 2 error paths have been triggered often, as excluding the current status of master with the serializer implementation still being finished, my guts say errors that could have resulted in either of these 2 steps failing would have been caught within a goto end block, before reaching this part of genpkey_main.
Anyway, one could argue that fixing this bug is changing an established behavior of genpkey:

do we require a discussion and vote to change this in 1.1.1?
do we require a discussion and vote to change this in master?

I would rather move ret = 0 to line 192 and replace your goto end with ret++

I would rather move ret = 0 to line 192 and replace your goto end with ret++

I like it! I actually fixed it like that first, but later changed to use goto just for conformity with our usual handling and to shorten the discussion!
Fixup pushed!

Travis failure is due to #12306 (the failure was already there, both in 1.1.1 and master, this PR just bring it to the surface!)

ret++  Why not ret = 1?

ret++ Why not ret = 1?

@richsalz either works for me, I guess both 1 and 2 are valid "failure" exit statuses, but I agree that it does not add much more information than is already reported on the screen to know which of the two is failing.

I only brought it up because there are very few instances where an exit code is meaningful.  (Verify, maybe?)

@paulidale Yes, the failures are due to #12306
I'll soon open PRs to fix it in both master and 1.1.1, and I will update this PR and the 1.1.1 one to rebase on top of those and to further test out these problematic curves!

@paulidale
Travis failures are expected: #12305, #12312 and #12307 depend on each other.
Check #12307 (based on top of the other 2) for (hopefully) green Travis.

24 hours has passed since 'approval: done' was set, but this PR has failing CI tests.  Once the tests pass it will get moved to 'approval: ready to merge' automatically, alternatively please review and set the label manually.

CI failures are expected, and fixed in #12307 / #12308  which have been approved.
They will be merged together

Merged to master as:

466d30c0d7fa861a5fcbaebd2e2010a8c2aea322 [apps/genpkey] exit status should not be 0 on output errors

Merged to 1.1.1 as:

1940c092a52afd8bc919b8faa5f3d51004503f3a [apps/genpkey] exit status should not be 0 on output errors

Thanks!


python 3 support

need support for python3

Due to Fabric's development roadmap there are no any plans on implementing Python 3 support for Fabric 1.x. This caused by incompatibility of Python 2.5 (which is still supported by Fabric 1.x) and Python 3.
So, the only Fabric version which will work with Python 3 is 2.x but it hasn't been released yet.

https://github.com/mathiasertl/fabric/

It's OK to use Fabric3. But I found bug with abort() method there. It isn't a blocker but user may suddenly face with it while getting an unreadable error.


HS_USERNAME assigned admin at startup

The HSDS app startup process sets the 'current user' to the admin user, where current user may be pulled from UserConfig, which is in turn populated from the environment. As such, having HS_USERNAME set in the environment (as recommended by h5pyd documentation) can result in a different admin user being assigned at HSDS startup, leading to hard to diagnose test failures.
This might be something to resolve with more consistent documentation about what env vars should be used to provide certain values.

The app.py hs_username and hs_password arguments were added to support a sort of single user mode.  I.e. without any password.txt file or active directory based authentication.  In the workflow script we use the password_file arg, so these aren't needed.
So maybe an easy fix would be to make a change to app.py so that if password_file is supplied, then hs_username, hs_password args are not passed to HsdsApp in the kwargs.

Resolved in #384 by granting password file precedence; this behavior has usefulness for use of HSDS on demand from h5pyd.


Rewrap bounds feature

This is an alternative and simpler solution for the rewrap bounds problem. Instead of adding an additional rewrap action I have just defined it so that if you wrap bounds it turns into rewrap/replace instead.
round wrap bounds air
fixes #270

It's a clever idea, but I have mixed feelings. I don't like that we lose expressiveness in case for whatever reason someone does want to wrap the bounds, especially as we're planning to generalise the notion of bounds. Also not super intuitive to me because "round wrap bounds" seems to pretty clearly indicate that we're going to wrap the bounds.
What's wrong with just having a "rewrap" command? I don't think it would be any more complex than what you've done here. Could just have the context object contain information about the boundary ranges and read that in the "rewrap" action. The context for surrounding pairs is constructed in one place so it should be quite straightforward

There is still an escape hatch if we actually want to wrap the bounds.  take bounds round wrap that
But I think that is so unlikely that you want to do that that I don't think it's a problem.
There's nothing wrong with it per se but I have two reasons for prefer this implementation

rewrap recognized really badly for me
Adding additional actions when we can make do with clever implementations of existing ones is not something I favor in general. I find it quite intuitive that if you wrap something that is already wrapped it will actually change it. Kinda like our format action which first removes existing format.

There is still an escape hatch if we actually want to wrap the bounds. take bounds round wrap this But I think that is so unlikely that you want to do that that I don't think it's a problem.
There's nothing wrong with it per se but I have 3 reasons for prefer this implementation

rewrap recognized really badly for me

Yeah that doesn't surprise me, but I don't think is a strike against the action itself.  We can find another name, eg  "change" or "switch"

Adding additional actions when we can make do with clever implementations of existing ones is not something I favor in general.

Not sure I agree with that philosophy.

That's not what this does, though, right?  And it is actually useful to be able to wrap something that is already wrapped.  I do that fairly commonly.  Something is in square brackets and I want to parenthesize it, etc

Kinda like our format action which first removes existing format.

The implementation was very easy since we already have the bounds as our selection.

I think that implementing "rewrap" will be even easier.  As suggested, just drop the info you need on the context object when we construct it, and read it from the "rewrap" action.  No need for the clever logic you have here

We have a current limitation where we can only have one modifier per command so we can't default to bounds when someone says round rewrap state. This could of course be fixed but the current implementation was the path of least resistance.

Not sure why you'd want to say "round rewrap state"?  Also, we can just add a simple modifier preference of surroundingPair: any, and then we could say things like "round rewrap air", and that would infer "round rewrap pair air", or "round rewrap square", which would override the default preference
If you don't feel strongly about the philosophical argument and would just prefer to have an action you can use today, I'd be happy to impl "rewrap" today or tomorrow.  If it turns out to be more complicated than I thought then let's revisit this approach?
If, on the other hand, you feel strongly about the philosophical argument, let's hop on a discord and hash this one out; I don't think it should be too difficult to find something we're both happy with here

I don't feel strongly about it if you do please go ahead with another implementation.

Alright, calling my bluff; I like it 😄.  Give me a day or two and I'll report back


Add TFSec and Terraform Docs to Terraform features

Hi here,
This is a PR to add 2 new feature sets to Terraform

TFSec
Terraform Docs

Have a nice day

@microsoft-github-policy-service agree

Thanks for adding these options! ✨
Left some comments.

Thks for the Review ;)


Rewrite this project using Tkinter or PyQt6.

Using Tkinter or PyQt6 is better for performance and efficiency. And it won't be depended on Microsoft Edge.

Don't close

Don't close

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.