npm run build error

from a clean clone, running this gets me
><EMAIL_ADDRESS>build /foo/angular2-webpack
> rimraf dist && webpack --progress --profile --bail

/foo/angular2-webpack/webpack.config.js:212
      new CopyWebpackPlugin([{
      ^

TypeError: CopyWebpackPlugin is not a function

the webpack config looks good to me, but I've got like zero experience with it, so I'm kind of lost :)

have you run npm install first?
On May 13, 2016 6:26 PM, "tech-no-logical"<EMAIL_ADDRESS>wrote:

from a clean clone, running this gets me

<EMAIL_ADDRESS>build /foo/angular2-webpack
rimraf dist && webpack --progress --profile --bail

/foo/angular2-webpack/webpack.config.js:212
new CopyWebpackPlugin([{
^
TypeError: CopyWebpackPlugin is not a function
the webpack config looks good to me, but I've got like zero experience
with it, so I'm kind of lost :)
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub
https://github.com/preboot/angular2-webpack/issues/97

yup. npm start works, npm run watch works, but this one doesn't

replacing
new CopyWebpackPlugin(...)

with
new CopyWebpackPlugin.default(...)

fixes it for me. looks like a problem with the plugin ?

Will check later to see if there is a new version of something and broke this up

npm run build working for me
I am on Win10, npm  3.8.5 node 5.8.0

not on ububtu xenial with npm 3.5.2 and node 4.2.6. weird.

try to latest 4.x or latest 5.x node verston  but not 6.x due to this one https://github.com/preboot/angular2-webpack/issues/93

Hey guys,
When I run: npm run build after npm install I get some errors of TypeScript as:
ERROR in ./src/polyfills.ts
(15,3): error TS2304: Cannot find name 'require'.

And no dist folder is created.
My node version and npm version is:
node -v
v5.0.0

npm -v
3.3.6

Any thoughts?
Thx

do you have a typings folder?

No, Should I? I only have a typings.json

Yes, and for some reason it is not doing it for you. Perhaps because you have an old npm (you should install a later version, they are faster).
You can generate the folder if you do
$ ./node_modules/.bin/typings install
But again, should do it for you.

I exec the command U said and now it's working, the folder dist was created as expected.
I guess that this problem is because I'm running node commands as sudo, I'll fix it and update npm.
Thx for the support!

I have run this code, it build the dist folder and eveything works fine. but there is nothing on browser when i open index.html . It shows loading , nothing on console as well ...

answered by @Foxandxss
You need a server to serve the page. Try lite-server or http-server
$ npm install -g  #lite-server
$ lite-server
That inside the dist folder.
SOLVE #120

i'm closing this.


⚠ Bofrost.at has degraded performance

In e0d6b6c, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 1866 ms

Resolved: Bofrost.at performance has improved in 2cd0488 after 9 minutes.


When replacing a Submariner CR, wait for deletion

Before creating the new Submariner CR, wait for the old one to be
completely deleted, including all its owned resources. This should
make upgrades much more reliable.
(Ultimately we need to ensure we cope with fast re-creations...)
Signed-off-by: Stephen Kitt<EMAIL_ADDRESS>

@skitt I'm trying to remember why didn't we update the objects (instead of delete/re-create).

@skitt I'm trying to remember why didn't we update the objects (instead of delete/re-create).

Because there’s nothing we ever want to carry over from the old CR, and by deleting it, we get a lot of processing done for us (cascade-deleting all the dependent resources).


After Switching to iFrame not able to click on any other element which is outside of the page

What happened?
I am switching to jupyter ide iframe
When('{pronoun} switches to Jupyter IDE iFrame', async (actor: Actor) => {
  await actor.attemptsTo(Switch.to(DataScienceIdePage.ideIframe()));
});

and performing some ide related validations.
Once I complete validation I want to click on submit button which is outside the ide iFrame. (i.e. inside main page) but I am getting below error
  ✗ <<Submit Code Button>>.click() (1m 51s 715ms)
        Error: locator.click: Frame was detached
        =========================== logs ===========================
        waiting for locator('xpath=//button[.=\'Submit\']')
        ============================================================

What did you expect to happen?
Once iFrame related operations are done I want to perform actions on main page objects, which is not happening.
Node.js version
v18.18.2
Execution environment
MAc OS
Chrome
How to reproduce the bug.
Switch to iFrame and then click on any other element outside iFrame
Serenity/JS version
"@playwright/test": "^1.39.0",
    "@serenity-js/assertions": "^3.11.1",
    "@serenity-js/console-reporter": "^3.11.1",
    "@serenity-js/core": "^3.11.1",
    "@serenity-js/cucumber": "^3.11.1",
    "@serenity-js/playwright": "^3.11.1",
    "@serenity-js/rest": "^3.11.1",
    "@serenity-js/serenity-bdd": "^3.11.1",
    "@serenity-js/web": "^3.11.1",
    "@types/node": "^20.8.2",
    "@typescript-eslint/eslint-plugin": "^6.18.1",
    "@typescript-eslint/parser": "^6.18.1",
    "axe-html-reporter": "2.2.3",
    "axios": "1.5.0",
    "clipboardy": "^4.0.0",
    "dotenv": "16.3.1",
    "eslint": "^8.50.0",
    "eslint-plugin-import": "^2.28.1",
    "eslint-plugin-simple-import-sort": "^10.0.0",
    "eslint-plugin-unicorn": "^48.0.1",
    "eslint-plugin-unused-imports": "^3.0.0",
    "fs": "^0.0.2",
    "http-server": "^14.1.1",
    "is-ci": "^3.0.1",
    "link-module-alias": "^1.2.0",
    "mailgun.js": "^9.2.1",
    "mkdirp": "^3.0.1",
    "npm-failsafe": "^1.0.0",
    "playwright": "^1.38.1",
    "playwright-core": "^1.38.1",
    "prettier-config-hackerrank": "^2.0.0",
    "rimraf": "^5.0.5",
    "simple-git": "3.22.0",
    "stripe": "14.13.0",
    "ts-node": "^10.9.1",
    "typescript": "^5.2.2",
    "uuid": "9.0.1",
    "pixelmatch": "^5.3.0",
    "pngjs": "^7.0.0"
  },
  "_moduleAliases": {
    "@actors": "common-files/Actors.ts",
    "@models": "common-files/models",
    "@helpers": "common-files/helpers",
    "@common_pages": "common-files/pages",
    "@custom_interactions": "common-files/custom-interactions",
    "@tasks": "common-files/tasks",
    "@utils": "common-files/utils",
    "@config": "common-files/config"
  },
  "dependencies": {
    "axe-html-reporter": "^2.2.3",
    "stripe": "^14.14.0"
  }

page.reload() is also not working after switching context to iFrame

Hi @ChandanHackerrank, if you have a look at the examples in the Switch.to(..) API docs, you'll notice that they follow this pattern:
 await actorCalled('Francesca')
   .attemptsTo(
     Switch.to(LoginForm.iframe).and(                                          // <-- notice the "and"
       Enter.theValue('francesca@example.org').into(LoginForm.usernameField()),
       Enter.theValue('correct-horse-battery-staple').into(LoginForm.passwordField()),
       Click.on(LoginForm.submitButton()),
     )
   )

The idea is that Switch.to(iframe).and(activities) receives a sequence of activities and then automatically switches back when the last one completes.
Does this help?


perf(icon): use auro-icon for selected check mark

Alaska Airlines Pull Request
Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context. List any dependencies that are required for this change.
Resolves: #208
Summary:
Update to use auro-icon for the selected checkmark
Type of change:
Please delete options that are not relevant.

[ ] New capability
[x] Revision of an existing capability
[ ] Infrastructure change (automation, etc.)
[ ] Other (please elaborate)

Checklist:

[x] My update follows the CONTRIBUTING guidelines of this project
[x] I have performed a self-review of my own update

By submitting this Pull Request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
Pull Requests will be evaluated by their quality of update and whether it is consistent with the goals and values of this project. Any submission is to be considered a conversation between the submitter and the maintainers of this project and may require changes to your submission.
Thank you for your submission!
-- Auro Design System Team

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Htmx vs Unpoly

Hi Mr.Dan,
can you make an article to explain the deference between Htmx and Unpoly.
I'm using Unpoly with Django for now, and I'm used Htmx for testing but I think Unpoly more easer and it don't required more configuration.
the only problem in Unpoly that have poor docs for learning.

Not really familiar with unpoly myself  but would be interesting to see a
fork.
On Wed, 9 Feb 2022, 01:50 Abdullah Alnuaimi, @.***>
wrote:

Hi Mr.Dan,
can you make an article to explain the deference between Htmx and Unpoly.
I'm using Unpoly with Django for now, and I'm used Htmx for testing but I
think Unpoly more easer and it don't required more configuration.
the only problem in Unpoly that have poor docs for learning.
—
Reply to this email directly, view it on GitHub
https://github.com/danjac/realworld/issues/1, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAB47M2TWIFB44T43BWRDELU2GT3ZANCNFSM5N35YBDA
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

Ok, I will do that.


Does Waymo use multiple sweeps? How to work with multisweep models.

Issue #1002 seems to indicate that multisweeps is NOT used on the Waymo dataset models.
Yet in the preprocessing code for Waymo, there is a max_sweeps param seen here. The documentation in the function seems to indicate this is about including previous frame information.
When I used the default parameter, max_sweeps=5, I could train the Waymo model successfully. Then, I tried setting max_sweeps=1 as I want to work with single frames, but I could not train the Waymo model at all. The loss would either diverge very suddenly after a number of epochs, or I would get a catastrophic error (always an illegal memory access during sparse.conv_ext.indice_conv_backward_fp32. So clearly this parameter is changing something.
A more general question is, what are guidelines to work with multisweep models in general. I tried inference on Centerpoint NuScenes  models using multiple sweeps of LiDAR as N x [x, y, z, intensity, timestamp] arrays but results were worse than when using a single pointcloud, so I'm probably inputting the data incorrectly.
Thank you for your time.

The error I often encounter is also referenced here: https://github.com/open-mmlab/mmdetection3d/issues/37#issuecomment-906062053 , not limited to the Waymo models


Pass kwargs through in monkey-patched sendfn

Fix for https://github.com/dronekit/dronekit-python/issues/626

I don't fully understand the reasons for the change, but since you and Tridge are happy with this, merging now ...

@hamishwillee ask a monkey? :-o

@billbonney if only I had one handy.


not work in my Xcode7.2(7c68)

Same here. After the update the plugin is not working anymore.

@DanielBocksteger I have solves the problem  through the following site.http://www.bubuko.com/infodetail-1140233.html


Add analytics events for DateTimeSelectorScreen

[!WARNING]
This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

#464  👈 (View in Graphite)
#463
#462
#461
main

This stack of pull requests is managed by Graphite. Learn more about stacking.


Not compatible with React 17.0.2

I get this when attempting to install:
$ npm install --save react-images-upload
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR!
npm ERR! While resolving<EMAIL_ADDRESS>npm ERR! Found<EMAIL_ADDRESS>npm ERR! node_modules/react-dom
npm ERR<EMAIL_ADDRESS>from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm ERR! node_modules/react-images-upload
npm ERR!   react-images-upload@"*" from the root project

To fix this: stackoverflow
Use npm i -save --legacy-peer-deps react-images-upload


Considerations for trees and filtering

This looks very interesting!
I'm currently using redux and the connect decorator to build and filter a tree dynamically. Basically, I use chokidar in my electron app to watch a folder and build an in-memory representation of it. Then, I allow for text-based filtering plus some modes (like flatten or hierarchical) to build another tree that gets rendered reasonably optimally:

maintain a flat representation watching a folder using chokidar and a normalizr-like representation

depending on the search string and mode (flat or hierarchical) and tree node expanded flags, build a flat array to represent the tree (the depth is a numeric property rather than an actual tree)

use connect on each tree node component to pull out a minimal representation into the properties so each component only renders if it actually changed

How would I do something similarly optimized with mobservable?
(basically, I haven't been able to find an example of mobservable for trees yet but think it could simplify my application logic by operating directly on a tree of nodes rather than jumping through hoops with normalr + redux, am wondering about how cascading transformations between different representations should be implemented, and am looking for more clarity on how @observer and @connect are similar in ensuring minimal re-renders given the transformation step).

Hi @kmalakoff
A few comments on how I would approach this.
I wouldn't introduce a flat representation unless this is really convenient for your algorithms. I always suggest to keep the mental model as close to the in memory model as possible as it will benefit the readability (especially for others) of your code base.
After that I would introduce reactive properties that express whether a node should be currently visible, something like:
const currentSearchFilter = observable({
  filter: ''
});

class Folder {
  @observable name;
  @observable fullPath;
  @observable children = [];
  @observable get isVisible() {
      return !currentSearchFilter.filter ||
                name === currentSearchFilter.filter ||
                this.children.filter(child => child.isVisible).length > 0
   }
}

After that just decorate your components with @observable and mobservable will figure out automatically when folders need to be shown / hidden by just changing the currentSearchFilter.filter property:
@observer
class TreeNode extends React.Component {
   render() {
      if (!this.props.folder.isVisible)
          return null;
      return
{this.props.folder.name

                  {this.props.folder.children.map(child => <TreeNode folder={child} key={child.fullPath} />)}

   }
}

That's in the basis all you need as far as I could conduct from your description :)

@mweststrate thank you for the quick response! This makes a lot of sense and I like the clear separation between models and components...using stores as you suggest in the documentation is really clear and clean.
Unfortunately, the transformation step is necessary since the display mode can be logical / simplified (eg. removing folders or flattening and merging similar nodes) or raw as on disk, and I'm filtering the tree by tags, search terms, etc so the raw models are not really what I need to render.
How should I do the following with mobservables in a simple and performant way:
raw models -> representation to render -> rendering in components
I know it is a bit more complicated than usual and I'd love to avoid it, but it is the correct design for the problem. I feel like it is related to somehow configuring a reactive transformation pipeline, but not sure how to configure and propagate the observables themselves to avoid re-rendering.

It is good to realize that observable functions of any kind purely observe the values they did actually use and will always update accordingly if something changes. So if an @observer component uses an value, like isActive during its render phase it will update as soon as it changes. What is even more fun; if you slam @observer on each component, a child will rerender when a value it has used but, unlike when using smart components, its parents will not update. And the inverse holds as well, parents can rerender without rerendering their children; @observer actually applies the pure render mixin as well :)
So a TreeRender component will rerender if either the name changes, or the lists of children. But it won't rerender when one of the children itself changes; because it doesn't access the properties of the children! That is done in the child components. In other words the map just picks elements from the array, which is registered as read for the parent treeNode. But the data inside each child is being read only inside the the child components that are being created, which have their own lifecycle.
To put it differently:
var a = mobservable(7);

var b = mobservable(function() { Math.pow(a(), 2); })

var c = mobservable(function() { b()  + 3 });

In this case c only depends on b, because it doesn't access a directly. Nonetheless c will re-evaluate if you change a to 8, because the changes cascade.
On the other hand, if you would update a to the value -7, b would re-evaluate, because a has changed. But c wouldn't re-evaluate, because b didn't change after re-evaluation.

So suppose you the following property on the Folder data structure, and print the whole json structure in an autorun:

class Folder {
  get toJSON() {
     return {
         name: this.name,
         children: this.children.map(child => child.toJSON)
    }
  }

// later

autorun(() => {
   console.dir(theRootFolder.toJSON)
})

From now on, on any change in any name or children list, the autorun will trigger and print the json. But not all toJSON functions will be called again! Only the the folder that changed, and its parent up to the root will re-evaluate their toJSONfunction. So each observable function acts as its own cache as long as the data it observers doesn't change.
... To be continued, have an appointment right now :)

... So what Folder.toJSON and React components have in common is that each time you render / read you get the same observable which make it really efficient.
So in your case (which sounds completely valid to me) I think you should just start modelling your intermediate state as a second state tree which has (almost) only derived properties as members. That should be pretty straightforward.
But the second important thing to do is that you reuse parts of this tree as much as possible, in essence, given a folder and your transformation function, you want to be able to reuse the same intermediate representation if your transformation function has been applied to he same folder earlier. So probably you need a cache for that mapping, or store reference(s) to the display item on the original folder (the latter is a bit easier as you don' t have to clean up, but maybe less flexible as well). Remember that the second time you apply the same transformation to the same folder you don't have to actually apply it! Your derivation is reactive so that will be done automatically for you.
So something like:
class DiskItem {
  @observable name;
  @observable fullPath;
  @observable children = [];
  @observable get isVisible() {
      return !currentSearchFilter.filter ||
                name === currentSearchFilter.filter ||
                this.children.filter(child => child.isVisible).length > 0
   }
}

class DisplayItem {
  @observable isExpanded;
  @observable canExpand;

  constructor(diskItem) {
    this.diskItem = diskItem;
  }

  @observable get chidren() {
         return this.diskItem.children.map(transform);
  }

  @observable get isVisible() {
      return !currentSearchFilter.filter ||
                this.diskItem.name === currentSearchFilter.filter ||
                this.children.filter(child => child.isVisible).length > 0
   }
}

// using a cache, a simpler approach would be to just store a reference on the diskItem
var displayItems = {}; // map with key: fullpath, value: display item

function transform(diskItem) {
     if (!displayItems[diskItem.fullPath])
          displayItems[diskItem.fullPath] = new DisplayItem(diskItem);
     return displayItems[diskItem.fullPath];
}

I have the strong impression that there is a generic pattern here, that can be applied to avoid the burden of needing to 'cache'.
Let me know whether this helps!

@mweststrate this is exactly what I was looking for. It confirms my hunch that the intermediate representation needed to reuse the identical observables. Thank you!
FYI: my current implementation has a cache for ensuring the same items are looked up, but like you say, it is open to accumulating memory so I like your idea of storing them on the original nodes to allow them to be garbage collected. If I come up with a more generic transform solution or pattern, I'll let you know.
I'm going to run some sandbox experiments with my more complex use cases over the coming days by reimplementing parts of this app in mobservable. I've closed this for now and will reopen if needed.
I really like the simplicity of what you have done...fewer hoops to jump through and less code than redux and much simpler to learn!


[Question] Why foreignTime is not reactive?

https://github.com/annaghi/xstate-svelte-workshop/blob/e60b85a882ea1f480b73c0bec140fb9a7c4f702a/src/workshop/complete/ForeignClock.svelte#L20-L33
Why foreignTime.toLocaleTimeString(...) does not work?

I guess it is reactive? 🤔
  let formattedForeignTime = null;
  $: localTime &&
    foreignTime &&
    // TODO Why foreignTime is not reactive in here?
    (formattedForeignTime = $state.context.foreignTime.toLocaleTimeString(
      'en-US',
      {
        hour: '2-digit',
        minute: '2-digit',
        second: '2-digit',
        timeZone: timezone
      }
    ));

+  $: console.log({ 'state.context.foreignTime': $state.context.foreignTime });

I meant the destructured field foreignTime is not reactive. I assumed this will work:
 let formattedForeignTime = null;
  $: localTime &&
    foreignTime &&
    // TODO Why foreignTime is not reactive in here?
    (formattedForeignTime = foreignTime.toLocaleTimeString(   // destructured field of $state.context
      'en-US',
      {
        hour: '2-digit',
        minute: '2-digit',
        second: '2-digit',
        timeZone: timezone
      }
    ));

I was experimenting with these:
$: console.log({ 'state.context.foreignTime': $state.context.foreignTime });
$: console.log({ 'foreignTime': foreignTime });
$: localTime && console.log({ 'localTime && foreignTime': foreignTime });

Closing this issue without answer. Will create a separate small app to crystallize the question.


Cannot Publish Schema

Hi,
I am trying to publish a schema that I just created on Nexus v0, but I receive a "IncorrectRevisionProvided" error.
The schema is published both under 0.1.0 and 0.1.1. I used the following three methods to publish with no success:
#1.
client.schemas.publish(entity=schema,publish=True)

#2.
client.schemas.publish(entity=schema,publish=True,revision=1)

#3.
url_schem = "http://sprshnexus01.camhres.ca:8080/v0/schemas/kcni/redcap/questionnaire/v1.0.0"
url_schem_publish = "{}/config?rev=1".format(url_schem)
response = requests.patch(json={"published":True},url=url_schem_publish)
print(response.text)

Schema create and publish works using the same variables on Nexus sandbox.
Thanks in advance!

This error usually occurs when the provided revision number is not the latest one. Can you get the schema:
GET http://sprshnexus01.camhres.ca:8080/v0/schemas/kcni/redcap/questionnaire/v1.0.0

and look at the nxv:rev value. That revision value should be the one used when publishing.

Thank you, that resolved the issue.


Too many superfluous console messages

During startup SublimeLinter prints messages about loading linters. These should really only be printed if debug mode is enabled.

The SublimeLinter: flake8 linter loaded and SublimeLinter: php linter loaded messages are redundant. ST is already telling us that those plugins are reloaded. If there is some value in those messages then they can be reserved for debug mode.
When the plugins are finished loading SublimeLinter prints:
SublimeLinter: debug mode: off

This message can be omitted. Print it only if debug mode is enabled.

Lastly, the one I can agree with the most to remove, SublimeLinter: debug mode: off does seem silly, but you'd be surprised after years that when we ask for debug console pastes, that people will post this, with it blaring in their face that debug is off.
I'm sorry that it seems like a lot, but SublimeLinter is a beast, that needs to load many different, independent wheels. It's overall best to sometimes use the 'info' log level and be able to see that in the default console, leaving just the nitty gritty to the debug.

Those messages you posted are well formed. I don't think user laziness or stupidity is good reason to print the debug mode message, nor do I think the redundant messages are valuable outside debugging, wontfix is annoying, but whatever.

I'm sorry, it's not meant to offend. This is a disagreement of opinion. Neither party can be fully right here. As the administrator to this stream of SublimeLinter, I have the choice to accept suggestion, but in this case, I believe the project itself is better rejecting it. If you have a need for this suggestion, then please feel free to fork SL for your own use and pull down changes that happen from the main stream. This is the beauty of open source and git.
As for the wontfix label, this is also not meant in a cruel or malicious way. It is simply a standard label that allow myself, maintainers, and our future selves to be able to quickly find features that were earlier passed on that may now fall into scope of the project.

After looking around and consulting https://github.com/SublimeText/PackageDev/issues/134
Here is a compromise: https://github.com/SublimeLinter/SublimeLinter3/commit/6278e30747ee1b96717fd4029ce6e130d7bbab83
Thanks for your help.

I'm not offended. It takes a lot to offend me.
That change is not a compromise (at least in terms of the debug mode message), it's precisely what I wanted.
Do the same with the other two messages.
There are also other messages. Those are not the only ones. For example when linter is activated it's prints a messages(this message seems to occur when you first open a python file) :
SublimeLinter: flake8 activated: /usr/bin/flake8

It’s a compromise to the effect that this is all I am willing to do right now towards the issue.
Thanks again!

On Oct 20, 2017, at 6:50 PM, Gerard Roche<EMAIL_ADDRESS>wrote:
I'm not offended. It takes a lot to offend me.
That change is not a compromise (at least in terms of the debug mode message), it's precisely what I wanted.
Do the same with the other two messages.
There are also other messages. Those are not the only ones. For example when linter is activated it's prints a messages(this message seems to occur when you first open a python file) :
SublimeLinter: flake8 activated: /usr/bin/flake8
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub, or mute the thread.


Delete old version (<IP_ADDRESS>)

Checklist for Pull Requests

[x] Have you signed the Contributor License Agreement?
[ ] Is there a linked Issue?

Manifests

[x] Have you checked that there aren't other open pull requests for the same manifest update/change?
[x] This PR only modifies one (1) manifest
[ ] Have you validated your manifest locally with winget validate --manifest <path>?
[ ] Have you tested your manifest locally with winget install --manifest <path>?
[ ] Does your manifest conform to the 1.6 schema?

Note: <path> is the name of the directory containing the manifest you're submitting.

Microsoft Reviewers: Open in CodeFlow

URL: https://languagetool.org/download/windows-desktop/Languagetool.Packaging_<IP_ADDRESS>/Languagetool.Packaging_<IP_ADDRESS>_x64.msixbundle
Response Error: The remote server returned an error: (404) Not Found.
(Automated message - build 720)


Migrating away from latest.tar.gz

Description
The latest.tar.gz is no longer advertised by Source Controller for GitRepository CRs, hence we are forced to drop support for it in the konfigure. This PR introduces a minimal, in my opinion, changes that are necessary to achieve that goal.
The new behavior can be characterised as follow. The lastmod has been replaced with the lastarchive that holds name of the archive currently loaded into cache. Each time the kustomizepatch command gets executed, the konfigure uses the name kept in the aforementioned file to issue a HEAD request to Source Controller to check the archive is still advertised. This is to avoid unnecessary download of it again. In case it is gone, and since we cannot rely on the latest.tar.gz, the konfigure uses the Service Account's token to issue a GET request to the Kubernetes API server to get the giantswarm-config GitRepository. It then gets the latest artifact URL from this Git Repository .status.artifact.URL field and uses it for downloading a new archive and replenishing cache with it. The GitRepository CR is get in this way to avoid extending konfigure with a true Kubernetes client and importing Source Controller-related packages.
One thing that is not nice about this part of the konfigure, regardless of latest.tar.gz being supported or not, is it gets executed each time an App with accompanying configuration is to be generated. Hence if we have 50 applications in collections, the kustomizepatch is going to be executed 50 times, and this means 50 requests to at least Source Controller. It would be much nicer if we had a side-car container running and watching the GitRepository CR for changes, and updating cache on spotting a new archive. But this obviously requires slightly more work and hence would delay the migration.
Towards: https://github.com/giantswarm/roadmap/issues/2650
Checklist

[x] Update changelog in CHANGELOG.md.

Wondering if we can use something to identify unique runs somehow so it is downloaded only once. I found this so far but it does not seem useful unless there are more annotations: https://github.com/kubernetes-sigs/kustomize/blob/master/cmd/config/docs/api-conventions/functions-spec.md?fbclid=IwAR2FnNC7tIdoEnmF73EwnJP8t-t0WQR39XvES4dIeIS6zPtpYYWvm9EATjU#internal-annotations
Or maybe maybe if the path in internal.config.kubernetes.io/path contains the git hash, we can cache the config source URL for that hash so we only run it once. Tho if the cache persist between run it would not use the new config if the source othwrwise did not change. 🤔 😞

@uvegla Not sure what you mean. I believe the solution persists the cache between runs now. We keep the name, which contains a checksum, of the latest archive known to us. And at each run we check if it is still available at Source Controller by issuing a HEAD request. Only when not, we then get the GitRepository CR and use its .status to download a new artifact, and after that, when a next resource is built, the source is there so it is not downloaded again. Is that what you have meant?


Android error " Parameter specified as non-null is null: method kotlin.jvm.internal.Intrinsics.checkParameterIsNotNull, parameter value"

Hi
I can't see what is causing this error

Parameter specified as non-null is null: method kotlin.jvm.internal.Intrinsics.checkParameterIsNotNull, parameter value

The app compiles with the code from this repository, references are fine.
I call
 digestKeccak = "Hello World".toByteArray().digestKeccak(parameter = KeccakParameter.KECCAK_512)
This (or any attempt at calling the digest method) fail with the same error
I would be grateful for any ideas or a solution. Thanks

I think the issue is with initialising BigInteger - specifically using the value of BigInteger.ONE at the top of the Keccak.kt file
That instance does not appear to be initialised so it seems it would return null

I will close this issue since it is really on the BigInteger library - issue referenced above


fn not highlighted for function pointer types

For example:
Option<extern "C" fn (c_int)>

fn is not highlighted as keyword (and if there is no space before the opening parenthesis, it's erroneously highlighted as an identifier).

Fixed by https://github.com/rust-lang/sublime-rust/pull/65

@aldanor closing


Some RFC 1769 conformance

This changes the protocol version to 1 for maximum compatibility, see:

The VN field must
agree with the software version of the NTP or SNTP server; however,
NTP Version 3 (RFC-1305) servers will also accept Version 2 (RFC-
1119) and Version 1 (RFC-1059) messages, while NTP Version 2 servers
will also accept NTP Version 1 messages. Version 0 (RFC-959) messages
are no longer supported. Since there are NTP servers of all three
versions interoperating in the Internet of today, it is recommended
that the VN field be set to 1.

It also adds the validity checks for the server reply as described at page 9 and 10 of the same RFC.
https://www.rfc-editor.org/rfc/rfc1769.html

Added one more check. While this isn't defined in the RFC some SNTP 3 clients do it and SNTP 4 has it in its RFC.

This seems to work for the current server, time.windows.com, but would all of these changes work if somebody were to want to use another NTP server?

would all of these changes work if somebody were to want to use another NTP server?

Has been testes against pool.ntp.org. Also should work with all NTP servers.

Some more infos:
LI == 11 or packet.stratum == 0 or received timestamp == 0 can happen if the NTP server itself is not correclty synced, so according to (S)NTP specs this shold always be checked for.
packet.li_vn_mode beein 0x04 is required by the spec, so a good thing to check for.
VN beeing 1 highers compatibility without harming anything.


Update pyproject.toml

Can this module supports google-api-python-client v2.0.0 or above?

Hi! Thanks for your interest in v2 compatibility. Unfortunately it's not quite as simple as bumping the constraint, because v2 started bundling discovery documents instead of fetching them at runtime. It might be the same for some or many of the APIs but I'd like to base the stubs on these bundled documents to avoid any false negatives or positives. Thankfully it's not a huge change and I'll try to get it done this weekend.

I've just released v0.6.0 which adds support for v2.

Thanks for your answer :)


False warning on Ollama model names

After the we now get:
[WARNING] [io.quarkus.config] Unrecognized configuration key "quarkus.langchain4j.ollama.embedding-model.model-name" was provided; it will be ignored; verify that the dependency extension for this configuration is set or that you did not make a typo
[WARNING] [io.quarkus.config] Unrecognized configuration key "quarkus.langchain4j.ollama.chat-model.model-name" was provided; it will be ignored; verify that the dependency extension for this configuration is set or that you did not make a typo

when the application starts.
@radcortez any idea what the issue is?

Yes. I've noticed that you added both a fallback and a relocate, but they both use the same function, when the function should be inverse.
The fallback and the relocation add the resolved property to the list of names (used to determine which properties are unused). You get the warning if the unmapped property does not cycle back to the mapped property. For instance foo fallbacks to bar which relocates to foo.

Oh, I didn't realize that, thanks for spotting the problem!


Automated Package Upgrade

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Create a function to add/remove recipes

Need a function to add/remove recipes.

Added in v1.0.0 beta


Grab the guild count and member count in real time(it didn't seem to update in real time)

Thank you for your pull request!


Fix README formatting

Code snippets should not overflow horizontally:

Table formatting is off:

We fixed this: https://github.com/MrPowers/jodie/pull/58


For avoiding SERVICE_UNAVAILABLE -- no Raft leader

Type of change

Bug fix
New feature
Improvement (improvement to code, performance, etc)
Test update
Documentation update

Description

Additional details

Related issues

We require signed commits, please follow the instructions here to sign your changes: https://github.com/hyperledger/fabric/pull/421/checks

/azp run

Thanks for contribution! Please update PR message to reflect the intend of this change.
Also, i wonder why this change is needed, as single node orderer should also work. Are you seeing any errors running the sample?

Yes. While running sample(basic-network), got the above error. So updated the document

Thanks for contribution! Please update PR message to reflect the intend of this change.
Also, i wonder why this change is needed, as single node orderer should also work. Are you seeing any errors running the sample?

Yes. While running sample(first-network), got the above error. So updated the document

normally it takes a few seconds for a leader to be elected, depending on election timeout config. So you may see this error if a channel has just been started, and you'll need to retry. Plus, adding more orderers would not solve the "problem".
Are you seeing this error constantly after several retry?

close due to inactivity. pls reopen if needed.


Update dependencies

Ran bundle update.
This was mainly to try and get Snyk to stop complaining about nokogiri :crossed_fingers:

I'm just going to push an equivalent nix update on top of this if ya don't mind...


malfeasance2: update GRPC API

Motivation
This updates the malfeasance v2alpha1 endpoints to be able to return both legacy and v2 malfeasance proofs.
Description
I changed the malfeasance events to not include the encoded proof any more instead they only report which identity was detected to be malicious and expect the receiver of the event to fetch a proof from the state DB if needed (or call Info on one of the two malfeasance handlers to get information about the malicious behavior of the given identity)
GRPC tests have been updated to check if both v1 and v2 malfeasance proofs are handled correctly.
The malfeasance2.Handler in this PR always returns sql.ErrNotFound to keep the PR size manageable. The full implementation of the malfeasance2.Handler can be found in https://github.com/spacemeshos/go-spacemesh/pull/6307
Test Plan
existing tests have been updated and new tests were added for changed / added functionality
TODO

[x] Explain motivation or link existing issue(s)
[x] Test changes and document test plan
[x] Update documentation as needed
[x] Update changelog as needed

bors merge

Possibly overlooked before approving -- are we really using request.Limit?
It does not seem to be included in SQL queries and all of the rows are retrieved

Possibly overlooked before approving -- are we really using request.Limit? It does not seem to be included in SQL queries and all of the rows are retrieved

Yes we do - IterateOps uses the sql/builder package to build queries with limit. There are even tests that assert that request.Offset and request.Limit work as expected:
https://github.com/spacemeshos/go-spacemesh/blob/0cb2cfa2a1f329e29c8c28d971c0b13e24ffbe13/api/grpcserver/v2alpha1/malfeasance_test.go#L144-L152

Ok I see, thanks.
BTW read transaction still makes sense from consistency standpoint.
Imagine an API client making two requests w/o limit specified which yield N malfeasant identities. With new v1 malfeasance being processed between queries, it may so happen that these 2 sets of N identities may have different contents, with one item disappearing and another one taking its place (given that the order of items is by the ID which is effectively random) which may confuse some clients, as it breaks the assumption of the malfeasant identity set being add-only (no items should be removed)

Flaky test: https://github.com/spacemeshos/go-spacemesh/issues/6113
bors merge


Don't add ActionDispatch::Static middleware

Summary
On the case that we want to have previews on production environment but rails is not managing the static files is not necessary to add the middleware ActionDispatch::Static. If not the an error saying No such middleware to insert before: ActionDispatch::Static will be raised when we executed bundle exec rake assets:precompile.
There is a configuration flag on rails that we can use to check if rails is serving static files: public_file_server.enabled. This flag on combination with view_component.show_previews is used to know if the middleware should be inserted or not
Other Information

:wave: Hello and thanks for pinging us! This issue or PR has been added to our inbox and a Design Infrastructure first responder will review it soon.

:art: If this is a PR that includes a visual change, please make sure to add screenshots in the description or deploy this code to a lab machine with instructions for how to test.
:fast_forward: If this is a PR that includes changes to an interaction, please include a video recording in the description.
:warning: If this is urgent, please visit us in #primer on Slack and tag the first responders listed in the channel topic.

@danigonza any interest in continuing work on this PR?

@joelhawksley since this seems inactive I created a new pull request to finish this off

Thanks for your work on this @danigonza. Closing in favor of https://github.com/ViewComponent/view_component/pull/1892


Revert "Don't assume AssetName is UTF8"

This reverts commit 2144866b074698e5adec894fc24a7c5b79304c35.
Reverting as this was only changed in display, but transaction building still assumes latin1. It makes more sense to do this as one piece when devs have time to work on this to limit churn with community tools.

Looks reasonable to me. @sjoerdvisscher does this interfere with the reasons you needed this merged?

This was opened as a result of community feedback. Two complaints:

To be clear: I did not anticipate that this change would change the structure, and we don't need that. We only need support for non-UTF8 asset names.
I have asked @j-mueller to weigh in regarding how much reverting this will be a problem.

@disassembler : Without this change we won't be able to send certain transactions from the PAB to the wallet backend. So I would very much prefer not to revert it. The spec is pretty clear on this: AssetName can be any bytestring.

@j-mueller Would the PAB be able to continue developing against the existing version, if we back this out for this release and promise to have it (properly!) working again by the time the PAB is ready? @disassembler I guess this would mean we'd need to push a new release for PAB compatibility (but that wouldn't need a new HF)

I've asked @cblp to work on this, discuss the changes needed with him.

If this change is made, to make the token names as HEX due to a requirement of the PAB, I would also kindly suggest that cardano-cli support hex names at the same time.

@nc6 : Yes we will be able to keep working on the wallet backend integration, which is our main task currently. But after the HF, when our change is put back in, we'll also need a new release of the wallet backend, because that's where we send the transactions that use this encoding.
And just to be clear what the consequences are: Any apps that use hashes for AssetNames won't be able to send transactions to the network via wallet backend as long as the latin1 encoding is used. This includes everything that uses the thread tokens feature of our state machine library.

If I understand correctly, no-assuming-utf-8 works correctly, and reverting it will fail utxo queries. So, I object against assuming UTF8 and 3206. It's safer to show hex strings.

bors r+

Do we have an idea on how the switch to hex will look like for the normal query utxo output and also for the cli parameters --tx-out and --mint?
Is the idea to keep the . structure with the '.' in the middle as separator for all the outputs/inputs, or will it be a combined hexstring with  like the metadata-registry subject?

or maybe with an additional parameter for the cli query utxo command '--decode' to get out a readable format and defaulting to pure hex output?

resolved via https://github.com/input-output-hk/cardano-node/pull/3211


Regenerate gapic code

This includes the updated headers. It also includes changes to:

Pubsub (adding new methods)
Speech (adding streaming support)
Client config json files (removing retry_codes_def)

Updated, PTAL

Updated to fix reading VERSION file


Documentation

Version
1.12.3
Development Environment
Server is Express in a Node environment on Ubuntu.
Browser is Chrome 75.0.3770.142 (Official Build) (64-bit) on Mac 10.13.1
Current Behavior
Tui.calendar appears to be wonderful!  I'm finding the getting started instructions to be incomplete though.  When I follow https://github.com/nhn/tui.calendar/blob/master/docs/getting-started.md (using the 'month' defaultView, as shown in the JS below, the day-of-month grid is missing (image attached).  Looking at your API documentation, it's not clear what needs to be done differently.
If I change defaultView to 'week' (that's the only change to the JS below) I get a grid of times, but when I try to create a schedule using the default creation popup, I get an error (screenshot attached).

import Calendar from 'tui-calendar'; /* ES6 */
import "tui-calendar/dist/tui-calendar.css";

// If you use the default popups, use this.
import 'tui-date-picker/dist/tui-date-picker.css';
import 'tui-time-picker/dist/tui-time-picker.css';

var calendar = new Calendar('#calendar', {
  defaultView: 'week',
  taskView: ['milestone', 'task'],
  scheduleView: ['allday', 'time'],
  useCreationPopup: true,
  useDetailPopup: true,
  timezones: [{
    timezoneOffset: null,
    displayLabel: 'Local',
    tooltip: 'Depends on browser'
    }, {
    timezoneOffset: -420,
    displayLabel: 'Los Angeles',
    tooltip: 'GMT-08:00'
    }],
  template: {
    monthGridHeader: function(model) {
      var date = new Date(model.date);
      var template = '' + date.getDate() + '';
      return template;
    }
  },
  calendars: [
    {
      id: '1',
      name: 'My Calendar',
      color: '#ffffff',
      bgColor: '#9e5fff',
      dragBgColor: '#9e5fff',
      borderColor: '#9e5fff'
    },
    {
      id: '2',
      name: 'Company',
      color: '#00a9ff',
      bgColor: '#00a9ff',
      dragBgColor: '#00a9ff',
      borderColor: '#00a9ff'
    },
  ]
});

Screenshot of empty day-of-month grid:

Screenshot of error when using default popup to create schedule in week view:

Expected Behavior
I suggest that the getting started example should:

Show the grid of days
Use the default popups to create and edit schedules

Thank you!

@entropicrune
Do you still have this problem?

Yes.
On Mon, Jul 29, 2019 at 7:37 AM 조정은<EMAIL_ADDRESS>wrote:

@entropicrune https://github.com/entropicrune
Do you still have this problem?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/nhn/tui.calendar/issues/358?email_source=notifications&email_token=AAIXWX3BJUOB2PAZ2T6HZ4DQB3JARA5CNFSM4IHEUSJKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD3AN3BI#issuecomment-515956101,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAIXWX2RM5JJQAW5U7EIDBDQB3JARANCNFSM4IHEUSJA
.

--
Arthur Griesser  Founder  Prometheus Computing, LLC
Mobile:<PHONE_NUMBER>
Blog: https://prometheuscomputing.com/company_site/blogs
https://img.newoldstamp.com/r/71207/w
Email<EMAIL_ADDRESS>https://img.newoldstamp.com/r/71207/linkedin
https://img.newoldstamp.com/r/71207/quora

@entropicrune
Sorry.
Remove node_modules.
After 'npm install'
You need to reinstall npm packages.

After re-install, the error is gone.  Thank you jungeun-cho!
When I click the "Save" button, I expected to see a new schedule.  I guess the default creation popup does not actually call createSchedules.  How do I make the default do that?
When I set defaultView: 'month', I still don't see the days.  I expected something like this:

Instead I get only the following, with no grid of days:

@entropicrune Check this doc. I think you don't set the height style of container element.

Thank you dongsik-yoo, that did solve the missing grid problem.  It seems strange to me that this height affects the monthly view, but not the weekly view.
I will look at the code to try to figure out how to make the default creation popup actually save schedules.

I hope the following link will help you.
Happy coding. 🙂
https://github.com/nhn/tui.calendar/tree/master/examples
https://nhn.github.io/tui.calendar/latest/tutorial-example00-basic


Running processes - The sort order for Started is a mess

When i sort by Started the sort order will be a mess because it will sort by 0-9 and 07 is before 2018. Could this be fixed?

I also wondering if it could show a more specific Started time? I believe this will fix the above sort order issue if it show full date-month-day?

The sorting results are correct in terms of sorting but it sorts different kind of data, and I am not sure how it's related to the presentation (theme).
@jcameron Can we make _proc_module use make_date sub to generate time/date? By doing so, it will do sorting based on timestamp (delivered by theme_make_date), and thus will make it correct?

So sort by Started is totally useless when it mixes time, dates and years like it was random. Is that really how it should work?

This should be fixed on the server-side.

I've checked in a fix to use proper date formatting for this field.

Okay, cool.
I have made few tweaks as well and now sorting for Started not only works perfectly but also displays time in from now format, making it very comfortable to read.
Example:


Update kit-deployer to change labels after the deployment is complete

From: Quick Rollbacks
tl;dr We want the ability to continue running the previous X number of deployments even after a new deployment is out. We will direct all traffic to the new deployment via labels allowing us to do an instant rollback by updating labels to send traffic back to a previous deployment.
Deployment Workflow

Run kubectl label --overwrite pod -l sha!=$sha3 state=backup
Run kubectl label --overwrite deployment -l sha!=$sha3 state=backup
Delete n-3 deployments that are older than sha=$sha3 deployment

Rollback Workflow

Run kubectl get deployment -l sha=$sha2
Run kubectl label --overwrite pod -l sha=$sha2 state=live
Run kubectl label --overwrite deployment -l sha=$sha2 state=live
Delete all deployments newer than sha=$sha2 deployment

I've updated the description with more details.

We've since had to change the workflow. Here is the updated workflow:
Deployment/Rollback Workflow

If strategy == fast-rollback then continue
Rename deployment to <name>-<deployId> to prevent updating the current live deployment
Suppress deploying any service manifests until after all deployment manifests are available
If <name>-<deployId> is not already deployed, then Deploy as usual, otherwise skip deployment
If deploy fails then skip (fail as usual), otherwise continue
Verify deployment is fully available
Verify service selectors does select pods running in the cluster
Deploy all service manifests
If NOT rollback, delete n-3 deployments that are older than deployId=$deployId deployment creationTimestamp
If rollback, delete all deployments newer than deploy=$deployId deployment creationTimestamp

@chesleybrown Before you close this PR, I'd like that text (or whatever the final result is) in the Quip doc, por favor. That's super useful. ^

One other thing, @chesleybrown - we'd discussed storing 4 backup versions to make the deployment of previous versions easier. From my memory, we were going to delete N-4, so that when the following occurs:
A - backup
B - backup
C - backup
D - backup
E - current
F - new
A would be deleted right away during deployment, and then if F is rolled back, there are still 3 version to roll back to in backup.
~A - backup~
B - backup
C - backup
D - backup
E - current
~F - new~ (rolled back)
Does that match your understanding?

@brianhall I've updated the document with the latest workflow/diagrams.

This was implemented in #85 and #91, going to close.


Update documentation website to correct code examples for checkbox and radio button regarding background and color classes.

Also check the source code example ordering, e.g. checkbox1 placed after checkbox2, etc.

Completed.


Chin Spot placement highlight tiles

Would be great to have added to the hunter plugin. Common spots to place traps for chin hunting,
e.g. https://twitter.com/Zoydberg/status/745229185447268352
Very similar to cannon placement plugin

We have NPC tagging, and as of #2404, will have respawn locations of tagged NPCs. Chin placement spots are always around the respawn locations, so unless there's more to it than that, this should be resolved with #2404?

As others have said, use respawn indicators and/or ground markers.


Update geppetto to 4.3.1

Thank you for the contribution. It was merged directly as 402a32dad133edca3f6c6ca8030ff50feea29e18 to keep commit history cleaner. Your contribution is still credited to you.


Correct way to unsubsribe from channels in case of network failure / app going into background

Hi,
what is the correct way for an app to handle:

In case of a network failure/air plane mode to reinitialize when the network is back?
When I want to update my presence display depending of the app going into the background. Just unsubscribe and resubscribe or should I reinitialze the whole client and channel subscriptions?

Thanks a lot for this awesome package

Hi!

No need to reinitialize or reassign the client (if you didn't dispose it), it's well encapsulated. Just call client.reconnect(). Yes, it's better to reconnect while network changes since the connection gets interrupted.
Call client.reconnect() in this case also when app comes back from the background and organize your channel subscriptions like:

final StreamSubscription connectionSubs =
     client.onConnectionEstablished.listen((_) {
   for (final channel in allChannels) {
     // Subscribes to the channel if didn't unsubscribe from it intentionally
     channel.subscribeIfNotUnsubscribed();
   }
 });

With this, the stream will fire the event and automatically subscribe channels once you declare it.

Thanks for the quick reply. What if I want to intentionally unsubscribe when the app goes into background?
Am 13. Nov. 2023, 20:40 +0100 schrieb Kerim Amansaryyev @.***>:

Hi!

No need to reinitialize or reassign the client (if you didn't dispose it), it's well encapsulated. Just call client.reconnect(). Yes, it's better to reconnect while network changes since the connection gets interrupted.
Call client.reconnect() in this case also when app comes back from the background and organize your channel subscriptions like:

final StreamSubscription connectionSubs =
client.onConnectionEstablished.listen((_) {
for (final channel in allChannels) {
// Subscribes to the channel if didn't unsubscribe from it intentionally
channel.subscribeIfNotUnsubscribed();
}
});
With this, the stream will fire the event and automatically subscribe channels once you declare it.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: @.***>

Unsubscribe what? Channel or client?

Thinking again, unsubscribing should be enough to trigger a a presence 'user left' event
Am 14. Nov. 2023, 01:32 +0100 schrieb Kerim Amansaryyev @.***>:

Unsubscribe what? Channel or client?
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you were mentioned.Message ID: @.***>

Thanks a lot for your prompt resonses. I told our manager to buy you some coffees :-)

@escamoteur I appreciate it so much! Thank you!

Maybe adding a section to the Readme that contains what you told me here might be helpful for others
Am 15. Nov. 2023, 17:08 +0100 schrieb Kerim Amansaryyev @.***>:

Closed #42 as completed.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you were mentioned.Message ID: @.***>


Use new API endpoint

Fixes #7 - although, currently, the old API endpoint seems to redirect to the new one on the remote side.

@fabaff  & @mattsches
The curl url needs to be changed on https://www.home-assistant.io/integrations/luftdaten/


add changelog items for 0.55.0

Add 0.55.0 section in changelog to prepare for releasing 0.55.0.

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 58.57%. Comparing base (6c44e1f) to head (a19c310).

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #445      +/-   ##
==========================================
- Coverage   59.41%   58.57%   -0.84%
==========================================
  Files          71       71
  Lines        4408     4408
==========================================
- Hits         2619     2582      -37
- Misses       1174     1220      +46
+ Partials      615      606       -9

Flag
Coverage Δ

2.1
?

2.2
35.68% <ø> (-12.66%)
:arrow_down:

2.3
35.73% <ø> (-13.25%)
:arrow_down:

2.4
35.91% <ø> (-13.12%)
:arrow_down:

2.5
35.77% <ø> (-13.25%)
:arrow_down:

2.6
35.77% <ø> (-13.25%)
:arrow_down:

2.7
35.77% <ø> (-14.96%)
:arrow_down:

2.8
?

3.0
54.19% <ø> (-0.46%)
:arrow_down:

3.1
55.69% <ø> (-0.59%)
:arrow_down:

3.2
55.69% <ø> (-0.64%)
:arrow_down:

3.3
40.08% <ø> (-16.25%)
:arrow_down:

3.4
42.28% <ø> (-16.43%)
:arrow_down:

3.5
42.15% <ø> (-14.37%)
:arrow_down:

3.6
42.15% <ø> (-14.37%)
:arrow_down:

community
42.96% <ø> (-0.50%)
:arrow_down:

enterprise
52.45% <ø> (-5.59%)
:arrow_down:

integration
58.57% <ø> (-0.84%)
:arrow_down:

Flags with carried forward coverage won't be shown. Click here to find out more.

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


performance issue for some data handling in MultipartDecoder

The performance issue for data handling in MultipartDecoder( issue #2430 ) still exist.

Generate a file with code:

def test52():
    with open("uploadfile.dat","wb") as f:
        def _gen():
            yield b"\r"
            for i in range(10000000):
                yield b"1234567890"
        for i in _gen():
            f.write(i)
if __name__ == '__main__':
    test52()

Extract this project: upload_test.zip
pip install -r requirements.txt in this project
pip install werkzeug version you want to test
run command "uliweb develop" in this project
access http://localhost:8000
upload the file generate above

upload can be finished with several seconds, but it need about 47 seconds with werkzeug 2.0.2 and 2.2.2, if the file is bigger the upload time will increase with o(n^2) growth.
Environment:

Python version:3.9.7
Werkzeug version: 2.2.2 and 2.0.2

Simpler to reproduce the problem may be these:
Add this function to tests/test_formparser.py:
    def test_multipart_slow(self):
        def parse_multipart(stream, boundary, content_length):
            parser = formparser.MultiPartParser(content_length)
            return parser.parse(stream, boundary, content_length)
        def _gen():
            yield b"\r"
            for i in range(1000000):
                yield b"1234567890"
        data = b"".join(_gen())
        pytest.raises(ValueError, parse_multipart, io.BytesIO(data), b"foo", len(data))

Then run:
pytest test_formparser.py -k test_multipart_slow

@pgjones I explain in this comment, but the logic is for werkzeug 2.0.2, I am not sure for 2.2.2, but from the test result, the handling time of 2.0.2 and 2.2.2 is almost the same, so I think it is still o(n^2) in 2.2.2, if we increase the file size, the time will be much longer, so the test result also prove that.

I can't reproduce this, the test you've provided seems to scale linearly for me.

time unit: seconds
| 2.0.2 | 2.2.2 | main(b1911cd)
-- | -- | -- | --
50m | 11 | 11 | 11
100m | 43 | 43 | 36
150m | 82 | 75 | 97
200m | 171 | 132 | 153
250m | 270 | 207 | 227
300m | 307 | 328 | 299

Given that a maintainer cannot reproduce this, I'm closing this. It seems like something that is local to your machine, or you haven't provided enough detail to reproduce the issue.

It not only my local, in other's computer, and our servers, all can reproduce this problem, actually some users report that when they upload files.

Ok, but you haven't managed to convey that in a way that we can address, so it's on you at this point to diagnose it further.

I think I have given the steps how to reproduce in the first description, maybe you guys haven't try it.
I will try to make a PR later with another way, make the user can increase the buffer_size by give a parameter, which I think it is a good choice to users.

We have, in fact, tried it, as we stated earlier.

I have submit the PR #2514, you can have a look,

Data between different buff_size:
| 128 * 1024 | 512 * 1024 | 1024 * 1024
-- | -- | -- | --
50m | 4 | 1 | 1
100m | 20 | 6 | 3
150m | 43 | 14 | 8
200m | 70 | 20 | 12
250m | 119 | 33 | 16
300m | 252 | 52 | 22

Whilst increasing the buffer size, does reduce the number of next_event calls, and hence regex searches. I can't see the same improvement you have in your tables, nor do I see any indication of quadratic scaling.

You mean you don't understand why the buffer_size will can cause so much improvement? I am not sure I understand your question.
And for "any indication of quadratic scaling", from the data I am not so sure, but it is obviours that the increasing is not linear.

I add some log and get some more detail data, now my understanding about this problem is, for this kind of data, at last werkzeug will read all the data into memory, for example 100MBytes data, if buffer size is 10241024, it will split the data into about 96 data blocks to extend, and if buffer size is 641024, it will split the data into 1526 data blocks to extend, so the non-linear increasing is the buffer extend times.
2022-09-17 16:10:08 INFO #95 buffer +1048576 data, 98565991
2022-09-17 16:10:08 INFO #96 buffer +385482 data, 99614567
buffer_size: 1048576, time: 3.7 seconds, speed: 26996949.4 bytes/s
2022-09-17 16:11:50 INFO #190 buffer +524288 data, 99090279
2022-09-17 16:11:50 INFO #191 buffer +385482 data, 99614567
buffer_size: 524288, time: 6.0 seconds, speed: 16612928.1 bytes/s
2022-09-17 16:12:35 INFO #762 buffer +131072 data, 99745639
2022-09-17 16:12:35 INFO #763 buffer +123338 data, 99876711
buffer_size: 131072, time: 19.9 seconds, speed: 5020752.2 bytes/s
2022-09-17 16:13:33 INFO #1525 buffer +65536 data, 99876711
2022-09-17 16:13:33 INFO #1526 buffer +57802 data, 99942247
buffer_size: 65536, time: 38.4 seconds, speed: 2607136.3 bytes/s

The underlying call is bytearray extend, which I think is this code. Looks like the resize strategy is to create the exact required size on each extend, so clearly quicker if this is called less.

>>> 3.7/96
0.03854166666666667
>>> 6/191
0.031413612565445025
>>> 19.9/763
0.026081258191349932
>>> 38.4/1526
0.02516382699868938

Look like the times of function invoked is the main factor, buffer size is not the main factor.
So what do you think about the adding of buffer_size parameter? That won't change any default behavior of werkzeug, but give user choices to optimize the performance.

I do not want a configuration for this. Identify and fix the actual issue with the implementation.

Do you mean choose some way for example reimplementing a new bytearray.extend which don't having this performance issue?

I don't know, if I did then we would have already fixed it. If you think there's a performance issue with bytearray, then you need to report that to Python, not us.

My thinking is different, I think that is mainly because the buffer size too small, I don't have so much high expectation to a Python lib, Python is not C/rust, and the cost of a function call in Python is more expensive than C/rust, I don't think it is a right way to optimaze for Python.

Ok, I think we're at an impasse then and you'll need to move on from this.

OK, if you insist to hardcode the buffer size, I will think about make another package release just add the parameter exposed.


Reduce Docker image size and improve security

Welcome!

[X] Yes, I've searched similar issues on GitHub and didn't find any.
[X] Yes, I've searched similar issues on the Traefik Mesh community forum and didn't find any.

Proposal
I was able to reduce the Docker image size by 77% (8.6 MB instead of 38.8 MB in v1.4.8) by compressing the static binary and switching from alpine to scratch, only a few lines had to be changed.
Of course the security attack surface shrank massively too, no other binaries or libs with new CVEs every week.
Background
The Docker images are not being rebuilt regularly to address CVEs, so reducing the attack surface improves security by a long shot.
Smaller images start faster and make development easier when running integration tests again and again.
Workarounds
I have to rebuild mesh if I want to improve security, the project should do it so all users can enjoy these official improvements.

Is this repo active at all?


[In-progress] Adding windows_task resource

Description
Adding support for windows_task resource
Issues Resolved
https://github.com/chef/chef/issues/5810
https://github.com/chef-cookbooks/windows/issues/407
https://github.com/chef-cookbooks/windows/issues/245
https://github.com/chef-cookbooks/windows/issues/176
Check List

[ ] New functionality includes tests
[ ] All tests pass
[ ] RELEASE_NOTES.md, has been updated if required (not required for bugfixes, required for API changes)
[ ] All commits have been signed-off for the Developer Certificate of Origin. See https://github.com/chef/chef/blob/master/CONTRIBUTING.md#developer-certification-of-origin-dco

Is the plan for this implementation to use schtasks.exe or will it migrate to the win32 api? Will triggers be supported (chef-cookbooks/windows#258)?

@Tech356 the immediate effort is to obtain feature parity in core with the windows cookbook. This is one of the last, if not the last, resource we plan to migrate from the windows cookbook into core. We're trying to fix the bugs filed against the resource as well, but not trying to add features to it. The goal is to get a stable resource into Chef 13 to facilitate deprecating the resource in the windows cookbook.

This looks good to me @NimishaS . I'd really like to see some functional tests here. In the windows cookbook we had kitchen tests that created tasks and tested that the tasks existed and ran as well as some other functionality. Having equivilent functional tests would be great.

@mwrock , we had skipped the functional testcases for time being as this functionality needs to be merged for Chef 13. We had a discussion about this with @btm.
We have plans to add functional testcases later. Adding functional testcases requires 2-3 more days. Adding testcases for test-kitchen will require some more time. If that's ok then I can start work on that today.

@NimishaS are you happy for us to release this without functional tests? If so, we need to get this merged today for the 13.0 release candidate, before the release on monday.

@thommay , I have done a thorough testing for windows_task resource: https://gist.github.com/NimishaS/04cbc6937e32d74dc4bdbd2f72526e6a.
It's working successfully. This PR is good to merge. We will add the functional specs soon.

Done @thommay


Fix typos

Thank you for your contribution, @kianmeng!

:partying_face: :partying_face: :partying_face: :partying_face: :partying_face:


Some edits to the user study writing

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint.


Some batching improvements part 1 (ScheduleManager) - work in progress

Description
Related to 743 in ADO.
Does this introduce a breaking change?
Yes, ScheduleManager now requires a callback to fetch the clientId in the constructor.

@kian-thompson , @andre4i, can you please chat and see what makes sense here? You both are poking in this area, and I feel like there is some overlap / stepping on each other. Andrei - please also glance at Justus compression PR, it feels like in general we are changing where and how we process things (i.e. it's a pipeline with multiple steps - batch chunking, gathering batch, compression, unpacking), and we likely need to re-evaluate how to isolate and packages code.

@vladsud ack!
This PR can be closed. It was mostly experimental from my pov and I was aiming at refactoring the schedule manager to make it a more explicit state machine and fix some validations as part of ADO:743. None of which make sense in the current codebase though.. Noted about the pipeline!


Refactor: Move SetViperStructDefaults to utils

Summary
Provide a brief overview of the changes and the issue being addressed.
Explain the rationale and any background necessary for understanding the changes.
List dependencies required by this change, if any.
This change was reverted in https://github.com/stacklok/minder/pull/2822. https://github.com/stacklok/minder/pull/2839 was merged to solve the config overriding problem.
Change Type
Mark the type of change your PR introduces:

[ ] Bug fix (resolves an issue without affecting existing features)
[ ] Feature (adds new functionality without breaking changes)
[ ] Breaking change (may impact existing functionalities or require documentation updates)
[ ] Documentation (updates or additions to documentation)
[x] Refactoring or test improvements (no bug fixes or new functionality)

Testing
Outline how the changes were tested, including steps to reproduce and any relevant configurations.
Attach screenshots if helpful.
Review Checklist:

[x] Reviewed my own code for quality and clarity.
[ ] Added comments to complex or tricky code sections.
[ ] Updated any affected documentation.
[ ] Included tests that validate the fix or feature.
[ ] Checked that related changes are merged.

coverage: 47.36% (+0.01%) from 47.348%
when pulling 2fa1d82500a6a92412d5f7c7eaa0cb3e117e66dc on Vyom-Yadav:mv-to-utils
into 6f69727b17ed9ac0cfa5ffeaa3d01cff7ef7a3ef on stacklok:main.

@jhrozek @JAORMX If you're around, can we merge this? Just refactoring so the function can be used at https://github.com/stacklok/minder/pull/2638


G002 gives a false positive with translated strings

For example, when using gettext, it's common to write code like:
_("Loading module: %(module)s") % {"module": mod}

or:
_("Loading module: %s") % mod

If these messages are logged (for example, in a multilingual command line tool), like:
logger.info(_("Loading module: %s") % mod)

Then, G002 is raised, although the % operation is on the return value of a function (which is not how people typically misuse the logging module).

I feel hesitant to allow the format operator when the left side is a call expression. For example:

def test(): return "abcd %s"
...
logger.info(test() % "1")

This could be rewritten to

```python
def logTet(arg):
	logger.info("test %", arg)

log(1)

I also think flagging the gettext call is somewhat in the spirit of the rule. Ideally, gettext only gets called if the logger's level is higher than the called log function to avoid an unnecessary gettext calls and string interpolations.
I would probably explore adding custom infoTranslated helper methods that conditionally call gettext.

Ahh, good call. I'll close – but if some future user does want something similar, it can of course be reopened.


Failed to clone repository .... Underlying error: Failed to start SSH session

Hi Folks,
i am using an app and got this errormessage, maybe you can help with this message:
Failed to clone repository .... Underlying error: Failed to start SSH session: Unable to exchange encryption keys
Does anyone here have a tip for me?
thanks
hartmut

#643 has updated libssh2 to 1.8.0, which works against the "new" GitHub cryptosuite. You should check with the app's developer so it updates its Objective-Git framework. In the meantime, I'm closing the issue, but feel free to reopen !

Hi Etienne,
thanks.
hartmut


Fix Remove expect() in token transfer's acknowledgement conversion

Closes: #389
Description

PR author checklist:

[x] Added changelog entry, using unclog.
[ ] Added tests.
[x] Linked to GitHub issue.
[ ] Updated code comments and documentation (e.g., docs/).
[ ] Tagged one reviewer who will be the one responsible for shepherding this PR.

Reviewer checklist:

[ ] Reviewed Files changed in the GitHub PR explorer.
[ ] Manually tested (in case integration/unit/mock tests are absent).

what is the status of this PR? @DaviRain-Su it seems like you didn't address Farhad's review. Is this still something you're planning to work on?

present, I have no any idea.

I will close this as stale.


Sort the files and save the .bin model file for backwards compatibility

Changelogs

Tried fixing #84

See the issue for more details, but the ultimate fix was just to reupload the featurizers.

Also save the .bin files, as with transformer>=4.35.0 the default has changed to .safetensors and we want to remain backwards compatible.

Checklist:

[X] Was this PR discussed in an issue? It is recommended to first discuss a new feature into a GitHub issue before opening a PR.
[ ] ~Add tests to cover the fixed bug(s) or the new introduced feature(s) (if appropriate).~
[ ] ~Update the API documentation if a new function is added, or an existing one is deleted. Eventually consider making a new tutorial for new features.~
[X] Write concise and explanatory changelogs below.
[X] If possible, assign one of the following labels to the PR: feature, fix or test (or ask a maintainer to do it for you).

Can you pin the version of datamol or fsspec here ?

The test GH action succeeds again.
Also tested it locally with:
import datamol as dm

from molfeat.trans.pretrained.hf_transformers import PretrainedHFTransformer

# Load a pretrained model
model = PretrainedHFTransformer(kind="ChemGPT-4.7M", notation="selfies", dtype=float)
feats = model.transform(dm.data.freesolv().iloc[:100].smiles)
print(feats)


Error: No such label 'emitAssets' for WebpackLogger.timeEnd()

When following nest.js doc for hot reloading,
Hot reloading docs
Error: No such label 'emitAssets' for WebpackLogger.timeEnd()
\Desktop\projects\github_visualization\backend\node_modules\webpack\lib\logging\Logger.js:123
                        throw new Error(`No such label '${label}' for WebpackLogger.timeEnd()`);

this error happens.
It works well with @0.0.11 but @0.0.12 causes this error.
When looking for the commit which has changes between @0.0.11 and @0.0.12, I could only find this.worker.pid, but I'm not sure this causes the error.

Reverted the breaking changes. version 0.0.14 deployed. Apologies for a late revert :eyes:

Test it if it works and then i'll close an issue. Have no projects to test by myself for now

Okay, I'll test 0.0.14 and let you know. Thank you.

It works well with @0.0.14!


l's not 1's

Microsoft PowerToys version
0.63.0
Installation method
PowerToys auto-update
Running as admin
Yes
Area(s) with issue?
TextExtractor
Steps to reproduce
Using text extractor on a picture of a spreadsheet print out, it misread an email address.  It interpreted<EMAIL_ADDRESS>as<EMAIL_ADDRESS>
✔ Expected Behavior
Interpret text correctly.
❌ Actual Behavior
The lower case "L" was interpreted as the number "1"
Other Software
No response

@Tmiv44
It would be good to hid the first part of the e-mail address in the screenshot. #privacy

@Tmiv44 this is a result of 1 and l looking nearly identical. There is no way for the OCR engine to know which is which.
I doubt there is any fix.


Revert "sched: Don't duplicate caller file handler when creating kernel thread"

Summary
since the temporary kernel spawn proxy need duplicate file handler
from caller, please reference the follow source code for more info:
sched/task/task_posixspawn.c
sched/task/task_spawn.c
and the original patch: https://github.com/apache/incubator-nuttx/pull/5391
This reverts commit 5c5f1dec08390cbb92484a2efbd2cbe5b75b3188.
Impact
Keep the old behavior until we remove the proxy thread
Testing
sim:ostest

Do we have a task (issue) to remove the proxy thread?

No, it's on my TODO list, could you create an issue?


fix invalid getWorldSurfaceY() computation

Heightmap getter was not called correctly, thus messing up block rendering. This was especially noticeable in the End.
Before:

After:

Oh wow! Thanks for that ^_^


[Feature] Add functional search bar

Add functional search bar
Currently there are no ideas which tools we could use to implement search feature

Stale.


Melee attack system

Assigned to: Unassigned

Basics is now done.
DamageEntity now takes damage form both SpellController and MeleeController


🐞 - Calendar month pagination doesn't work with Angular v15

Which @taiga-ui/* package(s) are the source of the bug?
core
Please provide a link to a minimal reproduction of the bug
https://stackblitz.com/edit/angular-6je2tk?file=src/app/app.component.ts
Is this issue blocking you?
Non-Blocking
Description
Calendar month pagination doesn't work with Angular v15. That issue is only in simple Calendar component, CalendarRange works well.
Angular version
15.1.4
Taiga UI version
3.17
Which browsers have you used?

[X] Chrome
[X] Firefox
[ ] Safari
[ ] Edge

Which operating systems have you used?

[ ] macOS
[X] Windows
[X] Linux
[ ] iOS
[ ] Android

The issue with this example is that you recreate TuiDay on each change detection cycle. It becomes a new object which is passed to [value] which in turn switches month back to the month of that value. If you memoize it, it would work.


Spot solution

@unrealab we need to pull out Network Security Groups, Network Interface Configuration, and Location and perhaps add back in VM size if we think we'll run into region issues.

@unrealab we need to pull out Network Security Groups, Network Interface Configuration, and Location and perhaps add back in VM size if we think we'll run into region issues.

Yeah.. will scrub.


Requirements for the Domain Controller to exist within the AVD subscription are not clearly outlined.

The requirement for a DC to be located within the subscription isn't clearly stated in the "Requirements" section. Its implied, but isn't called out explicitly until later when going through the actual configuration:
"For Domain controller resource group, select the resource group where the AD DS VM is either located or peered to. The resource group with the domain controller must be in the same subscription. The get started feature doesn't currently support peered subscriptions at this time."

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

ID: d6474476-1912-a090-9c28-6c0613adfd5c
Version Independent ID: 4e3457e0-6abb-92fb-5080-56f5be0356fd
Content: Deploy Azure Virtual Desktop getting started feature - Azure
Content Source: articles/virtual-desktop/getting-started-feature.md
Service: virtual-desktop
GitHub Login: @Heidilohr
Microsoft Alias: helohr

@mcrosstx Thank you for the feedback!  We've assigned this to the document author for further review.

Thanks for the feedback. This information is now in the prerequisites section.
#please-close


⚠ Bofrost.fr has degraded performance

In 9be2ef2, Bofrost.fr (https://www.bofrost.fr) experienced degraded performance:

HTTP code: 200
Response time: 1151 ms

Resolved: Bofrost.fr performance has improved in 7a6bd4a after 47 minutes.


[3.0.X] Fix crash when function contains fused extension type

backport of #6204

python 3.5 tests seems to be failing but they are already failing in 3.0.X branch so I am merging PR.


TB-8 Modify posts content and adjust site layout

Please review for the merge to master branch.

LGTM. 👍


property order in subclass

Say I have 2 schemas a.json and b.json that generate classes A and B.
In b.json I "inherit" a.json using the "extends" mechanism.
In the generated classes A and B there is a JsonPropertyOrder annotation that specifies the correct property order; however, when serializing, B's properties appear before A's properties in the resulting JSON.
Is there a way to make Jackson serialize the super class properties before the subclass?

According to https://stackoverflow.com/questions/17995623/jsonpropertyorder-and-fields-from-the-super-class it looks like it should be ignoring the property order declared in A all together. If that's the case, we may need to update the property order declared in B to enforce that A properties are written before B properties.
However, as I'm not particularly savvy with the JSON schema standard, I have to ask whether super class properties preceding subclass properties is part of the standard or is it simply something you'd prefer? How do we know that it should be A->B instead of B->A?
In the short term, you can solve the problem using a jackson mixin, but that's understandably not a good solution since it requires you to make mix ins for all of your classes that have inheritance.

However, as I'm not particularly savvy with the JSON schema standard, I have to ask whether super class properties preceding subclass properties is part of the standard or is it simply something you'd prefer? How do we know that it should be A->B instead of B->A?

I think it's just a matter of preference, really, so I'm not sure this is even a bug. But I think "superclass properties before subclass" is what makes most sense.
The order of fields in a JSON object is not significant, but JSON documents are also sometimes read by humans so there should be a way to control this.

In the short term, you can solve the problem using a jackson mixin, but that's understandably not a good solution since it requires you to make mix ins for all of your classes that have inheritance.

I don't have that many so I might do this as a workaround.

I could see cases where you would want either one first.  I would say most of the time though that I would prefer the super class first then the subclass.  The best reason would if the base class defines a id I would like that to be first regardless of which class in the hierarchy is used.
I could see the following property order control to be defined:
Super Class -> Child Class
Child Class -> Super Class
Super Class Required -> Child Class Required -> Super Class Optional -> Child Class Optional
There is lots of discussion on the json schema project about this and I am not sure if it all resolved at some point. There was talk of moving it to sub-schemas like a json schema for UI.

Brainstorming of Implementation Types:

Single Static Property Order, non configurable
Built-In Property Orders defined in Generation Config
Built-In Property Orders defined in Generation Config with providing custom implementations for "ordering things" (could be made general purpose to maybe support toString or equals methods etc.)
Defined In Schema itself

In-Place with Property Definitions
Separate extension property, similar to javaEnums/javaEnumNames

.... more?

There is lots of discussion on the json schema project about this and I am not sure if it all resolved at some point. There was talk of moving it to sub-schemas like a json schema for UI.

Do you have a link to this maybe ? I'm surprised this is a concern of the json schema project, as a schema is mainly a definition of validity and we know that in this respect, the order of properties is not relevant.

https://github.com/json-schema-org/json-schema-spec/issues/571
https://github.com/json-schema-org/json-schema-vocabularies/issues/7

Some progress about this:
I was set to write a custom annotator to include the parent class properties first in the PropertyOrder annotation, but then I did an experience: I removed the PropertyOrder annotation altogether in one of the generated subclasses, and what happened was that the properties were serialized in the expected order: parent class properties, then subclass properties (in class order)!
So, my conclusion is that Jackson's serialization strategy is:

first, all properties specified in PropertyOrder
then all remaining properties from parent class (recursively)
then all remaining properties from subclass (in class order)

By generating a PropertyOrder, we actually tell Jackson to serialize the subclass properties first.
My workaround for this is to use a custom annotator that extends Jackson2Annotator, and replaces the propertyOrder method with a no-op:
public class CustomAnnotator extends Jackson2Annotator {
    public CustomAnnotator(GenerationConfig generationConfig) {
        super(generationConfig);
    }
    @Override
    public void propertyOrder(JDefinedClass clazz, JsonNode propertiesNode) {
    }
}

By systematically using the PropertyOrder annotation, we force Jackson into a behavior which is not "natural". Without the PropertyOrder annotation, Jackson does the least surprising thing. My suggestion would be to make this the default behavior

Without the PropertyOrder annotation, Jackson does the least surprising thing

IMO it's great that the generated @JsonPropertyOrder preserves the order of the properties in the schema (I've tested with sourceType=yamlschema). That allows an ordering that is relevant to the doman.

Of course, but if you read all the discussion form the start, you'll see that it's about the order of properties when inheritance is involved.


Dashboards don't work with scylla 1.6+

The following sed fixes some graphs, but not all:
sed 's/{type=\\\"\([a-zA-Z_ ]*\)\\\", metric/_\1{type/g' -i grafana/scylla-dash-per-server.json

@amnonh we need either a branch (or tag) per Scylla release or a dashboard group per version.
You have been looking at the second, any results?

Yes,
Without changing grafana (maybe we should)
Tagging works.
Starring does not works (based on storing in the DB)
row repeat does not work
No hierarchy support

Thanks, please send a PR

@amnonh ping

@amnonh ping
People are using monitoring with master branch as well. Keeping dashboards broken for so long is a source of pain to people like me, who want to test changes. Changes to scylla-grafana-monitoring should be ready at the same time as changes to scylla.
\cc @slivne

On Tue, Jan 3, 2017 at 3:24 PM, Tomasz Grabiec<EMAIL_ADDRESS>wrote:

@amnonh https://github.com/amnonh ping
People are using monitoring with master branch as well. Keeping dashboards
broken for so long is a source of pain to people like me, who want to test
changes. Changes to scylla-grafana-monitoring should be ready at the same
time as changes to scylla.
\cc @slivne https://github.com/slivne

We have moved to tag based dashboards.
There's a v1.6, v1.5 supported dashboard, I'll add v1.7 and will keep it up
to date with master.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/scylladb/scylla-grafana-monitoring/issues/104#issuecomment-270113216,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ACBRv6ifLpmwbUasydSM8I9Eu37iMzSzks5rOkv1gaJpZM4LUJjm
.

Closing since we now have a dashboard pre Scylla release (and master)


Align teams channel commands with our naming convention

Align the team channel commands with out naming convention.

teams channel get

Rename -c, -channelId to -i, --id
Remove short -i from -i, --teamId
Rename --channelName to --name

teams channel remove

Rename -c, --channelId to -i, --id
Remove short -i from -i, --teamId
Rename --channelName to --name

teams channel set

Rename --channelId to -i, --id

Dependant on: #3688

Remove short -i from -i, --teamId
Rename --channelName to --name
Rename --newChannelName to --newName

@pnp/cli-for-microsoft-365-maintainers
Any remarks on this one?

v6 already has some changes that you're suggesting but some points do need some improvement.

teams channel get

Remove short -c from id and change it to -i
Remove short -i from teamId
Add short -n to name

teams channel remove

Remove short -c from id and change it to -i
Remove short -i from teamId

teams channel remove

Rename --channelId to -i, --id

Dependant on: #3688

Remove short -i from teamId

Maybe we could also remove the short -i from teams channel add to align it with the other commands

Thank you for the feedback @Jwaegebaert. I've updated the spec!

Let's ensure that we do these changes timely for v6 and also include them in the v6 upgrade guidance.

For suggestion #3, I'd say, let's merge #3688 directly to v6 and do it right the first time, instead of introducing new functionality in v5.9, only to break it in v6 😄

I'll merge this one with #3688


Can you add this to bower?

Searched for you in bower, can't find this library. Is it possible to add this so my team can keep all our external dependencies centralized?

@siriusstrebe
bower install ng-intl-tel-input --save
straight from Readme...

Sweet, thanks.


[bdwgc] Update to v8.2.0

Remove 001-install-libraries.patch (all changes are in upstream)
Change REF from 0c8905e84 (old master) to v8.2.0
Remove -Dbuild_tests=OFF which is default one
Kill spaces at EOLn in portfile.cmake
Update version-string, reset port-version

Describe the pull request

What does your PR fix?
Fixes #...

Which triplets are supported/not supported? Have you updated the CI baseline?
<all / linux, windows, ...>, <Yes/No>

Does your PR follow the maintainer guide?
Your answer

If you have added/updated a port: Have you run ./vcpkg x-add-version --all and committed the result?
<Yes / I am still working on this PR>

If you are still working on the PR, open it as a Draft: https://github.blog/2019-02-14-introducing-draft-pull-requests/

Hello @vicroms,
Could you please help with this PR? I don't understand why it fails.

Builds are still failing

Is git-tree value correct?

Still failing, help is appreciated:
-- Performing post-build validation
/debug/share should not exist. Please reorganize any important files, then use
    file(REMOVE_RECURSE "${CURRENT_PACKAGES_DIR}/debug/share")
The /lib/cmake folder should be merged with /debug/lib/cmake and moved to /share/bdwgc/cmake.
Please use the helper function `vcpkg_fixup_cmake_targets()`
The following cmake files were found outside /share/bdwgc. Please place cmake files in /share/bdwgc.

    /Users/vagrant/Data/packages/bdwgc_x64-osx/lib/cmake/bdwgc/BDWgcTargets.cmake
    /Users/vagrant/Data/packages/bdwgc_x64-osx/lib/cmake/bdwgc/BDWgcConfig.cmake
    /Users/vagrant/Data/packages/bdwgc_x64-osx/lib/cmake/bdwgc/BDWgcTargets-release.cmake
    /Users/vagrant/Data/packages/bdwgc_x64-osx/lib/cmake/bdwgc/BDWgcConfigVersion.cmake
    /Users/vagrant/Data/packages/bdwgc_x64-osx/debug/lib/cmake/bdwgc/BDWgcTargets.cmake
    /Users/vagrant/Data/packages/bdwgc_x64-osx/debug/lib/cmake/bdwgc/BDWgcConfig.cmake
    /Users/vagrant/Data/packages/bdwgc_x64-osx/debug/lib/cmake/bdwgc/BDWgcTargets-debug.cmake
    /Users/vagrant/Data/packages/bdwgc_x64-osx/debug/lib/cmake/bdwgc/BDWgcConfigVersion.cmake

Still failing, help is appreciated:
-- Performing post-build validation
/debug/share should not exist. Please reorganize any important files, then use
    file(REMOVE_RECURSE "${CURRENT_PACKAGES_DIR}/debug/share")
The /lib/cmake folder should be merged with /debug/lib/cmake and moved to /share/bdwgc/cmake.
Please use the helper function `vcpkg_fixup_cmake_targets()`
The following cmake files were found outside /share/bdwgc. Please place cmake files in /share/bdwgc.

    /Users/vagrant/Data/packages/bdwgc_x64-osx/lib/cmake/bdwgc/BDWgcTargets.cmake
    /Users/vagrant/Data/packages/bdwgc_x64-osx/lib/cmake/bdwgc/BDWgcConfig.cmake
    /Users/vagrant/Data/packages/bdwgc_x64-osx/lib/cmake/bdwgc/BDWgcTargets-release.cmake
    /Users/vagrant/Data/packages/bdwgc_x64-osx/lib/cmake/bdwgc/BDWgcConfigVersion.cmake
    /Users/vagrant/Data/packages/bdwgc_x64-osx/debug/lib/cmake/bdwgc/BDWgcTargets.cmake
    /Users/vagrant/Data/packages/bdwgc_x64-osx/debug/lib/cmake/bdwgc/BDWgcConfig.cmake
    /Users/vagrant/Data/packages/bdwgc_x64-osx/debug/lib/cmake/bdwgc/BDWgcTargets-debug.cmake
    /Users/vagrant/Data/packages/bdwgc_x64-osx/debug/lib/cmake/bdwgc/BDWgcConfigVersion.cmake

The failures on arm are like this

Got it, I'll fix it.

D:\buildtrees\bdwgc\src\v8.2.0-a140da6a73.clean\extra\msvc_dbg.c(139,14): error C2065: 'STACKFRAME': undeclared identifier [D:\buildtrees\bdwgc\arm-uwp-dbg\gc.vcxproj]

How to see this in the build logs? Probably I've overlooked it.

All checks passed, waiting for the review.


How to support new arch 'arm64e'

Currently, iPhone XS/XS Max/XR support new arch 'arm64e', we want to the script can build such arch.
But i don't know how to modify 'DEFAULTTARGETS="ios-sim-cross-x86_64 ios-sim-cross-i386 ios64-cross-arm64 ios-cross-armv7s ios-cross-armv7 tvos-sim-cross-x86_64 tvos64-cross-arm64" ' & '      *_ios_arm64.h)
DEFINE_CONDITION="TARGET_OS_IOS && TARGET_OS_EMBEDDED && TARGET_CPU_ARM64"
;;'

https://github.com/jasonacox/Build-OpenSSL-cURL
Finally, I use above build script to support 1.1.1b & arm64e

https://github.com/openssl/openssl/issues/8745

Okay, looks like changing the arch from arm64 to arm64 works fine. ;)


How to insert data?

Thank you in advance for your time.
I'm trying out your application to integrate into a biology project that I have.
I've already managed locally using your tutorial to get the application running, but I didn't understand how I input my data into the platform.
Can you help me?

The preferred option is to use the Germinate data templates. These are Excel spreadsheets for the main data types within Germinate. These can be imported into the database by either using a commandline tool or the Germinate web interface. Documentation on how to do this is still missing and needs to be written. Using the Germinate interface requires that you use Gatekeeper for user authentication, as we're only allowing data curators to add data into the database.
Another option for users with thorough understanding of the database design is to directly interact with the database using tools like DBeaver or Navicat, or using something like Germinate Daim, but this is probably not the option you'd want to start with.
I'd recommend looking into the data templates and trying to fit your data into the Excel files. There's documentation on how to do this and example files available in the GitHub repo.
I'll hopefully get a chance to write documentation about how to import the data templates into the database soon.

Thanks for the answers.
By the way, I read somewhere that Germinate can integrate with BRAPI.How do you integrate with BRAPI?
Do I have to integrate Geetkeeper to enter the data via Germinate client?

BrAPI support us currently under development for the new release of Germinate. It'll be a while before it's production ready.
What do you mean when you say "Germinate client"? The web interface? Then yes, you do need Gatekeeper if you want to upload the templates via the web interface.

BrAPI support us currently under development for the new release of Germinate. It'll be a while before it's production ready.
What do you mean when you say "Germinate client"? The web interface? Then yes, you do need Gatekeeper if you want to upload the templates via the web interface.

Thanks for the explanation.
Sorry to ask, but how do I install the gatekeeper-vue and the gatekeeper-server? Is there a procedure for the installation?

The process is pretty identical to Germinate. There are instructions here: https://germinateplatform.github.io/gatekeeper-server/

Thank you so much for your help.
I wasn't finding the website you indicated.
If you don't mind me saying, it'd be nice to stick that url in the github repository.
I'll try it and if you have any more questions I'll write.
Thanks again.


There is a lot of redundancy in the default pak file and the per-scene pak files generated by build_paks.py

I built SpearSim in the usual way and looked at the manifest of files that are stored in the default pak file, which is generated at path\to\UE_5.2\Engine\Programs\AutomationTool\Saved\ResponseFiles\PakList_SpearSim-Windows.txt on Windows. There are roughly 1000 seemingly redundant assets that are in the default pak file that would be also captured by the "allow" filters in build_paks.py. We should remove all of these redundant files to make our pak files smaller.

The command-line options we currently use for generating pak files deviate significantly from what you'd get by doing a usual build of SpearSim with the -pak option. build_paks.py should mimic the default way of generating pak files unless we have a good reason not to.