Node package

Would you be interested in turning this into a proper Node.js package, possibly even with TypeScript support? This would make it easier to integrate the code into other codebases. For instance, instead of manually copy-pasting the source code files, one could do:
npm install codec-string

Then:
import { decode } from 'codec-string';

decode("…");

The source code and files would mostly stay as they are; they'd just be packaged quite differently. I can provide a (somewhat large) PR for that, but it'd also be a bit of a maintenance burden for you in the long term.
I could also provide my own NPM package based on your code if that's easier for you.

I certainly agree with making this capability available as a node.js module, but have a couple of considerations

It would be good to ensure that 'browser use' is not inhibited. Even now, one can clone this repo and use any browser as their local application framework.
A module should be able to produce both HTML formatted and object based results for example decode("...") produces an  object while decode("...").text() and decode("...").html() produce textual and HTML marked up formats.

Some further elaboration of the 'maintenance burden' would be nice. Ideally any new decoder should be straightforward in its inclusion into a node module, although I understand that publishing on npm will require some additional documentation and effort.

Great, thanks for the feedback!
Regarding browser use: no problem. It would be preferable to provide a CommonJS module (for Node.js), an ES module (for “modern” tools), and a UMD module, the latter of which can directly be imported in browsers. The NPM build script would produce a codec-string.min.js file (or similar) which could directly be used in a <script> tag for import.
As for maintenance: I didn't mean to imply that adding a new decoder would become harder; that should be the same effort. Maybe I'd add a test suite to cover the currently implemented codecs. It's the publishing part that takes a bit more effort, although I think the maintenance over the lifetime of the package should be minimal, seeing that it does not have any runtime dependencies (which are often the source of breakage or security issues).
I'll provide a PR once I have a first draft ready.

As for the HTML and textual output, I have to check the code base in detail. It appears like we'd need to separate the concerns a little bit.
Currently, formatting is mixed in with the information, and there is no dedicated error handling. This would make it hard to use the libraries within another library.
For programmatic use, it would be preferable to be able to extract raw, unformatted string representations, and handle errors through try/catch. For HTML use, a dedicated formatter function could be provided. Perhaps the extracted codec information will be stored in an intermediate, internal format, from which both raw and formatted strings could be extracted. Errors would simply be thrown and left for the user (or HTML formatting function) to catch.

What type of 'output' do you expect that a node.js application will need? Knowing that will help with improving the function calls to return something that is applicable (rather then just an HTML markup that is done today - that is what I needed at the time)
I will think some more about having each decoder return a class that can be further processed by the caller (or use some basic processing from the library). For example, the return could be
{name, overall_error,
[{line, error [OK, WARNING, ERROR]},
 { },  ... ]}

if overall_error==null then you will likely find some decoded lines.

Thinking about it more, some kind of structured output would be ideal for later programmatic usage. I realize though this is not what you intended this code to do, and that this might add some extra work.
Here's a dummy example using TypeScript definitions for the decoded info, an abstract decoder class with a factory for the actual decoders (based on the string prefix), and a toHtml method that takes the decoded info.
This would allow you to do:
try {
  const decodedInfo = CodecStringDecoder.decode("av01.2.15M.<IP_ADDRESS>.16.09.0");
  console.log(decodedInfo);

  const html = CodecStringDecoder.decodeToHtml("av01.2.15M.<IP_ADDRESS>.16.09.0");
  console.log(html);

  // direct usage:
  const av1Decoder = new Av1CodecStringDecoder();
  const av1DecodedInfo = av1Decoder.decode("av01.2.15M.<IP_ADDRESS>.16.09.0");
  console.log(av1DecodedInfo);
} catch (error) {
  console.log(error);
}

Error handling will be done by means of exceptions.
That said, if errors should be allowed while still creating some output, an error property could be added to the return type.

PS: I'm willing to convert your existing code, of course, once we agree on how to proceed. If you believe that this would go way beyond what you initially intended, I could of course just create a new project! Just let me know what you think.

I'm happy to expand the current code base to suit different use cases (without breaking the original ambition) so give me some time to update the codebase to provide generic, reformattable results and then you could repackage that for node.js etc.

From: Werner Robitza @.>
Sent: Tuesday, January 31, 2023 7:59:05 PM
To: paulhiggs/codec-string @.>
Cc: Paul Higgs @.>; Comment @.>
Subject: Re: [paulhiggs/codec-string] Node package (Issue #2)
PS: I'm willing to convert your existing code, of course, once we agree on how to proceed. If you believe that this would go way beyond what you initially intended, I could of course just create a new project! Just let me know what you think.
—
Reply to this email directly, view it on GitHubhttps://github.com/paulhiggs/codec-string/issues/2#issuecomment-1410224710, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AAYDGF3O2BJRGHJSXTMTCF3WVD5ATANCNFSM6AAAAAAULPNHEM.
You are receiving this because you commented.Message ID: @.***>

I have created a fork of this project that keeps the current design of producing HTML output, but using ESM modules. This allowed me to use the code in a project where putting everything in the global JS namespace wasn't an option.
Annoyingly, it shows up as a lot of code changes (due to editor whitespace cleanup) but isn't actually that many changes. Hence why I didn't make it a pull request to the main repository.
https://github.com/asrashley/codec-string/pull/1

Thanks @asrashley, I have merged your fork, and subsequently updated the enviroment to work with VScode, eslint and perttier.


Update Unifi and package versions

@jmcphail thank you!

Thank you for the continued support, any progress on getting this package into the pfSense source tree so we can update easily from the package browser?

@kklouzal its something I believe that the original package maintainer @gozoinks envisioned, and I have looked into it briefly.  Before this happens, we need to fix the package dependency installation (having to manually update the list is not a long-term solution), which I have made some progress on.

Beat me to the punch 👍  This patch worked great on my pfsense 2.3.2 build

Yes, the dependencies and the proprietary binary are the obstacles. Automating these inclusions in a reliable, maintainable, and compliant way is the challenge.
Nevertheless, if someone were inclined to put together a test repository and a framework for a package, we could be a little further along when we come back to these details.

test repository

You can do that by creating a new branch and PRing the current code from main repository to dev repository...


Can't rebuild working teamviewer image with teamviewer 12

If I try to rebuild the docker image for teamviewer it builds and starts up fine, but the GUI never appears. If I look at the logs or run it with docker run -it it just stops at Launching TeamViewer GUI ...
I really like the this docker image and how it's constructed. The makefile is really nice. But I need teamviewer 12 and can't get it to work.
Log:
Cleaning up stopped teamviewer instances...
Starting teamviewer...

Init...
Checking setup...
err:ole:CoGetClassObject class {4315d437-5b8c-11d0-bd3b-00a0c911ce86} not registered
err:ole:CoGetClassObject class {4315d437-5b8c-11d0-bd3b-00a0c911ce86} not registered
err:ole:CoGetClassObject no class object {4315d437-5b8c-11d0-bd3b-00a0c911ce86} could be created for context 0x3
wine: configuration in '/opt/teamviewer/profile' has been updated.
Launching TeamViewer ...
Starting network process (no daemon)
Network process started (459)
Launching TeamViewer GUI ...

I can get it to work, if I drop back to the initial commit in the repo, rebuild and change the APP_REPO variable in the start script.

I will take any pull request as long it is reasonable.
On Oct 4, 2017 10:20 AM, "Anian Z"<EMAIL_ADDRESS>wrote:

I can get it to work, if I drop back to the initial commit in the repo,
rebuild and change the APP_REPO variable in the start script.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/hurricanehrndz/docker-containers/issues/11#issuecomment-334210492,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AFiQzQL50uFk8JlnMDLKN6XD6ufv-96pks5so7BNgaJpZM4PtyvZ
.

I will see if I can make out the issue and get it to work :)

Thanks, I was under the impression that the build from the first commit
works??
On Oct 5, 2017 3:02 AM, "Anian Z"<EMAIL_ADDRESS>wrote:

I will see if I can make out the issue and get it to work :)
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/hurricanehrndz/docker-containers/issues/11#issuecomment-334404822,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AFiQzXK_TFC8t-mVj4-M1LLPcAdp1evWks5spJtBgaJpZM4PtyvZ
.

Yes. I'm currently diffing that against the current version to find out what's causing it 🤔

I have exactly the same error. Your PR is it ready or "not starting" as the name let me to hear ?
Thank you :)


⚠ Bofrost.lu has degraded performance

In d9bd146, Bofrost.lu (https://www.bofrost.lu) experienced degraded performance:

HTTP code: 200
Response time: 1480 ms

Resolved: Bofrost.lu performance has improved in cdf1ad2 after 58 minutes.


create a whats-going-on page

create a page called
whats-going-on.html under src/news-and-events/
with headers and footers from
src/contact.html
and include that in webpack.config.js accordingly.

create folders as needed

Make sure you change the title in html page to What's Going On | CEA

If anyone is on this, first say it here!

i'll try

[Merged] #169
Closing.


Fixed state interfaces

Related with this issue https://github.com/ros-simulation/gazebo_ros2_control/issues/52
FYI @olivier-stasse
Signed-off-by: ahcorde<EMAIL_ADDRESS>

Thanks a lot for your reactivity.


Translate Valkyrie to nonEnglish nonSpanish languages

Valkyrie APP now supports multilanguage. We need foreign colaborators to translate de App to:

French (PARTIAL)
German (PARTIAL)
Italian (PARTIAL)
Portuguese
Polish
Japanese
Chinese

The localization file is here: link
For acutes, east-asia characters or other special characters it is recommended to view the localization file with the MAD font, in order to be compatible with Valkyrie. font
Instructions are easy. Edit the Localization file, translate each line in the language position. What is the language position? Look at the first line of the file and look what position corresponds to your language. IE: German translation should be bethween fourth and fifth comma. If the translated text includes commas wrap all message between double quotes ("). Some texts contains a {0} text. This is a replacement key for a variable word. The translation should have the {0} where corresponding.
Any doubt ask here. If you begin the translation comment here in order to not do it twice.

I created a pull request for the german translation

I for italian translation.

Where are the updates?

Sorry, I'm newbie.
I edited Localization.txt with italian traslated and after I sent the"Propose file change".
Did I do something wrong?

Da: NPBruce<EMAIL_ADDRESS>Inviato: domenica 9 aprile 2017 23.14
A: NPBruce/valkyrie
Cc: Landar77; Comment
Oggetto: Re: [NPBruce/valkyrie] Translate Valkyrie to nonEnglish nonSpanish languages (#195)
Where are the updates?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHubhttps://github.com/NPBruce/valkyrie/issues/195#issuecomment-292813522, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AZ2eKVufhMho4kxl6MLSt0umrZNIoa3Kks5ruUpBgaJpZM4M1b2E.

It looks like you've forked the repo and created two branches (patch-1 and patch-2).  I think patch-1 is the correct one?
I have raised a 'pull request' here to move this into the main repo:
#223
Please check if this is correct.
I noticed a comment regarding testing, you need to build this in, if you like I can upload a dev build here after the pull request (you can always do more pull requests to fix mistakes).

Also note that you can just attach the file directly to this issue if that is easier.

Correct!  This Github is a new world for me. XD
I begin to understand.

Italian added in 0.8.7.

Italian added in 0.8.7.

Sorry. Did you enable in the options screen the language selection buttons? I disabled all but English and Spanish

Yep.

I've just started the French translation.

Thanks, Added.

Happy to give a little help on this great project 👍

Added new localization elements:
CONFIRM
FAIL
NONE
PASS
and all elements in Localization.txt file between
//Items
and
//Inherited from FFG localization files
Please complete your translations.

I have just removed CONFIRM, FAIL and PASS, they are not needed (only for legacy support and didn't work anyway).

not only the NONE key must be translated. There are many traits to translate between the line //Items and the line //Inherited from FFG ...

and EVENT_DOOR_DEFAULT_TEXT
sorry. I forgot... T_T

No prob. Already found it 😄

French added. Pull request #279. Ignore #278.

There are some entries that in the Localization.txt, that appear multiple times like:
small, medium

I translated the example quest and The Fall Of House Lynch to german.

The buttons of default mythos events don't seem to be translated like: "Resolve Event", "No Effect" and "Continue".

This has been fixed, but not in a published version.

It is fixed in release 1.1.0a.

Should be fixed in 1.0.0 also.

New translations required:

QITEM (Quest Item or Special Item)
KO
SKILLS
ITEMS
GOLD
NONE
AUTOSAVE
SELECT_SAVE
SELECT_CLASS
HIDDEN
ACTIVE
SELECT_SKILLS
STARTING_ITEM
UI
UNITS
HORIZONTAL
VERTICAL
ALIGN
POSITION
SIZE

This is still being worked on and changed, so don't get to eager.

@eorahil There are new entries in the development branch, that need more spanish ;)

Hi Guys, I send the localization text for Portugues

If anyone is interested, heres is a good example of how to fork, change files and do a pull request. https://www.youtube.com/watch?v=_NrSWLQsDL4
It works for basic stuff without any tools. However, NPBruce is using https://www.sourcetreeapp.com/ to sync his lokal files with github. I use https://tortoisegit.org/ as it comes with windows explorer integration.

Thanks @redwolf2 , gonna see this tutorial.

Here is a simple explaination:

Goto https://github.com/NPBruce/valkyrie press the "Fork" Button. Click on your user icon and goto "Your Profile". Click on your own "valkyrie" repository.
Navigate to: https://github.com/<your username here>/valkyrie/blob/master/unity/Assets/Resources/Text/Localization.txt
Change the file.
After that go from "Code" to "Pull Request" and create one there.

There is now a new file that needs translations:
https://github.com/NPBruce/valkyrie/blob/development/content/MoM/base/Localization.English.txt
This is because content packs can now have their own dictionaries.

Hi. Im gonna handle Polish translation.

This system has changed a fair bit for 1.4, hopefully much easier now.
I have created new documentation here:
https://github.com/NPBruce/valkyrie/wiki/Translations


Surface coverage report to GitHub, gate on coverage level

Is your feature request related to a problem? Please describe.
This is related to issue #15 - to caikit CI infrastructure rather than caikit itself.
Describe the solution you'd like
to keep the coverage level above the desired threshold it would be helpful to have the coverage data published as a comment on PRs and possibly enforce a minimum level of coverage required.
This helps PR reviewers to catch PRs that would reduce coverage before they are merged.
Describe alternatives you've considered
There are github apps in the marketplace that could provide this feature, like for instance python-coverage. I'm not recommending this one specifically, it would need to be verified.

I would be happy to help with this.


PrometheusRule added up == 0 rule does not take effect

Add the up alarm rule as shown below in the PrometheusRule alarm rule file. After apply, the rule file is created successfully, but this file is never added in the /etc/prometheus/rules/prometheus-k8s-rulefiles-0 directory of prometheus.

Log in to one of the prometheus pods and go to the rules directory. There is still no rule file I just created.

I tried to delete the up rule, and I was able to successfully generate a rule alarm configuration file in the rules directory of prometheus.

My k8s version is eks-1.28.4, and the kube-prometheus version used is the latest 0.13.0 version


[MCLEAN-93] Support junctions on NTFS

Jira issue: MCLEAN-93

I'm investigating if I can setup a test on windows.  I've been sidetracked by trying to switch the tests to junit 5 / plexus-testing, but it's missing the helper methods to setup/lookup mojos...
I'll provide one asap.

When can this happen? I mean, can we create a junction in Java without using native code?

I'm experimenting with something like:
        Path testDir = Paths.get( "target/test-dir" ).toAbsolutePath();
        Files.createDirectories( testDir );
        Path orgDir = testDir.resolve( "org-dir" );
        Path jctDir = testDir.resolve( "jct-dir" );
        Files.createDirectories( orgDir );

        Process process = new ProcessBuilder()
                .directory( testDir.toFile() )
                .command( "mklink", "/J", jctDir.toString(), orgDir.toString() )
                .start();
        int result = process.waitFor();

The idea comes from https://www.geeksforgeeks.org/creating-junction-points/

When can this happen? I mean, can we create a junction in Java without using native code?

The test is here: https://github.com/apache/maven-clean-plugin/pull/10/files#diff-f51e0a6f6bcc199bb061d2f1b751c0740ae8cd016a1e87b5349758c4ee96e7d1R297-R321

When can this happen? I mean, can we create a junction in Java without using native code?

Not sure if you are asking about this regarding "tests" or regarding what "real world" use case this could occur in, but if asking in the second case:
NPM does this on Windows.  So if you link a NPM component with a package.json like:
{
  ...
  "dependencies": {
    "someTestServer": "file:src/test/node_server/someTestServer"
  }
}

You will get a node_modules directory like:
node_modules/someTestServer <- Junction Point pointing to: src/test/node_server/someTestServer
If you configure mvn clean to delete node_modules (or a directory above node_modules) - it will walk the junction point and delete your src files.


Cleanup logging

Use logger package with standardised messages
Add verbose flag
Use 'silent' kubectl when verbose is not set (default)

I used the branch and everything worked great 👍  . I run the install with the --verbose flag.
Given the fact that we do have a verbose flag, that verbose flag can start adding messages on the install command. I'm not sure if the feedback asked was for this PR or for future reference, so please feel free to ignore if this is not the right place.
With the verbose flag on installation, I would mention to the user what namespace we are installing things, storageos, etc... What components we are enabling, some are by default, some are explicit. I'd mention that we are enabling all the components that may or may not be installed. Portal-manager, Node guard, metrics, etc.
I think we are good with what we have, but I leave this as feedback for a verbosity increment on the messages.

Thanks @Arau, that's great feedback. I will keep that in mind going forward for future PRs 👌


Utf8 language issue fixed in new version

@hadifar  I've merged the last PR with Development branch. What is the difference between that and this one?

Just created two different PR for Pep8 and Utf8 issue but it seemed not work as I expected.


mwc-textfield and mwc-textarea

Fixes #293
Finished up Frankie's implementation of mwc-textfield.
Some TODOs:

Need to implement mwc-floating-label and see how it fits in here
After publish, create gist, stackblitz, and glitch examples for readme

on its own, it works. Just will have to update for following element.

I think this one should also close #154

rebased to tachometer branch. Resuming work on this

Ran this adapter/foundation implementation vs component implementation and tachometer results in 2-4% faster @ 1000 element creations but statistically insignificant at 10

rebased onto #313

blocked by #309

maybe this would be closing as well #17 and #14

Ready for review

cc @aomarks for README 👀

rebased


Question:  what hook determines the data that is sent to resource data a list?

We are struggling to figure out where the data comes from for any resource on a List page. So for example in OrderList.tsx in the orders app, you have the FilteredList component, which sends the data to the ListItemOrder template. But the data provided thru the ListItemOrder is a resource prop. Where does the data come from for the resource? It's only has certain information from the order, but we wanted to display additional information on the list. We thought we can do that by adding a query to the FilteredList, like below, but none of that information shows up in the resource for the list. So how do we get additional data in the list? The only optio we saw that worked was to just call a useOrdersDetails hook for every single item in the list, but this seems like a wasteful query and we will hit the API a significant amount of time for each item in the list. But how can we do it otherwise? Which hook controls the data that is sent back to the list?
<FilteredList
          type='orders'
          ItemTemplate={ListItemOrder}
          query={{
            include: ['customer']
          }}
          metricsQuery={{
            search: {
              limit: 25,
              sort: 'desc',
              sort_by: isPendingOrdersList
                ? 'order.updated_at'
                : 'order.placed_at',
              fields: ['order.*', 'billing_address.*', 'market.*','customer.*']
            }
          }}
          hideTitle={viewTitle === presets.pending.viewTitle}
          emptyState={
            <ListEmptyState
              scope={
                hasActiveFilter
                  ? 'userFiltered'
                  : viewTitle !== presets.history.viewTitle
                    ? 'presetView'
                    : 'history'
              }
            />
          }
        />

OK, I see the problem here. The List Item is controlled by the ResourceListItem component. This component has a transform function apparently, so only some of the resource data is displayed, based on the hard coded transform function in the actual app elements code. I suggest you allow an additional data type prop that allows you to pass in additional data you want to be displayed as part of the ResourceListItem, because the tranform function doesn't always give the data that is needed. I know we can just create a new ListeItem component, but that's a bit more work. It would be easier if the ResourceListItem accepted some additional data that is not transformed.  Maybe allow the ability to pass in an additional component into the ResourceListItem, which can then display the additional data.

Hi @osseonews, I believe what you are trying to achieve would be possibile with the existing components.
The FilteredList component is a wrapper around the ResourceList exported by the useResourceList filters.
This means that the filtered list use the ResourceList but applies automatically the filters selected from the UI.
The orders app is the only one that leverages the metrics api (and not our core api) to fetch the list of orders, for performance reasons.
The data returned from metrics api does not support the including of relationships as our core api does.
What I see is not clear from the developer point of view is that is not possible to set both metricsQuery and query, since the first one will have priority.
When you specify a metricsQuery prop, the components will use the metrics api to fetch data and then then the transformation function will be executed to adapt the metrics response to the shape of our core api. Of course the transformation will be done only for the attributes that exists in metrics api.
What you can do now is to get rid of the metricsQuery prop and only use query prop, adding the include you want.
You will also need to modify the filter instruction object that is now shaped fore the metrics api attributes.
Mainly you will need to revert to the state where the app was before using the metrics api. A reference can still be found here: https://github.com/commercelayer/app-orders/pull/146/files
Let me know if this gets too complicate or it's still doable.

@gciotola Thanks. Actually, after messing around a bit with the code, we ended up doing the exact same thing as you suggested. The metricsquery is what really threw us off and when we deleted it, we noticed that you can't use that and query at the same time. But, if you get rid of the metricsquery you also need to fix the filter in the search for order. Thanks for the reference to the old repo, that was helpful in fixing some outstanding issues we had.
BTW, what's the benefit of using ResourceList alone over the FilteredList? From what I can tell the Resource list has built in transformers and they are not necessarily the data we actually need in most instances. So we are busy changing the ResourceList to FitleredLists when we need to customize things.

BTW, what's the benefit of using ResourceList alone over the FilteredList? From what I can tell the Resource list has built in transformers and they are not necessarily the data we actually need in most instances. So we are busy changing the ResourceList to FitleredLists when we need to customize things.

They are exactly the same component.
The only component is ResourceList that is responsible to list (with infinite scrolling) the specified resource with the specified query.
FilteredList needs to be used along with other filters component since it is already connected with the selected filters as specified here
If you do not have a search bar and the filters page (<SearchWithNav />), you don't need FilteredList.
To clarify
the standard usage of <ResourceList> is destructuring the component from its hook useResourceList and pass the filters you want as your normal filters query (same objected used by the sdk)
const { ResourceList } = useResourceList({
  type: 'orders',
  query: {
    fields: ['number', 'market'],
    filters: {
      status_eq: 'placed'
    },
    pageSize: 25,
    sort: [...],
    include: ['market']
  }
})
)

return (
  <ResourceList
       title='My orders list'
       ItemTemplate={(props) =>
order number {props.resource?.number}
 }
  />
)

But if you don't want to build the filters object yourself, you can use the our filters hook that returns also the components to build the filters form and a search bar, along with a ResourceList that automatically reacts when user interact with the search bar or with the filters form.
In fact the query prop on the FilteredList won't allow to set filters key, but you can only add fields, sort, pageSize and include keys.
Under the hood it uses ResourceList (view source) and automatically applies filters from URL query string (that are generated by FiltersForm component or SearchWithNav)

So finally, to answer the following:

what's the benefit of using ResourceList alone over the FilteredList?
There is not really a benefit, but ResourceList is the base component used to build FilteredList (from a component composition point of view).

Imagine you want to list the orders of a specific customer, for a specific market, with placed status (fixed list, not dinamically filtrable by the user). You can simply do:
const { ResourceList } = useResourceList({
  type: 'orders',
  query: {
    filters: {
      status_eq: 'placed',
      markets_id_in: ['xxxx'],
      customer_id_eq: 'zzzzz'
    },
    pageSize: 25
  }
})
)

return (
  <ResourceList
       title='My orders list'
       ItemTemplate={(props) =>
order number {props.resource?.number}
 }
  />
)

Right but when you use  the component has a built in transform and it only returns the data that is hard coded into the ResourceList component. Basically, it seems like a quick way to create a list from a resource. That's at least how we see the results. But you can't customize the display of the list at all, to include additional data etc. So when we want to customize the list, we have been using  Is that the idea?

For example, take a look at your code in the customers app. CustomerList component uses FilteredList to display the data, while CustomerOrders component uses ResourceList.

Right but when you use ResourceList the component has a built in transform and it only returns the data that is hard coded into the ResourceList component. Basically, it seems like a quick way to create a list from a resource. That's at least how we see the results. But you can't customize the display of the list at all, to include additional data etc. So when we want to customize the list, we have been using FilteredList. Is that the correct approach?

No, that's not correct. The transformation function is only used when metrics api is used (so when metricsQuery prop is defined).
The ItemTemplate prop is the function that will be used to render each single item of the list as retuned by the API request.
If you look at the example above, I am using ItemTemplate to fill the list with a custom div.
Let me re-writing it adding an include to show for each order the customer email and the payment method
const { ResourceList } = useResourceList({
  type: 'orders',
  query: {
    filters: {
      // optional filters
    },
   include: ['customer'],
    pageSize: 25
  }
})
)

return (
  <ResourceList
       title='My orders list'
       ItemTemplate={(props) =>
             // props.resource is now a single `order` because the `useResourceList` has been initialized with `type: orders`

order number {props.resource?.number}

placed at {props.resource?.placed_at}

from customer {props.resource?.customer?.email}

payed by {props.resource?. payment_method?.name}

 }
  />
)

You can do whatever you want with ItemTemplate for both ResourceList (from useResourceList) and FilteredList (from useResourceFilters)

metricsQuery: Oh ok, that's what confused us. Because we were on the orders app. now i understand.
But, based on what you wrote, why in the Customers App, do you use Filtered List in  CustomerList component instead of ResourceList?

because CustomerList has a filtrable list of customers (as any other*List page)
Applied filters will be added in query-string and list is automatically filtered every time the user interact with the other filters component

Ah ok. I think I am finally understanding this and when to use what. Thanks!

Ok, so I've been confusing things. Our issue is with the ResourceListItem component. This has a built in transformer, so if you pass data to it from ResourceList or FilterList, you can't get all the data you want and you need to create a separate component. This is a bit annoying, if I'm understanding this correctly. Why does ResourceListItem have built in transformers?

That's right. ResourceListItem is a component that we use to share the same UI (for a specific resource list) in all apps.
In this way we have the same item to preview an order or a customer everywhere.
But it's just a pre-made component, you can build your custom list item component to be used in ItemTemplate prop.
It will receive the resource fetched from the list with the query (filters and include) you have specified.


Simplify getting variable by name

Suppose we created a variable foo/v
with tf.variable_scope("foo"):
    v = tf.get_variable("v", [1])

To get this variable from its name one currently needs to write two lines:
with tf.variable_scope("foo", reuse=True):
    v1 = tf.get_variable("v")

Instead, it would be much more intuitive to just write:
v1 = tf.get_variable("foo/v", reuse=True)

You can do v = sess.graph.get_tensor_by_name("foo/v:0")

@Androbin : that's an interesting option I wasn't aware about! But it might still make sense to simplify the standard tf.get_variable call as suggested above.

It should be possible to split the name and then place the scope as a hack.
I'll try to submit a PR to do so.

Seems like tf.get_variable should already do that:
https://github.com/tensorflow/tensorflow/blob/master/tensorflow/python/ops/variable_scope.py#L1069

@wielandbrendel Can you confirm that tf.get_variable accepts this name layout?

@Androbin : Sorry, but could you explain in more detail?

The documentation suggests that at least one of these should work:
v = tf.get_variable("foo/v")
v = tf.get_variable("foo/v:0")

with tf.variable_scope("foo"):
    v = tf.get_variable("v", [1])

v1 = tf.get_variable("foo/v")

throws a ValueError
ValueError: Variable foo/v already exists, disallowed.
Did you mean to set reuse=True in VarScope?

@wielandbrendel get_variable doesn't return old variables unless reuse=True in order to prevent subtle bugs.  It seems like the behavior you want is already available either via reuse=True or sess.graph.get_tensor_by_name.

Get tensor by name gets a tensor, not a variable object.  It would be nice to add a reuse keyword to tf.get_variable so we could grab variables directly.


Integrate Vue

Adds Vue and configures it for use in a hybrid app:

Configure webpack to expose JS snippets in entry_points/ to the browser.
These can then be invoked in <script> elements, with params, from server rendered pages.
Entry point snippets will then import and instantiate individual Vue instances, passing along any props from the page.

Also disable turbolinks.

Looks good! I'll catch up with you this afternoon for a walkthrough on the integration.


Update libcontainer to 3d8a20bb772defc28c355534d83

Fixes #14203
This bump fixes the issue of having the container's pipes connection
reset by peer because of using the json.Encoder and having a \n added to
the output.
Signed-off-by: Michael Crosby<EMAIL_ADDRESS>

LGTM

LGTM

Thanks!

For people in the future, this vendors the single patch opencontainers/runc@ddcee3cc2a2ffb3ab8c630fd62689fd14ce82e07 from master (it's based on resource-hf).

Added impact/changelog because this is a notable bug fix


gprof_dot_reader: use pydot to fix python3 errors

I pushed some fixes to this PR here: https://github.com/slabasan/hatchet/tree/features/python3-fix

@slabasan: can you push the fixes here?  You should be able to push to the actual PR branch.

Oops yes didn't realize I had write access. Thanks!

Fixes #17


It shall not interprete the angle brackets inside coding block

The raw source:

The presentation on GitHub

The presentation interpretated by markdown-it.js

Can not reproduce. Please, show example in demo https://markdown-it.github.io/

Sorry it was my problem. If I remove highlight part from the configuration shown below it will be all good.

However I need it to hightlight the syntax. Still wondering where I am wrong ...

Okay I endup with replacing prism with hilight js and the issue is gone


increase size of page title to xxxl

What
Bumped the font size of the page title (h1) of the default template up to xxxl.
How to review
Before

After

Who can review
Anyone

Looks good to me, also seems concourse timed out whilst waiting for a worker to run the PR in CI. Will look into this.

Ah https://api.github.com/graphql TLS handshake timed out. So it could get the PR in the first place. Audit and Build have now been retriggered and are passing.


Only check ServerConfigDocument after server config has been copied

The ServerConfigDocument will only be created after config files and properties have been copied and resolved. This should work around the issue where an instance was cached without the correct property values causing app config to fail.
Fixes #969 and #718

As I was reviewing this code, I realized undeploy isn't working either.
Itook a quick look at where io.openliberty.tools.maven.server.PluginConfigSupport.getAppsDirectory() is called from.
Turns out it's also called from the undeploy mojo in addition to deploy, install-server, and create (which we already knew).
The undeploy mojo has a related problem... because we never call copyConfigFiles, we never merge the Maven properties before loading the DOM object.

One more comment:  I did test and it fixed all my problem cases

@scottkurz With your last comment, are you saying the fix in this PR fixed all your issues? If so, do we still need to alter this fix to cover some of the other points you made in previous comments?

@scottkurz With your last comment, are you saying the fix in this PR fixed all your issues? If so, do we still need to alter this fix to cover some of the other points you made in previous comments?

I still thought we should make the changes, esp. adding tests... just clarifying that this does work and solve the problem.

@mattbsox I definitely agree with the part on adding some tests.


Error when extending the default template

Morning, sorry for my bad English. When I use the:
@extends('adminlte::page')
I get this error:
ReflectionFunction::__construct() expects parameter 1 to be string, array given (View: /home/user/LABS/LARAVEL/project/resources/views/vendor/adminlte/page.blade.php) (View: /home/guysolamour/LABS/LARAVEL/project/resources/views/vendor/adminlte/page.blade.php).
What 's wrong ?

I have exactly the same issue.

are u using the exact requirements?? like your PHP Version , now only support for >= 7

I changed the requirements and added php 5.6.
It will be removed in the next versions.

We changed the requirements of PHP to >= 7.0.x and Laravel to >= 5.5.x.
The pre version of v1.27.0 is released.


Unable to access service via ip

I created an ubuntu in orbstack and a mysql service in ubuntu. I cannot access the mysql service using ubuntu's IP.
I don’t want to map Ubuntu services directly to the port of my machine. Is there a way to solve this?

Duplicate of #748. Please check my reply in that issue for ways to fix this.


ci: migrate-to-pnpm-v8

I noticed that with pnpm v8, we have some warnings now during installation:
 WARN  Local dependency not found at /home/runner/work/graphql-hive/graphql-hive/packages/libraries/client/dist
 WARN  Local dependency not found at /home/runner/work/graphql-hive/graphql-hive/packages/libraries/core/dist
 WARN  Local dependency not found at /home/runner/work/graphql-hive/graphql-hive/packages/libraries/core/dist
 WARN  Local dependency not found at /home/runner/work/graphql-hive/graphql-hive/packages/libraries/core/dist
 WARN  Local dependency not found at /home/runner/work/graphql-hive/graphql-hive/packages/libraries/core/dist
 WARN  Local dependency not found at /home/runner/work/graphql-hive/graphql-hive/packages/libraries/external-composition/dist
 WARN  Local dependency not found at /home/runner/work/graphql-hive/graphql-hive/packages/libraries/external-composition/dist
 WARN  Local dependency not found at /home/runner/work/graphql-hive/graphql-hive/packages/libraries/client/dist
 WARN  Local dependency not found at /home/runner/work/graphql-hive/graphql-hive/packages/libraries/core/dist

Also, please note that in some workflows we are not using the shared-pipelines (but a similar one, that lives in this repo). So it needs to adjustments as well.

I noticed that with pnpm v8, we have some warnings now during installation:
 WARN  Local dependency not found at /home/runner/work/graphql-hive/graphql-hive/packages/libraries/client/dist

@dotansimha hmm, but that looks ok, the local dependency's files were not found as those packages are specifying their main entry to be dist/index.js and dist doesn't exist unless after doing a successful build.
I have noticed that in the root tsconfig.json, there is a configured paths like this "@graphql-hive/client": ["./packages/libraries/client/src/index.ts"], which means that in development we reference the local dependencies as TS files to avoid having to re-build multiple projects continuously, so I think this warning doesn't have a lot of meaning in development, but just a warning that if we didn't have that tsconfig paths that we would have trouble using the local packages without them being built.

Our pnpm setup here also have some configuration overrides (see .npmrc) - so we need to make sure pnpm v8 does not change any defaults that might effect this.

I have verified that both .npmrc configs work locally and are still supported in pnpm@v8 from the release notes, nothing is listed regarding deprecating any of the listed below:
enable-pre-post-scripts=true
shamefully-hoist=true


⚠ Minecraft has degraded performance

In d8b2b30, Minecraft (https://www.minecraft.net) experienced degraded performance:

HTTP code: 200
Response time: 1186 ms

Resolved: Minecraft performance has improved in 9d7ef84.


Investigate speed of NULLIFIEREXISTS operation

Investigated this. It was a red herring based on other actions performed at a similar time found to be slow.


Integration stopped working

The Integration is no longer showing entities.
There are no errors in the Log but it seems to no longer work

Still working correctly on my system - unfortunately you have provided no other details so we cannot help until we have anything more - narrow it down to what you did just before it stopped working?

Well thats the thing. I did nothing. It worked a week ago and now every Entity is no longer available
I can share my config:
sensor:

platform: mobile_alerts
phone_id:<PHONE_NUMBER>12
devices:

device_id: 0B6B1288E823
name: Wind Speed
type: ws
device_id: 0B6B1288E823
name: Wind direction raw
type: wd
device_id: 03054542A811
name: Outside Humidity
type: h
device_id: 03054542A811
name: Humidity 3H
type: h3havg
device_id: 03054542A811
name: Humidity 24H
type: h24havg
device_id: 03054542A811
name: Outside Temperature
type: t1
device_id: 080A7EA0E0A2
name: Rain
type: r

template:

sensor:
- name: Wind Direction
state: >
{%- set wd = {
'0': 'N',
'1': 'NNE',
'2': 'NE',
'3': 'ENE',
'4': 'E',
'5': 'ESE',
'6': 'SE',
'7': 'SSE',
'8': 'S',
'9': 'SSW',
'10': 'SW',
'11': 'WSW',
'12': 'W',
'13': 'WNW',
'14': 'NW',
'15': 'NNW'} -%}
{%- set state = states('sensor.wind_direction') -%}
{{ wd[state] if state in wd else state }}

I have added the first 2 entities on my system:
the start of my weather.yaml reads:
  - platform: mobile_alerts
    devices:
      - device_id: 0B6B1288E823
        name: N3 Wind Speed
        type: ws
      - device_id: 0B6B1288E823
        name: N3 Wind direction raw
        type: wd

they show up correctly and are showing values of 0.9 and 11
So I assume that it is something else in your configuration...
(the phone_id is optional - if you set up rules it can return the data but we don't do anything with this)

I deleted it from my config, restarted, added it again and restarted again. Now everything is working again.
must have been a formating error somewhere

Closed - user error
(and not a please or thank you in sight - so glad to have helped)


Create environment request form

The user must be able to request an environment to the podcast API.

Closed by #6


invalid cross-device link

Hi,
We have oklog v0.3.0 running in docker. I'm mounting external disk on /data. After while I get below error:
ts=2018-03-22T11:27:58.697719584Z level=info ingest_path=data/ingest
during recovery: rename data/store/0093a279-2977-42ec-b9d3-7771d4551950.active 01C96FFQG2W35WWA9VMPKCGCG1-01C96FFTAXR3F5QW47JTJGRQPS.flushed: invalid cross-device link

I know this is because it tries to use os.Rename cross disks, however I'm not fully understanding why oklog want to move file outside data folder (which is disk on it's own). I could replace Rename method to handle it with io.Copy instead, but best solution would be to avoid moving files outside data folder in first place.

This issue is fixed on master:
https://github.com/oklog/oklog/blob/master/pkg/store/file_log.go#L414
v0.3.0 is broken.

Thanks, I'll make a new release now.


Joining a room races with room subscriptions

If you issue a /join for a room and then immediately make a room subscription for that room, there is no cached data for that room so the room subscription returns nothing. When the /join is processed, the room subscription is not then fed to the client, even though global caches are updated.

https://github.com/matrix-org/sliding-sync/commit/7dded699a95111510e8b137c6570d835398f7188


maxLength counter misaligned on Safari

-Fixes #1440
-Added a force repaint of the counter when an error is passed after the initial rendering
-Added test case in spec

@javivelasco

I think this is too much code for that kind of problem, I've been having a look at it and seems that applying some css to the counter fixes it.
position: absolute;
bottom: 2rem;

I just tried with your issues example, so it would be nice if you could give it a try in your project and see if that fixes it.
Thank you for the PR!


Emmet extensions_path option

VSCode Version: 1.4.0 (2016-08-04T16:39:36.387Z)
OS Version: OS X El Capitan 10.11.3

There's an extensions_path option for Emmet in Sublime and Atom, which allows you to have an external source for preferences.json and snippets.json.

You can easily extend Emmet with new actions and filters or customize existing ones. In Preferences > Emmet, set Extensions path to folder with Emmet extensions. By default, it’s ~/emmet, e.g. emmet folder in your system HOME folder.

https://github.com/emmetio/emmet-atom#extensions-support
It's not available in the latest version of editor.
Can this option be ported into Visual Studio Code?

Any progress on this issue? I've a long list of the snippets to use for Emmet (both CSS and HTML), if I add them to my settings.json, it will become messy, that's why an extended file is appreciated.

@fronteed This is now implemented and should be in tomorrow's insiders build. Can you give it a try and provide feedback?

The setting to use is called emmet.extensionsPath
You need to provide absolute path at the moment.
The files snippets.json, syntaxProfiles.json and preferences.json will be read from this directory.
emmet.preferences and emmet.syntaxProfiles settings will take precedence over the contents of the above file
The files are read once and cached. Will be re-read on VS Code reload or whenever there is a change to emmet.extensionsPath

More on emmet customization: http://docs.emmet.io/customization/


add result integer to transaction result codes

High Level Overview of Change
Added the result code integer to the transaction results.

Context of Change
This will help sidechains sync with the registry. Currently if a sidechain wanted to add their own amendment, they would need to bring in every tel code as a placeholder. This allows them to specify a specific result code while skipping other amendment result codes.

Type of Change

[x] Refactor (non-breaking change that only restructures code)

This would break everyone working on an amendment. You would get a clash but hopefully you can use the registry to resolve and reserve your fields.
Its just a suggestion. No pressure.

I don’t have context to understand how this might affect existing or users.
Does this mean you’re expecting consumers to be able to do a greater than / less than compare?

I don’t have context to understand how this might affect existing or users.
Does this mean you’re expecting consumers to be able to do a greater than / less than compare?

See here. See how on Xchain they needed to add the AMM error codes? This is because when generated without the absolute #, the error codes are generated in order. So for Xchain, they needed to add the AMM error codes in order to add their own error codes after. Or else there would have been a difference in error codes between the 2 builds. AMM error would have been 261 and the first Xchain error would have been 261 as well.
I just thought it would be helpful if they were numbered.

I'm going to move this draft and possibly close. After more thought, I don't know if it adds that much value. If you are writing an amendment or a sidechain then you need to be aware of the error codes anyways. Technically they are added when the amendment is merged so you have to keep up anyways.
My bad lol

I'm going to move this draft and possibly close. After more thought, I don't know if it adds that much value. If you are writing an amendment or a sidechain then you need to be aware of the error codes anyways. Technically they are added when the amendment is merged so you have to keep up anyways.
My bad lol

Heh wouldn’t say “your bad” but whatever you think is best! Thanks for helping my understand. 🙏🏻

Yeah, @dangell7, as you noted I don't know that this change helps the situation very much.
The two kinds of codes that need to be stable, tes and tec, already have explicit values.  It's important that they be stable because those values are stored in ledger history.  And, yeah, those need to be carefully managed as the code base changes.
For the other kinds of codes, tel, tem and the like, it is less critical that they stay stable.  I think it's okay for those values to accrete, as they have been, when code is merged to develop.


Fix 32-bit arm build of antctl

One of the architectures we build antctl for at release time is armv7,
which is a 32-bit architecture. Some recent changes broke that build
(invalid uint32 - int conversions) and this commit fixes it.

Out of curiosity, does building antctl compiling pkg/agent/openflow?

Apparently it does now (https://github.com/vmware-tanzu/antrea/blob/master/pkg/antctl/antctl.go#L333). Fortunately, it seems that this package doesn't have any OS-specific dependencies, which means we can still build antctl for Windows & macOS. Any thoughts? Do you think we should avoid this dependency?

/test-all

/test-all

@tnqn I'm going to merge this now so the release can go through. Feel free to look into removing that dependency from antctl. It seems that the binaries became a bit large because of that (although there may be some other new dependencies explaining this...).


Private Tangle: Spammer fails

Describe the bug
When starting the private tangle the Spammer goes into a crash loop, reproduceable locally and in CI.
Anecdotally beta.9 shows the same behavior locally, where beta.8 works. But in beta.8 the Faucet does not come up initially , although it works after restarting the container.
To Reproduce
Steps to reproduce the behavior:

Pull latest private_tangle from GitHub releases or use latest dev branch
Start private tangle
See error

inx-spammer          | 2022-09-26T10:27:24Z	INFO	INX	Connecting to node and reading node configuration ...
inx-spammer          | 2022-09-26T10:27:24Z	INFO	INX	Reading node status ...
inx-spammer          | 2022-09-26T10:27:24Z	INFO	Spammer	Setting up spammer ...
inx-spammer          | 2022-09-26T10:27:24Z	INFO	Spammer	Address for Sender: tst1qqweu75ldpyann5jsthqsa6m0thx4tmqxncj6uqxf5q974pmqx30y5mcdp2
inx-spammer          | 2022-09-26T10:27:24Z	INFO	Spammer	Address for Receiver: tst1qqkzz4kd0e5gz5dwequ8mwvjljd78gzh4hv677djcqe3cj28je7u5c6n09a
inx-spammer          | 2022-09-26T10:27:24Z	INFO	App	Loading core components ...
inx-spammer          | 2022-09-26T10:27:24Z	INFO	App	Loading core components: INX ... done
inx-spammer          | 2022-09-26T10:27:24Z	INFO	App	Loading core components: Spammer ... done
inx-spammer          | 2022-09-26T10:27:24Z	INFO	App	Loading core components: Shutdown ... done
inx-spammer          | 2022-09-26T10:27:24Z	INFO	App	Loading plugins ...
inx-spammer          | 2022-09-26T10:27:24Z	INFO	App	Loading plugin: Profiling ... done
inx-spammer          | 2022-09-26T10:27:24Z	INFO	App	Loading plugin: Prometheus ... done
inx-spammer          | 2022-09-26T10:27:24Z	INFO	App	Executing core components ...
inx-spammer          | 2022-09-26T10:27:24Z	INFO	App	Starting core component: INX ... done
inx-spammer          | 2022-09-26T10:27:24Z	INFO	App	Starting core component: Spammer ... done
inx-spammer          | 2022-09-26T10:27:24Z	INFO	App	Starting core component: Shutdown ... done
inx-spammer          | 2022-09-26T10:27:24Z	INFO	App	Executing plugins ...
inx-spammer          | 2022-09-26T10:27:24Z	INFO	App	Starting plugin: Profiling ... done
inx-spammer          | 2022-09-26T10:27:24Z	INFO	App	Starting plugin: Prometheus ... done
inx-spammer          | 2022-09-26T10:27:24Z	INFO	App	Starting background workers ...
inx-spammer          | 2022-09-26T10:27:24Z	INFO	Prometheus	Starting Prometheus exporter ... done
inx-spammer          | 2022-09-26T10:27:24Z	INFO	Prometheus	You can now access the Prometheus exporter using: http://<IP_ADDRESS>:9311/metrics
inx-spammer          | 2022-09-26T10:27:24Z	INFO	Profiling	You can now access the profiling server using: http://<IP_ADDRESS>:6060/debug/pprof/
inx-spammer          | 2022-09-26T10:27:24Z	INFO	Spammer	Starting Spammer 1 ... done
inx-spammer          | 2022-09-26T10:27:24Z	INFO	INX	Starting NodeBridge ...
inx-spammer          | ⇨ http server started on <IP_ADDRESS>:9311
inx-spammer          | 2022-09-26T10:27:24Z	INFO	Spammer	Starting API ... done
inx-spammer          | 2022-09-26T10:27:24Z	INFO	Spammer	Starting API server ...
inx-spammer          | 2022-09-26T10:27:24Z	INFO	Spammer	You can now access the API using: http://<IP_ADDRESS>:9092/
inx-spammer          | ⇨ http server started on <IP_ADDRESS>:9092
inx-spammer          | 2022-09-26T10:27:24Z	INFO	Spammer	Starting API server ... done
inx-spammer          | 2022-09-26T10:27:43Z	WARN	Shutdown	Critical App self-shutdown: Spammer plugin hit a critical error while applying new ledger update: context deadline exceeded; waiting (max 300 seconds) to finish processing ...
inx-spammer          | 2022-09-26T10:27:43Z	INFO	Prometheus	Stopping Prometheus exporter ...
inx-spammer          | 2022-09-26T10:27:43Z	INFO	Prometheus	Stopping Prometheus exporter ... done
inx-spammer          | 2022-09-26T10:27:43Z	INFO	Spammer	Stopping API ...
inx-spammer          | 2022-09-26T10:27:43Z	INFO	Spammer	Stopping API ... done
inx-spammer          | 2022-09-26T10:27:43Z	INFO	Spammer	Stopping Spammer 1 ...
inx-spammer          | 2022-09-26T10:27:43Z	INFO	Spammer	Stopping Spammer 1 ... done
inx-spammer          | 2022-09-26T10:27:43Z	INFO	INX	Stopped NodeBridge
inx-spammer          | 2022-09-26T10:27:43Z	INFO	App	Shutdown complete!

Expected behavior
Spammer should start and stay up.
Environment information:

OS: GitHub runner ubuntu-latest and locally Ubuntu 22.04
Hornet Version: beta.10

Thanks for the bug-report. I could reproduce it and a fix for the inx-indexer is incoming. This should fix the spammer issue.
I'll close this ticket as soon as the fix is released.

Ok, should work now. Please run ./bootstrap.sh build or do a docker compose pull inx-indexer

Can confirm it works on latest dev. Thank you for the swift resolution!


Embedding docs pages in website

Is there any way to embed these docs pages in external website? It gives "Refused to connect" because of CORS.
Thanks in advance.

I haven't seen it done before, so I'm thinking it's not permitted.


Fix crash on recovered orphaned nodes.

There are a lot of issues in regards to how Godot recovers nodes from situations where an instanced or inherited node has its overall composition changed, resulting in nodes which might no longer reference a valid parent. However, the most notable issue right now is that if this happens, the scene will become corrupted to the point that it will crash if you attempt to close any scene containining one or more of these orphaned nodes. This is due to the default recover mechanism first extracting the nodes's path, then prepending it to the nodes name between an @ symbol. However, @ is a reserved character, so it sets it with the nocheck name, which subsequently updates the name, but does NOT update its parent's cache, resulting in failure if the node is referenced by path, and subsequently leads to crashes. The scene is essentially corrupted now beyond repair without manual text editing.
While there's a lot more that can be done in regards to recovering scenes with orphaned nodes (I recommend the next step should be constructing dummy nodes to recreate the original path composition as close as possible rather than shoving them in the root), I've changed from the reserved @ symbol to the ~ symbol and used the set_name command which does checks. This should at least now give users an oppertunity to manually repair their scene if nodes become orphaned, but may also be considering an editor-only UID system for scenes, which should more or less completely eliminate scene breakage like this.
Closes https://github.com/godotengine/godot/issues/83595

Using ~ instead of @ makes it less obvious that the path was modified, at a glance (especially when underscores are used). Maybe # would be better?

vs

Yeah, I agree, # is probably a better symbol. I'll change it.

Thanks!


feat(Tabs): add subtitle props

Summary
Type

Enhancement

Summarise concisely:
📄 Specification
Max width: TBD and it seems we need truncation script on the description when its long (it should be limited to 1 line)
Alignment : left-align
Text color : neutral weak when not selected
Text color : primary when tab is active
Typography: bodySmall
FRONT SPECIFICATIONS
We need to add a prop subtitle into Tabs.Tab component that will be shown according to the figma proto.
We need to align all Tabs.Tab on top
We don't need to add the description in the Tab Menu.
What is expected?
Add a Subtitle to the Tab only on the Nav component ( not Menu )
Relevant logs and/or screenshots

Page
Before
After

url

url

Note:
Migrate Menu to MenuV2 is more complex and required a focus on that @matthprost

Spacing between title and subtitle should be 4px

Text color on subtitle should be neutralWeak

There is a missalignment on the badge

This case will never occur so it might be better not to show it. When subtitle will be enabled it will be for all tabs

@PetmePant  Everything should be corrected


Missing propguard-rule for Android -> obfuscated keys in FlutterCallkitIncoming.activeCalls()

The following rule needs to be added in the proguard-rules.pro to avoid obfuscated keys.
Please add that to the README:
-keep class com.hiennv.flutter_callkit_incoming.** { *; }

@hiennguyen92  Are you even care about the issues?

Ok. I will add it to Readme. Thanks

There are several more issues, open prs and so on. Do you need help with the contribution?

I added it in the README.md


Version bump requested.

Seems the project built, but the test failed. If it's still good, I'd like to include the official library in my project but a version bump will be needed for a new release.
I don't know why the test failed for Firefox, but I suspect this was a fluke.
Regarding my previous PR discussed here: https://github.com/umaranis/svelte-lexical/issues/53

new version 0.3.4 is published @maietta

Thank you so much!


[BULK] - DocuTune remediation - Sensitive terms with GUIDs (part 8)

Applying sensitive terms with GUID changes as part of Content SFI and outlined in Overview - Writing content securely - Platform Manual. Changes are part of the Microsoft-wide SFI effort. Point of contact: @CelesteDG
DocuTune v<IP_ADDRESS>
CorrelationId: ac15aa43-4e2b-437f-ab1c-fdd7e79cd4db
#docutune

#docutune-review

Trigger rebuild.


Can it be used with middle-button autoscroll like jquery.scrollbar?

jquery.scrollbar example

+1 this -- it was one of the first things i tried and it simply makes the main page scroll

@bugfreetech, i think they don't approve patch for this, because it can be made only with hacks, wich not works in some browsers. I probably will make purejs port of jquery-scrollbar.

@bugfreetech, there is cool gemini-scrollbars.

@imShara thanks, looks very nice

Merged into #412. Thanks for the interest, guys!


Calling hass.http.register_static_path is deprecated

FRom Home Assistant Core log:
Detected that custom integration 'webrtc' calls hass.http.register_static_path which is deprecated because it does blocking I/O in the event loop, instead call await hass.http.async_register_static_paths([StaticPathConfig("/webrtc/embed", "/config/custom_components/webrtc/www/embed.html", True)]); This function will be removed in 2025.7 at custom_components/webrtc/init.py, line 74: hass.http.register_static_path("/webrtc/embed", str(path / "embed.html")), please create a bug report at https://github.com/AlexxIT/WebRTC/issues

same here :
Detected that custom integration 'webrtc' calls hass.http.register_static_path which is deprecated because it does blocking I/O in the event loop, instead call await hass.http.async_register_static_paths([StaticPathConfig("/webrtc/video-rtc.js", "/config/custom_components/webrtc/www/video-rtc.js", True)]); This function will be removed in 2025.7 at custom_components/webrtc/init.py, line 67: hass.http.register_static_path("/webrtc/" + name, str(path / name)), please create a bug report at https://github.com/AlexxIT/WebRTC/issues
Detected that custom integration 'webrtc' calls hass.http.register_static_path which is deprecated because it does blocking I/O in the event loop, instead call await hass.http.async_register_static_paths([StaticPathConfig("/webrtc/embed", "/config/custom_components/webrtc/www/embed.html", True)]); This function will be removed in 2025.7 at custom_components/webrtc/init.py, line 74: hass.http.register_static_path("/webrtc/embed", str(path / "embed.html")), please create a bug report at https://github.com/AlexxIT/WebRTC/issues
And for 2025.05
HomeAssistantType was used from webrtc, this is a deprecated alias which will be removed in HA Core 2025.5. Use homeassistant.core.HomeAssistant instead, please report it to the author of the 'webrtc' custom integration
ServiceCallType was used from webrtc, this is a deprecated alias which will be removed in HA Core 2025.5. Use homeassistant.core.ServiceCall instead, please report it to the author of the 'webrtc' custom integration


Audio Meter: Show Media & controls dynamically

Feature request to show Media & controls only when music is playing

I never thought about doing this... and it's not even going to be that difficult! It'll be in for the next beta. :)

just make sure that the panel is extending to the top instead down :D

You mean move the top of the gadget up, rather than moving the bottom down?
This is actually very (VERY) difficult, as Rainmeter defines skin positions from the top-left of a skin. So for me to make the top go up, I would have to finagle with the skin's actual position. Sorry, but it'll move the visualizer down when it appears. :(

It doesn't hurt to ask  :innocent:

This is now implemented in v1.5.0-beta.10, which will be releasing in a few hours.

v1.5.0-beta.10 is released!


Cannot stringify Ember.Object with ownerInjection()

Environment

Ember Version: 2.11.3
Ember CLI Version: 2.11.1
Ember CP Validations Version: 3.3.2

Hi!  Thanks for the awesome library!
Steps to Reproduce
I have followed steps found in the docs and in other issues on how to validate Ember.Objects using the getOwner API.  Validations are found and work really well.  The problem arises when trying to JSON.stringify(...) the validated Ember.Object instance.
I doubt this is an issue with ember-cp-validations but was hoping you might have some insight into how to deal with this issue.
To reproduce:
const FooValidations = buildValidations({ name: validator('presence', true) });
const Foo = Ember.Object.extend(FooValidations);

let bar = Foo.create(Ember.getOwner(this).ownerInjection(), { name: 'baz' });
JSON.stringify(bar);

This results in the following:
TypeError: Converting circular structure to JSON
    at JSON.stringify (<anonymous>)
    at Class.save (index.js:7)
    at Backburner.join (ember.debug.js:771)
    at Function.run.join (ember.debug.js:22291)
    at ember.debug.js:9935
    at Object.flaggedInstrument (ember.debug.js:18477)
    at Class.<anonymous> (ember.debug.js:9934)
    at ember.debug.js:11629
    at Object.flaggedInstrument (ember.debug.js:18477)
    at ember.debug.js:11628

Ember Data Models do not exhibit this behavior (guessing due to serializers stripping out the internals).  Unfortunately for this case I am unable to use an Ember Data Model.
Any insight, workarounds, etc. you may have would be greatly appreciated.
Thanks!

I've worked around the issue by overriding RESTAdapter.ajaxOptions to ignore the injected owner:
  ajaxOptions(url, type, options) {
  let hash = options || {};
  hash.url = url;
  hash.type = type;
  hash.dataType = 'json';
  hash.context = this;

  if (hash.data && type !== 'GET') {
    hash.contentType = 'application/json; charset=utf-8';
    hash.data = JSON.stringify(hash.data, this._stringify_replacer);
  }

  let headers = get(this, 'headers');
  if (headers !== undefined) {
    hash.beforeSend = function (xhr) {
      Object.keys(headers).forEach((key) =>  xhr.setRequestHeader(key, headers[key]));
    };
  }

  return hash;
},

_stringify_replacer(key, value) {
  if (key.startsWith('__OWNER__')) {
    return undefined;
  }
  return value;
}

While this gets me around the issue, I wonder if there is something that could be done to allow validated Ember Objects requiring an owner injection to work more seamlessly with the default ajaxOptions function that calls JSON.stringify on the validated instance?

@rynam0 this seems to be an Ember core issue and should be posted on the ember.js repo since this only has to do with ownerInjection. Hopefully they can be of some more help there.

Ok, that's what I was thinking but wanted to see if you had run into this before.
I'll create an issue in the appropriate repo.
Thanks!

@rynam0 I havent ran into that issue before but I suggest trying it out in an ember-twiddle as well without ember-cp-validations so you can provide reproductions.

Sounds, good.  Thanks again :)


Forwarded Headers are being overwritten

In what area(s)?

/area runtime

/area operator
/area placement
/area docs
/area test-and-release

What version of Dapr?
1.0.0
Expected Behavior
Sending a service invocation request with X-Forwarded headers should maintain their values.
This is useful when their are multiple proxies involved and the dapr runtime incorrectly calculates the host details.
Actual Behavior
These headers are being overwritten with the details of the dapr proxy
Steps to Reproduce the Problem

Nb. This didn't work locally, only when I was running in kubernetes, presumably something to do with host detection.

Run a daperized app that logs all headers (app-id: test)
curl http://<IP_ADDRESS>:3500/v1.0/invoke/test/method/ -H "X-Forwarded-Host: override.example.com"

See logged output similar to:
"X-Forwarded-Host: ingress-nginx-controller-6b6b4d847b-b4zzf"

Potential fix
Update https://github.com/dapr/dapr/blob/8f9cba4931bd184acac70bf7aedcba283ccfcb35/pkg/messaging/direct_messaging.go#L180 To only set headers that aren't already set
or based on https://kubernetes.github.io/ingress-nginx/user-guide/nginx-configuration/configmap/#use-forwarded-headers have an option to do nothing when there is an upstream proxy
Release Note

RELEASE NOTE: Fix Runtime will no longer override X-Forwarded Headers if they already exist

That makes sense. Would you be interested in submitting a PR for this?

I'd be happy to submit a PR


loading bytes object failed.

Hi, I used the command used in Memory file -> numpy -> memory file #156,
input_data = client.get()  # bytes object
decode = (
                ffmpeg
                .input('pipe:')
                .output('pipe:')
                .get_args()
            )
output_data = p.communicate(input=input_data)[0]

However, I get some errors.
1. Could not find codec parameters for stream 0 (Video: mpeg4 (mp4v / 0x7634706D), none, 210 kb/s): unspecified size
Consider increasing the value for the 'analyzeduration' and 'probesize' options

2. [mov,mp4,m4a,3gp,3g2,mj2 @ 0x55ee01839e80] stream 0, offset 0x1bc655: partial file
pipe:: Invalid data found when processing input
Cannot determine format of input stream 0:0 after EOF
Error marking filters as finished
Conversion failed!

How to solve these problems?

Hello, have you been able to solve this issue?


"Uncaught TypeError: Cannot read property 'selectGrammar' of undefined" occurs when beautifying from files list.

Uncaught TypeError: Cannot read property 'selectGrammar' of undefined

/home/my-user-name/.atom/packages/atom-beautify/lib/beautify.coffee:169

What version of Atom are you on? I am on v0.165.0 which has the atom.grammars API (see https://atom.io/docs/api/v0.165.0/Atom#instance-grammars ). If you update this should work.


[BUG] Longhorn does not use values provided during Helm chart installation

Describe the bug
For the installation we provide custom values for longhorn to use, like default data locality, or number of replicas, etc.
These are reflected in configMap but in UI these are not visible.
To Reproduce
Steps to reproduce the behavior:

Define configMap values
Install helm chart
UI shows defaults instead custom values.

Expected behavior
I do want to see custom values beeing used for installation.
Log
If applicable, add the Longhorn managers' log when the issue happens.
You can also attach a Support Bundle here. You can generate a Support Bundle using the link at the footer of the Longhorn UI.
Environment:

Longhorn version: 1.1.1
Installation method (Helm):
Kubernetes distro (e.g. RKE//EKS) and version:

Number of management node in the cluster: 3
Number of worker node in the cluster: 3

I think it's duplicate to #2570

Hmm, weird. @wojtasool could you provide more info on how have you defined the configMap? Is it by the helm command for example, helm install longhorn --namespace longhorn-system --set defaultSettings.defaultReplicaCount="5" .  ?
Is it happening on a  fresh install or upgrade?

To install we use terraform helm provider.
There is configMap named  default-setting.yaml with content:
default-replica-count: 2
backup-target:
backup-target-credential-secret:
allow-recurring-job-while-volume-detached:
create-default-disk-labeled-nodes:
replica-soft-anti-affinity:
storage-over-provisioning-percentage:
storage-minimal-available-percentage:
upgrade-checker:
default-data-locality: best-effort
guaranteed-engine-cpu: 5
default-longhorn-static-storage-class:
backupstore-poll-interval:
taint-toleration:
system-managed-components-node-selector:
priority-class:
auto-salvage: true
auto-delete-pod-when-volume-detached-unexpectedly: true
disable-scheduling-on-cordoned-node:
replica-zone-soft-anti-affinity:
volume-attachment-recovery-policy:
node-down-pod-deletion-policy:
allow-node-drain-with-last-healthy-replica:
mkfs-ext4-parameters:
disable-replica-rebuild:
replica-replenishment-wait-interval:
disable-revision-counter:
system-managed-pods-image-pull-policy:
allow-volume-creation-with-degraded-availability:
auto-cleanup-system-generated-snapshot:
concurrent-automatic-engine-upgrade-per-node-limit:
backing-image-cleanup-wait-interval:
guaranteed-engine-manager-cpu: 5
guaranteed-replica-manager-cpu: 5

I can see in container it is mounted under /var/lib/longhorn-setting/default-setting.yaml and I can see those values I specified. But in UI I can still see that for example default data path is /var/lib/longhorn/

This is fresh install

We recommend to use the defaultSettings in the chart/values.yaml. Does this not work for you?

This is how it is set.

Got it, do you know if the setting CR already exists before terraform provider runs helm installation? Are you able to try again by clean up the resources and re-install manually with helm install longhorn/longhorn --name longhorn --namespace longhorn-system --values values.yaml to see if the result is the same?

You mean CRD already exist?

Referring to the CR if it pre-exists before the helm install then the configmap will not get respected.
https://github.com/longhorn/longhorn-manager/blob/v1.1.1/datastore/longhorn.go#L40-L65 This behavior is explained in https://github.com/longhorn/longhorn/issues/2570.

Worked on manual installation. But I don't get it why?
Whats the difference?
In both installations any resource didn't existed.

I've verified this is happening with terraform-provider-helm. And issue was also raised in https://github.com/longhorn/longhorn/issues/2562#issuecomment-842228752.
@wojtasool , the only reason I could think of is the helm provider created the CR then later made an update with the custom values. With this case, we are tracking the fix in https://github.com/longhorn/longhorn/issues/2570.
The current workaround is to use the helm command instead.

default-replica-count: 2 is whats actually in default-setting.yaml file after templating. This is how it is defined in helm chart repository.
apiVersion: v1
kind: ConfigMap
metadata:
  name: longhorn-default-setting
  namespace: {{ include "release_namespace" . }}
  labels: {{- include "longhorn.labels" . | nindent 4 }}
data:
  default-setting.yaml: |-
    default-data-path: {{ .Values.defaultSettings.defaultDataPath }}
    default-replica-count: {{ .Values.defaultSettings.defaultReplicaCount }}
    backup-target: {{ .Values.defaultSettings.backupTarget }}
    backup-target-credential-secret: {{ .Values.defaultSettings.backupTargetCredentialSecret }}
    allow-recurring-job-while-volume-detached: {{ .Values.defaultSettings.allowRecurringJobWhileVolumeDetached }}
    create-default-disk-labeled-nodes: {{ .Values.defaultSettings.createDefaultDiskLabeledNodes }}
    replica-soft-anti-affinity: {{ .Values.defaultSettings.replicaSoftAntiAffinity }}
    storage-over-provisioning-percentage: {{ .Values.defaultSettings.storageOverProvisioningPercentage }}
    storage-minimal-available-percentage: {{ .Values.defaultSettings.storageMinimalAvailablePercentage }}
    upgrade-checker: {{ .Values.defaultSettings.upgradeChecker }}
    default-data-locality: {{ .Values.defaultSettings.defaultDataLocality }}
    guaranteed-engine-cpu: {{ .Values.defaultSettings.guaranteedEngineCPU }}
    default-longhorn-static-storage-class: {{ .Values.defaultSettings.defaultLonghornStaticStorageClass }}
    backupstore-poll-interval: {{ .Values.defaultSettings.backupstorePollInterval }}
    taint-toleration: {{ .Values.defaultSettings.taintToleration }}
    system-managed-components-node-selector: {{ .Values.defaultSettings.systemManagedComponentsNodeSelector }}
    priority-class: {{ .Values.defaultSettings.priorityClass }}
    auto-salvage: {{ .Values.defaultSettings.autoSalvage }}

And values.yaml file contains this:
defaultSettings:
  backupTarget: ~
  backupTargetCredentialSecret: ~
  allowRecurringJobWhileVolumeDetached: ~
  createDefaultDiskLabeledNodes: ~
  defaultDataPath: /mnt/data
  defaultDataLocality: best-effort
  replicaSoftAntiAffinity: ~
  storageOverProvisioningPercentage: ~
  storageMinimalAvailablePercentage: ~
  upgradeChecker: ~
  defaultReplicaCount: 2
  guaranteedEngineCPU: 5
  defaultLonghornStaticStorageClass: ~
  backupstorePollInterval: ~
  taintToleration: ~
  systemManagedComponentsNodeSelector: ~
  priorityClass: ~
  autoSalvage: true

Observed that when install with 1 custom setting updated, the change applies.
But when install with multiple custom settings updated, the default applies.

I've worked it arounding to what you said about changing all values altogether in defaultSettings field.
This is what worked for me:
resource "helm_release" "longhorn" {
  depends_on          = [var.depends_on_kubeconfig_cluster]
  count               = var.enable-longhorn ? 1 : 0
  name                = "longhorn"
  chart               = local.longhorn_chart_name
  repository          = var.url
  repository_username = *********
  repository_password = *********
  version             = var.longhorn-version
  namespace           = "longhorn-system"
  create_namespace    = true
  atomic              = "true"
  timeout             = 600
  wait                = "true"

  values = [
    templatefile("${path.module}/longhorn-values.yaml", local.file-templating),
    fileexists("${path.module}/longhorn-values.yaml") ? templatefile("${path.module}/longhorn-values.yaml", local.file-templating) : "",
    var.longhorn-values-file != "" ? fileexists(var.longhorn-values-file) ? templatefile(var.longhorn-values-file, local.file-templating) : "" : ""
  ]
  set {
    name  = "defaultSettings.defaultDataPath"
    value = format("%s", "/mnt/data")
  }
  set {
    name  = "defaultSettings.defaultDataLocality"
    value = format("%s", "best-effort")
  }
  set {
    name  = "defaultSettings.defaultReplicaCount"
    value = format("%s", var.REPLICA_COUNT)
  }
  set {
    name  = "defaultSettings.autoDeletePodWhenVolumeDetachedUnexpectedly"
    value = format("%s", "true")
  }

}

@wojtasool the issue seems to be coming from the guaranteedEngineCPU: 5 in the value.yaml. This setting had been deprecated in v1.1.1 and replaced with   guaranteedEngineManagerCPU and guaranteedReplicaManagerCPU. There should be an error in longhorn-manager after deployment.,
time="2021-06-29T14:30:11Z" level=error msg="Customized settings are invalid, will give up using them: the value of customized setting guaranteed-engine-cpu is invalid: value 5 of settings guaranteed-engine-cpu is invalid: cannot set a value 5 for the deprecated setting guaranteed-engine-cpu"

It seems to be resolved, close it.
Feel free to reopen it if there is any further question.
Thank you all.


Add null check for timer and assign to variable so it is shutdown..

Fixes https://github.com/redisson/redisson/issues/671.

Thank you!

@mrniko thanks!


Fix pages access

Make:

Leader board public
Team Leader board public

The tag-report page needs to be inaccessible unless logged in. If a user attempts to tag someone and is not logged in it will:

Not work
Reveal a bunch of runtime errors


New UI design part 2: Project List

Description
The new Project List view.
Some explanations on not implementing the details in the design:

The drop-files-to-screen-to-create-project  functionality is removed due to unclear value and usability concerns (now Examples Tab resides in the same view, it's confusing, for example, a user might want to drag-n-drop files to submit an example).
The pagination of Project List in the design didn't consider "specify the number of project per page", we need further discussion on this. At the moment the original TablePagination is kept.
I think the "Sorting" in the Example List needs more discussion: 1) it's a new feature 2) its location is far away from the list in the design, might have some usability concerns (normally the filter/sorting option should directly on top of the list). So, I decided to postpone the implementation.

It's okay to replace this with GitHub widget actually... it's a better indicator of what this is/doe

s

Can this go straight to this dialog?

Title of this "New Project"

Can we change this to the non-table type of pagination please?

Reduce to 0px

Reduce by 16px

Capitalise "Delete Project"

Could we change the text button for all dialogs to be blue?

Change to "more options"

Please use this version illustration!

This is super annoying overlap... could you move intercom to bottom right side of screen please?

Could we match with https://github.com/orchest/orchest/pull/1027#issuecomment-1151116909
Also could we update text button on both dialogs to say "Keep Project"?

@ncspost All your remarks are addressed. Here are some explanations.

It's okay to replace this with GitHub widget actually... it's a better indicator of what this is/does

Actually I found a technical bottleneck: every example will fire a request to GitHub, and user could pretty easily hit rate limits with an IP (i.e. the numbers will stop showing after a few visits to the Examples View.).

Can we change this to the non-table type of pagination please?

The fact that it is a MUI Table under the hood and TablePagination just works out of box. And the same Table component is re-used in many places. If we want to plug Pagination to Table component, it'd be better to do this in the mega PR, where we could capture all use cases.

Can this go straight to this dialog?

Good idea. I'll come back to this later.

Can "click Import of an example" go straight to this dialog?

@ncspost Just pushed my changes. You could test it.

Please use this version illustration!

@ncspost  I don't think this version is the same as the one in the final Figma file. https://www.figma.com/file/o9S8qtPAx3Vd1HIVtsQfYv/ORC-573-Navigation%2C-layout-%26-IA-(solution)?node-id=1445%3A60215
Could you update the Figma file since it's the single source of truth for implementation? Thanks.

Caught a typo here.
I see what you mean about it being a little weird with the tooltip @iannbing - we can make this better by using a disabled cursor and extending the text to "First create a Project to navigate here"

I keep on getting this error message when trying to import quickstart

@ncspost

we can make this better by using a disabled cursor and extending the text to "First create a Project to navigate here"

Implemented and pushed.

I keep on getting this error message when trying to import quickstart

I couldn't reproduce this on the latest commit. Could you deploy the latest commit and test it again?


Windows 7 PromoteHandle BSOD [ SYSTEM_THREAD_EXCEPTION_NOT_HANDLED]

Hello,
today I tried to Promote a Handle and give it All Acess rights, I can load a driver and all is fine.
But then I try to call PromoteHandle my PC bsod and I cannot do anything, so I testet the PromoteHandle on Windows 8, 8.1, 10 there is it working without a Problem but on Windows 7 it crashs.
Here is a Picture of the Bluescreen dump.
http://puu.sh/lVe6b/aa9d35a1cd.PNG
http://puu.sh/lVe7c/39ef985932.PNG
I hope you may can help me, to fix this error.

Can you send me a BSOD memory dump + your driver pdb?

Sure.
Here you go : s0pex.xyz/Debug.zip
Github dont wanted that I Upload it here normal it says Unfortunately, we don’t support that file type.

Weird. But this BSOD was triggered by failed security cookie initialization during driver startup.

And how I can prevent this or fix ?

I know this is very late but WDK 8+ changed the way the security cookie is initialized.  Make sure you're targetting Windows 7.


Horizontal Scroll

Is Horizontal scroll support for this control?

I'm also interested in that feature. it seems like the split area directive set the overflow:x hidden with the ! important so I assume that it is mandatory but I'm would like to have an explanation also

Hi @KelvinKaYiuLok @HugzM ,
Sorry for the delay!
Yes you can have an horizontal scroll using a div container inside your split-area like the following plunker:
http://plnkr.co/edit/mOqKDF?p=preview
let me know if it helps you.

It helps  me 👍

Hello @bertrandg ,
I checked the plunker project, and unfortunatelly it does not work any more.
I created a stackblitz project which uses div as you recommended. I do not see any horizontal scroll bar.
Stackblitz project: https://stackblitz.com/edit/angularsplit-horizontalscroll
How could I implement horizontal scrolling?

@He-Wolf It works perfectly if you change split-area to as-split-area in app.component.scss

Yes, you are right. :) I corrected the stackblitz project.
Thanks for the quick response and support!


isApplicable Testing for Convolution Stability Tests

Convolution stability tests (see #586)

Anyone knows what this means?

This issue is not well defined and therefore its utility is unknown


Inclusion criteria

Hissp's repository seems to be several projects rolled into one:

The Sphinx docs, with separate licensing.

API docs
Tutorials
Quick Start
Style Guide
FAQ
The Lissp ReST directive.
The Lissp lexer.

setup.py

the README

The Hissp compiler
The Lissp reader

REPL
CLI
munger

The bundled macros
The testing machinery

Sybil parser
workflows

Some of these components seem a lot more stable than others, and that's an argument for separating them. The stable parts could get a 1.0 release, without the unstable parts holding them up. I'm obviously not going to break up all of these pieces. Some really do belong together.
Some of the documentation/testing machinery, the Sybil parser, Lissp ReST directive, and the Lissp lexer, at least, would be useful in other Lissp projects. That's an argument for adding them to the hissp package itself, but they have dependencies (Sybil, Sphinx), and I don't want hissp to have any dependencies. I could maybe make those dependencies optional, or I could split them off into their own package, which still seems a bit premature until Lissp stabilizes.
Hissp and Lissp maybe don't need to be together. Readerless mode is usable in its own right. Hebigo is already separate. I feel like I'm close to being able to implement an EDN-based Hissp as well. Lissp turned out to be a bit more complex than I wanted, mostly around the "reader macros", which is an argument for simplifying them, and munging. But currently, the docs and tests for Hissp proper depend on Lissp being there. Separating them seems premature, but it's something I'm considering.
That leaves the bundled macros. Having them implemented in Lissp complicates packaging a bit. Hebigo's macros are in readerless mode, so that's an option, but it's dogfooding Lissp/Hissp at least a little, which I feel is important. That said, this is one of the least stable areas, and one most in danger of bloat. Every addition needs tests and docs, which also have to change with changes. Those are strong arguments for separating them, but Lissp feels kind of crippled without them, so I'm reluctant to give them up. On the other hand, most of the early tutorials get by without them, and macros can really only expand to code that you could write yourself, but some of them seem to really help a lot.
Therefore, the bundled macros should be very minimal, but where do we draw the line? It's been my own case-by-case judgement so far, without too much thought for the whole. I've changed my mind several times. I've removed things and tried different approaches. That's why I want to develop some more objective criteria for what gets included and what doesn't.

I want to enumerate the candidates, but this is getting too big for an issue comment. Moving to the wiki: https://github.com/gilch/hissp/wiki/Bundled-macro-candidates

OK, most of the candidates are implemented. I will probably end up dropping a few of these that don't seem worth it, but I expect to keep most of them. The rest need docs/tests. There are a few more advanced threading macros in Clojure that I probably won't be implementing this pass (if ever), although I'm still seriously considering ...
I did get generators (yield) working via a smallish prelude class. That one was giving me trouble for a long time. It took a lot of iterations once I figured out how to do it, but I think I've found a balance I'm happy with. As a part of the micro-prelude that might be at the top of every file, a terse implementation was a high priority, but the result still had to be usable. I hand-minified (golfed?) it down to eight lines, by far the most complex object defined in the prelude, but much shorter than the Pythonic style would have been.

#155 is ready.

Merged.

The missing candidates still up for consideration are

Arc ssyntax :, !, ~, .. Anarki has more now. A bundled reader macro could expand these. This is getting too complex. I can see this approaching APL-level terseness, like J's hooks and forks. Where does it end? : seems especially useful, but kinda built into Hebigo already, and trailing parens aren't that hard with parinfer. Maybe belongs in an external library. Leaning against it.
Clojure/Hy ../.. Hebigo uses !of:, which seems a bit less useful in Lissp. I want getattr, getitem, and call somehow. It would be nice if it could do slice notation too. -> can already do it via calls, but it's pretty verbose. Not sure how this should work yet, but it's a loose end.
as->. Seems much less important than ->/->>. Python's argument ordering isn't always as consistent as Clojure's, but methods (at least) work well with ->. An alternative might be a let1 or let-in that has (value name *body) form so it fits in -> and can adapt functions that don't fit. But X# pretty much works already. Leaning against.
cond->/cond->>. Not in Python or the other Lisps, but they're more imperative than Clojure. It's hard to call this essential. Leaning against.
some->/some->>. Similar story. Leaning against.
case-lambda. Arity matching. This is built into Clojure's defn. One would usually have default arguments in Python instead, but this might work a little better for macros. Given case and specialized use cases, it's hard to call this essential. Leaning against.

I'm also considering a bench or timeit macro that can run a snippet repeatedly. time# doesn't have the resolution to distinguish fast cases.

Adding @#foo as an abbreviation for (operator..attrgetter 'foo).
It's a bit strange that spam.foo in Python is easily expressed the same way in Lissp, and spam-expr().foo() is still easily expressed as (.foo (spam-expr)), but something like spam-expr().foo required awkward workarounds, like (getattr (spam-expr) 'foo).
Now it can be expressed simply as (@#foo (spam-expr)), perhaps similar to Clojure's (.-foo (spam-expr)) syntax.
It also works in ->, so (-> (spam-expr) (@#foo) (@#bar)) works like spam-expr().foo.bar.

BTW, attrgetter names can have internal dots:
#> (-> (object) (@#__class__.__class__.__name__))
>>> # Qz_QzGT_
... # hissp.macros..QzMaybe_.Qz_QzGT_
... __import__('operator').attrgetter(
...   '__class__.__class__.__name__')(
...   object())
'type'

Really leaning against .. now.

Adding get# as an abbreviation for operator..itemgetter (single-arg version only). That makes getitem work in ->.
First (car) is now get#0, which is really nice; implementation is the best name. Don't expect this to work on iterators, but let-from can pull those apart.
Rest (cdr) is now (get#(slice 1 None) foo). Still not nearly as nice as foo[1:]. Python's notation seems unassailable here. Nothing I've come up with beats an inject: .#"foo[1:]". Of course, that's only for simple cases.

Added a tutorial on making a macro for easier slice notation. I don't know that I want to bundle this one. It works best with a helper class. It's small enough to maybe inline, but that seems too heavyweight for how it's likely to be used. Maybe it's no worse than the itemgetter we're already using. __slots__ would probably make it even lighter, even if it does take a bit more code to define. I could certainly process literals at read time, but that's slightly less useful. It's also a string-injection macro. I have mostly avoided those so far, but this case wouldn't be too bad if I only supported literals. There's always slice as a fallback. I'm considering it. Definitely tier 4.

I figured out how to do it without the helper class. New version also added to tutorial. Added in #166.

Added decorators and removed deftype@ in #167. There's kind of a conflict between the @# attr getters and the decorator macros, which would most naturally have the same name. The attr getters seem more important, and also share the @ mnemonic with set@ and<EMAIL_ADDRESS>So decorators are @@#!foo instead of @#!foo for now. The extra is already enough to make them distinguishable, so I could just overload the name, but this is a bit awkward to document and implement. setat, zapat, at# would give up the symmetry with set! and zap!, but be more similar to get#.

Overloaded @# to be both attr getter and decorator (as  @#! ) in #168. Wasn't that hard to implement, but does make the docstring a little strange.

I'm eliminating the attergetter- overload for @#. #171. It saved all of two characters vs. X#X.. If I had thought of that earlier, I probably wouldn't've implemented @# in the first place. Because others might not think of it either, I kept the examples in the docs.


GridView widget problem with array query parameters

I want to use filter in grid view that allows me to select multiple values (for example <select multiple=multiple>). But with current implementation of the yii.gridView::applyFilter  Js method I can't do this, because, it does not support mulpile parameters with the same name here:
https://github.com/yiisoft/yii2/blob/master/framework/assets/yii.gridView.js#L89
I think it would be greate to rewrite this part of code to support multiple parameters with the same name

@omnilight yeah, it's a problem. Can you make a PR?

#10223

https://github.com/yiisoft/yii2/commit/d3cfb87ba67a328d197d1a9e52dbb12a7bf8476b

I've found small, but important bug.
I the case when you have standard Html::activeListView as a filter input, it really adds two inputs: one is select with the name name[] and second is hidden input with name name. Second one is passed, when no value is selected.
In the case we have selected some value, query string will be: name=&name[]=1&name[]=2. That's correct. Now, if you deselect all values from select, applyFilter function will find only hidden's input value (because of $(settings.filterSelector).serializeArray()). So, when later it will try to override query string values, it will not override &name[]=1&name[]=2 part because no key name[] will be in the keysInFilter variable. So my new pull-request is fixing with behavior


Incorrect paths in sfz

A few sfz files have paths that incorrectly start with a \ character.  For example
default_path=\Percussion\

That should be
default_path=Percussion\

This causes an error when you try to load it in Sforzando, at least on Mac OS.  This problem appears in four files: Marimba.sfz, TubularBells.sfz, FluteSusVib.sfz, and Flute-KS.sfz.

Fixed all, thanks! Fix should be all sync'd up with the SFZ branch now.


Document exposed filters with images

Once https://bugs.chromium.org/p/skia/issues/detail?id=5163 is fixed, we should document all the filters we expose.

I'm certain all of our image/color filters are well documented and can be found via the Paint API docs:
https://api.flutter.dev/flutter/dart-ui/ImageFilter-class.html


Khcheck Pods are not getting scheduled, also Khstate is stale

Describe the bug
None of the khcheck pod was getting scheduled, Last scheduled pod was a long time ago(~6day ago). On looking at the khstate it was last updated a long time ago(~6day), khstate was stale for all khchecks.
Kuberhealthy service was in Running state.
Steps To Reproduce
Expected behavior
Khcheck Pods should be scheduled, Khstate should be updated.
Screenshots
Since this happened  on a prod environment I didn't get time to collect screenshots and other evidence. We do have Logs (log level : error) of kubehealthy service and khcheck pods in es.  All khcheck pods logs are pushed to a separate index in es. Also I can provide the list of k8s events .

Versions

Kubernetes Version: 1.21.5-eks-bc4871b

Additional context
On restart all khchecks pods were scheduled.   @integrii Can you pls help in figuring out the root cause.

Happy to help there. What was going on in the Kuberhealthy pod logs during the bad behavior?

@integrii  Log level of Kuberhealthy service was set to "error"
During the bad behaviour only logs present were of type "Error parsing run duration: for metric: kuberhealthy_check{check=<>,namespace=<>,status="1",error=""} error: time: invalid duration """"
I have filtered those logs to see for any other logs in service, but it seems no other logs were there.

http server was up as prometheus was successfully scraping metrics for khchecks.

Same issue occurred again, have not restarted yet. @integrii Can you pls help in debugging

Master election is chosen by simply doing a kubectl get pods on Kuberhealthy and picking the instance that comes first in the listing.  This has been consistent in all versions of k8s we tested it on thus far.
Changing the log level to debug might help here... Kuberhealthy should log when it becomes or loses master status.  Try setting logLevel: debug in the configmap.  The last log lines should show where things are stuck.

We also might want to change the health check in the helm chart to an http check instead a tcp one.

Master election is chosen by simply doing a kubectl get pods on Kuberhealthy and picking the instance that comes first in the listing. This has been consistent in all versions of k8s we tested it on thus far.
Changing the log level to debug might help here... Kuberhealthy should log when it becomes or loses master status. Try setting logLevel: debug in the configmap. The last log lines should show where things are stuck.

Yes , We did change log level to debug, we saw only one log line  of configmap change event from non master pod . No activity in master pod (as mentioned earlier it's http server  crashed).
@integrii  What could be the possible reasons for kuberhealthy http server crash ?  there are hardly 40 khchecks running currently,  Since past 22h master pod container has been restarted 5 times (by using http probe)


Version 1.11.0 missing @azure/core-auth

Package Version: 1.11.0

[ ] nodejs

nodejs version: 14
os name/version: Windows 10

[ ] browser

name/version: ____

Describe the bug
A clear and concise description of what the bug is.
Error<EMAIL_ADDRESS>Module not found: Error: Can't resolve '@azure/core-auth' in '\node_modules@azure\ms-rest-js\es\lib'
resolve '@azure/core-auth' in '\node_modules@azure\ms-rest-js\es\lib'
@azure/core-auth is being listed in this version as a dev dependency instead of a dependency.

Should be fixed in v1.11.2 now.  Closing