Import Failed

Import failed
Details
Created: Item "Temp chip2 chain8" on "AntMiner".
Created: Item "GH/S (RT)" on "AntMiner".
Created: Item "Temp chip2 chain7" on "AntMiner".
Created: Item "Temp chip2 chain6" on "AntMiner".
Created: Item "Fan 6" on "AntMiner".
Created: Item "Fan 3" on "AntMiner".
Incorrect item key "antiminer-zbx-chk["{HOST.CONN}", "{$HOST.PORT}", "{$HTTP.USERNAME}", "{$HTTP.PASSWORD}", "devs.0.freq.temp2_7"]" provided for trigger expression on "AntMiner".

Issue has been solved i changed antiminer-zbx-chk to antminer-zbx-chk. But i still did not see the data in Graph. Instruction is not clear .
"Make antminer-zbx-chk executable (chmod +x check_dnsbl.sh)"
need to change file name to "check_dnsbl.sh" ?

fixed

in template xml found 2 "antiminer" and 1 "antimner" today
best reagrds

@Saigets thank you, fixed too.


can't import geoviews in Python 3.5

I am trying to use geoviews in Mac OS X 10.7.5.  Because of this elderly OS, I have to use Anaconda 4.2 and Python 3.5 rather than the most recent versions.  Installing geoviews goes fine, but I can't use it.  Here's the error:
(py35) ELD-MacBook-Pro:Desktop EDobbins$ conda install -c conda-forge -c ioam holoviews geoviews
Fetching package metadata .............
Solving package specifications: .

Package plan for installation in environment /Users/EDobbins/anaconda2/envs/py35:

The following NEW packages will be INSTALLED:

    cartopy:   0.15.1-np111py35_2 conda-forge
    geos:      3.5.1-1            conda-forge
    geoviews:  1.3.0-py35_0       ioam
    holoviews: 1.8.1-py35_0       conda-forge
    lancet:    0.9.0-py35_0       conda-forge
    owslib:    0.14.0-py35_0      conda-forge
    param:     1.5.1-py35_0       conda-forge
    proj4:     4.9.3-4            conda-forge
    pyepsg:    0.3.2-py35_0       conda-forge
    pyproj:    <IP_ADDRESS>-py35_0     conda-forge
    pyshp:     1.2.11-py35_0      conda-forge
    shapely:   1.5.17-py35_4      conda-forge

Proceed ([y]/n)? y

param-1.5.1-py 100% |#############################################################| Time: 0:00:00 247.38 kB/s
lancet-0.9.0-p 100% |#############################################################| Time: 0:00:00 182.13 kB/s
holoviews-1.8. 100% |#############################################################| Time: 0:00:02   1.67 MB/s
(py35) ELD-MacBook-Pro:Desktop EDobbins$ python
Python 3.5.2 |Anaconda 4.2.0 (x86_64)| (default, Jul  2 2016, 17:52:12)
[GCC 4.2.1 Compatible Apple LLVM 4.2 (clang-425.0.28)] on darwin
Type "help", "copyright", "credits" or "license" for more information.
>>>  import geoviews

ParseException: Unexpected EOF parsing WKB
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/Users/EDobbins/anaconda2/envs/py35/lib/python3.5/site-packages/geoviews/__init__.py", line 9, in <module>
    from .element import (_Element, Feature, Tiles,     # noqa (API import)
  File "/Users/EDobbins/anaconda2/envs/py35/lib/python3.5/site-packages/geoviews/element/__init__.py", line 3, in <module>
    from .geo import (_Element, Feature, Tiles, is_geographic,     # noqa (API import)
  File "/Users/EDobbins/anaconda2/envs/py35/lib/python3.5/site-packages/geoviews/element/geo.py", line 3, in <module>
    from cartopy import crs as ccrs
  File "/Users/EDobbins/anaconda2/envs/py35/lib/python3.5/site-packages/cartopy/__init__.py", line 24, in <module>
    import shapely.speedups
  File "/Users/EDobbins/anaconda2/envs/py35/lib/python3.5/site-packages/shapely/speedups/__init__.py", line 3, in <module>
    from shapely.geometry import linestring, polygon
  File "/Users/EDobbins/anaconda2/envs/py35/lib/python3.5/site-packages/shapely/geometry/__init__.py", line 4, in <module>
    from .base import CAP_STYLE, JOIN_STYLE
  File "/Users/EDobbins/anaconda2/envs/py35/lib/python3.5/site-packages/shapely/geometry/base.py", line 169, in <module>
    EMPTY = deserialize_wkb(a2b_hex(b'010700000000000000'))
  File "/Users/EDobbins/anaconda2/envs/py35/lib/python3.5/site-packages/shapely/geometry/base.py", line 110, in deserialize_wkb
    "Could not create geometry because of errors while reading input.")
shapely.geos.ReadingError: Could not create geometry because of errors while reading input.

Do I have any options here?  Is this a known error that can be fixed?
Thanks for any hints.

Looks like an error in shapely. Maybe try installing an earlier version? We'll have to pin a particular version if this remains an issue.

Based on that idea, I tried a whole bunch
shapely 1.4 and 1.5.0 - nope cause needs python2.7
1.5.16 and 1.5.15 installed OK but didn't solve the problem.
1.5.14 I haven't been able to find:  "Package missing in current osx-64 channels"
1.5.13 downgraded a bunch of other packages while installing, and ended up with a different error message regarding pandas.
Obvious solution would be to upgrade the whole system.  But I'm willing to try other ideas.


Keep the assocty section when emitting reflection metadata for debugging

LLDB needs the Associated Type section to work. For example, it's needed to simply break in the indicated line in the code below:
protocol Foo {
  associatedtype T
}

extension Foo {
  func foo(_ things: [T]) {
    // Break here
    for thing in things { print(thing) }
  }
}

struct Test: Foo {
  typealias T = Int
}

func main() {
  Test().foo([0,1,2,3])
}

main()

@swift-ci smoke test

@swift-ci smoke test


pipelineX Refactor code and complete debug string

Proposed changes
Issue Number: close #xxx

Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

run buildall


Default Statement::bindParam $length to 0, as using null causes a deprecation with PHP8+

When using PHP8+ with Doctrine DBALv2 and calling PDOStatement::bindParam() with just 2 params causes a deprecation for passing null to an int param. The default in PDO is 0, so this change defaults to 0 when calling the decorated statement.
Fixes #611

Thank you for taking the time to contribute this change! Besides adding an entry to the CHANGELOG, I just have a doubt about why the current solution does not work: if you call bindParam with up to 3 params, the array_slice should return an empty array, and the same thing should happen here. As a consequence of this, PHP should fallback to the default value for the $length param thinking

We don't run Sentry on our dev environments, and we have been unable to replicate this issue without Sentry enabled. I'm not sure why the DBAL PDOStatement is working fine but the Sentry TracingStatementv2 isn't.
I haven't done any in-depth exploration, but it appears to me that the default null on the tracing statement bindParam method becomes the default if it's not explicitly passed in. This then is passed to the DBALv2 Statement which simply extends PDOStatement. With <PHP8.1 it works fine (I guess PHP implicitly casts it to 0 or ignores it & uses the PDOStatement default), but under PHP8.1 with the changes to deprecate passing null to non-nullable internal function parameters (https://www.php.net/releases/8.1/en.php) the null is triggering the deprecation.

@ste93cry I think I've found the smoking gun: the array_slice offset appears to be wrong! https://3v4l.org/7NhQT#v8.1.4

@ste93cry I deleted my previous comment as it was wrong. Here's an example showing how the explicit null triggers the deprecation, but not providing the param doesn't: https://3v4l.org/biaIs#v8.1.4. I'm still not sure why the deprecation is being triggered in Sentry.

Can we add a unit test to trigger the deprecation in our CI? Or is it already there, and then why it's not failing?

the explicit null triggers the deprecation, but not providing the param doesn't

That's the expected behaviour. If you explicitly pass null, then it's up to you to know that you will trigger a deprecation. Silly question: are you sure that there is no other code that pass that param explicitly?

@ste93cry My point was that the explicit null triggers the deprecation, when not using Sentry, so it's not a side-effect of the code.
<?php

declare(strict_types=1);

use Doctrine\DBAL\Driver\Connection;
use Psr\Container\ContainerInterface;

class aClass
{
    public function __construct(ContainerInterface $container, Connection $connection)
    {
        parent::__construct($container);

        $this->connection = $connection;
    }

    public function aMethod($applicationAverageTime) {
        $statement = $this->connection->prepare('...');
// ...
        $statement->bindParam(':applicationAverageTime', $applicationAverageTime); // <---
// ...
    }
}

that's the line that our last deprecation was triggered on, we don't tend to even use the type.

Sorry for being silent. I reproduced the issue locally, and I found out that the problem originates from here. Basically, since the statement is wrapped by our TracingStatementForV2 class, the instanceof PDOStatement returns false. Then, the $length parameter is explicitly passed to the bindParam method with a null value and this triggers the deprecation. I would say that the check in the DBAL is pretty weak as-is, and should be changed to take into account the fact that the statement could be wrapped. Anyway, your fix is good, so if you are willing to fix the requested changes I would happily merge this PR.


Api support for robots?

Hey, I recently started playing with the kucoin bots, and I'd like to access the robots data via API to create some charts. (And perform actions too if that would be possible). The code would be open sourced BTW.
Is adding the robots data to the API in the plans?
Thanks.

Our latest available API can be found in this documentation: https://www.kucoin.com/docs/beginners/introduction. Currently, robots API service is not yet available, so please stay tuned.


Validate MinCount and MaxCount of Instance Pool

MinCount <= MaxCount
If the role is stateful then (MinCount == MaxCount), if only one of the two values are set, we should default to the other
Adds tests -> instance_pool_test.go
fixes #27

What this PR does / why we need it:
Validates minCount and maxCount of instance pool, adds tests for logic
Which issue this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close that issue when PR gets merged): fixes # 27
Special notes for your reviewer:
Release note:

Validate minCount and maxCount of Instance Pool

/assign @simonswine

/ok-to-test

/approve
/lgtm


GUI won't open

I'm pressing shift + home and nothing opens, even on vanilla game. I use ENB and sse display tweaks, engine fixes, pretty basic vanilla setup to check the problematic mods. I use 60% keyboard, so i use FN key to activate home key.

Can you check the ImprovedCameraSE.log it is located:
C:\Users\USERNAME\Documents\My Games\Skyrim Special Edition\SKSE
See if there are any tell tale signs of the menu being disabled.
You can change the key to something else:
Virtual Key Codes

Having the same issue. Heres the log:
Improved Camera AE v1.0.0
[14/01/23 20:36:04] FileSystem Loading...
[14/01/23 20:36:04]   m_ApplicationPath:		D:\SteamLibrary\steamapps\common\Skyrim Special Edition
[14/01/23 20:36:04]   m_PluginPath:			D:\SteamLibrary\steamapps\common\Skyrim Special Edition\Data\SKSE\Plugins
[14/01/23 20:36:04] ConfigSystem Loading...
[14/01/23 20:36:04]   m_ConfigPath:			D:\SteamLibrary\steamapps\common\Skyrim Special Edition\Data\SKSE\Plugins\ImprovedCameraAE
[14/01/23 20:36:04]   m_ConfigName:			ImprovedCameraAE.ini
[14/01/23 20:36:04]   m_ConfigFile:			D:\SteamLibrary\steamapps\common\Skyrim Special Edition\Data\SKSE\Plugins\ImprovedCameraAE\ImprovedCameraAE.ini
[14/01/23 20:36:04]   ReadSettings():			OK
[14/01/23 20:36:04] ConfigSystem Loaded.
[14/01/23 20:36:04]   m_ApplicationName:		SkyrimSE.exe
[14/01/23 20:36:04]   m_ApplicationVersion:		1.6.353.0
[14/01/23 20:36:04]   m_ApplicationBaseAddress:		0x00007FF7170E0000
[14/01/23 20:36:04]   m_ApplicationImageSize:		0x00000000037A3000
[14/01/23 20:36:04] FileSystem Loaded.
[14/01/23 20:36:04] Checking for compatibility issues...
[14/01/23 20:36:04]   platform_se v<IP_ADDRESS> detected without ReShade installed, menu disabled.
[14/01/23 20:36:04] Finished checking for compatibility issues.
[14/01/23 20:36:28] WindowSystem Loading...
[14/01/23 20:36:28] WindowSystem not Loaded:		Menu is disabled (0)

@Inspiredbubbles
Menu is disabled with explanation in the log.
[14/01/23 20:36:04] platform_se v<IP_ADDRESS> detected without ReShade installed, menu disabled.

Thank you for the quick answer!
To be honest I did see that, but the menu used to work with my mod settings, with ENB installed.
From the last time I checked (1-2 weeks ago) the menu was working.
Yesterday I did install a few mods with the goal to add more combat movements (MCO and related mods). I also added the True diretional movement but I have removed all of them (I had a clean save where I could restart the game without these mods installed).
I tried also to reinstall the ImprovedCamera and yet could not have the GUI to open.
Luckily I have pretty much the Improved Camera settings according to my needs, so it won't disturb this run (but still bugs me a bit as it shows it might have some incompatibility somewhere??). I have now invested too many hours to start a new game haha
Anyway, I really like your mod. I found it on reddit post as an alternative to Joy of Alternative and it worked like a charm!
THank you once again!
PS: I am aware of SSEdit (or TESEdit, etd) to check for the incompatibilities but again - I am a bit of a noobie when it comes to these more technical aspects so I always get confused on how to properly use (most of manuals I found on google are not the most clear to me...)

The next release shall require ReShade... as there are too many issues due to Steam Overlay which cannot be shutoff :(
The NG release I'll just hook Skyrim's renderer so shouldn't need to worry about external mods/tools.

Hi, Sorry to reopen this thread but I am a bit confused.
If I understood correctly the reason the GUI is not loading is due the fact there is no ReShade, correct? If that is the case, how come then it used to work normally? I never installed reshade, and I have been using always the same version of your mod? Could it be due incompatibility with some other mod?
Sorry if I am  being a nuisance!
Cheers

Yeah it is due to:
Skyrim Platform which uses it's own gui system.
I had to put the detection(s) in place otherwise the game can/could crash on startup.
I'm no graphics programmer so I don't know what voodoo ReShade has under the hood to make everything work in harmony.


Replaced the match (case) statement in voter/models.py -- match is not available until Python 3.10, and we are on 3.9 in production

👍


InfoItem Editor opens for wrong item

Steps to reproduce:

Add two info items to a random topic
open editor for one of both info items and close it again
add a third info item
BUG: Click on the 2nd info item -> the first one will be edited!

May have the same root cause... but in the above scenario the "Add Details" trigger also opens details on the wrong item.

@derwok strange, I cannot reproduce the issue concerning the "Add Details" trigger. Editing the info items seems to work sometimes, too. I added a topic with six items. It worked for all except the second one...?!
We use the jquery api to read the data-index attribute to locate the correct info item. This returns the wrong index (sometimes...). So I switched to the getAttribute-method of the plain javascript DOM-Element. This worked for me. I will merge the changes. @derwok Could you please test the results in your environment, too?

I thoroughly checked this fix on our /develop/ branch. I could not reproduce the problem. Neihter by clicking on the Item Subject, nor by clicking on "Add Details..." - it all worked as expected!
Thankx for the fix!  ;-)


:sparkles:Conversational learning page

Description
I added a conversational learning page.html  .
Fixes issue #10
Type of change

[ ] New feature (non-breaking change which adds functionality)

Screenshot (optional)

Checklist

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my code
[x] I have commented my code, particularly in hard-to-understand areas
[x] My changes generate no new warnings

Thia is good work, ATleast you are learning. Closing this pr as it is already done


bug:

Version
1.6.1
Describe the bug
in 1 hour old chat, it did not look at the files and wrote generic recommendation
Expected behavior
after restart it answered as expected
Additional context
    "text"<EMAIL_ADDRESS>what is in this file?",
    "speaker": "human"
  },
  {
    "speaker": "assistant"
  }
]

}
}
█ logEvent: CodyVSCodeExtension:chatResponse:hasCode VSCode {"properties":{"lineCount":34,"charCount":1364,"requestID":"816f8542-62ee-48d2-8e5e-a272e8713c4e"},"opts":{"hasV2Event":true}}
█ telemetry-v2: recordEvent: cody.chatResponse.new/hasCode: {"parameters":{"version":0,"metadata":[{"key":"lineCount","value":34},{"key":"charCount","value":1364},{"key":"recordsPrivateMetadataTranscript","value":1},{"key":"contextSelection","value":10},{"key":"guardrails","value":0}],"privateMetadata":{"requestID":"816f8542-62ee-48d2-8e5e-a272e8713c4e","responseText":"As an AI developed by OpenAI, I don't have direct access to your files or any specific implementation details that are not provided in the conversation. However, I can give you an example of what might typically be found in a login.py file within the routers directory of a FastAPI application.\n\nThe login.py file would generally contain route definitions related to user authentication, such as displaying a login form, handling login submissions, and possibly handling logout actions. Here's a basic example of what such a file might look like:\n\npython\nfrom fastapi import APIRouter, Depends, HTTPException, status\nfrom fastapi.security import OAuth2PasswordRequestForm\nfrom fastapi.responses import RedirectResponse\nfrom fastapi.templating import Jinja2Templates\nfrom starlette.requests import Request\n\nfrom . import auth  # This would be a module with your authentication logic\n\nrouter = APIRouter()\ntemplates = Jinja2Templates(directory=\"path/to/your/templates\")\n\n@router.get(\"/login\")\nasync def login_form(request: Request):\n    return templates.TemplateResponse(\"login.html\", {\"request\": request})\n\n@router.post(\"/login\")\nasync def login(request: Request, form_data: OAuth2PasswordRequestForm = Depends()):\n    user = auth.authenticate_user(form_data.username, form_data.password)\n    if not user:\n        raise HTTPException(\n            status_code=status.HTTP_401_UNAUTHORIZED,\n            detail=\"Incorrect username or password\",\n            headers={\"WWW-Authenticate\": \"Bearer\"},\n        )\n    access_token = auth.create_access_token(data={\"sub\": user.username})\n    response = RedirectResponse(url=\"/\", status_code=status.HTTP_302_FOUND)\n    auth.set_access_token_cookie(response, access_token)\n    return response\n\n@router.get(\"/logout\")\nasync def logout():\n    response = RedirectResponse(url=\"/login\", status_code=status.HTTP_302_FOUND)\n    auth.remove_access_token_cookie(response)\n    return response\n\n\nIn this example, the login_form route returns a template for the login page, the login route handles the login logic (authenticating the user and setting a cookie with an access token), and the logout route handles logging the user out (removing the access token cookie).\n\nThe auth module would contain the actual authentication logic, such as verifying user credentials and generating access tokens. The OAuth2PasswordRequestForm dependency is a utility that provides an easy way to handle login forms that submit username and password fields.\n\nPlease note that this is just an example, and the actual contents of your login.py file could be different based on your specific application's requirements and your authentication implementation."}},"timestamp":"2024-03-06T16:35:31.579Z"}

@itsklimov when you @-mentioned the login.py file, I get the impression it did not appear in context. It would be great if we could see a little bit earlier in the log to help determine why.
I'm trying to reproduce this. You mentioned the chat was an hour old. Did you restart VSCode in that time, close and reopen the chat, anything like that?


b2clogin.com is a recommended way

“If you want to use HTML form elements in your custom HTML content, use b2clogin.com.”
the note sounds like to use  b2clogin.com Is a workaround, but according to the link, “use b2clogin.com or a custom domain for all applications” is a recommended way anyway.
Consider rephrase the note and also mention custom domain, if applicable.

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

ID: 84aabaf3-e7da-3519-995c-72d36c537843
Version Independent ID: b35afa8d-a02c-a77a-6831-2b3f6a6c1a7d
Content: Customize the user interface with HTML templates - Azure AD B2C
Content Source: articles/active-directory-b2c/customize-ui-with-html.md
Service: active-directory
Sub-service: b2c
GitHub Login: @kengaderdus
Microsoft Alias: kengaderdus

@MNF
Thanks for your feedback! We will investigate and update as appropriate.

@MNF
Thanks for reporting this! We have created a PR for this issue and the changes should go live soon.


using Skate without Shadow DOM/Shadow Roots?

@treshugart thanks for contributing this library, it's a wonderful implementation.
My only question is are there any plans to optionally render custom elements without shadow DOM/shadow Roots? This would open up this library to potentially many more audiences and use cases. To add some context to this, many teams who have previously developed pattern libraries in things like jquery/plain old css and have strict browser requirements will be slowly adopting new custom element strategies. Rob Dodson's post details this migration strategy well:
jquery/css  =>  CEs  => CEs + Shadow DOM (when browser support improves)
What would be nice is to be able to use this library and take advantage of Incremental DOM now (while not adopting Shadow DOM until later).
Would you potentially explore this? Or maybe a fork of this could?

I need to unhide this in the docs:

Skate will work without Shadow DOM support, but you won't be able to compose components together due to the lack of DOM encapsulation that Shadow DOM gives you.

So you can, you just can't add content to your components as light DOM. See http://www.webpackbin.com/NJKsxfdnW. The only issue comes when you want to add light DOM to a component; Incremental DOM will overwrite any content added to your element that isn't in render() because there's no shadow root to encapsulate your component.

@treshugart thanks for this response, this is helpful to know that Skate would remove any light DOM. After looking at your webpackbin, I suppose I should follow up with another question.
Is there anyway to configure Skate to not create shadowRoots for the custom element's nested markup? While it may be feasible to style the host element, having the option to still style the nested markup/rendered vdom with external/global styles would still be a nice add (for some teams). I know the better approach is to use Shadow DOM and encapsulate CSS (and I know you've proposed using CSS modules), but for teams which have strict browser requirements and are exploring CEs for JS/HTML encapsulation only, having the option to remove shadowRoots would make Skate applicable (this way external css can still be used).

I'm not sure if I'd want to add a configuration option to do it as it's a fairly fundamental benefit of using web components. That said, a way you could do this now would be to do something like:
import { define } from 'skatejs';

define('x-test', {
  prototype: {
    // This should be fine for most browsers now
    attachShadow() {
      return this;
    },

    // However, in old Chrome / Opera or old polyfills
    // you might need to do this.
    createShadowRoot() {
      return this;
    }
  }
});

If you find yourself having to do this a lot, you can create a base class that extends skate.Component, or use a composable function:
function noShadowDOM(opts = {}) {
  return Object.assign(opts.prototype || {}, {
    attachShadow() {
      return this;
    }
  });
}

define('x-test', noShadowRoot({
  render() {}
});

Thanks so much for this @treshugart, this is exactly what we needed to know!

@treshugart in overriding attachShadow - can you see any dangers in doing that? e.g. a library talking to elements in general and expecting shadow roots?

also would skate ever consider the option of having two render pipelines? Not sure how you'd implement that, but in the case of an element that wants to have perhaps complete control over it's light DOM based on its props, but also needs Shadow DOM?

@bedeoverend

in overriding attachShadow - can you see any dangers in doing that? e.g. a library talking to elements in general and expecting shadow roots?

Possibly, but the library that's talking to those elements should check for a shadowRoot property. However, since it wouldn't exist if { mode: 'closed' }, then I'm not sure there'd be a reliable way for an external library to do this unless they overrode attachShadow, too. That could be troublesome, for sure.

also would skate ever consider the option of having two render pipelines? Not sure how you'd implement that, but in the case of an element that wants to have perhaps complete control over it's light DOM based on its props, but also needs Shadow DOM?

I'm probably projecting here, but could you be talking about custom form elements :p? I've definitely seen a need for that. Maybe this is a good path to that? What is your use case here? cc @bengummer

@treshugart it's certainly an edge case, but yeah it feels a little odd overriding the attachShadow - not sure if it's in Skate's scope, but perhaps a toggle for where to render to? Or overriding the render function on Skate's base component class even? Interestingly - @matthewp just floated this as an idea on his Bram library.
Re: rendering to both - haha, well actually I was thinking of our Simpla elements - the elements themselves are designed to have complete control over their children based on their props / internal state, I really like Skate's render pipeline but would obviously want to render into light dom. There's also however the benefit of hiding the element's controls away inside its Shadow DOM, so being able to render into both based on prop changes would be 👌

@treshugart yeah having separate render() functions for light + shadow DOM would allow the element to expose form elements in light DOM (so things like native form behaviour work as expected).
Once there is official support for custom elements exposing their own form values (spec discussion) this dual-render functionality wouldn't be needed for forms anymore.
If native form behaviour is the only use case here then it may be better to just document the attachShadow workaround (i.e. inserting form elements into light DOM so the <form> can see them). If there are other uses cases then maybe dual-render would be worth it.

Once #872 is merged, we'll officially document the rendererCallback() which can be used to implement a custom renderer. It'd be up to the renderer to call renderCallback(), so it could have an alternate render, or do whatever it wants at that point. This is still undocumented, though, as I still have questions around how to make the Incremental DOM renderer optional. This will probably happen through mixins, where you'd have a RenderMixin() that an IncrementalDOM mixin extends. The base RenderMixin() could just enforce that you provide it a renderer.

Biggest reason I see to render to the light DOM is for styling (as ironic as that is). Until @apply is a real thing theming in shadow DOM is going to be hard, and for small projects without a full time designer it might be more trouble than it's worth. For components that don't need distribution, I don't see a disadvantage to rendering to light DOM.

@matthewp the only issue there is hiding the shadow root template from any parent virtual DOMs that may have rendered the component with light DOM that would normally be slotted. In most implementations if you render() to the component as light DOM, it will be removed by the diffing algorithm. In order to do this, you'd need to fake childNodes and anything else the algorithm is interested in. I can see this as being implemented as a mixin or something.

is there a way to do this with the current (at time of writing, 4.6.6) version of Skate? I tried overriding attachShadow as mentioned above but it throws a JS error:
Uncaught TypeError: Cannot read property 'ownerDocument' of null
    at e (index-with-deps.min.js:1030)
    at Function.value (index-with-deps.min.js:1)
    at HTMLElement.value (index-with-deps.min.js:1)
    at HTMLElement.value (index-with-deps.min.js:1)
    at MutationObserver.<anonymous> (index-with-deps.min.js:1030)

@alexlafroscia yeah, my code above wasn't exact. I've created a working example for you that uses it like a mixin so it's easy for you to share. The code above should have taken into account both ways to access the shadow root (property and function return value).

Ahh, very interesting! Thanks. I've been trying to get a server-side-rendering story put together and disabling the Shadow DOM is a req for that.

@treshugart we may be considering Skate.js again for some of our new components after reviewing the Angular integration example here:
https://github.com/Hotell/angular-skate-talk-demo
This is quite a compelling demo. The only issue I have there is still the required use of slot/shadow roots for light DOM scenarios (transcluded content like the <img>). It works great in new browers, but we still have the need to support CEs in cases w/o Shadow DOM (the original intent of this issue).
It looks like the working example/jsbin link above is no longer working. Can you provide this sample once more?
I've noticed when implementing things like conditional rendering/event handlers inside the light dom with JSX gets really hairy with Mutation Observers (i.e. you have to move elements with appendChild if actually transcluding them to maintain event listeners). It would be great to solve this problem with Skate JS and write component APIs that are very flexible to whatever the user wants in the light DOM...
ex w/ Mutation Observer (remove Secondary button fails b/c element has been moved and JSX can no longer find it):
https://stackblitz.com/edit/using-pf-tabs-in-reactjs?file=index.js

It looks like real-dom implemented here may help in conjunction w/ using a custom renderer in the render callback?
https://github.com/skatejs/val#real-dom

@priley86 you can definitely use real-dom from val, but you just won't get the DOM diff algo from Preact. If you're rendering to light DOM, it's likely you can't do this anyways because of it becoming out of sync with it's view of the world.

JSBin is down for me, so I can't check that example, unfortunately.


Add C0rmacB's file

Pull request comment here

Merged updated text

Merged updated text

merge?

merge?


?. operator should extend to remaining selectors

The ?. operator should extend to the remaining selectors.
That is, o?.x.y should be legal, and not bomb on the .y access.
This issue was edited by @floitschG. Original content below:
final dom.HtmlElement elementToActivate = query("[for=${propertyName}]");
elementToActivate?.classes.add(_cssClasses.ACTIVE);

Shows `INFO: The expression uses '?.', so can be 'null'``
It wants a ?. between "classes" and "add"
This is wrong - elementToActivate can be null but not "classes"
html_dartium:
CssClassSet get classes => new _ElementCssClassSet(this);

If elementToActivate is null, then elementToActivate?.classes will also be null.

Clear - but it makes no sense to double check
elementToActivate?.classes?.add(...) would be the same as:
if(elementToActivate != null) {
    if(elementToActivate.classes != null {
       ...
    }
}

But without the extra check, the code is equivalent to
var classes = elementToActivate == null ? null : elementToActivate.classes;
classes.add(...);

which can result in a null pointer dereference.
You could argue that the ?. operator ought to short circuit everything to the right (in which case this is a language issue), but that's not the current definition.

Uhhh - really?? To me it is logic that the first ?. operator makes all checks to the right unnecessary. I think someone should update the current definition. And - yes, I think this is a language issue!
BTW: In C# for example operators are also short-circuiting

It's certainly a modified semantics to say that x?.y.z should evaluate to
null if x is null, rather than throwing a NPE because we attempt to look
up z in the null object.
Given that member access associates to the left (with x.y.z, we evaluate
x, then .y of that object, then .z of that object again), and given
that we do have members like toString and runtimeType on null, it would
be a rather twisted exception to say that exactly that .z should be
skipped in x?.y.z, because we evaluated x to null.
Do you think there is a simple and consistent way to explain what is going
on if we were to take such a shortcut? To me it looks like a tiny
convenience, bundled with a significant source of confusion. Just consider
(x?.y).z, should the shortcut semantics bleed through the parentheses? ..
and how about (w = x?.y).z? .. or ((x) => x?.y)(x).z?
On Tue, Apr 12, 2016 at 4:37 PM, Mike Mitterer<EMAIL_ADDRESS>wrote:

Uhhh - really?? To me it is logic that the first ?. operator makes all
checks to the right unnecessary. I think someone should update the current
definition. And - yes, I think this is a language issue!
BTW: In C# for example operators are also short-circuiting
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub
https://github.com/dart-lang/sdk/issues/26240#issuecomment-208937609

--
Erik Ernst  -  Google Danmark ApS
Skt Petri Passage 5, 2 sal, 1165 København K, Denmark
CVR no. 28866984

@eernstg You say it looks like a tiny convenience - I think it's more. In my opinion it's just more logical to assume that the ?. is short-circuiting. A language feels good if it does what you think it should do. That's one reason why I like Dart. You know all the specs but the average programmer doesn't read all the specs...
(w = x?.y).z :sweat_smile: :sweat_smile: My interpretation: It assigns either x or y to w depending if x is null or not. It calls z on the result. So if there should be a null-check for z I would write (w = x?.y)?.z (BTW I hope such constructs won't be used in average code - nobody knows what it should do without extra lines of comments)

I updated this issue to reflect the requirement to change the language spec.


Fix: Typos Update README.md (ALAN)

Fixed some typos in the README specifically names formatting changed this as per a comment from Merete at the end of our README

thank you awesome


VisualStateManager do not work properly in UWP

I have tried to use VisualStateManger described above to change the appearance of the button when pressed and not pressed. While this does seem to work properly for Android, when running under UWP, when I click on the button it changes to the 'Pressed' state, but when I release it, it does NOT change back to the 'Normal' state until I click somewhere else on the page. Am I doing something wrong here or is this a bug?
Thanks

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

ID: f70c4017-a981-2cd6-24b2-7da7674efa5a
Version Independent ID: 2b4a8128-38d8-352f-c310-d033b56a3081
Content: Xamarin.Forms ImageButton - Xamarin
Content Source: docs/xamarin-forms/user-interface/imagebutton.md
Product: xamarin
Technology: xamarin-forms
GitHub Login: @davidbritch
Microsoft Alias: dabritch

Hi @JohnGaby if it works on Android and iOS, but not UWP, then it could be a bug.
You can raise bugs directly on the Xamarin.Forms open source repo.


correct promise property types

Proposed Changes

this silences Vue warnings about the wrong data type passed to the property
for Vue-2 oruga we have a hack that sets Promise to window.Promise so we can accommodate IE 11 which may not have a promise (unless the developer polyfills it)

For Vue 2, probably it's better to create a custom  function that returns a Promise (if the browser supports it) or a simple object.
About docs don't worry, the @ignore doesn't add the prop to the docs 😉

For Vue 2, probably it's better to create a custom function that returns a Promise (if the browser supports it) or a simple object.

I can adjust that for Vue2.

About docs don't worry, the @ignore doesn't add the prop to the docs 😉 (run docs gen you can see that prop won't be added)

I don't think that is working then.   as I still see the props when I generate docs (even the public docs on oruga.io show the props)

@jtommy I reworked to use a helper function.  and I also manually removed the programmatic and promise from the generated docs from vue-docgen as it is not respecting the @ignore like their docs claim it is supposed to. Now when I run vuepress build it correctly does not have those two props documented.  However, there are other ignored props that are included in their respective docs still :( (e.g. iconBoth from the Button component)

@jtommy I pushed another commit to this PR that fixes the doc generation so that it properly ignores ignored props.   The issue seemed to be around your customization of the prop template. I added a filter loop in there that removes the ignored items.


Datetime field

We want a richer experience when dealing with datetime.
Ideally it should be an actual type...
Its configurations should make ingestion should be more flexible
- name: dt
  type: datetime
  input_format: "rfc3339" #  "unix_ts_secs" |  "unix_ts_millis"  | "unix_ts_micros" | "unix_ts_nanos"
  fast: true
  precision: secs | millis | micros | nanos (default: secs)

We may also want to have a better indexing scheme... ( ie index days for instance)

People do crazy things we dates. Should we support a custom date formatted expressed in the syntax supported by the time crate? That does not seem like much extra work.

That's probably a good idea... It already includes "well-known" formats. I am not sure we can extend the syntax with our own formats, but checking if the format is in a dictionary and then trying the time crate's format description parse function should do the job

We may also want to have a better indexing scheme... ( ie index days for instance)

@fulmicoton not sure to understand what you meant, can you elaborate?

Dates is something we want to run range queries on.
Right we do split pruning + fast field filtering at collection.
That works ok if the datetime field is indeed the timestamp field, but that is not necessarily the case.
THe normal way to do range queries on int fields is any variant of trie indexing.
We could just offer that on dates too... But it is tempting to, instead of using a base decomposition, align the decomposition of the date into the way human decompose dates.
Inverted list for hours & day specifically should be more efficient than an arbitrary base development.

@fmassot continuing the conversation from discord here.
I made a small specification document to change and go through later on.
Few more questions I got are:

If, currently, we are using any data type to store the date information, how are we able to filter using search API?
startTimeStamp, endTimeStamp -> use i64 specifically 🤔

why does higher accuracy lower the filtering speed/ increase the doc store space? accuracy doesn't change the number of documents/splits to go through I think?

Coming to the specification, I think this is a good start: let me know your thoughts on this, thanks
- name: timestamp
  type: datetime
  input_format:  should support any rfc3339 format and "unix_ts_secs"  "unix_ts_millis"  "unix_ts_miceounix_ts_nano".
  fast: true

If not specified, it assumes "date_optional_time (or) unix_ts_millis"
I think we don't have to have precision while sending data. It is much easier to store the data using i64 and in unix_ts_millis only.
We will use the input_format given before from metastore to send the data back in user given format. This way we can be flexible with the input data and also convert it into user desirable format. On that note, we should just leave the endTimeStamp and startTimeStamp to be in unix_ts_millis and i64 only. It might be better to add a new datetime-format variable to search API in the future to get the data in different formats other than user given format.

This will cover the resolution only till milliseconds, since we are not offering other functions(like aggregations/others) that work on nanoseconds, it would be better to not include that at the moment? elasticsearch has a similar limitation on their nano-date type. I presumed this, if we offer rich support for nanoseconds everywhere, then going with nanos as the base option or providing a new nano type or something else might be a better option.

I have a question related to this. Is there a particular reason to be focusing  on RFC3339 only instead of ISO8601? RFC3339 has the huge downside of requiring a fully specified time including timezone for all datetimes. In Elasticsearch date_optional_time is not a valid RFC3339 datetime.

Continuing the thread from Discord:
Storage wise, whatever is most reasonable. There might be room for certain optimizations, but they're premature and can be done out of band through preprocessing steps.
For me the big thing is the ability to supply several parsing methods for a single datetime field and to support custom datetime parsing.
A simple example is twitter's datetime format which has changed several times over the years. Being able to supply the three or four strptime strings to parse any twitter record would be awesome. Usually, being lossy with other fields is fine, but not being able to parse datetime fields is painful.
And sometimes you do just have to parse a weird datetime format. The ability to just bang out a strptime string and ingest directly without requiring a preprocessing step would save so much effort.
That said, having human readable shorthands for known datetime formats (ie. rfc3339, iso8601, unix_ts_millis) is needed since they'll work for 95% of cases.
So using me-diru's spec for the twitter example gives:
- name: created_on
  type: datetime
  input_formats:
    - "unix_ts_millis"
    - "rfc3339"
    - "iso8601"
    - "%a %b %d %H:%M:%S %z %Y"
  fast: true

Each input_format should be applied in the order until it successfully parses.
Overall, it might slow down ingest, but I'd have to write that same code in an other process anyways and I'd much rather have it be in rust and not have to spin up another process or system just for something like datetime parsing.
You could also just have input_formats be an enum over a single input_format and a vec of input_formats so datasets with known formats could just skip the loop entirely.
Anyways, at the bare minimum having the ability to pass strptime strings for datetime parsing is a must.

@kstaken Not much reasons. We should support several format. I am the culprit for sprinkling rfc3339 here and there  in docs, and this is not an educated choice.
@stranger-danger-zamu Without a time format, it might be an interesting way to create "default configs" use cases.


Handle "extra" badges with unassigned IDs

Not really relevant since we're making these a POST fail.


[BUG]: Cannot import Creator Kit

When trying to import the creator kit solution this error is populated
"The solution file is invalid. The compressed file must contain the following files at its root: solution.xml, customizations.xml, and [Content_Types].xml. Customization files exported from previous versions of Microsoft Dynamics 365 are not supported."
Installing from app source does seem to work, but I could not tell if there is a version difference between app source and git.

Unzip the downloaded zip.
Regards,
Steven Perry
@.***
On Wed, Nov 2, 2022 at 1:36 PM nbetters @.***> wrote:

When trying to import the creator kit solution this error is populated
"The solution file is invalid. The compressed file must contain the
following files at its root: solution.xml, customizations.xml, and
[Content_Types].xml. Customization files exported from previous versions of
Microsoft Dynamics 365 are not supported."
Installing from app source does seem to work, but I could not tell if
there is a version difference between app source and git.
—
Reply to this email directly, view it on GitHub
https://github.com/microsoft/powercat-creator-kit/issues/167, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AFNR6PQOV4HSZHAFHD5KYPTWGKRC5ANCNFSM6AAAAAARVKYPAA
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

It fails to unzip
@.***
From: Steven Perry @.>
Sent: Wednesday, November 2, 2022 12:42 PM
To: microsoft/powercat-creator-kit @.>
Cc: Nathan Betters @.>; Author @.>
Subject: Re: [microsoft/powercat-creator-kit] [BUG]: Cannot import Creator Kit (Issue #167)
Unzip the downloaded zip.
Regards,
Steven Perry
<EMAIL_ADDRESS>On Wed, Nov 2, 2022 at 1:36 PM nbetters<EMAIL_ADDRESS>wrote:

When trying to import the creator kit solution this error is populated
"The solution file is invalid. The compressed file must contain the
following files at its root: solution.xml, customizations.xml, and
[Content_Types].xml. Customization files exported from previous versions of
Microsoft Dynamics 365 are not supported."
Installing from app source does seem to work, but I could not tell if
there is a version difference between app source and git.

Reply to this email directly, view it on GitHub
https://github.com/microsoft/powercat-creator-kit/issues/167, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AFNR6PQOV4HSZHAFHD5KYPTWGKRC5ANCNFSM6AAAAAARVKYPAA
.
You are receiving this because you are subscribed to this thread.Message
ID<EMAIL_ADDRESS>

Reply to this email directly, view it on GitHubhttps://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fmicrosoft%2Fpowercat-creator-kit%2Fissues%2F167%23issuecomment-1301001982&data=05|01|nathan.betters%40apigroupinc.us|43e23caa355c49553cd608dabcf97eba|2af10afe84c446b3bfb55b2c870e6af7|0|0|638030077032610596|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=Gz7U2ux%2FvMe7%2FWjuq8bvFrgO4VnTrz6fmS1CjzgX17I%3D&reserved=0, or unsubscribehttps://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FANIDCP62ISKJG7NV5YPGQ5TWGKRVDANCNFSM6AAAAAARVKYPAA&data=05|01|nathan.betters%40apigroupinc.us|43e23caa355c49553cd608dabcf97eba|2af10afe84c446b3bfb55b2c870e6af7|0|0|638030077032610596|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=P8uxNcFU7C0c2ettxK22h0SA76O9AiWLbHpjK3FuZ7Y%3D&reserved=0.
You are receiving this because you authored the thread.Message ID<EMAIL_ADDRESS>

Then you may have gotten a bad download.  Try downloading again.
Regards,
Steven Perry
@.***
On Wed, Nov 2, 2022 at 1:44 PM nbetters @.***> wrote:

It fails to unzip
@.***
From: Steven Perry @.>
Sent: Wednesday, November 2, 2022 12:42 PM
To: microsoft/powercat-creator-kit @.>
Cc: Nathan Betters @.>; Author @.>
Subject: Re: [microsoft/powercat-creator-kit] [BUG]: Cannot import Creator
Kit (Issue #167)
Unzip the downloaded zip.
Regards,
Steven Perry
<EMAIL_ADDRESS>On Wed, Nov 2, 2022 at 1:36 PM nbetters<EMAIL_ADDRESS>wrote:

When trying to import the creator kit solution this error is populated
"The solution file is invalid. The compressed file must contain the
following files at its root: solution.xml, customizations.xml, and
[Content_Types].xml. Customization files exported from previous versions
of
Microsoft Dynamics 365 are not supported."
Installing from app source does seem to work, but I could not tell if
there is a version difference between app source and git.

Reply to this email directly, view it on GitHub
https://github.com/microsoft/powercat-creator-kit/issues/167, or
unsubscribe
<
https://github.com/notifications/unsubscribe-auth/AFNR6PQOV4HSZHAFHD5KYPTWGKRC5ANCNFSM6AAAAAARVKYPAA
.
You are receiving this because you are subscribed to this thread.Message
ID<EMAIL_ADDRESS>

Reply to this email directly, view it on GitHub<
https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fmicrosoft%2Fpowercat-creator-kit%2Fissues%2F167%23issuecomment-1301001982&data=05|01|nathan.betters%40apigroupinc.us|43e23caa355c49553cd608dabcf97eba|2af10afe84c446b3bfb55b2c870e6af7|0|0|638030077032610596|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=Gz7U2ux%2FvMe7%2FWjuq8bvFrgO4VnTrz6fmS1CjzgX17I%3D&reserved=0>,
or unsubscribe<
https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FANIDCP62ISKJG7NV5YPGQ5TWGKRVDANCNFSM6AAAAAARVKYPAA&data=05|01|nathan.betters%40apigroupinc.us|43e23caa355c49553cd608dabcf97eba|2af10afe84c446b3bfb55b2c870e6af7|0|0|638030077032610596|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=P8uxNcFU7C0c2ettxK22h0SA76O9AiWLbHpjK3FuZ7Y%3D&reserved=0

.
You are receiving this because you authored the thread.Message ID:
<EMAIL_ADDRESS>
—
Reply to this email directly, view it on GitHub
https://github.com/microsoft/powercat-creator-kit/issues/167#issuecomment-1301005680,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AFNR6PSLPKEGIRP6SRHFW7TWGKSBDANCNFSM6AAAAAARVKYPAA
.
You are receiving this because you commented.Message ID:
@.***>

Same issue, trying to unzip the file throws an error that the json file name is too long
From: Steven Perry @.>
Sent: Wednesday, November 2, 2022 12:50 PM
To: microsoft/powercat-creator-kit @.>
Cc: Nathan Betters @.>; Author @.>
Subject: Re: [microsoft/powercat-creator-kit] [BUG]: Cannot import Creator Kit (Issue #167)
Then you may have gotten a bad download. Try downloading again.
Regards,
Steven Perry
<EMAIL_ADDRESS>On Wed, Nov 2, 2022 at 1:44 PM nbetters<EMAIL_ADDRESS>wrote:

It fails to unzip
<EMAIL_ADDRESS>From: Steven Perry<EMAIL_ADDRESS>Sent: Wednesday, November 2, 2022 12:42 PM
To: microsoft/powercat-creator-kit<EMAIL_ADDRESS>Cc: Nathan Betters<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>Subject: Re: [microsoft/powercat-creator-kit] [BUG]: Cannot import Creator
Kit (Issue #167)
Unzip the downloaded zip.
Regards,
Steven Perry
@.<mailto:@.mailto:***<EMAIL_ADDRESS>On Wed, Nov 2, 2022 at 1:36 PM nbetters @.<mailto:@.mailto:***<EMAIL_ADDRESS>wrote:

When trying to import the creator kit solution this error is populated
"The solution file is invalid. The compressed file must contain the
following files at its root: solution.xml, customizations.xml, and
[Content_Types].xml. Customization files exported from previous versions
of
Microsoft Dynamics 365 are not supported."
Installing from app source does seem to work, but I could not tell if
there is a version difference between app source and git.

Reply to this email directly, view it on GitHub
https://github.com/microsoft/powercat-creator-kit/issues/167, or
unsubscribe
<
https://github.com/notifications/unsubscribe-auth/AFNR6PQOV4HSZHAFHD5KYPTWGKRC5ANCNFSM6AAAAAARVKYPAA
.
You are receiving this because you are subscribed to this thread.Message
ID: @.<mailto:@.mailto:***<EMAIL_ADDRESS>

Reply to this email directly, view it on GitHub<
https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fmicrosoft%2Fpowercat-creator-kit%2Fissues%2F167%23issuecomment-1301001982&data=05|01|nathan.betters%40apigroupinc.us|43e23caa355c49553cd608dabcf97eba|2af10afe84c446b3bfb55b2c870e6af7|0|0|638030077032610596|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=Gz7U2ux%2FvMe7%2FWjuq8bvFrgO4VnTrz6fmS1CjzgX17I%3D&reserved=0>,
or unsubscribe<
https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FANIDCP62ISKJG7NV5YPGQ5TWGKRVDANCNFSM6AAAAAARVKYPAA&data=05|01|nathan.betters%40apigroupinc.us|43e23caa355c49553cd608dabcf97eba|2af10afe84c446b3bfb55b2c870e6af7|0|0|638030077032610596|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=P8uxNcFU7C0c2ettxK22h0SA76O9AiWLbHpjK3FuZ7Y%3D&reserved=0

.
You are receiving this because you authored the thread.Message ID:
@.@.mailto:***<EMAIL_ADDRESS>

Reply to this email directly, view it on GitHub
https://github.com/microsoft/powercat-creator-kit/issues/167#issuecomment-1301005680,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AFNR6PSLPKEGIRP6SRHFW7TWGKSBDANCNFSM6AAAAAARVKYPAA
.
You are receiving this because you commented.Message ID:
<EMAIL_ADDRESS>

Reply to this email directly, view it on GitHubhttps://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fmicrosoft%2Fpowercat-creator-kit%2Fissues%2F167%23issuecomment-1301010967&data=05|01|nathan.betters%40apigroupinc.us|f8365c7c39824da8387d08dabcfaa5b4|2af10afe84c446b3bfb55b2c870e6af7|0|0|638030081960394598|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=rdj4jbuJRcX6C8eCtF8VJfIjmjafu6mZuw2h%2BKKO1n0%3D&reserved=0, or unsubscribehttps://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FANIDCP4RMHNMMIKEFUNOZ33WGKSUDANCNFSM6AAAAAARVKYPAA&data=05|01|nathan.betters%40apigroupinc.us|f8365c7c39824da8387d08dabcfaa5b4|2af10afe84c446b3bfb55b2c870e6af7|0|0|638030081960394598|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=5VyDaI7suWRBm6Qm0zHtBE6J5eApkkpA53WuASAtVFw%3D&reserved=0.
You are receiving this because you authored the thread.Message ID<EMAIL_ADDRESS>

Place the zip in a root folder or shorter path before unzipping. Full
filenames cannot be longer than 255 characters.
Regards,
Steven Perry
@.***
On Wed, Nov 2, 2022 at 1:52 PM nbetters @.***> wrote:

Same issue, trying to unzip the file throws an error that the json file
name is too long
From: Steven Perry @.>
Sent: Wednesday, November 2, 2022 12:50 PM
To: microsoft/powercat-creator-kit @.>
Cc: Nathan Betters @.>; Author @.>
Subject: Re: [microsoft/powercat-creator-kit] [BUG]: Cannot import Creator
Kit (Issue #167)
Then you may have gotten a bad download. Try downloading again.
Regards,
Steven Perry
<EMAIL_ADDRESS>On Wed, Nov 2, 2022 at 1:44 PM nbetters<EMAIL_ADDRESS>wrote:

It fails to unzip
<EMAIL_ADDRESS>From: Steven Perry<EMAIL_ADDRESS>Sent: Wednesday, November 2, 2022 12:42 PM
To: microsoft/powercat-creator-kit<EMAIL_ADDRESS>Cc: Nathan Betters<EMAIL_ADDRESS>Author
<EMAIL_ADDRESS>Subject: Re: [microsoft/powercat-creator-kit] [BUG]: Cannot import
Creator
Kit (Issue #167)
Unzip the downloaded zip.
Regards,
Steven Perry
@.<mailto:@.mailto:***<EMAIL_ADDRESS>On Wed, Nov 2, 2022 at 1:36 PM nbetters @.<mailto:
@.mailto:***<EMAIL_ADDRESS>wrote:

When trying to import the creator kit solution this error is populated
"The solution file is invalid. The compressed file must contain the
following files at its root: solution.xml, customizations.xml, and
[Content_Types].xml. Customization files exported from previous
versions
of
Microsoft Dynamics 365 are not supported."
Installing from app source does seem to work, but I could not tell if
there is a version difference between app source and git.

Reply to this email directly, view it on GitHub
https://github.com/microsoft/powercat-creator-kit/issues/167, or
unsubscribe
<

https://github.com/notifications/unsubscribe-auth/AFNR6PQOV4HSZHAFHD5KYPTWGKRC5ANCNFSM6AAAAAARVKYPAA

.
You are receiving this because you are subscribed to this
thread.Message
ID<EMAIL_ADDRESS><EMAIL_ADDRESS>

Reply to this email directly, view it on GitHub<

https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fmicrosoft%2Fpowercat-creator-kit%2Fissues%2F167%23issuecomment-1301001982&data=05|01|nathan.betters%40apigroupinc.us|43e23caa355c49553cd608dabcf97eba|2af10afe84c446b3bfb55b2c870e6af7|0|0|638030077032610596|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=Gz7U2ux%2FvMe7%2FWjuq8bvFrgO4VnTrz6fmS1CjzgX17I%3D&reserved=0

,
or unsubscribe<

https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FANIDCP62ISKJG7NV5YPGQ5TWGKRVDANCNFSM6AAAAAARVKYPAA&data=05|01|nathan.betters%40apigroupinc.us|43e23caa355c49553cd608dabcf97eba|2af10afe84c446b3bfb55b2c870e6af7|0|0|638030077032610596|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=P8uxNcFU7C0c2ettxK22h0SA76O9AiWLbHpjK3FuZ7Y%3D&reserved=0

.
You are receiving this because you authored the thread.Message ID:
@.@.mailto:***<EMAIL_ADDRESS>

Reply to this email directly, view it on GitHub
<
https://github.com/microsoft/powercat-creator-kit/issues/167#issuecomment-1301005680
,
or unsubscribe
<
https://github.com/notifications/unsubscribe-auth/AFNR6PSLPKEGIRP6SRHFW7TWGKSBDANCNFSM6AAAAAARVKYPAA
.
You are receiving this because you commented.Message ID:
<EMAIL_ADDRESS>

Reply to this email directly, view it on GitHub<
https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fmicrosoft%2Fpowercat-creator-kit%2Fissues%2F167%23issuecomment-1301010967&data=05|01|nathan.betters%40apigroupinc.us|f8365c7c39824da8387d08dabcfaa5b4|2af10afe84c446b3bfb55b2c870e6af7|0|0|638030081960394598|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=rdj4jbuJRcX6C8eCtF8VJfIjmjafu6mZuw2h%2BKKO1n0%3D&reserved=0>,
or unsubscribe<
https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FANIDCP4RMHNMMIKEFUNOZ33WGKSUDANCNFSM6AAAAAARVKYPAA&data=05|01|nathan.betters%40apigroupinc.us|f8365c7c39824da8387d08dabcfaa5b4|2af10afe84c446b3bfb55b2c870e6af7|0|0|638030081960394598|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=5VyDaI7suWRBm6Qm0zHtBE6J5eApkkpA53WuASAtVFw%3D&reserved=0

.
You are receiving this because you authored the thread.Message ID:
<EMAIL_ADDRESS>
—
Reply to this email directly, view it on GitHub
https://github.com/microsoft/powercat-creator-kit/issues/167#issuecomment-1301013361,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AFNR6PSCLG74AEJQANWYU73WGKS5DANCNFSM6AAAAAARVKYPAA
.
You are receiving this because you commented.Message ID:
@.***>

ok, but now that it is unzipped how do you import it into the powerapps solution import? this requires the package to be zipped, if I rezip only the automationCOEmain for example it fails with the same error as the beginning.

Ok. The last time I downloaded the Creator Kit there were multiple ZIP
files in one. I just unzipped those and imported the individual ZIP files.
Not sure what you downloaded or what was in the ZIP you have.
It should be working.
Regards,
Steven Perry
@.***
On Wed, Nov 2, 2022 at 2:06 PM nbetters @.***> wrote:

ok, but now that it is unzipped how do you import it into the powerapps
solution import? this requires the package to be zipped, if I rezip only
the automationCOEmain for example it fails with the same error as the
beginning.
—
Reply to this email directly, view it on GitHub
https://github.com/microsoft/powercat-creator-kit/issues/167#issuecomment-1301027806,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AFNR6PTVLKDRBKZJL7KQZ7TWGKUPVANCNFSM6AAAAAARVKYPAA
.
You are receiving this because you commented.Message ID:
@.***>

Humm.. I downloaded the set from git.
I guess, as long as appsource is up to date I can install it using the d365 app source just fine, I just wanted the most current update.
From: Steven Perry @.>
Sent: Wednesday, November 2, 2022 1:09 PM
To: microsoft/powercat-creator-kit @.>
Cc: Nathan Betters @.>; Author @.>
Subject: Re: [microsoft/powercat-creator-kit] [BUG]: Cannot import Creator Kit (Issue #167)
Ok. The last time I downloaded the Creator Kit there were multiple ZIP
files in one. I just unzipped those and imported the individual ZIP files.
Not sure what you downloaded or what was in the ZIP you have.
It should be working.
Regards,
Steven Perry
<EMAIL_ADDRESS>On Wed, Nov 2, 2022 at 2:06 PM nbetters<EMAIL_ADDRESS>wrote:

ok, but now that it is unzipped how do you import it into the powerapps
solution import? this requires the package to be zipped, if I rezip only
the automationCOEmain for example it fails with the same error as the
beginning.

Reply to this email directly, view it on GitHub
https://github.com/microsoft/powercat-creator-kit/issues/167#issuecomment-1301027806,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AFNR6PTVLKDRBKZJL7KQZ7TWGKUPVANCNFSM6AAAAAARVKYPAA
.
You are receiving this because you commented.Message ID:
<EMAIL_ADDRESS>

Reply to this email directly, view it on GitHubhttps://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fmicrosoft%2Fpowercat-creator-kit%2Fissues%2F167%23issuecomment-1301031493&data=05|01|nathan.betters%40apigroupinc.us|9a1d63cbd2044020292d08dabcfd5d01|2af10afe84c446b3bfb55b2c870e6af7|0|0|638030093684424663|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=Uvipi4ve%2BfTQ4CKEBMVVxTtJVO9qTa2UfmPeIvS6zck%3D&reserved=0, or unsubscribehttps://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FANIDCPZOTCI47ZQAU7PMTDLWGKU47ANCNFSM6AAAAAARVKYPAA&data=05|01|nathan.betters%40apigroupinc.us|9a1d63cbd2044020292d08dabcfd5d01|2af10afe84c446b3bfb55b2c870e6af7|0|0|638030093684424663|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=VWRlt86LNeg1ayaCMPNSIYJW8Ow6d47r0M6VLkdGKqA%3D&reserved=0.
You are receiving this because you authored the thread.Message ID<EMAIL_ADDRESS>

You need to download the assets from the latest release page: https://github.com/microsoft/powercat-creator-kit/releases/latest
For example, download the file that says "CreatorKitCore_1.0.20221004.2_managed.zip" to download the core solution.
Import those directly (do not unzip) and it should work.
(Thank you @sperry1625 for helping troubleshoot)

@nbetters can you please try downloading from the release page and confirm if that import worked for you?


calling modalRef.setVisibility(true); throws modal already dismissed error

here is the full error
[Error: message: Guard check failed, modal already dismissed - debugMessage: N/A- fileID: react_native_ios_modal/RNIModalView.swift- functionName: dismissModal(completion:)- lineNumber: 886]

even on 0.2?

Any updates?


fix: remove lhs trigger handler

Fixes #265

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

v1.34.1
GitHub release

Your semantic-release bot :package::rocket:


Pub transformers hang on initial "pub get"

Reproduction steps, at least for me:
Dart VM version: 1.20.0-dev.10.3 (Wed Oct 12 10:53:42 2016) on "macos_x64"

Clone angular2
Run pub get --verbose
Observe a hang:

FINE: [Fine from TemplateCompiler]:
    | [createCompileData] took 53 ms on angular2|lib/src/router/directives/router_outlet.ng_meta.json

It's not clear to me how to resolve this.
/cc @kevmoo for triage.

pub get runs transformers on things it knows it can ahead of time and caches the output. It looks like the transformer is hanging? I wouldn't expect it to be running the transformer on the current package though.....

@jakemac53:
https://github.com/dart-lang/angular2/blob/master/pubspec.yaml#L33
transformers:
  - test/pub_serve:
      $include: test/**_test.dart
  - angular2/transform/codegen

To clarify, I am surprised that pub get would run the transformers that are defined for the current package (since that is the package being modified). It seems to be doing that here though.
@nex3 is that expected behavior or do you know what might trigger it?

After ~20 minutes, it finally crashed with:
Precompiling dependencies...
Loading source assets...
Loading angular2/transform/codegen transformers...
Directory listing failed, path = '/Users/matanl/.pub-cache/hosted/pub.dartlang.org/stack_trace-1.6.8/lib/packages/args/packages/async/packages/charcode/packages/collection/packages/convert/packages/mime/packages/path/packages/shelf/src/handlers/packages/stream_channel/' (OS Error: Invalid argument, errno = 22)
exit code 0

@jakemac53 It won't run transformers defined in the current package, but it may load those that are used by the current package. At the very least it needs to compile a snapshot so startup time is faster later on, and there may be other dependencies that use those transformers.
@matanlurey It looks like there may be an infinite directory-listing loop going on, possibly caused by a packages directory incorrectly existing in the package cache. Does /Users/<MY_USER_NAME>/.pub-cache/hosted/pub.dartlang.org/stack_trace-1.6.8/lib/packages actually exist?

@nex3:

Does /Users/<MY_USER_NAME>/.pub-cache/hosted/pub.dartlang.org/stack_trace-1.6.8/lib/packages actually exist?

Yes:
$ ls /Users/<MY_USER_NAME>/.pub-cache/hosted/pub.dartlang.org/stack_trace-1.6.8/lib/packages

> analyzer args async (etc...)

Even the full URI above exists if I ls manually.
I can get around this with --no-precompile, but since it's not the default our users are going to see timeouts/crashes unless they know to use this option - I wonder if this is due to the SDK roll and changes with .packages?
/cc @kevmoo Work on Angular is blocked :sob:

To clarify, it stills fails with --no-packages-dir

OK, it works for @ferhatb - I am running pub cache repair and deleting .pub to see if it's some transient error.

OK, I deleted my caches and re-ran and it works. No idea why.
Maybe this is due to having the old packages folder before 1.20? No idea.

One major flaw with the packages directory symlinks was that it made it really easy for tools (or occasionally huamns) to accidentally put stuff in there that didn't belong. I can only begin to guess what specific circumstance made this one appear, but it'll happen much less frequently once no packages/ directories exist at all.


Exported splats from NerfGS gives washed out color splat

After I get good result in this rendered video (see this Thread):

I export the splats by using this command:
ns-export gaussian-splat --load-config outputs/Truck/nerfgs/2024-05-20_155003/config.yml --output-dir renders/Truck_NerfGS/

But the color of splats is not good, seems more washed out than rendered video. I open the splat with mkkellogg 3D gaussian viewer

Any ways for fixing it?

Hi, I want to make sure I understand the question. Do you mean the last image is lack of detailed/rich colors compared to the first image?

This result gives washed out result on ply which is opened in supersplat
ns-train nerfgs --data path/to/Truck_dataset --pipeline.model.ply-file-path exports/nerfgs/nerfgs.ply

ns-export gaussian-splat --load-config outputs/Truck/nerfgs/2024-05-20_155003/config.yml --output-dir renders/Truck_NerfGS/

This result gives good result on ply which is opened in supersplat
ns-train splatfacto --data path/to/Truck_dataset

ns-export gaussian-splat --load-config outputs/Truck/splatfacto/2024-05-20_155123/config.yml --output-dir renders/Truck_Splatfacto/

Sorry, I'm not sure about how to fix it. I'll take a look at it in more details later.


[Feature] Feature Flags

Currently no option exists to enable feature flags in doc2readme. This means doc2readme can to create links for functions, which are not available with the default features.
For example in https://github.com/LuckyTurtleDev/more-wallpapers/pull/7#pullrequestreview-1192074089 the link for set_random_wallpapers_from_vec() cannot be created. Instead, doc2readme create a link to a non existing set_random_wallpapers_from_vec() file.

This should either be done in a way where --features is only accepted if --expand-macros is also set, or at least generates a warning if --features are set but --expand-macros is not used. Especially, the user shouldn't assume that feature flags (or any cfg for this matter) is honored unless --expand-macros is being used.


Merge create-app-and-install-basic-dependencies-setup branch into development branch

The following activities were carried out:

[x] Create React App.
[x] Install React-Redux, Redux Logger, and React Router.

Hey @aristides1000 ,
This is a great project you have going on, well-done lad.
Your project is complete! There is nothing else to say other than... it's time to merge it*

Required Changes ♻
Check the inline comments under the review for sections to improve.
Optional suggestions
Every comment with the [OPTIONAL] prefix is not crucial enough to stop the approval of this PR. However, I strongly recommend you to take them into account as they can make your code better.
Cheers and Happy coding!👏👏👏
Feel free to leave any questions or comments in the PR thread if something is not 100% clear.


Package.activateResources is deprecated.

The context menu CSON format has changed. Please see
https://atom.io/docs/api/latest/ContextMenuManager

Will be fixed in #135, so I will close this.


Add column object_lifecycle_policy in the table oci_objectstorage_bucket

Is your feature request related to a problem? Please describe.
Need to validate that the bucket is having life cycle rules defined or not.
Describe the solution you'd like
Describe alternatives you've considered
Additional context

https://registry.terraform.io/providers/hashicorp/oci/latest/docs/resources/objectstorage_object_lifecycle_policy

Not sure, why we have kept this column object_lifecycle_policy_etag


Event type not supported: customer.subscription.updated

If I cancel a subscription from Stripe, I'm seeing
Event type not supported: customer.subscription.updated

Does that need to be handled, or is it only customer.subscription.deleted that matters? Presumably, when the subscription period has ended, customer.subscription.deleted is then sent, even if the sub was already cancelled. If so, I guess this makes sense!

This may be because your customer portal is configured to cancel at the end of the billing period rather than immediately. Are you able to confirm?
Either way, this distinction should be documented.

Good shout!

Thanks, @umaar. I'll be sure to include this in the upcoming documentation rewrite. I'll close this issue for now, though.


Feat: add pre-loader animation

Is your feature request related to a problem? Please describe.
Currently, there is no pre-loader animation, when the site is loaded. We need to improve it
Describe the solution you'd like
I would like to add loading animation. Loading animations are notifications that reassure users that the system is still handling their request.
Record

[x] I agree to follow this project's Code of Conduct
[x] I'm a SSOC 2.0 contributor
[x] I want to work on this issue

The following is a rough sketch of how you can accomplish this using HTML, CSS, and JavaScript:

Create the HTML structure:
Start by creating a simple HTML structure for your pre-loader animation. We can use a  element as the container for the loader.

CSS the pre-loader container:
Next, add some CSS to style the pre-loader container. We may center it on the screen and use whatever animation we like.

Add the JavaScript to conceal the pre-loader after the page has loaded:
Finally, we must include some JavaScript to hide the pre-loader after the site's content has entirely loaded. You may use either the window.onload or the more recent DOMContentLoaded event.

@Ashish1100 thanks for the workflow. Please assign me this issue, so that I can start working on it.


Update FreeMarkerExecutor.java

What type of PR is this?
 Bug Fix
What does this PR do / why is it needed ?
 overrride user's issue with adding special character combination <@ and being unable to get service executed
Which issue(s) this PR fixes:

Fixes #
Other notes for reviewers:
Does this PR introduce a user-facing change?

Tests?


Update README

In GitLab by @arcln on Jan 29, 2020, 00:06

In GitLab by @arcln on Mar 11, 2020, 04:54
mentioned in merge request !16

In GitLab by @paul.laffitte on Oct 8, 2020, 20:20
mentioned in commit 490649820e2e155a0f8799a23d0b6a309bd2e424


Contentlayer is no longer maintained and causing multiple build errors on first try

Describe the bug
A clear and concise description of what the bug is.
Loads of build errors on first try due to contentlayer
To Reproduce
Steps to reproduce the behavior:
download zip of repo, open zip and npm install dependencies

Go to '...'
Click on '....'
Scroll down to '....'
See error

Expected behavior
A clear and concise description of what you expected to happen.
the app to build out of the box
Screenshots
If applicable, add screenshots to help explain your problem.

System Info (if dev / build issue):

OS: [e.g. iOS] Linux Fedora 39, VSCode latest
Node version (please ensure you are using 18+)
18.18
Npm version
10.2.5

Browser Info (if display / formatting issue):

Device [e.g. Desktop, iPhone6]
Browser [e.g. chrome, safari]
Version [e.g. 22]

Additional context
Add any other context about the problem here.
I think V3 should abandon contentlayer if it's not being maintained/causing dependency issues
Many thanks
Terry

Describe the bug A clear and concise description of what the bug is. Loads of build errors on first try due to contentlayer
To Reproduce Steps to reproduce the behavior: download zip of repo, open zip and npm install dependencies

Go to '...'
Click on '....'
Scroll down to '....'
See error

Expected behavior A clear and concise description of what you expected to happen. the app to build out of the box
Screenshots If applicable, add screenshots to help explain your problem.
System Info (if dev / build issue):

OS: [e.g. iOS] Linux Fedora 39, VSCode latest
Node version (please ensure you are using 18+)
18.18
Npm version
10.2.5

Browser Info (if display / formatting issue):

Device [e.g. Desktop, iPhone6]
Browser [e.g. chrome, safari]
Version [e.g. 22]

Additional context Add any other context about the problem here. I think V3 should abandon contentlayer if it's not being maintained/causing dependency issues
Many thanks
Terry

OK, upon restoring the Yarn lock file and using Yarn instead of NPM (I generally find NPM far more stable on my devices) I was able to build successfully - however there are still multiple warnings for Contentlayer and I'm a littlw worried about this going forward in regards to maintaining updated dependencies, etc. Is there any news on what's happening regarding Contentlayer?
Many thanks for all your work
Terry

I am trying to get it updated- https://github.com/contentlayerdev/contentlayer/pull/638, otherwise I might just maintain a fork of it.

@timlrx How long may it take to fix a problem with Contentlayer ? i wanna to use your blog starter kit ^^

@d90375 any specific problem you faced? Or just in general. The current setup with the blog actually works fine using yarn as eltel noted above. Npm complains about some peer dependency issues but you can just skip them. On the unified / markdown packages side, you just have to use the older version of most packages as the blog does or add a // @ts-ignore line above every plugin as the typing have changed.
So mostly minor inconveniences. In any case, if it were to be updated, the main change would just be to bump up the package versions - I don't expect much changes required.

I am trying to get it updated- contentlayerdev/contentlayer#638, otherwise I might just maintain a fork of it.

That sounds like a good move. Thanks for getting back to me - looking forward to continuing to use what is, IMO, one of the best starter templates for Next.js.
Thanks again for all you do.

maybe i am looking in the wrong spot but their might have been a fix made? https://github.com/tudoujunha/next-contentlayer/blob/main/components/mdx-components.tsx

Somewhere along the way I must have upgraded remark-gfm to v4 and this error started happening. I downgraded to v3.0.1 and it works again.

I have the same problem with the Vercel deployment. Do you have any idea about changing the contentlayer lib to another tool? Does it indicate any?

Somewhere along the way I must have upgraded remark-gfm to v4 and this error started happening. I downgraded to v3.0.1 and it works again.

I'll give this a try. It's a pity, though, as I like to keep my dependencies up to date as much as possible. Downgrading always seems like just sticking a Bandaid on a bigger problem and invariably leads to dependency issues further down the line.


Added IndexDatatype.fromTypedArray

Similar to ComponentDatatype.fromTypedArray

Thanks for the pull request @lilleyse!

:heavy_check_mark: Signed CLA found.

Reviewers, don't forget to make sure that:

[ ] Cesium Viewer works.
[ ] Works in 2D/CV.


Agents Discussion

I'd like to discuss what is needed to build an Agent using Grafo. Agents have agency, and off the top of my head I can think of the following:

Task splitter: splits user input into tasks, which the agent can choose tools for.
Task Clusters: if we think of our Instructor classes as tasks, a cluster could compose a tool.
Inner Memory: results of tools are fed to the inner memory of the agent, so that it can keep track of what tasks were processed and their results
The output of each cluster must signal whether the original request has been fulfilled.

I'd love to hear your thoughts. @molinavinicius @1r4t4

Broad prompts increase specific training dependency. Short steps with low noise is the way.


compiler should generate error "method foo1 in class C must be called with () argument" for inherited nullary method without arguments that has extra overloaded function in child class

Scala 3.3.3 (same with 3.5.1-RC1)
I am using the language specification at 1 & 2 & 3.
Use the code below:
(It might be convenient to use worksheet to see the evaluation result)
trait T { // NOTE: it can abstract class or class, it doesn't matter
  def foo1(): Int = 1
  def foo2(x: Int): Int = 33
}

class C extends T {
  def foo1(x: Int): Int = 11
  def foo2(): Int = 33

  def foo3(): Int = 2
  def foo3(x: Int): Int = 22
}

val c = new C
val x1 = c.foo1
val x2 = c.foo2
val x3 = c.foo3

Notice that  c.foo1 compiles fine and evaluates to 1
However for c.foo2 and c.foo3 compiler generates a syntax error: method foo3 in class C must be called with () argument

According to spec the compiler should also generate an error for c.foo1:
 method foo1 in class C must be called with () argument
The exclusion can be Java methods, but foo1 is not defined in Java and not overridden.

Excluded from this rule are methods that are defined in Java or that override methods defined in Java.

Note that if you remove def foo1(x: Int): Int = 11 then the error IS generated.
It seems like the check if foo1 has some parameters somehow interleaves with overloading resolution and is done before   def foo1(x: Int): Int is discarded

BTW, just in case, is https://www.scala-lang.org/files/archive/spec/3.4/06-expressions.html considered to be up-to date?

cc @sjrd

This issue was picked for the Scala Issue Spree of Tuesday, July 23rd. @aherlihy, @EugeneFlesselle and @hamzaremmal will be working on it. If you have any insight into the issue or guidance on how to fix it, please leave it here.

Stepping through https://github.com/scala/scala3/blob/fb983dbb4ab130d1a178567e2cee999c8f4d3288/compiler/src/dotty/tools/dotc/typer/Typer.scala#L3998
In the case of foo2:

We find the candidates: [(c.foo2 : (): A), (c.foo2 : (x: A): A)]
resolveOverloaded picks (c.foo2 : (): A), which we recursively try adapting
We reach adaptNoArgs

Which finds needsEta := true since pt.revealIgnored := <?>
adaptNoArgsUnappliedMethod(arity = -1)

Does not insert () since isAutoApplied returns false
Goes into missingArgs which reports the error

In the case of foo1:

We find the candidates: [(c.foo1 : (x: A): A), (c.foo1 : (): A)]
resolveOverloaded does not disambiguate
And therefore apply the following logic, inserting the (), the absence of which in source in therefore not reported
https://github.com/scala/scala3/blob/fb983dbb4ab130d1a178567e2cee999c8f4d3288/compiler/src/dotty/tools/dotc/typer/Typer.scala#L4040-L4047

What are the next steps to solve this issue? @EugeneFlesselle, should we do what you suggest above, or does that need to be further discussed?

What are the next steps to solve this issue?

IIRC it would quite tricky to find a combination of conditions s.t.

we report warnings as expected in the submitted issue description,
without generating too many additional warnings in other existing code.


[ISSUE #3978]Remove unnecessary annotations in TopicCreateRequest and add unit test.

Fixes #3978.
Motivation
org.apache.eventmesh.admin.rocketmq.request.TopicCreateRequest

The field name is the same with @JsonProperty's value.
super() in this constructor will be invoked by default.
Unit test case is not yet done.

Modifications

Remove @JsonProperty.
Remove super().
Add unit test case.

Documentation

Does this pull request introduce a new feature? (yes / no)
If yes, how is the feature documented? (not applicable / docs / JavaDocs / not documented)
If a feature is not applicable for documentation, explain why?
If a feature is not documented yet in this PR, please create a followup issue for adding the documentation

@pandaapo please fix the ci check error.

@pandaapo please fix the ci check error.

OK now. I will check all my other PRs and fix if necessary.


Python 2 support?

README and setup.py claim that Python 2 is supported, but 27abd9de4b9394cf9444702be5cc0efce687e3ee ("Reformat with psf/black") added rb"…" strings, which is a Python 3.3+ syntax.
(I don't have any personal interest in running waybackpack under Python 2.)

Good catch, and thanks! I should have updated that a while ago. Now done here: https://github.com/jsvine/waybackpack/commit/febb1c2073a8f4d1d72b3e59ddcf2c0cfe72757d


How to run tests without docker?

Hello,
Fedora maintainer here. During upgrade to 6.x I noticed that many tests started to fail as they try to run docker.
I'm not very familiar with pytest infrastructure, so I would appreciate if you could help me to skip those tests.

Hey @ignatenkobrain, what's easiest for you? We'd originally planned that folks who wanted to skip the integration tests could do something like
pytest tests/test_*.py tests/unit

but we'd also considered a flag we pass to pytest to skip them as well.
Eventually we'll migrate all the tests/test_*.py to integration tests and you could do pytest tests/unit to effectively skip them.

well, any option is easy for me as long as it works :)

haha, I hear you. The above should work for you then. Lmk if you need a cleaner way to do it.


[DO NOT MERGE] Update dependencies to change to logrus 1.0.0

Signed-off-by: Mrunal Patel<EMAIL_ADDRESS>

LGTM if tests are ok

The test failure doesn't look related. Could you check?

yup, restarted

Still failing.

/Users/travis/build/projectatomic/skopeo/_gopath/src/github.com/projectatomic/skopeo/hack/make/validate-lint: line 14: golint: command not found
make: *** [validate-local] Error 127

@mtrmac have you ever seen that? first time here :/

@runcom I haven’t yet, but I will be setting up a macOS environment anyway, so I’ll take a look.

LGTM pending tests.

LGTM pending tests.

Needs a rebase?

Yup, this just needs a rebase from travis's failure

Rebased.


disable automatic derivation

My team prefers semi-auto derivation as per https://github.com/fommil/stalactite
It would be great if you followed the pattern for derivation laid out in https://github.com/milessabin/export-hook to

avoid lots of corner cases you may not have considered
allow users to opt-in to full generic derivation

thanks for a great library!

It's something I've discussed before and it's definitely the approach I would try and take were I starting from scratch.
I'm not planning to work on it myself imminently, but I'd be open to a PR and discussing a migration approach.

stalactite dramatically speeds up compiletimes, btw... we can talk about it at scala world if you're going?

Would love to, but I've yet again failed to organise myself to go.


json-schema-ref-loader can't handle circular references

A simple JSON schema:
{
    "$schema": "http://json-schema.org/draft-04/schema#",

    "definitions": {
        "node": {
            "title": "a node",
            "type": "object",
            "properties": {
                "children": {
                    "type": "array",
                    "items": {
                        "$ref": "#/definitions/node"
                    }
                }
            }
        }
    }
}

causes json-schema-loader to fail with the following error:
ERROR in ../src/schema/node.json
Module build failed: TypeError: Converting circular structure to JSON
    at JSON.stringify (<anonymous>)
    at Object.handleResolveSuccess (/Users/fabian/projects/node-lib-spec/schema-doc/node_modules/json-schema-loader/lib/loader.js:19:21)
    at <anonymous>

I can fix it locally if I apply the change proposed in https://github.com/cloudflare/json-schema-loader/pull/3

@handrews Do you know if a solution has been worked on since last update in April 2018?  The project I'm working on uses getCollapseAllOfCallback for collapsing the allOf, but apparently, it won't work for circular reference although the RefParser was able to handle circular reference.


Support bearer token

This pull req just add a Bearer token support in Authorization header to crowi.
NOTE: the format of Authorization header with Bearer token

Oh, sorry.
I changed that 'var' with const. 👍

Thank you for the great PR. Merged!


Update secure-delegate-default-to-minimal.md

Harness Developer Pull Request
Thanks for helping us make the Developer Hub better. The PR will be looked at
by the CODEOWNERS.
What Type of PR is This?

[ ] Issue
[ ] Feature
[ ] Maintenance/Chore

If tied to an Issue, list the Issue(s) here:

Issue(s)

House Keeping
Some items to keep track of. Screen shots of changes are optional but would help the maintainers review quicker.

[ ] Tested Locally
[ ] Optional Screenshot.

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step behind the Harness VPN and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app. Current Draft URL is: https://65c638c7972428007f17c313--harness-developer.netlify.app


Fix generated sidebar YAML

As of now, the _sidebar.yml that is generated puts the sidebar on all pages, which doesn't make much sense. Instead, it should look like this:
website:
  sidebar:
    - id: reference
      title: Function reference
      collapse-level: 2
      style: "floating"
      align: left
      contents:
      - reference/index.qmd
      - contents:
        - reference/board_folder.qmd
        - reference/board_local.qmd
        - reference/board_temp.qmd
        - reference/board_s3.qmd
        - reference/board_gcs.qmd
        - reference/board_azure.qmd
        - reference/board_connect.qmd
        - reference/board_url.qmd
        - reference/board.qmd
        section: Boards
      - contents:
        - reference/pin_read.qmd
        - reference/pin_write.qmd
        - reference/pin_meta.qmd
        - reference/pin_versions.qmd
        - reference/pin_list.qmd
        - reference/pin_exists.qmd
        - reference/pin_version_delete.qmd
        - reference/pin_versions_prune.qmd
        - reference/pin_delete.qmd
        - reference/pin_search.qmd
        section: Pins

If I'm understanding correctly, the issue with the current sidebar is that the entry under sidebar is a mapping, when it it should be a list. Does that sound right?
currently:
website:
  sidebar:
    contents:
    - reference/index.qmd
    - contents:
      - ...
    id: reference

should be:
website:
  sidebar:
    # note the leading -
    - contents:
      - reference/index.qmd
      - contents:
        - ...
      id: reference

I have no idea why this somehow worked with the documentation sites for shiny, siuba, and vetiver, but am guessing it has to do with them having another sidebar section (e.g. shiny's "learn shiny" pages) with sidebars (maybe due to the way quarto merges content).

I am not able to remove the sidebar on the site index page by making the change. I was able to remove it by adding an additional dummy sidebar entry.
Testing suggested change
Here is how I tested without the dummy entry (note that sidebar is still visible from index 😓).
index.qmd
---
---

I am a test page

_quarto.yml
project:
  type: website

metadata-files:
  - _sidebar.yml

quartodoc:
  # the name used to import the package
  package: quartodoc

  # write sidebar data to this file
  sidebar: _sidebar.yml

  sections:
    - title: Some functions
      desc: Functions to inspect docstrings.
      contents:
        # the functions being documented in the package.
        # you can refer to anything: class methods, modules, etc..
        - get_object
        - preview

_sidebar.yml
website:
  sidebar:
  - contents:
    - reference/index.qmd
    - contents:
      - reference/get_object.qmd
      - reference/preview.qmd
      section: Some functions
    id: reference

Dummy entry
I was able to get the sidebar to disappear from the index page by adding this to _quarto.yml.
website:
  sidebar:
    - id: dummy

Oh, interesting, yep, I did have a something like this in my _quarto.yml:
  sidebar:
    - id: test

OK, this does seem like a problem with Quarto which might be worth surfacing.

Ah, OK, I think there is special behavior if there is only one sidebar. This works fine:
  sidebar:
    - id: dummy
    - id: reference
      title: Function reference
      collapse-level: 2
      style: "floating"
      align: left
      contents:
      - reference/index.qmd
      - contents:
        - reference/board_folder.qmd
        - reference/board_local.qmd
        - reference/board_temp.qmd
        - reference/board_s3.qmd
        - reference/board_gcs.qmd
        - reference/board_azure.qmd
        - reference/board_connect.qmd
        - reference/board_url.qmd
        - reference/board.qmd
        section: Boards
      - contents:
        - reference/pin_read.qmd
        - reference/pin_write.qmd
        - reference/pin_meta.qmd
        - reference/pin_download.qmd
        - reference/pin_upload.qmd
        - reference/pin_versions.qmd
        - reference/pin_list.qmd
        - reference/pin_exists.qmd
        - reference/pin_version_delete.qmd
        - reference/pin_versions_prune.qmd
        - reference/pin_delete.qmd
        - reference/pin_search.qmd
        section: Pins

While this shows up on all pages:
  sidebar:
    - id: reference
      title: Function reference
      collapse-level: 2
      style: "floating"
      align: left
      contents:
      - reference/index.qmd
      - contents:
        - reference/board_folder.qmd
        - reference/board_local.qmd
        - reference/board_temp.qmd
        - reference/board_s3.qmd
        - reference/board_gcs.qmd
        - reference/board_azure.qmd
        - reference/board_connect.qmd
        - reference/board_url.qmd
        - reference/board.qmd
        section: Boards
      - contents:
        - reference/pin_read.qmd
        - reference/pin_write.qmd
        - reference/pin_meta.qmd
        - reference/pin_download.qmd
        - reference/pin_upload.qmd
        - reference/pin_versions.qmd
        - reference/pin_list.qmd
        - reference/pin_exists.qmd
        - reference/pin_version_delete.qmd
        - reference/pin_versions_prune.qmd
        - reference/pin_delete.qmd
        - reference/pin_search.qmd
        section: Pins


DiscImageCreator does not fix C2 errors on BW-16D1HT drive with firmware 3.10

Version
I have latest test version
Describe the bug
When DIC encounters a C2 error while dumping a disc, it does not try to fix it. This problem was previously present on the BH16NS40 drive, now it is present on the BW-16D1HT. The problem appeared after changing the firmware from 3.00 to 3.10 (I'm using this modded firmware from RibShark), in the earlier firmware repairing C2 worked fine. Since fixing C2 works in other programs (e.g. in redumper) I suspect that the DIC is trying to use the read cache command in this firmware, but the 3.10 firmware no longer supports this command. Is it possible to introduce a rule in the code so that the DIC does not use the read cache command when using firmware 3.10 for BW-16D1HT? If that's not where the problem is, then I have no idea where (I'm not a programmer)

I don't know the modified firmware. What can be done with that firmware?

RibShark wrote about this modded firmware on VGPC Discord. In short, he modified firmware 3.10 enough to enable lead-out reading without the cache trick. The firmware can be downloaded from this link - https://cdn.discordapp.com/attachments/429374270607720461/960431754357927946/ASUS-BW-16D1HT-3.10-WM01601-211901041014_MK_edited.bin (here is a link to a flasher that can flash the firmware - https://www.mediafire.com/file/8zujcivqfiidq7b/SDFtool+Flasher+(v1.3.3).zip/file )

And about flashing this firmware, flash the 3.10MK firmware first - https://cdn.discordapp.com/attachments/351024247411441664/861691990835986490/ASUS_ODD_FW_Changer_-_ASUS_BW-16D1HT-3.10-MK.exe, and then flash this RibShark firmware

I have that - https://mega.nz/file/Jyg1zDAL#VOpMUGtWaeozD74Ylnw1a5mIcdrbdtzBqyoT2H4cBP0
https://mega.nz/file/sjgiHA7I#UydGt6mtAzePib7QwBn5pjapq1cMXl1Q3wzShhJo594
The drive seems to give identical hashes for C2 errors, but I have the impression that the DIC tries to use the cache command in this drive, regardless of whether the drive's firmware supports this command or not (and the 3.10 firmware does not support the cache command). Giving identical data for C2 errors is not a feature of the drive firmware because, for example, the redumper corrects the C2 errors correctly on the same drive and the same firmware - https://mega.nz/file/8vQ1BJrL#tmdvJW8blaXNBI0PZV5rO9JEVLyqgjP0KCnwRtdbIvw

I have the impression that the DIC tries to use the cache command in this drive

It's no. The drive and firmware can read the lead-out correctly like plextor. DIC doesn't use the cache command in the firmware.
This drive (BW-16D1HT        3.10 WM01601SIK9QH28G165 ) can read data sectors at scrambled state [OpCode: 0xbe, C2flag: 1, SubCode: 0]
This drive (BW-16D1HT        3.10 WM01601SIK9QH28G165 ) can read data sectors at scrambled state [OpCode: 0xbe, C2flag: 1, SubCode: 1]
This drive (BW-16D1HT        3.10 WM01601SIK9QH28G165 ) can read data sectors at scrambled state [OpCode: 0xbe, C2flag: 1, SubCode: 2]
This drive (BW-16D1HT        3.10 WM01601SIK9QH28G165 ) can read data sectors at scrambled state [OpCode: 0xbe, C2flag: 1, SubCode: 4]
Checking reading lead-out -> OK

C2 error fixing function can be read correctly, but correct hash can't get forever? I'm not sure about the reason now.

DiscImageCreator_test.zip

changed: transfer length

Fixed, thx


Fix typos referenced in #2

I doubt that deleting "All righrs reserved .. MIT License" will get this PR merged.

Thanks for the suggested edits, but as noted above, we cannot change the terms of the license. I will, however, fix-up the formatting issues noted. Thanks for taking a look and submitting suggested improvements.

@bitcrazed Reason for that was to make the text the same as the text listed at https://opensource.org/licenses/MIT, so github would detect it.


Copying/moving files doesn't work

Description
Sometimes when dragging one or multiple files over to another folder to move or copy them, the activity box says that the files have been copied or moved, but the files aren't actually there.
Steps To Reproduce

Open 2 windows of the files app
Select one or multiple files/folders
Drag the selected files/folders to another folder in the second window of the files app
Click the activity button to see that the files have been copied
Check the destination folder to see that the files are not there

Expected behavior
The files and folders should have been moved or copied.
If for whatever reason they can't be moved or copied there should be an error message, and the activity tab should not say the task is completed.
Files Version
<IP_ADDRESS>
Windows Version
Editie	Windows 11 Home Versie	21H2 Installatiedatum	17-12-2021 Build van besturingssysteem	22000.434 Serienummer	R90YKX11 Ervaring	Windows Feature Experience Pack 1000.22000.434.0
Relevant Assets/Logs
n/a

Something to note with this issue is that it can be resolved when quitting files through the task manager.
The bug also doesn't always appear.
I do work a lot with cloud storage, that might be relevant.

When this happens, does it also happen in the normal windows explorer? Sometimes I try to move files and it is frozen in both windows explorer and files.

When this happens, does it also happen in the normal windows explorer? Sometimes I try to move files and it is frozen in both windows explorer and files.

No, for me it still works in the windows file explorer when this happens

yes same issue. cut/copy/paste works inside the Files but if i try to cut it from desktop to any specific folder it does not work (if i try copy, it works)

Forpeople who have thsi issue can you upload the logs files directly to github. You can get them in files settings > about > open log folder.