rawtherapee: 5.8 -> 5.9

Description of changes
Update rawtherapee to the latest version.
Things done

Built and ran on x86_64-linux.
Removed patch from nix expression that has been applied upstream.

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
23.05 Release Notes (or backporting 22.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[ ] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 214033 run on aarch64-darwin 1

1 package failed to build:

rawtherapee

Closed by #215544.


[Flink-20999][docs] - adds usage examples to the Kafka Avro Confluent connector format

What is the purpose of the change

Provide additional examples of how to use the avro-confluent format. In particular, no example of how to serialize the kafka key or use the upsert connector are currently mentioned in the avro confluent connector documentation

Brief change log

Added an example of a table serializing the kafka value in an avro record registered in the schema registry, while keeping the key in raw format
Added an example of how to write to that table
Added an example of a table using the schema registry for both the key and value
Added an example of using the schema registry together with the kafka upsert connector

Only the English version of the documentation has been updated so far. Once the  examples are approved, I'm happy to copy/paste them to the Chinese version of the documentation, at which point I'll need support for the few sentences that were updated/added.
Verifying this change
Manually executed ./build_docs.sh -p to check visually the result
This change is a trivial rework / code cleanup without any test coverage.
Does this pull request potentially affect one of the following parts:

Dependencies (does it add or upgrade a dependency): no
The public API, i.e., is any changed class annotated with @Public(Evolving): no
The serializers: no
The runtime per-record code paths (performance sensitive): no
Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Kubernetes/Yarn/Mesos, ZooKeeper: no
The S3 file system connector: no

Documentation

Does this pull request introduce a new feature? no
If yes, how is the feature documented? no

Thanks for the feed-back @wuchong .
I copied the code examples to the Chinese version of the documentation, although they contain some English sentences at the moment, which I'm not capable of translating. Please let me know if I should open a ticket for that part or if we can handle it as part of this PR.

Thanks for the feed-back @wuchong .
I copied the code examples to the Chinese version of the documentation, although they contain some English sentences at the moment, which I'm not capable of translating. Please let me know if I should open a ticket for that part or if we can handle it as part of this PR.


Incrementally adding new languages to multilingual checkpoint

Reproduce the same experiments as done by @yongzx  on English checkpoint with  multilingual checkpoint: https://huggingface.co/bigscience/tr5a-1B3-multilingual-mt5tok-checkpoints/tree/global_step30000
Related issues:

https://github.com/bigscience-workshop/multilingual-modeling/pull/3
https://github.com/bigscience-workshop/multilingual-modeling/issues/2

TODOs

[ ] zero-shot evaluation of multilingual checkpoint on German and Korean
[ ] finetune embedding layer on the German/Korean Oscar dataset
[ ] train adapter layer on German/Korean dataset

Thanks @vnikouliNLE! For the adapter layer training, I think I should work on this instead of GPT-2, since now we have this model.

Here's the link to the repo for incremental-addition-of-languages: https://github.com/bigscience-workshop/multilingual-modeling/tree/+lang


python 3 full not working

Describe the bug
I have a hash based routing example app that I migrated to use this routing.  It all works great when running the app from the base URL.  But when I try to go directly to a form using that form's route, I get the following error in the logs:
SyntaxError: invalid syntax (history.py, line 1)
at /downlink/anvil/history.py, line 1

The app I converted was pre-layouts, and as part of adding the routing dependency, the app was upgraded for layouts.    I'm also using the TemplateWithContainerRoute since the app I'm migrating used templates.
This doesn't happen with the example M3 based app, so it might very well be something boneheaded I've done during the migration, but I'm not seeing anything.
Version
The latest master.
To Reproduce
Go to: https://dtcvv32xon5ief24.anvil.app/debug/23LB67SX66FHPDU5JYKDFNF23DCIVQ5R%3DZZQ6DR2JFMQID5TJNLEL7FWE/about
Here's the clone link for the app: https://anvil.works/build#clone:DTCVV32XON5IEF24=TAI5S6GFWVB64I75SCXVQKZW

If you switch to python 3.10 on the server it should work
We'll get that fixed in python 3 full

Thanks!  I'd forgotten that app was old enough to predate the Python 3.10 server runtime that's the default now.

this should now be fixed

just looking at the app - would recommend turning your links into routing.NavLink components

Thanks, I'll add that to the list.  This was practice migrating an old hash routing example to the new routing.  I'll add NavLinks to the todo list.
Another thing that gave me some  pause that you might want to document is the environment the routing methods run in.  I'd been going to do an authorization check in a before_load method and force the user to login if they weren't already, but then realized that when they go directly to a URL that probably runs on the server.  Sticking a print(is_server_side()) in before_load it looks like the initial run is on the server, and then another happens on the client.
I'm assuming the best practice is to redirect in before_load, rather than do anything that relies on the client-side environment.

yes moved to #30
correct - before load was designed with redirects in mind
although - maybe that'd work with an is_server_side check
Best practices are up for grabs


hold the mutex while calling notify_all

according to this https://github.com/realm/realm-core/blob/master/src/realm/util/interprocess_condvar.cpp#L459-L461
the caller should be holding the mutex before calling notify_all
In what other branch/repo this changes should be cherry-picked ?

@fealebenpae  Could the win32 CI hang be related to this

@blagoev I think it's very likely. I think additional debugging is warranted.

this seems not the correct fix. Closing this PR


chore: create log dir

Signed-off-by: Jim Ma<EMAIL_ADDRESS>
Description

Related Issue

Motivation and Context

Screenshots (if appropriate)
Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] Documentation Update (if none of the other choices apply)

Checklist

[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[ ] I have read the CONTRIBUTING document.
[ ] I have added tests to cover my changes.

Codecov Report

Merging #1947 (57448b3) into main (fdb11e2) will decrease coverage by 0.04%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             main    #1947      +/-   ##
==========================================
- Coverage   42.92%   42.88%   -0.05%
==========================================
  Files         133      133
  Lines       16763    16763
==========================================
- Hits         7195     7188       -7
- Misses       9020     9027       +7
  Partials      548      548

Flag
Coverage Δ

Object-compatibility-e2etests
?

e2etests
?

unittests
42.88% <ø> (-0.05%)
:arrow_down:

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

Impacted Files
Coverage Δ

...ent/daemon/peer/peertask_piecetask_synchronizer.go
56.28% <0.00%> (-0.60%)
:arrow_down:

client/daemon/peer/piece_manager.go
52.99% <0.00%> (-0.41%)
:arrow_down:

client/daemon/peer/peertask_conductor.go
52.69% <0.00%> (-0.17%)
:arrow_down:


vscode: bump some extensions

Description of changes

Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
23.05 Release Notes (or backporting 22.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

Just one more note about the native devsense.php.ls: it would be nice to have checkPhase ensure it's a legit working executable, so that it's easier to track regressions later

The previous comment was rather a nit pick. If you manually tested that the language server has been fixed on your platform, I think that's good enough to merge.
I'd still set explicit meta.platforms. Also, I'd split the version update and the fix into separate commits. Otherwise LGTM

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/prs-already-reviewed/2617/921


Added public API of UI Grid

UI Grid Builders are still not ready
Defaults values are not ready

@ bigsnickers

Reviewed. Some of the comments I've written only once. Please check similar places In other files.

All fixes, except notes, which partially done in the next PR


(PE-27909) Return plan metadata for init plan

Previously when the plan metadata is requested for the special init.pp plan (with the same name as its parent module) the metadata endpoint would not trim the init from the name before calling in to get_plan_info. With this commit the endpoint has been updated to handle plans referenced only by [module name]::init.

CLA signed by all contributors.


build: add sync-clean target

Helpful target to ensure all vendored files are fresh
Since the sync target uses file timestamps, if you jump back and forth between different upstream commits it can get confused and fail to sync the "new" content since timestamps are older.  This gives a quick way to reset all the vendored files to avoid potentially missing anything.

I'll carry this in #7499


Clearer instructions, more n00b friendly.

Changed the instructions to make them n00b friendly.
What issue does this PR address?
Does this PR introduce a breaking change?
Please check if the PR fulfills these requirements

[x] The commit follows our guidelines
[x] Unit Tests for the changes have been added (for bug fixes / features)

Other information:

 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.:x: JwanKhalaf sign nowYou have signed the CLA already but the status is still pending? Let us recheck it.


Request support for Eleuther generative task

Hi all,
Thank you for the excellent work you guys have been doing thus far.
I request that we add support to Eleuther's generative tasks.
We are not encoding batch prompts correctly, leading to an index lookup error in tok_embeddings.
Can you help?
Thank you!

Thanks so much for opening this issue. Coincidently @joecummings is working on this right now.

@ScottHoang  This was enabled in #975 - check it out!

@joecummings this should be completed, right? Gonna close the issue but re-open if I'm mistaken here


Updates for Tapir

@gdalle as alluded to on slack, v0.2 of Tapir made breaking changes which affect DI. This PR updates provides updates which handle that.
I've not checked, but I'm assuming you're doing continuous delivery, so I've bumped the patch to make a release possible. Happy to change it if that's not what you're doing.

On a related note, Tapir now has a "safe mode", which I would like to force users to choose being on / off. Is this best done by modifying ADTypes.AutoTapir (in a non-breaking way), or should I add something in this package?

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

Project coverage is 95.01%. Comparing base (7d3b258) to head (108ec69).
Report is 3 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #241      +/-   ##
==========================================
- Coverage   96.27%   95.01%   -1.26%
==========================================
  Files          74       15      -59
  Lines        3924     1787    -2137
==========================================
- Hits         3778     1698    -2080
+ Misses        146       89      -57

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

I've not checked, but I'm assuming you're doing continuous delivery, so I've bumped the patch to make a release possible. Happy to change it if that's not what you're doing.

That's perfect, although we're already on 0.3.1 so it's gonna have to be 0.3.2

On a related note, Tapir now has a "safe mode", which I would like to force users to actively choose to turn on / off. Is this best done by modifying ADTypes.AutoTapir (in a non-breaking way), or should I add something in this package?

Yeah this should go in ADTypes.jl. Is this information useful for dispatch (in which case it goes in a type parameter) or just at runtime (in which case a struct field will do)?

This also asks the question of what to do when an AD package wants to use DI for testing, in terms of releasing breaking versions:

You can't test with DI until I bump the compat
I can't bump the compat unless you test with DI

Yeah, this is a good question. I actually don't know what the answer is -- maybe AD packages should maintain the DI extensions in their own repos? That way if they make breaking changes, they can continue to support the DI interface without needing to bump the DI version.

Yeah that is probably the right answer. AbstractDifferentiation.jl wanted to do that, but it never got enough traction. Let's wait a bit more while things are in flux, but in the medium term I could definitely see Tapir having a DI extension instead of the other way around


Bug: fail CI on missing package-lock.json sync

v14.13.0 has been released and contains a fix for the issue. Feel free to reopen the issue or to submit a new one if you meet any problems.


Space characters in Confluent.SchemaRegistry.RestService encodes as '+' instead of '%20'

Description
Incorrect encoding space characters of subject parameter value in all methods which accepts subject in Confluent.SchemaRegistry.RestService class.
How to reproduce
Register schema with subject field containing space character.
Try to get schema version.
Request will be executed with incorrect url with '+' characters instead of '%20'.
For example executing simple curl request
curl http://<IP_ADDRESS>:8081/subjects/Some%20Domain%20Event/versions
gives correct response - list of schema versions.
The reason for the problem is that Confluent.SchemaRegistry.RestService class uses WebUtility.UrlEncode to encode subject parameter value. I think you should use Uri.EscapeDataString to encode uri segment.
Package version used: Confluent.SchemaRegistry.2.3.0

Fied by https://github.com/confluentinc/confluent-kafka-dotnet/pull/2226


feat: initial commit

What I did

rename and reorganize all the icons:

delete the white and red variants
keep the black variants
the a variants are default
the b variants are renamed *-alt.svg
keep the 2 color variants (renamed *-duotone)

remove eps, png, jpeg, etc. these should be generated by a build script and gitignored
generally, icons live in ${setName}/${iconName}.svg, e.g. to put a 50% harvey ball on a page,

<rh-icon set="harvey" icon="50"></rh-icon>

Corresponds to src/harvey/50.svg

The exception to this is the standard icons which have one level of subdirectory. These will require some build magic, but ultimately it should work something like this:
"standard" is the default icon set, so doesn't need to be specified

<rh-icon icon="school"></rh-icon>

Corresponds to src/standard/buildings/school.svg

<rh-icon icon="beaker"></rh-icon>

Corresponds to src/standard/science/beaker.svg

This will mean contributors must be careful to avoid name conflicts.
TODO:

[ ] build scripts that generate optimized svg, jpg, png, webp, and eps artifacts, including red and white variants
[ ] ci/cd which adds artifacts to github releases
[ ] documentation, readme, contributing.md, etc
[ ] automation to detect name conflicts (git hooks?)
[ ] linting/verifying monotone icons work properly (no fill or fill="currentColor")
[ ] perhaps some by-hand optimization of svg sources?
[x] add license file

@bennypowers I'm ok with this structure. We might need to update the icon names throughout the other systems to match these renamed duplicates.
@libbylevi are you ok with the icon names and directory structure?

This looks good. We can make sure to avoid re-using icon names as we create new icons (and I think the school/beaker example you found was an error, that icon SHOULD be called "beaker").
You can exclude the two-color / duotone versions, they're not commonly used.

yes, @libbylevi confirming that was a typo in the example. I fixed that now.
I'm going to continue working on the checklist above then. Thanks for the feedback

@libbylevi can you check if the files in this PR were saved with the right pixel boundaries? @markcaron said there were some possible issues with decimal precision.

bumping previous question re decimal @libbylevi. Am I clear to proceed?

Gonna merge and we'll open issues for the other stuff


feat: SQL Database support

Is this missing migrations support?

Is this missing migrations support?

implemented now


Pass in Questions to Ground Truth Matching

According to UpTrain's documentation, questions is necessary.
If it is not passed in, it errors.
2024-03-10 21:10:53.253 | ERROR    | uptrain.framework.remote:raise_or_return:32 - {"detail":"Error running the evaluation: 500: Error running the evaluation: concurrent.futures.process._RemoteTraceback: \n\"\"\"\nTraceback (most recent call last):\n  File \"/usr/local/lib/python3.10/concurrent/futures/process.py\", line 246, in _process_worker\n    r = call_item.fn(*call_item.args, **call_item.kwargs)\n  File \"/app/uptrain_server/worker.py\", line 429, in _run_log_and_eval\n    res = func(settings, dataset, **filtered_args)\n  File \"/app/uptrain_server/evals/chatgpt.py\", line 1534, in score_response_matching\n    question = row[\"question\"]\nKeyError: 'question'\n\"\"\"\n\nThe above exception was the direct cause of the following exception:\n\nTraceback (most recent call last):\n  File \"/app/uptrain_server/worker.py\", line 959, in run_eval_v2\n    result = future.result()\n  File \"/usr/local/lib/python3.10/concurrent/futures/_base.py\", line 451, in result\n    return self.__get_result()\n  File \"/usr/local/lib/python3.10/concurrent/futures/_base.py\", line 403, in __get_result\n    raise self._exception\nKeyError: 'question'\n"}
2024-03-10 21:10:53.254 | ERROR    | uptrain.framework.remote:evaluate:74 - Evaluation failed with error: Server error '500 Internal Server Error' for url 'https://demo.uptrain.ai/api/open/evaluate_no_auth'
For more information check: https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/500

More changes elsewhere might be needed.

@shadeMe can you take a look at this?

@lbux Our integration currently only supports uptrain==0.5.0. Are you sure you're using this version of the dependency in your env?

@lbux Our integration currently only supports uptrain==0.5.0. Are you sure you're using this version of the dependency in your env?

Thanks for the info. I'll take a look at what version of uptrain is being used. I don't recall any other package potentially conflicting with uptrain as I just installed it with the pip install uptrain-haystack command which, if my understanding is correct, specifies uptrain==0.5.0 as I didn't see it elsewhere in the documentation?

Confirmed that uptrain is version 0.5.0. @shadeMe

Confirmed that uptrain is version 0.5.0. @shadeMe

Thanks for confirming - We'll investigate. At first glance, it looks like the UpTrain devs have made changes to their upstream server code that breaks existing consumers of their client library.


go 1.18

gsed -i 's/1\.17/1.18/' go.mod .github/workflows/*

Codecov Report

Merging #1187 (ce5f15a) into master (313ccf3) will decrease coverage by 0.01%.
The diff coverage is 37.50%.

@@            Coverage Diff             @@
##           master    #1187      +/-   ##
==========================================
- Coverage   77.39%   77.38%   -0.02%
==========================================
  Files         277      277
  Lines        7813     7817       +4
==========================================
+ Hits         6047     6049       +2
- Misses       1406     1407       +1
- Partials      360      361       +1

Impacted Files
Coverage Δ

...ders/terraform/commons/extract-container-images.go
78.63% <25.00%> (ø)

.../mapper/iac-providers/cft/config/dynamodb-table.go
87.50% <50.00%> (-12.50%)
:arrow_down:

Upgraded to go 1.19 by  #1385


[Epic] Improve documentation and make odo.dev ready for 3.0 GA

[x] https://github.com/redhat-developer/odo/issues/5842
[x] https://github.com/redhat-developer/odo/issues/5860

Can we close this? @kadel

/close


[DP-393] ORM Mapped entities extracted from Riak KV do not contain ke…

…y and index fields

:+1:


Is it possible to lazy load components and use them in TSX?

const LazyComp = () => import('@/LazyComp');

and somewhere below in render function:
<LazyComp />

Runtime is ok, but Typescript is not:
JSX element type 'Promise<typeof import("path/to/LazyComp")>' is not a constructor function for JSX elements.
  Type 'Promise<typeof import("path/to/LazyComp")>' is missing the following properties from type 'Element': isRootInsert, isComment

Currently, async components are not supported.
As a workaround, you can let async components pretend normal component like below.
export function pretendNormalComponent<A extends Promise<typeof Vue>>(
  factory: () => A
): A extends Promise<infer V> ? V : never {
  return factory as any;
}

const LazyComp = pretendNormalComponent(() => import("@/LazyComp"));

Leave this issue opened until async component will be supported formally.

I tried this but got an issue.
Severity	Code	Description	Project	File	Line	Suppression State
Error	TS2322	(TS) Type 'Promise<typeof import("C:/dev/IO-Board.Management.Portal/apps/IO-Board.Management.Portal/src/components/OLMap")>' is not assignable to type 'Promise<VueConstructor<Vue>>'.
  Type 'typeof import("C:/dev/IO-Board.Management.Portal/apps/IO-Board.Management.Portal/src/components/OLMap")' is missing the following properties from type 'VueConstructor<Vue>': extend, nextTick, set, delete, and 9 more.	C:\dev\IO-Board.Management.Portal\apps\IO-Board.Management.Portal (tsconfig or jsconfig project)	C:\dev\IO-Board.Management.Portal\apps\IO-Board.Management.Portal\src\pages\index.tsx	14	Active

The component look like:
@Component
export default class OLMap extends tsx.Component<OLMapOptions>{
...
}

Marked in Bold is what helped me to achieve the same.
import("./lib/select-list").then((m) => m.default)
More details follows:
export function pretendNormalComponent<A extends Promise<typeof Vue>>(
  factory: () => A
): A extends Promise<infer V> ? V : never {
  return factory as any;
}

const EmployeeList = pretendNormalComponent(
  () => import("./lib/select-list").then((m) => m.default)
);
export { EmployeeList };

My Component look like
import Vue from "vue";
import { VNode } from "vue";
import Component from "vue-class-component";
import * as tsx from "vue-tsx-support";

@Component
export default class EmployeeList extends Vue{
  _tsx!: tsx.DeclareProps<
    tsx.PickProps<
      EmployeeList,
      | "store"
      | "label"
      | "rules"
    >
  >;
}


Update date

Hi @beckylino, 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 (borooji). 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;


Recipe selector bug

Recipe selector dropdown on main page shows "recipe" when there is only one way to produce the item selected in the item selector dropdown.

Added logic to remove dropdown options when there is only one recipe available for the selected item. May iterate on this further when app is more developed.


didn't run

Due to the default settings of Windows, you could not direct  run PowerShell Script.
See  about_Execution_Policies


About python-fbxsdk modules

Trying to convert .pkl files from AIST++, I`m troubling with some classes
I guess it is from imported packages from FbxCommon.
2020 version would be fine? and I wonder if I can know how did you installed fbxsdk
Autodesk provides diffrent ways

Install fbxsdk and wrapp with python bindings
install python-fbxsdk
which one did you get?
I think it would help my problem

Hello,
I use python-fbx sdk. Here's the step to install it:

Install FBX Python SDK from here: https://www.autodesk.com/developer-network/platform-technologies/fbx-sdk-2020-0. I use the 2020.0.1 version.
Follow https://download.autodesk.com/us/fbx/20112/fbx_sdk_help/index.html?url=WS1a9193826455f5ff453265c9125faa23bbb5fe8.htm,topicNumber=d0e8312. Basically, you have to move <yourFBXSDKpath>\lib\<Pythonxxxxxx>\ into the right directory.
Change the 'ascii' in FbxCommon::SaveScene to 'binary'. The fbx-ascii file format loads and saves slower than the binary format.
The python-fbx sdk might only work with python 3.7. If you keep facing problems, try to use python-3.7.

OMG, I succeed!!!
For posterity,
I did follow the same instruction as they explained and double checked,
but trying to import fbx.so, terminal says 'no module named fbxsip'
So, I trying to import fbxsip.so by command
import fbx.fbxsip
and then trying to import fbx.so, but again, it says 'no module named fbxsip'
I solved this problem by pulled every items out side of the packages
I don`t know why python-fbxsdk is not working with packages but working with independent modules
(before solved the problem)
<(conda)site-pakcages>
| --numpy
| --tqdm
| --fbx
| --fbx.so
| --FbxComm.py
| --fbxsip.so
(after solved the problem)
<(conda)site-pakcages>
| --numpy
| --tqdm
| --fbx.so
| --FbxComm.py
| --fbxsip.so

hi, are you use windows platform? it seems that I can not download the paper anymore. if possible do you mind share the .so .py files here? thanks, it seems that they make changes to the exe file in their website.

@innopeak-zhangsihao-yang  I did it with Widows. Recently, I moved AI to FE engineer. I'll looking for the computer I used in a week(may take some time..) :)


HARP-7582 Move IBCT utils to /coresdk

Signed-off-by: Arkadiusz Spiewak<EMAIL_ADDRESS>Thank you for contributing to harp.gl!
Before requesting a pull request, please remember to check the following documents:

contribution guidelines
coding style

If you are adding new functionality we would highly appreciate if you can describe what is the capability you are adding and even better if you can add some examples. Please also remember to add tests for it.
CI Check
Our bots will check whether your PR can be directly integrated into the mainline. We have some internal integration tests running on the background, our bots will inform you of the next steps and someone from our team will take a look and help if needed!
And please do not forget to sign-off your commit! You can read more about DCO here. But, in short, you just need to use git commit -s or append --signoff when you are committing to the repo.
Happy contributing!

Codecov Report

Merging #947 into master will decrease coverage by 0.36%.
The diff coverage is 11.47%.

@@            Coverage Diff             @@
##           master     #947      +/-   ##
==========================================
- Coverage   48.12%   47.76%   -0.37%
==========================================
  Files         231      246      +15
  Lines       21702    22146     +444
  Branches     4942     5017      +75
==========================================
+ Hits        10444    10577     +133
- Misses      11258    11569     +311

Impacted Files
Coverage Δ

@here/harp-test-utils/lib/rendering/FeedbackCli.ts
0% <0%> (ø)

@here/harp-test-utils/lib/rendering/HtmlReport.ts
2.53% <2.53%> (ø)

...re/harp-test-utils/lib/rendering/FeedbackServer.ts
21.97% <21.97%> (ø)

...re/harp-test-utils/lib/rendering/FeedbackCommon.ts
31.57% <31.57%> (ø)

@here/harp-materials/lib/Utils.ts
20% <0%> (-80%)
:arrow_down:

@here/harp-materials/lib/IconMaterial.ts
44.44% <0%> (-55.56%)
:arrow_down:

@here/harp-map-controls/lib/Utils.ts
46.15% <0%> (-23.85%)
:arrow_down:

@here/harp-omv-datasource/lib/OmvTiler.ts
50% <0%> (-16.67%)
:arrow_down:

@here/harp-utils/lib/Logger/ConsoleChannel.ts
53.84% <0%> (-16.16%)
:arrow_down:

@here/harp-utils/lib/ObjectUtils.ts
83.33% <0%> (-10.22%)
:arrow_down:

... and 33 more

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 67022cd...d31a2a5. Read the comment docs.

@heremaps-bot retest this please

@heremaps-bot retest this please

@heremaps-bot retest this please


Update Review app to import govuk-frontend via local package

This PR makes the Review app a user of govuk-frontend as part of:

https://github.com/alphagov/govuk-frontend/issues/3280

For the performance work all source code and build artifacts can now be resolved from a single package
Additionally, the Review app now follows our own documentation:
https://frontend.design-system.service.gov.uk/importing-css-assets-and-javascript/
These areas in particular:
Import CSS, assets and JavaScript

Simplify Sass import paths
Import JavaScript using a bundler

Which means the Review app now imports govuk-frontend ESM JavaScript for the first time, without having to navigate to ../../../src sources or rely on a separate review-specific UMD bundle
Package directory changes
Previously npm link only resolved the pre-built packages files but they're now consolidated:
Before
├── app
│   ├── src
│   └── dist
└── package
    ├── govuk
    ├── govuk-esm
    ├── govuk-prototype-kit
    ├── package.json
    └── README.md

After
└── packages
    ├── govuk-frontend
    │   ├── src
    │   │   ├── govuk
    │   │   └── govuk-prototype-kit
    │   ├── dist
    │   │   ├── govuk
    │   │   ├── govuk-esm
    │   │   └── govuk-prototype-kit
    │   ├── package.json
    │   └── README.md
    └── govuk-frontend-review
        ├── src
        └── dist

~src~ → packages/govuk-frontend/src
~package~ → packages/govuk-frontendpackage/dist
To maintain backwards compatibility these directory changes aren't found in the published package.json
The problem with dist
Unfortunately the standard convention of building src to dist doesn't fit
We already reserve ./dist for our GitHub tagged releases, do we need to move it?
Will it be confusing to have a committed ./dist alongside ./package/src → ./package/dist build output?
Some options:

dist — Leave it where it is
~dist~ → package/release — Maintain two build directories under ./package
~dist~ → package/dist/release — Consolidate single build directory under ./package

This PR has currently picked 1) from the list above

Having the app consume govuk-frontend itself, however, I'm with Brett with it looking like a big change to enable the performance work. I'm not clear about what it enables that was blocked before, so I'd welcome some more details about that, please 😄
I'm wondering if there's a shorter route we may take to enable us to ship v5 (even if it means more manual checks, less isolation between the packages while we ship it), before we look into finishing re-organising our internal repository structure once it's shipped 😊

@romaricpascal Sounds good, give me a nudge when you're free

Hi @romaricpascal @domoscargin
This PR was split out into related-but-separate PRs for:

https://github.com/alphagov/govuk-frontend/pull/3560
https://github.com/alphagov/govuk-frontend/pull/3562
https://github.com/alphagov/govuk-frontend/pull/3491 ← current PR
https://github.com/alphagov/govuk-frontend/pull/3498

Do you see anything missing?
I've added a README (and symlinks) to explain the src move too:
https://github.com/alphagov/govuk-frontend/tree/review-app-user/src

Also worth popping a reminder here that this PR means we have to update our Decision on repo structure: https://github.com/alphagov/govuk-design-system-architecture/pull/24
(I see @36degrees has just added that to the board as well)

Agree with Brett on notifying people before we merge it, and making sure we don't wait too long before rebasing the PRs that still need rebasing as well 😊

Agree with Brett on notifying people before we merge it, and making sure we don't wait too long before rebasing the PRs that still need rebasing as well 😊

Thanks @romaricpascal
We rebased all these earlier:
cssnano-autoprefixer (#3243)
delete-package-dist (#3498)
remove-compat-mode-legacy-colours (#3576)
remove-compat-mode-legacy-fonts (#3574)
remove-ie8-css (#3572)
remove-ie8-js (#3570)
remove-typography-use-rem-setting (#3575)
review-app-user (#3491)


docs(guide/Templates): describe your change...

What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
Adding a title to the page for consistency

What is the current behavior? (You can also link to an open issue here)
Not title

What is the new behavior (if this is a feature change)?
A title

Does this PR introduce a breaking change?
No

Please check if the PR fulfills these requirements

[ ] The commit message follows our guidelines: https://github.com/angular/angular.js/blob/master/CONTRIBUTING.md#commit-message-format
[ ] Tests for the changes have been added (for bug fixes / features)
[ ] Docs have been added / updated (for bug fixes / features)

Other information:

Adding in the title for consistency

I signed it!


Add starting message

Hi! I just added a basic starting message. After running of mist, output will be
Starting Mist monitor...
TCP address: <IP_ADDRESS>:1445
HTTP address: <IP_ADDRESS>:8080

This looks great! Thanks for your help.


Adds Support for Safari Pinned tabs

This closes #192 by adding the SVG and required html snippet.
The SVG was cut out from https://en.wikipedia.org/wiki/File:Gov.uk_logo.svg as I couldn't find a similar SVG in the repo.

looks nice! :fire:

When does this SVG get downloaded? Do other browsers ignore the file?
I agree it looks nice, but is it necessary page weight for the feature it adds?

Yet another apple icon with a weird offstandard meta tag aha.
Can see the support for other browsers here: https://github.com/whatwg/html/issues/110
I agree, if it's adding to the page weight it's not needed. Apparently there's a cache for the SVGs but still, favicons seem to suffice.

As it’s got a mask-icon rel other browsers don’t seem to proactively download this resource (or at least Firefox and Chrome don’t). I’d be happy to see this go in, especially seeing as we already do touch icons.


Dockerize the converter

Add application to the container. Resolves #39
Additionally, you can run container as a daemon with "docker run -d -p 5000:5000 external_doc_pdf_converter" but then you should figure out the ip address on your own with "docker ps"

Please try to fix the linter errors


Make readme visible on pypi

Makes the readme file visible on pypi via setting the long description

Yeah , perhaps I should actually add the file I need.


FIX use redirect_stdout in get_sys_info for windows

@Badr-Moufad I tested on windows and it fixed the problem you had (that I could reproduce)

Codecov Report

Merging #390 (8476324) into main (1ecd1c9) will increase coverage by 0.01%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##             main     #390      +/-   ##
==========================================
+ Coverage   56.09%   56.11%   +0.01%
==========================================
  Files          42       42
  Lines        2519     2520       +1
  Branches      476      476
==========================================
+ Hits         1413     1414       +1
  Misses       1006     1006
  Partials      100      100


[redditr] Fix extraction of i.redd.it animated GIFs

Before submitting a pull request make sure you have:

[x] At least skimmed through adding new extractor tutorial and youtube-dl coding conventions sections
[x] Searched the bugtracker for similar pull requests
[x] Checked the code with flake8

In order to be accepted and merged into youtube-dl each piece of code must be in public domain or released under Unlicense. Check one of the following options:

[x] I am the original author of this code and I am willing to release it under Unlicense
[ ] I am not the original author of this code but it is in public domain or released under Unlicense (provide reliable evidence)

What is the purpose of your pull request?

[ ] Bug fix
[x] Improvement
[ ] New extractor
[ ] New feature

When a Reddit post embedded an i.redd.it animated GIF, youtube-dl would download the raw GIF, even though better format (MP4) was available.
Before:
$ youtube-dl https://www.reddit.com/r/WatchPeopleDieInside/comments/7kb915/first_of_all/
[RedditR] 7kb915: Downloading JSON metadata
[generic] aspakv7pfvry: Requesting header
WARNING: Falling back on generic information extractor.
[generic] aspakv7pfvry: Downloading webpage
WARNING: URL could be a direct video link, returning it as such.
[download] Destination: First of all...-aspakv7pfvry.gif
[download] 100% of 17.72MiB in 00:00

After:
$ youtube-dl https://www.reddit.com/r/WatchPeopleDieInside/comments/7kb915/first_of_all/
[RedditR] 7kb915: Downloading JSON metadata
[download] Destination: First of all...-7kb915.mp4
[download] 100% of 945.60KiB in 00:00

Ho-hum, 022d336e9213f17846838b9a9bb556d8f0b1a846 doesn't work for some links, for example:
https://www.reddit.com/r/ProgrammerHumor/comments/7kk22g/what_working_with_css_feels_like/
The anti-gif-bot somehow got its hands of the MP4:
https://www.reddit.com/r/ProgrammerHumor/comments/7kk22g/what_working_with_css_feels_like/dreyplg/
No sure how it managed to do that. :-/

Ho-hum, 022d336e9213f17846838b9a9bb556d8f0b1a846 doesn't work for some links, for example:
https://www.reddit.com/r/ProgrammerHumor/comments/7kk22g/what_working_with_css_feels_like/

I still don't understand what's going on, but I implemented fallback so that at least you get something when this happens.
I also fixed the problems pointed out in the review.


ENH: automatically test that examples run

RN I have to run them manually and sometimes I don't notice that they break
Check how it's done in sklearn

addressed in #142


$request->getBody() returns empty stream

When I use $request->getParsedBody() everything works fine, but when I use $request->getBody() it returns just empty stream. According to geggleto it looks like the stream gets detached at some point.
demo: source, output

Maybe something with the pointer already being at the end after parsing the body?

*rewind()*ing didn't help so I don't think that's the problem

https://github.com/slimphp/Slim/blob/3.x/Slim/Http/Stream.php#L181
shows that the contents of the stream are returned, thus theres nothing left in the string.
slim uses getParsedBody internally which is why if its a parsable item the body is left empty.
Rewinding does not help because PHP is dumping the content as it reads it as its basically a byte buffer.
Only in a file implementation could you rewind since the data is on disk and not in memory.
I do believe this to be a bug in our implementation.
Upon Request class initialization the stream should be read in full and stored in a protected attribute, then it can be returned at will via __toString and getContents()

But how to make getBody() functional and remain PSR-7 compliant? getParsedBody(), which consumes the original stream, gets called all over the place and getBody() should return StreamInterface. Storing the contents in the Request class won't help either because string is just not StreamInterface. Maybe some kind of cached Stream, but i don't know if that's a proper way to do things. In the end I never really used PHP more than needed.

As @geggleto mentioned according to php.net php://input can be read only once, because right now there is no support for a seek operation. I think there is a really simple solution of just dumping the whole body into a string and then creating a stream from it. Not really a clean solution, but I can't seem to find a better one.

:+1: This is pretty much what I was thinking in terms of a solution.

//cc @akrabat

@Outfl3sh The tip of the 3.x branch should fix this issue for you.

Great, thanks for the fix.


[SPARK-38362][BUILD] Move eclipse.m2e Maven plugin config in its own profile

What changes were proposed in this pull request?
Move org.eclipse.m2e:lifecycle-mapping in its own Maven profile
https://stackoverflow.com/a/23707050/497381
Why are the changes needed?
This Maven "plugin" is needed only inside Eclipse when M2E plugin is being used to map Maven lifecycle with Eclipse's one.
There is no need to bother non-Eclipse users' build with warnings like:
WARNING] The POM for org.eclipse.m2e:lifecycle-mapping:jar:1.0.0 is missing, no dependency information available
[WARNING] Failed to retrieve plugin descriptor for org.eclipse.m2e:lifecycle-mapping:1.0.0: Plugin org.eclipse.m2e:lifecycle-mapping:1.0.0 or one of its dependencies could not be resolved: org.eclipse.m2e:lifecycle-mapping:jar:1.0.0 was not found in https://maven-central.storage-download.googleapis.com/maven2/ during a previous attempt. This failure was cached in the local repository and resolution is not reattempted until the update interval of gcs-maven-central-mirror has elapsed or updates are forced

Does this PR introduce any user-facing change?
No!
How was this patch tested?
Local dev environment.

Merged to master.

Can one of the admins verify this patch?


Feature Suggestions (Microsoft.Data)

I'm excited about this work! I've been using python for a while and while overall a vast improvement over R for my data analysis, it can still be lacking.
FYI I'm an academic with almost no formal training in computer science. Please forgive me for any opinions I have that are uninformed. I think my feature requests would get you a lot more interest from the academic community.
Increased IO support?
I think that if you want a lot of people to try it out the more formats, you support the more people will try it out. File IO is an easy excuse to not try out alternatives especially when there are larger files.
These file formats would be very handy for getting attention from a lot academics if you had them all (in order of my preference)?

.parquet ideally (you'll need gzip, snappy support and I'm personally a big fan of zstd compression for parquet). Here is a repo that deals with parquet files
json
rdata, .rda for R
Stata .dta format a lot social scientists use Stata. I think Stata is ripe for a quick death if someone else can make a lot of effort to make doing statistics easy like stata is.
feather (my understanding is that is a lot like parquet but quick and not meant for long-term storage)

Statistics built in or as a side package that is easy to access
Or at least included in some future documentation. For example you could make it very easy to do basic correlations, ANOVAS, linear and logistic regression eceterea. I would like to also see the opportunity to pull out pretty much any part of the calcuations along with a lot of accompaning staistics. Also, being able to output the resutls in an easy to read format would help a lot too.
Again this is all from a very academic perspective if that is not who you're targeting I completely understand. Either way good luck!

I almost forgot. Missing values I saw some discussion about if you people wanted missing values to be the same across different data types. I think it would be fine if there were options for both that would be fine. However, again as a non-computer scientist having several kinds of missing values for different columns is a major pain! Pandas has realized this too and are working towards a unified(ish) missing type. I would really like to see something similar here as well. If I don't what to see the type difference for the missing values that would save me a ton of time. My data is never as clean as a lot of businesses deal with, missing values are everywhere so I just have to deal with them. This makes my life a lot easier. R and Julia both do this as well.
Again, good luck!

Great feedback! About the IO file support, I'm thinking about starting a DataFrameIO project that deals with the different IO formats. My hope is that we can seed a few formats and the community can contribute to the other ones.
Can you elaborate more on the different types of missing values you are encountering? AFAIK, we support missing values for all column types the same way in DataFrame: as null values. So in our case, both a float column and an int column will have null values representing missing values. Any operations on them will have effect on the column type. This does mean that we don't differentiate between null values and missing values though. Is that part of what you mean?

First off, I think the separate DataFrameIO project is a great idea. It never ceases to amaze me how difficult IO can be when trying out some languages. The more this gets streamlined and easy to deal with, the faster the cleaning and analysis can happen.
As for the missing values, I wasn't really sure I tried looking through your documentation and I must have misinterpreted something. It looks like you're already doing what I was talking about. Though just to make sure, a null would work for a string or bool or all other types of columns too, right?

Yup. null works for string, bool and the numeric column types. There's actually strong unit tests for this :)

Perfect! And thank you for your patience with my lack of experience with c#/dotnet etc.

With DataFrames being based on Arrow, first class support for Parquet would be great. This is currently accomplished in dotnet/spark with Spark (java/scala) doing the Parquet -> Arrow conversion. Being able to use dataframes + parquet locally (ie run non-distributed jobs) using the same implementation (on dataframes) would be open up a lot of use cases.


optimize business param empty check

Signed-off-by: wufan<EMAIL_ADDRESS>
Describe what this PR does / why we need it
Does this pull request fix one issue?
fix and optimize #214
Describe how you did it
Describe how to verify it
Special notes for reviews

Since the relevant codes has been modified, I will close the PR fist, thank you for your contribution.


Update slick, slick-hikaricp to 3.5.0

About this PR
📦 Updates

com.typesafe.slick:slick
com.typesafe.slick:slick-hikaricp

from 3.4.1 to 3.5.0
📜 GitHub Release Notes - Version Diff
Usage
✅ Please merge!
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

🔍 Files still referring to the old version number
The following files still refer to the old version number (3.4.1).
You might want to review and update them manually.
website/yarn.lock

⚙ Adjust future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "com.typesafe.slick" } ]

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequests = { frequency = "30 days" },
  dependency = { groupId = "com.typesafe.slick" }
}]

labels: library-update, early-semver-minor, semver-spec-minor, version-scheme:pvp, old-version-remains, commit-count:1

Superseded by #790.


[analyzer/compiler/spec] catch clause parameters support optional trailing commas?

@munificent pointed out in https://github.com/dart-lang/dart_style/issues/1424 that the parameters of a catch clause support an optional trailing comma:
main() {
  try {} catch (e, s,) {}
  print("foo");
}

The analyzer emits an error, but we can still compile this program as if it had no errors:

Running it prints foo.
 The parameters of a catch clause are not expressions. They are either one or two identifiers separated by a comma. I think they shouldn't feel like expression lists, because they aren't, and they are usually short, so a trailing comma would add very little benefit to most users.

CC @munificent @eernstg but I'm happy to call this an analyzer issue.

Note that a single identifier with a trailing comma is not supported, that is, the analyzer reports an error and DartPad rejects compilation of such a construct.
Calling the example program an analyzer-only-issue would introduce a weird inconsistency between other similar constructs:
void a() {
  try {} catch (e) {} // Legal!
  try {} catch (e,) {} // Illegal? Today, this is rejected by the analyzer and during compilation.
  try {} catch (e, s) {} // Legal!
  try {} catch (e, s,) {} // Legal? Today, this is rejected by the analyzer but not during compilation.
  assert(a); // Legal!
  assert(a,); // Legal!
  assert(a, m); // Legal!
  assert(a, m, ); // Legal!
  f(a); // Legal!
  f(a,); // Legal!
  f(a, m); // Legal!
  f(a, m, ); // Legal!
}

So to me it looks like the most reasonable two choices are the following:
1. trailing commas are unsupported
It's not an analyzer issue and (e, s,) should be rejected during compilation. The spec needs no adjustments.
2. trailing commas are supported
It's a compiler, analyzer and spec issue. Both need to allow trailing commas for one and two identifiers.

the spec needs to be adjusted to support trailing commas in the one and two identifier case
the compiler needs to add support for trailing commas in the one identifier case and continue to support compilation for the trailing comma in the two identifier case
the analyzer needs to not report any issues when it encounters trailing commas in the one and two identifier case

I think trailing commas in <catchPart> is a new proposal. I created https://github.com/dart-lang/language/issues/3672 to handle the discussion about this proposal. The proposal I put there does support the trailing comma for both one and two identifiers in the <catchPart>.

I just filed https://github.com/dart-lang/sdk/issues/55301 before noticing this issue, but I guess it's a duplicate. I'll leave it open for now because I think it's a little clearer to implementation folks that this is an implementation bug as it currently stands, but we can merge these issues at some point.

Analyzer still does not accept this (not yet accepted) syntax.


fix product cannot be updated in ocp upgrade failure case

Signed-off-by: Zhiwei Yin<EMAIL_ADDRESS>

/retest

/assign @elgnay

/lgtm

/cherry-pick release-2.4


insim: Packet should probably be non_exhaustive

Already was. Proof I shouldn't just log issues as reminders immediately after waking up!


[Workbox] New third-party plugin section

R: @philipwalton
CC: @tpiros from Cloudinary as an FYI.
This adds a new "Third-party Plugins" section to the Workbox docs, with some general info about publicizing your plugins, and specific info about the plugin that Cloudinary created.

Whoops!
There were 3 warnings that will prevent this PR from being merged. Please take a look, and either fix, or provide a justification for why they can't be fixed.
WARNINGS
src/content/en/tools/workbox/guides/using-plugins.md#L156 - Consider adding a "was this page helpful?" widget to your page: https://developers.google.com/web/resources/widgets#helpful
src/content/en/tools/workbox/guides/using-plugins.md#L47 - Common typo found: 'javascript' Should it be 'JavaScript'?
src/content/en/tools/workbox/guides/using-plugins.md#L95 - Common typo found: 'javascript' Should it be 'JavaScript'?

This is awesome @jeffposnick . I will also investigate the idea on writing an article about the experience of creating the plugin.

:tada: This has been pushed live to https://developers.google.com/web/


create puray pkg (manage all file in puray folder)

Great idea to implement animation. I'm thinking how to integrate this without impacting people who need the original tutorial. How about a separate branch?

I am also following your tutorial...
ok.. to create a separate branch


CMLK-1552 Excludes unwanted snappy-java version from transitive kafka-clients and sets the desired version

CMLK-1552
Camel K (camel-k-1.10.5 : CK6) CVE backlog verification

@oscerd Can you merge ?
Thanks


[Enhancement] count distinct mv can rewrite when missing group by has equal predicate

mv: select a, b, c, count(distinct d)  from emps group by a, b, c
query: select a, count(distinct name)  from emps where b=0 and c=0 group by a
this query could rewrite when b/c all have equal predicate, because doesn't have rollup.
What type of PR is this:

[ ] BugFix
[ ] Feature
[x] Enhancement
[ ] Refactor
[ ] UT
[ ] Doc
[ ] Tool

Checklist:

[x] I have added test cases for my bug fix or my new feature
[ ] This pr will affect users' behaviors
[ ] This pr needs user documentation (for new or modified features or behaviors)

[ ] I have added documentation for my new feature or new function

Bugfix cherry-pick branch check:

[x] I have checked the version labels which the pr will be auto-backported to the target branch

[x] 3.1
[x] 3.0
[ ] 2.5
[ ] 2.4

[FE PR Coverage Check]
:heart_eyes: pass : 17 / 17 (100.00%)
file detail

path
covered_line
new_line
coverage
not_covered_line_detail

:large_blue_circle:
com/starrocks/sql/optimizer/rule/transformation/materialization/AggregatedMaterializedViewRewriter.java
17
17
100.00%
[]

@Mergifyio backport branch-3.1

@Mergifyio backport branch-3.0


Whitespaces in organization, project & repo names not allowed

We have a whitespace in our project name: Test App. Thus the uri resolves to https://dev.azure.com/test-org/Test App/_apis/git/repositories/Test App/stats/branches?name=dev which is considered as invalid uri by the ruby RFC3986_Parser. Our uri doesn't match the used regex: see code.

For now it's sufficient to not use whitespaces in project and organization names but it would be nice if dependapot could escape whitespaces before passing the uri to the ruby parser. Moreover a comment in the docu would be helpful.
My ruby skills are limited but I think it already works if repo_name (code) is encoded e.g. with repo_name= URI.encode("#{organization}/#{project}/_git/#{repository}").

Resolved in https://github.com/tinglesoftware/dependabot-azure-devops/commit/9dec0f90d9b2a7f1c00aa09f5fb1b0c12e973f85

Released (https://github.com/tinglesoftware/dependabot-azure-devops/releases/tag/0.1.4)


lazy loading / dynamically changing days array

Hello,
I'm trying to implement a lazy loading for a week view, by having a scrolleable div with 21 days, and only 7 visible, alert me when the view is near the start or the end of the scroll.
Is there a way to append new days (before or after) in the days array of the clndr object?
Thanks for all.

Unfortunately clndr isn't built this way— calling render destroys any previous markup you had.
The only way I can think of to explore this would be to have a clndr instance hiding somewhere on the page, controlled via the API, and grabbing the markup output from it after it renders using the doneRendering callback. That would allow you to lazily render other months and append them to the actual view.
Did that make any sense?

Closing this, feel free to open it back up if you have any other questions or thoughts.


Tutorial Page cp-aibus-dox-ui-schema-custom.md Issue. PROD

Tutorial issue found: https://github.com/sap-tutorials/Tutorials/blob/master/tutorials/cp-aibus-dox-ui-schema-custom/cp-aibus-dox-ui-schema-custom.md Your tutorial was not created on the site. Please ensure there is an experience tag among the assigned tags.
Affected server: PROD

Issue resolved.


Disable recommended extensions view

There is a setting 'extensions.ignoreRecommendations' which I believe inhibits the recommended extension notifications.
Could this also be used to ignore the recommend extensions view in the side bar? Everytime I open a new workspace I end up hiding the view from the side bar.
Either it should remember that I've hidden it or the setting should apply to both.

Everytime I open a new workspace I end up hiding the view from the side bar.

The extensions view doesnt open by default. Do you mean that whenever you open a new workspace and then open the extensions view, you hide the "Recommended" section and only keep the "Installed" section?

Yes - that's right. I like the recommendations, but all my projects are C++, so I get the same recommendations every time. 8-)

I am trying to understand your workflow here...
When you open a new workspace and go the the extensions view, what is your intention? To search for new extensions to install? If yes, then how does the existence of the recommended view matter? The second you start typing the search text, both the "Installed" and "Recommended" view go away.
Are you instead referring to the need to remove individual items from the recommended view?

It's usually to enable or disable extensions. I have some workspaces where I need some C++ extensions and some which I don't. I also develop some extensions, so I tend to disable the 'official' versions in order to link the dev versions.
It's not a huge problem, it's just that I already have the extensions that I want, so I don't need the recommendations. I thought I had disabled the view when I set 'extensions.ignoreRecommendations', but I realised that this is for the popup notifications. It's just a bit confusing.

I thought I had disabled the view when I set 'extensions.ignoreRecommendations', but I realised that this is for the popup notifications. It's just a bit confusing.

Yes, I agree that the setting is a little confusing. It was more confusing before :). I recently updated the description on it to say   // If set to true, the notifications for extension recommendations will stop showing up. to make it more clear that the setting is about the notifications.

Either it should remember that I've hidden it or the setting should apply to both.

The recommendations that show up in the notifications/popups are a very small subset of the recommendations that show up in the view, so we cant re-use the same setting to hide the recommendations view.
VS Code does remember your choice (either collapsing the view or resizing it), but it remembers this for each workspace and not at a user level.
@sandy081 Any reason we store the state of the sections in the extensions (or explorer for that matter) at workspace level instead of global level?

@ramya-rao-a With 1.20 we store the extensions visibility state globally. But expansion state and the order is still workspace level.

@Gruntfuggly In 1.20 you can right click on the "Recommendations" section and choose to hide it. Like @sandy081 mentioned this state is retained across workspaces.
@sandy081 I don't see this feature covered anywhere in the release notes. Can you link the issue that was tracking it? Also, I couldn't find a way to bring back the hidden section

@ramya-rao-a This is not a big feature and is mentioned as a notable fix.  https://github.com/Microsoft/vscode/issues/35462
You can right click on the viewlet title area to select the views to show.

Thanks @sandy081
@Gruntfuggly https://github.com/Microsoft/vscode/issues/35462#issuecomment-360512568 should help you


Catalog template README doesn't update when switching between templates

If I view a template from the UI and switch to another using the dropdown in the top left the README won't update.

Duplicate of #6470


Referenda proposal not moving to confirming automatically

Is there an existing issue?

[X] I have searched the existing issues

Experiencing problems? Have you tried our Stack Exchange first?

[X] This is not a support question.

Description of bug
We had a proposal that people voted for and had enough vote/support to pass at a future time.
Once that time was reached, the referendum stayed in "deciding", and I also saw the scheduler being triggered (by the alarm if I understood correctly).
12h later, I decided to try to vote again (with insignificant amount) and it passed it to "confirming".
Is that expected ?
I thought the alarm system was there to trigger the change when the threshold was supposed to be reached
(Also, there might have been some conviction vote delegation removed after the last vote was done during the deciding period which might be the reason the alarm didn't do anything once executed)
Steps to reproduce
No response

CC @kianenigma @ggwpez

Possibly fixed by #13704

Possibly fixed by #13704

any confirmation on this?

@kianenigma We didn't upgrade yet (probably another 2 months before this fix reaches prod), but the issue happened again today:

on Moonriver (Kusama) https://polkadot.js.org/apps/?rpc=wss%3A%2F%2Fwss.moonriver.moonbeam.network#/referenda
{
  Ongoing: {
    track: 0
    origin: {
      system: Root
    }
    proposal: {
      Lookup: {
        hash_: 0x31b4bd6249363c0ace1bef13719d2f3b531c95ff883209ff96dbe78cb41eaf96
        len: 188
      }
    }
    enactment: {
      After: 100
    }
    submitted: 3,867,858
    submissionDeposit: {
      who: 0x381d106C440F92654827D2B2c637Dd5B38A362A7
      amount: 10,000,000,000,000,000,000
    }
    decisionDeposit: {
      who: 0x381d106C440F92654827D2B2c637Dd5B38A362A7
      amount: 100,000,000,000,000,000,000,000
    }
    deciding: {
      since: 3,875,058
      confirming: null
    }
    tally: {
      ayes: 92,537,936,792,079,023,742,502
      nays: 89,000,100,000,000,000,000
      support: 63,219,232,282,079,023,742,502
    }
    inQueue: false
    alarm: null
  }
}

(The referenda passed the required 0.5% support some blocks before the end, but stayed in deciding)
I'm going to vote for it now to see if it moves

And it moved to confirming voting with 1 token:


fs.Unlink -- Promise -- Directory Test

Hello,
There isn't a promise version of a fs.Unlink() --  √ should not unlink directories .
I'd like to be assigned this issue and create the test.

Dupe of #431


Reset travel statistics after Klimaticket is renewed

Currently, it seems that the travel journal simply keeps counting up the ticket prices in the travel statistics and with it the Klimaticket gains. However, these gains should be reset every time the Klimaticket is renewed, because then the price of the ticket has to be gained again as well.
The information about when the Klimaticket is renewed is already there in the profile (given that for the ticket no bonus months or other shenanigans are added). There could also be another page where one can compare the statistics for different validity periods instead of just the current period.

My current use-case looks like this: I set the "Klimaticket start date" in my profile to the start date of my current ticket. That way the "Statistics" and the "Current" travel journal tab should only account for trips with date > that start date.  This has the advantage of supporting special extended tickets (but i guess these are anyway not coming back) and gaps in my ticket if i don't immediately renew it. Of course it has the disadvantages of needing to set this ~ once a year and only having a single archive that are not split up by individual past tickets.
I guess we could support both my and your use case by  automatically making the current start date of the ticket the start day + month of the profile + the current year. Would that work for you?
Statistics and archives per year could then also be added.

Actually, simply setting a new start date manually would be a perfectly acceptable workaround for me. I didn't think of this (and thought that there might be data loss), and there is a high chance that one is reminded to change the date as soon as the statistics don't make sense anymore. If the start date changes automatically after a year, this is just an added bonus.
For historical statistics, one could also simply add multiple validity date ranges to the profile, so instead of using a single text field, each Klimaticket purchase is an additional entry in the database. This would also foresee eventual price increases for the ticket, which would need to be considered in those historical statistics.

Actually, simply setting a new start date manually would be a perfectly acceptable workaround for me. I didn't think of this (and thought that there might be data loss), and there is a high chance that one is reminded to change the date as soon as the statistics don't make sense anymore. If the start date changes automatically after a year, this is just an added bonus.
For historical statistics, one could also simply add multiple validity date ranges to the profile, so instead of using a single text field, each Klimaticket purchase is an additional entry in the database. This would also foresee eventual price increases for the ticket, which would need to be considered in those historical statistics.


Provide comprehensive Qt5.15.7 (LTS, LGPL)

While upstream provides an up-to-date LGPL version with https://github.com/meta-qt5/meta-qt5/commit/2df0f760c200c932cfbb61a0ad684896dfe49e07 recipes for qpdf and qtwebengine still seem to make use of 5.15.10 which is not an LGPL release yet.
Therefore, we need to provide a backport in https://github.com/jhnc-oss/meta-qt5/ which uses 5.15.7 only to circumvent any license issues.

https://github.com/jhnc-oss/yocto-manifests/blob/5.15.7-lts-gpl/default.xml


Google doesn’t work as an IndieAuth delegate

Need to work out why

Google+ is no longer a supported authenticator


problem with file upload

trying to upload a file to an asp.net web app I obtain this error message
An unhandled exception has occurred while executing the request System.IO.InvalidDataException: Missing content-type boundary.
I compared two my app, one using angular 1 and one using angular 2 using chrome tools.
the angular component send this Content-Type:multipart/form-data; boundary=----WebKitFormBoundaryXAIXdwxDD9DS3PsV and it works,
the angular2 component send Content-Type:multipart/form-data and doesn't work ( according chrome tools)
How can I fix it?

this is a problem with the backend server, not this module I guess. Otherwise you can set custom headers also. Please check the docs.

looks like there is a potential issue if I change the custome header of content type, the boundary is not added after the content-type itself.


Disable toDiscordChannel()

Aims to close #1741
Needs testing and discussion about initial implementation before merge.

I'll test it right away. You also need to remove the DiscordWebhook::class from here
https://github.com/nabeelio/phpvms/blob/6b9658a4e37e193e00e5b1f4b1084130a64aaf1c/app/Notifications/Messages/NewsAdded.php#L32

It seems like everything is working. I received the emails, and the Discord notification has been sent. However, it's a bit ugly to have HTML in the Discord notification, but I'm not sure if there's anything we can do about that.

yeah, discord needs markdown formatting as far as I remember and html messes it up.
If we can implement something converting html to markdown, they will look better for sure.

That's exactly what I was looking for

Maybe this ;
https://github.com/thephpleague/html-to-markdown

Yeah I also found this, let me give it a try

The headings aren't converted very well, but it's already better. At least we have paragraphs and lists.

Then we are waiting another PR for it to be added and implemented.
To be honest, headings are ok. At least better than nothing. Rest looks ok as you said, much better compared to what we have now.

Yeah, we'll create another PR for that. I might also try adding tests for notifications. It's happened several times that we realize a notification isn't working, and adding a few unit tests to ensure they work wouldn't be a bad idea, I think.

Ready to merge.


RET-5186 : Added multiples start bulk amend event method

Added a new method, startBulkAmendEventForMultiple, which allows for the starting of the event that returns the correct multiple case type object. Also updated CaseDataBuilder to use GenericRequest in places.
Jira link (if applicable)
Change description
Checklist

[ ] commit messages are meaningful and follow good commit message guidelines
[ ] README and other documentation has been updated / added (if needed)
[ ] tests have been updated / new tests has been added (if needed)
[ ] Does this PR introduce a breaking change

Temp solution for perf test data prep


Update type declaration file

Add comments for each interface and function. This help people when they consume this module as they can see the documenation inline and do not have to look it up online.
Add options for the parser: "trim" and "join"
Add the "stringify" function; as well as the "stringifyBlock", "stringifyBlocks", and "stringifyTag" functions
Add properties on the parsed tag object: "default", "errors", and "tags"
Rename the namespace from "CommentParser" to "parse", as per the official recommendations on a function module. Otherwise, it is not possible to export properties on the exported function.

@blutorange thanks for the great contribution

published<EMAIL_ADDRESS>


1.0.x-dev dont work in Silex 1.3

Earlier everything worked, but now 1.0 also want pimple 3.0, while silex 1.3 use pimple 2.0.
How to fix this?

I think it's due to a mistake in composer.json. I forgot to bump the version. I just publish a v1.0 and v2.0.1 releases to fix that.
Set silex-cache-service-provider dependency to ~1.0 should resolve your problem I think.

Yes! Everything is fine now!
Thank you!


Add tyttp and dependencies

I tested these with a local pack.toml file and they built with
nightly-220527 so I think this should work, but I'm not sure how the
package set gets built so maybe I'm missing something.

These will be included and tested in today's nightly, which I'll add later on today. For your info, I use pack-admin for extracting a new nightly from HEAD and check all packages locally.


[tool_crash] HttpException: Connection closed before full header was received

Command
flutter drive --profile --device-timeout=20

Steps to Reproduce
This happens seemingly at random after the first run of 'flutter drive'. After many attempts I am not able to reproduce the problem on-demand. Once it happens it continues to happen every time. I have tried the following with limited success:
a) flutter clean
b) uninstalling the app from the target device
c) disconnecting and re-connecting the USB cable to the device
d) ensuring the screen on the target device is unlocked
It seems to relate to how long I wait before re-attempting the 'flutter drive' command, it seems like something (maybe on the target device?) is taking time to clean up?
Logs
HttpException

[✓] Flutter (Channel stable, 2.8.0, on Microsoft Windows [Version 10.0.19042.1348], locale en-GB)
    • Flutter version 2.8.0 at C:\Dev\flutter
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision cf44000065 (8 days ago), 2021-12-08 14:06:50 -0800
    • Engine revision 40a99c5951
    • Dart version 2.15.0

[✓] Android toolchain - develop for Android devices (Android SDK version 30.0.3)
    • Android SDK at C:\Dev\Android-SDK
    • Platform android-30, build-tools 30.0.3
    • Java binary at: C:\Program Files\Android\Android Studio\jre\bin\java
    • Java version OpenJDK Runtime Environment (build 11.0.10+0-b96-7249189)
    • All Android licenses accepted.

[✓] Chrome - develop for the web
    • CHROME_EXECUTABLE = C:\Users\Chris Thompson\AppData\Local\Google\Chrome SxS\Application\chrome.exe

[✓] Visual Studio - develop for Windows (Visual Studio Community 2019 16.9.6)
    • Visual Studio at C:\Program Files (x86)\Microsoft Visual Studio\2019\Community
    • Visual Studio Community 2019 version 16.9.31313.79
    • Windows 10 SDK version 10.0.19041.0

[✓] Android Studio (version 2020.3)
    • Android Studio at C:\Program Files\Android\Android Studio
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 11.0.10+0-b96-7249189)

[✓] VS Code (version 1.63.0)
    • VS Code at C:\Users\Chris Thompson\AppData\Local\Programs\Microsoft VS Code
    • Flutter extension version 3.29.0

[✓] Connected device (4 available)
    • GT I9505 (mobile) • 2d03b7aa • android-arm    • Android 5.0.1 (API 21)
    • Windows (desktop) • windows  • windows-x64    • Microsoft Windows [Version 10.0.19042.1348]
    • Chrome (web)      • chrome   • web-javascript • unknown
    • Edge (web)        • edge     • web-javascript • Microsoft Edge 96.0.1054.53

• No issues found!

Flutter Application Metadata
Type: app
Version: 1.0.0+1
Material: true
Android X: false
Module: false
Plugin: false
Android package: null
iOS bundle identifier: null
Creation channel: stable
Creation framework version: ffb2ecea5223acdd139a5039be2f9c796962833d
Plugins
path_provider-2.0.8
path_provider_android-2.0.9
path_provider_ios-2.0.7
path_provider_linux-2.1.4
path_provider_macos-2.0.4
path_provider_windows-2.0.4

Closing this as a duplicate of https://github.com/flutter/flutter/issues/79748


use future to replace latch

In case task failed exceptionally.

Codecov Report

Merging #9030 (654f244) into 3.0 (87f869d) will decrease coverage by 0.12%.
The diff coverage is 66.66%.

:exclamation: Current head 654f244 differs from pull request most recent head 43ffae6. Consider uploading reports for the commit 43ffae6 to get more accurate results

@@             Coverage Diff              @@
##                3.0    #9030      +/-   ##
============================================
- Coverage     63.32%   63.20%   -0.13%
+ Complexity      314      311       -3
============================================
  Files          1189     1189
  Lines         50480    50453      -27
  Branches       7540     7515      -25
============================================
- Hits          31968    31889      -79
- Misses        15029    15064      +35
- Partials       3483     3500      +17

Impacted Files
Coverage Δ

...gistry/client/migration/MigrationRuleListener.java
70.83% <66.66%> (-1.49%)
:arrow_down:

...ng/transport/dispatcher/WrappedChannelHandler.java
47.82% <0.00%> (-15.22%)
:arrow_down:

...ng/transport/dispatcher/all/AllChannelHandler.java
75.86% <0.00%> (-13.80%)
:arrow_down:

...ache/dubbo/remoting/transport/AbstractChannel.java
75.00% <0.00%> (-12.50%)
:arrow_down:

...dubbo/common/status/support/LoadStatusChecker.java
50.00% <0.00%> (-11.54%)
:arrow_down:

...e/dubbo/remoting/transport/netty/NettyChannel.java
51.13% <0.00%> (-9.10%)
:arrow_down:

...mmon/threadpool/support/fixed/FixedThreadPool.java
80.00% <0.00%> (-7.50%)
:arrow_down:

.../common/threadpool/serial/SerializingExecutor.java
70.37% <0.00%> (-7.41%)
:arrow_down:

.../apache/dubbo/remoting/transport/AbstractPeer.java
54.34% <0.00%> (-6.53%)
:arrow_down:

.../threadpool/support/limited/LimitedThreadPool.java
83.33% <0.00%> (-5.56%)
:arrow_down:

... and 36 more

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 87f869d...43ffae6. Read the comment docs.


Update documentation for source

Update documentation and security for Kusto source

overall just think we need to refer to it as Distributed vs Single and not ForceDistributedMode vs ForceSingleMode

Done Ohad


Bash  block highlighting breaks issue fixed and removed $ sign

Fixes #98

Fixed bash highlighting breaks issue in docker setup markdown.
Removed $ sign from bash block.

@vishnu-narayanan, please take a look.


Possible UX Improvements

I was playing around with it and noticed some things:

I at first thought that the disappearing white frame around the editor was a bug. Maybe it would be more clear that it's expected behavior if it fades in/out.

Why doesn't the scroll bar go away as well? Its gray color disturbs my zen.

How do I exit? My first thought was to go back to the view menu, where I activated zen mode. There was no "exit ZEN" option so I just pressed GO ZEN again. I guess this opened another window. Then I tried the red close button in the top left corner. The first time I didn't notice any change (because I accidentally opened a second window probably) and the second time it worked.

Maybe the text font of the editor can become a bit bigger when we enter zen mode? Just to increase the feeling of "focusing in" on the code.

Great plugin overall! :)

@maartenschumacher

It is going to be adressed, definitely.
I think it does go away. It's normal that it appears on the screen during scrolling but it shouldn't be there anymore when you finished scrolling. If it's not the case for you please elaborate more!
This is not going to be adressed. You simply click red button. It's a standard Mac behaviour.
It is not possible easily. I wouldn't like it anyway.

Thanks for the contribution!

@wczekalski

This is what the scroll bar looks like for me :/
I forgot to say that actually the first thing I tried was pressing the "escape" key on my keyboard, which is how I usually exit some full screen mode. I didn't actually realize that it just opened another window.

Actually I tried pressing escape when I use the osx full-screen feature (the green button) and it didn't work either :)
But to be fair, pressing the red button doesn't return to normal size but gets rid of the entire window. I guess this is what actually should happen because the zen mode is just a window, but again, it wasn't clear to me that it worked like that.

The animation was added in #17


Chunked string parsing

This is a new v0.5 feature: the ability to parse chunked CBOR strings per chunk. It also adds the ability to do zero-copy parsing of strings. From the docs:
   if (cbor_value_is_text_string(value)) {
       char *ptr;
       size_t len;
       while (1) {
           err = cbor_value_get_text_string(value, &ptr, &len, &value));
           if (err) return err;
           if (ptr == NULL) return CborNoError;
           consume(ptr, len);
       }
   }

There are two commits in this series:

Add support for parsing chunked strings
rewrite the iterate_string_chunks function with new chunk code

@lpereira @otaviobp @rzr @erichkeane @alradmsft

Wrong target branch. This is meant for dev.


Implementing B-Tree in Python and C++

Implementing B-Tree in JAVA, python, C and C++
The B-Tree can handle massive amounts of data with ease. When it comes to storing and searching large amounts of data, traditional binary search trees can become impractical due to their poor performance and high memory usage. B-Trees, also known as B-Tree or Balanced Tree, are a type of self-balancing tree that was specifically designed to overcome these limitations.

B-Trees are characterized by the large number of keys that they can store in a single node, which is why they are also known as “large key” trees. Each node in a B-Tree can contain multiple keys, which allows the tree to have a larger branching factor and thus a shallower height. This shallow height leads to less disk I/O, which results in faster search and insertion operations. B-Trees are particularly well suited for storage systems that have slow, bulky data access such as hard drives, flash memory, and CD-ROMs.
Describe the solution you'd like
Implementing the following operation in B-Tree

Search
Insert
Delete

In following languages

C++
Python

Please Assign this issue to me under SSoC 2.0

Assigned!
@dhruvmillu : Python and C++


chore: 0.8.0 internal-release mergeback

Brings 0.8.0 changes back into edge.

diff --cc api/release-notes-internal.md
index 3494a4ce1,bff81e3f9..471e54ada
--- a/api/release-notes-internal.md
+++ b/api/release-notes-internal.md
@@@ -10,93 -10,64 +10,8 @@@ This is internal release 0.9.0 for the

  Some things are known not to work, and are listed below. Specific compatibility notes about peripheral hardware are also listed.

 -## Hardware Revision Compatibility
 -
 -- This release will work best on a DVT robot frame with a programmed rear-panel board. If that doesn't apply, edit `/data/feature_flags.json` and turn `rearPanelIntegration` to `false` or the robot server won't start.
 -- This release is compatible with EVT pipettes and gripper only if they have received the tool ID rework.
 -- This release is compatible with DVT pipettes and gripper.
 -- This release should be used with DVT module caddies. This might introduce a slight LPC offset change if the previous offsets for labware on modules were measured while using EVT caddies.
 -- This release should be used with pipette bootloaders of at least v7.
 -
 -## Big Things That Don't Work Yet So Don't Report Bugs About Them
 -
 -### ODD
 -- While many individual flows work, going in between them often does not, you have to use the secret menu
 -- The ODD generally won't synch up to what the robot is doing if the app is controlling it - for instance, if you start a protocol from the app the ODD won't follow along on its own
 -- The ODD doesn't really tell you if the robot server hasn't started yet; if a robot looks on but has the name "opentrons", or says it's not network-connected when you know it is, probably the server isn't up yet, give it another little bit
 -- It can take a while for the robot to start after installing an update (it's the firmware updates happening on boot). Allow 10 minutes after an update that has a firmware change.
 -
 -### Robot Control
 -- Pipette/gripper firmware update on attach: if you need to attach a new instrument, attach it and then power-cycle the robot or restart the robot server
 -- Pipette pressure sensing both for liquid-level sensing purposes and for clog-detection purposes
 -- Labware pick up failure with gripper
 -
  ## Big New Things
  ### Robot Control
 -- USB connectivity! You can connect your Flex to your computer with a USB cable and the Opentrons App will detect and interact with it. Please let us know if
there's anything weird you see while doing this, because this is very new.
 -
 -### ODD
 -- The ODD should only display once the robot server has come up, removing that awkward time where the ODD looked like it was running but would display no network connectivity, no pipettes, etc. This is done via a new loading screen. A spinner with a blue background will now appear after the spinner with the grey background. When the blue background is displaying, the app has started but the robot server has not.
 -
 -## Reasonably Sized New Things
 -### ODD
 -- Lots of flow fixups, visual fixups, and startup changes.
 -
 -### Robot Control
 -- Fixed an issue where module calibration would take the previous module offset into account, leading to the offsets drifting further and further every time you ran module calibration.
 -- Attach and detach should have more consistent positioning.
 -- Various 96 channel fixes
 -
 -
 -## Big Things That Do Work Please Do Report Bugs About Them
 -### Robot Control
 -- Liquid handling protocols with 1 and 8 channel pipettes
 -- Labware movement between slots/modules, both manual and with gripper, from python protocols
 -- Labware drop/gripper crash errors, but they're very insensitive
 -- Pipette and gripper automated offset calibration
 -- Network connectivity and discoverability
 -- Firmware update for all devices attached when the robot turns on
 -- Cancelling a protocol run. We're even more sure we fixed this so definitely tell us if it's not.
 -- USB connectivity
 -
 -### ODD
 -- Protocol execution including end-of-protocol screen
 -- Protocol run monitoring
 -- Attach and calibrate
 -- Network connection management, including viewing IP addresses and connecting to wifi networks
 -- Automatic updates of robot software when new internal releases are created
 -- Chrome remote devtools - if you enable them and then use Chrome to go to robotip:9223 you'll get devtools
 +- move_labware now requires apiLevel to be at least 2.15. You can now move labware off-deck using the python API by supplying OFF_DECK to the new_location arg.

 -## Smaller Known Issues
 -
 -## Smaller fun features
 -- The lights work (don't do anything yet though)
 +For more details about this release, please see the full [technical change log][].
-
- # Internal Release 0.7.0
-
- This is internal release 0.7.0 for the Opentrons Flex robot software, involving both robot control and the on-device display.
-
- Some things are known not to work, and are listed below. Specific compatibility notes about peripheral hardware are also listed.
-
- ## Big New Things
- ### Robot Control
- - Updated python api version to 2.15
- - Added load Magnetic block as a module in python api and in PE. You can now load a magnetic block using `protocol_context.load_module("magneticBlockV1", <slot_name>)` with `apiLevel` of 2.15.
-
- For more details about this release, please see the full [technical change log][].
-
- [technical change log]: https://github.com/Opentrons/opentrons/releases
-
- ---
-
- # Internal Release 0.6.0
-
- This is internal release 0.6.0 for the Opentrons Flex robot software, involving both robot control and the on-device display.
-
- Some things are known not to work, and are listed below. Specific compatibility notes about peripheral hardware are also listed.
-
- ## Hardware Revision Compatibility
-
- - This release will work best on a DVT robot frame with a programmed rear-panel board. If that doesn't apply, edit `/data/feature_flags.json` and turn `rearPanelIntegration` to `false` or the robot server won't start.
- - This release is compatible with EVT pipettes and gripper only if they have received the tool ID rework.
- - This release is compatible with DVT pipettes and gripper.
- - This release should be used with DVT module caddies. This might introduce a slight LPC offset change if the previous offsets for labware on modules were measured while using EVT caddies.
- - This release should be used with pipette bootloaders of at least v7.
-
- ## Big Things That Don't Work Yet So Don't Report Bugs About Them
-
- ### ODD
- - While many individual flows work, going in between them often does not, you have to use the secret menu
- - The ODD generally won't synch up to what the robot is doing if the app is controlling it - for instance, if you start a protocol from the app the ODD won't follow along on its own
- - The ODD doesn't really tell you if the robot server hasn't started yet; if a robot looks on but has the name "opentrons", or says it's not network-connected when you know it is, probably the server isn't up yet, give it another little bit
- - It can take a while for the robot to start after installing an update (it's the firmware updates happening on boot). Allow 10 minutes after an update that has a firmware change.
-
- ### Robot Control
- - USB connectivity
- - Pipette/gripper firmware update on attach: if you need to attach a new instrument, attach it and then power-cycle the robot or restart the robot server
- - Pipette pressure sensing both for liquid-level sensing purposes and for clog-detection purposes
- - Labware pick up failure with gripper
-
- ## Big New Things
- ### Robot Control
- - All python protocol API functions that take deck slot names (like load_labware) now support deck slot "coordinates", e.g. specifying a deck slot as "A1" rather than 1. This feature requires a Python protocol to request API version 2.15.
-
- ## Reasonably Sized New Things
- ### ODD
- - Protocol result screens! No more do you have to stare at those big buttons forever
-
- ### Robot Control
- - Python API `load_labware`, `load_module` and `move_labware` can accept location as deck coordinates (e.g. "A1", "D3") in addition to slot numbers
- - The `.parent` property for Module and Labware objects (loaded on the deck) will return a coordinate style deck location (e.g. "B2", "C3") for protocols with robotType "OT-3 Standard" instead of the slot number
- - Rerunning a protocol should no longer result in being on step ?
- - DVT gripper sets its force more accurately now
- - Fixed a couple more bugs with pipette calibration; it should no longer fail during the Z height calibration
- - Fixed a problem where the change-pipette process would crash after removing a pipette because it tried to home the now-not-present pipette
-
- ## Big Things That Do Work Please Do Report Bugs About Them
- ### Robot Control
- - Liquid handling protocols with 1 and 8 channel pipettes
- - Labware movement between slots/modules, both manual and with gripper, from python protocols
- - Labware drop/gripper crash errors, but they're very insensitive
- - Pipette and gripper automated offset calibration
- - Network connectivity and discoverability
- - Firmware update for all devices attached when the robot turns on
- - Cancelling a protocol run. We're even more sure we fixed this so definitely tell us if it's not.
-
- ### ODD
- - Protocol execution including end-of-protocol screen
- - Protocol run monitoring
- - Attach and calibrate
- - Network connection management, including viewing IP addresses and connecting to wifi networks
- - Automatic updates of robot software when new internal releases are created
- - Chrome remote devtools - if you enable them and then use Chrome to go to robotip:9223 you'll get devtools
- - After a while, the ODD should go into idle; if you touch it, it will come back online
-
- ## Smaller Known Issues
-
- ## Smaller fun features
- - The lights work (don't do anything yet though)```

(aka just go with the 0.9.0 changes)


The optimization objective is the categorical_crossentropy？

Hi,
I realize that the optimization objective is the categorical_crossentropy in your code, i.e.,
model.compile(loss='categorical_crossentropy', optimizer='adam', metrics=['accuracy']).
However, in my opinion, if we want to train the neural network with the IB, the IB objective should be set as the loss, i.e.,
model.compile(loss='IB_loss ', optimizer='adam', metrics=['accuracy']).  Or maybe the IB just acts as a regularizer?
I  am confused about it. Could you make an explanation about it? thanks.
Best

Hi!
The cross-entropy functions like a variational upper bound on the I(M;Y) term.  The compression term I(M;X) is added in as a regularizer.
Cheers
-a