CRA Installs an old version of react-scripts and generates throws "The react-scripts version you're using is not compatible with the --template option."

UPDATE: I tried doing: yarn create react-app my-app --template typescript And it works fine. I think the issue has to do with linux and npm/npx.
Describe the bug
I have a fresh install of Ubuntu 20 and when I do
npx create-react-app my-app --template typescript
I get this error: The react-scripts version you're using is not compatible with the --template option.

I did control + C but if I let the script continue it creates the react app without typescript.
And my app is created with Javascript and no tsx files. I checked on the package.json generated by cra. And I see this:
{
"name": "my-app7",
"version": "0.1.0",
"private": true,
"dependencies": {
"react": "^18.0.0",
"react-dom": "^18.0.0",
"react-scripts": "0.9.5" <---- I THINK THE ISSUE IS RIGHT HERE
},
"devDependencies": {},
"scripts": {
"start": "react-scripts start",
"build": "react-scripts build",
"test": "react-scripts test --env=jsdom",
"eject": "react-scripts eject"
}
}
I did some research but I was not able to find how to specify the react-scripts version that cra should install. I tried also to create this app with a windows computer with same Node version and CRA 5.0.0 and It works fine. That's why I think it has to do with linux.
I have already checked with which that create-react-app is not installed globally. And I did the same with react-scripts.
Did you try recovering your dependencies?
Things that I did:

npm -g uninstall create-react-app react-scripts
Cleaning npm cache with
npm uninstall -g create-react-app && npm i -g npm@latest && sudo npm cache clean -f && npx create-react-app my-app --template typescript
Did npx create-react-app --version and I get 5.0.0
Did npx clear-npx-cache

With every single try I created a new app.
Environment
After running: npx create-react-app --info
current version of create-react-app: 5.0.0
running from /home/yari/.npm/_npx/24521/lib/node_modules/create-react-app
System:
OS: Linux 5.13 Ubuntu 20.04.4 LTS (Focal Fossa)
CPU: (24) x64 AMD Ryzen 9 5900X 12-Core Processor
Binaries:
Node: Not Found
Yarn: Not Found
npm: Not Found
Browsers:
Chrome: 100.0.4896.60
Firefox: 98.0.2
npmPackages:
react: Not Found
react-dom: Not Found
react-scripts: Not Found
npmGlobalPackages:
create-react-app: Not Found
Although it says I have no binary for node and npm I have them installed and working.

Node in /snap/bin/node
NPM in /snap/bin/npm

Steps to reproduce

npx create-react-app my-app --template typescript

Expected behavior
I want to get tsx files with Typescript applied.
Actual behavior
I get js files.

I have the same issue as @yaritaft . I'm using Ubuntu 20.04 LTS. npm cache clean, uninstall of CRA did not help. I'm using snap version of npm 8.5.5 and node 16.15.0.
yarn create react-app my-app --template typescript works

This is occurring because in packages/create-react-app/createReactApp.js, in the function checkNpmVersion(), execSync('npm --version').toString().trim() is returning an empty string, causing the subsequent semver.gte(npmVersion, '6.0.0') call to error out. Presumably, execSync() isn't executing with the npm snap on its path; notably, if npx create-react-app --info is run, under Binaries, Node and npm both display as "Not Found".
I can hack around this by doing the following:

npm install create-react-app
Editing node_modules/create-react-app/createReactApp.js to hardcode npmVersion to the correct number (8.17.0, in my case)
node ./node_modules/create-react-app/index.js, followed by normal CRA arguments

Thanks @VioletRose now it is working fine again npx with cra. I think it was fixed in newer versions ! If you still have the issue you can try an easier fix that is the one mentioned in my post (the yarn one)

I had the same issue. react-scripts 0.9.5 uses a very old version of webpack and I had lots of problem with generated bundle.js output file. It wasted my time. Finally I manually installed latest version of react-scripts and fixed all issues.

Node is unable to spawn some snap programs due to sandbox limitations.
thus as VioletRose noticed correctly, execSync does not return any data, since node cannot run the snap binary from within the sandbox.
meaning if node would be run by calling the true path of node /snap/node/6694/bin/node (in my case with current version) with npm location as arg (which npm) like this:
execSync('/snap/node/6694/bin/node $(which npm) --version').toString().trim() where $(where npm) returns the path of the npm binary, which in my case is not inside snap, but in /usr/local/bin/npm
output is the following:
> execSync('/snap/node/6694/bin/node $(which npm) --version').toString().trim()
'8.19.2'

the same problem, please fix it. yarn helped...

I got the same issue at Ubuntu 22.04 and tried nodeJS stable/edge snap versions. But if you install snap version, there is no easy solution with snap node installs.
On the other hand Ubuntu dep repo's nodeJS version is v12 and outdated.
I suggest that you can install deb or snap version and then set npm prefix to your local: npm config set prefix ~/.local.
Then install latest nodejs lts version as global in your user local: npm i -g node@lts
Finally update/installl npm as global in your user local: npm i -g npm
With these steps, you will install node and npm in your user local as global. You can check current node version and npm prefix:
which node -> like /home/YOUR_USERNAME/.local/bin/node
which npm -> like /home/YOUR_USERNAME/.local/bin/node
npm config get prefix -> like /home/YOUR_USERNAME/.local

Same problem


Issues with miniplayer while maximized in Linux

OS:
CentOS 7 64 bit
Gnome desktop
1980x1200 display.
NVIDIA GTX960 with propietary drivers (latest as of July 17 2016).
Issue Descriptions:
While the player is maximized, when enabling the miniplayer, this will show up with some glitching covering the whole area the maximized player used to cover, as if there was a void the miniplayer left.
Now that could be my display drivers, so I need confirmation about the glitching, but the main problem is:
when you can finally click on the button to go back to the normal player, the normal player will be zoomed in as if the screen was the size of the miniplayer. No way out of this. Also no way to close the player because it will minimize to tray, but it doesn't show in the gnome notification area. Must be killed with top.
Steps to Reproduce:
Start the player (If using system window border notice that there are no minimize or maximize buttons, only close. Double click on title bar to maximize.)
Now click in the bottom right corner to go to the miniplayer.
Miniplayer will show up while there is some glitching covering the whole screen where the full player used to be.
http://i.imgur.com/wB63d30.jpg
(The art work behind the miniplayer either flashes or stays on).
Attempt to click in the bottom right corner of the miniplayer to go to the full player.
Full player will appear zoomed in.
As in here http://i.imgur.com/JsdntiE.png
To prevent this, miniplayer must be opened while the player is NOT maximized, or the window must be restored (un maximized) BEFORE going back to the full player.
If anybody want's to throw me a bone on what should I know to attempt to fix this I'd appreciate it a lot, I'm trying to get myself involved in the project but my knowledge could (or could not) be limited.
Thanks!

This was fixed in Master in 3.3.0
What version are you running?

3.3.0

@nlabrad Can you set up the dev environment and add a new line here
https://github.com/MarshallOfSound/Google-Play-Music-Desktop-Player-UNOFFICIAL-/blob/master/src/inject/GPMWebView/interface/mini.js#L25
mainWindow.unmaximize()

And see if that fixes it

I'll try. Installing dependencies for the development environment now. Thanks.

I'm not sure whether or not @nlabrad got around to testing your fix. However I do notice that when maximized in windows and pressing the mini player causes the mini to show with the full height of the original maximized window (if not larger?). On linux what usually happened would be the miniplayer would stay "maximized" but the drawable area flashed between the new dimensions (300x300?) and the full screen size. I'll have to check if that's still happening in 3.3.0 on linux.

I did apply the fix, but brings another little nuisance. After going back to big the window doesn't resize to what it was.  There is a fix in the works.


Issue with typescript config

What version of this package are you using?
1.3.0
What operating system, Node.js, and npm version?
Macos, node - 12.4.0, npm- 6.9.0
What happened?
I've set in settings.json that config:
  "standard.validate": [
    "typescript",
    "typescriptreact"
  ],
  "javascript.validate.enable": false,
  "standard.autoFixOnSave": true

I've installed standards and parsers for typescript. I wanted to use standard.js with React and Typescript. But when I install this plugin, it shows me an error with 'interface' and 'type'.

What did you expect to happen?
I expected to not show this error.

@iiskaandar If you're using TypeScript, I recommand you to use ts-standard instead of the standard javascript.

This issue should be closed.


Feature Suggestion

Hi,
This module is cool - sometimes it isn't stats or a tree you want, it's just which files made it into the shipping bundle to make sure you are license compliant.
Now that everyone is going to be moving to angular-cli based projects, those break up the chunks into a standard set,  with vendor, and polyfills being the chunks that house third party content.
1.) How can I configure your plugin to read a configured set of chunks?
2.) Does this go into the N levels deep or just list the top level deps that landed in the chunk?
Thank you

I'm sorry but I do not have any experience with angular-cli and how the chunks are created.
This plugin should go as deep as needed to find the license files.


Cache key "ideasbucket_queue:restart" contains reserved characters {}()/@:

exception when running bin/console idb_queue:work
symfony 3.3

Is this specific to Symfony 3.3

yes, it is


Fix unsafe code

Visual Studio is complaining that some code like fopen is unsafe and deprecated claiming that fopen_s would be better. I can see that an attempt has been made to disable the warning but unfortunately it is still a lot of effort to really get it disabled. Is there any reason why the "unsafe" code has not been replaced with "safe" code yet?

fopen_sonly works on VS, not portable, and generally I don't see how it would be any safer than fopen.

@memononen Ok, I didn't realize that. Would it be fine if I just added "safe" versions as conditional code for VS because it seems that VS feels very strongly about this?

@memononen It seems that it actually became standard with C++11, or am I mistaken?

fopen_s is not part of any "official" c/c++ standard. It is Microsoft CRT only! See https://msdn.microsoft.com/en-us/library/8ef0s5kh.aspx.
The definition of _CRT_SECURE_NO_WARNINGS for source files disables these functions and "removes" them from the headers.

@Hockenberry I have actually found it easiest to just disable the "STL checks" in the properties of the source file in VS. I don't see that the MSDN article points out that the functions are MS only. What I have found though is that according to http://en.cppreference.com/w/c/io/fopen fopen_s was introduced into ISO C++ as of C++11 with their references pointing towards :
C11 standard (ISO/IEC 9899:2011):
<IP_ADDRESS> The fopen function (p: 305-306)
K.<IP_ADDRESS> The fopen_s function (p: 588-590)
If memory serves me correct though, support for C++11 has to be enabled by using a flag on GCC and is not supported by default even though GCC has support for C++11. As far as I know, most modern compilers have support for C++11 with many already having support for some of the proposed C++17 features.


Support updating tags for all RDS resources

Currently, all the RDS resources (DBParameterGroup, DBSecurityGroup, DBSubnetGroup, DBInstance, DBCluster, DBClusterParameterGroup) support tags on creation. However, there is no support for modifying those tags after creation.
Add support for the ListTagsForResource, AddTagsToResource and RemoveTagsFromResource API calls.

/remove-lifeycle stale

/remove-lifecycle stale

Does https://github.com/aws-controllers-k8s/rds-controller/pull/106 resolve this issue?

Does aws-controllers-k8s/rds-controller#106 resolve this issue?

yessir.


WireUpControls throws an exception

WireUpControls throws an exception:
System.MissingFieldException: Failed to wire up the Property CurrentFocus to a View in your layout with a corresponding identifier
But I have no view called CurrentFocus.
I think this commit caused it:
https://github.com/reactiveui/ReactiveUI/commit/276f96302a0ed9e444884dfa40f1cd5691ffd725
Example project with issue demo:
https://github.com/orzech85/ReactiveExample/blob/master/ReactiveUI.Droid/MainActivity.cs#L20

See #1231.


metamodel for late attributes

class Example() {
    shared late Integer i;
}
print(type(`Example.i`));

prints com.redhat.ceylon.compiler.java.runtime.metamodel::AppliedAttribute<example::Example,ceylon.language::Integer,Nothing>, so the Setter type parameter of Attribute is Nothing. This means I cannot call set() on the bound Value<Integer,Nothing> I obtain from that Attriibute.
If I try to use setIfAssignable() I get an exception "Value is not mutable".
This makes late attributes pretty much unusable from the metamodel.

Some way of assigning to non-variable late attributes will be necessary in order to implement dependency injection in Ceylon. Constructor injection isn't always an option.

And I suppose without ceylon/ceylon-compiler#2153, attribute-injection would be my preferred form of injection :).

Moving to 1.3.


Knife doesn't bootstrap properly on windows 64 bits.

This patch has been tested on windows 2008 64 bits and windows 2003 32 bits.

Thank you for supporting Chef! Our process has a couple prerequisites before we can merge your contribution. We need to ensure you've completed a Contributor License Agreement (CLA) and a ticket on our ticket tracker for the release workflow. Please take a moment to review the below wiki page for the appropriate steps:
http://wiki.opscode.com/display/chef/How+to+Contribute
The Opscode Team


First version of serializer

For now an astropy Table is used as only backend.
It can't save to table hierarchical containers and container with dictionaries inside.
It can be used also with with ... as (context management) syntax.
To test and try:
python example/serialization.py

Could you please explain why It can't save to table hierarchical containers and container with dictionaries inside ?
Could we use a Fits Binary tables to store serialized data with Pickle ?

Could we use a Fits Binary tables to store serialized data with Pickle ?

Please, no. What is the point of using a standardized file format to store data only readable by a certain program? We could then just pickle the complete object.

Close and replace by
PR #241


[No QA] Update Sage Intacct Connect + Configure docs with images

Explanation of Change

Fixed Issues

$ https://github.com/Expensify/App/issues/50430
PROPOSAL:
Tests

[ ] Verify that no errors appear in the JS console

Offline tests

QA Steps

// TODO: These must be filled out, or the issue title must include "[No QA]."

[ ] Verify that no errors appear in the JS console

PR Author Checklist
PR Author Checklist

[x] I linked the correct issue in the ### Fixed Issues section above
[x] I wrote clear testing steps that cover the changes made in this PR

[x] I added steps for local testing in the Tests section
[x] I added steps for the expected offline behavior in the Offline steps section
[x] I added steps for Staging and/or Production testing in the QA steps section
[x] I added steps to cover failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
[x] I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
[x] I tested this PR with a High Traffic account against the staging or production API to ensure there are no regressions (e.g. long loading states that impact usability).

[x] I included screenshots or videos for tests on all platforms
[x] I ran the tests on all platforms & verified they passed on:

[x] Android / native
[x] Android / Chrome
[x] iOS / native
[x] iOS / Safari
[x] MacOS / Chrome / Safari
[x] MacOS / Desktop

[x] I verified there are no console errors (if there's a console error not related to the PR, report it or open an issue for it to be fixed)
[x] I followed proper code patterns (see Reviewing the code)

[x] I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick)
[x] I verified that the left part of a conditional rendering a React component is a boolean and NOT a string, e.g. myBool && <MyComponent />.
[x] I verified that comments were added to code that is not self explanatory
[x] I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
[x] I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method

[x] If any non-english text was added/modified, I verified the translation was requested/reviewed in #expensify-open-source and it was approved by an internal Expensify engineer. Link to Slack message:

[x] I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
[x] I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is approved by marketing by adding the Waiting for Copy label for a copy review on the original GH to get the correct copy.
[x] I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
[x] I verified the JSDocs style guidelines (in STYLE.md) were followed

[x] If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
[x] I followed the guidelines as stated in the Review Guidelines
[x] I tested other components that can be impacted by my changes (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar are working as expected)
[x] I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
[x] I verified any variables that can be defined as constants (ie. in CONST.js or at the top of the file that uses the constant) are defined as such
[x] I verified that if a function's arguments changed that all usages have also been updated correctly
[x] If a new component is created I verified that:

[x] A similar component doesn't exist in the codebase
[x] All props are defined accurately and each prop has a /** comment above it */
[x] The file is named correctly
[x] The component has a clear name that is non-ambiguous and the purpose of the component can be inferred from the name alone
[x] The only data being stored in the state is data necessary for rendering and nothing else
[x] If we are not using the full Onyx data that we loaded, I've added the proper selector in order to ensure the component only re-renders when the data it is using changes
[x] For Class Components, any internal methods passed to components event handlers are bound to this properly so there are no scoping issues (i.e. for onClick={this.submit} the method this.submit should be bound to this in the constructor)
[x] Any internal methods bound to this are necessary to be bound (i.e. avoid this.submit = this.submit.bind(this); if this.submit is never passed to a component event handler like onClick)
[x] All JSX used for rendering exists in the render method
[x] The component has the minimum amount of code necessary for its purpose, and it is broken down into smaller components in order to separate concerns and functions

[x] If any new file was added I verified that:

[x] The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory

[x] If a new CSS style is added I verified that:

[x] A similar style doesn't already exist
[x] The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(themeColors.componentBG))

[x] If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
[x] If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
[x] If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
[x] If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
[x] If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
[x] If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.
[x] I have checked off every checkbox in the PR author checklist, including those that don't apply to this PR.

Screenshots/Videos

Android: Native

Android: mWeb Chrome

iOS: Native

iOS: mWeb Safari

MacOS: Chrome / Safari

MacOS: Desktop

A preview of your ExpensifyHelp changes have been deployed to https://928cab5b.helpdot.pages.dev ⚡

Thanks, @neil-marcellini! I'll go through my urgent Concierge tasks this morning and see if I can work through your comments this afternoon.

Ok! I've just tried the 8 spaces formatting suggestion! Is it possible to regenerate the preview link?

Cool. I kicked off the workflow for that, it should post here again soon.

Oh darn it! I misunderstood and thought the indentations were required for all of the images 🤦
Ok, I'll go back through and clean the indents up. Thanks!

Ok! I think I've understood what I did wrong and what I needed to do to fix it.
For starters, it sounds like there was one image that was broken, because it needed to be indented to match the indentation of the list it was included in. I misunderstood and indented every image. I've now un-indented the images that should never have been indented in the first place.
Fingers crossed these are the last edits 🤞

@neil-marcellini can you re-run the workflow above so I can preview the changes?

Cool. Sure I kicked it off here https://github.com/Expensify/App/actions/runs/12126383519

https://b58214f4.helpdot.pages.dev/

An updated preview will deploy here https://github.com/Expensify/App/actions/runs/12145891367

Merged with failing checklists since this is a help site change only


[HUDI-5199] Fixed HoodieParquetDataBlock failed to read data when schema evolutio…

Change Logs
Fixed HoodieParquetDataBlock failed to read data when schema evolution was enabled
Impact
Helps the user avoid causing an exception
Risk level (write none, low medium or high below)
low
Documentation Update
N/A
Contributor's checklist

[ ] Read through contributor's guide
[ ] Change Logs and Impact were stated clearly
[ ] Adequate tests were added if applicable
[ ] CI passed

@xiarixiaoyao Could you please help me review the code?

@shangwen
thanks for the fix
Looks good,
Pls add some UT to case this fix， thanks

cc @xushiyan， @xiarixiaoyao

waiting for ci pass

hi @xiarixiaoyao , it looks like Test Call rollback_to_savepoint Procedure test case fails, not related to my test case

@hudi-bot run azure


Build Tasks using msbuild should have support to VS CODE

Hi guys, build tasks are configured using msbuild in project like this:

Note: I modified the original source to use yarn and not npm.
In the wiki or readme I think you should have a tasks.json with the msbuild tasks equivalent for people that uses VS CODE IDE. Could somebody please help me with that ?

I also think that its useful (at least for me sometimes) to have a task named clean in msbuild in the templates like this:

So if you wanna clean your project you also clean the webpack "compiled" files.
And i think is good idea to add it to the templates .....
Thanks for reading me

After looking for a solution over the web ... I Found that You can reuse the msbuild options ,  stored in the csproj file ....


mypy annotation and constrained lists recommendation

Question
Please complete:

OS: Debian 10 (python:3.7-slim Docker image)
Python version: 3.7.5
Pydantic version 0.32.2

Hello!  I'm hoping to find the best practice for the interaction between mypy checks and the ConstrainedList/conlist() pydantic types.   For the MWE below, we're expecting a BaseModel taking a fixed-length list of floats (this is used as a request body in FastAPI):
from pydantic import BaseModel, conlist

class EmbeddingRequest(BaseModel):
    embedding: conlist(float, min_items=100, max_items=100)

which behaves as expected, but complains when run through mypy checks (same error as in the older #239 issue).  From #862 it sounds like it's still on deck to add improvements to documentation for mypy+constrained types, so hopefully this can help.  Alternately, I suppose this might be something that is resolved in v1.0/1.1 - for the time being I'm pinned to 0.32.2 for FastAPI compatibility, but I doubt that will last long.
Older issues propose a few options:
option 1
per #239,
from typing import List, Type
from pydantic import BaseModel, conlist

Vector: Type[List[float]] = conlist(float, min_items=100, max_items=100)

class EmbeddingRequest(BaseModel):
    embedding: Vector

runs, but complains that Vector is not valid as a type (and defining it as type ConstrainedList rather than List[float] per #156 fails for type mismatch).
option 2
also in #239 , explicitly subclassing the type
from pydantic import BaseModel, ConstrainedList

class Vector(ConstrainedList):
    item_type = float
    min_items = 100
    max_items = 100
    __args__ = [float]

class EmbeddingRequest(BaseModel):
    embedding: Vector

functions properly and passes mypy, but forcing the explicit __args__ overloading for it to behave properly relative to conlist() feels evil to me.
option 3
just punt and add a type: ignore flag on the original conlist call.
Any advice on this would be much appreciated!

What happens with option 2, but removing __args__ = [float] and then use Vector[float]?

oh, that probably doesn't work but would be the best solution,
The other thing to do is
from typing import TYPE_CHECKING

if TYPE_CHECKING:
    Vector = List[float]
else:
    Vector = conlist(float, min_items=100, max_items=100)

or something.

yeah Vector[float] throws a type error - 'type' object is not subscriptable

Best to do
from typing import List
from pydantic import BaseModel, Field

class EmbeddingRequest(BaseModel):
    embedding: List[float] = Field(..., min_items=100, max_items=100)

EmbeddingRequest(embedding=list(range(100)))

We could perhaps allow paramaterising of ConstrainedList as per my suggestion in future?

Import cycling on TYPE_CHECKING worked, but I imagine a more stable solution is desirable.
That Field functionality is new in v1.0, right?  That's a breaking change for FastAPI (though it's slated for a fix) so that won't work for the time being.  Can get the equivalent functionality with pydantic.Schema in the older version but mypy doesn't like it.
It sounds like the play is to use the shim with import cycling until FastAPI supports pydantic>=1.0.0, then use the Field type which should give the cleanest solution.  I do really like the idea of parameterized ConstrainedList as a way to define constrained types in a way that feels very consistent with the rest of typing's behavior.

Yup, Field() is the best solution as of v1. As well as changing the name in v1 we made Field a function with return type Any to avoid mypy complaining.
I'd be happy to accept a PR to implement parameterized ConstrainedList.

rad, I'll start taking a crack at that!

Some remarks regarding conlist:

the __args__ thing was a mistake in hindsight. I didn't realize at the time that the class would be use directly. But is is probably easy to modify the code to set __args__ from item_type..

We currently have something like this:
class InstanceListMeta(type):
    """Metaclass allow for easier creating constrained lists.

    All this code should be removed once pydantic has a nicer interface for contrained lists
    """

    def __new__(metacls: Type[T], name: str, bases: Tuple[type, ...], namespace: Dict[str, Any], **kwds: Any,) -> T:
        if "__args__" not in namespace and "item_type" in namespace:
            namespace["__args__"] = [namespace["item_type"]]
        return super().__new__(metacls, name, bases, namespace)  # type: ignore

class InstanceList(ConstrainedList, metaclass=InstanceListMeta):
    pass

I could not get a properly parameterized conlist to work in combination with cython. But given that a lot has changed since then it might just work now. I would welcome it since we run into the same issues..

Hmmm just using this will also work on python >3.6
class InstanceList(ConstrainedList):
    def __init_subclass__(cls, **kwargs):
        super().__init_subclass__(**kwargs)
        cls.__args__ = [cls.item_type]

the Field solution is not sufficient using FastAPI, as those can only be used for bodies, not query strings:
AssertionError: Param: [name] can only be a request body, using Body(...)

@AngryUbuntuNerd there's a good chance the fastapi.Query construct would provide sufficient validation, what exactly are you trying to do?

Hi everyone
Does something like https://github.com/samuelcolvin/pydantic/pull/2553 sound like a good solution to you?
The goal is to leverage Annotated instead of struggling with Generic or dynamic types

If you (as I'm) don't get what does it means: "With the new Annotated syntax, it should now be possible to make it work properly"
In Python 3.9+:
class _Artist(pydantic.BaseModel):
    image: typing.Annotated[list, pydantic.conlist(_Image, min_items=5, max_items=5)]

Thanks, @rustam-python, but unfortunately this approach skips any validation. For example:
from typing import Annotated
from pydantic import BaseModel, confloat

# mypy likes this
class ProbabilityAnnotated(BaseModel):
    p: Annotated[float, confloat(ge=0, le=1)]

# mypy doesn't like this
class Probability(BaseModel):
    p: confloat(ge=0, le=1)

# this doesn't throw an error
pa = ProbabilityAnnotated(p=10)

# this throws an error
p = Probability(p=10)

Bump, issue reproduced with genos' code
Python 3.10.5
pydantic==1.9.1
mypy==0.961
mypy-extensions==0.4.3

It seems @genos code did not work because the Annotated was malformed.
The syntax is verbose, conlist is much cleaner and concise. Hopefully the mypy plugin can fix this in the future to avoid such clutter?
Python 3.10.6
pydantic==1.10.2
mypy==0.971
mypy-extensions==0.4.3
from typing import Annotated
from pydantic import BaseModel, Field, conlist

# mypy likes this
class VectorAnnotated(BaseModel):
    xs: Annotated[list[str], Field(min_items=1, max_items=5)]
# mypy doesn't like this
class Vector(BaseModel):
    xs: conlist(float, min_items=1, max_items=5)
# this now throws an error!
va = VectorAnnotated(xs=[float(x) for x in range(10)])
# this throws an error
v = Vector(xs=[float(x) for x in range(10)])

Based on syntax I found in this comment.

@holocronweaver it seems there is a mistake in your example because the field in VectorAnnotated is for a list of str, and in Vector it is a list of float

@glarrain-cdd Updated, though this doesn't change the output with the versions listed, which fail on item count rather than type.


Do not allow deleting currently logged in user

Do not show the link of Delete against currently logged in user in manage collaborator

@kshijiD The fix was overridden by your PR #340 . Minor changes, please fix it asap.

Fixed it.  Also made the Manage Collaborator code in backbone style.


docker-machine creation fails in subprojects like eu-de_test1

(ansibleenv) ubuntu@tino-dev2:~$ openstack --os-cloud otc project list
+----------------------------------+-------------------------+
| ID                               | Name                    |
+----------------------------------+-------------------------+
| d380837226214dfd87_shortened | eu-de_test1               |
| 16d53a84a13b49529d_shortened | eu-de                        |
+----------------------------------+-------------------------+

In eu-de it is working
In eu-de_test it is not working
Error 1)
(dockermachine-3) DBG | subnets:[] response code:400 error info:{VPC.0007 urlTenantId is not equal tokenTenantId.}
Error 2)
Error creating machine: Error in driver during machine creation: dockermachine-3 | Failed to crate ssh key pair: unknown error, status code: 400, err: { }
notifying bugsnag: [Error creating machine: Error in driver during machine creation: dockermachine-3 | Failed to crate ssh key pair: unknown error, status code: 400, err: { }]

I fixed it here:
https://github.com/AdamVB/DockerMachineDriver4OTC/commit/9ef3aa38e7e0e99d267a6ac1bf4a9fa6377d998d

https://github.com/Huawei/DockerMachineDriver4OTC/pull/29


[BEAM-7512] Replace deprecated self.assertEquals with self.assertEqual

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

[ ] Choose reviewer(s) and mention them in a comment (R: @username).
[ ] Format the pull request title like [BEAM-XXX] Fixes bug in ApproximateQuantiles, where you replace BEAM-XXX with the appropriate JIRA issue, if applicable. This will automatically link the pull request to the issue.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

R: @youngoli @tvalentyn
CC: @boyuanzz

cc: @laschmidt


[Launcher] Fluent UX: predictive text goes through the search icon

I think we should let the text stop before the search icon with a nice padding.

@crutkas Do we need an X button to clear the textbox? If the expected behavior is that the textbox will be empty always I don't think that's needed.

box would either be selected or empty by default so i don't think we'd need an X


Add ArcGIS Pro to CF Software List

Hi all - I think this is mergeable. Just added a few reviewers for a double check before merging.
Thanks!


ASE: Refactoring 3 -- Removed redundant buffer definition of wsmeta_t in app_backend.c

Removed redundant buffer definition of wsmeta_t in app_backend.c  for MMIO and UMAS buffers, fixed some memory leak issues related to buffers, and changed some global variables to be local variables.
Passed regression tests on Linux with VCS.

I enabled "#define ASE_DEBUG 1 " at the beginning of ase_common.h , and hello_fpga test still passes. We should merge this changes today.

@lzhan55  ASE_DEBUG is used to debug ASE ,if an error occurs. It is not used for Validation of ASE .

I suggest waiting till the CI infrastructure is completely regressing the code.

What else is needed for CI infrastructure enabling? To enable CI to automatically do regression tests on branches? Nakul sent an email yesterday saying that CI is ready now.

@lzhan55 If Jenkins has passed the test and if the DCP tests pass , you are good to go . Please check with Modelsim 32 bit and 64bit on your end .

@lzhan55 CI infrastructure checks for VCS simulation with different AFU's . It doesnt check Modelsim . Developer is needed to check for this on his end , till it gets enabled on the CI.

Full DCP run: http://sw-pert.altera.com/pert/pert.php?test_run_id=2050289
Looks good. There are few failures due to infrastructure issues.

ASE: Removed redundant buffer definition of wsmeta_t in app_backend.c

Replaced struct wsmeta_t list with struct buffer_t in app_backend.c to make it consistant with simulator side buffer list
Fixed buffer_t memory leak issue at app_backend.c
Changed some global variables to local variables in protocol_backend.c


related

v1:

https://www.npmjs.com/package/freshdesk
https://www.npmjs.com/package/freshdesknode

v2:

this https://www.npmjs.com/package/node-freshdesk-api
https://www.npmjs.com/package/freshdesk-nodejs
https://www.npmjs.com/package/freshdesk-sdk

and there are several packages about freshdesk SDK

seems like some of them are hardly maintained though

Most of repositories have 3-5 commits, and very limited set of implemented functions. Sometimes - without documentation.

Note for self:

https://github.com/arjunkomath/node-freshdesk-api
https://docs.npmjs.com/cli/unpublish
https://docs.npmjs.com/cli/deprecate

README:
This repository and NPM package are deprecated in favor of:

NPM: https://www.npmjs.com/package/freshdesk-api
GITHUB: https://github.com/arjunkomath/node-freshdesk-api

note for self:
npm install freshdesk-api@APIv1
npm deprecate freshdesk-api@"< 2.0.0" "Please, upgrade to<EMAIL_ADDRESS>

WARNING

This repository and corresponding NPM package are deprecated in favor of freshdesk-api.
Useful links:

NPM package:

v2 preferred: npm install freshdesk-api
v1: npm install freshdesk-api@APIv1

GitHub, node-freshdesk-api:

v2 on master branch
v1 in additional branch

Instructions:
Hello, I would like to offer you to take part in this open source, github-based freshdesk-project: https://github.com/arjunkomath/node-freshdesk-api . I'am sure, this project could be a good alternative for your project.
So, if you are not going to maintain your project in the future:

Merge this PR to your repo
Deprecate old NPM package, with this command:npm deprecate <YOUR-PACKAGE-NAME> "Please, use this package: freshdesk-api"

Don't unpublish your package, it is enough to deprecate it :+1:


Consider supporting fromisoformat as the default datetime parser

The current parser for datetime in file names uses the following format "%Y-%m-%d_%H-%M-%S"
https://github.com/AllenNeuralDynamics/aind-data-schema-models/blob/412736e4588b1e2232c655da18b3f941f28f92ff/src/aind_data_schema_models/data_name_patterns.py#L53
More documentation on this choice is available here. However, reading the document I found at least 4 instances of different standards (some of which are compatible with ISO8061 which is confusing from my perspective).
This format does not conform to ISO8061 conventions since, as per the  ISO:
3.2.6   Separator symbols
In date and time expressions and date and time representations, the following characters are used as separators.
“-” (hyphen)	the “-” hyphen character, in extended format, separates the time scale components for “year” and “month”, “year” and “week”, “year” and “day”, “month” and “day”, and “week” and “day”.
“:” (colon)	the “:” colon character, in extended format, seperates the time scale components for “hour” and “minute”, and “minute” and “second”.

I understand the intentions behind this choice since ":" is probably a difficult character to support (e.g. not allowed in paths).
However, using a custom parser ensures that users have to rely on this library to parse their datetimes. Instead, I propose we support the ISO8601 format by relying on the stdlib datetime.datetime.fromisoformat method. E.g.:
import datetime

tz_not_iso = "2022-04-26_11-48-09"
tz_proposed = "2022-04-26T114809"

print(datetime.datetime.fromisoformat(tz_proposed))
# 2022-04-26 11:48:09
print(datetime.datetime.fromisoformat(tz_not_iso))
# Throws error ValueError: Invalid isoformat string: '2022-04-26_11-48-09'

(I should point out that the string that I am using is not necessarily ISO8061 compliant since it mixes the compact with the extended format, I would prefer to not use "-" at all for the date portion, but people usually like to have it for readability and python seems to consider it ISO compliant, so....)
Having this implemented would allow users to use datetimes that are ISO8061 compliant instead of being forced to use the current non-ISO format.
The idea would be to modify the aforementioned parser method to have try-catch routine that uses the fromisoformat as default and falls back on the current parser to ensure backward compatiblity.
Finally, I would encourage people to use the format that is laid out on this PR where feedback for the current datetime format is being discussed.

@dbirman @saskiad we should consider this for 2.0


PHP 7.2 and EntityRepository::find signature mismatch

<?php

namespace Doctrine\Common\Persistence {
    interface ObjectRepository
    {
        public function find($id);
    }
}

namespace Doctrine\ORM {

    use Doctrine\Common\Persistence\ObjectRepository;

    class EntityRepository implements ObjectRepository
    {
        public function find($id, $lockMode = null, $lockVersion = null) {}
    }
}

namespace {

    use Doctrine\ORM\EntityRepository;

    class MyRepository extends EntityRepository
    {
        public function find($id) {}
    }
}

Fatal error: Declaration of MyRepository::find($id) must be compatible with Doctrine\ORM\EntityRepository::find($id, $lockMode = NULL, $lockVersion = NULL) in /in/2akM2 on line 24

Runnable: https://3v4l.org/2akM2
I think this is a bug in PHP 7.2 and if not, I can't see it mentioned anywhere in changelogs etc, but I thought it might be worth tracking here. Someone else has reported it to PHP: https://bugs.php.net/bug.php?id=75590

This is not a bug in Doctrine and this isn't a bug in PHP either. Your code violates LSP so you are correctly warned about it. I don't think this could even be called BC break as it is obvious bug in user code and also code smell.
I suppose it may be related to Type Widening RFC but I may be wrong.

FYI: PHP bug was closed as Not a bug for exactly the same reason I gave here: LSP violation, fixed in 7.2.


Can't use the tools.

Hello, I've been using Metroframework for awhile now and I love it. When i open visual studio and make a new project I get the Form to show Metroframework style but I can'r use most of the tools like MetroTab and others. I could use them before and I've tried to reinstall Metroframework and do it again but it always ends up doing this. It done it on my old computer and now I have this computer and Metroframework worked great but now it won't let me use most of the tools. Thanks for your help

I also have this same problem. When I drag the metro framework controls onto a form, they do not render and I cannot position them. The only way I can get them to display on the form is to programatically add the controls onto the form, and even then, a lot of the controls such as the tabbedcontrol cannot be interacted with. This used to work on my old PC too. I'm using Visual Studio 2015. I've tried downgrading to Visual Studio 2013 with no success.
Here is what happens when I drag, say, a metro button onto the form:

It just goes to the bottom of the display manager.
Can someone please help?

Currently, the only controls that actually do work as expected for me are:

HtmlLabel
HtmlPanel
MetroComboBox
MetroContextMenu
MetroDateTime
MetroGrid
MetroPanel
MetroTrackBar
MetroUserControl

Nothing else works.

Okay i have same problem but it weid. I can add controls to other forms and SOMETIMES to form that i want to add them to, but after some time all controls just mess up and it ends up being like this

I cant move them either.


add more tips for PR reviews

Added some things I've learned about PR reviews.
Let me know your thoughts. Happy to discuss/remove/change things.

Maybe we can add something about target pull request sizes?

Maybe we can add something about target pull request sizes?

We actually already have something for that under Project Delivery Metrics but perhaps a link to that somewhere pertinent?

@jalada is this good to merge now?

Do it!


Automated cherry pick of #1100: gpfs

Cherry pick of #1100 on release/2.9.0.
#1100: gpfs

Codecov Report

:exclamation: No coverage uploaded for pull request base (release/2.9.0@086fa0d). Click here to learn what that means.
The diff coverage is 0%.

@@               Coverage Diff               @@
##             release/2.9.0   #1102   +/-   ##
===============================================
  Coverage                 ?   7.65%
===============================================
  Files                    ?     334
  Lines                    ?   53725
  Branches                 ?       0
===============================================
  Hits                     ?    4115
  Misses                   ?   49230
  Partials                 ?     380

Flag
Coverage Δ

#aFlag
7.65% <0%> (?)

Impacted Files
Coverage Δ

pkg/cloudcommon/db/opslog.go
1.6% <ø> (ø)

pkg/compute/models/storages.go
1.12% <0%> (ø)

pkg/compute/models/disks.go
0.72% <0%> (ø)

pkg/compute/models/guests.go
0.66% <0%> (ø)

pkg/compute/models/hosts.go
0.36% <0%> (ø)

pkg/cloudcommon/cmdline/parser.go
38.77% <0%> (ø)

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 086fa0d...ab4d92f. Read the comment docs.

/lgtm
/approve


Implement Cashflow Schedule Generation in Time Module for Pricing Models and Instruments

Currently, RustQuant lacks a robust mechanism to generate cashflow schedules that can be utilized in conjunction with pricing models and financial instruments. This functionality is essential for accurately pricing a wide range of financial products, such as bonds, options, and swaps. The absence of this feature makes it challenging to perform comprehensive pricing and risk management.
I propose implementing a schedule generation feature within the time module. This feature will enable the creation of cashflow schedules based on specified parameters such as start date, end date, frequency, and conventions (day counting and date rolling). The generated schedules will integrate seamlessly with existing models and instruments, facilitating accurate pricing and valuation.
Describe alternatives:

Manually inputting cashflow dates for each instrument, which is time-consuming and error-prone.
Using external libraries for schedule generation, which might not align perfectly with RustQuant's architecture and conventions.

Additional context:
The implementation will involve:

Creating functions to generate schedules based on input parameters (start date, end date, frequency, etc.).
Ensuring compatibility with date rolling conventions and day counting conventions.
Adding unit tests to validate the correctness of the generated schedules.
Document the new functionality and provide examples of usage.

This enhancement will significantly improve RustQuant's ability to handle a variety of financial instruments and streamline the pricing and risk assessment process.

This test is failing:

    // Test for non-matching dates during addition (should panic).
    #[test]
    #[should_panic(expected = "Dates must match.")]
    fn test_non_matching_dates_add() {
        let date1 = OffsetDateTime::now_utc();
        let date2 = date1 + Duration::days(1);
        let cf1 = SimpleCashflow::new(100.0, date1);
        let cf2 = SimpleCashflow::new(50.0, date2);
        let _ = cf1 + cf2;
    }

    ```

    Due the comparison among self.date and rhs.date is not working

    ```rust

    impl std::ops::Add for SimpleCashflow {
    type Output = Self;

    fn add(self, rhs: Self) -> Self::Output {
        assert_eq!(self.date, rhs.date, "Dates must match.");
        Self {
            amount: self.amount + rhs.amount,
            date: self.date,
        }
    }
}

Steps to Reproduce
Run the test test_non_matching_dates_add in the test suite.
Observe the test failing due to the assert_eq!(self.date, rhs.date, "Dates must match."); not working correctly.
Expected Behavior
The test should pass by panicking with the message "Dates must match." when self.date and rhs.date are not equal.
Environment
Rust version: 1.79.0
time crate version: v0.3.34
Possible Solution
Ensure that the OffsetDateTime comparison is correctly implemented or consider an alternative approach for comparing dates within the SimpleCashflow struct.

Hi, the test passes for me.
Can you make a new issue with the error output ?


New signals

Summary
Prototype of new signals for discussion. Currently just doing things in a new file new_signals.py and trying out functionality in new_signals.ipynb.
Design Motivation
The design is motivated by the following considerations:

Basic element for a "signal" is a time-dependent function fo the form s(t) = Re[f(t)exp(i(2 * pi * v * t + phi))].

f(t) is a complex envelope, and v and phi are floats giving carrier frequency and phase.
Common representation for hand-written analysis; used for common model transformations like RWA.
Corresponds directly to how a pulse is defined in Pulse.

Want algebraic operations on signals (add/multiply), while preserving frequency information.

E.g. IQ-mixers involve multiplying and summing signals, producing components of signals centred at various frequencies.

Design simultaneous facilitates very general and very efficient implementations

A user should be able to supply an arbitrary envelope as a Callable. Algebraic operations treat this is a black-box function.
Alternatively, a user can specify a piecewise constant signal. These are internally represented as arrays of samples, and where possible, algebraic operations will operate directly on these arrays.

All signal evaluation should be vectorized.

Design
Classes
Basic signal classes

Signal

Specified via arbitrary Callable envelope, carrier frequency, and phase
Main methods:

envelope(t) - Vectorized evaluation of the complex envelope
complex_value(t) - Vectorized evaluation of f(t)exp(i(2 * pi * v * t + phi))
__call__(t) - Vectorized evaluation of Re[f(t)exp(i(2 * pi * v * t + phi))]
conjugate() - Return the signal with the complex conjugate of f(t) and phase -phi
plot, plot_envelope, plot_complex_value - plotting functions

Main attributes:

carrier_freq - returns carrier freq
phase - returns phase

This class also contains dunder methods for algebraic operations, to be discussed later

PiecewiseConstant(Signal)

Signal whose envelope is specified by dt, start_time, and samples
Evaluation functions are based on array look-ups
Additional attributes:

dt, start_time, samples

Constant(Signal)

Signal with zero frequency and phrase, taking a constant value.
This is useful for unified treatment of all coefficients in a model (whether a proper time-varying signal or a constant).

Aggregate signal class:

SignalSum(Signal)

Class representing a sum of any subclass of Signal (aside from SignalSum itself).
Evaluation functions are modified naturally for a "sum":

envelope returns an array for each component in the sum for every time
complex_value and __call__ return the sum of all signals in the sum.

Additional methods:

__getitem__(idx) - returns the signal at the idx location in the sum
__len__ - number of terms in the sum
simplify and merge - discussed later

Additional attributes:

components - storage of the list signals in the sum.

Algebraic operations
Algebraic operations are implemented via dunder methods in the base Signal class:

__add__, __radd__, __mul__, __rmul__, __neg__, __sub__, and __rsub__
Where relevant, the above operations also work with scalars (they get wrapped in Constants)
Addition is implemented via direct construction of a SignalSum object

If one (or both) of the signals being added together are a SignalSum, they will be appropriately unrolled.

Multiplication is performed by constructing a SignalSum via the relation:

Re[f(t)exp(i(wt + phi))] * Re[g(t)exp(i(vt + psi))] =
Re[0.5 *f(t)g(t)exp(i( (w+v)t + (phi + psi)))] + Re[0.5 *f(t)conj(g(t))exp(i( (w-v)t + (phi - psi)))]
The above relation works for SignalSums by performing the above operation for all pairs in the sums (distributivity of multiplication over sums).

Multiplication of envelopes: the above formula involves multiplication of envelopes. Where possible, special rules apply: E.g. constants are multiplied by just multiplying their values. If compatible (based on start_time, dt, and number of samples), piecewise constants are multiplied by multiplying their sample arrays. If no special rules applied, the envelopes are multiplied as functions (e.g. any multiplication involving a generic Signal.)

Simplifying SignalSum objects
Algebraic operations result in collections of Signal objects. It would be natural, e.g. for a SignalSum containing only Constants, to merge them into a single constant. More generally, when doing things like modelling IQ mixers or doing RWA, we may wish to simplify sums containing terms with the same frequency. The SignalSum.simplify() method implements this:

The default behaviour is to only attempt to merge terms of the same type with the same carrier frequency. E.g.:

Constants get merged by adding the values.
PiecewiseConstants of the same frequency with the same sample structure get merged into a single PiecewiseConstant by adding the sample arrays
Signals with the same frequency get added together via function addition of the envelopes

Optional argument: combine_types=True forces merging of all terms with the same carrier frequency, regardless of type.

Another form of "simplification" in SignalSum is collapse():

Returns a single non-SignalSum Signal object  that implements the sum.
This averages frequencies of all components.
Due to the non-preservation of frequency information, I don't expect this function to get used much. However, it will be useful initially before models/model transformations are updated to properly work with SignalSum.

Efficiency and sample-based computation
As mentioned, where possible, signals use sample-array based computations to implement multiplication and sum simplification. Hence, for high performance applications, if a user wants these operations to be performed in this way, they just need to make sure to define their signals as PiecewiseConstants with consistent sample structure. (We can definitely make the consistency checks a bit more general too.)
This is less developed, but this PR also contains a PiecewiseConstantSignalSum object (rename?):

Same as SignalSum but exclusively for storing a sum of PiecewiseConstants with compatible sample structure.
Stores an auxiliary sample array with all samples, and all envelopes can be evaluated simultaneously by look ups in this array.

To do
While evaluating this design, we also need:

implement sampling of arbitrary signals (just bring to_pwc over, but implement with vectorized envelope evaluation).
Implement sampling of SignalSums to create PiecewiseConstantSignalSum objects.
Demo some transformations implemented with this, primarily: IQ Mixer and filters.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

Going to remake this PR as a draft - forgot to make it a draft initially, but tests are still being run after changing it to a draft.


How can I use this model to predict my dataset?

I want to use the model you have built to predict the answer in my dataset.
The content in the file, "dev-v1.1.json", is shown belowed.
{"data": [{"title": "winograd", "paragraphs": [{"context": "If thing A doesn't fit into thing B, A is big and B is small. The trophy doesn't fit into the brown suitcase.", "qas": [{"answers": [{"answer_start": 67, "text": "trophy"}, {"answer_start": 67, "text": "trophy"}, {"answer_start": 67, "text": "trophy"}], "question": "What is big?", "id": "5737aafd1c456719005744ff"}]}]}], "version": "1.1"}
When I use the command, "python parse_data.py data/dev-v1.1.json --outfile data/dev_parsed.json"
I get this file and the content in the file is shown belowed.
[{"answer_start": 67, "question": "What is big?", "topic": "winograd", "context": "If thing A doesn't fit into thing B, A is big and B is small. The trophy doesn't fit into the brown suitcase.", "answer": "trophy", "id": "5737aafd1c456719005744ff", "answer_end": 72}]
And then I use the command "python preprocessing.py data/dev_parsed.json --outfile data/dev_data_str.pkl --include_str". I get a file with six bytes.
At last, I use the command "python predict.py --batch_size 100 --dev_data data/dev_data_str.pkl models/31-t3.05458271443-v3.27696280528.model prediction.json".
I get this error.
Traceback (most recent call last):   File "predict.py", line 44, in <module>     char_level_embeddings = len(dev_data[0]) is 4 IndexError: list index out of range
My pkl file has the size of six bytes, but why dev_data is empty?
How to fix this problem?
Thanks!

Sorry for late response,
What Keras version do you use?


Update documentation and versions, trigger tests for newer versions

Description of changes:

updated microk8s version to the latest release
added (identical) tests for newer Ubuntu versions
updated documentation

Note: I've tried to run Travis build on my branch but it fails for some reason. The same happens also on build from master, without my changes

btw, I've successfully deployed the following
    - role: istvano.microk8s
      vars:
        registry_size: 40Gi
        microk8s_version: "1.27/stable"
        microk8s_plugins:
#          dns: "<IP_ADDRESS>"
#          istio: true
#          ingress: true
          fluentd: true
          prometheus: true
          portainer: true

to ubuntu 22.04 running on Oracle Cloud


Added some basic tests

R: @jeffposnick @jakearchibald
I never found a satisfactory way of running the tests in the worker, but hopefully this will work.
Doesn't currently cover all features, but some is better than none.

Thanks for writing tests! They look good in general.
My main piece of feedback is that the tests would be more useful if they could be automated via some sort of runner, which was then tied in to the release process. I've had good luck using selenium to test the <platinum-sw> elements in supported browsers via the web-component-tester framework, and maybe that's something you could borrow (without all the web component-y bits).
I don't think that needs to block merging this PR, but automation could be a future enhancement.

Definitely agree about automation! I'd love to run this through Travis. I've opened a separate issue for that (#15).
Will resolve the other issues.

My main piece of feedback is that the tests would be more useful if they could be automated via some sort of runner, which was then tied in to the release process.

@jeffposnick are you familiar with our Polymer CI runner? http://polymerlabs.github.io/ci-runner/#!/PolymerElements/iron-a11y-keys/1ab9e69aff38a8712dffdfe6749a6d83fcab9e84
One of the benefits is that it's able to run your WCT tests through CI each time a PR comes in, which can be handy for making sure your tests aren't breaking with new patches coming through.

@addyosmani Yep, I am! It would be awesome if Mat could move towards something like that, though WCT as-is might not be an option, since his tests are QUnit-based and he doesn't have a web component.
I'm not entirely happy with the sw-precache approach, but it's another option—I use mocha to test the behavior of various JS helper methods, but don't test the actual service worker in-browser behavior.

@jeffposnick PTAL

Not sure if you're opposed to pulling in QUnit as a local dependency or if you just missed that comment. If you'd rather continue using the CDN version, that's fine too, and feel free to merge.

My two cents are a local dep for QUnit would make sense here, but if the CDN version is preferable and we intend to move over to something else long term anyway, that also sgtm.
PR itself LGTM.

Sorry, actually missed the qunit comment first time around. Have brought it in locally. Will merge, but feel free to check over the latest commit :)

:+1:


Fields of type Array cannot be assigned nil after their value is set

require "spec_helper"

class Foo
  include Mongoid::Document
  field :range, type: Array
end

describe "Mongoid::Document" do

  before do
    [ Foo ].each(&:delete_all)
  end

  describe "field" do

    let(:foo) do
      Foo.new
    end

    it "saves the relationship" do
      foo.range = [1000.0, 1000.0]
      foo.save! # works
      foo.range = nil
      foo.save! # fails
    end

  end

end

You get an unhelpful error.
     Failure/Error: foo.save!
     NoMethodError:
       undefined method `-' for nil:NilClass
     # ./lib/mongoid/dirty.rb:120:in `block (2 levels) in setters'
     # ./lib/mongoid/dirty.rb:114:in `each_pair'
     # ./lib/mongoid/dirty.rb:114:in `block in setters'
     # ./lib/mongoid/dirty.rb:113:in `tap'
     # ./lib/mongoid/dirty.rb:113:in `setters'

Repro on 2.4.0-stable.

Thanks for reporting this, @dblock . I've confirmed it in 2.4.0 .


⚠ Bofrost.fr has degraded performance

In 48c29f5, Bofrost.fr (https://www.bofrost.fr) experienced degraded performance:

HTTP code: 200
Response time: 1302 ms

Resolved: Bofrost.fr performance has improved in 8608572 after 37 minutes.


Remove kubectl dependency from images

Removes all use of kubectl from images.
Description
Including the kubectl binary in the Emissary image is no longer necessary, and it would be better to remove it completely.
Related Issues
Testing

Built and deployed the full environment locally. Confirmed the local environment was fully functional.
Manually confirmed that the kubectl binary was no longer present in the Emissary image.
Ran the full suite of tests.

Checklist

[X] Does my change need to be backported to a previous release?
No.

[X] I made sure to update CHANGELOG.md.
Unnecessary for this change.

[X] This is unlikely to impact how Ambassador performs at scale.
This change will not impact performance in any way.

[X] My change is adequately tested.

[X] I updated DEVELOPING.md with any any special dev tricks I had to use to work on this code efficiently.
Unnecessary for this change.

[X] The changes in this PR have been reviewed for security concerns and adherence to security best practices.

@rick-a-lane-ii you should have permissions to upload directly to emissary-ingress.git and not have to open a PR from your fork (our CI doesn't work on community forks due to permission issues though @LanceEa has been looking into fixing that).

Yep, I'll close this out and open a PR normally against the main repo. I wanted to specifically adhere to the community-based process for one of these PRs.

Also can you update https://github.com/emissary-ingress/emissary/blob/master/docs/releaseNotes.yml for the change? when you update docs/releaseNotes.yml, you will have to run make generate which will generate the new CHANGELOG.md

I went back and forth on whether this should have an updated CHANGELOG or not, because it doesn't feel like this should have been an advertised/inherent feature in the first place, and it feels a bit odd to announce that it no longer supports it. But no matter, I will update accordingly.


Ignore clippy::let_unit_value lint

bors r+

auto retry is not triggered or is very slow.
bors r-
bors r+

bors r+

bors r+


Autogenerate the java test GetAllRecordsOfAllTypes so it is kept up to date with the available API objects.

The original test file was out of date and attempted to get records for objects removed from the latest server versions. Now it is autogenerated, ensuring no code calling get_all_records for removed or deprecated objects is included.

I think for classes that are deprecated but not yet removed, we should still test.

@thomassa would that return meaningful results though?

@gaborigloi I corrected that and I'm merging.


Miniver ^3.0.4 dependency breaks when minimatch 3.0.5 is installed

Hey,
Node v0.12.18.  Our version of pm2 depends on a version of shelljs, which depends on glob, which depends on ^3.0.4 of minimatch.  New release of minimatch is busted due to newer syntax used.  I suppose there are a lots of way to look at it, but this arguably breaks semver, IMHO.
/var/www/html/admin/modules/pm2/node/node_modules/pm2/node_modules/shelljs/node_modules/glob/node_modules/minimatch/minimatch.js:4
const path = (() => { try { return require('path') } catch (e) {}})() || {
Would you be ok if I pushed a PR changing the dependency version requirement for glob to be 3.0.4 instead of ^3.0.4 until minimatch fixes it?
Thanks,
Matthew Fredrickson

您好，我最近正在休假中，无法亲自回复您的邮件。我将在假期结束后，尽快给您回复。

Yes! We need this as well!!

Fixed on minimatch 3.0.6


Ram usage

I'm not able to understand why, but blog zinnia use a lot of RAM during executions.
I don't know where can I check really. Are there someone had same problem???

I am having RAM issues too, but in my case also the CPU goes crazy.
I recently opened an issue about it and in my case this seems to happen because of some URLs in the entry's content.
I also tried reducing the number of MaxClients etc. but this didn't solve it and my guess is that anyways the reason is a single worker, thus reducing any number of processes/threads in Apache will not have any effect on this issue.
Do you use URLs in your content? And if so, in case you remove them, does the issue still occur?

Hello,
today I have just mae some new tests with Django 1.10, and with only the admin app, my instance use ~40Mo at startup and ~80Mo once a detail page has been rendered.
WIth a complete installation once the pages of the blog rendered even the admin pages, I reach ~86Mo so Zinnia does not create memory leaks, but Django like the RAM.
I close the issue, unless new informations.
Regards


[DOC]Deseasonalizer Clarity Needed

Describe the issue linked to the documentation
The Deseasonalizer does not remove the trend, if I am not wrong?

A transformer that removes a seasonal and trend components from time series.

An alternative/fix

A transformer that removes the seasonal component from time series.

Hi @satya-pattnaik - yes that's right, good catch! I'd appreciate a PR!


businessman.ru is broken by HTTPS filtering [Windows]

URL:
https://businessman.ru/new-individualizaciya-yuridicheskogo-lica-osobennosti-sredstva-i-sposoby.html
Actual behavior:

Response(not header):
HTTP/1.1 200 OK
Server: nginx
Date: Mon, 23 Apr 2018 21:19:01 GMT
Content-Type: text/html; charset=UTF-8
Transfer-Encoding: chunked
Connection: keep-alive
Vary: Accept-Encoding
Expires: Thu, 19 Nov 1981 08:52:00 GMT
Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0
Pragma: no-cache
Strict-Transport-Security: max-age=63072000;
    includeSubdomains; preload

This site works as expected on Android and MacOS.

Works normally on Windows.
It seems they fixed the issue on server side.  Now it's like this:
Strict-Transport-Security: max-age=63072000;    includeSubdomains; preload

Yes. It works now.


fix weird submodule error

woho after some annoying testing i found a workaround against the failing circleci problem.
AFAICT they restore the .git directory and that seemed to be corrupted, however running the submodule sync twice works around twice - yep it's pretty weird.
Let's see.
(fixes #143)

I am so free and going to merge this as CircleCI is finally passing + it's just two lines of fixes :)

Tnanks!

Thanks!

Didn't know that you were still awake - would have waited then. Get some sleep ;-)

you too)


Allow redirects to external URLs & fragments

This gem validates the redirect_url more strictly than router-api does. It doesn't allow fragments or external URLs.
This commit makes the validations consistent between this gem and the router-api (see the Route model). This means users can redirect off-site, as well as redirect to specific guidance chapters like this one.
This was discussed here when implementing the redirect feature, so @boffbowsh @bradwright @alext might have thoughts?
Zendesk: https://govuk.zendesk.com/agent/tickets/1177725

This means users can redirect off-site

We're typically very careful about where we allow off-site redirects. That may not be something we want to allow here. @bradwright may have a steer on this.

Updated after irl conversation. Now allows fragment urls, but not external sites.

You're right. Fixed it and added the tests from router-api (https://github.com/alphagov/router-api/blob/master/spec/models/route_spec.rb#L246).


[SPARK-45556][UI] Allow web page respond customized status code and message through WebApplicationException

What changes were proposed in this pull request?
Adds an extra catch of WebApplicationException in Spark core and history server's web page servlet, to let customized response to pass-through instead of wrapping them in a 500 response, to make web page and REST API have consistent behavior.
After the change, when a WebApplicationException is thrown, servlet will render a basic Spark page with the exception message, and respond with the status code of the exception.
For example, previously when a customized 418 exception is thrown, the response will be a 500 like this:

After the change, a 418 response will be rendered like this:

Why are the changes needed?
Currently for web page servlet in Spark, when an exception is thrown, there's only 3 possible responses:

If it is history server unable to find an app, a 404 will be responded.
It the exception is an IllegalArgumentException, a 400 will be responded.
Otherwise, a 500 will be responded, wrapping the original exception within it.

However for REST API, if a response is a WebApplicationException, its response can be directly returned with the designed status code and message, without being wrapped. This causes inconsistent behavior between web page and REST API.
For history server, Spark allows to use alternative ApplicationHistoryProvider, or adds extra page and API through "AppHistoryServerPlugin". Suppose some extra provider or plugins is used, and in some cases they want to return a special status code due to their needs. Currently there's no way to do it other than forking Spark because web page servlet does not support it.
Does this PR introduce any user-facing change?
By default, no. Because Spark UI's built-in web page servlet does not throw WebApplicationException.
For 3rd party provider or plugin, if a WebApplicationException is thrown, after this change, its message and status code can be directly responded. Previously it is wrapped within a 500 response.
How was this patch tested?

3 UTs are added:

Testing whether history server servlet can handle WebApplicationException
Testing whether servlet created by JettyUtils can handle WebApplicationException
Testing whether servlet created by JettyUtils can handle other exceptions as before

Manually tested

Was this patch authored or co-authored using generative AI tooling?
No

Would be great if we can contain the screenshot of UI with this fix.

Would be great if we can contain the screenshot of UI with this fix.

Thanks for the comment. Have updated the screenshot before and after the change.

Kindly ping @HyukjinKwon . Could you please help to take a look at this PR if you think it is OK to do this change? Thanks.

Also kindly ping @srowen @dongjoon-hyun.

Seems OK. It's a little bit better than the raw stack trace. I don't suppose there's a similar change to make in the main Spark UI? or does it also already work this way?

I don't think Spark's built-in UI needs this change, because web page doesn't seem to throw WebApplicationException, and REST API already supports this. The gap may be because web page and REST API are using different ways to handle HTTP requests.
The main goal of this PR is to let web page part also able to return customized response code (like 418 as an example), instead of just 200, 400, 404 and 500. It is basically for those who wants to extend Spark UI through plugins, without forking Spark source code.

Kindly ping @srowen


Best effort fix for CodeNarc capturing issue

The previous version of the code assumed that the CodeNarc XML report
would always just contain a single SourceDirectory element. It turns
out that that is not true with the CodeNarc version we're using. There's
a SourceDirectory element for each package of the tested module. The
code then prepended all the SourceDirectory elements in front of each
file, which resulted in broken path being rendered into the custom
value.
With this commit the code now tries to find the right SourceDirectory
element by iterating over all of them and then checking whether the
violating file exists in that directory. This results in correct paths
being rendered. However it can result in the wrong file being reported
in case files with identical file names exist in different directories.

This is just updating the Groovy version of the script. The Kotlin version needs to have the same changes.

Thanks for the PR @britter, it is is indeed fixing the multi source directory case and not harming the default case.
Would it be possible for you to create the Kotlin version as well?


histograms: Support expansion of native histogram values in templating

In particular alert templates (i.e. what to do if an alert description contains {{ $value }} and the value is a native histogram), but let's not forget console templates.

Thoughts:
A pure text representation of the values will be difficult to read for a human. We could additionally add functions that render it in different ways – like $value | histogramASCII to build a graphical approximation out of ASCII art, $value | histogramD3 for a context where d3.js is available to do the rendering. If we want to go that far, even one to produce a Base64 encoded PNG for inline data: URLs.
We need a safe default behavior, but most of the time the user will know that they expect a histogram as $value. Different representations will work in different contexts. Functions to transform the representation let the user choose one that is appropriate in the context.
This may break down when the same text (alert description) is used in different contexts (email, Slack, Pagerduty notification). For these cases it might be helpful if the default text representation is uniquely identifiable, so that a filter in the receiver specific template can walk over the whole text and do something to any histogram it finds.

@marctc plans to work on this.

Now @suntala is giving it a try.

Hey @beorn7,
@britishrum and I would like to be assigned to this one please.

@britishrum apparently GH requires you to actually comment on this issue before I can assign it to you. :thinking:

@beorn7 commenting now, could you try again please?

https://github.com/prometheus/prometheus/pull/13731 solved this for text expansion (note the palindromic PR number!).
I'm actually not so sure if a fancier representation is worth the effort. Let's first see how often histograms are actually used in templates.
Introducing something like a rendering context would be a whole new concept in template expansion. If somebody things that's useful and want to invest the work, I won't stop them. But I'm going to close this issue now so that we know that we have covered the bases. If somebody has concrete plans to work on the fancier renderings, I suggest to open a new issue for it, maybe focused on the concept of a rendering context and not so much specifically histograms. (Cf. the ongoing discussion about little mini dashboards in alerts, which is still an open topic for the dev-summit.


[SPARK-50581][SQL] fix support for UDAF in Dataset.observe()

What changes were proposed in this pull request?

Mark inputProjection field as transient in org.apache.spark.sql.execution.aggregate.ScalaAggregator.
Why are the changes needed?

To support UDAF in Dataset.observe() which currently fails due to serialization exception.
Does this PR introduce any user-facing change?

No
How was this patch tested?

Added test.
Was this patch authored or co-authored using generative AI tooling?

No

@hvanhovell , @cloud-fan - could you please take a look here?

Merged to master.


v1.4.0rc1

Checklist

[x] Used a personal fork of the feedstock to propose changes
[x] Bumped the build number (if the version is unchanged)
[x] Reset the build number to 0 (if the version changed)
[x] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[x] Ensured the license file is being packaged.

@xylar @mahf708 I followed the example of https://github.com/conda-forge/zppy-feedstock/pull/1. It looks like the changes to use zstash_dev were already made. So, I think this pull request should be good to go.

@forsyth2, this looks good.  Please mark as ready for review and merge when you're ready.  I will be off for the weekend pretty soon.


When editing a board, columns always show in the order of creation - although they are already re-ordered

Is that a correct observation?

Somehow I never saw this issue.
When editing a board, the columns should be displayed in the same order as on the board itself (except left-to-right becomes top-to-bottom).

Thanks for caring :-) Unfortunately I switched to Wekan and cannot give further details anymore. But I'm sure I made this observation.

we also have this bug :

in setting screen, columns are in the right order.
after clicking the edit button, they appear in order of creation
so I think the fix is very quick, please :-)

I also noticed that having more that 10 columns is bugged :
displayed order is 0, 1, 10, 11, 12, ..., 2, 3, 4, ...
problem of string order instead of number order !

I only looked at this in the rewrite, but apparently, the columns are only sorted in effectively one place in the board.component.ts constructor. The addTask, updateTask and removeTask functions in the column component call the updateActiveBoard function, but that function never does any column sorting, so it displays in the order the api gives it in, which is the order the columns were created in.
This also happens when you try to move the task to a different column from the context menu.


Russian Translations

Get Involved!
We are seeking Russian translators for this project. If you would like to get involved with translating a lesson please fork the project and start translating.

Set up

[x] _config.yml (@brain-geek)
[x] index.md (@brain-geek)

Basics

[x] basics.md (@brain-geek)
[x] collections.md (@brain-geek)
[x] enum.md (@brain-geek)
[x] pattern-matching.md (@brain-geek)
[x] control-structures.md (@brain-geek)
[x] functions.md (@brain-geek)
[x] pipe-operator.md (@brain-geek)
[x] modules.md (@brain-geek)
[x] mix.md (@brain-geek)
[x] sigils.md (@nscyclone)
[x] documentation.md (@brain-geek)
[x] testing.md (@nscyclone)
[x] comprehensions.md (@nscyclone)
[x] strings.md (@nscyclone)
[x] mix-tasks.md (@nscyclone)
[ ] iex-helpers.md

Advanced

[x] erlang.md (@brain-geek)
[x] error-handling.md (@nscyclone)
[x] escripts.md (@nscyclone)
[x] concurrency.md (@nscyclone)
[x] otp-concurrency.md (@brain-geek)
[x] otp-supervisors.md (@nscyclone)
[x] metaprogramming.md (@brain-geek)
[x] umbrella-projects.md (@yuriibodarev)
[x] typespecs.md (@yuriibodarev)
[x] behaviours.md (@yuriibodarev)
[x] gen-stage.md (@Saneery)
[x] protocols.md (@brain-geek)

Specifics

[x] plug.md (@yuriibodarev)
[x] ecto.md (@tetiana12345678)
[x] eex.md (@yuriibodarev)
[x] ets.md (@brain-geek)
[x] mnesia.md (@nscyclone)
[ ] debugging.md

Libraries

[x] guardian.md (@brain-geek)
[x] poolboy.md (@nscyclone)

Note
Those new to Elixir and / or Github are encouraged to get involved :smile:. 1 Pull Request per lesson.

@brain-geek @tetiana12345678 & @gaynetdinov
Let's close the other two (#218 + #99), and work within this one. If you are working on any lessons please let everyone know just incase someone is already working on it in this thread. Hope this is ok
:heart:

I'll take "Functions" next. And "erlang.md" later on.

great move.

I'll take "Composition" next.

I'm going to take advanced/error-handling.md next. It is called errors.md in this issue for some reason.

I've marked it for you, @nscyclone .

I'll start working on advanced/concurrency.md soon.

advanced/concurrency.md is already merged (#266), so I guess we could mark it as translated here.
I'll take basics/sigils.md soon.

I've updated the translations status. Also, I'll take otp-concurrency.md next.

I'll take 'basics/comprehensions.md' next. It's original version is already merged but is not included in our list yet.

I'll take "Documentation" next to finish up all 'Basics' lessons.

I'm going to start translating the 'Mix Tasks' lesson soon.

I'll take 'Metaprogramming' next.

I'll take eex.

@brain-geek @nscyclone and everyone else, I'm wondering how best to track small changes to previously translated lessons and I was hoping to get your feedback.  Do you find this particular Issue format helpful?  Would it be sufficient to make additions to it for each change awaiting translation?
I'm looking for ways to handle PRs like #452, any thoughts would be greatly appreciated.

@doomspork, I think this is the best option so far. The only question is how to automate this. Some sort of webhook that would check whether a specific label is applied to an issue and then would apply the required changes to issues like this one when needed (adding an empty checkbox under the new Improvements section or something else).

@nscyclone That's nice idea to create issues for each translation!
We can do it manually - creating an issue ticket with checklist for each merged PR and look how it goes.

I'm taking ets.md next.

I can translate eex.md and after that I can take plug.md

@yuriibodarev, AFAIK, eex.md is already a WIP by @sobolevn.

we had a conversation, that it's totally fine by me.

I've reassigned everything in first post according to Slack discussion.

I've just updated the list because it lacked the strings.md lesson from the basics sections and the sections were described differently.
I'll try to find some time to send a PR with strings.md tonight.

I've just started translating the last free lesson — mnesia.md.

Wow, looks like we've translated all lessons to Russian!
Plug is still in review ( #542 ), but I guess we'll finish with it in a few days.

Hm, not yet - there's new 'Umbrella projects' lesson. I'm adding it to top list.

Can I take Umbrella projects for translation? I will start it after we'll finish with Plug!

@yuriibodarev Sure, marked it as taken by you.

There is a new lesson in the advanced section. Does anyone want to take it?

I will take it

I think You can mark typespec as translated. And there is a new lesson on behaviours in Advanced which I want to take for translation!

@yuriibodarev thanks for the note. Added and marked for you.

Hi @brain-geek, i want to take for translation a new lesson GenStage

@Saneery Marked for you. Thanks!

I'll take the fresh guardian lesson.

You can mark GenStage lesson as translated.

Thanks for noting. Marked.

I'll start working on Poolboy this weekend.

I was reviewing the translations today. It seems like some of them need to be updated:

basics/enum;
basics/modules;
advanced/metaprogramming;
specifics/plug.

Does anyone want to take a stab at them?

@nscyclone I guess we should restructure this document somehow. e.g. list only TODO items or just keep it up-to-date. Other option would be closing this issue. Any ideas?

@brain-geek Actually I've recently updated the task list according to the current translations state.
The problem is that it doesn't yet reflect the newly added versioning: the lessons are simply divided in two groups depending on whether there is any translation for it even it's outdated. So I think that maybe adding a version next to every lesson and unchecking the outdated ones would be sufficient for now.
We really shouldn't overcomplicate this. And it also would be nice to ask the other translators' opinion on this topic.


feat!: update to ACVM 0.16.0

Description

Problem*

Resolves
Summary*
This PR updates to track the head of ACVM master so that it includes all the changes which will go into ACVM 0.16.0.
Documentation

[ ] This PR requires documentation updates when merged.

[ ] I will submit a noir-lang/docs PR.

[ ] I will request for and support Dev Rel's help in documenting this PR.

Additional Context

PR Checklist*

[x] I have tested the changes locally.
[x] I have formatted the changes with Prettier and/or cargo fmt on default settings.

Mac test failure is unrelated to ACVM 0.16.0


User input models

Your proposed functions take in the data, train a model, and return a metric. However, they don't allow a user to input their own models which is functionality most, if not all, users will want. Your functions also don't return the underlying trained model, so if the users were to find a model that was well-fit to the data there would have no way to access it.

Thanks. We have taken care of this issue by redefining the function which now allows the user to input the observed and the predicted values from a trained model and outputs the score. The user can now decide which model to keep and use our function to compare the performance of different models.


Access Firebase ref

Is it possible to access the Firebase object that has been created by Angularfire2? i.e. I want to be able to get the Firebase object with my Firebase details as set by defaultFirebase(). There are some things Angularfire2 doesn't do yet but I want  to be able to do directly until support is there.

I will also add that I am trying to do this. I've gone through all of the github issues I could find that had to do with typings, but no matter what I continually get the error:
[nwatkins@eduroam-169-233-195-121 journaling]$ ng serve
Could not start watchman; falling back to NodeWatcher for file system events.
Visit http://ember-cli.com/user-guide/#watchman for more info.
Livereload server on http://localhost:49152
Serving on http://localhost:4200/
The Broccoli Plugin: [BroccoliTypeScriptCompiler] failed with:
Error: Typescript found the following errors:
  /home/nwatkins/journaling/tmp/broccoli_type_script_compiler-input_base_path-cwSQxM5U.tmp/0/src/app/app.component.ts (5, 27): Cannot find module 'firebase'.
    at BroccoliTypeScriptCompiler._doIncrementalBuild (/home/nwatkins/journaling/node_modules/angular-cli/lib/broccoli/broccoli-typescript.js:120:19)
    at BroccoliTypeScriptCompiler.build (/home/nwatkins/journaling/node_modules/angular-cli/lib/broccoli/broccoli-typescript.js:43:10)
    at /home/nwatkins/journaling/node_modules/angular-cli/node_modules/broccoli-caching-writer/index.js:152:21
    at lib$rsvp$$internal$$tryCatch (/home/nwatkins/journaling/node_modules/angular-cli/node_modules/rsvp/dist/rsvp.js:1036:16)
    at lib$rsvp$$internal$$invokeCallback (/home/nwatkins/journaling/node_modules/angular-cli/node_modules/rsvp/dist/rsvp.js:1048:17)
    at lib$rsvp$$internal$$publish (/home/nwatkins/journaling/node_modules/angular-cli/node_modules/rsvp/dist/rsvp.js:1019:11)
    at lib$rsvp$asap$$flush (/home/nwatkins/journaling/node_modules/angular-cli/node_modules/rsvp/dist/rsvp.js:1198:9)
    at nextTickCallbackWith0Args (node.js:420:9)
    at process._tickCallback (node.js:349:13)

I've solved it for now by:
To be able to retrieve the firebase reference through a :FirebaseObjectObservable angularFire object: In firebase_object_observable.d.ts, set private _ref; -> public _ref;

See #294. We're adding this in a future release.


sdl: render: Add UpdateYUV()

Add SDL_UpdateYUVTexture function.

This change is

Hi @malashin, thanks for the contribution!
Could you add a stub function to substitute for the missing function? We use SDL 2.0.0 for Travis CI builds to make sure it can work with older SDL2. You can see sdl/filesystem.go for an example of how to provide the stub function.
I've also added the note in the CONTRIBUTING.md for future contributors.

@veeableful
Seems to be working now. Really need to get up to speed on Travic CI, all of this is quite new to me.

No worries @malashin. Thanks for getting it to work!


User staking not updated correctly

User redelegates from validator A to validator B. Before redelegation is complete, User undelegates from validator B.
Bdjuno now stores both redelegation and unbonding.
Expectation:
Redelegation is removed and only Unbonding remains;
Any staking TX should update the user's staking info

@ryuash I don't think this is a bug with BDJuno, but is how things should work. This is because the user cannot undelegate before the redelegation is completed. What I believe happened here is the following:

the user had an amount of tokens delegated (let's say 100 DSM for simplicity)
they had parts of their tokens delegated to Validator A and part delegated to Validator B (let's say 20 DSM to Val A and 80 DSM to Val B)
the redelegated their amount from Val A to Val B (20 DSM)
they unbonded their already-delegated amount from Val B (part of the 80 DSM)

I believe this is the case because inside Cosmos you can not undelegate some tokens before they are fully re-delegated to the destination validator

After investigating more, turns out this is not a bug but how things are intended to work. As we can see, the redelegation and unbonding delegation exist at the same time on-chain as well:

Redelegations
Unbonding delegations

I'm going to close this issue and consider it a non bug


Update container-service-load-balancing.md

Update Azure CLI usage to create probe/rule.
azure lb rule create -> azure network lb rule create
azure lb probe create -> azure network lb probe create

Hi @wbuchwalter, I'm your friendly neighborhood Azure Pull Request Bot (You can call me AZPRBOT). Thanks for your contribution!

It looks like you're working at Microsoft (wibuch). If you're full-time, we DON'T require a contribution license agreement.

If you are a vendor, DO please sign the electronic contribution license agreement. It will take 2 minutes and there's no faxing! https://cla.azure.com.

TTYL, AZPRBOT;

@wbuchwalter : Thanks for your contribution to the Azure documentation! The author, @rgardler, has been notified to review your proposed change.

#sign-off
Thank you @wbuchwalter for your valuable contribution.


Dockview Framework Wrappers (Vue.js, Angular, JavaScript etc.)

All feedback is welcome.
Vue.js
A Vue.js wrapper is currently being developed which will support Vue 3+ (see attached PR)
Angular
Work is intended to start after Vue.js is completed
JavaScript/TypeScript
Since dockview is mostly written in plain Typescript under dockview-core whilst the framework packages are being developed the apis in dockview-core are being cleaned up for offical support

I just wanted to comment that the javascript example breaks with v1.13.0 due to this.accessor.options.createComponent is not a function at dockview.addPanel.
Working example at 1.12:
https://codesandbox.io/p/sandbox/priceless-hellman-7ppjpx?file=%2Fpackage.json
This may have been intentional but I didn't find anything in the docs about pure js.
Also great work on this project!

I just wanted to comment that the javascript example breaks with v1.13.0 due to this.accessor.options.createComponent is not a function at dockview.addPanel. Working example at 1.12: https://codesandbox.io/p/sandbox/priceless-hellman-7ppjpx?file=%2Fpackage.json
This may have been intentional but I didn't find anything in the docs about pure js. Also great work on this project!

Ah yes - the plain JavaScript/TypeScript implementation has required some breaking changes to make it better compatible with supporting multiple framework implementations built on top of it.
I will get some examples and docs built for this before it's offically all released but it will look something like the below:
const dockview = new DockviewComponent({
    parentElement: document.getElementById('app'),
    createComponent: (options) => {
        switch (options.name) {
            case 'default':
                return new Panel();
        }
    },
});

https://github.com/mathuo/dockview/blob/5d6055c4d21d317a0478dca1d605be8a810f3aed/packages/docs/templates/dockview/basic/typescript/src/index.ts


Production and preview deployments not working

Cloudflare pages not deploying the production and preview builds
I raised a PR on 8 March 2023 IST as a part of a hotfix that would remove the signing button from the main site i.e. website-www
My PR was merged and even sync dev to main was merged. But as observed by @rohan09-raj @prakashchoudhary07 and me, we found our builds are not deploying.
We tried re-deploying a previously deployed instance. That instance showed re-deployment successful but the new changes of the latest PR were not reflected.
For the preview builds we tried to open the latest preview build which resulted in NOT Found
Link to Sync dev to main: https://github.com/Real-Dev-Squad/website-www/pull/415
Link to the hotfix PR: https://github.com/Real-Dev-Squad/website-www/pull/414

Looking at CF dashboard,
This commit is the latest deployed: aba3bde Merge branch 'develop'
Success
3:01AM March 6, 2023
Not sure why this happened. We have "Enable automatic production branch deployments" enabled for main branch. Let's continue keeping an eye on new merges.
Thank you for raising this issue.

Weirder: The preview link generated also doesn't match the commit hash of the stale deployement.

I think the reason for CF pages not working is this: https://discord.com/channels/673083527624916993/749241412830232679/1082766042142617621
The issue has been resolved and latest commit 6b23714 is now deployed.


TrumpScript examples

Please add some sample TS codes in the repository!

It's already in test/test_files.

Name of folder is not self-explanatory and should be renamed to Examples, because now people think about unit tests, not about test examples

Examples are for socialists!

Done.


Rename match groups

This has no impact on the user experience, but it might have on readers of the source code: the match groups are taken directly from the Elixir lexer, even though they don't make much sense when applied to the semantics of the JSON file format. Not that here, a pair of curly brackets is referred to as a tuple, even though it should be called a map in a JSON object. I'd also rename the list to something like array.

Thank you, it's a copy paste error. It should have been object and array like you have mentioned.


Update doc for adding new param in cat shards action for cancellation…

… support
Description
Cancellation support on cat shards admin API. Added new flag to set the timeout for shard request.
Issues Resolved
Closes #13908
Version
From OS version 2.17 and onwards, the cancellation support will be given to cat shards API.
Checklist

[ ] By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license and subject to the Developers Certificate of Origin.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

@kolchfa-aws can you please check and merge if it looks good?

Thank you, @aasom143! Applying "Done but waiting to merge" label to put this in the 2.17 editorial queue starting 9/10. This PR will be merged before the release.


respect assets that have been ignored and don’t process

@tdreyno here's a partial fix for #96 / https://github.com/middleman/middleman/issues/1789 -- I realized I'm not quite sure what the correct behavior for linked assets is though.
With this implementation -- ignored assets are never processed, so if they had linked assets they aren't linked. But since we're inserting linked assets after the ignore descriptors have run -- they don't get ignored. I feel like this is the "least surprising" option, but leaves me with two questions:

should we process ignored assets for links
should linked assets be ignorable (I'm not sure why you would do this, and it could cause issues as the link indicates a dependency)

look forward to your thoughts

I think we should process ignored assets for links. It is possible to proxy to an ignored asset.
I think they should be ignorable, if possible. It might blow up in people's faces, but atleast its predictable. Some sprockets gems link a ton of shit they don't need (fonts, icons, etc)

Cool, glad I asked :)
Is the best way to run the sprockets assets through the ignore descriptors to call app.extensions[:sitemap_ignore].manipulate_resource_list with the resources from middleman-sprocket's manipulate_resource_list?

Looks like I've got some work to do for MM 4.0, but does this match what you were thinking? https://github.com/middleman/middleman-sprockets/pull/97/commits/debae5700d739727efff9ea6811a3d3397770e7e#diff-7cd0aea0abb64cf9966fafa7c916f2b7

What is base_resource?

That's a great question -- was left in since the initial v4 lift. My assumption is it was put in place to make sure the extension was only acting on "original" Middleman::Sitemap::Resource objects -- that way it wouldn't re-create SprocketsResources, but I guess that means it wouldn't act on ProxyResources (or others) either.

I think it makes sense to try and support any resource type (and except our Sprockets resources directly?). The sitemap is kind of duck-type-y.

Also, merge away if you're happy

"delete method" refactoring is my favorite :)
Will try this for now then can come up w/ a good test case if anyone runs into trouble.


State information missing in context while running slu test.

Describe the bug
ValueError: Plugin XLMRMultiClass requires state to be passed to the model
When use_state=True is passed inside plugins.XLMRMultiClass.

Context missing in this line inside slu/dev/test.py.
Simple fix like this would solve it.
const.CONTEXT: {const.CURRENT_STATE: row["state"]}


Put gdmls in subdirectories

The gdml directory is getting very messy. Probably split it up based on detector

I totally agree. We should resume this at some point.