Getting duplicate key error

Hello,
I have been saving models in a for loop which is causing a duplicate key error. Essentially I have an array of id's which I use to create and save new models in a for loop. The slug is to be the date and time with no spaces or dashes<PHONE_NUMBER>1200, the error is below along with how I define my slug. I think sluggable is not checking if a slug already exists properly.
protected $sluggable = ['build_from' => 'generate_slug'];

public function getGenerateSlugAttribute()
{
    return preg_replace('/[^0-9]/', '', $this->created_at ?? date('Y-m-d H:i:s'));
}

QueryException in Connection.php line 651:
SQLSTATE[23505]: Unique violation: 7 ERROR: duplicate key value violates unique constraint "competency_data_slug_unique"
DETAIL: Key (slug)=(20160229095303-2) already exists. (SQL: insert into "competency_data" ("form_data", "group", "slug", "updated_at", "created_at") values ({}, 1,<PHONE_NUMBER>5303-2, 2016-02-29 09:53:03, 2016-02-29 09:53:03) returning "id")

I am using version 3.1.4 of cviebrock/eloquent-sluggable.

Hello,
I've noticed that there are four possible results related to this issue. The results are random and inconsistent but always result in one of four of these:
I check four ids on my form, click submit and it either:

Works as expected.
Submits and redirects to index but has duplicate entries on some rows.
Produces error posted above in the first comment but worked as expected.
Produces error posted above in the first comment but has duplicate entries on some rows.

In my example I want to create more competencies that are related to a group, all competencies in a group must share the same information.
On all four of these scenarios I logged the form submission's ids and it is consistently correct as commented below, I also have logic to not add a row if it already exists which also works exactly as expected.
// CompetencyController@update
// $request->competencyids = [26, 27, 28, 29]
foreach ($request->competencyids as $competency_id) {
    if (! in_array($competency_id, $this->existingCompetencyIds($competency_data->group))) {
        $data = new CompetencyData;
        $data->form_data = $competency_data->form_data;
        $data->group     = $competency_data->group;
        $data->save();
    }
}

Sorry, this was something entirely unexpected, I've been stepping through trying to figure out this issue and haven't seen anything wrong with what eloquent or sluggable is doing, turns out my client side validator is sending ajax requests to the update method on my controller as I submit my form.
https://github.com/proengsoft/laravel-jsvalidation
This is strange because it's been configured not do ajax form validation.
I resolved this for now by adding if ($request->ajax()) return;. My recommendation for others who experience this when even two seperate users submit a form on the same second is to rethink your slug to be a little more user specific or simply not to slug in this situation.


Godot 4.3 doesn't recognize de plugin

I try to install in the assets store, but when i open project settings, the plugin isn't there

@ChairmanChairXD ok Ill check. Untill now I only rested/used Godot 4.2

@ChairmanChairXD I tried with Godot 4.2 and 4.3, the gdcef folder is downloaded correctly inside the folder addons. I did not get the point with your "project settings" I'm a Godot noob. You have to call the addons/gdcef/build.py to compile (and maybe edit it to set Godot 4.3) and obtain the build folder cef_artifacts. Else you can try prebuild artifcats https://github.com/Lecrapouille/gdcef/releases

@ChairmanChairXD ah ok I understand, after seeing a plugin having it. I missed the cfg and a dummy gd file. I can add them but I'm not sure this is really a need for this plugin maybe fixing https://github.com/Lecrapouille/gdcef/issues/41

@ChairmanChairXD Available in release https://github.com/Lecrapouille/gdcef/releases/tag/v0.11.0-godot4


[bug] fix for python2,7, 3.3, 3.4, 3.5 support

Thank you for wonderful repository.
Current 3.9.0 drops python2.7, 3.3, 3.4, 3.5 support, and it is caused by #434 .
f" " (f-strings) syntax is from python3.6.
https://peps.python.org/pep-0498/
As written in setup.cfg and setup.py,  this project is released for  python2.7, 3.3, 3.4, 3.5.
so I made this PR to support  python2.7, 3.3, 3.4, 3.5.
https://github.com/Uberi/speech_recognition/blob/3f4162faed237845d4dcb0cc01130fd33e715da4/setup.cfg#L4
https://github.com/Uberi/speech_recognition/blob/3f4162faed237845d4dcb0cc01130fd33e715da4/setup.py#L66-L70

Thanks for your pull request.
i do not agree support python2.7, 3.3, 3.4, 3.5, 3.6.
I think we should support Active Python Releases on https://www.python.org/downloads/ (that is, python 3.7 or later).
Pull requests to drop inactive Python are welcome.

@ftnext if so please correct the setup.py and stop releasing the bugged version to python2.7 and 3.5 in pypi


Update README.md with v0.9.0

What type of PR is this?
Subproject Management
What this PR does / why we need it:
Update of README.md to reflect release v0.9.0 as latest.
Which issue(s) this PR fixes:

Fixes #191
Special notes for reviewers:
Are you aware of other places which we should update?
Changelog input
na
Additional documentation

@RandyLevensalor @jlurien @patrice-conil @eric-murray Can one of you have a short view if the change is fine for you?


Print a log message if GetPage response takes too long

We have metrics for GetPage request latencies, but this is an extra measure to capture requests that take way too long in the logs. The log message is printed every 10 s, until the response is received:
PG:2024-12-06 21:33:14.713 GMT [1507715] LOG:  [NEON_SMGR] [shard 0] no response received from pageserver for 10.000 s, still waiting
PG:2024-12-06 21:33:24.721 GMT [1507715] LOG:  [NEON_SMGR] [shard 0] no response received from pageserver for 20.009 s, still waiting
PG:2024-12-06 21:33:29.719 GMT [1507715] LOG:  [NEON_SMGR] [shard 0] received response from pageserver after 25.006 s

We also talked about disconnecting and retrying with a new connection, if a request takes too long. I didn't dare to do that yet, but just logging long requests is useful already.
I set the threshold at 10 s, but I'm open to opinions on that. (A cop out answer would be to make it configurable, but I think that'd be overkill, and would still leave us with the question of what to actually set it to)


menus.py fails

Following the documentation (http://docs.django-cms.org/en/latest/extending_cms/app_integration.html#apphook-menus)
I created a menus.py file in my app, yet I experienced the following awkward behavior:
Traceback (most recent call last):
  File "/usr/lib/python2.7/wsgiref/handlers.py", line 85, in run
    self.result = application(self.environ, self.start_response)
  File "/home/vagrant/.virtualenvs/zita/local/lib/python2.7/site-packages/django/contrib/staticfiles/handlers.py", line 67, in __call__
    return self.application(environ, start_response)
  File "/home/vagrant/.virtualenvs/zita/local/lib/python2.7/site-packages/django/core/handlers/wsgi.py", line 187, in __call__
    self.load_middleware()
  File "/home/vagrant/.virtualenvs/zita/local/lib/python2.7/site-packages/django/core/handlers/base.py", line 47, in load_middleware
    mw_instance = mw_class()
  File "/home/vagrant/.virtualenvs/zita/local/lib/python2.7/site-packages/django/middleware/locale.py", line 24, in __init__
    for url_pattern in get_resolver(None).url_patterns:
  File "/home/vagrant/.virtualenvs/zita/local/lib/python2.7/site-packages/django/core/urlresolvers.py", line 365, in url_patterns
    patterns = getattr(self.urlconf_module, "urlpatterns", self.urlconf_module)
  File "/home/vagrant/.virtualenvs/zita/local/lib/python2.7/site-packages/django/core/urlresolvers.py", line 360, in urlconf_module
    self._urlconf_module = import_module(self.urlconf_name)
  File "/home/vagrant/.virtualenvs/zita/local/lib/python2.7/site-packages/django/utils/importlib.py", line 40, in import_module
    __import__(name)
  File "/python-projects/zita/zita/zita/urls.py", line 14, in <module>
    url(r'^', include('cms.urls')),
  File "/home/vagrant/.virtualenvs/zita/local/lib/python2.7/site-packages/django/conf/urls/__init__.py", line 26, in include
    urlconf_module = import_module(urlconf_module)
  File "/home/vagrant/.virtualenvs/zita/local/lib/python2.7/site-packages/django/utils/importlib.py", line 40, in import_module
    __import__(name)
  File "/home/vagrant/.virtualenvs/zita/local/lib/python2.7/site-packages/cms/urls.py", line 18, in <module>
    if apphook_pool.get_apphooks():
  File "/home/vagrant/.virtualenvs/zita/local/lib/python2.7/site-packages/cms/apphook_pool.py", line 63, in get_apphooks
    self.discover_apps()
  File "/home/vagrant/.virtualenvs/zita/local/lib/python2.7/site-packages/cms/apphook_pool.py", line 55, in discover_apps
    load('cms_app')
  File "/home/vagrant/.virtualenvs/zita/local/lib/python2.7/site-packages/cms/utils/django_load.py", line 56, in load
    get_module(app, modname, verbose, failfast)
  File "/home/vagrant/.virtualenvs/zita/local/lib/python2.7/site-packages/cms/utils/django_load.py", line 40, in get_module
    module = import_module(module_name)
  File "/home/vagrant/.virtualenvs/zita/local/lib/python2.7/site-packages/django/utils/importlib.py", line 40, in import_module
    __import__(name)
  File "/python-projects/zita/zita/products/cms_app.py", line 4, in <module>
    from products.menus import ProductCategoryMenu
  File "/python-projects/zita/zita/products/menus.py", line 1, in <module>
    from menus.base import NavigationNode
ImportError: No module named base

My menus.py:
from menus.base import NavigationNode
from menus.menu_pool import menu_pool
from django.utils.translation import ugettext_lazy as _
from cms.menu_bases import CMSAttachMenu
from products.models import ProductCategory

class ProductCategoryMenu(CMSAttachMenu):

    name = _("test menu")

    def get_nodes(self, request):
        nodes = []
        for category in ProductCategory.objects.all().order_by("tree_id", "lft"):
            node = NavigationNode(
                category.name,
                category.get_absolute_url(),
                category.pk,
                category.parent_id
            )
            nodes.append(node)
        return nodes

menu_pool.register_menu(ProductCategoryMenu)

My cms_app.py:
from cms.app_base import CMSApp
from cms.apphook_pool import apphook_pool
from django.utils.translation import ugettext_lazy as _
from products.menus import ProductCategoryMenu

class ProductsAppHook(CMSApp):
    name = _("Products")
    urls = ["products.urls"]
    menus = [ProductCategoryMenu]

apphook_pool.register(ProductsAppHook)

Changing the name of the file from menus.py to something like cms_menus.py removes the above exception.
versions:
django-cms==3.0.3
Django==1.6.5

closed in favour of https://github.com/divio/django-cms/issues/4597, feel free to continue the conversation here

Menus will be moved into cms app as per #5112


Underscores mess up code highlighting

Thanks for providing this package, I mainly use it to highlight my Rmarkdown code properly.
Unfortunately, it seems that the extension does not handle underscores well when they are in unquoted variable names in my Rmarkdown file (see image below).

When I have the extension enabled this is also an issue for any other scripts. For example, my python scripts then start looking like this whenever there is an underscore, which can become quite distracting.

My Python scripts also had broken syntax highlighting on underscores after installing. However, upon uninstalling and reinstalling, I was unable to reproduce the issue.

This also affects syntax highlighting in ordinary Python files, where no RMarkdown is involved.


Proposal: add or, or_else, and, and_then to std Iterator trait

Hello,
Recently I experienced fun issue and thought it would be good to be in Iterator.
Iterator trait would be good to have methods for checking whether iterator instance is empty or not, before it is evaluated.
Of course, I can figure out the iterator is whether empty using next() method.
But the problem is after I call next() like method, it evaluates iterator.
What I just want to do is just adding some code logic to Iterator, without evaluating.
Fortunately, it is possible to do using existing methods, though it looks little bit verbose.
This code example below shows implementing or,
let iter_a: Iterator<_> = ... ;
let iter_b: Iterator<_> = ... ;

// (1)
iter_a
    .map(|item| (false, item))
    .chain((true, item))
    .enumerate()
    .filter_map(|(i, (is_last, item))| {
        match !is_last || i == 0 {
            true => Some(item),
            false => None,
        }
    })

// can be replaced with
// (2)
iter_a.or(iter_b)

What I wrote was (1) which is combination of map-chain-enumerate-filter_map, but it can be replaced simply with or.
Let's assume both A and B implemented Iterator trait.

A.or(B)
Return A if A is not empty, else if A is empty then return B.
Iterator B will be evaluated only if (A is evaluated and then A is empty) case.

Basically I got interested at first was only or.
But if I add those feature, maybe it's natural to add other related methods:

and, and_then and or_else (like Option and Result enums have.)

How do you think of these?

Oh, sorry it was the first time I wrote this kind of thing,
I read When you need to follow this process section but I noticed that I also had to read Before creating an RFC.
I'll talk about this first in the community and then will come back or not.
https://internals.rust-lang.org/t/pre-rfc-add-or-or-else-and-and-then-to-std-iterator-trait/12197
Maybe... it's better to close this issue for now?

it would be good to be in Iterator.

My opinion is that basically any addition to Iterator should go to itertools. There it can mature. If it truly becomes used enough, then it can potentially be moved to the standard library.

checking whether iterator instance is empty or not, before it is evaluated

This sounds like a trait that would be orthogonal to Iterator:
trait IsEmpty {
    fn is_empty(&self) -> bool;
}

and then you could restrict your functions to IntoIterator + HasMore.

@shepmaster I really should not be rushed to write this, thanks so much for fast and kind reply.
And I also even found that this code example I wrote was quite.. wrong.
I fixed that code in the link below, and got help:
https://internals.rust-lang.org/t/question-resolved-add-or-or-else-and-and-then-to-std-iterator-trait/12197
Oh, now I understand the meaning of "orthogonal" you said.
That's such a good explanation for this issue, I got what was I wanted to have.
Again, thanks a lot for the comment. I will close this issue.


WIP: cleanup (again)

[x] Introduce more general checks for sequence, join, and repeatFlat
[x] Introduce MappableProperties
[x] Use "can be combined checks" more
[x] Organize helpers better into sections
[x] Introduce helpers to create type subset properties

to discuss

I'd like to rename "andThen" checks to "mapFlat" which is in my mind easier to understand as concatMap and has a nice conststency with e.g. "repeatFlat" which is effectively repeat >> andThen identity.

You have some conflicts because of my restoration of old PR (sorry :see_no_evil:). Let me know if you want some help with that.

I'd like to rename "andThen" checks to "mapFlat"

Go ahead. These names are all quite abstract at this point anyway (but not Haskell-like abstract).


Routable tabs component

This is a work in progress, but I'd like feedback before I invest time in adding some tests.
Prerequisite: #33 - Update to ember-cli 0.2.2

{{#materialize-tabs tabWidth=2}}
  {{#materialize-tabs-tab dest="tabs.index"}}First{{/materialize-tabs-tab}}
  {{#materialize-tabs-tab dest="tabs.second"}}Second{{/materialize-tabs-tab}}
  {{#materialize-tabs-tab dest="tabs.third"}}Third{{/materialize-tabs-tab}}
{{/materialize-tabs}}

I have opted to implement the animation using velocity, in an effort to make this as idiomatic as possible, and have left the $.material_tabs() script unused.

It looks really good.
Is tabWidth the number of tabs?
Why you set tabWidth to 2 with 3 tabs?

@sgasser just a design choice to have smaller left-aligned tabs rather than larger justified tabs. If you have a preference I'm happy to change it

@sgasser you might want to disable Codacy. It doesn't like a lot of ES6 stuff like template strings

TODO:

[ ] Non-block component needs to be able to work

{{materialize-tabs tabs=myTabs}}

And also
{{#materialize-tabs}}
  {{materialize-tabs-tab materialize-tabs-tab dest="list.items"}}
{{/materialize-tabs}}

Removed codacy

Ready to merge?

@sgasser will definitely add more tests to this soon. I'm using it in one of my apps in order to ensure the API surface makes sense

@sgasser @rynam0 this has good test coverage now, and is ready for review

Looks good.
Why in package.json are you using the full git url for liquid-fire with master branch and not the latest stable version?

@sgasser latest version doesn't support 1.11 afaik. Good catch on the branch reference though -- We should at least use a SHA so we don't take in any new code unknowingly

All conflicts resolved, all tests passing

Looks great to me.  Can't wait to test-drive it.


Added open issue section in our contributor page

Title and Issue number

**Title: #336
**Issue No.: show open issue and what they contribute
Close #336
https://github.com/user-attachments/assets/bec1baaf-111d-4d1b-8ca0-1d606b7962df
ADDED OPEN issue section where user can see all the open issue
and can directly contribute from there itself by clicking on that page
it is beneficial for both admin and developer to look upon the issues
added pagination for betterment of UI
clean and clear view of isssue !!
Checklist:

[X ] I have mentioned the issue number in my Pull Request.
[ X] I have commented my code, particularly in hard-to-understand areas.
[ X] I have created a helpful and easy-to-understand README.md if it's a new page/tech stack.
[ X] I have gone through the contributing.md file before contributing.

Additional context (Mandatory):
Are you contributing under any Open-source programme?

[ X] I'm a GSSOC-EXT contributor
[ X] I'm a HACKTOBERFEST contributor

@GUNJESH843 , @Anuj3553 , why this PR doesn't get merge it there any issue with this ?
i can resolve it please reply !!

@GUNJESH843 is there no label on this PR... Just asking??

@GUNJESH843 @Anuj3553 is there no label on this PR why... Just asking??

Solved problem or not @Sawan-Kushwah. Just asking to help you.

@Anuj3553 yes solved thanks for the help ☺


Add Magnanimous to projects.

I am the author of Magnanimous, a static website generator!
The project website is hosted on GitHub Pages and is, of course, generated via Magnanimous itself. The source is on GitHub.
My own website, Renato Athaydes is also generated by Magnanimous (and hosted by you guys at Netlify! Thanks!).
It would be awesome if you added my project to your list!

Looks great, thanks for adding!


Name nucleobases, not nucleosides

Closes #9

@mienaikage I've updated the body of the PR to include the magic comment "Closes NNN" where NNN is the number of the pull request. Check out this blog post for more info: https://github.com/blog/1506-closing-issues-via-pull-requests


Release 0.1.0, What can we improve?

Please reflect on our journey to 0.1.0 and leave your comments here on areas you feel we can improve.
Please add ideas on how we can improve these areas in your comment.
Thanks

We didn't do a very good job at tagging our projects.

We were fairly informal regarding the freeze. Was it a code freeze (no)? Was it a feature freeze (sort of)? What were the goals of the freeze? Did we achieve them? Do we have a plan for future freezes?

Slightly related to the tagging and code freezes, I think there was a lack of clarity and communication of what versions of different components got into the release and when they were tested. e.g. We cut the final payload on Tuesday, so any PRs made to components after this weren't included and we pulled in certain commits of components (e.g. image-rs) so some of them hadn't been updated in a few weeks.
We also waited until the operator CI was finished before merging in the RC1 payload, at 12:51 UTC on Wednesday, so any testing run before then was on something we didn't release.

The current process to create the payloadImage is pretty reliable, but manual to kick-off, so susceptible to human error (e.g. not updating the branch you are building on correctly)

We didn't manage to including the signature verification features in the sample payload and the payload was just created from one of my branches, so not tracked, or repeatable. For the next release, if we are still producing a sample payload, we should have some automated/scriptable process to add the required artefacts to the kata image.

Other agent configuration is a bit of a mess at the moment.  Some things are only customisable in the agent-config.toml (the endpoints allowed and aa_kbc_params). These have to be ‘baked’ into the image which makes it difficult for users to interact with. The agent config also overrides all the other kernel_params settings, so we should consider adding the ability to pass through these settings via kernel_params, and/or update the prioritisation so that the kernel_params override the baked in agent-config.toml. We also have a ‘default/sample’ agent-config template duplicated in a few places, so we should try and unify them if possible.

Probably bigger than the scope of a single release, but having a proper CD process (we’ll need some CNCF resource first, so starting to try and get that might help) would help with us keeping quality high and being able to minimise code freezes.
I think the utopian goal here is that when dev updates something in ocicrypt-rs/image-rs/attestation-agent/kata-containers we are able to run the E2E operator based tests with that change included. I’d expect this to take much longer than a single release cycle, but the sooner we start, the sooner we finish!
If we had this system then I think the release process would be simplified a lot - on release date we'd just take the last passing 'integration' build and ship that (we'd need to ensure that the release notes matched it still I guess).

Add some CI automated tests for all the features we doc and therefore 'support' e.g. secure ephemeral storage

The current process to create the payloadImage is pretty reliable, but manual to kick-off, so susceptible to human error (e.g. not updating the branch you are building on correctly)

https://github.com/kata-containers/kata-containers/issues/5330

Probably bigger than the scope of a single release, but having a proper CD process (we’ll need some CNCF resource first, so starting to try and get that might help) would help with us keeping quality high and being able to minimise code freezes. I think the utopian goal here is that when dev updates something in ocicrypt-rs/image-rs/attestation-agent/kata-containers we are able to run the E2E operator based tests with that change included. I’d expect this to take much longer than a single release cycle, but the sooner we start, the sooner we finish! If we had this system then I think the release process would be simplified a lot - on release date we'd just take the last passing 'integration' build and ship that (we'd need to ensure that the release notes matched it still I guess).

https://github.com/confidential-containers/community/issues/62

We were fairly informal regarding the freeze. Was it a code freeze (no)? Was it a feature freeze (sort of)? What were the goals of the freeze? Did we achieve them? Do we have a plan for future freezes?

As far as I understand we had requests of "new things" coming in till the last week, such as the sample payload image (please, don't take me wrong, I'm NOT blaming the ones who requested that, I'm just using this as an example).
In the future we should consider having a week or so for stabilisation and be strict that no new requests will come in.  By the moment we have a new thing popping up, it means that all the validation and testing done so far is basically thrown away.

There's the sincere need of more people involved with the projects we rely on. At the end of the day the reviews on Kata Containers were mostly on the back of a very small group of folks, who were also working on huge set of different tasks.
We need people to get more involved with Kata Containers as we're relying on the project, and with enough contributions become an official reviewer / member of the project, then we can start spreading the load.

I'd like to emphasize those points as being critical for the CoCo project long term.
On this first release I very few people were reviewing the changes on Kata Containers, and a portion of those doing so weren't accounted on merge policy (2 or more people members of Kata Containers on github).
Not just for reviews, we need more developers in general to help on developing features/build/release/CI tasks.

There's the sincere need of more people involved with the projects we rely on. At the end of the day the reviews on Kata Containers were mostly on the back of a very small group of folks, who were also working on huge set of different tasks.
We need people to get more involved with Kata Containers as we're relying on the project, and with enough contributions become an official reviewer / member of the project, then we can start spreading the load.

I'd like to emphasize those points as being critical for the CoCo project long term.
On this first release I very few people were reviewing the changes on Kata Containers, and a portion of those doing so weren't accounted on merge policy (2 or more people members of Kata Containers on github).
Not just for reviews, we need more developers in general to help on developing features/build/release/CI tasks.

I concur. That actually emphasizes the need to work harder on upstreaming. The tighter we'll be to Kata, the higher the incentive, imho.

Add some CI automated tests for all the features we doc and therefore 'support' e.g. secure ephemeral storage

I was going to ask about how to have an automated test for secure storage in https://github.com/kata-containers/kata-containers/pull/5314 :)
Still regarding tests:

Asses the current tests in Kata Containers, their coverage and the gaps. Of course implement more tests afterwards.
Perhaps have a policy like: new features don't get merged without e2e automated tests running on CI. Unless otherwise there is a good technical justification to not do so
Use of current tests on CI operator is a hack. We need to figure out a better way to share tests between Kata and the Operator CI

Scope creep a little but understandable as everyone wanted to see their efforts in the first release.
Hopefully we can get into a good cadence with frequent releases, so features get added to the next release after they are ready, rather than rushing the into a release.

@magowan recommend we close this issue.


Chunkify regex_search

Resolves #11
Happy to consider alternatives here!
I ran this and the unmodified version and both took about the same amount of time to process a solution file with 5000 lines @ ~100kB each.

I was not aware of the issue. That's indeed a great improvement - thanks!


feat(publisher-github): add debug support for Octokit

[x] I have read the contribution documentation for this project.
[x] I agree to follow the code of conduct that this project follows, as appropriate.
[x] The changes have sufficient test coverage (if applicable).
[x] The testsuite passes successfully on my local machine (if applicable).

Summarize your changes:
Hooks the debug module into Octokit's logging mechanism. You can enable info messages by adding electron-forge:publisher:github:info to the DEBUG environment variable, and debug messages by adding electron-forge:publisher:github:debug to the DEBUG environment variable. Please note that both will be enabled if you already have electron-forge:* in the DEBUG environment variable.
Also does some cleanup while working on the module (namely, using the userAgent option instead of setting a header).
Addresses #2498.
Fixes #1672.
Closes #1673.

There appears to be an unrelated problem with CI in general, with the native modules support. Can't really merge with that there (since it'll affect the main branch anyway).

There appears to be an unrelated problem with CI in general, with the native modules support. Can't really merge with that there (since it'll affect the main branch anyway).

I guess it was a weird transient error? Although I did repro this locally the other day, so this is very confusing.


Multi Tenant - cannot chat with one of my coworkers anymore...

...because I don't am a member of the chat. ???

I can chat with anybody else, but this guy.

I also don't see any phone or video buttons on the right upper area

Desktop app. Restarted it already twice

Hello, I cannot determine whether you are trying to chat in-tenant or whether you are cross tenant (either federated or using a Guest identity). Can you please confirm? Thanks

It was in-tenant.
Francois Doremieux (Microsoft<EMAIL_ADDRESS>schrieb am Mo.,
12. Aug. 2019, 15:31:

Hello, I cannot determine whether you are trying to chat in-tenant or
whether you are cross tenant (either federated or using a Guest identity).
Can you please confirm? Thanks
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/MicrosoftDocs/msteams-docs/issues/876?email_source=notifications&email_token=AGMSZMTCFWQDZYPJD2LMJBDQEFQ33A5CNFSM4IKTDOFKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD4CRC4Q#issuecomment-520425842,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AGMSZMVBHU5ZFJG6L5IC2H3QEFQ33ANCNFSM4IKTDOFA
.

Please re-open if you are still facing the issue.


Generating CSS only if neccessary

Hello,
I want to ask a question — is there any way to prevent spritesmith generate CSS file?
If no, do you think there is any possible profit in speed of generating CSS in such case?
Thanks.

Generating CSS is far from the limiting factor in this utility. Image manipulation is much more costly. Can you elaborate on when you would need the spritesheet without corresponding CSS?


Support TLS when using the Mysql driver

Summary
Extended xk6-sql to support mysql connection over TLS.
Details
The mysql driver already supports TLS. These are additions to make xk6-sql TLS aware; such that, the TLS settings can be passed to the underlying drivers.

[!NOTE]

No changes are required for the existing scripts. The open interface is retained as-is.
TLS is registered only if enableTLS: true is passed to loadTLS

Testing Done
./k6 run examples/mysql_secure_test.js -v
DEBU[0000] Logger format: TEXT
DEBU[0000] k6 version: v0.51.0 (commit/a3010c8ad2-dirty, go1.22.6, darwin/arm64)

          /\      |‾‾| /‾‾/   /‾‾/
     /\  /  \     |  |/  /   /  /
    /  \/    \    |     (   /   ‾‾\
   /          \   |  |\  \ |  (‾)  |
  / __________ \  |__| \__\ \_____/ .io

DEBU[0000] Resolving and reading test 'examples/mysql_secure_test.js'...
DEBU[0000] Loading...                                    moduleSpecifier="file:///<redacted>/xk6-sql/examples/mysql_secure_test.js" originalModuleSpecifier=examples/mysql_secure_test.js
DEBU[0000] 'examples/mysql_secure_test.js' resolved to 'file:///<redacted>/code/xk6-sql/examples/mysql_secure_test.js' and successfully loaded 1141 bytes!
DEBU[0000] Gathering k6 runtime options...
DEBU[0000] Initializing k6 runner for 'examples/mysql_secure_test.js' (file:///<redacted>/code/xk6-sql/examples/mysql_secure_test.js)...
DEBU[0000] Detecting test type for...                    test_path="file:///<redacted>/code/xk6-sql/examples/mysql_secure_test.js"
DEBU[0000] Trying to load as a JS test...                test_path="file:///<redacted>/code/xk6-sql/examples/mysql_secure_test.js"
DEBU[0000] Babel: Transformed                            t=40.119292ms
DEBU[0000] Runner successfully initialized!
DEBU[0000] Parsing CLI flags...
DEBU[0000] Consolidating config layers...
DEBU[0000] Parsing thresholds and validating config...
DEBU[0000] Initializing the execution scheduler...
DEBU[0000] Starting 2 outputs...                         component=output-manager
DEBU[0000] Starting...                                   component=metrics-engine-ingester
DEBU[0000] Started!                                      component=metrics-engine-ingester
     execution: local
        script: examples/mysql_secure_test.js
        output: -

     scenarios: (100.00%) 1 scenario, 1 max VUs, 10m30s max duration (incl. graceful stop):
              * default: 1 iterations for each of 1 VUs (maxDuration: 10m0s, gracefulStop: 30s)

DEBU[0000] Trapping interrupt signals so k6 can handle them gracefully...
DEBU[0000] Starting emission of VUs and VUsMax metrics...
DEBU[0000] Start of initialization                       executorsCount=1 neededVUs=1 phase=execution-scheduler-init
DEBU[0000] Starting the REST API server on localhost:6565
DEBU[0000] Initialized VU #1                             phase=execution-scheduler-init
DEBU[0000] Finished initializing needed VUs, start initializing executors...  phase=execution-scheduler-init
DEBU[0000] Initialized executor default                  phase=execution-scheduler-init
DEBU[0000] Initialization completed                      phase=execution-scheduler-init
DEBU[0000] Start of test run                             executorsCount=1 phase=execution-scheduler-run
DEBU[0000] Running setup()...

DEBU[0000] Test finished cleanly
DEBU[0000] Stopping vus and vux_max metrics emission...  phase=execution-scheduler-init
DEBU[0000] Metrics emission of VUs and VUsMax metrics stopped
DEBU[0000] Releasing signal trap...
DEBU[0000] Sending usage report...
DEBU[0000] Waiting for metrics and traces processing to finish...
DEBU[0000] Metrics and traces processing finished!
DEBU[0000] Stopping outputs...
DEBU[0000] Stopping 2 outputs...                         component=output-manager
DEBU[0000] Stopping...                                   component=metrics-engine-ingester
DEBU[0000] Stopped!                                      component=metrics-engine-ingester
DEBU[0000] Generating the end-of-test summary...

     data_received........: 0 B 0 B/s
     data_sent............: 0 B 0 B/s
     iteration_duration...: avg=9.11ms min=6.87µs med=13.57ms max=13.75ms p(90)=13.72ms p(95)=13.74ms
     iterations...........: 1   26.986911/s

running (00m00.0s), 0/1 VUs, 1 complete and 0 interrupted iterations
default ✓ [======================================] 1 VUs  00m00.0s/10m0s  1/1 iters, 1 per VU
DEBU[0000] Usage report sent successfully
DEBU[0000] Everything has finished, exiting k6 normally!

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.surajvshankar seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.

@szkiba : We are attempting to add TLS support to the mysql driver used by this plugin. Could you please review and provide your feedback?

@szkiba : We are attempting to add TLS support to the mysql driver used by this plugin. Could you please review and provide your feedback?

@surajvshankar
Of course. Could you fix the linter problem first?

@surajvshankar  still has linter issues
https://github.com/grafana/xk6-sql/actions/runs/10721473919/job/29735069904?pr=71

@surajvshankar still has linter issues https://github.com/grafana/xk6-sql/actions/runs/10721473919/job/29735069904?pr=71

Thank you @szkiba. I have fixed the double import.
I have ensured that on manually running the linter at my end, it now succeeds:
golangci-lint run
WARN [config_reader] The configuration option `linters.govet.check-shadowing` is deprecated. Please enable `shadow` instead, if you are not using `enable-all`.
WARN The linter 'exportloopref' is deprecated (since v1.60.2) due to: Since Go1.22 (loopvar) this linter is no longer relevant. Replaced by copyloopvar.

Ivan, we are pulling the "latest" version/tag of xk6-sql. Thank you for
creating the release: https://github.com/grafana/xk6-sql/releases/tag/v0.4.1.
Could you also update the "latest" tag to point to this release, please?
Regards,
suraj.
On Fri, Sep 6, 2024 at 6:13 AM Iván Szkiba @.***> wrote:

Merged #71 https://github.com/grafana/xk6-sql/pull/71 into master.
—
Reply to this email directly, view it on GitHub
https://github.com/grafana/xk6-sql/pull/71#event-14161904561, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AIIUIKQ7DQ54M5ZSQNR7ESDZVGTAFAVCNFSM6AAAAABNFHKZK2VHI2DSMVQWIX3LMV45UABCJFZXG5LFIV3GK3TUJZXXI2LGNFRWC5DJN5XDWMJUGE3DCOJQGQ2TMMI
.
You are receiving this because you were mentioned.Message ID:
@.***>

Done


Scaffold Courses Page

Describe the task that needs to be done.
Create basic page for displaying courses. Does not need functionality or styling.
Describe how a solution to your proposed task might look like (and any alternatives considered).
Basic skeleton of an course display page similar to designs on figma
Notes
This issue was discussed and approved during a timetable team meeting on 11/03/22.

closed by #91


Is it bannable in Valorant?

I started using your software two days ago, but i forgot to find any information about bans. So i wanna know what could happen if i use it.

Nobody got banned yet!


Carry On mod + RPGDifficulty

Make sure you are not opening a duplicate.

[X] I have searched the issue tracker and did not find an issue describing my bug.

Description of your suggestion.
Hi, sorry to bother you. I have encountered a small issue between two mods: RPGDifficulty and CarryOn.
To provide a simple explanation of CarryOn, this mod allows you to manually grab entities or blocks using your hands and relocate them to a different location.
RPGDifficulty adjusts the base HP of entities based on factors such as the player's LevelZ, distance, time, etc. When an entity is grabbed using CarryOn and then put back, it acquires a new base HP value, and RPGDifficulty applies its scaling bonus to it.
It's quite amusing, but some of my players managed to create a villager with 10 million health by continuously spamming the grab function, hahaha.
I will also reach out to the CarryOn developers. Thank you for your understanding. If you could offer any assistance, it would be greatly appreciated! Otherwise, have a wonderful day!

Do you use the latest version of this mod?


SQM upload and download mixed

Latest full version for Nanopi R4S.
So i just installed it yesterday and noticed that upload and download speed settings are mixed.
If i put them correctly for my 1000/500 connection (900000 for dl and 490000 for up) i get 470/470 and if i set them other way around i get 870/470.

Thanks for reporting, however I am not sure this issue is related to my build or a more general OpenWrt issue. I would recommend to check on OpenWrt forums or open an issue on OpenWrt github repository. Let me know if there is a fix/workaround and I could integrate it to the build.

Latest full version for Nanopi R4S. So i just installed it yesterday and noticed that upload and download speed settings are mixed. If i put them correctly for my 1000/500 connection (900000 for dl and 490000 for up) i get 470/470 and if i set them other way around i get 870/470.

This is happening cause by default the interface that comes selected in SQM page is eth1 and not eth0.


Set the content encoding on artifacts uploaded to s3

This sucker isn't fully tested yet, wanted to get buy in on the approach before doing the leg work :)
We (Shopify) upload a whackload of artifacts to s3 using the buildkite agent, and have started to need to compress some of the bigger ones. We're working on a bunch of coverage stuff and other test time instrumentation who's artifacts can get really, really big at the highest fidelity, so we gzip them after we produce them and before they get uploaded. This is all well and good and Buildkite doesn't have to care, but, we also want to start doing useful stuff with them after they're uploaded!
S3 serves them, and it gets the mime type right (or I guess as right as you can be for a csv.gz file), but it doesn't set a Content-Encoding header when it serves the file. Technically, it's fine to serve a gzipped stream without specifying that that is how the stream is compressed, but, it breaks consumers that aren't smart enough to know the thing is gzipped. We have one such consumer which is a codebase we don't really control and don't really want to couple to our file naming format (Neo4j). It uses the Content-Encoding to know how do decode the incoming stream and if it should decompress, and since S3 doesn't set the encoding unless you tell it to, it doesn't do any decoding, and we end up with compressed gobbledegook in the database.
So, I'd love it if the agent did the same kind of profiling that it does for the mime type for the content encoding, and set that in the s3 options for the put. That way, S3 would serve the blob with the right content encoding, and any downstream consumers (like neo4j or the browser for that matter) would consume knowing that it had to decompress.
What do y'all think of the idea? And if you like it, where should I put the code that does this profiling? I did a simple version to illustrate but I'm not the best go programmer so feel free to tell me how it can be better and how to test.
Thanks!

Sounds like a great idea!

Ok, questions for moving forward then:

Is it ok to land the logic that guesses at a content encoding in the agent's mime module? It's not really a mime related thing, but I like putting it somewhere other than the s3 uploader
Is there a way to mock the whole upload process so I can write a test that actually executes the code in question? Looks like there isn't one for the flow yet
Any tips on testing this locally? I can bootstrap my environment and run the agent but should I just be able to invoke the upload task?

I just merged https://github.com/buildkite/agent/pull/474 in, which brings in the latest aws sdk. I resolved conflicts as best as I could.
I'd love to get your PR merged and I will do some manual testing. You should absolutely be able to run the agent locally if you have AWS credentials setup and a custom s3 bucket. Check out https://buildkite.com/docs/agent/cli-artifact#using-your-own-s3-bucket

Ok, I ran a test successfully locally and uploaded an artifact, so awesome, but then pulled and merged in the AWS SDK changes as well as the hotfix branch up to 13c0739 and am now getting segfaults with what worked before. Same issue as mentioned over there with the AWS_REGION env var, but, I actually set it to us-east-1 locally and still get a segfault. Here's the stack:
OTT-HarryBrundage ~/C/g/s/g/b/agent (gzip-content-type) ➜
go run main.go artifact upload ~/Code/wedge-viewer/artists.csv.gz s3://shopify-test/buildkite-upload-test
2017-06-27 17:46:09 INFO   Found 1 files that match "/Users/hornairs/Code/wedge-viewer/artists.csv.gz"
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x0 pc=0x13cec13]

goroutine 1 [running]:
github.com/buildkite/agent/vendor/github.com/aws/aws-sdk-go/aws/ec2metadata.(*EC2Metadata).GetMetadata(0x0, 0x198bcef, 0x19, 0x921e0, 0x1ef1cc0, 0x18b9340, 0x18b9340)
	/Users/hornairs/Code/go/src/github.com/buildkite/agent/vendor/github.com/aws/aws-sdk-go/aws/ec2metadata/api.go:26 +0x153
github.com/buildkite/agent/vendor/github.com/aws/aws-sdk-go/aws/credentials/ec2rolecreds.requestCredList(0x0, 0x1, 0x1ef2960, 0x21af280, 0x10000c420000340, 0xc4201ddcc8)
	/Users/hornairs/Code/go/src/github.com/buildkite/agent/vendor/github.com/aws/aws-sdk-go/aws/credentials/ec2rolecreds/ec2_role_provider.go:133 +0x58
github.com/buildkite/agent/vendor/github.com/aws/aws-sdk-go/aws/credentials/ec2rolecreds.(*EC2RoleProvider).Retrieve(0xc4201991d0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x21af280, ...)
	/Users/hornairs/Code/go/src/github.com/buildkite/agent/vendor/github.com/aws/aws-sdk-go/aws/credentials/ec2rolecreds/ec2_role_provider.go:89 +0x65
github.com/buildkite/agent/vendor/github.com/aws/aws-sdk-go/aws/credentials.(*ChainProvider).Retrieve(0xc420199230, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x18c5400, ...)
	/Users/hornairs/Code/go/src/github.com/buildkite/agent/vendor/github.com/aws/aws-sdk-go/aws/credentials/chain_provider.go:77 +0xc9
github.com/buildkite/agent/vendor/github.com/aws/aws-sdk-go/aws/credentials.(*Credentials).Get(0xc420071b00, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, ...)
	/Users/hornairs/Code/go/src/github.com/buildkite/agent/vendor/github.com/aws/aws-sdk-go/aws/credentials/credentials.go:208 +0x13a
github.com/buildkite/agent/vendor/github.com/aws/aws-sdk-go/aws/signer/v4.Signer.signWithBody(0xc420071b00, 0x0, 0x1e8e4e0, 0xc42000e1b8, 0x10100, 0x19acb58, 0x0, 0xc42000b800, 0x1e92da0, 0xc4201a9960, ...)
	/Users/hornairs/Code/go/src/github.com/buildkite/agent/vendor/github.com/aws/aws-sdk-go/aws/signer/v4/v4.go:338 +0x259
github.com/buildkite/agent/vendor/github.com/aws/aws-sdk-go/aws/signer/v4.signSDKRequestWithCurrTime(0xc4201be800, 0x19acb58, 0x0, 0x0, 0x0)
	/Users/hornairs/Code/go/src/github.com/buildkite/agent/vendor/github.com/aws/aws-sdk-go/aws/signer/v4/v4.go:472 +0x2f4
github.com/buildkite/agent/vendor/github.com/aws/aws-sdk-go/aws/signer/v4.SignSDKRequest(0xc4201be800)
	/Users/hornairs/Code/go/src/github.com/buildkite/agent/vendor/github.com/aws/aws-sdk-go/aws/signer/v4/v4.go:416 +0x52
github.com/buildkite/agent/vendor/github.com/aws/aws-sdk-go/aws/request.(*HandlerList).Run(0xc4201be970, 0xc4201be800)
	/Users/hornairs/Code/go/src/github.com/buildkite/agent/vendor/github.com/aws/aws-sdk-go/aws/request/handlers.go:164 +0x87
github.com/buildkite/agent/vendor/github.com/aws/aws-sdk-go/aws/request.(*Request).Sign(0xc4201be800, 0x19ab640, 0xc4201be800)
	/Users/hornairs/Code/go/src/github.com/buildkite/agent/vendor/github.com/aws/aws-sdk-go/aws/request/request.go:337 +0xb0
github.com/buildkite/agent/vendor/github.com/aws/aws-sdk-go/aws/request.(*Request).Send(0xc4201be800, 0x0, 0x0)
	/Users/hornairs/Code/go/src/github.com/buildkite/agent/vendor/github.com/aws/aws-sdk-go/aws/request/request.go:474 +0x13d
github.com/buildkite/agent/vendor/github.com/aws/aws-sdk-go/service/s3.(*S3).ListObjects(0xc42000e1d0, 0xc4201ec400, 0x0, 0x0, 0x0)
	/Users/hornairs/Code/go/src/github.com/buildkite/agent/vendor/github.com/aws/aws-sdk-go/service/s3/api.go:3887 +0x4d
github.com/buildkite/agent/agent.newS3Client(0x7fff5fbff6de, 0xc, 0xc, 0xc420010f01, 0xc4201babb0)
	/Users/hornairs/Code/go/src/github.com/buildkite/agent/agent/s3.go:108 +0x55c
github.com/buildkite/agent/agent.(*S3Uploader).Setup(0xc4201a9020, 0x7fff5fbff6d9, 0x27, 0x0, 0x1976c01, 0x4)
	/Users/hornairs/Code/go/src/github.com/buildkite/agent/agent/s3_uploader.go:35 +0x6e
github.com/buildkite/agent/agent.(*ArtifactUploader).upload(0xc4201ec100, 0xc42000e1b0, 0x1, 0x1, 0x2, 0x0)
	/Users/hornairs/Code/go/src/github.com/buildkite/agent/agent/artifact_uploader.go:152 +0x13f
github.com/buildkite/agent/agent.(*ArtifactUploader).Upload(0xc4201ec100, 0x1e, 0xc4200100bd)
	/Users/hornairs/Code/go/src/github.com/buildkite/agent/agent/artifact_uploader.go:47 +0x212
github.com/buildkite/agent/clicommand.glob..func5(0xc4201bc8c0)
	/Users/hornairs/Code/go/src/github.com/buildkite/agent/clicommand/artifact_upload.go:91 +0x297
github.com/buildkite/agent/vendor/github.com/urfave/cli.HandleAction(0x17c66a0, 0x19ab520, 0xc4201bc8c0, 0xc420071800, 0x0)
	/Users/hornairs/Code/go/src/github.com/buildkite/agent/vendor/github.com/urfave/cli/app.go:487 +0x7c
github.com/buildkite/agent/vendor/github.com/urfave/cli.Command.Run(0x1979530, 0x6, 0x0, 0x0, 0x0, 0x0, 0x0, 0x199677e, 0x23, 0x0, ...)
	/Users/hornairs/Code/go/src/github.com/buildkite/agent/vendor/github.com/urfave/cli/command.go:207 +0xb72
github.com/buildkite/agent/vendor/github.com/urfave/cli.(*App).RunAsSubcommand(0xc4201469c0, 0xc4201bc640, 0x0, 0x0)
	/Users/hornairs/Code/go/src/github.com/buildkite/agent/vendor/github.com/urfave/cli/app.go:374 +0xacc
github.com/buildkite/agent/vendor/github.com/urfave/cli.Command.startApp(0x197b06b, 0x8, 0x0, 0x0, 0x0, 0x0, 0x0, 0x199d134, 0x2d, 0x0, ...)
	/Users/hornairs/Code/go/src/github.com/buildkite/agent/vendor/github.com/urfave/cli/command.go:293 +0x8a3
github.com/buildkite/agent/vendor/github.com/urfave/cli.Command.Run(0x197b06b, 0x8, 0x0, 0x0, 0x0, 0x0, 0x0, 0x199d134, 0x2d, 0x0, ...)
	/Users/hornairs/Code/go/src/github.com/buildkite/agent/vendor/github.com/urfave/cli/command.go:93 +0x14c7
github.com/buildkite/agent/vendor/github.com/urfave/cli.(*App).Run(0xc420146820, 0xc420010230, 0x5, 0x5, 0x0, 0x0)
	/Users/hornairs/Code/go/src/github.com/buildkite/agent/vendor/github.com/urfave/cli/app.go:250 +0x7d0
main.main()
	/Users/hornairs/Code/go/src/github.com/buildkite/agent/main.go:102 +0x565
exit status 2

This was a regression I accidentally introduced 😱! Fixed in https://github.com/buildkite/agent/pull/497

@lox I double checked to make sure by merging master again, but even with #497 merged that SIGSEGV is still happening with the AWS_REGION variable set. Then, I realized I hadn't re-set my environment variables for AWS authentication (BUILDKITE_S3_ACCESS_KEY_ID etc), and when I set them, the upload worked again which is great news, so this PR is good to go. But, the above exception is in fact still possible to hit on master if you don't have S3 access creds in the environment before starting the s3 session. I am not sure why that would be because it looks like it should panic earlier when those env vars aren't found, but you might know better :)

Investigating this today @airhorns!

I've had a go at reproducing the panic on master, having a hard time doing so. This PR looks good to go, so I will keep going with it in master. Thanks for the hard work!


Ansible refactor interim PR #3 of 7 - Move Seattle-specfic files/paths to more general location name

To make the codebase more general, this PR renames the folder "seattle_example" to "local_customizations" and the sub-folder that used to be specific to Seattle to "geofiles". This PR also removes a few files that are now in templates from the previous PR, and in anticipation of a unified playbook in a later PR, removes the seattle_tasks.yml playbook.

This change is

LGTM.


Spin up & tear down separate Docker networks for individual test cases

Required for parallelized test cases, but not necessary while these are in serial

Dunnnnnn


create blackjack simulation

Blackjack simulation game.
Main feature:
- Totally object oriented
- Player multiple decision
- Bet
- Hit
- Stand
- Double-down
- Surrender
- Record display
- Color output support
Develop & Test environment
- Ubunt 16.04.6 LTS
- Python 3.5.2
Dependence package:
- Built-in
- os, random, functools

Sorry, I'm am familiar with the github pull request


nuclei: 2.5.3 -> 2.5.4

Motivation for this change
Update to latest upstream release 2.5.4
Change log: https://github.com/projectdiscovery/nuclei/releases/tag/v2.5.4
Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
22.05 Release Notes (or backporting 21.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

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

1 package built:

nuclei


Multi meter

Has the multi meter that indicated in the code actually been tested?

Yes, I tested it about a month ago.
On Sat, Aug 5, 2023, 07:38 disforw @.***> wrote:

Has the multi meter that indicated in the code actually been tested?
—
Reply to this email directly, view it on GitHub
https://github.com/kdeyev/eyeonwater/issues/26, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AA6LHLOVLBHZNCGNYM3PBC3XTZLGJANCNFSM6AAAAAA3FIFS74
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

Being that I only have a single meter, can you explain what attribute gets duplicate when having more than 1? Is it "register_0"?

I'm still away from the keyboard. Sorry for the laconic answers.
I believe it was two different meters each one had its uuid and a single
register_0. I newer saw register_1 and, yes, the data model is not clear
but I did my best in reverse engineering.
On Sat, Aug 5, 2023, 07:45 disforw @.***> wrote:

Being that I only have a single meter, can you explain what attribute gets
duplicated when having more than 1? Is it "register_0"?
—
Reply to this email directly, view it on GitHub
https://github.com/kdeyev/eyeonwater/issues/26#issuecomment-1666524625,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AA6LHLLOEFVSLTQLD4BYUEDXTZL7RANCNFSM6AAAAAA3FIFS74
.
You are receiving this because you commented.Message ID:
@.***>


Won't draw strider answer

On this query:
query_graph = {
    "nodes": [
        {
            "id": "a",
            "type": "disease",
            "curie": "MONDO:0005015"
        },
        {
            "id": "b",
            "type": "gene"
        },
        {
            "id": "c",
            "type": "chemical_substance"
        }
    ],
    "edges": [
        {
            "id": "ab",
            "source_id": "a",
            "target_id": "b",
            "type": "gene_associated_with_condition",
        },
        {
            "id": "bc",
            "source_id": "c",
            "target_id": "b",
            "type": "decreases_activity_of"
        }
    ]
    }

sent to strider, and waiting for the first few results, and then sending that message to GammaViewer gives a "BadMessage" Error.
The problem seems to be that strider is adding curie:None to nodes b & c in the question graph. If those are deleted, then gamma viewer can draw it.

The JSON validation is based off of Translator Reasoners API version 0.9.2. More informative validation error messaging has also been added. Closing for now, but feel free to reopen if you think we need to support more types of messages.


Added react-native-segmented-control-tab

https://github.com/kirankalyan5/react-native-segmented-control-tab

Epic! Thank you so much :D


Windows build error: 64-bit mode not compiled in

I get the following error when trying to build time on Windows 7, 64bit system...
failed to run custom build command for `time v0.1.12`
Process didn't exit successfully: `C:\Users\alchemist\Documents\Rusty\face-blaster\target\build\time-7c7fc3eb0c12ad75\bu
ild-script-build.exe` (status=101)
--- stdout
TARGET = Some("x86_64-pc-windows-gnu")
OPT_LEVEL = Some("0")
TARGET = Some("x86_64-pc-windows-gnu")
HOST = Some("x86_64-pc-windows-gnu")
CC_x86_64-pc-windows-gnu = None
CC_x86_64_pc_windows_gnu = None
HOST_CC = None
CC = None
TARGET = Some("x86_64-pc-windows-gnu")
HOST = Some("x86_64-pc-windows-gnu")
CFLAGS_x86_64-pc-windows-gnu = None
CFLAGS_x86_64_pc_windows_gnu = None
HOST_CFLAGS = None
CFLAGS = None
CARGO_MANIFEST_DIR = Some("C:\\Users\\alchemist\\.cargo\\registry\\src\\github.com-1ecc6299db9ec823\\time-0.1.12")
OUT_DIR = Some("C:\\Users\\alchemist\\Documents\\Rusty\\face-blaster\\target\\build\\time-7c7fc3eb0c12ad75\\out")
running: gcc '-O0' '-c' '-ffunction-sections' '-fdata-sections' '-mwin32' '-m64' '-fPIC' 'C:\Users\alchemist\.cargo\regi
stry\src\github.com-1ecc6299db9ec823\time-0.1.12\src\time_helpers.c' '-o' 'C:\Users\alchemist\Documents\Rusty\face-blast
er\target\build\time-7c7fc3eb0c12ad75\out\src\time_helpers.o'

--- stderr
C:\Users\alchemist\.cargo\registry\src\github.com-1ecc6299db9ec823\time-0.1.12\src\time_helpers.c:1:0: warning: -fPIC ig
nored for target (all code is position independent) [enabled by default]
// Copyright 2012 The Rust Project Developers. See the COPYRIGHT
^
C:\Users\alchemist\.cargo\registry\src\github.com-1ecc6299db9ec823\time-0.1.12\src\time_helpers.c:1:0: sorry, unimplemen
ted: 64-bit mode not compiled in
thread '<main>' panicked at 'nonzero exit status: exit code: 1', C:\Users\alchemist\.cargo\registry\src\github.com-1ecc6
299db9ec823\gcc-0.1.4\src\lib.rs:125

$ cargo build
Compiling gcc v0.1.4
Compiling time v0.1.12
failed to run custom build command for time v0.1.12
Process didn't exit successfully: D:\root\Language_Performance_Contest\Prime\Rust\target\build\time-7c7fc3eb0c12ad75\build-script-build.exe (status=101)
--- stdout
TARGET = Some("x86_64-pc-windows-gnu")
OPT_LEVEL = Some("0")
TARGET = Some("x86_64-pc-windows-gnu")
HOST = Some("x86_64-pc-windows-gnu")
CC_x86_64-pc-windows-gnu = None
CC_x86_64_pc_windows_gnu = None
HOST_CC = None
CC = None
TARGET = Some("x86_64-pc-windows-gnu")
HOST = Some("x86_64-pc-windows-gnu")
CFLAGS_x86_64-pc-windows-gnu = None
CFLAGS_x86_64_pc_windows_gnu = None
HOST_CFLAGS = None
CFLAGS = None
CARGO_MANIFEST_DIR = Some("C:\msys64\home\Administrator\.cargo\registry\src\github.com-1ecc6299db9ec823\time-0.1.12")
OUT_DIR = Some("D:\root\Language_Performance_Contest\Prime\Rust\target\build\time-7c7fc3eb0c12ad75\out")
running: gcc '-O0' '-c' '-ffunction-sections' '-fdata-sections' '-mwin32' '-m64' '-fPIC' 'C:\msys64\home\Administrator.cargo\registry\src\github.com-1ecc6299db9ec823\time-0.1.12\src\time_helpers.c' '-o' 'D:\root\Language_Performance_Contest\Prime\Rust\target\build\time-7c7fc3eb0c12ad75\out\src\time_helpers.o'
I also hit this.

64-bit Windows 8 here

This typically means that you're running in a 32-bit MSYS shell instead of a 64-bit MSYS shell. Could you guys confirm that you're running in the 64-bit shell?

32-bit MSYS was the culprit in my case.

Closing issue, fixed my case


Doc Feedback: This page has a JIRA link

Location : https://is.docs.wso2.com/en/5.11.0/develop/creating-a-third-party-authenticator-or-connector-and-publishing-in-wso2-store/

This issue is being closed due to extended inactivity. Please feel free to reopen it if further attention is needed. Thank you for helping us keep the issue list relevant and focused!


Support resource naming override

Description
When using the core module to deploy resources there we have identified a need to override the standard naming of resources.
Scenario 1 - Subscription short name
When using the core-module to deploy multiple core setups in customers environments we will end up with multiple resources with the same name. This is because we use the core-module to deploy any kind of Landing zones in Azure.
Example:
Using the core module multiple times will result in multiple virtual networks called vnet-prod-we-core.
Suggestion:
Would it be possible to introduce subscription short as a optional attribute in the naming?
vnet-prod-we-lzvw-core where lzvw is shorten for Landing zone Virtual Workspace.
Scenario 2 - CAF Naming Convention / Customer specific
Microsoft have a naming convention in Azure which we try to align to but it does not follow a strict pattern:
Example:
Subnet - 'snet-subscription-region-###'
Public  IP - pip-"vm name or app name"-environment-region-###
Route Table - route-"route table name"
More examples: https://docs.microsoft.com/en-us/azure/cloud-adoption-framework/ready/azure-best-practices/resource-naming
In this case it would be useful to be able to override the naming convention to align with CAF.
The same scenario goes for deployments where customer have a established naming convention we need to follow for new resources.

@ahockersten can you make sure we get started with this? Please and thank you. 😊


Minor detail fixes for Developer Guide

Codecov Report

Merging #370 (a0a24b9) into master (5a8c109) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master     #370   +/-   ##
=========================================
  Coverage     77.68%   77.68%
  Complexity      721      721
=========================================
  Files           101      101
  Lines          2120     2120
  Branches        244      244
=========================================
  Hits           1647     1647
  Misses          425      425
  Partials         48       48

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more

Ran a spellchecker for American English (rationale - code is done with American English so we should be consistent)

[ ] Under DG file format "capitalisation" should be "capitalization"

[ ] Under Use cases, impatient user, "visualization"

[ ] Non-functional requirements > Accessibility, point 9 > "recognizable"


'Go live' does not work on windows.

I had other problems, I dont know if it's related or not to #32
I inserted an win.webContents.openDevTools() to see the output when I click on Go live and the error was Uncaught Error: route 'C:/broadcast' did not match. So I went to home.js (line 38) and changed to ./brodcast, then the error was Uncaught Error: route 'C:/Users/*/Documents/GitHub/hypervision/broadcast' did not match. So, again I changed to ./components/broadcast and the error is the same, just different directory Uncaught Error: route 'C:/Users/*/Documents/GitHub/hypervision/components/broadcast' did not match. I even tried to change to ./components/broadcast.js but I got nothing.

Great stuff. Any plans soon to support WIN?

One possible way to fix the routes I came across is intercepting file:// requests, removing the file: identifier, and normalizing the path to remove the duplicate slashes. So file:///broadcast ends up becoming /broadcast and choo can match it. Here's app.js with the changes:
var electron = require('electron')
var path = require('path')

var win = null
var app = electron.app
var BrowserWindow = electron.BrowserWindow

app.on('ready', function () {
  console.log('The application is ready.')

  const PROTOCOL = 'file'
  electron.protocol.interceptFileProtocol(PROTOCOL, (request, callback) => {

      // Strip protocol
      let url = request.url.substr(PROTOCOL.length + 1)

      // Build complete path for node require function
      url = path.join(__dirname, url)

      // Removes duplicate slashes
      url = path.normalize(url)

      callback({path: url})
  })

  win = new BrowserWindow({
    width: 854,
    height: 650,
    minWidth: 550,
    minHeight: 200
  })

  // win.loadURL('file://' + path.join(__dirname, 'index.html'))
  win.loadURL('file://' + '/index.html')

  win.on('close', function () {
    win = null
  })
})

I had the same issue as @obernardovieira and the solution by @gwbutler didn't fix it (Windows 10, Chrome v67).
It looks as though Choo already intercepts electron file paths, but the regex in nanorouter doesn't account for Windows adding the drive letter so /broadcast returns as C:/broadcast etc
Changing the regex in node_modules\nanorouter\index.js to capture the drive letter worked for me:
previous:
var electron = '^(file:\/\/|\/)(.*\.html?\/?)?'
new:
var electron = '^(file:(\/\/|\/)|\/C:)(.*\.html?\/?)?'
This match is only checked when isLocalFile is true so I assume it won't break anything elsewhere in nanorouter but either way it seems to get the job done here (between two instances of hypervision on the same computer, anyway, I haven't checked remote peers yet...)

Confirming that the fix by @cihapus works for me as well on a new hypervision instance (also Windows 10, Chrome v67). I tweaked it a little to account for different drive letters: var electron = '^(file:\/\/|\/([A-Z]:)?)(.*\.html?\/?)?'


[PW-6019] Add option to easily provide additionalData.RequestedTestAcquirerResponseCode to test payment errors

Describe the bug
In order to test all possible payment errors, it is possible to be able to specify additionalData.RequestedTestAcquirerResponseCode in the \Adyen\Shopware\Handlers\AbstractPaymentMethodHandler::preparePaymentsRequest method.
According to documentation: https://docs.adyen.com/development-resources/test-cards/result-code-testing/adyen-response-codes
Best would be to add the information somehow with the payment-details request or maybe automatically convert the holder name to the correct value that way it can be entered in the credit card form.
It cannot be set currently that way because all additional data is overridden here:
https://github.com/Adyen/adyen-shopware6/blob/develop/src/Service/PaymentStateDataService.php#L82
and in the php api library the CheckoutStateDataValidator removes it, if not set after calling it:
https://github.com/Adyen/adyen-php-api-library/blob/develop/src/Adyen/Service/Validator/CheckoutStateDataValidator.php
I tried the card holder option. However, not all error codes seem to provide the correct refusal code with the holder name. a lot just result in FRAUD instead of the corresponding refusal code but e.g. differentiating between refused and ERROR works with the holder name too.

@AndreasA no it will not

@AndreasA no it will not

Thanks for letting me know. This one isn't that important anyway. Way more important is the one that provides the reason code in the store api 😄

can probabky be fixed (for headless) by removing the checkoutstatevalidator which should not be used anymore anyway according to https://github.com/Adyen/adyen-php-api-library/issues/531#issuecomment-1735749828 and https://github.com/Adyen/adyen-php-api-library/issues/536#issuecomment-1735747796

Hi Andreas,
Thank you for suggesting this option for testing payment errors. We appreciate your input.
At this time, however, this feature is not planned, nor is it anticipated in the near future. Its development would depend on the Adyen team’s roadmap and priorities.
Should there be any updates regarding this feature, we’ll be sure to keep you informed.
Best regards


vaadin-text-area style in readonly mode

The vaadin-text-area styles are not being applied correctly when it’s in readonly mode.
There is no dashed border, or a transparent background as it is the case for the vaadin-text-field

Expected behavior:
The vaadin-text-area has a dashed border and transparent background when in readonly mode, such as:

Actual behavior:
The vaadin-text-area has no borders and the background is not transparent:

Caused by this line: https://github.com/vaadin/vaadin-text-field/blob/master/theme/lumo/vaadin-text-area-styles.html#L18
Should be fixed if we change to this one:
:host(:not([readonly])) [part="input-field"]::after {


Support on Safari 12

It seems Animate.css is not working on Safari (macOs) v12.0.3. After some research, I see no information about a lack of support on Safari. Do I miss something?
To reproduce it, visit https://daneden.github.io/animate.css/
The intro animation (bounceIn) will work, not the others. In my application, all animations are working on Chrome, but not on Safari

The same with mobile Safari on iOS 11.

Version 3.6.2 works by the way, only 3.7.0 doesn't.


Expose match count/index for modeline segments?

Does ctrlf expose its current search state anywhere for use in segments like https://github.com/seagle0128/doom-modeline/blob/master/doom-modeline-segments.el#L1222 ?
My experimentation and skimming of the code suggested that it constructs its overlays lazily, so that I can't just count the number of overlays.

I do not believe these stats are exposed in a friendly way, but they could/should be. Sorry for the inconvenience.


Why did nameko use RPC for Communication between Service?

I think this is not issue, rather than just a question. Why did nameko use RPC for Communication between Service? Is there any issue when using REST? or RPC much faster for this communication purpose? Sorry I am newbie at microservices

The main reason is that RPC is simple. It can be invoked just like a "normal" method and is very flexible in terms of what the server can offer. Unlike REST it doesn't force you to write your APIs in a particular way.
There's a good (tongue-in-cheek) article about it here: https://medium.freecodecamp.org/rest-is-the-new-soap-97ff6c09896d

RPC over RabbitMQ, as implemented in Nameko, gives you service discovery for free where you can have multiple services handling RPC requests effortlessly. Additionally Nameko comes with HTTP endpoint (based on werkzeug) which lets you build any REST APIs you'd like.

Does nameko only support RPC over *MQ, not raw RPC?  If I have an existing RPC server, and I want to use nameko just for the RPC client, is that possible?
thanks.

"RPC" just means Remote Procedure Call. It doesn't imply an implementation or even a protocol. You'll only be able to talk to your "existing RPC server" using whatever protocol it uses.
You could build an extension in Nameko that implemented whatever protocol that is so your Nameko service could speak it, but you can't just use the built-in AMQP client unless your remote server is listening for Nameko AMQP RPC.

This issue was moved to https://discourse.nameko.io/t/why-did-nameko-use-rpc-for-communication-between-service/304


[WIP] adaptive sampling: double sampling time on edges with mapper scores > n

fixes https://github.com/asapdiscovery/asapdiscovery/issues/1227
Developers certificate of origin

[x] I certify that this contribution is covered by the MIT license as defined in our LICENSE and adheres to the Developer Certificate of Origin.

also added in some speed improvement suggestions by OpenFE, and added a class for adaptive settings that is a draft version of https://github.com/asapdiscovery/asapdiscovery/issues/1254, but good enough for now. @jthorton can you have a look over these changes as it's mostly pydantic finaggling?


Syntax highlighting is broken

Thanks for the awesome plugin!
I can code comfortably thanks to this plugin!
However, when I installed the latest version of this plugin, I encountered a few bugs.

The syntax highlighting is very different from the previous ones(after | before)

Commenting breaks the syntax highlighting

Adding new code changes the highlighting

I've tried the following

Reinstall omnisharp-vim using dein
rm -rf ~/.omnisharp ~/.cache/omnisharp-vim
Reinstall omnisharp-roslyn v1.35.2(I've tried the latest version too.)

My environment

MacOS 10.15.5 (x64)
NVIM v0.4.3

[[plugins]]
repo = "OmniSharp/omnisharp-vim"
on_ft = ["cs"]
build = "xbuild server/OmniSharp.sln"
hook_add = '''
let g:OmniSharp_server_stdio = 1
autocmd FileType cs nnoremap gd :OmniSharpGotoDefinition<cr>
autocmd FileType cs nnoremap <C-m><c-n> :OmniSharpRename<cr>
autocmd FileType cs nnoremap <C-m><C-f> :OmniSharpCodeFormat<cr>
'''

(I wrote it while using a translator, so I'm sorry if it's hard to understand.)

Hi @DuGlaser,
Thanks for opening the issue, I just merged a big PR today and it looks like some things aren't working properly, sorry about that.
One change I made was to enable highlighting by default - you can just turn it off by adding this to your .vimrc:
let g:OmniSharp_highlighting = 0

@nickspoons Thank you for the reply!
All the plugins I use are listed here.

https://github.com/DuGlaser/nvim_setting/tree/master/dein

But even with the other plugins over there, I still got the bug.
So I'm not sure if it conflicts with other plugins, but I'll check things out here as well.

It's interesting how in your example, when you comment out using UnityEngine; the highlights appear to remain in place, as the code moves. Very peculiar - when I do the same, the highlights move with the code.
I'm using a more recent version of neovim (NVIM v0.5.0-571-g721f69c4a) - I wonder if it has to do with the version? I'll try to get hold of an older version to test with.
Did you try just turning semantic highlighting off as I suggested earlier? Is that better?

let g:OmniSharp_highlighting = 0

I don't have a problem when I use this.
Thank you very much!

Ah OK that's good. Were you using the OmniSharp-vim highlighting before this latest change? When was the last time you updated the plugin? Highlighting has only been available in neovim since #588 was merged 1 month ago.

Ah, I just tried with neovim 0.4.3 and I see the behaviour you show in your gif

However, it is fixed as soon as I leave insert mode.
So this looks like the highlight anchoring/positioning is fixed in later versions of neovim.
As for the rest of the highlighting, you can of course leave it turned off if that works for you. If you want to configure it, there's a wiki article describing the options in detail: Highlighting configuration

I wasn't using OmniSharp-vim highlighting.
Also, the last time I updated the plugin was about a week ago

Right, so the issue was just me turning it on by default.
Perhaps turning it on by default was a mistake. I'm not sure, I'll leave it for a while and see if any others have input.

I don't think this one is a bug (although it highlights a neovim issue which has been fixed), so closing

Hope commenting on a closed issue doesn't come as annoying. I've tested this in a barebones nvim config, but I decided to check the issues later.
I'm not sure the plugin's syntax highlighting is "correct": it looks like it's colouring many of roslyn's classification types the same way. The only difference between the screenshots is tweaking the value of OmniSharp_highlight_groups:
Before:

After:

Roslyn's types FieldName and LocalName seem to have the Identifier highlight value by default, which tints a lot of the code the same way (blue in my case).
https://github.com/OmniSharp/omnisharp-vim/blob/f517e774e4e940dc5fdcd3f1dcc0fc6dcd190888/autoload/OmniSharp/actions/highlight.vim#L208-L212
In the "after" screenshot I've got the following configuration:
let g:OmniSharp_highlight_groups = {
\ 'Comment': 'NonText',
\ 'FieldName' : 0,
\ 'LocalName' : 0,
\ 'XmlDocCommentName': 'Identifier',
\ 'XmlDocCommentText': 'NonText'
\}

(with a numeric value insted of a valid literal seems to get no highlighting, which is fine to me right now)
This is my setup. I've tried different combinations of windows-terminal themes too, but it doesn't seem to be about that.

NVIM v0.5.0-638-g91109ffda
microsoft-windows-terminal 1.0.1811.0

Is this the expected behaviour? Also thank you for taking the time to read this post and taking care of this project!

Hi @compilercomplied, I would say that yes, that is the expected behaviour.
It might be that we can find better defaults, but I'm not sure what the best way to go about that would be - some kind of public poll/discussion?. As you've said, it is reasonably simple to change groups to whatever you like, and get full control over your highlighting.
I don't like to tweak the defaults too much, as that results in unexpected changes for users as they upgrade. So if we do decide to change any defaults I think we should do it in one go.

I personally think it's kind of weird; if everything is highlighted then nothing actually is. Nevertheless, if that's the expected outcome  and it's trivial to change, I guess there is any reason to change it.
Thank you for the quick response!


FutureUniverseSelectionModel Doesn't Pass Canonical Symbol to OnSecuritiesChanged

Expected Behavior

Whether we use AddFuture or AddUniverseSelection(FutureUniverseSelectionModel), we get the canonical Symbol in OnSecuritiesChanged.
Actual Behavior

We get the canonical Symbol if we use AddFuture, but not AddUniverseSelection(FutureUniverseSelectionModel).
Potential Solution

N/A
Reproducing the Problem

Run both cases in this backtest
System Information

QC Cloud
Checklist

[x] I have completely filled out this template
[x] I have confirmed that this issue exists on the current master branch
[x] I have confirmed that this is not a duplicate issue by searching issues

[x] I have provided detailed steps to reproduce the issue

Note that OptionUniverseSelectionModel has the same behavior as FutureUniverseSelectionModel

Note: This limits continuous future usage with the universe selection APIs. It seems currently the canonical security isn't even added to the algorithms.Securities collection. Believe though, the CreateUniverse implementation of the option/future selecitons could potentially directly call AddFuture/Option APIs


Windows Services updates

Fixes #9226
Internal Review Topic (Convert a project into a Windows Service section)

Drops 1.x and 2.0 coverage. Versions whole topic to 2.1 or later.
Upgrades sample app to 2.2 preview3. Added to the 2.2 RTM update tracking issue: #8518
Drops wwwroot assets. Uses new <style> CSS styles.
🎪 User account: Instructs the user on how to create a user account for the service, assign permissions, and set up the service to use the account. The only permissions granted to the user account are read, write, and execute on the service's deployment folder.

Note: The topic is currently still relying on SCD deployment. The updates for FDD/FDE are coming later on another issue.

One thing it might be worth calling out is where you say {domain} if you're not domain joined it should be the local machine?

Yes ... I did NOT do a good job on that. I'll get it on the next commit. Thanks.

@scottaddie No rush on this.


sanitize feature is implemented incorrectly

DOMPurify, when run on a server, requires an external DOM implementation such has JSDOM. The current initialization of sanitize will always be undefined for that reason. Correct usage:

import createDOMPurify from 'dompurify'
import {JSDOM} from 'jsdom'

const {sanitize} = createDOMPurify(new JSDOM('').window)

With 0.6.6 there's a new way of sanitizing user input.
https://github.com/kitajs/html#sanitization


Add YT-1300 Stock Light Freighter from Kerbal Stuff

This pull request was automatically generated by Kerbal Stuff on behalf of LuizChacon, to add YT-1300 Stock Light Freighter to CKAN.
Please direct questions about this pull request to LuizChacon.

part of #1860


Increase contrast for line number foreground

This fixes https://github.com/sdras/night-owl-vscode-theme/issues/60
Before:

After:

Great, thanks!


Bug : Wildcarded source file path in Project file for 'paket pack' symbols flag

Hello again,
While applying the 'paket pack' 'symbol' flag in our projects, I noticed that there was a bug when paket tried to pack sources files that were wildcarded in the Microsoft project file. Paket crashes with "Illegal characters in path." or "Could not find source file [...]".
e.g.
<Compile Include="GENERATED_CS\*.cs" />

or
<Compile Include="GENERATED_CS_LINKED\*.cs">
  <Link>translated\%(FileName).cs</Link>
</Compile>

Here is a repro example : https://github.com/franknarf8/paket-issue-repro/tree/92a01bed12d54b953f518b34979763fa7b14cb01
Thank you

/cc @pms1969

I'll take a look.

@franknarf8, do you know if this was always the case, or was this always a problem?

Well, that was using the new 'symbol' flag for the 'paket pack' command, so it is fairly recent. I just started using this flag so I unfortunately can't tell you if it once was working with wildcards in the <compile [...]> elements.
Prior to this new flag, to get the source files in the nuget package, we had to manually add them in the paket.template file.
e.g.
files
    ../**/*.cs

The wildcards worked then, but with the new flag all the source files are added correctly in the .nupkg except for the ones with wildcards.

OK. I know what to do and where, just need to formulate a plan for how.  I'm not a native f# speaker, but I'll get it done soon.

@franknarf8  should be fixed in 2.45.0.  can you give it a shot and let me know how it goes?

@pms1969 @forki I just tested and everything seems to works perfectly.
Thanks again @pms1969

Awesome


[stable/prometheus] Bump node-exporter to 0.18.0

What this PR does:
Bump node-exporter to latest version (0.18.0)

/ok-to-test
/assign
/lgtm


fix: ollama listModel endpoint when a model doesn't have TEMPLATE

fix for https://github.com/enricoros/big-agi/issues/239

Thanks @g1ibby ! really useful. I made the parsers strict to catch if there are changes in expectations form the Ollama vendor. You probably found this fast and saved others ! :)


Add TA troubleshooting page

Adding page to the docs with tips for troubleshooting the OTel Operator's Target Allocator.
This was originally going to be a blog post; however, per suggestion from @svrnm, this is a much better fit.
Reference issue: #4707

Question for @open-telemetry/operator-approvers - I have a working example repo that I'd like to reference on this page, but I think that it's probably best to move this code to an examples folder the OTel Operator repo before doing this. Thoughts?

Thanks, this is a really good addition to docs! A few comments and suggestions. Note that the section titles are really long which might look strange in the outline navigation, maybe we can review and shorten them

Yeah, they do look a bit long. I think that when we had the step numbers, it was a bit easier to distinguish one from the other. Is there a reson why you prefer to leave those out, @svrnm?

FYI @svrnm @swiatekm-sumo @theletterf - I had some previous content for troubleshooting auto-instrumentation, so I creaded a page for that too.

FYI @svrnm @swiatekm-sumo @theletterf - I had some previous content for troubleshooting auto-instrumentation, so I creaded a page for that too.

Can you fork that out in a dedicated PR or is this closely related?

FYI @svrnm @swiatekm-sumo @theletterf - I had some previous content for troubleshooting auto-instrumentation, so I creaded a page for that too.

Can you fork that out in a dedicated PR or is this closely related?

It's not closely related, so I can definitely create a separate PR.

Removed auto-instrumentation troubleshooting page. I have created a separate PR for this (#4724).

@swiatekm-sumo thanks for keeping me honest! I've incorporated your suggestions and did another read through. Hopefully I didn't miss any spots where I mis-explained the TA functionality.

THANK YOU @avillela fantastic work here :D :D :D


Patron Pull Request

Please let me know if this looks ok to merge! Thanks!

Everything looks fine! Merged to main,


Added react-optimize, dev-expression

Coverage remained the same at 93.939% when pulling abbaaa8d5643c2e64d4e9ea4f28373fec9266015 on babel into 7fb6d7e772cd1e2caccf455c5712a2c890122161 on master.


Swapper price impact calculation inaccurate

Overview
The displayed price impact is way off on the swapper display
References and additional details

Acceptance Criteria

Accurate price impact percentage

Need By Date
No response
Screenshots/Mockups
No response
Estimated effort
No response

fix the value here to show the diff between input fiat amount vs output fiat amount and keep the copy as is

Left one will be NET send/receive diff percentage
Right one will be unchanged.


Fix typo for local_client.h

fix typo

@wyzero thanks you for your contribution , latest changes have deleted that line, we don't need this change now, thank you


rustup

@bors r+

@bors r+

:pushpin: Commit 739d796b0588bb7c38c2a69f17d44084d48d5010 has been approved by RalfJung

:hourglass: Testing commit 739d796b0588bb7c38c2a69f17d44084d48d5010 with merge 9b01141b043d8e81394ac18390dfbeda449c7c6a...

:boom: Test timed out


Only bake bakeable objects

Doesn't export mesh block or instance for items that do not have a bake node when baking.

So couple things here.  We shouldn't be doing motion blur at all for baking.... just bake at frame.  I wouldn't worry too much about caching motion in that case (if there's no motion nothing is cached).
Finally can skip the lights in the bake rib.

Sounds good.  I'll get it in.

The rib gen might fail but the rib might render without one.
On Tue, Apr 18, 2017 at 7:28 AM Jon D<EMAIL_ADDRESS>wrote:

@jdent02 commented on this pull request.
In export.py
https://github.com/bsavery/PRMan-for-Blender/pull/481#discussion_r111968127
:

@@ -1779,6 +1779,21 @@ def has_emissive_material(db):
return False

+def export_for_bake(db):

export = True
node_names = []
for mat in db.material:

   if mat and mat.node_tree:

       nt = mat.node_tree

       for n in nt.nodes:

           node_names.append(n.name)

if node_names:

   if 'PxrBakeTexture' not in node_names:

       export = False

Really? One of the early tests I did didn't export a camera and I had an
export fail because it couldn't be found in the instances list. Or should I
add a bake check to the export_camera line in write_rib?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/bsavery/PRMan-for-Blender/pull/481#discussion_r111968127,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABzffLIG4XlnpNZsIY-P_lsjJkYODurKks5rxMh4gaJpZM4M-hcM
.

--
<EMAIL_ADDRESS>508-274-8700

I'm pretty sure it failed when the export_camera function couldn't find the camera in the instance list.  But if that whole function (export_camera) doesn't run then it should be okay.  I'll try it out.


Ferdi Tray icon issue

Bug description:
In Gnome 3.38, the ferdi tray icon doubles (attached SS) whenever there is a screen lock or reloading (Alt+F2). The issue is persistent with Appimage as well as AUR and Flatpak.
Steps to reproduce:

Install Ferdi
Enable Tray Icon
Lock the screen or reload the desktop
Now, two tray icons should be visible

Expected behavior
There should be one icon per application. This bug seems to create a dummy icon on tray.
Screenshots

Environment:

Operating System: Manjaro Linux
Ferdi Version: 5.5
Server: Exists in Ferdi, Franz and Using without an account

Can confirm this on Gnome 3.8 via Manjaro Arch Linux with ferdi-git installed via AUR:

Same issues on Ubuntu 18.04 with Gnome 3.28.4

The issue is no longer persists in 5.5.10 version from official repositories of Manjaro Linux. Not sure about the changes, but no longer the second icon is created.

I am on 5.6.0-n15 and the error is still there.

Please, reopen this issue.
I can confirm that the version from official Manjaro repositories (ferdi-5.5.0-10) fixed this bug but this version is only available for Manjaro users (although you can download the .zst file from their repositories and install it in Arch Linux, like I did - link here from Brazil's mirror).
It's better to keep this issue open until it's fixed for all platform, through developers release.

Based on @DenysMb comment, reopening the issue.

I got the same error with the new nightly 5.6.0-n48

Can all of you please try the new beta.6?

@vraravam It's still broken in the current beta (and also on develop). I'll get around to this, eventually, but it will likely require writing our own StatusNotifierItem implementation (Chromium's built-in one just doesn't handle enough edge cases atm).

In that case, lets keep this for after 5.6?  we need to have minimal changes and get to releasing 5.6 @kris7t

Still present in 5.6.1-nightly43

Is this fixed with this morning's latest nightly?

I tried the today's nightly (#7) but I still have the same error. After blocking the system and login in again, a second icon (invisible) is created.
I'm on Ubuntu 18.04.

I might have some time available in the next few days to take a look at this.

The above fix seems not to have been accepted due to the forced tray icon changes.
How can we fix the duplicate tray icons without force enabling the tray icon?


Feature/profile defaults

Closes #94, #95, and #96.

+1 in the interest of speed although I don't entirely know what I'm looking at.

Thanks!


[CLIPPER-162] [CLIPPER-163] [CLIPPER-146]: Check conda environment for issues in management library and fix bugs

This is a replacement for #130
clipper_manager.deploy_prediction_function now inspects the user's conda environment for solvability within the container's conda channel.
If the environment on the client has packages with conflicting dependencies, we now require them to resolve those issues. Deployment of their prediction function doesn't take place.
If no packages have conflicts, we check if they all exist in the linux-64 conda channel. If some packages do not, we warn the user that those packages will not be installed on the container and update the environment file we provide the container accordingly.
Then, we deploy the function as usual.
Output in the latter case can be long:

Should limit the number of missing packages we list to some small number (say, 5) and write out the full list to a file we give the user the path to?

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Clipper-PRB/256/
Test PASSed.

@nishadsingh1 I know you're busy with finals right now, so I'm going to just make these last couple changes and get this merged.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Clipper-PRB/261/
Test FAILed.

So I've been testing this more and it doesn't quite seem to work. First of all, the containers take a really really long time to build. Like 10 minutes. And including the additional Python dependencies in the container didn't really reduce the time to create the container. But more importantly, as the code stands I can't get the deployed container to actually make predictions. I'm digging into the issue right now.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Clipper-PRB/262/
Test FAILed.

Okay I'm not sure what's going on. This actually seems to be working. The containers still take a really long time to build though. We should definitely look into that and see if we can shorten that somehow.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Clipper-PRB/263/
Test PASSed.


Unifying dataflow & expressions

As a team we've discussed whether there should be a syntax for calling functions like methods (|> was one of the proposals). In a recent discussion we agreed we might revisit that topic after we've addressed what's already linked to this Epic.


Update login page with new style

Update the login page with Tailwind CSS. Reorganize the DOM as necessary.

Resolved by #14.


[QnA Maker] Issue with recognizing emojis / emoticons

Problem description:
I would like to train my QnA Maker model, so that it correctly recognizes emojis (or group of emojis) and returns the relevant key which I will then handle further in my code. As a simple example I added following inputs and associated them with the QnA answer smalltalk.emoji.grin:
😀, :D and grinning face
This is how it looked like after I finished the training (notice that I can search the knowledge base using unicode emoji):

However when I tried to test the knowledge base, QnA did not recognize the 😀 and neither the :D:

I also tried to call the QnA Maker's Generate Answer API directly by passing the both raw and UTF encoded emoji, but that did not work neither:
{
  "question": "😀",
  "top": 3,
  "userId": "Default",
  "isTest": true
}

{
  "question": "\ud83d\ude00",
  "top": 3,
  "userId": "Default",
  "isTest": true
}

Response for both of the above scenarios:
{
  "answers": [
    {
      "questions": [],
      "answer": "No good match found in KB.",
      "score": 0.0,
      "id": -1,
      "metadata": []
    }
  ]
}

Question
How do I correctly train my QnA model so that it can correctly handle the emojis (both unicode and textual) or any other complex unicode characters? This seems to be supported by LUIS as it correctly categorizes the intent in case that I input emoji into it.

As you've discovered, QnAMaker doesn't know how to handle emojis coming in an activity from the bot. Therefore, you need to build in the functionality. This example demonstrates setting up via Node, however the implementation would essentially be the same for C#. There are nuget packages that can be installed, like Unicode.net. (I've purposely kept this demonstration simple. Alter as needed.)
For Node, you can download and install the NPM package node-emoji which has a number of nicely packaged methods. Once installed, add the following into your onTurn handler along with the necessary QnA bits. You can also setup to allow user's the send literal emoji's which QnA Maker can also match on (see pic below).
See inline comments for further explanation.
async onTurn(turnContext) {
    if (turnContext.activity.type === ActivityTypes.Message) {
        await turnContext.sendActivity(`Try sending ':heart:' or ':pizza:'`);

        // Strips out ":" from the user text to get the raw input
        let userText = turnContext.activity.text.replace(/:/gi, '');

        // Adds ":" to the new variable to compare if the original text input is an emoji
        if (':' + userText + ':' === turnContext.activity.text) {
            let emojiMsg = emoji.emojify(turnContext.activity.text);
            await turnContext.sendActivity(`Looks like I have that emoji! ${ emojiMsg }`);
            await turnContext.sendActivity(`Checking QnAMaker for a response to the image.`);

            // Perform a call to the QnA Maker service to retrieve matching Question and Answer pairs.
            const qnaResults = await this.qnaMaker.generateAnswer(emojiMsg);

            // If an answer was received from QnA Maker, send the answer back to the user.
            if (qnaResults[0]) {
                console.log('QNA Results: ', qnaResults[0].answer);

                // Assigns the emoji response and sends as an activity message to the user
                let emojiResponse = emoji.emojify(qnaResults[0].answer);
                await turnContext.sendActivity(emojiResponse);

            // If no answers were returned from QnA Maker, reply with help.
            } else {
                await turnContext.sendActivity('No QnA Maker answers were found. This example uses a QnA Maker Knowledge Base that focuses on smart light bulbs. To see QnA Maker in action, ask the bot questions like "Why won\'t it turn on?" or "I need help."');
            }
        } else {
            await turnContext.sendActivity(`You said: ${ turnContext.activity.text }`);
        }

    // Sends a quick greeting message to the user.
    // :heart: exists as an emoji but isn't in QnAMaker, so it responds "No answer".
    // :pizza: exists as an emoji and has a matching QnA pair and returns the :grinning: emoji (😀)
    // Because the user text in parsed and matched, simply typing "pizza" returns "No answer"
    } else if (turnContext.activity.type === ActivityTypes.ConversationUpdate &&
                turnContext.activity.recipient.id !== turnContext.activity.membersAdded[0].id) {
        await turnContext.sendActivity(`Try sending ':heart:' or ':pizza:'`);
}

I convert both :pizza: and "🍕" to "🍕" and always return "😀" . Because I parse the user text, if I simply type "pizza", nothing is returned. Without the parsing, "pizza" would match on :pizza: and return the second response.

The flow is far from perfect, but then that wasn't the point. Hope of help!