[SPARK-9788][MLlib] Fix LDA Binary Compatibility

Add “asymmetricDocConcentration” and revert docConcentration changes. If the (internal) doc concentration vector is a single value, “getDocConcentration" returns it. If it is a constant vector, getDocConcentration returns the first item, and fails otherwise.
Give LDAModel.gammaShape a default value in LDAModel concrete class constructors.

@jkbradley

Merged build triggered.

Merged build started.

Merged build finished. Test FAILed.

Test build #1422 has started for   PR 8077 at commit 9d6a71e.

reviewing now

Note (not requiring changes): I had meant for the default gammaShape to be defined in the abstract LDAModel, in order to improve (but not fix) binary incompatibility issues for anyone who extended LDAModel.  However, I just noticed that LDAModel has a private constructor, so we don't need to worry about binary incompatibility.  So feel free to arrange gammaShape however you like.  I think the current setup is fine.

Test build #1422 has finished for   PR 8077 at commit 9d6a71e.

This patch passes all tests.
This patch does not merge cleanly.
This patch adds no public classes.

This will need an update to PySpark as well.

Merged build triggered.

Merged build started.

LGTM pending tests

(Are you updating PySpark in a separate PR?)

Merged build finished. Test FAILed.

@jkbradley This PR doesn't need a PySpark update. Eventually, PythonMLLibAPI.scala will need to be updated to support asymmetric priors, hyperparam optimizations, and the predict methods. However, I think it might be better to hold off until the EM optimizer and Online optimizer have a consistent API.

True, it's outside this PR.  OK we'll see if tests will ever pass

Jenkins test this please

Merged build triggered.

Merged build started.

Test build #40494 has started for   PR 8077 at commit 6b07bc8.

Test build #40494 has finished for   PR 8077 at commit 6b07bc8.

This patch fails some tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Jenkins test this please

Merged build triggered.

Merged build started.

Test build #40496 has started for   PR 8077 at commit 6b07bc8.

Test build #40496 has finished for   PR 8077 at commit 6b07bc8.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Merging with master and branch-1.5


hyprtrails failing to build

my life ruined

Hyprland version?

seems to build for me, this might be that I forgot to add a 0.43.0 pin and there has been a breaking change since, try now

lets go it works now, thanks so much!


Needs testing !

We need to add more unit tests, basically test each features but also test the middleware "independently" & test the response.

Going to put masonite 3 and orm into production and going to use this package


Add support for

👋
I wanted to propose this minimal implementation, trying to keep to the spirit of Sergey, based loosely on the approach taken with Vue's <router-link>.
See https://router.vuejs.org/api/#router-link
I tried to also add some documentation and tests to explain why this would be useful. While the slots model works great for loads of cases, I think navigation is a major use case not currently well-served. I've been thinking of using Sergey as an introductory SSG with my design students, and active navigation states is usually the first pain point they run into when using plain old HTML.

[x] Adds class="active" on links to current page and parents
[x] Adds aria-current="page" on links to current page
[x] Configurable active class with --active-class or SERGEY_ACTIVE_CLASS
[x] Example site uses an example for its navigation
[x] New documentation page for links on example site
[x] Tests added and passing

If you like this idea and it's worth adding despite the additional complexity, I might recommend adding support similar to <router-link> for adding classes on an outer element kind of like:
<router-link tag="li" to="/foo">
  <a>/foo</a>
</router-link>

Known issue: The "Links" page on the documentation/example site uses Markdown. I spent some time tracking down why the current implementation is breaking fenced code blocks, but couldn't get anywhere. I'd prefer to keep the code examples directly in the markdown files, instead of using Github gists, but if that's a better solution for now, I'm all for it.

Hey @trys — I wanted to apologize for submitting all this as a pull request, and not raising a feature request for discussion instead. I got overly-excited by the idea itself, had some downtime from work and enjoyed the challenge of putting together this as a proof of concept for what I had in mind.
For now I'll leave this open in case you want to discuss the possibility of adding a feature like this. But of course, no hard feelings at all if this is simply out of scope for your vision of Sergey. I admire how focused of a tool you've put together.

@nevanscott My apologies - I didn't get an email for this, nor the open issues 😬 I had no idea it was here!
I'm pretty stacked right now, but I'll try and take a look this week. Once again, apologies for not replying sooner!

@trys No worries at all! Would love to have your feedback.

@nevanscott - I'm so, so, so, sorry for taking an age to look through this - it's mega. Thank you so much! Merging now 🎉

Nice! Glad this was useful. :)

On Aug 8, 2019, at 7:22 PM, Trys Mudford<EMAIL_ADDRESS>wrote:
@nevanscott https://github.com/nevanscott - I'm so, so, so, sorry for taking an age to look through this - it's mega. Thank you so much! Merging now 🎉
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/trys/sergey/pull/22?email_source=notifications&email_token=AAARZ2EZQMUZ5ESVTTHL2QTQDRI6JA5CNFSM4HVU3LOKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD34KK7Y#issuecomment-519611775, or mute the thread https://github.com/notifications/unsubscribe-auth/AAARZ2D53G6P3TFHXKBDZRLQDRI6JANCNFSM4HVU3LOA.


OutputCache

Is there a way to use OutputCache with the caching extension? Is OutputCache even in ASP.NET Core? With ASP.NET MVC, you could put attributes on controller action methods, and the result would be cached (in-proc by default).

Mr. Groves -
Yes, there is an output cache in core:
https://docs.microsoft.com/en-us/aspnet/core/performance/caching/response
I haven't used it yet, but assume it would use whatever Distributed Cache
you have configured.
-Jeff
On Wed, Aug 30, 2017 at 1:10 PM, Matthew D. Groves<EMAIL_ADDRESS>
wrote:

Is there a way to use OutputCache with the caching extension? Is
OutputCache even in ASP.NET Core? With ASP.NET MVC, you could put
attributes on controller action methods, and the result would be cached
(in-proc by default).
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/brantburnett/Couchbase.Extensions/issues/8, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAbuIMvLu8bFR5261WDHcpdtdyyAk6kDks5sdcHIgaJpZM4PH6Xf
.

That's the ResponseCache, which I believe just affects the HTTP headers, it doesn't actually store in cache. It might be the case that OutputCache was not created for ASP.NET Core; I can't find evidence to suggest otherwise.

@mgroves
I think you use it in combination with the Response Caching Middleware.  This sees the headers coming back from MVC and then performs caching based on the headers at the server side.

I followed the below steps according to that link, and ResponseCache doesn't seem to be putting anything in Couchbase. It's not clear to me if I'm doing something wrong or it's a bug.

Added MicrosoftAspNetCore.ResponseCaching (v1.1.2)
In Startup.cs, I added services.AddResponseCaching(); to ConfigureServices
In Startup.cs, I added app.UseResponseCaching(); to Configure
I added [ResponseCache(Duration = 10)] attribute to an action in HomeController

When I go to the HomeController action, the page loads and displays correctly, but nothing is cached into Couchbase.
I should also note that, otherwise, caching is working fine. I'm using IDistributedCache methods like GetString, SetString, Set<> and so on, and values set with those methods are showing up in Couchbase correctly.

@mgroves
Looking at the code for response caching in .NET Core, it appears that in-memory caching is the only option.
https://github.com/aspnet/ResponseCaching/blob/dev/src/Microsoft.AspNetCore.ResponseCaching/ResponseCachingMiddleware.cs#L40
It also doesn't appear to have an extension point to substitute other behavior, unless we replicate the very large amount of functionality in ResponseCacheMiddleware.  I think serializing CachedResponse would probably be a bit tricky, too.
Brant

I could create an ActionFilter pull request, would that be something you'd want in this project?

@mgroves
My concern would be getting something like that right.  There's a whole lot of complexity around what to cache and when, and how to vary it by headers and query params, caching redirects, etc.  That logic is already worked out in the ResponseCaching library of .NET Core, and replicating it correctly seems like it would be difficult and buggy.
Perhaps we should instead try to get ResponseCaching to add support for substituting an IDistributedCache?  Maybe file an issue or pull on that project?

Okay, just submitted an issue there - https://github.com/aspnet/ResponseCaching/issues/137


NIFI-2687: RPG Port ID was used instead of RPG ID

It caused "Error: Unable to find remote process group with id 'XXXX'" error with modifying the transmitting toggle switch of an Input or Output port.

Reviewing....

Thanks @ijokarumawak! This has been merged to master.


az webapp config ssl upload fails on MacOSX Catalina

This is autogenerated. Please review and update as needed.
Describe the bug
Command Name
az webapp config ssl upload
Errors:
[('PKCS12 routines', 'PKCS12_parse', 'mac verify failure')]
Traceback (most recent call last):
python3.7/site-packages/knack/cli.py, ln 206, in invoke
    cmd_result = self.invocation.execute(args)
cli/core/commands/__init__.py, ln 603, in execute
    raise ex
cli/core/commands/__init__.py, ln 661, in _run_jobs_serially
    results.append(self._run_job(expanded_arg, cmd_copy))
cli/core/commands/__init__.py, ln 654, in _run_job
    six.reraise(*sys.exc_info())
...
python3.7/site-packages/OpenSSL/crypto.py, ln 2996, in load_pkcs12
    _raise_current_error()
python3.7/site-packages/OpenSSL/_util.py, ln 54, in exception_from_error_queue
    raise exception_type(errors)
OpenSSL.crypto.Error: [('PKCS12 routines', 'PKCS12_parse', 'mac verify failure')]

To Reproduce:
Steps to reproduce the behavior. Note that argument values have been redacted, as they may contain sensitive information.

Put any pre-requisite steps here...
az webapp config ssl upload --name {} --resource-group {} --certificate-file {} --certificate-password {} --query {} --output {}

Expected Behavior
Environment Summary
Darwin-19.2.0-x86_64-i386-64bit
Python 3.7.5
Shell: bash

azure-cli 2.0.77

Additional Context

after upgrading to azure-cli 2.0.78 the issue is resolved.


Record upgrade tests for Snowflake

This enables upgrade tests in the provider as these had previously been disabled.
I've enabled the ones which work - the others seem to do implicit refreshes and fail to find the resources in the cloud.

Thanks!!


Got "64bit addressess not supported" when "make qemu CPUS=2"

Please answer these questions before submitting your issue. Thanks!
What version of Go are you using (go version)?
go1.14.7 linux/amd64
Does this issue reproduce with the latest release?
Yes, I also tried go1.15, which has the same problem
What operating system and processor architecture are you using (go env)?
Ubuntu 16.04.7 LTS, Linux kernel 4.15.0-112-generic
GOHOSTARCH="amd64"
GOHOSTOS="linux"
GOOS="linux"
What did you do?
If possible, provide a recipe for reproducing the error.
A complete runnable program is good.
A link on play.golang.org is best.
make qemu CPUS=2
What did you expect to see?
get into the Biscuit OS and be able to type "ls"
What did you see instead?
          BiscuitOS
      go version: go1.10.1

4763 MB of physical memory
CPUID: family: 6, model: 1a
sse3 true, ssse3 true, sse41 true, sse42 true, avx false
invariant TSC not supported
bmi1 false, bmi2 false
1GB pages not supported
No hardware performance monitoring
panic: 64bit addressess not supported
goroutine 1 [running]:
ahci.attach_ahci(0x8086, 0x2922, 0x2000)
/home/zym/src/biscuit/biscuit/src/ahci/ahci.go:94 +0x73a
pci.pci_attach(0x8086, 0x2922, 0x0, 0x4, 0x0)
/home/zym/src/biscuit/biscuit/src/pci/pci.go:221 +0xd2
pci.Pcibus_attach.func2(0x0, 0x4)
/home/zym/src/biscuit/biscuit/src/pci/pci.go:164 +0x9d
pci.Pcibus_attach()
/home/zym/src/biscuit/biscuit/src/pci/pci.go:179 +0x53
main.attach_devs(0x5a98e0)
/home/zym/src/biscuit/biscuit/src/kernel/main.go:952 +0x105
main.main()
/home/zym/src/biscuit/biscuit/src/kernel/main.go:1654 +0x1f7
exit with code<PHONE_NUMBER>000002 .
halting

Problem solved by upgrading to the latest version of Qemu.
$ qemu-system-x86_64 -version
QEMU emulator version 5.1.0


Custom route  problem

Environment
**Flutter version:0.17.3
Plugin version:  ^3.3.0+3
Android version:  none
iOS version:
Xcode version:
Device information:  iOS-all
Description
Expected behavior:
Current behavior:
Steps to reproduce
1.PageA to PageB ，
2.use custom pagerouter
3.pop pageB and drag pagA Scroll list hold it，when pageB closed， pageA touch even is invalid！。
class PageA extends StatefulWidget {
  @override
  _PageAState createState() => _PageAState();
}

class _PageAState extends State<PageA> {
  @override
  Widget build(BuildContext context) {
    return Scaffold(
      body: CustomScrollView(
        slivers: <Widget>[
          SliverList(
            delegate: SliverChildListDelegate([
              Text('a'),
              Text('a'),
              Text('a'),
              Text('a'),
              Text('a'),
              Text('a'),
              Text('a'),
              Text('a'),
              Text('a'),
              Text('a'),
              Text('a'),
              Text('a'),
              GestureDetector(
                onTap: () {
                  Navigator.pushNamed(context, 'test2');
                },
                child: Text('aaaaaaaaaaaaaaaaaaaaaaaa'),
              ),
            ]),
          )
        ],
      ),
    );
  }
}

class PageB extends StatefulWidget {
  @override
  _PageBState createState() => _PageBState();
}

class _PageBState extends State<PageB> {
  InAppWebViewController webView;

  @override
  Widget build(BuildContext context) {
    return Scaffold(
        appBar: AppBar(),
        body: Container(
          color: Colors.deepPurple,
          child: InAppWebView(
            // 初始化加载的url
            initialUrl: 'https://www.baidu.com',
            onWebViewCreated: (InAppWebViewController controller) {
              webView = controller;
            },
            onLoadStop: (InAppWebViewController controller, String url) {
              print('onPageFinished');
              setState(() {});
            },
          ),
        ));
  }

  @override
  void dispose() {
    super.dispose();
  }
}

class FadeRouteBuilder extends PageRouteBuilder {
  final Widget page;
  final int duration;

//you can set duration longer ，
  FadeRouteBuilder({this.page, this.duration = 1000})
      : super(
          transitionDuration: Duration(milliseconds: duration),
          //Page builder doesn't do anything special, just return the ui.page we were passed in.
          pageBuilder: (context, animation, secondaryAnimation) => page,
          //transitionsBuilder builds 2 nested transitions, one for transitionIn (animation), and one for transitionOut (secondaryAnimation)
          transitionsBuilder: (context, animation, secondaryAnimation, child) {
            return FadeTransition(
                //Transition from 0 - 1 when coming on the screen
                opacity: Tween<double>(begin: 0, end: 1).animate(animation),
                child: FadeTransition(
                  //Transition from 1 to 0 when leaving the screen
                  opacity: Tween<double>(begin: 1, end: 0)
                      .animate(secondaryAnimation),
                  child: child,
                ));
          },
        );
}

Sorry, I didn't understand what's the problem about the InAppWebView widget.
Is it related to your Page or the InAppWebView widget? Is there any error?

I tried to use a WebView and I had problems with it. maybe about dispose


ImportError if django 1.9 AppConfig is used for installed apps

if I add permission.autodiscover() to my urls.py, the following exception is thrown, if the Django 1.9 AppConfig ist used for my apps. If the .apps.ProjectAppConfig is removed, the exception does not occur.
INSTALLED_APPS = [
    ...
    'project_app.apps.ProjectAppConfig',  # Not working
    # 'project_app',  # Working
]

Traceback (most recent call last):
  File "/project/env/lib/python3.4/site-packages/django/utils/autoreload.py", line 226, in wrapper
    fn(*args, **kwargs)
  File "/project/env/lib/python3.4/site-packages/django/core/management/commands/runserver.py", line 116, in inner_run
    self.check(display_num_errors=True)
  File "/project/env/lib/python3.4/site-packages/django/core/management/base.py", line 426, in check
    include_deployment_checks=include_deployment_checks,
  File "/project/env/lib/python3.4/site-packages/django/core/checks/registry.py", line 75, in run_checks
    new_errors = check(app_configs=app_configs)
  File "/project/env/lib/python3.4/site-packages/django/core/checks/urls.py", line 10, in check_url_config
    return check_resolver(resolver)
  File "/project/env/lib/python3.4/site-packages/django/core/checks/urls.py", line 19, in check_resolver
    for pattern in resolver.url_patterns:
  File "/project/env/lib/python3.4/site-packages/django/utils/functional.py", line 33, in __get__
    res = instance.__dict__[self.name] = self.func(instance)
  File "/project/env/lib/python3.4/site-packages/django/core/urlresolvers.py", line 417, in url_patterns
    patterns = getattr(self.urlconf_module, "urlpatterns", self.urlconf_module)
  File "/project/env/lib/python3.4/site-packages/django/utils/functional.py", line 33, in __get__
    res = instance.__dict__[self.name] = self.func(instance)
  File "/project/env/lib/python3.4/site-packages/django/core/urlresolvers.py", line 410, in urlconf_module
    return import_module(self.urlconf_name)
  File "/project/env/lib/python3.4/importlib/__init__.py", line 109, in import_module
    return _bootstrap._gcd_import(name[level:], package, level)
  File "<frozen importlib._bootstrap>", line 2254, in _gcd_import
  File "<frozen importlib._bootstrap>", line 2237, in _find_and_load
  File "<frozen importlib._bootstrap>", line 2226, in _find_and_load_unlocked
  File "<frozen importlib._bootstrap>", line 1200, in _load_unlocked
  File "<frozen importlib._bootstrap>", line 1129, in _exec
  File "<frozen importlib._bootstrap>", line 1471, in exec_module
  File "<frozen importlib._bootstrap>", line 321, in _call_with_frames_removed
  File "/project/src/project/urls.py", line 21, in <module>
    permission.autodiscover()
  File "/project/env/lib/python3.4/site-packages/permission/utils/autodiscover.py", line 19, in autodiscover
    mod = import_module(app)
  File "/project/env/lib/python3.4/importlib/__init__.py", line 109, in import_module
    return _bootstrap._gcd_import(name[level:], package, level)
  File "<frozen importlib._bootstrap>", line 2254, in _gcd_import
  File "<frozen importlib._bootstrap>", line 2237, in _find_and_load
  File "<frozen importlib._bootstrap>", line 2221, in _find_and_load_unlocked
ImportError: No module named 'project.apps.ProjectConfig'; 'project.apps' is not a package

This hack fixes the error for now:
#/project/env/lib/python3.4/site-packages/permission/utils/autodiscover.py:18
    for app in settings.INSTALLED_APPS:
        if '.apps.' in app:
            app = app.split('.')[0]
        mod = import_module(app)

Maybe a better fix would be
#/project/env/lib/python3.4/site-packages/permission/utils/autodiscover.py:18
    for app in settings.INSTALLED_APPS:
        if '.' in app:
            mod = import_string(app)
        else:
            mod = import_module(app)

Aha, yeah the autodiscover feature was developed when there were not appconfig thing...
Probably there should be a way to use autodiscover with appconfig but for now, I don't know the way.
What happen if you don't use autodiscover feature and manually assign in models.py? I'm the one who made this but I know sometime these kind of auto feature makes things too complicated...

Maybe you could use django.utils.module_loading.autodiscover_modules for autodiscovering permissions. Maybe I can take a look at it in the next days.

django admin autodiscovery uses django.utils.module_loading.autodiscover_modules for the same purposes

More and more apps are using the AppConfig feature which will break if django-permission is used. Please add any of the stated solutions and create a new release as soon as possible. Thanks in advance.

I'm not directly impacted by this bug, but as the maintainer of django-dynamic-preferences, I was also impacted by this (we needed to autodiscover some modules in installed apps).
I never used django.utils.module_loading.autodiscover_modules, but we solved this issue by grabbing the app paths from django.apps.apps, as showed here:
from django.apps import apps
app_names = [app.name for app in apps.app_configs.values()]
for module in app_names:
    # your import logic

This way, you can get the real package path for each app (and not the AppConfig path declared in INSTALLED_APPS which break your import logic).
Just my 2 cts ;)

@giginet Do you have time to investigate nd fix this?

@JanMalte @vosi @EliotBerriot sorry for late. I take @EliotBerriot 's way and it fix the problem 👍


Miner Bug:  Hopper Planter Always light gray after use...

This is in:
MC 1.12.2 - Skyblock 4
When you make a bonsai hopper plot (the tier 2), it has no color, but once placed upon a chest it becomes "light gray"
This isn't much of a bug, but more so an inventory/storage stacking issue.

Light gray is the default color for bonsai pots.
There are no uncolored pots.


fix: pass reveal public key to SDK when updating DID

Hi,
I noticed that updating a DID doesn't work.
The reason is that the underlying SDK also expects the public key that needs to be revealed (update public key or recovery public key respectively).
https://github.com/decentralized-identity/ion-sdk/blob/a7603470b980688353eed03e1425382eb903bad8/lib/IonRequest.ts#L168-L177
I just added the missing lines in generateRequest() so that the required value is passed to the SDK.

@csuwildcat could you maybe have a look at this or notify the responsible person?

@nikolockenvitz will do this over the next few days, thank you for bringing this up!


DPF flux import bug with 2022R2

From Costas at Honeywell:
Running the code below using 2022R2 crashes the Python interpreter with the message that follows. This is run with Python 3.9.6 with the environment shown in the requirements.txt document on Windows 10 pro. ANSYS 2022R1 is also installed on that machine. The model is fairly complex with many 2D and 1D elements including FLUID116. The RTH file is run with an earlier version of ANSYS, 2020Rxx.
The same code runs fine in 2022R1. The only reason I am trying this in 2022R2 is because ANSYS suggested it as a way to improve performance which is poor with earlier versions (see attached e-mail chain). Can you or ANSYS explain what tests are run on PyAnsys prior to releasing it to customers? Specifically is the code tested on all element types (1D/2D/3D), models of various degree of complexity, etc.? The impression I got from ANSYS presentations is that PyAnsys is touted as production software but I seem to be encountering quite a lot of issues with it, especially DPF.
from ansys.dpf import post
from ansys.dpf import core
rstfile=r'C:\Users\THERMAL.rth'
res=post.load_solution(rstfile, physics_type='thermal')
flux=res.heat_flux(time_scoping=10)
nodes = flux.vector.get_scoping_at_field(0)
data = flux.vector.get_data_at_field(0)
Process finished with exit code -1073741819 (0xC0000005)
Attachments:
iCostas Attachments

Hi @agrishin,
I do not seem to have access to the attachments, nor to the requirements.txt. Would it be possible to share at least the requirements.txt?

Hi @agrishin,
I have tried replicating the issue but have not been able to. Would it be possible to have more information on the element types included in the model?
One remark though is that some package versions are not the right ones for Ansys R222. The compatibility table needs a little update, but using Ansys R222 would require ansys-grpc-dpf 0.5.2 (the latest patch for 222), as well as ansys-dpf-gate and ansys-dpf-gatebin 0.1.2 (same).


change labels for "disease" and "disorder"

OGMS takes two strings that are part of non-ontological discourse that have complicated but often interchangeable usage and imposes ontological commitments on them. This leads to a lot of confusion.
Names are important. I recommend changing to "pathological organism disposition" and "pathological material entity" or something like that.

The labels proposed by @cmungall look good to me. However, 'disease' and 'disorder' are commonly used terms in the biomedical areas. Do have any plan to add the 'disease' and 'disorder' as synonyms of "pathological organism disposition" and "pathological material entity"? not necessary exact synonym, might be narrow/broad/related synonym

I think if we change the labels, we definitely need to retain the previous labels as some type of synonym.

I agree with @scheuerm that OGMS not having the terms 'disease' or 'disorder' is a bit odd. But, IMHO, the benefits outweigh the cost.  For example, see the debate in COB about this. We can (of course) add synonyms for whichever labels we choose.
However, if OGMS is going to change its labels, MONDO and DO (and others) should change its labels in order to hopefully avoid confusion across Foundry.  I've submitted an issue for this on the MONDO tracker.

I am not opposed to adding "pathological organism disposition" and
"pathological material entity"  as skos:altLabel to the terms 'Disease' and
'Disorder' if it will help clarify the meaning.
cheers
Sivaram

Sivaram Arabandi, MD, MS
ONTOPRO
W:  http://ontopro.com/
Ph:<PHONE_NUMBER>
Li : https://www.linkedin.com/in/sivaramarabandi/
Think Semantics. Tame Silos.
On Wed, Mar 1, 2023 at 9:51 AM Bill Duncan @.***> wrote:

I agree with @scheuerm https://github.com/scheuerm that OGMS not having
the terms 'disease' or 'disorder' is a bit odd. But, IMHO, the benefits
outweigh the cost. For example, see the debate
https://github.com/OBOFoundry/COB/pull/226 in COB about this. We can
(of course) add synonyms for whichever labels we choose.
However, if OGMS is going to change its labels, MONDO and DO (and others)
should change its labels in order to hopefully avoid confusion across
Foundry. I've submitted an issue
https://github.com/monarch-initiative/mondo/issues/5998 for this on the
MONDO tracker.
—
Reply to this email directly, view it on GitHub
https://github.com/OGMS/ogms/issues/176#issuecomment-1450378430, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AB4D6F3RNZLYEMPV4LII5FLWZ5V67ANCNFSM6AAAAAAVGKQQ2I
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

Hi all,
Interesting discussion! I've been asked about this question just recently,
and been posted about this as an example of how important it is to
harmonize ontology and provide a clean, non-redundant and coherent
ontologies to the end user who don't usually build ontologies.
My suggestion: Replace the label of term "disorder" to "pathological
material entity" in OGMS and make 'disease or disorder' an alternative term
with COB ID in OGMS.
Reason: The BFO:style "disorder" is a very BFO-level philosophical term,
which elucidates the full ontological definition of disease. Disorder (as a
'pathological material entity'), but it does cause confusion for end users
who don't know the BFO ontological definition of disease, because as Chris
M. said, end users use disorder and disease exchangeably. The creation of
BFO: disorder in deed causes user's confusion.
I think the advantages of my suggestion are: 1. keeps the use of disease
and disorder in OGMS, and 2. maintains a consistency with COB.
Before making changes of the "disorder" in OGMS, we might need to double
think of the use of the label "pathological material entity" to avoid the
confusion by its face value. Can we use 'pathologically disordered material
entity" instead?
Thanks,,
Asiyah
On Wed, Mar 1, 2023 at 6:12 PM Sivaram Arabandi @.***>
wrote:

I am not opposed to adding "pathological organism disposition" and
"pathological material entity" as skos:altLabel to the terms 'Disease' and
'Disorder' if it will help clarify the meaning.
cheers
Sivaram

Sivaram Arabandi, MD, MS
ONTOPRO
W: http://ontopro.com/
Ph:<PHONE_NUMBER>
Li : https://www.linkedin.com/in/sivaramarabandi/
Think Semantics. Tame Silos.
On Wed, Mar 1, 2023 at 9:51 AM Bill Duncan @.***> wrote:

I agree with @scheuerm https://github.com/scheuerm that OGMS not
having
the terms 'disease' or 'disorder' is a bit odd. But, IMHO, the benefits
outweigh the cost. For example, see the debate
https://github.com/OBOFoundry/COB/pull/226 in COB about this. We can
(of course) add synonyms for whichever labels we choose.
However, if OGMS is going to change its labels, MONDO and DO (and others)
should change its labels in order to hopefully avoid confusion across
Foundry. I've submitted an issue
https://github.com/monarch-initiative/mondo/issues/5998 for this on
the
MONDO tracker.
—
Reply to this email directly, view it on GitHub
https://github.com/OGMS/ogms/issues/176#issuecomment-1450378430, or
unsubscribe
<
https://github.com/notifications/unsubscribe-auth/AB4D6F3RNZLYEMPV4LII5FLWZ5V67ANCNFSM6AAAAAAVGKQQ2I
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

—
Reply to this email directly, view it on GitHub
https://github.com/OGMS/ogms/issues/176#issuecomment-1451009105, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/ACCPEPK75UYMSXQSXHCWXRLWZ7JUNANCNFSM6AAAAAAVGKQQ2I
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

I support the change, with the old labels being added as alternative terms, and other labels as alternative terms, as desired.

To summary, this is my suggestion:

change "disorder" to "pathologically disordered material entity" and keep "disorder" as alternative terms with detailed explanation of the change.
keep "disease" and add "disease or disorder" as alternative term, and add explanation as well.
Do you agree with above, Alan?

@linikujp I'm not thrilled with the "disease or disorder" as an alternative label, but wouldn't oppose it, push come to shove. The reason is that we don't generally recommend disjunctive classes in ontologies, and the label suggests that. But it's only a label and as @wdduncan  says, it's the definition that matters more.
I think there's objection to keeping disease as the primary label, so I'm more inclined to support @cmungall's suggestion for pathological organism disposition, or something similar, with disease as an alternative label. Disease as an alternative label for disorder also seems appropriate, given what we've been told about usage in the wild.

"pathological organism disposition" will then become a term that is not going to be easily understand by non-BFO people, although I think it is maybe a broader term than disease, can a symptom become a "pathological organism disposition"?

Schulz uses "pathological disposition", which is shorter. Symptom is another of those words that's used in several senses. For example, the usage "symptom: runny nose" could mean the disposition to have a runny nose, or a type of realization of the disposition. It's also used in the disorder sense, as in "symptom: rash", which could also mean a tendency to develop rashes, i.e. part of disease course in which a rash disorder is created. Language is not the ontologist's friend in this domain.

@linikujp Also, regarding not being understood, as with all labels we need to be training ontology users to read the definition to understand the term. Applications should be designed to make the definition hard to avoid. Also, there's no suggestion that the term "disease course" be changed, and there ought to be an axiom on disease/pathological disposition: realized in only (part of some disease course). Maybe that would help.

Maybe I'm mistaken. There is the suggestion of "pathological process", though I don't think that means the same thing as disease course, as the latter is the "The totality of all processes through which a given disease instance is realized." whereas I think a pathological process would be a part of that. But maybe the axiom would be realized in only pathological process. But then "pathological process" is currently defined as "A bodily process that is clinically abnormal.", and such things are not only realizations of dispositions, but also processes associated with injuries. It looks like changing the labels won't be a surgical change but will require rewording of other definitions and possibly adding new classes.

I agree that both human and machine need to understand the definitions. But only hope that trained ontology users to read the definition won't be a way for ontology to go far. I think the labels need to be somehow touching the reality and intuitive, not everyone is Aristotle.
As you mentioned @alanruttenberg and @zhengj2007 also mentioned, if labels is being changed, the definitions and axioms need to be changed and make it work.
Symptom and sign are difficult to deal with ... I think end users want to use "running nose" and relate it to things it is supposed to relate to. Perhaps we could put them all as "pathological disposition", and the disease ontology, symptom ontology can use the term as their upper term. COB can then set up some relations such as characteristics to relate a disease with symptoms.  Would that be a possible path?

While I agree that changing 'disorder' to 'pathologically disordered material entity' or 'pathological material entity' is an improvement useful to disambiguate the label and add face value, I am not sure that changing 'disease' to 'pathological organism disposition' or 'pathological disposition' helps much, and might rather confuse users, who would see familiar disease names as subclasses. We could simply call it 'disease disposition' to retain the face value of the word disease.

@addiehl I like that idea.

Support the "disease disposition" idea too!

Thanks for the suggest @addiehl! In the context of OGMS, I like the label disease disposition better than pathological disposition too.

Remember it’s really important to be consistent with actual usage. Everyone
will assume you mean predisposition
On Tue, Mar 7, 2023 at 7:45 AM Bill Duncan @.***> wrote:

Thanks for the suggest @addiehl https://github.com/addiehl! In the
context of OGMS, I like the label disease disposition better than pathological
disposition too.
—
Reply to this email directly, view it on GitHub
https://github.com/OGMS/ogms/issues/176#issuecomment-1458394438, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAAMMOPTWGMHPLL2NH4ZQRDW25JYLANCNFSM6AAAAAAVGKQQ2I
.
You are receiving this because you were mentioned.Message ID:
@.***>

Do we have a definition or elucidation of 'pathological'?
In the context of OGMS, 'clinically abnormal' was the phrase, not 'pathological'
From the paper:
'Disorder' =def. – "A causally relatively isolated combination of physical components that is (a) clinically abnormal and (b) maximal, in the sense that it is not a part of some larger such combination."
'Pathological Process' =def. – "A bodily process that is a manifestation of a disorder."
"When we say that some bodily feature of an organism is clinically abnormal, this signifies that it: (1) is not part of the life plan for an organism of the relevant type (unlike aging or pregnancy), (2) is causally linked to an elevated risk either of pain or other feelings of illness, or of death or dysfunction, and (3) is such that the elevated risk exceeds a certain threshold level"
Although it would smack of circularity, could add synomyms to disorder of "clinically abnormal body part" and "clinically abnormal anatomical entity".

@cmungall  it is better to add disposition to disease, so that it is friendly and clear to the end user - who are unfamiliar with the BFO approach. Although we want them to read the definition, a lot of them still have their mental definition when they read labels.
Support @hoganwr's point on elucidation of "pathological".

The general principle is:

if the concept corresponds to the same concept used by an ordinary
scientist or clinician, use the standard label
if you are creating a novel abstraction, don't use a label that confuses
with an existing concept

On Wed, Mar 8, 2023 at 8:15 AM Alexander Diehl @.***>
wrote:

@cmungall https://github.com/cmungall Keep in mind that 'pathological
material entity' does not match usage in the medical literature either as
far as I know. We are in the process of making some compromises in regards
to labels to use in OGMS and possibly other ontologies. I am not completely
thrilled by 'disease disposition' in part for the reason you suggest, but
the label does at least include the word disease and imply that it is a
type of disposition, which is not wrong.
—
Reply to this email directly, view it on GitHub
https://github.com/OGMS/ogms/issues/176#issuecomment-1460439703, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAAMMOJI3MWIJRUF5X55A5DW3CWAVANCNFSM6AAAAAAVGKQQ2I
.
You are receiving this because you were mentioned.Message ID:
@.***>

@alanruttenberg I don't agree that "For example, the usage "symptom: runny nose" could mean the disposition to have a runny nose, or a type of realization of the disposition."  A runny nose is a realization.

It seems like we are approaching a consensus on this.  So the proposal would be to:

Change OGMS:disorder => OGMS:pathologically disordered material entity, with disorder as a synonym and =def. – "A causally relatively isolated combination of physical components that is (a) clinically abnormal and (b) maximal, in the sense that it is not a part of some larger such combination."
Change OGMS:disease => OGMS:disease disposition, with synonym disease (but not disorder) and =def. - "A disposition (i) to undergo pathological processes that (ii) exists in an organism because of one or more disorders in that organism."
Add OGMS: disease predisposition with =def. something like "a disposition to form a pathologically disordered material entity" and perhaps "disorder predisposition" as a synonym.
Define OGMS:pathological that is consistent with the clinically abnormal elucidation


[Bug] Performance degrades for large DOM trees

Describe the bug
There's a lot of DOM processing happening which makes editing slow for large,nested DOM trees.
Try with example:
https://www.google.com/search?sca_esv=f34a7ccbd9a4492c&sca_upv=1&q=sport+climbing+combined+olympics&oi=ddle&ct=348045702&hl=en&sa=X&ved=0ahUKEwi4_Pys7OWHAxWqFlkFHVwPFvQQPQgC&biw=1362&bih=823&dpr=1

This is isolated down to the user of getDeepElement and how when using in tandem with shadowDom it can have a large effect


UVI Request

--- UVI JSON ---
{
  "vendor_name": "Linux",
  "product_name": "Kernel",
  "product_version": "versions from  to before v4.14.253",
  "vulnerability_type": "unspecified",
  "affected_component": "unspecified",
  "attack_vector": "unspecified",
  "impact": "unspecified",
  "credit": "",
  "references": [
    "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=232ed9752510de4436468b653d145565669c8498"
  ],
  "extended_references": [
    {
      "type": "commit",
      "value": "232ed9752510de4436468b653d145565669c8498",
      "note": "fixed"
    }
  ],
  "reporter": "joshbressers",
  "reporter_id": 1692786,
  "notes": "",
  "description": "ocfs2: mount fails with buffer overflow in strlen\n\nThis is an automated ID intended to aid in discovery of potential security vulnerabilities. The actual impact and attack plausibility have not yet been proven.\nThis ID is fixed in Linux Kernel version v4.14.253 by commit 232ed9752510de4436468b653d145565669c8498. For more details please see the references link."
}
--- UVI JSON ---

This issue has been assigned UVI-2021-1001959


Extend CLI with --publish flag option configurable

Is your feature request related to a problem? Please describe.
As we see the publish: true is enabled in CLI (https://github.com/storyblok/field-plugin/blob/main/packages/cli/src/commands/deploy/helper.ts#L83C7-L83C21), this it is not possible to push an update of the Plugin in draft level, thus it gets instantly published, which may not align with the way teams may use it in CI automations.
Describe the solution you'd like
It should be possible to define --publish false (though by default it is enabled, that is fine), so the release process would be 2 steps:

CI automation pushes new version of plugin after monorepo project tag creation in "draft" level
Release manager or QA makes sure the plugin is as expected
Manually publish a certain version to go live.

Describe alternatives you've considered
No alternatives, we have to be sure the version we push is the one we want to appear on production, thus there is no doublecheck step or other flows possible.
Additional context
Severity: minor.

Hi @edvinasjurele, thanks for your feature request! We've implemented a small improvement in the latest version of @storyblok/field-plugin-cli (v1.4.0).
The deploy command now includes a --no-publish option, which applies when updating an existing field plugin. While the initial creation still auto-publishes the plugin, you can now save changes without publishing by running:
npx @storyblok/field-plugin-cli@latest deploy --no-publish

Feel free to reach out if you have any questions. I'm happy to help!


MINOR: improve consoleProducer option description

kafka-console-producer.sh provides users some options to configure. But some of them are ambiguous to users to map the option to a specific producer config. Ex: timeout option, is actually configuring the linger.ms config in producer. And max-partition-memory-bytes option is actually the batch.size config in producer, etc.)
In this PR, I tried to map the option to a producer config, if not clear. And also side fix some expected wrong types, and update the retries defaults.
Committer Checklist (excluded from commit message)

[ ] Verify design and implementation
[ ] Verify test coverage and CI build status
[ ] Verify documentation (including upgrade notes)

@hachikuji , could you help review this PR? Thanks.

@mimaison , improve the console producer option descriptions. I think it's good to merge this PR before you started your KIP-810. Thanks.

@mimaison , Thanks for the comment. I've updated the PR. Thanks.


Problems with SVGR

Description
Since we started to use @svgr/webpack to load .svg files and import them in our components which are then imported in the component library we've been having the following issue on build:
See our docs page for more info on this error: https://gatsby.dev/debug-html

  101 |
two session labels

  102 |       <SessionCardPlaceholder status={SESSION_STATUSES.draft} mdxType="SessionCardPlaceholder">
> 103 |         <SessionBadge status={SESSION_STATUSES.draft} badgesAreCombined limitToShow={2} content={[{
      |         ^
  104 |               kind: SESSION_BADGE_KIND.label,
  105 |               display: 'DS'
  106 |             }, {

  WebpackError: Minified React error #130; visit https://reactjs.org/docs/error-decoder.html?invariant=130&args[]=undefined&args[]= for the full message or use the non-minified dev environment for full er
  rors and additional helpful warnings.

Adding 'gatsby-plugin-svgr to our gatsby-config plugins means the build runs successfully but the build is not correct. None of the navigation buttons in the left sidebar are clickable, and if I navigate directly to a URL, the components are not rendering correctly.
I've tried adding the following to my gatsby-node:
exports.onCreateWebpackConfig = ({ actions }) => {
  actions.setWebpackConfig({
    module: {
      rules: [
        {
          test: /\.svg$/,
          use: {
            loader: '@svgr/webpack',
          },
        },
      ],
    },
    resolve: {
      // ⚠ Note the '..' in the path because the docz gatsby project
      // lives in the `.docz` directory
      modules: [path.resolve(__dirname, '../src'), 'node_modules'],
      alias: {
        components: path.resolve('../src/components'),
        api: path.resolve('../src/api'),
        actions: path.resolve('../src/actions'),
        constants: path.resolve('../src/constants'),
        utils: path.resolve('../src/utils'),
        DEPRECATED_stylus: path.resolve('../DEPRECATED_stylus/styles'),
        src: path.resolve('../src'),
        selectors: path.resolve('../src/selectors'),
        'react-assets': path.resolve('../react-assets'),
      },
    },
  });
};

but still no joy.
Additional context
This is taking place inside the main repo with code in src and a root webpack.config.js and babelrc, the docz files build into ./docs. I've seen that can cause problems in other areas.
An example svg being loaded in a component in our ./src. react-assets is being aliased as you can see above:
import { ReactComponent as SearchSvg } from 'react-assets/images/search.svg';

Any help much appreciated

@Phil-Barber try to use https://github.com/doczjs/docz/issues/1184#issuecomment-543737651, helps for me

I no longer work on this repo so will be unable to confirm if that fixes things. I think we can close this since it's likely stale anyway


Update README.md

Portfolio Author

Portfolio Link?

GitHub Link:

Tech Stack

Hey, @sidharthviz thanks for your PR. Please fix the table lines accordingly.
Sure, Thanks for the review


Lookup Fields in SharePoint Online not Working Correctly

Recently my SharePoint Online lookup fields have been defaulting to the first value in the list no matter what I select.  Example.  I upload a document, then go to set some lookup fields on that document.  When I pull up the list of values, no matter which value I select SharePoint will select the first and auto-save.  I can then change that value to something else, then click that value or select it from the list again and it will save correctly.  Basically 3 clicks for what should take 1.  We had this problem in 6 different tenants, then one day it was fixed, then the next day it was broken again.
Category

[ ] Question
[ ] Typo
[x] Bug
[ ] Additional article idea

Expected or Desired Behavior
SharePoint should allow you to select any value from the lookup field value list and auto-save with the correctly selected value.
Observed Behavior
SharePoint will always select the first value in the lookup field value list, regardless of what you selected.
Steps to Reproduce

Add a generic list.  Populate it with 3 or 4 items (titles only is fine).
Add a new lookup column to a document library.  Configure that lookup column to point to the generic list you created in step 1.
Upload a document to the library.
Click details on the document if the details/property pane is not yet open.  Attempt to set the value for the lookup column to any value EXCEPT the first value in the list.
BUG : this is where SharePoint will automatically use the first value in the lookup list, regardless of the value you selected.
SharePoint will autosave with the incorrect first value from the list.

Now here’s the work around I’ve been telling my clients.

Select the value you want again.  SharePoint won’t do a thing.
Select the value you want again or just click the lookup field drop-down since the value is already selected from step 7.
SharePoint will engage auto-save and save the correct value from the list.

Thanks for your contribution! Sharing is caring.

As of 715 CST this morning the issue has been fixed.  I am reluctant to close this issue out though b/c last time a fix was rolled out, it was broken 24-36 hours later.  I will gladly close this out in a couple of days if the fix persists.  Mods please feel free to close out if you feel differently.

Since nothing is broken ATM, let's close it and feel free to create a new issue if it comes up again...


[video_player] Support for Embedded Captions

Use case
For accessibility, video_player should be able to support Embedded/Closed Captioning, specifically the CEA-608/EIA-608/CTA-708.

Proposal
At current implementation, video_player does not support or detect CEA-608 captions. Testing out with ExoPlayer's demo application at 2.18.0 the captions are getting recognized and toggleable.
Changing the implementation to use StyledPlayerView works well. An example package would be video_360 with some modifications to not display in a 360 video format.

This is found in Flutter 3.1, video_player 2.4.6. Platform: Android. Haven't tested with iOS yet.


Feature Request: Binding to node property

Description:
This answer explains the difference between HTML Property and Attribute: http://stackoverflow.com/questions/6003819/properties-and-attributes-in-html#answer-6004028
I am using WebComponents made with Polymer (own created by me, and third parties like paper-elements by Polymer Project) and in both my components and those of third parties I need two-way data binding to some node properties instead of HTML Attribute.
Versions affected:
Maybe future version?
Platforms affected:
All?
Reproduction:
Any by the moment
Code:
I can do the two-way data binding to HTML attribute with:
<some-component some-attribute={{name}}></some-component>
I propose do the two-way data binding on node property too.
Vue.js allow do using a modifier, and I propose use similar syntax:
<some-component some-attribute.prop="{{name}}></some-component>"
Note: Writting this issue I've noticed this can be done with some syntax that only transform HTML attribute to property, and observe changes in both attribute and property and update the other when some change. Then, combine this with ractive.js two-way data binding.
Any idea to do this?

I'm not sure if I follow. Can you give a more complete example if what you're trying to achieve? Like which properties are you trying to bind to? Also for the sake of other who aren't familiar with Polymer and/or Vue.js features.

Of course.
When I select an HTML tag via JavaScript and store it in variable, I can access a lot of properties of the elements, that can be (or not) reflect to an HTML Attribute.
I'm trying bind some of this properties data in model.
In my example, I've a WebCompont custom tag <address-selector>, that is composed by 4 inputs (actually paper-input) for retrieving the street, country, city and postal code.
This HTML tag render 4 inputs:
<address-selector></address-selector>
And for access data of these inputs, I do:
document.querySelector('address-selector').country //Get "ES" document.querySelector('address-selector').city = "Valencia" //Set the city to Valencia
This properties, are NOT reflected to HTML attribute, thats mean I can access it only accessing the property of HTMLElement object. This is explained here.
My problem is i'm trying to bind these properties values to the model instance using Ractive ViewModel, but with Ractive, I can only access to HTML attributes and not to HTMLElement object properties (or I know how can I do it).

Perhaps I'm misunderstanding, but is there a way to observe changes to those properties? Or were you after twoway binding?
As it stands in 0.9, if the webcomponent fires some sort of update event, you could do a bit of manual binding e.g. <address-selector on-change="@context.set({'.city', @node.city, '.state': @node.state })" />.

Somebody with more custom element experience would have to chime in to verify, but I think we could mostly handle this sort of thing with a proxy. When ractive sees a custom element, it could wrap it in a proxy when attaching to the dom. Then when checking for a binding, if it detects a custom element with a property that could be bound rather than an attribute, it could add a listener to a hook on the relevant property set.
A cursory glance at caniuse shows that proxies are reasonably well supported sans IE, and waaay more supported than native custom elements. The webcomponent polyfills appear to only cover IE11, so it looks like that would be the only one left out in the cold completely.


upgrade to .net 5.0 breaks because of System.Reactive

when upgrading my project to .net 5.0 I encountered an issue with the new version of System.Reactive.
System.TypeLoadException: 'Could not load type 'System.Reactive.Linq.DispatcherObservable' from assembly 'System.Reactive, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=94bc3704cddfc263'.'

I have exactly the same problem.

I have updated the library to net6 https://github.com/dojo90/NLogViewer/pull/82


API key not working

i've created a bat file and set environment variable, but i'm still getting the error :

my bat file looks like this
set REPLICATE_API_TOKEN=r8_123456keynumber
.\python_embeded\python.exe -s ComfyUI\main.py --windows-standalone-build

(i'm running a comfyui portable build)
the environment variable is set at the global level, as comfyui portable doesn't have a venv.  any suggestions how to resolve?

SOLVED – First a Personal Note
I resolved this issue, thanks to a helpful Discord community member who tipped me in the right direction to a solution.  Unfortunately, Replicate's official documentation is not only lacking but also contains errors. Despite opening multiple GitHub issues, Discord queries, and support tickets over the past two months, I’ve received no responses from their support staff…. Just like all the other folks that asked the same question. It's frustrating that customers must solve problems caused by poor documentation without any assistance from the company.
If you're facing similar issues, don’t rely on Replicate’s official channels. Turn to the community for help—they’re the real MVPs.
Steps to Resolve Replicate API Token Issues in ComfyUI (Portable Mode)

Set the Windows Environment Variable:
o	Add the REPLICATE_API_TOKEN as a global Windows environment variable.
o	Note: This global variable is not automatically picked up by ComfyUI in portable mode.
Test the Environment Variable with curl:
o	Use a simple curl command in the terminal to confirm the variable is being picked up and the API token works:
cmd
Copy code
curl -X GET "https://api.replicate.com/v1/account" -H "Authorization: Bearer %REPLICATE_API_TOKEN%"
Verify run_gpu.bat Picks Up the Variable:
o	Add a debug statement in ComfyUI/main.py to confirm the environment variable is accessible:
python
Copy code
print(f"REPLICATE_API_TOKEN: {os.getenv('REPLICATE_API_TOKEN')}")
Hard Code the API Key in node.py:
o	Modify the replicate.Client initialization in ComfyUI/custom_nodes/comfyui-replicate/node.py:
python
Copy code
replicate = Client(
headers={
"User-Agent": "comfyui-replicate/1.0.1",
"Authorization": f"Token {os.getenv('REPLICATE_API_TOKEN')}"
}
)

Important Notes
•	Updates May Overwrite Changes:
o	If you update either ComfyUI or its custom nodes, the changes in main.py and node.py will be overwritten. You’ll need to reapply these fixes after updates.


fix: flip condition to disable public access by default

By submitting a PR to this repository, you agree to the terms within the Code of Conduct. Please see the contributing guidelines for how to create and submit a high-quality PR for this repo.
Description

Describe the purpose of this PR along with any background information and the impacts of the proposed change. For the benefit of the community, please do not assume prior context.
Provide details that support your chosen implementation, including: breaking changes, alternatives considered, changes to the API, etc.

References

Include any links supporting this change such as a:

GitHub Issue/PR number addressed or fixed
StackOverflow post
Support forum thread
Related pull requests/issues from other repos

If there are no references, simply delete this section.

Testing

Describe how this can be tested by reviewers. Be specific about anything not tested and reasons why. If this library has unit and/or integration testing, tests should be added for new functionality and existing tests should complete without errors.
Please include any manual steps for testing end-to-end or functionality not covered by unit/integration tests.
Also include details of the environment this PR was developed in (language/platform/browser version).

[ ] This change adds test coverage for new/changed/fixed functionality

Checklist

[ ] I have added documentation for new/changed functionality in this PR or in /docs
[ ] All active GitHub checks for tests, formatting, and security are passing
[ ] The correct base branch is being used, if not master

:tada: This PR is included in version 1.0.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Ode example

Modified the ODESolver module. Less epochs are required to achieve the same loss as the "ode" branch.
Added two examples to test the ODESolver class on: Lorenz63 and SEIR.

Not ready for merge yet. "torchts/nn/models/ode.py" still needs to be cleaned.

I need help, I'm not sure how to fix the following error in my Jupyter notebooks:
RuntimeError: Trying to backward through the graph a second time, but the saved intermediate results have already been freed. Specify retain_graph=True when calling backward the first time.

Ready for code review!

This branch is ready for code review

@klane In my latest commit, I was able to reproduce the results in the "SEIR model with ODESolver.ipynb" notebook you added into your #57 branch. Since my modified class is compatible with both of our examples, would you be willing to close your pull request (#57) and review/merge this instead? Thanks.

Thank you for your contribution @amartyamukherjee. We can certainly use this PR in favor of #57. Would you be able to add a few tests as well?

@klane Thanks for letting me know. I just added some test cases. Hope it helps.

@klane Happy holidays! Could I get an update on the code review process for this pull request?

Thank you for reminding me @amartyamukherjee. I should be able to take a look this weekend. @droten can you review as well?

@klane @droten @Rui1521 @yuqirose
Hello, could I get an update on the code review for this PR? Thanks

@amartyamukherjee I looked over the code, but I would like one of the other reviewers to have a look since I was not part of the model development.

@klane Got it, thanks for the update!

@klane Professor Rose Yu has let me know through email that this PR is ready to be merged. Could you merge this please?

@klane I was wondering if there's a reason why this isn't merged yet? Thanks

No reason @amartyamukherjee. I have just been trying to fix a few other things and have not gotten to it quite yet. I am going to make some small changes to ensure this is compatible with #190 before merging.


changed all name from PhoneAuth to GymFlow

changed PhoneAuth -> GymFlow, and also changed the tab bar to be more seamless with the UI, and fixed ID icon


[stable/ambassador] - Changing the var podLabels to extraLabels to use in Pods and Deployments

Signed-off-by: Thiago Dias<EMAIL_ADDRESS>What this PR does / why we need it:
The same way we can add new labels into the Pods resource I'm suggesting here to make usage of the same "additional" or "extra" labels and use them into the Deployment resource also
I believe other users are trying to track the labels in order to have cost report or maybe some Open Policy Rules where they want to keep a standard in their labels names and values.
Which issue this PR fixes
Special notes for your reviewer:
Checklist
[Place an '[x]' (no spaces) in all applicable fields. Please remove unrelated fields.]

[X] DCO signed
[X] Chart Version bumped
[X] Variables are documented in the README.md
[X] Title of the PR starts with chart name (e.g. [stable/mychartname])

/assign @lukeshu

/ok-to-test

/assign

/lgtm

/retest

/retest

/retest

/retest


GKE install - role names incorrect

In the GKE install guide, the role names listed in the section about granting GCP IAM roles didn't work in the gcloud CLI, and it was hard to find them in the Google IAM UI as well.
The roles listed were:
project/viewer
kubernetes-engine/admin
service-account/user

Here's a gcloud command that I think corresponds to the intent of this document and did seem to work (at least no errors in role names), so it would be good to check the role names and correct them if you agree:
gcloud projects add-iam-policy-binding myprojectname --member<EMAIL_ADDRESS>\
        --role roles/viewer --role roles/container.admin --role roles/iam.serviceAccountUser

The Rancher UI v2.1.4 seems to have the correct role names, including one extra one - so the docs can be updated based on source code.
String from UI when you do Add Cluster:

These IAM roles are required: Compute Viewer (roles/compute.viewer), (Project) Viewer (roles/viewer), Kubernetes Engine Admin (roles/container.admin), Service Account User (roles/iam.serviceAccountUser).

Updated the command above.


Feature | Landing page

Using this portfolio video as a reference point, build a landing page for our app - Figuringout.life
Reference: https://youtu.be/FTH6Dn3AyIQ?si=2sxai20i67MjHIax
For now, add the page as a new route /landing
Once done, share a PR and attach a video recording of your output.

Hey, I got a doubt... the Landing Page is going to be a hook for news users or for dev helping on the project?

New users

This has been open for a long time. If no one else picks it by the weekend, I'll pick it up


Refactor redisgraph.js to Typescript

Refactor redisgraph.js to Typescript
Issue Ref: https://github.com/RedisGraph/redisgraph.js/issues/5
I was very surprised to see Redis wasn't using Typescript, it's rare to see new libraries built using CommonJS syntax.

👏 👏 👏 👏

I'll be sending more PR's once this is merged

@gkorland would you prefer just adding the Typescript types instead of the entire code being refactored?

@DenisCarriere I would prefer not to switch to TypeScript, if we need any special things that will help you TypeScript consume the client please feel free to send another PR

looks like another one for definitely typed. It's a shame cause I can see they're already getting type errors that you've probably fixed in your refactoring eg https://github.com/RedisGraph/redisgraph.js/issues/19

Thanks, @DenisCarriere.
We decided not to refactor our current JS client to TypeScript.
If you like, you can fork and modify it to a TypeScript client. When your work is done, we will be happy to add the reference to your repo.

Just found this redisgraph and this lib and was excited to start using it. Well, fired it up and went  yarn add --dev @types/redisgraph.js and to my suprise there were no types there. I would tend to agree with the above, this is a fairly new project so I just expected it to be compatible with modern mainstream technologies. To be honest I'm a bit disappointed, now instead of being able to code away on a cool redisgraph project, I'm stuck to solve the typing problem myself which will seriously slow me down :-/.
For reference this was written 2016 and today I guess most people just expect any serious library to just work for typescript: https://staltz.com/all-js-libraries-should-be-authored-in-typescript.html

Btw, forking a separate typescript client is probably not a good idea. There are no specific typescript libraries, there are only javascript libraries which provides typescript annotations. If this project does not want to use typescript annotations internally, then it should provide them externally on definetely typed which will then end up published as @types/redisgraph.js.

Anything on approving this?

@jdgamble555 RedisGraph support was moved to node-redis see: https://github.com/redis/node-redis


Make code work on no_std

We want to try to use this filter in the rust firmware we are writing for slimevr. Having it working on #![no_std] and ideally even without alloc would be awesome.

so, my code doesn't allocate, and the only use of std should be easily replaced with core. However, the code that autocxx generates may be a different story. I can't tell whether it would also just be fine with core or not. Am checking if there's a way to put it into a no-std mode or if we need to submit a patch.

yeah, linking to libc/++ would be a nono here. Does the original C code use standard library stuff?

Found out autocxx actually has an option to disable all the usually helpful codegen, so that's even less of an issue than i originally thought.
However, cxx, even, if we remove the bits about unique_ptr and string and such still wants the c++ stdlib parts that are equivalent to core (i.e. language support for placement new, type traits) to enforce its safety invariants.
This is fine if you've built a version of the c++ stdlib for your target (especially if you have a toolchain to go with it). I'm not sure there's a good way to integrate that into cargo atm, though.
GNU's libstdc++ seems to be "yeah you build this at the same time as the compiler" but they do explicitly support freestanding c++. Maybe there's a way to build it on its own, idk.
LLVM's libcxx/libc++ has flags to disable parts of the stdlib, and an ongoing patch for c++23's freestanding definition. (current version here: https://reviews.llvm.org/D140691, previous discussion here: https://reviews.llvm.org/D135911) I've not looked very closely at what the current flags would let us disable, so maybe it's not necessary.
I think it would be really cool if we could build libc++ as a crate, enable lto, the whole nine yards. But it's somewhat moot for this crate since y'all are porting vqf to rust anyway.
I might still investigate anyway. would be neat if libc++ compile times aren't hell.


fix(app-shell): delete protocols across both protocol storages

Closes RQA-1600

Overview
Removes protocol files from both versions of the app to prevent protocol re-migration upon navigation to the ProtocolDashboard. This is part of the pre-parity stop-gap work for the app and will be removed after parity.
Current Behavior
https://github.com/Opentrons/opentrons/assets/64858653/e8dc4c75-3c90-4448-b9d0-e76a364f9960
Fixed Behavior
https://github.com/Opentrons/opentrons/assets/64858653/2fa0a088-05ba-478c-b92c-972ad409f150

Test Plan

From the app, delete any protocol that exists within the ~/Library/Application Support/Opentrons/protocols and protocols_v7.0-supported directories.
Navigate away from ProtocolDashboard and return. Note that the protocol is now properly deleted.

Changelog

Add support for deleting protocols from the old protocols directory if they exist.

Risk assessment

low

it works-ish, but if I have both 7.0 and 6.3 apps open, deleting requires me to navigate off the protocol cards list for 7.0? It works fine if i have just 7.0 or 6.3 open individually. And 6.3 works if i have both open at the same time. IDK if its also just my dev env being laggy.

Hm, interesting. Thanks for catching that. Yes, I didn't account for the case where if a protocol didn't exist on the OT-2, then the re-render wouldn't happen. This should fix it.


Missing name for new org using REST API

Description
Using the REST API, it is not possible to set the "name" attribute for a new organization. It will be set to default value "string".
How to reproduce:

have an admin account

Use the swagger API at https://try.gitea.io/api/swagger#/admin/adminCreateOrg to generate a request for a new organization (replace with non-demo-system)

fill in values of the payload
secondary bug: leave field "user" as default value "string" otherwise you get an exception that the user already exists

add user credentials to CURL call for gitea account

run command

a new organization is created, but the name field is set to value "string"

Gitea Version
1.18.0
Can you reproduce the bug on the Gitea demo site?
No
Log Gist
No response
Screenshots
No response
Git Version
No response
Operating System
No response
How are you running Gitea?
Docker environment
Database
MySQL

Could you please show me your request parameters? I guess you might have mixed up the two "username"s.

Gitea version: 1.18.3
Can no longer reproduce the issue myself.
It would help the understanding of the API if the documentation references "username" in the payload as "the name of the new organisation".
Closing issue.


fix: update utils

Please ensure your pull request adheres to the following guidelines:

[ ] make sure to link the related issues in this description
[ ] when merging / squashing, make sure the fixed issue references are visible in the commits, for easy compilation of release notes

Related Issues
Thanks for contributing!

:tada: This PR is included in version 1.32.15 :tada:
The release is available on:

v1.32.15
GitHub release

Your semantic-release bot :package::rocket:


Timer or Clock running slower then real time when Screen is off !

I was trying to create e timer in flutter app !
the problem is ... when screen is off the clock run slow !  I found .... It was about 8 minute in real clock  but in clock in flutter app around 1.45 minute !
but when screen is on, the timer works well!
i have used TimerService from 'dart:async'
here is s sample code
`
import 'dart:async';
import 'package:flutter/material.dart';
void main() {
final timerService = TimerService();
runApp(
TimerServiceProvider( // provide timer service to all widgets of your app
service: timerService,
child: MyApp(),
),
);
}
class TimerService extends ChangeNotifier {
Stopwatch _watch;
Timer _timer;
Duration get currentDuration => _currentDuration;
Duration _currentDuration = Duration.zero;
bool get isRunning => _timer != null;
TimerService() {
_watch = Stopwatch();
}
void _onTick(Timer timer) {
_currentDuration = _watch.elapsed;
// notify all listening widgets
notifyListeners();

}
void start() {
if (_timer != null) return;
_timer = Timer.periodic(Duration(seconds: 1), _onTick);
_watch.start();

notifyListeners();

}
void stop() {
_timer?.cancel();
_timer = null;
_watch.stop();
_currentDuration = _watch.elapsed;
notifyListeners();

}
void reset() {
stop();
_watch.reset();
_currentDuration = Duration.zero;
notifyListeners();

}
static TimerService of(BuildContext context) {
var provider = context.inheritFromWidgetOfExactType(TimerServiceProvider) as TimerServiceProvider;
return provider.service;
}
}
class TimerServiceProvider extends InheritedWidget {
const TimerServiceProvider({Key key, this.service, Widget child}) : super(key: key, child: child);
final TimerService service;
@override
bool updateShouldNotify(TimerServiceProvider old) => service != old.service;
}
class MyApp extends StatelessWidget {
@override
Widget build(BuildContext context) {
return MaterialApp(
title: 'Service Demo',
home: MyHomePage(),
);
}
}
class MyHomePage extends StatefulWidget {
@override
_MyHomePageState createState() => _MyHomePageState();
}
class _MyHomePageState extends State {
@override
Widget build(BuildContext context) {
var timerService = TimerService.of(context);
return Scaffold(
appBar: AppBar(),
body: Center(
child: AnimatedBuilder(
animation: timerService, // listen to ChangeNotifier
builder: (context, child) {
// this part is rebuilt whenever notifyListeners() is called
return Column(
mainAxisAlignment: MainAxisAlignment.center,
children: [
Text('Elapsed: ${timerService.currentDuration}'),
RaisedButton(
onPressed: !timerService.isRunning ? timerService.start : timerService.stop,
child: Text(!timerService.isRunning ? 'Start' : 'Stop'),
),
RaisedButton(
onPressed: timerService.reset,
child: Text('Reset'),
)
],
);
},
),
),
);
}
}
`

This work is being tracked in a few places.  See metabug https://github.com/flutter/flutter/issues/32164.
https://stackoverflow.com/questions/41924890/how-do-i-run-code-in-the-background-even-with-the-screen-off

Thanks !
Checking those :)


TypeError when calling Array.prototype.find on HTMLAllCollection

The shimmed version of Array.prototype.find raises a TypeError when called on an HTMLAllCollection.
This is happening in v54.0.2840.71 of Chrome.
Here is a codepen that reproduces this bug in Chrome: http://codepen.io/pifantastic/pen/vyLxGq
Array.prototype.find.call(document.all, (item, idx) => console.log)
// Uncaught TypeError: Cannot call method on [object HTMLAllCollection](…)

document.all is HIGHLY deprecated, and should never be used - try document.querySelectorAll('*') instead, if you really want that.
document.all is a special case as the only falsy object in all of JS and browsers, and there's not a reliable way for me to detect it - but it's been a bad practice for over a decade to use it.

@ljharb Yep. We don't actually use it. Apparently a lot of browser extensions do though :(
We reported this due to a big spike in errors in our error reporting service. I understand if you're not interested in fixing it at the es6-shim level. We can find a workaround on our side.

@aaron-stripe i'd love to fix it if there's a proper way to do it, but document.all is a pretty horrifically bad thing to have explicit support for :-/
The codepen is helpful - can you point me to some libraries that are trying to pass document.all into Array.prototype.find? The latter is new enough that these libs should be PR-able to do the right thing instead.

@ljharb unfortunately I don't know what library is responsible. From our end we can't see much, and our best guess is that it's a browser extension that is doing something on each page load. I can tell you that we first saw it happening ~ Nov 9, 2016 6:37:08 PM UTC. I will definitely post more details if I can figure out how to get them.

If someone interested, VueJS Devtools extension for Chrome causes this error too. But I don't think that a lot of @aaron-stripe users have devtools installed.

@tzurbaev amazing! The timing on this lines up pretty well, it's possible that VueJS Devtools are causing the issue I'm seeing. I just opened a PR with a fix.

@aaron-stripe since that PR is merged, let's give it a few days to land. If the errors don't subside, I'll write an awful hack to make this work here.

I ended up writing the awful hack. The next release will include this fix.

@ljharb thanks :)


Replace whitelist and blacklist terms

Terms blacklist and whitelist are metaphoric (not descriptive) and have racial connotations.
Let's use deny and allow instead.

Docs updated: https://github.com/devopsfaith/krakend-documentation/pull/82/commits/0f73291414a6c52ef5e40b7672923126081c5646#diff-3738c68375993b92287517d6768302d6

done at v2 branch. waiting for the final release to close this


docs(README.md): add service table entry for Partner Center Sell service

PR summary

PR Checklist
Please make sure that your PR fulfills the following requirements:

[x] The commit message follows the Angular Commit Message Guidelines.
[ ] Tests for the changes have been added (for bug fixes / features)
[x] Docs have been added / updated (for bug fixes / features)

Current vs new behavior

Does this PR introduce a breaking change?

[ ] Yes
[x] No

Other information

:tada: This PR is included in version 0.68.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


CSD multitaper: should we keep single tapers ?

Dear all,
I have a question regarding the computation of the CSD using multitapers.
The def _csd_from_mt seems to return the average CSD across tapers.
However, as far as I understand the methods (see Mitra and Pesaran, 2009) the PSD is computed by averaging the power estimates computed for each taper (eq. 6 and 7).
Questions:

Do you think that the two approaches are equivalent ?

If yes, forget this issue.

If not, I would suggest to keep the single tapers complex CSD. However, the PSD should be computed for each taper and then averaged.

I am asking this, because the correct implementation of the PSD using mtm could be relevant also for source estimated using DICS and mtm.
Thanks a lot

@wmvanvliet can you comment?

Sorry, I know nothing about multi-tapers. I always use wavelets to compute de CSD.

the diag of the CSD matrix is the PSD. So averaging the CSDs is compatible with averaging of the PSDs as done with MT. Makes sense?

Well, however, the CSD is complex-valued, whereas the PSD is not. So averaging the CSD across tapers and then take the power should be different from taking the PSD and then avereage the power.....
In practice, a colleague of mine has now tried the two approaches for the calculcation of source-power using DICS with multitapers and she finds practically identical (at the 10^-20 resolution).
So, this may not be an issue at all. In fact, I think I remember Fieldtrip does the same thing as MNE

the diag is real valued:
In [13]: np.diag(csd_mt.get_data(index=0)).imag
Out[13]:
array([0., 0., 0., 0., 0., 0., 0., 0., 0., 0., 0., 0., 0., 0., 0., 0., 0.,
   0., 0., 0., 0., 0., 0., 0., 0., 0., 0., 0., 0., 0., 0., 0., 0., 0.,

   0., 0., 0., 0., 0., 0., 0., 0., 0., 0., 0., 0., 0., 0., 0., 0., 0.,

   0., 0., 0., 0., 0., 0., 0., 0., 0., 0., 0., 0., 0., 0., 0., 0., 0.,

   0., 0., 0., 0., 0., 0., 0., 0., 0., 0., 0., 0., 0., 0., 0., 0., 0.,

   0., 0., 0., 0., 0., 0., 0., 0., 0., 0., 0., 0., 0., 0., 0., 0., 0.,

   0., 0., 0., 0., 0., 0., 0., 0., 0., 0., 0., 0., 0., 0., 0., 0., 0.,

   0., 0., 0., 0., 0., 0., 0., 0., 0., 0., 0., 0., 0., 0., 0., 0., 0.,

   0., 0., 0., 0., 0., 0., 0., 0., 0., 0., 0., 0., 0., 0., 0., 0., 0.,

   0., 0., 0., 0., 0., 0., 0., 0., 0., 0., 0., 0., 0., 0., 0., 0., 0.,

   0., 0., 0., 0., 0., 0., 0., 0., 0., 0., 0., 0., 0., 0., 0., 0., 0.,

   0., 0., 0., 0., 0., 0., 0., 0., 0., 0., 0., 0., 0., 0., 0., 0.])

Ahhh of course ! Super Alex ! Thanks
Could it still be an issue for the calculation of spectral coherence based on multitapers using mne.connectivity.spectral_connectivity since the off-diagonal terms are used ?
I guess that Denis and Martin have been checking this already...

I think we are good as it is.

Great! I think we can close this issue.

please close


[std.regex] More compact ThompsonMatcher struct

Surprisingly non-zero performance gain. It's also very dependent on the exact layout.

This is a new benchmark, the one that runs engine in line by line fashion instead of all at once.


bigquery: allow AVRO format

RE: #1379
This unifies the areas where we accept a format of CSV, JSON, or AVRO.
Also, table.import accepts a shorthand options.format in place of options.sourceFormat.
And yes, it replaces var that with var this because it's not 2009.

Changes Unknown when pulling 1980eaa78c42ce2651a354b0fa00a578dc8ab097 on stephenplusplus:spp--1379 into ** on GoogleCloudPlatform:master**.


New condition callback: "valuesChanged"

Adding new callbacks.condition.valuesChanged which is a more aggressive form of condition.changed that takes into account changes to currently-being-edited textboxes.
This condition returns true if any of the values of the fields have changed. This differs from the 'changed' condition callback which waits for field  onChange events and those don't get fired until the current input loses
focus. Using this condition callback allows you to use an interval-based trigger to autosave while a user is still typing in a textbox, without calling unnecessary save() events if the values haven't changed.

Thanks for this, Phil. It seems like this should actually be the default behavior of changedInputs, since essentially it should return anything with a changed value regardless of focus. When I get some time I'll see how difficult it would be to refactor that.

agreed - I wished this was the default (though it'd be good to have the current functionality as an option also). after playing with this more, my implementation has problems as-is whenever there are multiple form elements with autosave - somehow the states are being intermingled.

Merged here: https://github.com/nervetattoo/jquery-autosave/pull/9


Display Album Art in Discord instead of iTunes logo

Instead of just displaying the iTunes logo as the Discord status, it would be neet if the Album Artwork could be displayed.

Duplicate of #74, #24, #22, #18

Duplicate of #74, #24, #22, #18


SPP-10025-update-confluence-documentation

Description
This PR updates the confluence page to include guidance on how to install poetry and instructions on basic usage.
This PR also updates the README.md file to reflect the changes to the confluence file.
Code has not been commented and documentation has not been written because it is not necessary for this PR.
Type of change
Please delete options that are not relevant.

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[x] Technical Enhancements

Checklist:
If any of these are not completed, please explain why in the notes.
Definition of Done
Code and merges

[ ] Code to be commented on where applicable
[ ] Documentation updated where required
[x] Have considered non-functional requirements such as Security, Performance, Scalability, and Fault Tolerance
[x] I have linted the code

Testing

[x] All levels of acceptance test are passing (automated, integration, manual, accessibility, etc.)
[x] I have run the behave command to check the selenium behaviour tests pass locally
[x] Acceptance criteria met

Other Checks

[x] I have performed a self-review of my own code
[x] I have checked for spelling errors
[ ] I have commented on my code, particularly in hard-to-understand areas
[x] My changes don't break anything unexpected
[x] I have checked and updated the security.txt file where required
[x] Up to date with the main branch

DEPLOY_URL=https://d2smjabvhlou30.cloudfront.net/
cloudfront_id=E345E1H6DGCSUY

DEPLOY_URL=https://d2smjabvhlou30.cloudfront.net/
cloudfront_id=E345E1H6DGCSUY


can instructcodet5p-16b module run in Cpu

hello,I run instructcodet5p-16b module in CPU ,this is the code
from transformers import AutoModelForSeq2SeqLM, AutoTokenizer
import torch

checkpoint = "Salesforce/instructcodet5p-16b"
device = "cpu" # for GPU usage or "cpu" for CPU usage

tokenizer = AutoTokenizer.from_pretrained(checkpoint)
model = AutoModelForSeq2SeqLM.from_pretrained(checkpoint,
                                              torch_dtype=torch.float16,
                                              low_cpu_mem_usage=True,
                                              trust_remote_code=True).to(device)

encoding = tokenizer("def print_hello_world():", return_tensors="pt").to(device)
encoding['decoder_input_ids'] = encoding['input_ids'].clone()
outputs = model.generate(**encoding, max_length=15,pad_token_id=tokenizer.eos_token_id)
print(tokenizer.decode(outputs[0], skip_special_tokens=True))

but it comeout with an error

I want to know whether this model can support cpu and how to fix the error

I can run in CPU now ,but it takes huge ram.  The ram up to 64.9G（the machine ram total 83.5G）


About the input Matrix A.

In this train model ,the train data's adj is 0 or 1.
But my adj is the N*N similarity matrix which is filled within [0,1].
Should I change the method of normalize_adj ?
Looking forward for you reply.

This should work fine! If your adjacency matrix is already normalized (e.g. all rows sum to 1), then you might just want to skip the re-normalization altogether.

It's very nice of your so rapidly reply.
Your paper is very nice!!
Thank you very much.


Update UITransactionDlg.cpp

This fixes the NPC icons being scattered around the 12 pages.
And not being able to purchase some of them in the selling group list.
Description
This fixes the following issue/ticket:
https://github.com/ko4life-net/ko/issues/203
💔Thank you!

PS/NOTE: Although this fixes npc selling icons I want this to be double tested and checked thoroughly, I don't feel okay with the loops especially if end user ends up selling an item slot that he didn't intend to sell which is a big disaster lol.

Merged in here: https://github.com/ko4life-net/ko/pull/212
because the last push from @UTengine broke the PR, so I had to cherry-pick and separate commits.


Fixes 140: Create LICENSE

https://issues.redhat.com/browse/HMSCONTENT-140

Built and pushed image for 6dbcce2440f3b91efdf4af3614e225a5dd162315

Its already there! (I checked).  I had held off adding it to the backend until i got some feedback from the insights platform, and they finally ended up suggesting this license as a base recommendation


Disable installation of Python legacy code + merged devel branch - [merged]

In GitLab by @cmastalli on Aug 29, 2019, 16:46
Merges topic/release -> cpp_devel

In GitLab by @cmastalli on Aug 29, 2019, 16:47
added 1 commit
b1247760 - [format] Formatted jump and salto examples
Compare with previous version

In GitLab by @cmastalli on Aug 29, 2019, 16:47
enabled an automatic merge when the pipeline for b1247760fb1bdf2e48cd3032e98b835d0bdef6f0 succeeds

In GitLab by @cmastalli on Aug 29, 2019, 17:01
merged

In GitLab by @cmastalli on Aug 29, 2019, 17:01
mentioned in commit 40c3b126a996cd09810c7095fd39727735c2393f


value::operator= does not allow for navigation

The current implementation of value::operator= first destroys the current value and then assigns the new value.
This breaks cases in which you want to descend iteratively down an object hiearchy, as in the following example:
for (auto k : paths) // paths is an iterator of keys
{
    if (branchV.is<picojson::null>()
        || !branchV.is<picojson::object>())
    {
        throw JSONFieldConversionException("JSON value is null or not an object");
    }

    const picojson::value::object & obj = branchV.get<picojson::object>();
    const auto & it = obj.find(k);
    if (it == obj.end())
    {
            throw JSONFieldConversionException("Cannot find element \"" + k + "\" in JSON object");
    }

    branchV = it->second; // this breaks
}

The last statement breaks because the assignment first destroys the current value, which ends up invalidating the iterator.

Thank you for reporting the issue with details.  It is evident that we should fix the implementation.

Thanks for replying, Kazuho.
I think the fix is easy; the affected code is:
inline value& value::operator=(const value& x) {
if (this != &x) {
this->~value();
new (this) value(x);
}
return *this;
}
The fix would be to save the old value to a temporary variable, do the assignment, and only then delete the temporary variable.

@GabrieleGiuseppini Thank you for the suggestion.
I have created the PR above to fix the issue in an efficient exception-safe way.  Would you mind checking if it fixes your problem?

I've tested it and it works perfectly!!! Thanks Kazuho!
When will it be released?

Thank you for checking.  I've just merged the PR to master.  Please wait for a day or so if you want me to tag a release.


Issue with migration

Issue description
Migrating to the new network, Firefly is stuck transferring my funds on the Migrate Your funds page, I hit the button to begin the migration, but it's not going anywhere, had been already 40 minutes and the Migrating funds icov is just turning constantly but I don't get the message that is completed, it seems stuck and I'm worries funds are lost in limbo...
Wallet version
Migrating from Trinity 1.6.2 to Firefly

wallet version (version number, commit, or branch):

System specification
What is your operating system?
Windows
Is it a repeatable issue?
stuck in migrating funds, nothing happens
Steps To reproduce the issue
Explain how the maintainer can reproduce the issue.

Begin migration, stuck at the Migrate your funds page when I hit begin transfer

Expected behaviour
Migration to be completed in few minutes, but it has been more then 40 mins and it's still  not completed
Actual behaviour
Describe what actually happens.
Errors
Paste any errors that you see from the Error Log in the Firefly menu or share screenshots of the issue.

Had the same issue, did you resolve it @LV1830 ? My firefly crashed and I had to close it, after restart the funds show to be migrated on the tangle explorer but no account with the new private key....
Are they gone forever? Lost in Limbo? :(


How to pause/resume on Listener ?

Can you please share a code snippet how to invoke the pause( )/resume( ) on the listener instead on a consumer as advised in spring-kafka reference doc as it is not always thread-safe.
I tried injecting or Autowiring the listener in the kafka-consumer but it lead to below cyclic error
The dependencies of some of the beans in the application context form a cycle: because
┌─────┐
|  myListener defined in class path resource [no/demo/services/configuration/KafkaConfiguration.class]
↑     ↓
|  myMessageConsumer (field org.springframework.kafka.listener.KafkaMessageListenerContainer no.demo.services.MyMessageConsumer.myListener)
└─────┘

Please don't use GitHub issues to ask questions; use Stack Overflow or Gitter for questions; issues are for bug reports or new feature requests.
See Pausing/Resuming Listener Containers.

Thanks for this. It was helpful.  It would be great if we can add a code example to the docs also (https://docs.spring.io/spring-kafka/reference/html/_reference.html#pause-resume). There is a different pause() method in the KafkaConsumer API and the doc was a bit ambiguous if it was referring to the "Consumer" object or the Container object.


[WIP][web]Static viewer converter for mitmweb

This PR is trying to add a static viewer converter, which can convert the dumped flows file into a group of static file, so that we could view the flows without backend server support.
This is about the first step, copying the resource files to a destination path. Also modifying index.html a bit, so we can have the interface by opening this html file.
If I understand the thing correctly, the next step is about converting the flows file into a bunch of json files in certain structure, so that our frontend could fetch the flow information from those local files.
However, there are two troubles here as far as I can see:

The fetch api we used in StaticBackend does not support the file:/// protocol, ref: https://github.com/github/fetch/pull/92, I tried XMLHttpRequest too, but it only works in Firefox, Chrome prevents us to fetch from local file. We need to change the design of StaticBackend, maybe importing the json files directly from our js code.
Since we will mimic the API calls in a folder structure of local files, updatesStoreFromUrl and updateUrlFromStore can not work as excepted, we need to find some workarounds for them.

The fetch api we used in StaticBackend does not support the file:/// protocol, ref:

Doesn't matter for the final use case. For testing we can just start a webserver (python3 -m http.server or devd .), ultimately those files would be uploaded to our testing server anyways.

Since we will mimic the API calls in a folder structure of local files, updatesStoreFromUrl and updateUrlFromStore can not work as excepted, we need to find some workarounds for them.

Good catch. AFAIK they currently work on the location hash though, so this should just work. 😃
Other than that, this is going in the right direction. Let's continue with the flows! :)

If there is anything that I'm not satisfied with this implementation yet, that should be the speed. We are doing a lot of IO operations here, basically creating a mass of static files, so it is kind of slow... It takes over 30s to process a flows file which is only 2MB on my computer. How could we improve this?
I will write the tests for this addon once we nail down the design of it.


Requirements: html2text in Readme?

This is super minor, but should html2text be listed in the Readme as a requirement? It's used by tracker_consumer  (from todo.mail.consumers import tracker_consumer as shown here).

Thanks, I'll look into it eventually. I don't use that feature in todo, so haven't come across this.

It's already / has always been listed as a dependency. It should have been installed automatically when you installed todo.
Closing, but let me know if there was another reason it didn't get installed for you. Maybe you weren't using Pipenv? I don't really accommodate other dependency management systems, but I would entertain the possibility if people had strong opinions on this.


Nuke: settings for reformat node in CreateWriteRender node

Brief description
Reformat node can be altered in creator settings.
Description
We are supporting reformat knob configurations at creator plugin settings. Since we needed to refectory the way settings are working with knob configurations we are now able to do per subset overrides. Pre nodes were added to all creators plugins in settings so the studio can add some other nodes before a write node with defined knobs - also with ability to format templated values (this needs to be enhanced for custom key inputs in future PR)
Additional info
We needed to unify the way nuke knobs are defined in settings, so all knob configurations are now using only one template schema. This will allow for imageio driven node overrides with subset filter.
Known issue
Since project anatomy was refactored now we have broken backwards compatibility of anatomy data. The way to workaround is to open the project anatomy settings in older version, screengrab settings in "project_anatomy/imageio/nuke/nodes/requiredNodes" particular Knobs are what we are interested in. Then open settings in this PR and see that original values had disappear (schemas had changed). Now you need to add manually those screengrabed values.
Testing notes:
General behaviour

Before you check out this PR save the anatomy info (look to Known issue)
Checkout to this PR and add the saved knob settings
Save the settings nad open Nuke in some project's task
Create Write render/prerender/still
all should look as you would expect from settings

ImageIO Plugin node overrides

add some node override to project_anatomy/imageio/nuke/nodes/overrideNodes
example here:

should result in

Works as described. I tested Numbers, Booleans and Hexa.


arch-riscv: Fix incorrect vector slide instructions and statically filter redundant uops

This PR fixed incorrect vector slide instructions mentioned in #1667.
And statically filter redundant uops for vslideup.vi/vslidedown.vi/vslide1up.vx /vsilde1down.vx/vfslide1up.vf/vfslide1down.vf instructions to improve performance.
Change-Id: I1ba36f216f0bb55372206a94b7f8108acc674f5a

@saul44203 could you take a look at this? I think you're our resident RVV expert :)

@5265325 Hello, thank you for your contribution. Could you give an update on the status of this PR on your end?

@saul44203 when you get a chance can you re-review this?


Add functionality to change tracker status.

Add functionality to allow users with role at least ROLE_QA make trackers active and inactive.

Closed by 92e3b59c02916402b1651881c89b1f0bb36ae6e4