[Bug]: Unresponsive Light Node on two Hue Hubs

Node-Red-Contrib-Huemagic-Fork Version
4.2.6
Node JS Version
14.17.1
NPM Version
8.19.2
Node-Red Version
3.0.2
Operating System
MacOS
What happened?
HueMagic works well for about 48 hours after the Hue Hub is rebooted.
After an
About 48 hours after a reboot I can set a Scene using the Scene Node of a specific hue bulb, but Hue Light node no longer works.
Once the issue starts…

The Hue Light node no longer updates,
The Hue Light node if invoked will show a message instead of state - next time this occurs I’ll capture it ‘ I think it is “configuring” but will need to confirm.
The issue is consistent on Both Hue Hubs.
The issue is resolved after a hard reboot of the Hue Hubs
While the Light node stalls, the Scene node still works

I can work around this by forcing a reboot of the hubs at night during the night
I will grab screen shots next time.
How to reproduce?
Run Hue Magic for 48 hours against 2 hue hubs
Expected behavior:
Both Scene and Light nodes should work
Light node should show current state.
Additional comments?
Additional comments here, if any.
Relevant log output
No response

The message I see when this happens, for me it's on the second event - even with the example flow - is "executing command" which takes a long time before it eventually clears, sometimes hours. While this status us under the node, all further messages are queued.  Restarting Nodered clears this "executing command" tag on the node. Only one message can be sent, after which it's locked into "executing command" status again.
Tested and it happens in named, and in universal mode, however in universal mode you don't see the "executing command" status.
Tested and it happens with both colour and temperature controllable white. It also happens with dimmable but fixed-K white.
It seems unrelated to the "not established a connection yet" type messages in nodered's log when we query too fast, careful testing with a 3 minute wait still causes it.
After number of hours (which i have not yet been able to quantify) the status returns to normal and one queued message is allowed through, after which its back to "executing command".
In my case I have a motion sensor and use it to manually set time-off period depending on a few other factors, the result being, to my family the lights look like they are turning on and off all the time by themselves, as if a ghost is operating them.
The only real difference I have is Apple Homekit and potentially using the Bayonet not the ES type of globe, should these be factors.
To check the Apple Homekit in a preliminary manner, I just fully deleted my home in both hue and homekit and did a full setup. The problem on my crude n=1 test of this is adding homekit cause the problem to start.

.


Clarify generate_targets_metadata()

Fixes issue #: N/A
Description of the changes being introduced by the pull request:

Improve documentation for generate_targets_metadata(), in the docstring and code comments, to make the use_existing_fileinfo and write_consistent_targets arguments, and their interactions, clearer.
Fix generate_targets_metadata() so that both use_existing_fileinfo and write_consistent_fileinfo can be used together, as required by Warehouse for PEP 458

Please verify and check that the pull request fulfills the following
requirements:

[x] The code follows the Code Style Guidelines
[ ] Tests have been added for the bug fix or new feature
[x] Docs have been added for the bug fix or new feature

@lukpueh already resolved this issue at the right level by modifying _generate_and_write_metadata() to call generate_targets_metadats() with an appropriate value for write_consistent_targets based on the values of consistent_snapshot and use_existing_fileinfo in b9891e171bde7626e3218b4e2c3674f447a0b980
Apologies for the noise. I will close this PR and include the first patch in a later PR.


CacheAdapter type is not exported

import type { CacheAdapter } from '@farfetched/core'

Complains:
Module '"@farfetched/core"' declares 'CacheAdapter' locally, but it is not exported.(2459)

I understand that TypeScript could infer type from createCacheAdapter function, but there are cases, when it is required to define return type for function, for example, eslint rule explicit-function-return-type or explicit-module-boundary-types.
In that case user have to write ad hoc solution like
function redisCache(options: { maxAge: number }): ReturnType<typeof createCacheAdapter>

or define own type like
type CacheAdapter = ReturnType<typeof createCacheAdapter>
function redisCache(options: { maxAge: number }): CacheAdapter

Both looks ugly IMO, while library could just export this type, with zero extra cost.

Thanks for report 🫶 done in https://github.com/igorkamyshev/farfetched/commit/528416b906094788a4b17cf3a389b1bee991d434, will be released in 0.8.11


[REG2.072] Unique does not work with private members

dransic reported this on 2017-01-07T14:08:13Z
Transfered from https://issues.dlang.org/show_bug.cgi?id=17065
CC List

code (@MartinNowak)
petar.p.kirov

Description
This code doesn't compile anymore:

---
import std.typecons : Unique;

struct Foo
{
    private int i;
}

void main()
{
    Unique!Foo foo = new Foo(1);
    foo.i = 2;  // Error: no property 'i' for type 'Unique!(Foo)'
}
---

It compiled before https://github.com/dlang/phobos/pull/4763 was merged. But the new implementation uses Proxy, which is a template mixin that is instantiated from std.typecons itself.

If this behaviour is intended, the doc should state it.

!!!There are attachements in the bugzilla issue that have not been copied over!!!

dransic commented on 2017-01-07T22:04:11Z
(In reply to greenify from comment #1)
> > If this behaviour is intended, the doc should state it.
>
> This should definitely have gotten a proper changelog entry (and deprecation
> warning).
> However, I am not really convinced that it should be noted in the
> documentation that access to private member variables isn't supported as
> this is the way visibility is supposed to work in D. Did anything lead you
> to this assumption or was it just by chance that accessing `private`
> variables worked and you didn't realize until the hole was fixed?

Private members are supposed to be accessible in the module where the type is declared (module-level encapsulation). A type constructor like `Unique` should return a type with the same access behavior. RefCounted works as I expect (but maybe I have wrong expectations...):

---
import std.typecons : RefCounted;

struct Foo
{
    private int i;
}

void main()
{
    RefCounted!Foo foo = Foo(1);
    foo.i = 2;  // OK
}
---

b2.temp commented on 2017-01-07T23:10:07Z
(In reply to dransic from comment #2)
> Private members are supposed to be accessible in the module where the type
> is declared (module-level encapsulation).
> [...]
> ---

There's a bigger underlying problem. Clearly something is broken by the change but the change doesn't work because Proxy uses __traits() and __traits() has a limitation related to the protection attributes. I don't know if you've followed the NG discussions last months but there's been several topics about this. A semantic change is even planned for the next 6 months (see the recent announce about H1)

That being said I don't suggest to wait the semantic change to happen. I just come because this __traits() thing has been a personal concern.

dransic commented on 2017-01-07T23:49:34Z
(In reply to b2.temp from comment #3)
> (In reply to dransic from comment #2)
> > Private members are supposed to be accessible in the module where the type
> > is declared (module-level encapsulation).
> > [...]
> > ---
>
> There's a bigger underlying problem. Clearly something is broken by the
> change but the change doesn't work because Proxy uses __traits() and
> __traits() has a limitation related to the protection attributes. I don't
> know if you've followed the NG discussions last months but there's been
> several topics about this. A semantic change is even planned for the next 6
> months (see the recent announce about H1)
>
> That being said I don't suggest to wait the semantic change to happen. I
> just come because this __traits() thing has been a personal concern.

OK, thanks. I didn't know about these discussions about __traits() and I see now why Proxy doesn't work. So there's a plan to allow __traits() to bypass access rules to provide more useful introspection. That's good. Maybe we should have waited for this change before switching to a new implementation of `Unique`.

greeenify commented on 2017-01-07T21:42:22Z
> If this behaviour is intended, the doc should state it.

This should definitely have gotten a proper changelog entry (and deprecation warning).
However, I am not really convinced that it should be noted in the documentation that access to private member variables isn't supported as this is the way visibility is supposed to work in D. Did anything lead you to this assumption or was it just by chance that accessing `private` variables worked and you didn't realize until the hole was fixed?

b2.temp commented on 2020-01-08T20:21:36Z
Created attachment 1772
fix proposal

code (@MartinNowak) commented on 2017-01-17T23:58:31Z
I'm for reverting this change (the Proxy part).

Proxy is a horrible hack that employ a giant template machinery and was only introduced to replace typedef. It's main difference from alias this being, that you cannot implicitly convert it to the type.

Unique should work like this, but cannot until -dip1000 became default.

static if (class_or_interface)
    T get() return scope { return _p; }
else
    ref T get() return { return *_p; }

alias this get;

This does allow implicit conversion, but binds the lifetime of the returned class ref/ref to the lifetime of Unique, thus making it impossible to escape.

It'll still take a while until that works, and we're likely to come up with new RC implementations after that (b/c both Unique and RefCounted leave a lot to wish).

Also opDot isn't going away for a while (and maybe be could be replaced with opDispatch).

See https://trello.com/c/pTlDuyBD/31-finish-smartref-implementation for previous attempts on fixing Unique/RefCounted.

dransic commented on 2017-01-18T08:24:39Z
(In reply to Martin Nowak from comment #5)
> I'm for reverting this change (the Proxy part).

I agree.

But I suggest reverting all of PR #4763: the Proxy part and the destroy part. The latter also because it introduces undeterministic destruction of Unique!structs (see [1], there is no bug report for this yet, I guess).

[1]<EMAIL_ADDRESS>

dransic commented on 2017-12-16T10:59:14Z
std.experimental.typecons.Final is also affected, since its implementation uses Proxy the same way.

I should probably change the title for a more general one.


Potential race condition/conflict

We've experienced what looks like a potential race condition/conflict on HAPI FHIR 6.6.2.
From the data it looks like that two consecutive updates have been issued almost at the same time messing up the order in which version of the resource is the newest. The consequence of this leaves the resource in an inconsistent state where the resource cannot be updated afterwards.
The error message from the server is the following (when trying to update it afterwards):
"The operation has failed with a version constraint failure. This generally means that two clients/threads were trying to update the same resource at the same time, and this request was chosen as the failing request."
A dump of the resource history is as follows:

   "entry": [
        {
            "fullUrl": "https://xyz.cloud/fhir/Practitioner/416718",
            "resource": {
                "resourceType": "Practitioner",
                "id": "416718",
                "meta": {
                    "versionId": "3",
                    "lastUpdated": "2023-09-02T19:12:47.060+00:00",
                    "source": "http://xyz/admin"
                },
                "identifier": [
                    {
                        "extension": [
                            {
                                "url": "http://xyz/originatesFrom",
                                "valueString": "http://xyz"
                            },
                            {
                                "url": "http://xyz/verified",
                                "valueBoolean": true
                            }
                        ],
                        "system": "urn:oid:<IP_ADDRESS>",
                        "value": "123"
                    }
                ]
            },
            "request": {
                "method": "PUT",
                "url": "Practitioner/416718/_history/3"
            },
            "response": {
                "status": "200 OK",
                "etag": "W/\"3\""
            }
        },
        {
            "fullUrl": "https://xyz.cloud/fhir/Practitioner/416718",
            "resource": {
                "resourceType": "Practitioner",
                "id": "416718",
                "meta": {
                    "versionId": "4",
                    "lastUpdated": "2023-09-02T19:12:46.892+00:00",
                    "source": "http://xyz/admin"
                },
                "extension": [
                    {
                        "url": "http://xyz/fhir/StructureDefinition/practitioner-is-messageable",
                        "valueBoolean": false
                    }
                ],
                "identifier": [
                    {
                        "extension": [
                            {
                                "url": "http://xyz/originatesFrom",
                                "valueString": "http://xyz"
                            },
                            {
                                "url": "http://xyz/verified",
                                "valueBoolean": true
                            }
                        ],
                        "system": "urn:oid:<IP_ADDRESS>",
                        "value": "123"
                    }
                ]
            },
            "request": {
                "method": "PUT",
                "url": "Practitioner/416718/_history/4"
            },
            "response": {
                "status": "200 OK",
                "etag": "W/\"4\""
            }
        },

As can be seen, version 3 has a newer lastUpdated than version 4. Any modification on the resource afterwards produces the error message above.

We have a similar issue possibly related: https://github.com/hapifhir/hapi-fhir/issues/4843. Also see https://github.com/hapifhir/hapi-fhir/issues/4690.

Is this still replicable in master?

We've seen it on 6.6.2 when the server comes under high load. We haven't had the chance yet to try out on either 6.8.2 or master.

This looks like the same issue as the two above - I'm going to close this as a duplicate of https://github.com/hapifhir/hapi-fhir/issues/4843, let's discuss over there.


Installing encountered a problem

Hi @dakaraphi
Thank you very much for developing this plugin.
I tried to install it via marketplace (default procedure Eclipse > Help > Eclipse Marketplace)
I got an error because one or required items could not be found:

The manual installation failed as well.
I double checked the behavior to ensure I do nothing wrong. Unfortunately, I cannot find violations. Am I the only one with this issue?

OS: macOS Sierra 10.12.6
Eclipse: Oxygen.2 (4.7.2)

Build id: M20171130-0510

I haven't seen this before.  For some reason it says it needs org.junit but can't find it.
I will look into it and get back to you.

Hi @dakaraphi
Thank you very much for responding.
I reinstalled eclipse orbit which contains junit (http://download.eclipse.org/tools/orbit/downloads/drops/R20180206163158/repository).
Afterward, I was able to install the plugin without error.

However, the commands/key bindings are not available in Preferences > General > Key

I also checked the workspace > .metadata > .log file. Unfortunately, I do not notice errors containing a reference to your plugin.
Do you have further ideas for debugging?

What type of install was your original Eclipse?  I would have thought all distributions already have org.junit, but maybe not.

I started with Eclipse Platform:

The missing junit/orbit was my mistake – I am sorry for that.
However, the plugin is installed but not working, and I have no more error messages. That is a little bit unusual.

ok, I'm normally installing the plugin into 'Eclipse IDE for Java Developers'
I will see if I can install into 'Eclipse Platform' and see if I can observe a problem.
When you say you have no errors, have you checked the 'Error Log' view?

Yes, however, I saw no entries for your plugin. Did I overlook something?
workspace > .metadata > .log:
!SESSION 2018-03-06 23:59:52.580 -----------------------------------------------
eclipse.buildId=4.7.2.M20171130-0510
java.version=9.0.1
java.vendor=Oracle Corporation
BootLoader constants: OS=macosx, ARCH=x86_64, WS=cocoa, NL=en_CH
Framework arguments:  -keyring ~/.eclipse_keyring
Command-line arguments:  -os macosx -ws cocoa -arch x86_64 -keyring ~/.eclipse_keyring

!ENTRY org.eclipse.jface 2 0 2018-03-06 23:59:58.518
!MESSAGE Keybinding conflicts occurred.  They may interfere with normal accelerator operation.
!SUBENTRY 1 org.eclipse.jface 2 0 2018-03-06 23:59:58.518
!MESSAGE A conflict occurred for ALT+COMMAND+Q P:
Binding(ALT+COMMAND+Q P,
	ParameterizedCommand(Command(org.eclipse.ui.views.showView,Show View,
		Shows a particular view,
		Category(org.eclipse.ui.category.views,Views,Commands for opening views,true),
		org.eclipse.ui.internal.WorkbenchHandlerServiceHandler@5e75cf7a,
		[Parameter(org.eclipse.ui.views.showView.viewId,View,null,true), Parameter(org.eclipse.ui.views.showView.secondaryId,Secondary Id,null,true), Parameter(org.eclipse.ui.views.showView.makeFast,As FastView,null,true)],,true),[org.eclipse.core.commands.Parameterization@351c7030]),
	org.eclipse.ui.defaultAcceleratorConfiguration,
	org.eclipse.ui.contexts.window,,cocoa,system)
Binding(ALT+COMMAND+Q P,
	ParameterizedCommand(Command(org.eclipse.php.ui.explorer,PHP Script Explorer,
		Shows the Script Explorer,
		Category(org.eclipse.ui.category.views,Views,Commands for opening views,true),
		org.eclipse.ui.internal.WorkbenchHandlerServiceHandler@6f12fca0,
		,,true),null),
	org.eclipse.ui.defaultAcceleratorConfiguration,
	org.eclipse.ui.contexts.window,,cocoa,system)
!SUBENTRY 1 org.eclipse.jface 2 0 2018-03-06 23:59:58.518
!MESSAGE A conflict occurred for ALT+COMMAND+R:
Binding(ALT+COMMAND+R,
	ParameterizedCommand(Command(org.python.pydev.debug.setnext,Set Next Statement,
		,
		Category(org.python.pydev.ui.category.run,PyDev - Run,Python run category,true),
		org.eclipse.ui.internal.WorkbenchHandlerServiceHandler@12c30824,
		,,true),null),
	org.eclipse.ui.defaultAcceleratorConfiguration,
	org.eclipse.ui.contexts.window,,,system)
Binding(ALT+COMMAND+R,
	ParameterizedCommand(Command(org.eclipse.jdt.ui.edit.text.java.rename.element,Rename - Refactoring ,
		Rename the selected element,
		Category(org.eclipse.jdt.ui.category.refactoring,Refactor - Java,Java Refactoring Actions,true),
		org.eclipse.ui.internal.WorkbenchHandlerServiceHandler@7d0e43d6,
		,,true),null),
	org.eclipse.ui.defaultAcceleratorConfiguration,
	org.eclipse.ui.contexts.window,,cocoa,system)

!ENTRY org.eclipse.core.net 1 0 2018-03-07 00:00:02.364
!MESSAGE System property http.nonProxyHosts has been set to local|*.local|169.254/16|*.169.254/16 by an external source. This value will be overwritten using the values from the preferences

!ENTRY org.eclipse.oomph.setup.ui 1 0 2018-03-07 00:00:06.033
!MESSAGE Setup tasks were performed during startup updating 1996 preferences. See '/Applications/eclipse/ide-latest-released/Eclipse.app/Contents/Eclipse/configuration/org.eclipse.oomph.setup/setup.log' for details

Using the Eclipse Platform install, this is what I additionally needed to install.

Eclipse Orbit.  I installed all packages.
Eclipse Java Developer Tools

Then I was able to install Commander.
Do you have both 1 and 2 installed?  If you go to 'about eclipse' -> 'Installed Software' and search for 'commander', do you see 'Commander Feature' listed?
If it is listed, if you type 'commander' in 'quick access' does it show there?

Thank you very much, that solves the problem.
Together with the newly installed JDT, Commander is now available as expected.

I had problems getting this extension to run with Eclipse Rust edition. Installing Java Developer Tools helped. @dakaraphi , could you add a note to README or Marketplace page?


add err traceback

pass data between spans without corrupting attributes
add error type and error stacktrace to span
simplified the errorHandler function in exporter.js


Add parse-backticks feature

This feature will convert `code` into code where applicable. Currently it only looks for it in issue titles, but it can be expanded (hence the very generic name)
The style is TBD.

Should the backticks stay?
Should the text size be increased?
Should the background be turned gray?

Edit: no, yes, yes; see next comment
Test
https://github.com/sindresorhus/np/issues
Before

After
Edit: discarded, see next comment

Here's what happens when I add .markdown-body to the title (and drop its margin-top)

Another screenshot. Maybe it looks a bit busy with the gray background:

Pro-tip: hub checkout origin/test-all-currently-open-prs-at-once

Should the backticks stay?

What about visually hiding it, but keeping it for copying?

What about visually hiding it, but keeping it for copying?

Possible, but what do you need to copy issue titles for?

@bfred-it commented on Mar 25, 2019, 5:01 PM GMT+1:

What about visually hiding it, but keeping it for copying?

Possible, but what do you need to copy issue titles for?

No particular reason, just a suggestion.

What about visually hiding it, but keeping it for copying?

I too think this would be nice if it's not hard. Before a large release, I like to create a v2 issue with an overview of what work is left and important issues, so then I would copy-paste the issue titles.

I was afraid this would look noisy, but it actually looks quite nice: https://github.com/sindresorhus/eslint-plugin-unicorn/issues?q=is%3Aissue+is%3Aopen+sort%3Aupdated-desc


tfsec endless loop

Describe the bug
Invoking  tfsec  stuck in andless loop :crying_cat_face:
To Reproduce
I have a terraform project with the following structure:
➜  tf-reco-engine ✗ tree
.
├── config.tf
├── dev.auto.tfvars
├── main.tf
├── modules
│   ├── cdn
│   │   ├── main.tf
│   │   ├── outputs.tf
│   │   └── vars.tf
│   ├── certificate
│   │   ├── main.tf
│   │   └── outputs.tf
│   ├── dynamodb
│   │   ├── main.tf
│   │   └── vars.tf
│   ├── elasticache
│   │   ├── main.tf
│   │   └── vars.tf
│   ├── es
│   │   ├── main.tf
│   │   └── vars.tf
│   ├── main.tf
│   ├── rds
│   │   ├── main.tf
│   │   ├── outputs.tf
│   │   └── vars.tf
│   ├── roles.tf
│   ├── route53
│   │   ├── main.tf
│   │   └── vars.tf
│   ├── s3
│   │   ├── locals.tf
│   │   ├── main.tf
│   │   ├── outputs.tf
│   │   └── vars.tf
│   ├── secretsmanager
│   │   ├── main.tf
│   │   └── vars.tf
│   ├── sns
│   │   ├── main.tf
│   │   └── vars.tf
│   └── vars.tf
└── vars.tf
11 directories, 31 files
When, in the root path of the project I execute   tfsec --exclude-downloaded-modules --tfvars-file dev.auto.tfvars (or tfsec with any other combination of flags), an endless loop (that consumes a lot of resources of my laptop) start to happen until I kill it.
Expected behavior
tfsec to quickly parse the fails and print the vulnerabilities found
Desktop:

OS: Linux (Same bug in CentOS 7 & Ubuntu 20)
Version of tfsec v0.39.14

Additional context
You can find the verbose output until I kill the process here:
https://we.tl/t-jOxLbBlDSq

I removed the .terraform folder from the directory and it ran without issues.

Was able to reproduce it with a simple tf file containing only module
module "s3-bucket" {
  source  = "cloudposse/s3-bucket/aws"
  version = "0.32.0"
  # insert the 16 required variables here
}

It looks like infinite loop when evaluating
.terraform/modules/s3-bucket.s3_user.s3_user.this

I've got a fix that seems to resolve this - I just want to be sure its not going to cause headaches elsewhere.
The resulting stats from the change are
  ------------------------------------------
  disk i/o             22.438564ms
  parsing HCL          120.107µs
  evaluating values    70.102094ms
  running checks       34.767509ms

  counts
  ------------------------------------------
  files loaded         21
  blocks               1
  evaluated blocks     243
  modules              6
  module blocks        242

1 potential problems detected.

With regard to --exclude-downloaded-modules, this just removes the results from the output, it doesn't prevent them from being parsed as @michal-franc says
exclude-downloaded-modules - Remove results for downloaded modules in .terraform folder

Yes that fixed it for me. thanks for the quick turnaround.


Can not override NO_PROXY (* not mapped to ECMAScript syntax)

Agent Version and Platform

2.200.2
Windows

Azure DevOps Type and Version

https://dev.azure.com/ZEISSgroup-SMT

What's not working?
The proxy configuration through .proxybypass is not exclusive. The Azure Pipelines Agent uses the proxy configuration from different sources. It's not possible to override the configuration from NO_PROXY (env variable).
https://github.com/microsoft/azure-pipelines-agent/blob/c5e9872c7c88713401aac5111f92e20c8cfc70ab/src/Microsoft.VisualStudio.Services.Agent/VstsAgentWebProxy.cs#L130-L149
The Azure Pipelines Task SDK expect the proxy configuration in ECMAScript syntax, but other tools do not. We get following error: Invalid regular expression: /*\.zeiss\.org/: Nothing to repeat. Even if we set the proxy configuration through .proxybypass, NO_PROXY is read.
Our configuration:

.proxybypass

localhost
10\.1\.1\.\d{1,3}
.*\.zeiss\.org

NO_PROXY

localhost,<IP_ADDRESS>/26,*.zeiss.org

will set the Agent.ProxyBypassList variable to:

localhost
10\\.1\\.1\\.\\d{1,3}
.*\\.zeiss\\.org
localhost
10\\.1\\.1\\.0/26
*\\.zeiss\\.org

As you can see, the last item is not valid ECMAScript syntax. A lot of different tools use this syntax for NO_PROXY.
You already map the env variables to a different syntax (. → \\.). It's probably necessary to map * too.
https://github.com/microsoft/azure-pipelines-agent/blob/c5e9872c7c88713401aac5111f92e20c8cfc70ab/src/Microsoft.VisualStudio.Services.Agent/VstsAgentWebProxy.cs#L235
Agent and Worker's Diagnostic Logs
Checking job knob settings.
   Knob: AgentToolsDirectory = C:\hostedtoolcache\windows Source: ${AGENT_TOOLSDIRECTORY}
   Knob: NoProxy = localhost,<IP_ADDRESS>/26,*.zeiss.org Source: ${no_proxy}
   Knob: ProxyAddress = http://<IP_ADDRESS>:80 Source: ${http_proxy}
Finished checking job knob settings.

...

##[debug]Agent.ProxyUrl=http://<IP_ADDRESS>:80
##[debug]Agent.ProxyUsername=undefined
##[debug]Agent.ProxyPassword=undefined
##[debug]Agent.ProxyBypassList=["localhost","10\\.1\\.1\\.\\d{1,3}",".*\\.zeiss\\.org","localhost","10\\.1\\.1\\.0/26","*\\.zeiss\\.org"]

The issue still exists.

Do not close !


Storybook build fails with ember-destroyable-polyfill

I've upgrade hokulea to latest dependencies PR: hokulea/hokulea#13
With that I've upgrade to @glimmer/component and @glimmer/tracking to v1.0.1 and ember to v3.20 and not sure which one of those upgrades brings in ember-destroyable-polyfill. However, they break my storybook build on netlify. Here is the log: https://app.netlify.com/sites/hokulea/deploys/5f42add1bae43a0008544de5 (@hokulea/explorer is the addon which runs the storybook). The build runs locally for me, which keeps me wondering.
There is more to it, that might all depend together. Also the tests work for me locally but fail on github actions. Here is the latest run: https://github.com/hokulea/hokulea/pull/13/checks?check_run_id=1018844223
Which brings me to that fact, that I reported a similar problem to storybook: storybookjs/storybook#11853 I thought this issue is because storybook runs its own webpack bundling and as part of that fails to parse the template in there. Now I think, this is even more connected to ember itself.
I'm kind stuck with this but happy to provide help or am up for pairing

Hmm, neither @glimmer/component nor @glimmer/tracking use this polyfill themselves. My guess would be something like ember-modifier@2 (which does use this polyfill).

The failure in that PR's tests that I see:
Build Error (broccoli-persistent-filter:Babel > [Babel: @hokulea/buttons]) in @hokulea/buttons/components/accent-button/stories.ts
@hokulea/buttons<EMAIL_ADDRESS>Can't reference '{"id":"f8hLISdf","block":"{\"symbols\":[],\"statements\":[[2,\"\\n      \"],[8,\"accent-button\",[[24,\"aria-label\",\"Go Tomster!\"]],[[],[]],[[\"default\"],[{\"statements\":[[2,\"\\n        \"],[10,\"span\"],[14,\"aria-hidden\",\"true\"],[12],[2,\"🐹\"],[13],[2,\"\\n      \"]],\"parameters\":[]}]]],[2,\"\\n    \"]],\"hasEval\":false,\"upvars\":[]}","meta":{}}' as a bare identifier (This is an error on an internal node. Probably an internal error.)

Is also seems unrelated to this polyfill 🤔


Incompatible with Meteor 1.6.1-rc.1 due to babel-compiler upgrade

Hi @Urigo and @ardatan
recently Meteor 1.6.1 was upgraded to use babel-compiler 7.0.0 which breaks angular-meteor compatibility.
An example is to upgrade the examples/MeteorCLI/all-in-one and run it with an updated Meteor.
Running AOT=1 meteor using Meteor <IP_ADDRESS> works.
Error with 1.6.1:
examples/MeteorCLI/all-in-one
meteor update --release 1.6.1-rc.1
=> Errors while initializing project:
While selecting package versions:
error: Conflict: Constraint<EMAIL_ADDRESS>is not satisfied by babel-compiler 7.0.0-rc161.1.
Constraints on package "babel-compiler":

<EMAIL_ADDRESS><- top level
<EMAIL_ADDRESS><- ecmascript 0.10.0-rc161.1
<EMAIL_ADDRESS><- standard-minifier-js 2.3.1-rc161.1
<EMAIL_ADDRESS><- minifier-js 2.3.1-rc161.1 <- standard-minifier-js 2.3.1-rc161.1
<EMAIL_ADDRESS><- angular-typescript-compiler 0.2.9 <- angular-compilers 0.2.8_1

Thanks for your help!

Hi we have the same issue trying to upgrade to 1.6.1 from version <IP_ADDRESS>
I there any known workaround for this problem?

Hi  @choudrio, @pbureau,
When I try to update examples/MeteorCLI/all-in-one from 1.6 to <IP_ADDRESS>, I get:
$ svn export https://github.com/Urigo/angular-meteor/trunk/examples/MeteorCLI/all-in-one
$ cd all-in-one
$ meteor npm install
$ meteor update --patch
=> Errors while initializing project:

While selecting package versions:
error: Conflict: Constraint<EMAIL_ADDRESS>is not satisfied by babel-compiler 7.0.4.
Constraints on package "babel-compiler":
*<EMAIL_ADDRESS><- top level
*<EMAIL_ADDRESS><- ecmascript 0.10.0
*<EMAIL_ADDRESS><- standard-minifier-js 2.3.1
*<EMAIL_ADDRESS><- minifier-js 2.3.1 <- standard-minifier-js 2.3.1
*<EMAIL_ADDRESS><- angular-typescript-compiler 0.2.9 <- angular-compilers 0.2.8_1

As it seems that you managed to update your project, can you share your configuration (at least package.json, .meteor/packages, tsconfig.json)

Hi,

  I did not manage to make it work, the only configurations that
  works for me is using Meteor <IP_ADDRESS> and the old angular2-compiler

  Pierre

  On 17/02/2018 21:45, atao60 wrote:

  Hi @choudrio,
    @pbureau,
  When I try to update examples/MeteorCLI/all-in-one from 1.6 to
    <IP_ADDRESS>, I get:
  $ svn export https://github.com/Urigo/angular-meteor/trunk/examples/MeteorCLI/all-in-one

$ cd all-in-one
$ meteor npm install
$ meteor update --patch
=> Errors while initializing project:
While selecting package versions:
error: Conflict: Constraint<EMAIL_ADDRESS>is not satisfied by babel-compiler 7.0.4.
Constraints on package "babel-compiler":

<EMAIL_ADDRESS><- top level

<EMAIL_ADDRESS><- ecmascript 0.10.0

<EMAIL_ADDRESS><- standard-minifier-js 2.3.1

<EMAIL_ADDRESS><- minifier-js 2.3.1 <- standard-minifier-js 2.3.1

<EMAIL_ADDRESS><- angular-typescript-compiler 0.2.9 <- angular-compilers 0.2.8_1
As it seems that you managed to update your project, can you
  share your configuration (at least package.json,
  .meteor/packages, tsconfig.json)
—
  You are receiving this because you were mentioned.
  Reply to this email directly, view
    it on GitHub, or mute
    the thread.

{"api_version":"1.0","publisher":{"api_key":"05dde50f1d1a384dd78767c55493e4bb","name":"GitHub"},"entity":{"external_key":"github/Urigo/angular-meteor","title":"Urigo/angular-meteor","subtitle":"GitHub repository","main_image_url":"https://cloud.githubusercontent.com/assets/143418/17495839/a5054eac-5d88-11e6-95fc-7290892c7bb5.png","avatar_image_url":"https://cloud.githubusercontent.com/assets/143418/15842166/7c72db34-2c0b-11e6-9aed-b52498112777.png","action":{"name":"Open in GitHub","url":"https://github.com/Urigo/angular-meteor"}},"updates":{"snippets":[{"icon":"PERSON","message":"@atao60 in #1855: Hi  @choudrio, @pbureau,\r\n\r\nWhen I try to update examples/MeteorCLI/all-in-one from 1.6 to <IP_ADDRESS>, I get:\r\n\r\n```\r\n$ svn export https://github.com/Urigo/angular-meteor/trunk/examples/MeteorCLI/all-in-one\r\n$ cd all-in-one\r\n$ meteor npm install\r\n$ meteor update --patch\r\n=\u003e Errors while initializing project:

  \r\n                                              \r\nWhile selecting package versions:\r\nerror: Conflict: Constraint<EMAIL_ADDRESS>is not satisfied by babel-compiler 7.0.4.\r\nConstraints on package \"babel-compiler\":\r\n*<EMAIL_ADDRESS>\u003c- top level\r\n*<EMAIL_ADDRESS>\u003c- ecmascript 0.10.0\r\n*<EMAIL_ADDRESS>\u003c- standard-minifier-js 2.3.1\r\n*<EMAIL_ADDRESS>\u003c- minifier-js 2.3.1 \u003c- standard-minifier-js 2.3.1\r\n*<EMAIL_ADDRESS>\u003c- angular-typescript-compiler 0.2.9 \u003c- angular-compilers 0.2.8_1\r\n\r\n```\r\nAs it seems that you managed to update your project, can you share your configuration (at least package.json, .meteor/packages, tsconfig.json)\r\n"}],"action":{"name":"View Issue","url":"https://github.com/Urigo/angular-meteor/issues/1855#issuecomment-366470156"}}}

--
http://www.mykodibox.fr
Mobile: +33 6 74 79 18 59

@choudrio I don't believe there is much activity on the angular-meteor project at the moment, we are also trying to get more information about the status of the stack and the options for further support in the future.
Don't hesitate to keep me posted if you have any news on your side.

today we've released new versions for angular-compilers and meteor-client-bundler with a few fixes and to support the latest Meteor 1.6.1, thanks to the great work of @ardatan and @afaur !
Let us now if everything works as expected.

as a side note, my personal email is public and I'm always happy to talk, hear and help users of angular-meteor with their questions, whatever questions they may be!


DialogParser?

This is an amazing resource for managing OpenStack from ManageIQ/ Cloudforms! Thanks very much for publishing to Github.
A quick question - the build_vm_provision_request.rb method under the Service provisioning state machine references a DialogParser method. I couldn't find the method in its referenced location (/Service/Provisioning/StateMachines/Methods/DialogParser). Can anyone please help out?
Thanks again.
Shane

Shane,
Check out the ManageIQ domain that ships with the product. The DialogParser method was not modified, so it is not included with CloudForms_Essentials.

Ah, awesome. Thanks Nate!


Not able to save model as pmml

Traceback (most recent call last):
File "/home/administrator/ilabs/GIT/learning2rank/rank/LR_testing.py", line 22, in
rankerNN2pmml(estimator=ranker.model, file='Model_example.xml', **params)
File "/home/administrator/ilabs/GIT/learning2rank/.venv/lib/python3.6/site-packages/rankerNN2pmml/init.py", line 207, in rankerNN2pmml
feature_names = _validate_inputs(estimator, transformer, feature_names)
File "/home/administrator/ilabs/GIT/learning2rank/.venv/lib/python3.6/site-packages/rankerNN2pmml/init.py", line 29, in _validate_inputs
raise TypeError("Provided model is not supported.")
TypeError: Provided model is not supported.

You are getting this error because your ranker.model is not an instance of keras.models.Model. Please check your ranker.model, or look at my example in README.

I have used the given example only for verification and getting the same error.
I am now able to  save model as a pickle file with a hack. so closing this thread.

Same issue here!
Traceback (most recent call last):
  File "test.py", line 25, in <module>
    rankerNN2pmml(estimator=ranker.model, file='Model_example.xml', **params)
  File "/Library/Frameworks/Python.framework/Versions/3.8/lib/python3.8/site-packages/rankerNN2pmml/__init__.py", line 207, in rankerNN2pmml
    feature_names = _validate_inputs(estimator, transformer, feature_names)
  File "/Library/Frameworks/Python.framework/Versions/3.8/lib/python3.8/site-packages/rankerNN2pmml/__init__.py", line 29, in _validate_inputs
    raise TypeError("Provided model is not supported.")
TypeError: Provided model is not supported.


Allow accid.ges on

Currently @accid.ges is not allowed on <accid>. From an e-mail exchange with Perry:
<accid> was intended to only operate in the visual domain, leaving info about
the performed accidental on  <note>.  But, I'm not sure this approach is valid.
When something that was an attribute gets promoted to object status, ideally
the properties associated with it come along as well.  The determination of whether
@accid.ges is a property of <accid> or of <note> is a significant issue.

This is related to #261, where it was decided that @accid.ges would refer to a performed, but not visual accidental. If we want to use <accid> to specify the accidental on a note, but have it represent a performed but not visible accidental, we will need to add @accid.ges to <accid>.

Interesting question. Do we not have the same problem with <octave>, @oct and @oct.ges?

I don't think so -- <octave> is not a child of <note> like <accid> is. So @oct information is stored on the note anyway, and the presence of <octave> is explicitly gestural. From: http://music-encoding.org/documentation/2.1.1/octave/ :
An indication that a passage should be performed one or more octaves above or below its written pitch.

Closed by [081eb58]


docs: fix closing tag in readme

I've noticed that the opening tag is <h2> but the closing tag is </h3>

Thanks!


[CT-3509] [Bug] assets not being copied to targets directory

Is this a new bug in dbt-core?

[X] I believe this is a new bug in dbt-core
[X] I have searched the existing issues, and I could not find an existing issue for this bug

Current Behavior
Having an assets-path defined in the dbt_project.yml file:
...

model-paths: ["models"]
analysis-paths: ["analyses"]
test-paths: ["tests"]
seed-paths: ["seeds"]
macro-paths: ["macros"]
snapshot-paths: ["snapshots"]
target-path: "target"
docs-paths: ["docs"]
asset-paths: ["assets"]

...

The directory assets is not being copied to target/assets when running dbt docs generate, as mentioned in the docs. Then, any attempt to load an image from that directory fails. It works fine with external links and when manually copying assets to target/assets.
Expected Behavior
The assets directory is copied to target/assets and the images shown in the documentation
Steps To Reproduce

Create a new dummy dbt project with dbt init
Complete credentials in profiles.yml
Add asset-paths: ["assets"] to the dbt_project.yml file, and create the directory
Place any image in the assets directory
Create a models/properties.yml file for the example model, and include a description like this one
Run dbt docs generate
Run dbt docs serve --port 8080 --browser
Verify that no image is shown in your model's description

Relevant log output
N/A

Environment
- OS: macOS Sonoma 14.2
- Python: 3.10.12
- dbt: 1.5.6

Which database adapter are you using with dbt?
redshift
Additional Context
I'm running dbt in a virtual environment managed with poetry 1.6.1

Thanks for reaching out and providing such a nice set of instructions @hvignolo87 🥇
I tried reproducing the issue you reported using dbt-postgres==1.5.6, and everything worked as described in the docs.
I wonder if something is accidentally misspelled or misconfigured in your project that can explain what is going on?
Could you try out the example below and see if it works for you or not?

Example that worked for me

Project files
Here's my exact set of files:
dbt_project.yml
name: "my_project"
version: "1.0.0"
config-version: 2
profile: "postgres"

asset-paths: ["assets"]

models/customers.sql
{{ config(materialized="table") }}

select 1 as customer_id

models/properties.yml
version: 2

models:
  - name: customers
    description: "![dbt Logo](assets/dbt-logo.svg)"

    columns:
      - name: customer_id
        description: Primary key

Commands
mkdir -p assets
curl -o assets/dbt-logo.svg https://docs.getdbt.com/img/dbt-logo.svg
dbt docs generate
ls -al target/assets
dbt docs serve --port 8080 --browser

Output
(postgres_1.5) $ mkdir -p assets

(postgres_1.5) $ curl -o assets/dbt-logo.svg https://docs.getdbt.com/img/dbt-logo.svg

  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100  3899  100  3899    0     0  12146      0 --:--:-- --:--:-- --:--:-- 12417
(postgres_1.5) $ dbt docs generate

02:01:57  Running with dbt=1.5.6
02:01:57  Registered adapter: postgres=1.5.6
02:01:57  Found 1 model, 0 tests, 0 snapshots, 0 analyses, 307 macros, 0 operations, 0 seed files, 0 sources, 0 exposures, 0 metrics, 0 groups
02:01:57
02:01:57  Concurrency: 5 threads (target='blue')
02:01:57
02:01:57  Building catalog
02:01:57  Catalog written to /dbt-core-9308/target/catalog.json
(postgres_1.5) $ ls -al target/assets

total 8
drwxr-xr-x   3 dbeatty  staff    96 Dec 20 18:39 .
drwxr-xr-x  13 dbeatty  staff   416 Dec 20 19:01 ..
-rw-r--r--   1 dbeatty  staff  3899 Dec 20 19:01 dbt-logo.svg

Hi @dbeatty10! Thank you very much for your quick answer! 😅
I'm not able to reproduce your example. The assets directory isn't copied to target in my case.
Here is a MRE of what I'm doing locally.
dbt_test.zip
Once you fill in your credentials in profiles.yml, please run:
poetry run dbt docs generate --project-dir test --profiles-dir test

Here's a video of what I'm doing:
https://drive.google.com/file/d/1YLyHTxzjjByXJEjbgEQBy1DDquIN5qMP/view?usp=drive_link

Hi @dbeatty10! Thank you very much for your quick answer! 😅
I'm not able to reproduce your example, still not working for me.
Here's a MRE of what I have locally.
dbt_test.zip
Please fill in your credentials in profiles.yml, and then run:
poetry run dbt docs generate --project-dir test --profiles-dir test

Then please go to the targets folder and see if the assets directory is there.
Here's a video of what I'm doing:
https://drive.google.com/file/d/1YLyHTxzjjByXJEjbgEQBy1DDquIN5qMP/view?usp=drive_link

Thanks for your source code for a MRE along with a video 🤩
That helps get to the bottom of things.
Let's suppose I have a project located at /some_path/test/ and that is also the current working directory.
✅ Then any of the following does successfully add the /some_path/test/target/assets/ directory:
dbt docs generate
dbt docs generate --project-dir .
dbt docs generate --project-dir /some_path/test/

❌ But this does not add the /some_path/test/target/assets/ directory:
dbt docs generate --project-dir /some_path/test/

So ultimately it's the --project-dir flag that is not working with the docs generate sub-command when the project directory is not the current working directory.
This looks similar to https://github.com/dbt-labs/dbt-core/issues/8385 to me, and it might have a similar solution.

I've confirmed that this is an issue in 1.7 (currently the latest) as well as dbt-core 1.5 (as originally reported).
Acceptance criteria

Using the example project here, dbt docs generate --project-dir some_path will generate some_path/target/assets/ even when some_path is not the current working directory
There is a functional test (potentially similar to #8388) that tests --project-dir for docs generate

Let's suppose I have a project located at /some_path/test/ and that is also the current working directory.
✅ Then any of the following does successfully add the /some_path/test/target/assets/ directory:
dbt docs generate
dbt docs generate --project-dir .
dbt docs generate --project-dir /some_path/test/

This doesn't work for me either 😕


feat: set up env for test & add basic unit test example

Description

added basic unit test for ReputationService
tests are run by "npm run test"

Types of changes
What types of changes does your code introduce?
Put an x in the boxes that apply

[ ] Bugfix (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)
[ ] Documentation Update
[ ] Code style update (formatting, renaming)
[ ] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[ ] Other (please describe):

Further comments (optional)

Apparently viem library does not carry it's own evm for tests, it makes use of anvil or hardhat. We can use that with ethers.js as well, so I went on using Ethers in tests.
To run tests you must have Anvil installed: https://book.getfoundry.sh/getting-started/installation

I'll add some more unit tests for each module and service


Clarify what versions of windows server

What versions of Windows Server does this apply to?   Server 2008 R2 is still in extended support, but I was under the impression that you used dcpromo.exe, vice server manager to decom DCs.    I am not suggesting you update this page for 2008R2 just update what versions these steps apply to.

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 4db96074-3ebd-a88e-5d1c-fc8e8083c5c5
Version Independent ID: 0b5d953b-8fce-410f-037e-e81dda94a477
Content: Demoting Domain Controllers and Domains (Level 200)
Content Source: WindowsServerDocs/identity/ad-ds/deploy/Demoting-Domain-Controllers-and-Domains--Level-200-.md
Product: windows-server
Technology: ad-ds
GitHub Login: @iainfoulds
Microsoft Alias: iainfou

Closing and reopening as a test of PRMerger automation

Hi @alexknab,
Thanks for the feedback. Several articles including this one were updated with applies to in this commit: https://github.com/MicrosoftDocs/windowsserverdocs/commit/e057d07062045e3a97715861a3a762434ce23dd9.
I'm going to request closing the issue. #please-close.
Thanks again,
Pat


Trust wallet integration & SDK

Hey web3-onboard team! I'm Karim, and I'm representing the Web Extension team of Trust Wallet. Based on Pull Request Guide, I'm opening this PR with a complete list of the changes it introduces (all related to Trust Wallet).
Description

Trust Wallet SDK package was created.
Not displaying Trust Wallet name and logo when wallet was injected fixed.
Conflicts between multiple injected wallets fixed.
Documentation with Trust Wallet examples added.

Checklist

[x] The version field in package.json of the package you have made changes in is incremented following semantic versioning and using alpha release tagging
[x] The box that allows repo maintainers to update this PR is checked
[x] I tested locally to make sure this feature/fix works
[x] I have run yarn file-check, yarn type-check & yarn build to confirm there are not any associated errors
[ ] This PR passes the Circle CI checks

Tests with demo app (injected)

[ ] send transaction
[ ] switch chains
[ ] sign message
[ ] sign typed message
[ ] disconnect

Tests with demo app (SDK)

[ ] send transaction
[ ] switch chains
[ ] sign message
[ ] sign typed message
[ ] disconnect

[ ] QA (ongoing)

Thanks for putting this PR together @karim-yassine ! I left a few comments to address. Can you test and complete the new wallet injected and SDK checklist when you have a moment? Thanks! Looking forward to adding support!

Hello @Adamj1232, all the changes suggested where committed!
Our QA team is working on testing the wallet integration; could you please approve the Vercel deployment workflow?
Thank you in advance!

@karim-yassine the vercel deployment is for our docs site we pulled into the develop branch. Please pull the latest develop when you have a chance.
For a vercel demo app of the Demo app for QA-ing wallet integration you will have to run yarn build within the demo package and then upload the public file from the demo package to vercel manually. We ill have this automated in the future.

@Adamj1232 awesome, I'll update you when QA and the checklist are completed.
Thanks again Adam!

@karim-yassine friendly ping to see how things are going and a reminder to pull in the latest develop and handle conflicts.
If there is anything I can do to help please feel free to reach out and let me know 😄

@Adamj1232 Thanks for reaching out!
We are still under QA; we are fixing some small edge cases we managed to find. I'll make sure to sync the brach with develop and fix the conflicts before asking for new review and merge.
Everything should be done and ready for merge by the end of this week; I will keep you informed :)

@karim-yassine we are going to be putting together a release candidate today. Any chance this PR is ready for review? If not we will have a following release coming out next week (or the week after)

@Adamj1232 Hello! I'll be opening PR today, we found a bug in the index of injected package that we fixed, I'm just finalizing testing and making sure that it works correctly with other wallets.

@Adamj1232 ready for review.
Regarding our fix in the index file of injected package, the bug here was that the implementation assumed that if there is a provider array, that should only be checked, which is wrong because it excludes the global scope. For that reason we first check the global scope and then the providers array, if exist.

@karim-yassine thank you for the PR! I will test now! Can you give me write access if not already so I can add docs for your new module integration?

@karim-yassine If interested in doing a bit of co-marketing/tweeting on the new support and package please feel free to reach out 😃

Please ok


Use influxdb with ssl

Hi,
it could be nice to to be able to use influxdb with ssl, it could be simple as adding params in settings and pass params to InfluxDBClient here, https://github.com/bitmazk/django-influxdb-metrics/blob/master/influxdb_metrics/utils.py#L10
I can send a pull request if you are interested.
Thanks

@grangerp sure thing! please send a pull request. happy to merge!


Use date in permalink

Currently we used flat url structure - http://www.mydev.my/cara-murah-guna-https.html
What about http://www.mydev.my/posts/2015/01/20/cara-murah-guna-https.html ?
Maybe we should look from SEO perspective, which one is better.

Default Jekyll config is using having date in the URL. I changed it to
simple filename path so old link from the Pelican version wont break.
Personally, I don't see much benefit in it unless for personal blogs which
chronological timeline might bring some context to the article.
I am not sure about SEO though.
On Wed, Jan 21, 2015 at 12:40 PM, k4ml<EMAIL_ADDRESS>wrote:

Currently we used flat url structure -
http://www.mydev.my/cara-murah-guna-https.html
What about http://www.mydev.my/posts/2015/01/20/cara-murah-guna-https.html
?
Maybe we should look from SEO perspective, which one is better.
—
Reply to this email directly or view it on GitHub
https://github.com/mydevcommunity/mydevcommunity.github.io/issues/4.

You have a point there. As for SEO, adding category is better I think - http://www.mydev.my/javascript/belajar-javascript-bhg-2.html will optimize that for javascript keyword.


Model Evaluation

GluPredKit refactor for enhanced and strict model evaluation:
Refactor:

[ ] All models should be multiple output

[ ] Create multioutput models

[x] Scikit models
[ ] Neural networks

[ ] Create multioutput preprocessor
[ ] Update all CLI commands to support multiple outputs
[ ] Delete outdated files

[ ] What-if events should be default
[ ] Fix plug-and-play error: ohio should also be able to be used with normal preprocessor
[ ] Update README to the refactoring

Configuration:

[ ] Number of time lagged events should be specified for each feature (list instead of integer)
[ ] Configuration has one prediction horizon
[ ] Test size should be removed to parsers, CLI command instead. In that way, we can make preprocessors properly plug-and-play
[ ] Maybe the type of numerical transformation should be an input to the configuration instead of creating a new preprocessor for every time you want to use something different

Generate pdf reports for model evaluation:

[x] Create CLI command to generate a report
[ ] Add a text at top or bottom that refers to GluPredKit ("This report is generated using GluPredKit...")
[ ] Add dataset information
[ ] Add configuration information
[ ] Add traditional evaluation metrics
[ ] Add run time evaluation
[ ] Insulin and carbohdyrate effect evaluation: Use PCP or the other number (S..). Idea for Partial Dependence Plot: x-axis is prediction horizon, y axis is predicted blood glucose, but then we can have many lines with labels like (UI = 1, UI=2...).
[ ] Generate a report that compare models - have in mind that datasets usually will contain many subjects.

Models:

[ ] Delete models that don't fit our requirements? Or define included models based on inclusion criterion. Maybe models from the literature that have included their source code for example? Use Doyoungs work as help?
[ ] Uva padova model
[ ] T1D loop model
[x] Tidepool Loop model

Parsers:

[ ] Parsers should process data with the new set of features that we agree upon with Sam
[ ] Add OpenAPS as well
[ ] Should assume that all the dataset subjects are in the dataset initially
[ ] Parsers should already have separated train and test data to avoid data leakage

[ ] Remove test data fraction from configuration
[ ] Add it to parsing CLI command instead?

Metrics:

[x] Add MARD number

Testing:

[ ] Make sure that all components have tests and that running the tests is working

General improvements:

[ ] Be clearer about the expected input and output formats for each module
[ ] Add citation information in README

Checklist before merge

[ ] Clean up the code properly
[ ] Make sure that all the CLI commands are working on both Win and Mac
[ ] Run tests
[ ] Update README to reflect all of the changes

Subtasks adding Loop model:

[ ] Use the 1800 rule ++ to fit the therapy settings to individuals
[ ] Figure out how to handle smoothly the history lengths when calculating metrics (maybe loop prediction algorithm also should use the "time lagged features" from configuration)
[ ] Add future carbs and insulin
[ ] Make sure that parsers add basals correctly and loop model uses basals correctly wrt units

Subtasks adding whole Ohio dataset evaluation:

[ ] Parsing: Storing the dataset in one file,
[ ] CLI: Parse the whole dataset, store in one file
[ ] Model: Train one model each individual? Use the individual models for model evaluation?
[ ] Generated report

Subtask adding the single model evaluation:

[ ] Add a test-model function to store predictions and configurations so that you can prototype the generated reports more quickly
[ ] store predictions for a ridge and a loop model
[ ] train a loop model with optimizing parameters for a loop model to make the predictions and distributions more realistic
[ ] Add a zero-hold algorithm and store predictions
[ ] Add a naive linear regressor and store predictions
[ ] Add a 3rd or 4th order arx and store predictions
[ ] Model accuracy:

[ ] In the plot, compare to the naive models
[ ] Add metrics: MARE, ME/MRE
[ ] Plot parkes error grid (pick max 6 within the prediction horizon)
[ ] Write parkes error grid results in a table

[ ] Glycemia Detection:

[ ] Hypo: Plot accuracy, MCC across the prediction horizon
[ ] Hyper: Plot accuracy, MCC across the prediction horizon
[ ] Total: Make a table, calculate overall results

[ ] Predicted distribution: Remove the second plot, add indication from the test data, maybe add an interpretation of it in text format? Make it visually clear what is the preferred range.
[ ] Physiological Alignment:

[ ] Calculate SHAP numbers. They provide positive or negative impact indication, and magnitude.
[ ] Plot a matrix of SHAP numbers across the prediction horizon and for different time lags
[ ] Add color coding to the matrix so we can clearly see the impact.
[ ] Make the color red if it contradicts the physiological reality
[ ] Make an interpretation of the matrix in writing? Or add the plot for a physiological model.

[ ] Finish the first page overview of the model evaluation
[ ] Write a document explaining all of the plots and the numbers and the benchmark naive algorithms
[ ] Clean up the code so that the cli file is very understandable, and making a helper file that can be more messy

Subtask adding the single model evaluation:

[ ] Error grid analysis cost functions

JOSS To dos:

[ ] Parsers

[ ] Separate into test and train data immediately
[ ] Remove it from configs
[ ] Make sure that basal is always in the same format

[ ] Models

[ ] Make a set of models supporting multiple outputs
[ ] Fix the loop model accuracy (?)
[ ] remove tensorflow models?

[ ] Feature scaling technique should be defined in the model configuration
[ ] CLI

[ ] Make sure the CLI is updated to the new refactor
[ ] Update README

[ ] README

[ ] Define input and output formats for each module ("Community Contributions")

[ ] Dependencies: Make sure they are not too strict, and that all dependencies are there
[ ] Code cleanup: Remove all unneccessary.prints and comments in the code.
[ ] Error testing with both windows and mac, and both with pypi and the repo directly
[ ] Add tests
[ ] Add CI (Sam)
[ ] Merge to main
[ ] Push to PyPi
[ ] Check the JOSS checklist

JOSS specifics, last to dos:

[ ] Write good documentation and tests
[ ] Create a branch from the main branch, and add the paper.md with bib there
[ ] Send the paper for review from coauthors
[ ] Check that the paper compiles using github action
[ ] README should contain:

[ ] A statement of need: which problems the software is designed to solve, who the target audience is, and its relation to other work
[ ] installation instructions (pip install ...)
[ ] examples of how to use the software
[ ] API documentation: all functions are documented including example inputs and outputs
[ ] Community guidelines: clear guidelines for third-parties wishing to contribute, report issues or problems, or seek support

[ ] Tests: an automated test suite hooked up to continuous integration (github actions, circle CI or similar)
[ ] Sample dataset: There should be a sample dataset because reviewers are expected to install the software and verify core functionality

Tests:

[ ] Read into unit tests vs integration tests
[ ] Finish testing the cli commands, make sure that all the models are running and so on
[ ] Make unit tests on specific functions

[ ] Determine which functions are called most often by using a profiler
[ ] Test those functions


Support Next.js 15 Compatibility for next-contentlayer

Hi Contentlayer team,
I’m trying to use next-contentlayer with a project that relies on Next.js 15, but I encountered a dependency conflict. It seems<EMAIL_ADDRESS>currently specifies a peer dependency on Next.js versions ^12 || ^13, which prevents installation with Next.js 15.
npm install next-contentlayer

npm error code ERESOLVE
npm error ERESOLVE unable to resolve dependency tree
npm error While resolving<EMAIL_ADDRESS>npm error Found<EMAIL_ADDRESS>npm error node_modules/next
npm error<EMAIL_ADDRESS>from the root project

npm error Could not resolve dependency:
npm error peer next@"^12 || ^13" from<EMAIL_ADDRESS>npm error node_modules/next-contentlayer
npm error<EMAIL_ADDRESS>from the root project
npm error
npm error Fix the upstream dependency conflict, or retry
npm error this command with --force or --legacy-peer-deps

Steps to Reproduce:
1.	Start with a project using Next.js 15.
2.	Run npm install next-contentlayer.
3.	Observe the dependency conflict.
Request:
Could you update the peer dependencies for next-contentlayer to support Next.js 15? This would help users who are upgrading to or working on projects with the latest Next.js version.

Same issue i gett when i upgraded to Next js 15 and React19 rc.
error "[ Server ] Error: Cannot read properties of undefined (reading 'ReactCurrentDispatcher')"

use contentlayer2
for ref :https://github.com/timlrx/contentlayer2

use contentlayer2 for ref :https://github.com/timlrx/contentlayer2

Thank you for the ref, but I just wanna know if they will maintain this project officially to support Next.js 15.


Support EXTRACT_FROM and CONFIG env settings

To help avoid having to push changes just to test rendering:

Extract from repo at EXTRACT_FROM env var if set, rather than the origin remote. Typically this will be the local repo dir and you can use .. when doing make from .render.  Or it could be a different remote URL.
Use config file from CONFIG env var if set, rather than _config.yml. This allows you to override amwa_id, default_tree, etc. locally.

@garethsb going to assume you're ok with this and merge


Make an optional timeout options property on how long to wait until resetting/timing out/trying again

Some kind of watchdog that can detect if it's been at least 1000ms without the buffer's length having grown while expecting foo length message, just reset back to initial state as if we're waiting for the length-prefix of another message from a clean state
Otherwise, if a message fails to be received, when a client retries, it'll just get added to the already stuck message and then it all falls apart from there.

Are you using an unreliable transport stream?

@brandonros I don't quite understand the use case here.
Frame stream assumes the underlying stream is reliable, so doesn't try to cope with timeouts etc.

Sorry, don't want to cope with unreliable carrier stream.


[Feature Request] : Adding animeted Pre Loader

Is there an existing issue for this?

[X] I have searched the existing issues

Feature Description
The new feature is an animated preloader that would display while the website is loading its contents. The preloader would help enhance user experience by providing a smooth and visually appealing loading indicator before the main content of the site is fully rendered.
Use Case

Initial Load Times: Users might experience slight delays due to larger assets or slow networks. The preloader would fill this gap, making the waiting time feel more fluid and professional.
First-Time Users: First-time users of the site may have slower load times as assets like images and scripts are fetched for the first time. The preloader would reassure them that content is being loaded.

Benefits

Improved User Experience: Users won’t be left staring at a blank screen during loading times, which could otherwise lead to frustration or abandonment.
Enhanced Aesthetics: An animated preloader can add a professional touch, maintaining user engagement with an interesting visual instead of a plain loading bar.
Branding Opportunity: The preloader animation can incorporate elements of the website’s branding, such as its logo or color palette, helping to reinforce brand identity.

Add ScreenShots
Below one is sample video
https://github.com/user-attachments/assets/ab4e1fc8-54e5-4c2f-b58a-db67299b32af
Priority
High
Record

[X] I have read the Contributing Guidelines
[X] I'm a GSSOC-EXT contributor
[X] I'm a HACKTOBERFEST contributor
[X] I have starred the repository

@AbhijitMotekar99, this is a good feature enhancement, please go through it and add better animation and share the video of the animation.
Thank you


ASG propagate-tags filter typo - only works as proGagate-tags

custodian version - <IP_ADDRESS>
Typo: proGagated-tags vs proPagated-tags
It looks like the ASG propagated-tags filter actually requires the spelling "progagated-tags." (p => g)
This is shown in the output of "custodian schema asg", but not the documentation or examples.
The incorrect spelling does, happily, seem to work.
Thank you!
POLICY
======

policies:
  - name: asg-delete-if-nonpropagating-tags
    resource: asg
    description: |
       if required tags not set to propagate, delete ASG and notify
    filters:
      - type: propagated-tags
        keys: ["my-special-pony-key", "application-group"]
        match: false
        propagate: true
    actions:
      - *slack
      - type: delete

ERROR
=====

Traceback (most recent call last):
  File "/usr/local/bin/custodian", line 11, in
    sys.exit(main())
  File "/usr/local/lib/python3.7/site-packages/c7n/cli.py", line 357, in main
    command(config)
  File "/usr/local/lib/python3.7/site-packages/c7n/commands.py", line 66, in _load_policies
    collection = policy_load(options, fp, validate=validate, vars=vars)
  File "/usr/local/lib/python3.7/site-packages/c7n/policy.py", line 75, in load
    errors[1], errors[0]))
Exception: Failed to validate on policy asg-delete-if-nonpropagating-tags
 'sandbox-nonpropagating-tag-filters' is not valid under any of the given schemas

Failed validating 'anyOf' in schema[17]['allOf'][1]['properties']['filters']['items']:
    {'anyOf': [{'$ref': '#/definitions/resources/aws.asg/filters/capacity-delta'},
               {'$ref': '#/definitions/resources/aws.asg/filters/config-compliance'},
               {'$ref': '#/definitions/resources/aws.asg/filters/event'},
               {'$ref': '#/definitions/resources/aws.asg/filters/image'},
               {'$ref': '#/definitions/resources/aws.asg/filters/image-age'},
               {'$ref': '#/definitions/resources/aws.asg/filters/invalid'},
               {'$ref': '#/definitions/resources/aws.asg/filters/launch-config'},
               {'$ref': '#/definitions/resources/aws.asg/filters/marked-for-op'},
               {'$ref': '#/definitions/resources/aws.asg/filters/metrics'},
               {'$ref': '#/definitions/resources/aws.asg/filters/network-location'},
               {'$ref': '#/definitions/resources/aws.asg/filters/not-encrypted'},
               {'$ref': '#/definitions/resources/aws.asg/filters/offhour'},
               {'$ref': '#/definitions/resources/aws.asg/filters/onhour'},
               {'$ref': '#/definitions/resources/aws.asg/filters/progagated-tags'},
               {'$ref': '#/definitions/resources/aws.asg/filters/security-group'},
               {'$ref': '#/definitions/resources/aws.asg/filters/subnet'},
               {'$ref': '#/definitions/resources/aws.asg/filters/tag-count'},
               {'$ref': '#/definitions/resources/aws.asg/filters/valid'},
               {'$ref': '#/definitions/resources/aws.asg/filters/value'},
               {'$ref': '#/definitions/resources/aws.asg/filters/vpc-id'},
               {'$ref': '#/definitions/filters/valuekv'},
               {'enum': ['value',
                         'or',
                         'and',
                         'not',
                         'event',
                         'offhour',
                         'onhour',
                         'tag-count',
                         'marked-for-op',
                         'metrics',
                         'config-compliance',
                         'security-group',
                         'subnet',
                         'network-location',
                         'launch-config',
                         'valid',
                         'invalid',
                         'not-encrypted',
                         'image-age',
                         'image',
                         'vpc-id',
                         'progagated-tags',
                         'capacity-delta']}]}

On instance['filters'][1]:
    'sandbox-nonpropagating-tag-filters'

Note "progagated":

               {'$ref': '#/definitions/resources/aws.asg/filters/progagated-tags'},

CHANGE AND TEST
===============
Update this:
filters:
- type: propagated-tags
To this:
filters:
- type: progagated-tags
TEST RESULTS
============

RUNNING IN us-west-2...
2018-09-25 15:09:11,435: custodian.policy:INFO policy: asg-delete-if-nonpropagating-tags resource:asg region:us-west-2 count:13 time:0.88

RUNNING IN us-east-1...
2018-09-25 15:09:13,147: custodian.policy:INFO policy: asg-delete-if-nonpropagating-tags resource:asg region:us-east-1 count:2 time:0.95

MATCHES IN cloud-custodian SOURCE
==============================

$ git grep -i proGagated-tags
c7n/resources/asg.py:@filters.register('progagated-tags')
c7n/resources/asg.py:        'progagated-tags',
docs/source/policy/resources/asg.rst:``progagated-tags``
tests/test_asg.py:                    {"type": "progagated-tags", "keys": ["Tag01", "Tag02", "Tag03"]}
tests/test_asg.py:                        "type": "progagated-tags",
tests/test_asg.py:                        "type": "progagated-tags",
tests/test_asg.py:                        "type": "progagated-tags",
"P"
$ git grep -i proPagated-tags
c7n/resources/asg.py:@filters.register('propagated-tags')
c7n/resources/asg.py:              - name: asg-non-propagated-tags
c7n/resources/asg.py:                  - type: propagated-tags
c7n/resources/asg.py:        aliases=('propagated-tags',),
tests/test_asg.py:                    {"type": "propagated-tags", "keys": ["Tag01", "Tag02", "Tag03"]}
$

==============================

Thanks for the awesome bug report

we'll need to keep the misspelled name for compatibility but we should add in the correct spelling as well.

fixed via https://github.com/capitalone/cloud-custodian/pull/2784 can you pull the latest version of custodian? I'm seeing it show up correctly in the schema

Looks fixed for me - both correct and misspelled filter names work in <IP_ADDRESS>. Thanks a lot!


Tabs : Desktop VS Mobile

Bug, feature request, or proposal:
Probably a bug (?)
What is the current behavior?
Here's my app in desktop mode : (sidenav has a fixed width : 320px)

Notice the way tabs are displayed on the left :

When I open the app on my mobile :

1 or 2 versions of material2 before, tabs where displaying the same way.
I didn't take the time to open this issue before.
What is the expected behavior?
I'd like to have smaller tabs on desktop mode
What are the steps to reproduce?
Here's the funniest part : I tried to reproduce with a Plunkr : http://plnkr.co/edit/aGPvdK8qUL1jEBWXxYn4?p=preview
It's working as expected and not like on my site.
Still, I'm opening this issue in case there's some edge case you may be aware of.
Feel free to close it as I couldn't reproduce.
I didn't apply custom css so I don't understand where this is coming from.
If you really want to repro my problem, you can launch those commands to setup my project and you'll be running the app in a minute :
git clone https://gitlab.com/victornoel/petals-cockpit.git
git checkout ee685d5
cd petals-cockpit/frontend
yarn
ng serve

Then go to http://localhost:4200/workspaces/idWks0
Which versions of Angular, Material, OS, browsers are affected?
Material 2.0.0-beta.1
Ubuntu 16.10
Chromium 55.0.2883.87

This is due to the CSS rule in tab-header.scss:
@media ($md-xsmall) {
  .md-tab-label {
    min-width: 72px;
  }
}

We say that if the screen is small, then the labels should change their min-width from 160px to 72px. I would say that rather than looking at the screen width, we should look at the tab header width instead.
For now to fix your issue, you can set your own custom CSS rule that always sets the min-width as 72px. We will consider how to modify this rule in the library so that it will use the tab header's width rather than the screen.

@andrewseguin I have problems to set the labels width for a specific component.
I tried to define the css class (.md-tab-label) in a css file and defined it for a component via "styleUrls".
But this does not work...
Do you have a suggestion how I am able to do it?

This is an issue with view encapsulation in Angular. The tab component dynamically adds in some of its own templating, and it won't be able to use your CSS defined in your component.
To resolve this, you can either place your styles in a stylesheet outside of your Angular app (this is what I do in my apps), or you can turn off view encapsulation in your component containing the tabs (encapsulation: ViewEncapsulation.None). Both in my opinion are not ideal but it's what we have to work with right now

Additionally, in your case you probably just want to use the md-stretch-tabs feature in tabs: http://plnkr.co/edit/DIjIoK8byvQdaVUsF0Sw?p=preview

@andrewseguin can you explain what would need to be done to close this issue? The problem seems rather undefined / un-reproducible, are you opening a Pr to close this issue?

@andrewseguin md-stretch-tabs not working to stretch tabs in desktop browser with 2.0.0 beta.6 :/

Little fix :

Closing this since I believe it's working as intended; the behavior falls into the category of "do something different on desktop/mobile"


Add some more tests for run_command() function

This PR adds some more tests for st2common.util.green.shell.run_command() function.

It was more I didn't think you could copyright a file with a date earlier than it was created.

Also pushed a change (d19ebac25) which I think should help with occasional unit test failure we see.
TEST RESULT OUTPUT:
======================================================================
1) ERROR: test_service_setup_default_st2_conf_config_is_used (tests.unit.test_service_setup.ServiceSetupTestCase)
----------------------------------------------------------------------
   Traceback (most recent call last):
    virtualenv/lib/python3.6/site-packages/mock/mock.py line 1346 in patched
      return func(*newargs, **newkeywargs)
    st2common/tests/unit/test_service_setup.py line 160 in test_service_setup_default_st2_conf_config_is_used
      run_migrations=False,
    st2common/st2common/service_setup.py line 120 in setup
      config.parse_args(config_args)
    st2common/st2common/config.py line 723 in parse_args
      register_opts()
    st2common/st2common/config.py line 176 in register_opts
      do_register_opts(webui_opts, "webui", ignore_errors)
    st2common/st2common/config.py line 33 in do_register_opts
      cfg.CONF.register_opts(opts, group=group)
    virtualenv/lib/python3.6/site-packages/oslo_config/cfg.py line 1820 in __inner
      result = f(self, *args, **kwargs)
    virtualenv/lib/python3.6/site-packages/oslo_config/cfg.py line 1977 in register_opts
      self.register_opt(opt, group, clear_cache=False)
    virtualenv/lib/python3.6/site-packages/oslo_config/cfg.py line 1824 in __inner
      return f(self, *args, **kwargs)
    virtualenv/lib/python3.6/site-packages/oslo_config/cfg.py line 1961 in register_opt
      return group._register_opt(opt, cli)
    virtualenv/lib/python3.6/site-packages/oslo_config/cfg.py line 1344 in _register_opt
      if _is_opt_registered(self._opts, opt):
    virtualenv/lib/python3.6/site-packages/oslo_config/cfg.py line 574 in _is_opt_registered
      raise DuplicateOptError(opt.name)
   DuplicateOptError: duplicate option: webui_base_url

Per slack - we still see failures and timeouts with some Orquesta integration tests quite often.
Those failures and especially timeouts are rather annoying.
To try to mitigate and improve this situation, I will make the following change and see if it helps - isolate problematic tests and run them separate from other integration tests in a separate process. I will also set reasonable / low timeout for those tests and only try to retry those tests on failure / timeout - this should result in better UX, faster tests and less wasted time re-running CI builds...

Once CI is passing I will merge this into master to see if it's working correctly.
If we still encounter a lot of failures going forward, I will split orquesta integration tests in a new separate workflow. This will allow us to retry just that workflow on timeout / failure. It's not ideal, but better than current status quo / alternatives (wasting tons of time on re-runs).

Alright, orquesta integration tests now run as part of a separate workflow.
Hopefully in the future we will also be able to track and and fix actual race conditions so we can merge everything back into a single workflow again (and get rid of some duplication).
/cc @m4coder - can you please dig into those tests when you get a chance (st2tests/integration/orquesta). I did dig in a bit a while back, but without much success. You can find a bunch of examples of failures and timeouts due to race conditions in Travis and GHA build run logs.

I'll merge this since nightly CI is failing now daily and I think this should help with that (at the very least just Orquesta workflow will fail).


Geometry Cache: develop input file format (lossless)

Each file must contain:

Animation start/end.
Frame rate.
Number of frames.
Total number of triangles.
Total number of materials.
Total number of subsets. Subset is a range of triangles associated with particular material and index of visibility track.
Each triangle is defined by three indices.
Each vertex contains:

position (3 float),
normal (3 half),
color (4 half),
texture coordinate (2 float)

https://github.com/demiurghg/FusionEngine/wiki/Geometry-Cache


src: configured and lint fix on bin/cli.js

Connects to #23

Coverage remained the same at 95.652% when pulling 7ed7180a0d5d3de4c38ea286d7e0f44319c86eb4 on helio-frota:licenser-23 into c51b0699ea21d79b71aa5841c3707108a2f1a903 on bucharest-gold:master.


[WIP]Complete some todos added during reviewing code.

[x] Miners -> MinerList

[x] MappingKeyExtensions. To simplify ByteString.CopyFrom(ByteArrayHelper.FromHexString(hex)).

[x] Add view methods for blockchain browser.

[x] Fix a bug about TokenContract.Lock

[x] Use seconds in contracts in stead of days / months etc. Remove BaseTimeUnit in consensus contract.

:white_check_mark: Build AElf <IP_ADDRESS>1 completed (commit https://github.com/AElfProject/AElf/commit/4cee535b43 by @EanCuznaivy)

:x: Build AElf <IP_ADDRESS>8 failed (commit https://github.com/AElfProject/AElf/commit/eb16dbd416 by @EanCuznaivy)

:x: Build AElf <IP_ADDRESS>1 failed (commit https://github.com/AElfProject/AElf/commit/46fcba206d by @EanCuznaivy)

:x: Build AElf <IP_ADDRESS>1 failed (commit https://github.com/AElfProject/AElf/commit/9d14c18510 by @EanCuznaivy)

:x: Build AElf <IP_ADDRESS>3 failed (commit https://github.com/AElfProject/AElf/commit/d797021b98 by @EanCuznaivy)

:x: Build AElf <IP_ADDRESS>7 failed (commit https://github.com/AElfProject/AElf/commit/b7240b514c by @EanCuznaivy)

:x: Build AElf <IP_ADDRESS>9 failed (commit https://github.com/AElfProject/AElf/commit/4e06dbdc6a by @EanCuznaivy)

:x: Build AElf <IP_ADDRESS>0 failed (commit https://github.com/AElfProject/AElf/commit/a3b46ff875 by @EanCuznaivy)

:white_check_mark: Build AElf <IP_ADDRESS>8 completed (commit https://github.com/AElfProject/AElf/commit/ed8a890245 by @EanCuznaivy)


Integration scale subresource not working with Knative trait enabled

The Camel K integration custom resource enables the scale subresource in order to provide auto scaling and resource scaling e.g. via using the kubectl scale command
As soon as the Knative trait is enabled and the Integration uses a Knative service on top of the Deployment this scaling mechanism is not working anymore.
The result of scaling the Integration custom resource is a new revision of the Knative service instead of a proper scaling.
Reproduced with Camel K 1.10.x

@squakez @astefanutti FYI

Thanks for reporting. I am not sure if that is kind of expected. I mean, when we set a knative service trait, it would be supposed the user to scale via the trait as well.

It sounds similar to the discussion raised at #3132.

The current logic forces Knative auto-scaling to comply with the user-provided replicas count, by explicitly setting the  autoscaling.knative.dev/minScale and autoscaling.knative.dev/maxScale annotations to be equal to the specified replicas count.
This logic has been implemented a long time ago, even before KEDA came out, and I don't think there is an e2e test for it. So it's possible it does not behave correctly anymore.
That being said, following the discussions from #2838 and #3132, I'm starting to think that approach may not be correct, and incompatible with auto-scaler implementations. In practice, it seems they make the assumption they own the control of the scale sub-resource, which is probably a fair assumption, even from the end-user standpoint, as @squakez pointed out. So in that spirit, an option could be to remove the obsolete logic and document that auto-scaling and manual scaling are mutually exclusive.


[CI] Set integration test to use mirror_registry

Also update collection to inherit new Mirror Registry changes
Description
This change in the collection makes it easier to test the OpenShift Mirror Registry with a full workflow, including installation of OpenShift from these sources. There are some extra changes exposing a few more variables to make it easier to test some alternate scenarios as well, including changes to the location of the release images for OSUS.
Type of change
Please delete options that are not relevant.

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

How Has This Been Tested?
/test integration
Checklist:

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[x] My changes generate no new warnings
[x] I have added tests that prove my fix is effective or that my feature works
[x] New and existing unit tests pass locally with my changes
[x] Any dependent changes have been merged and published in downstream modules

/test integration

@afflom See above. Integration test on OpenShift Mirror Registry as the new default. Logs available in the attached artifacts on the integration job.


Autocompletion error (non implemented)

If I edit an .mmp file, I get this error
[Error - 5:08:09 PM] Request textDocument/completion failed.
Message: Not implemented
Code: -32601
I'm pretty sure it is because the server adverts that feature, but it's actually not implemented.
Just to let you know

Yes! This one is an easy fix.


forcing mailservers security value to be always upper case

e.g. [using SSLAUTO|SSLV2|SSLV3|TLSV1|TLSV11|TLSV12]

:+1: :clap:

resolved in https://github.com/bbg-cookbooks/monit-ng/pull/12


Feature/907 dpkg origin gardenlinux

How to categorize this PR?
/kind enhancement
/area os
/os garden-linux
What this PR does / why we need it:
This PR changes the default vendor from Debian to GardenLinux. GardenLinux is not Debian, but a Debian Derivative.
Which issue(s) this PR fixes:
Fixes #907
Release note:
NONE

There's probably no further need for /etc/dpkg/origins/debian after linking to /etc/dpkg/origins/gardenlinux. Therefore, we should remove the Debian related one.

I am currently checking with other deriviatives. I currently tend to leave  /etc/dpkg/origins/debian untouched in the images, as Debian is listed as the parent distribution.

There's probably no further need for /etc/dpkg/origins/debian after linking to /etc/dpkg/origins/gardenlinux. Therefore, we should remove the Debian related one.

I am currently checking with other deriviatives. I currently tend to leave /etc/dpkg/origins/debian untouched in the images, as Debian is listed as the parent distribution.

Looks like the most ones still include the Debian related one. So, nvm :)


About Us section is clumsy

@Anuj3553
About Us section has so many issues
I would like to enhance it
Kindly assign it to me
https://github.com/user-attachments/assets/d0c15473-4d5f-4d98-9447-04ff85e217d9

Hyy @AswaniBolisetti, I'm assigning this issue to you.


FireFox DTLS issue

I can't recall if I ever tested Firefox before, so I'm unsure if this is a regression in Werift or behavior change in Firefox.
When attempting to connect a peer connection with a Firefox browser, werift fails during dtls handshaking with:
' ContentType.alert [object Object] BadCertificate flight 5 lastFlight [object Object]'
I'll see if I can fix this, but figured I'd give you a heads up first in case you know what the issue is.

alert:
Alert {level: 2, description: 42}

dlls.lastFlight
(1) [Finished]
0:
Finished {verifyData: Buffer(12), msgType: 20, messageSeq: 4}
messageSeq:
4
msgType:
20
verifyData:
Buffer(12) [229, 131, 115, 13, 50, 130, 204, 215, 101, 26, 28, 178, buffer: ArrayBuffer(8192), byteLength: 12, byteOffset: 3488, length: 12, Symbol(Symbol.toStringTag): 'Uint8Array']
0:
229
1:
131
2:
115
3:
13
4:
50
5:
130
6:
204
7:
215
8:
101
9:
26
10:
28
11:
178


Why k is used in loss?

Hi, I wonder why k is used to compute the gauss probability in the loss function

Hi, I wonder why k is used to compute the gauss probability in the loss function

Hi, @ZRJMoon , I'm confused about this, could you give me an explanation?
And I think this constant term is useless for optimization?


Duplicated player names

Config.yml
tab_groups.yml

Hi is your a cracked setup?

Hi is your a cracked setup?

I'm using librelogin, and online mode is off since the login is made by velocity. Premium users join directly to the server

Could you join HuskHelp, there we will be able to give you a better support. Thanks

Hi is your a cracked setup?

I'm using librelogin, and online mode is off since the login is made by velocity. Premium users join directly to the server


Map won't load

When I go to {hostname}/worldmap, the map starts to load (I have the top bar with the menu button) but the main content remains white.
I have the following error in the console:
(index):1021 Uncaught SyntaxError: Unexpected token
The culprit seems to be line with a missing opening parenthesis
opts.size = opts.size - 30) / 2 + 30;
worldmap version: 1.3.7
Note that the flow library and NPM sites indicate a 1.3.8 version, but it's not available from the Node-Red GUI palette

yes you need 1.3.8. maybe stop and restart Node-RED - or install in manually.

Can you please re-open ?
I have installed 1.3.8, restard node-red as the UI recommended,  I still have the same issue
FYI,I'm using the demo flow from the flow library:
https://flows.nodered.org/node/node-red-contrib-web-worldmap

try flushing your browser cache - ctrl-r reload.


homebrew/apache/mod_fastcgi fails to load in apache (and warnings during install)

During installation of mod_fastcgi --with-homebrew-httpd24 5 warnings are thrown:
$ brew -v install mod_fastcgi --with-homebrew-httpd24
==> Installing mod_fastcgi from homebrew/apache
==> Downloading https://dl.bintray.com/homebrew/mirror/mod_fastcgi-2.4.6.tar.gz
Already downloaded: /Users/klaasvanderweij/Library/Caches/Homebrew/mod_fastcgi-2.4.6.tar.gz
==> Verifying mod_fastcgi-2.4.6.tar.gz checksum
tar xzf /Users/klaasvanderweij/Library/Caches/Homebrew/mod_fastcgi-2.4.6.tar.gz
==> Downloading https://raw.githubusercontent.com/ByteInternet/libapache-mod-fastcgi/byte/debian/patches/byte-compile-against-apache24.diff
Already downloaded: /Users/klaasvanderweij/Library/Caches/Homebrew/mod_fastcgi--patch-e405f365fac2d80c181a7ddefc9c6332cac7766cb9c67c464c272d595cde1800.diff
==> Verifying mod_fastcgi--patch-e405f365fac2d80c181a7ddefc9c6332cac7766cb9c67c464c272d595cde1800.diff checksum
==> Patching
==> Applying byte-compile-against-apache24.diff
/usr/bin/patch -g 0 -f -p1 -i /private/tmp/mod_fastcgi--patch-20161013-3670-13cxt4m/byte-compile-against-apache24.diff
patching file fcgi.h
Hunk #3 succeeded at 362 (offset -13 lines).
patching file mod_fastcgi.c
Hunk #2 succeeded at 2971 (offset -47 lines).
==> /usr/local/opt/httpd24/bin/apxs -o mod_fastcgi.so -c *.c
/usr/local/opt/apr/libexec/build-1/libtool --silent --mode=compile clang -prefer-pic   -DDARWIN -DSIGPROCMASK_SETS_THREAD_MASK -DDARWIN_10 -g -O2 -I/usr/local/Cellar/httpd24/2.4.23_2/include/httpd  -I/usr/local/opt/apr/libexec/include/apr-1   -I/usr/local/opt/apr-util/libexec/include/apr-1   -c -o fcgi_buf.lo fcgi_buf.c && touch fcgi_buf.slo
/usr/local/opt/apr/libexec/build-1/libtool --silent --mode=compile clang -prefer-pic   -DDARWIN -DSIGPROCMASK_SETS_THREAD_MASK -DDARWIN_10 -g -O2 -I/usr/local/Cellar/httpd24/2.4.23_2/include/httpd  -I/usr/local/opt/apr/libexec/include/apr-1   -I/usr/local/opt/apr-util/libexec/include/apr-1   -c -o fcgi_config.lo fcgi_config.c && touch fcgi_config.slo
fcgi_config.c:769:48: warning: format specifies type 'long' but the argument has type 'gid_t' (aka 'unsigned int') [-Wformat]
            s->group = ap_psprintf(tp, "#%ld", fcgi_util_get_server_gid(cmd->server));
                                         ~~~   ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
                                         %u
fcgi_config.c:774:46: warning: format specifies type 'long' but the argument has type 'uid_t' (aka 'unsigned int') [-Wformat]
            s->user = ap_psprintf(p, "#%ld", fcgi_util_get_server_uid(cmd->server));
                                       ~~~   ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
                                       %u
fcgi_config.c:962:48: warning: format specifies type 'long' but the argument has type 'gid_t' (aka 'unsigned int') [-Wformat]
            s->group = ap_psprintf(tp, "#%ld", fcgi_util_get_server_gid(cmd->server));
                                         ~~~   ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
                                         %u
fcgi_config.c:967:46: warning: format specifies type 'long' but the argument has type 'uid_t' (aka 'unsigned int') [-Wformat]
            s->user = ap_psprintf(p, "#%ld", fcgi_util_get_server_uid(cmd->server));
                                       ~~~   ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
                                       %u
4 warnings generated.
/usr/local/opt/apr/libexec/build-1/libtool --silent --mode=compile clang -prefer-pic   -DDARWIN -DSIGPROCMASK_SETS_THREAD_MASK -DDARWIN_10 -g -O2 -I/usr/local/Cellar/httpd24/2.4.23_2/include/httpd  -I/usr/local/opt/apr/libexec/include/apr-1   -I/usr/local/opt/apr-util/libexec/include/apr-1   -c -o fcgi_pm.lo fcgi_pm.c && touch fcgi_pm.slo
/usr/local/opt/apr/libexec/build-1/libtool --silent --mode=compile clang -prefer-pic   -DDARWIN -DSIGPROCMASK_SETS_THREAD_MASK -DDARWIN_10 -g -O2 -I/usr/local/Cellar/httpd24/2.4.23_2/include/httpd  -I/usr/local/opt/apr/libexec/include/apr-1   -I/usr/local/opt/apr-util/libexec/include/apr-1   -c -o fcgi_protocol.lo fcgi_protocol.c && touch fcgi_protocol.slo
fcgi_protocol.c:449:55: warning: format specifies type 'int' but the argument has type 'unsigned long' [-Wformat]
                            fr->fs_path, fr->dataLen, sizeof(FCGI_EndRequestBody));
                                                      ^~~~~~~~~~~~~~~~~~~~~~~~~~~
/usr/local/Cellar/httpd24/2.4.23_2/include/httpd/http_log.h:448:44: note: expanded from macro 'ap_log_rerror'
#define ap_log_rerror(...) ap_log_rerror__(__VA_ARGS__)
                                           ^~~~~~~~~~~
/usr/local/Cellar/httpd24/2.4.23_2/include/httpd/http_log.h:451:63: note: expanded from macro 'ap_log_rerror__'
             ap_log_rerror_(file, line, mi, level, status, r, __VA_ARGS__); \
                                                              ^~~~~~~~~~~
1 warning generated.
/usr/local/opt/apr/libexec/build-1/libtool --silent --mode=compile clang -prefer-pic   -DDARWIN -DSIGPROCMASK_SETS_THREAD_MASK -DDARWIN_10 -g -O2 -I/usr/local/Cellar/httpd24/2.4.23_2/include/httpd  -I/usr/local/opt/apr/libexec/include/apr-1   -I/usr/local/opt/apr-util/libexec/include/apr-1   -c -o fcgi_util.lo fcgi_util.c && touch fcgi_util.slo
/usr/local/opt/apr/libexec/build-1/libtool --silent --mode=compile clang -prefer-pic   -DDARWIN -DSIGPROCMASK_SETS_THREAD_MASK -DDARWIN_10 -g -O2 -I/usr/local/Cellar/httpd24/2.4.23_2/include/httpd  -I/usr/local/opt/apr/libexec/include/apr-1   -I/usr/local/opt/apr-util/libexec/include/apr-1   -c -o mod_fastcgi.lo mod_fastcgi.c && touch mod_fastcgi.slo
/usr/local/opt/apr/libexec/build-1/libtool --silent --mode=link clang    -o mod_fastcgi.la  -rpath /usr/local/Cellar/httpd24/2.4.23_2/libexec -module -avoid-version    mod_fastcgi.lo fcgi_util.lo fcgi_protocol.lo fcgi_pm.lo fcgi_config.lo fcgi_buf.lo
==> Cleaning
==> Finishing up
==> Caveats
You must manually edit /usr/local/etc/apache2/2.4/httpd.conf to contain:
  LoadModule fastcgi_module /usr/local/Cellar/mod_fastcgi/2.4.6/libexec/mod_fastcgi.so

Upon restarting Apache, you should see the following message in the error log:
  [notice] FastCGI: process manager initialized

NOTE: If you're _NOT_ using --with-homebrew-httpd22 or --with-homebrew-httpd24 and having
installation problems relating to a missing `cc` compiler and `OSX10.12.xctoolchain`,
read the "Troubleshooting" section of https://github.com/Homebrew/homebrew-apache
==> Summary
🍺  /usr/local/Cellar/mod_fastcgi/2.4.6: 5 files, 127.6K, built in 4 seconds

Upon restarting apachectl which loads fastcgi_module /usr/local/Cellar/mod_fastcgi/2.4.6/libexec/mod_fastcgi.so I get the following error:
httpd: Syntax error on line 129 of /usr/local/etc/apache2/2.4/httpd.conf: Cannot load libexec/mod_proxy_fcgi.so into server: dlopen(/usr/local/opt/httpd24/libexec/mod_proxy_fcgi.so, 10): Symbol not found: _proxy_module\n  Referenced from: /usr/local/opt/httpd24/libexec/mod_proxy_fcgi.so\n  Expected in: flat namespace\n in /usr/local/opt/httpd24/libexec/mod_proxy_fcgi.so

I suspect the warnings during install are related to the failure of loading the mod_proxy_fcgi.so.
Am I doing something wrong, or is this a bug that can be fixed or that I can fix? All help appreciated.

You are using the wrong path in your httpd.conf and the filename is incorect. The fastcgi module should be located in /usr/local/opt/mod_fastcgi/ and not in the http directory as the error states.

Hi @javian,
Thanks for the feedback, I have indeed loaded a different/invalid module because I had overlooked the brew info of mod_fastcgi which state to add the following line:
LoadModule fastcgi_module /usr/local/Cellar/mod_fastcgi/2.4.6/libexec/mod_fastcgi.so

This works, so this raised issue can be closed.
Jan, bedankt!


[C++] Using std::from_chars instead of std::atoi?

Describe the enhancement requested
Now, arrow has shift to C++17.
I've seen code like:
  try {
    return std::max(0, std::stoi(str));
  } catch (...) {
    return 0;
  }

Can we use std::from_chars to do the conversion?
Component(s)
C++

One concern is that the compiler support for std::from_chars was later than most c++17 features [1]. So you may also want to update [2] as well since it is not supported by gcc 7.
[1] https://en.cppreference.com/w/cpp/compiler_support/17 Search "Elementary string conversions"
[2] https://arrow.apache.org/docs/developers/cpp/building.html "On Linux, gcc 7.1 and higher should be sufficient"

Given the limitations we've had to work around in std::to_chars, we'd probably like to avoid this indeed.

@js8544 @pitrou I notice that [1] is partial support, "FP" is not support now. Could we just use this for integer first?

I've submit a tiny patch in https://github.com/apache/arrow/pull/37265 , would you mind trigger the CI and have a try?

Oh I found gcc libstdc++ support it in 8, so I cannot try this, what a pity. I'll reopen this until we don't support gcc7


[bug]: Sorting by date is still broken

Describe the Bug
Hi,
Yesterday after you made it works again, I thought for a second that the sorting by date is working properly again but unfortunatly it is not... If you accept PR I will do the editing myself
Steps to reproduce the behavior
Click over the sort by date on the header of the list and the sorting isn't working as expected, the years are scrambled...
Browser
Edge
Type
Userscript
URL
x.com

Fixed as of v6.7.0
https://github.com/magicoflolis/Userscript-Plus/releases/tag/6.7.0

Hi,
For some reasons the problem still persists, I tried to reset everything but the dates aren't sorted properly, it seems that it works at but when you scroll you will see that many scripts are from older dates that show among some recent ones... Should I do something specific on my side to get the sorting work as expected?


Range manager exists uses cache to verify that metarange exists

Graveler range manager calls the cache to check if 'id' exists.
We use this call to verify that a meta-range id exists while adding a commit.
My concern is that we can't assume that the data we just wrote will be available in the cache - the manager can use the cache for a quick check but still check the adapter/fs to the meta-range.
func (m *RangeManager) Exists(ctx context.Context, ns committed.Namespace, id committed.ID) (bool, error) {
   return m.cache.Exists(ctx, string(ns), id)
}

I don't believe this is actually true, it's more a matter of horrible naming (sorry).  What really happens is that a sstable Cache is created that directly tests "exists" on the backing store, https://github.com/treeverse/lakeFS/blob/93e8ebca846a709f22ba1134c0a4dcd1fc9e0c38/graveler/sstable/cache.go#L71.
Re-assigning in the hope you agree and we can close.  Or (even better!) suggest less confusing naming!

I don't believe this is actually true, it's more a matter of horrible naming (sorry).  What really happens is that a sstable Cache is created that directly tests "exists" on the backing store, https://github.com/treeverse/lakeFS/blob/93e8ebca846a709f22ba1134c0a4dcd1fc9e0c38/graveler/sstable/cache.go#L71.
Re-assigning in the hope you agree and we can close.  Or (even better!) suggest less confusing naming!

yes, the naming is very confusing - as cache.Exists doesn't really check the cache.
will have to align the noCache implementation to this spec and close this one.

yes, the naming is very confusing - as cache.Exists doesn't really check the cache.
will have to align the noCache implementation to this spec and close this one.


[v1] (Possible) checks to be added

Feel free to discuss and vote with your thumbs.

"should add a warning when Popper.js isn't imported, except if they use the bundle file" (suggestion from Johann-S in https://github.com/twbs/bootlint/pull/419#pullrequestreview-156319666)

Check for Bootstrap 3 classes: For a quick-and-dirty attempt see https://github.com/Herst/bootlint-ng/blob/v4-old-attempt/src/bootlint.js#L316

Input-group minutiae like .custom-select required to make <select>s to work, see #423 (replacement for E006)

Multiple inputs in an input-group only partly working, see #423 and https://getbootstrap.com/docs/4.1/components/input-group/#multiple-inputs, a case for a warning? (replacement in E010)

Tests for .card-group/.card-deck/.card-columns and making sure that .card-title/.card-subtitle are added to a <h*> and .card-link to <a> elements (#425).

#189

#356