German keys incorrectly shown in Command Editor

Apple Feedback Assistant ID: FB13716317
This bug has been around for a long time. I know John Matthews & BBC Engineering Support have encountered it. I'm surprised we've never logged it here before.
Justine Robilliard reports:

I know this is an old bug, and I am infested with the bug, to the point it renders Final Cut virtually useless.. Below is the screen grab of the problem, when I installed FCP, it was fine, then one day I opened FCP to start to change the commands to ones I would like to set, and wow, it was in German…
So I started to wonder, what happened.. So I did a factory reset of the 2020 M1 MacBook Air, 8GB RAM, standard as standard can be of a 2020 M1 MacBook Air..
Re-formatted the SSD, re-installed Sonoma, FCP, and it is still in German..
What I have discovered is this..Why does COMMAND + switch between 2 layouts? If I hold COMMAND + [2 keys] on the the screen the layout in Command Editor changes, and the [ ] keys appear, but if I release the keys, the layout reverts to German.
I know this is a bug of some age now, 2015 from my research, from what I understand is that if I plug in the Apple USB external keyboard, then the English correct Command Editor layout appears, unplug the keyboard, it disappears/reverts back to German
It seems to me that there is a bug that tells FCP my hardware keyboard, the one on the MacBook Air, FCP thinks it is German, even though it is not German, but English…
I have sent a number of feedbacks to Apple including the screen grabs and a “please” can you fix, and well nothing, for me now a couple months, and counting.. I just cannot understand how a bug can last 7 years…
Ok, so to sum up, the Mac was bug free, there was an update, it changed the language, I was not aware of this, then in the last couple months, I have been using FCP more as we are about to change from FCP7 to FCP, the crew use FCP [x] to edit, and they have questions, so I need to be prepared, so started using FCP, that is when I came across the bug, did the format SSD, re-install…Bug
This is with using iCloud and not, I am wondering if and this is going to sound insane, that the version of FCP I use to re-install is hosted in Germany, and the wrong version is active, a developer version…
Pressing Command and + [plus] changes the keyboard from default German to English, this is not permanent, but plug in an external keyboard it is.. I think a line of code is causing conflict..

This bug is still present in 10.8.
https://x.com/FishChips1/status/1804116375847186499

I have un-installed, rebooted, and re-installed FCP 10.8 on the Sequoia Beta, and still German Language Bug,

VideoAppDiagnostics-FinalCut-2024-06-30-211019.tar.gz

Hi Chris
I am not sure if this has anything to do with the German Language Bug, stiil not fixed, on a whin I checked System Report-Language Region-Requested Language Linguistics..EN DE EN_US is listed... My question is why is DE [German] listed in the system report? There is no setting to change this....

Justine Robilliard reports that this is still an issue.
I'm going to consolidate all Justine's feedback below (with permission) so we can hopefully get to the bottom of this.
Unfortunately I haven't been able to reproduce on any of our machines, both Intel and Apple Silicon running a variety of different macOS versions and Final Cut Pro versions.

FYI: I have submitted more information to Apple via FB13716317.

To sum up, there was no bug in FCP until I did an update around March 2024, in which the command set was changed to German Language, QWERTZ layout.. I did a google search, found this was a bug in around 2015, my system is a 2020 M1 Macbook Air 8GB RAM, 256GB SSD...
We have a couple of late model 15 inch macbook pro running FCP, 10 8 1, they are not affected.. But every Mac laptop in eevery "Istore" here in Durban, South Africa, that is M series, has German Language Bug.
I have been to 3 local "istores" Gateway, Balitto, and Pavillion, and about 100 machines affected, logged numerous faults, had my laptop in 3 times, and 3 times they were able to reproduce, but 6 months later, no reply or response..
I have logged faults, pleaded, begged, made deals with all sorts of things one does with evils in religion, to no avail, asked pleaded begged on the Apple Feedback Forum...
I have tried to use virtual machines, but I have no idea what I am doing...
What I know, is that Command + [plus key] when inside of Command Editor changes the keyboard from German to English, the change is not persistent, release a key, the command set reverts back to German.
So I suspect the issue is this.. Developers of FCP/Motion/Compressor/Logic are based in Germany, use German Keyboard and when Apple US needs to check, Command + is used to change from English-German-English..
It seems that South Africa is geo locked to a certain server, and this server hosts a faulty version of FCP, that is the only thing that makes sense, South Africa is locked to a German hosted Server, that has a line of code commented out that prevents the change of command set from German to English...
Either that is true, or the OS is faulty that I can access when I do a full re-format, re-install.. The only way to confirm this, is to travel to parts of the rock that I can, ie, Australia, the USA, re-install the OS, and FCP and verify which is true..
Is Pro Apps the issue, or the OS? Why only Silicon systems, and not Intels??

@ivyparrot - Legend, thank you! I have relayed all this information to Apple, and if I don't hear back from them, I'll definitely try do my best to bring it to their attention at the FCP Creative Summit in person. Fingers and toes crossed we can get to the bottom of this for you!

Also posted here: https://developer.apple.com/forums/thread/764513

HI Chris
Yeah. Hunting down where and what to do, found that site and wow, talk
about underwhelming.. Gee, like getting a box of chicken eggs for easter
when you really wanted choc coffee orange easter eggs... Disappointing
comes about 0.1% describing how I felt after posting.. Expected I guess...
I cannot understand how it is so hard, we know what/where/how to solve..
This cannot be mission impossible.. But it seems it is..
Am I the sole user of FCP with German Language Bug on this 3rd rock from
the sun???
I would love to travel to Apple Inc HQ, but to get a passport, flights,
hotels, ubers.. If the meet was say in London..or Dubai..not as far and
less costly...
Have a great time, and I really really hope and greatly appreciate any
updates..
Justine
On Mon, Oct 21, 2024 at 1:18 AM Chris Hocking @.***>
wrote:

Also posted here: https://developer.apple.com/forums/thread/764513
—
Reply to this email directly, view it on GitHub
https://github.com/CommandPost/FCPCafe/issues/350#issuecomment-2425282270,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/BJRZQJ2RGIRDS6N42F6XCT3Z4Q227AVCNFSM6AAAAABF52CWX2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIMRVGI4DEMRXGA
.
You are receiving this because you were mentioned.Message ID:
@.***>

HI Chris
Yeah. Hunting down where and what to do, found that Apple Developer site and wow, talk about underwhelming.. Gee, like getting a box of chicken eggs for easter when you really wanted choc coffee orange easter eggs... Disappointing comes about 0.1% describing how I felt after posting.. Expected I guess...
I cannot understand how it is so hard, we know what/where/how to solve.. This cannot be mission impossible.. But it seems it is..
Am I the sole user of FCP with German Language Bug on this 3rd rock from the sun???
I would love to travel to Apple Inc HQ, but to get a passport, flights, hotels, ubers.. If the meet was say in London..or Dubai..not as far and less costly...
Have a great time, and I really really hope and greatly appreciate any updates..
Justine

This is a known bug that also happened in French and Spanish. In Spanish it's also fixed after many, many years. Haven't tested in French.

Thanks, it was a huge problem here in South Africa, strangely no one was concerned, apart from me.. but I am German Language Bug free at this point..

It has re-appeared this time, it appears as the default command set, press a button and it resets to English.. I have re-reported to Apple via the Feedback Assistant as FB15897387


fastExp function

I am wondering what is the motivation behind the fastExp function used in net_update_wa. I cannot see that it is faster or more numerically stable than the exp function from std in any meaningful way. And I am interested as to where the expression was found:
inline prec fastExp(prec a) {
    a = 1.0 + a / 1024.0;
    a *= a;
    a *= a;
    a *= a;
    a *= a;
    a *= a;
    a *= a;
    a *= a;
    a *= a;
    a *= a;
    a *= a;
    return a;
}

I didn't write that part, but in my previous experience (about calculating exponential in deep-learning hardware for sigmoid), that approximate function was much faster than std::exp() function.
Reference: https://codingforspeed.com/using-faster-exponential-approximation/


Bigo.live

Your friend محمد فراری شاه ب invite you to join ludo talent: https://bigo.onelink.me/1168916328/p4po3fss

Your friend محمد فراری شاه ب invite you to join ludo talent: https://bigo.onelink.me/1168916328/p4po3fss

Enjoy

I'm closing this as off topic. Please see our Contributing.md for the types of feedback we're looking for on our Site Policies in this repo.


⚠ Bofrost.at has degraded performance

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

HTTP code: 200
Response time: 1920 ms

Resolved: Bofrost.at performance has improved in 04207ea after 7 minutes.


Range Queries

Hi,
this is not really a problem (unless it is :) ) but I wonder how to do range queries.
In the past - and i think that's what kibana does - I expanded my indexes to the specific dates. This option does exist here manually, however I wonder if that is necessary?
This query for example works for me as well:
'{"query":{"range":{"@timestamp":{"gte":"2016-08-10T00:00:00.000Z","lt":"2016-08-10T00:00:00.000Z"}}}}'
Is this the  intended way to query for ranges? And/or does that still query ALL indexes when I specify:
logstash-*
Essentially what I am trying to work out is if I need to expand my indexes and then apply these to your script?
Kind regards and thank you for this cool script!
Artur

The approach I outlines works perfectly well and fast. Closing this

'{"query":{"range":{"@timestamp":{"gte":"2016-08-10T00:00:00.000Z","lt":"2016-08-10T00:00:00.000Z"}}}}' should work fine in raw query mode(-r).
logstash-* if you specify this in -i arg it will query all indexes matching this mask. You can select any other mask like: logstash-2016-08-, logstash-2015- or logstash-2016-08-1*. It will query only indexes matching to selected mask.
You can query really ALL indexes with -i '_all'
Documentation: index – A comma-separated list of index names to search; use _all or empty string to perform the operation on all indices


Login state is not retained

Hi Eddie,
I open Indigenuous, get the login screen. I enter the site address, https://ascraeus.org/, and get the redirect to IndieAuth, that's all fine.
After logging into a designated provider, the program exits. On relaunch, the screen briefly flashes logged in as - then resets to the login screen.
iOS 11, iPhone 6

Thanks for letting me know!
This is likely a duplicate of #23 so I'll close this for now :)


make: *** No targets specified and no makefile found. Stop.

Not working
makefile not created

I have the next error:
-- The C compiler identification is unknown
-- The CXX compiler identification is unknown
CMake Error at CMakeLists.txt:2 (project):
The CMAKE_C_COMPILER:
gcc-12

is not a full path and was not found in the PATH.
Tell CMake where to find the compiler by setting either the environment
variable "CC" or the CMake cache entry CMAKE_C_COMPILER to the full path to
the compiler, or to the compiler name if it is in the PATH.
CMake Error at CMakeLists.txt:2 (project):
The CMAKE_CXX_COMPILER:
g++-12

is not a full path and was not found in the PATH.
Tell CMake where to find the compiler by setting either the environment
variable "CXX" or the CMake cache entry CMAKE_CXX_COMPILER to the full path
to the compiler, or to the compiler name if it is in the PATH.
-- Configuring incomplete, errors occurred!
See also "/home/almas/Desktop/Orion/Osiris/Release/CMakeFiles/CMakeOutput.log".
See also "/home/almas/Desktop/Orion/Osiris/Release/CMakeFiles/CMakeError.log".
make: *** No targets specified and no makefile found.  Stop.
mv: cannot stat 'libOsiris.so': No such file or directory

I solved the problem above
But, now i have the next problem:
warning: .dynamic section for "/lib/x86_64-linux-gnu/libstdc++.so.6" is not at the expected address (wrong library or version mismatch?)
warning: .dynamic section for "/lib/x86_64-linux-gnu/libgcc_s.so.1" is not at the expected address (wrong library or version mismatch?)
warning: Could not load shared library symbols for bin/linux64/launcher_client.so.
Do you need "set solib-search-path" or "set sysroot"?
78	../sysdeps/unix/sysv/linux/clock_nanosleep.c: No such file or directory.

try @ReShout876 's load script
I had the same problem and it fixed it immediately.
Just unzip all files into Osiris directory, then chmod +x ./load and sudo ./load


Refactor + Add new case studies

https://uktrade.atlassian.net/browse/CMS-170

Codecov Report

Merging #539 into master will decrease coverage by 1.01%.
The diff coverage is 59.32%.

@@            Coverage Diff             @@
##           master     #539      +/-   ##
==========================================
- Coverage    80.6%   79.58%   -1.02%
==========================================
  Files          29       32       +3
  Lines         887      926      +39
  Branches       85       88       +3
==========================================
+ Hits          715      737      +22
- Misses        142      159      +17
  Partials       30       30

Impacted Files
Coverage Δ

app/markets/urls.py
100% <100%> (ø)
:arrow_up:

app/casestudy/helpers.py
40% <40%> (ø)

app/casestudy/views.py
62.5% <62.5%> (ø)

app/casestudy/casestudies.py
70.58% <70.58%> (ø)

app/markets/views.py
77.01% <80%> (+1.35%)
:arrow_up:

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 080b987...f28c381. Read the comment docs.


correction typo error

Hello,
I have noticed an error in a section of your code and would like to suggest a correction in SBAS_dem.py
if product == 'SRTM1':
resolution = '03s'
to
if product == 'SRTM1':
resolution = '01s'
Thanks.

Thanks, it’s already fixed in my development branch where the DEM processing is completely rewritten. The new version is optimized to work on native Sentinel-1 grid (~15 x 4 meter) to allow PS-SBAS combined processing.


Fix mesh.wgsl error for meshes without normals

Objective
Split model assignment out of #ifdef VERTEX_NORMALS.
Remove outdated code/comments talking about required mesh attributes.

(Weak approval, I won't merge without another rendering expert).


Enable lazy activation of stats output

Currently CONCAT_STATS needs to be set at instantiation time. This enables to set it afterwards, just before the build.

released as v3.7.0 🎉


Can't read events from BDF file

Hi all,
When i import my data from the BDF format (test.zip) i can't read the event list. The events are present in the data as i can read them using EEGLAB.
i loaded the code using:
raw = mne.io.read_raw_edf(bdf_file, stim_channel="Status")
i have tried
raw.find_edf_events()
as well as
mne.find_events(raw)
both functions return an empty array.
when i use raw.plot() the stimulus channell appears to be completely flat.
i looked at the stim channel value for each sample:
data = raw.to_data_frame()
print(data["STI 014"])
the value at every sample is 41009.0 ( i have no idea where that comes from)
Not sure where i am doing something wrong (I'm pretty new to MNE-Python and EEG-Data processing in general) and i hope you can help me with this.
best,
Ole

I can confirm this issue. It has something to do how we (automatically) convert the stim channel. If you don't convert it, you actually get this picture:

I will look into it.

Also, it is OK that raw.find_edf_events() doesn't return any events, because your data file does not have a dedicated annotation channel. Instead, events are stored in the last channel as a regular data channel.

I think the problem is that the last channel gets scaled, because its physical range is 374940 and its digital range is 16777215. Each channel get scaled by the quotient, which in this case is 374940 / 16777215 = 0.022348166844139507 (just like for all other 24 channels in this file). Normally, the stimulus channel has identical physical and digital ranges, which makes the scaling factor equal 1.
Now apparently MNE relies on the channel scaling to extract events. One way to fix this is to enforce a scaling factor of 1 for stim channels. However, I don't know if this breaks other things, but it might be worth a try. At least this works with your test file.
Do you expect specific event types (numbers) for the three types?

Great, now i can get the eventlist. As is understood i have to subtract the values in the third column of the event list from the 'baseline' in the second. If i do this i get event types 1,2 and 4 which is what i am expecting. Thank you!


python312Packages.tencentcloud-sdk-python: 3.0.1277 -> 3.0.1278

Diff: https://github.com/TencentCloud/tencentcloud-sdk-python/compare/refs/tags/3.0.1277...3.0.1278
Changelog: https://github.com/TencentCloud/tencentcloud-sdk-python/blob/3.0.1278/CHANGELOG.md

Things done

Built on platform(s)

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

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] 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/)
25.05 Release Notes (or backporting 24.11 and 25.05 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.

Add a :+1: reaction to pull requests you find important.

nixpkgs-review result
Generated using nixpkgs-review.
Command: nixpkgs-review pr 363893

x86_64-linux

:white_check_mark: 4 packages built:

python311Packages.tencentcloud-sdk-python
python311Packages.tencentcloud-sdk-python.dist
python312Packages.tencentcloud-sdk-python
python312Packages.tencentcloud-sdk-python.dist


Refactored Codebase with "Coordinates" and Subpackages

What changes were made:
I created a new "Coordinate.java" class which wraps a pair of (X,Y) ints to unify our use of x's and y's. I then changed all relevant parts of the code to make use of this new structure.
I also moved all our files into subpackages to better organize our repo (per in-person discussion).
What are the relevant JIRA tickets:
(Jira is still down...)
How can these changes be tested(test #?):
Just run the regular test suite/watch the Travis CI build (it all passes).
Comments:

The merge conflicts begin!


feat: introduce POP_SMTP_PASSWORD_COMMAND

Add password command to allow command output to be used as password rather than hardcoding.

Decided against this as you can use an alias for pop:
alias p="POP_SMTP_PASSWORD=$(pass gmail.com) pop"

To achieve very similar results. This may be reintroduced when a configuration file is available.


IC2 Classic Crashing Industrial Turbine

I have a max size turbine (17x17 and 18 tall, using condensers), when I complete the multiblock structure (while steam is hooked up to it) it crashes with the attached log. I can log back in, and the turbine "works" (the animation is frozen, but the power generation works), but after awhile is crashes with the same errors again. Anytime I connect steam to it it crashes, I'm feeding it from a mekanism reactor (also when it crashes the reactors turn off and the fuel is set back to 0).
Removing IC2 Classic fixes the issue, so I know it's related to that. It seems like this was an issue in the past: https://github.com/aidancbrady/Mekanism/issues/3255
Minecraft Version: 1.7.10
KCauldron:1.7.10-1614.201
(IC2Classic Version <IP_ADDRESS>.jar)
(Mekanism-1.7.10-<IP_ADDRESS>1.jar)
crash-2017-04-29_16.17.07-server.txt

Reproducable in creative and singleplayer as well, the crash happens the moment the internal energy-storage of the turbine hits 8.49 or 8.5G RF.
I used a 11x11x18 turbine so I assume it's independent of the size as long as the internal buffer can go that high.
Versions used:
Minecraft 1.7.10
Forge <IP_ADDRESS>4
Mekanism <IP_ADDRESS>1
IC2Classic <IP_ADDRESS> (should probably update that)
Crashlog attached in case there's some additional usefull info.
crash-2017-04-30_02.20.33-server.txt

Glad to know it's not just me, thanks Palpiter. Just another thing IC2 fails at... If it wasn't for the mass fabricator (which is pretty much the only thing I've found that uses the kind of power these machines make) I'd ditch IC2 all together.
Think there's any way to fix this on the Mekanism side? because I imagine getting IC2 to do anything wouldn't happen.

1.7.10 isn't supported anymore. Development is currently focused on 1.11.2

Should be fixed.


create components to detect window height and width

create a components that can detect the height and width of the current windows that uses that components. For example, if this component is called in the header, the component should return the current width and height of the current window. It should also update the width and height when the screen size is updated.
Consider tutorial such as :-

https://bobbyhadz.com/blog/react-get-window-width-height
https://stackoverflow.com/questions/36862334/get-viewport-window-height-in-reactjs
https://www.codingbeautydev.com/blog/react-get-window-width-height

From those website, it seems that you can obtain current windows height via windowInnerWidth and windowInnerHeight. Change anything necessary to fit the case :-
import { useRef } from 'react';

export default function App() {
  const windowSize = useRef([window.innerWidth, window.innerHeight]);

  return (

Width: {windowSize.current[0]}

Height: {windowSize.current[1]}

  );
}

For resizing the windows:-
import { useState, useEffect } from 'react';

export default function App() {
  const [windowSize, setWindowSize] = useState([
    window.innerWidth,
    window.innerHeight,
  ]);

  useEffect(() => {
    const handleWindowResize = () => {
      setWindowSize([window.innerWidth, window.innerHeight]);
    };

    window.addEventListener('resize', handleWindowResize);

    return () => {
      window.removeEventListener('resize', handleWindowResize);
    };
  }, []);

  return (

Width: {windowSize[0]}

Height: {windowSize[1]}

  );
}

We use the useState React hook to create a state variable that will be updated whenever the height or width of the window changes.
The useState hook returns an array of two values. This first is a variable that stores the state, and the second is a function that updates the state when it is called.
 const [windowSize, setWindowSize] = useState([
    window.innerWidth,
    window.innerHeight,
  ]);

The useEffect hook is used to perform an action when a component first renders, and when one or more specified dependencies change. In our example, the action is to add the event listener for the resize hook with the addEventListener() method.
We pass an empty dependencies array to the useEffect, so that it gets called only once in the component's lifetime, and the resize event listener is only registered once - when the component first renders.
 useEffect(() => {
    const handleWindowResize = () => {
      setWindowSize([window.innerWidth, window.innerHeight]);
    };

    window.addEventListener('resize', handleWindowResize);

    return () => {
      window.removeEventListener('resize', handleWindowResize);
    };
  }, []);

In the resize event listener, we update the state variable with the new height and width of the window.
The function we return in useEffect is a function that performs clean-up operations in the component. We use the removeEventListener() method to remove the resize event listener in this clean-up function and prevent a memory leak.

Here's an example of a React component that can track the current width and height of the screen, and update the values when the screen is resized. This component can be adjusted according to the page setting:
import React, { useState, useEffect } from 'react';

const ScreenSizeTracker = ({ width, height, onResize }) => {
  const [screenWidth, setScreenWidth] = useState(width || window.innerWidth);
  const [screenHeight, setScreenHeight] = useState(height || window.innerHeight);

  useEffect(() => {
    const handleResize = () => {
      setScreenWidth(window.innerWidth);
      setScreenHeight(window.innerHeight);
      if (typeof onResize === 'function') {
        onResize({ width: window.innerWidth, height: window.innerHeight });
      }
    };

    window.addEventListener('resize', handleResize);

    return () => {
      window.removeEventListener('resize', handleResize);
    };
  }, [onResize]);

  return (

Screen width: {screenWidth} px

Screen height: {screenHeight} px

  );
};

export default ScreenSizeTracker;

Here's how this component works:

The component takes in two optional props: width and height. If these props are provided, they will be used as the initial values for the screen size. Otherwise, the component will use the current window size.
The component uses the useState hook to store the current screen width and height. These values are updated whenever the window is resized.
The useEffect hook is used to set up an event listener for the resize event on the window. When the window is resized, the event handler updates the screen width and height state variables, and also calls the onResize callback function (if provided) with the new screen size.
The onResize callback function is an optional prop that can be used to perform additional actions when the screen size changes (e.g., updating the layout of the page).
The component renders a simple div element that displays the current screen width and height.

You can use this component in your React app like this:
import ScreenSizeTracker from './ScreenSizeTracker';

const MyPage = () => {
  const handleResize = (size) => {
    console.log(`Screen size changed to ${size.width}x${size.height}`);
    // Perform additional actions here, such as updating the layout
  };

  return (

My Page

      <ScreenSizeTracker onResize={handleResize} />
      {/* Other page content */}

  );
};

export default MyPage;

In this example, the ScreenSizeTracker component is used within the MyPage component. Whenever the screen size changes, the handleResize function is called, which logs the new size to the console and can be used to update the layout of the page.


Invalid part id in /manifest route causes crash

Quick fix applied to prevent crash, invalid part id will get manifest for parent object
Update to return a 404 for an invalid or nonexistent part id

Currently, if no part data is found, the parent object manifest is generated by default
If no part data is found for specified object part, skip the manifest service code and return null manifest value to controller. Controller will return a 404 status


chore(release): 1.0.1

:robot: Merge this PR to release a new version
1.0.1 (2023-11-06)
Features

Added example to package (3dd1e27)
Changed design pattern (named params -> optional param map) (236d698)
release please with publish (1320caa)
Removed Flutter dependency (8f2272c)
upgrade to be compatible with Dart 3 (5426af5)

Bug Fixes

add secret token to release-please wf to trigger other workflows (3ffd455)
Corrected README (659c1b8)
Corrected README (e271d85)
warning and hints from dart publish dry run (a3b89d4)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/vlnevyhosteny/buttercms-dart/releases/tag/v1.0.1 :sunflower:


connect ECONNREFUSED issue

Hi guys,
I use redis with an (redis) sentinel environment.
When one server went away, i still get reconnection messages.
How can i handle unavailable redis instances?
Please explain how to handle with instances who have gone away, can't find any hints in the documentation.

Either this had nothing to do with node_redis or is fixed now as there should not be any reconnect messages after a failure, since a while back.


LAB_09a-Implement_Web_Apps.md.pdf

Description:
The architecture diagram is not translated

Hello contributor,
Thank you for your contribution! We are processing your suggestions and we will update you shortly.
Kind regards,
Microsoft Worldwide Learning Team

This is an image issue, I can't fix the issue.

https://github.com/MicrosoftLearning/AZ-104-MicrosoftAzureAdministrator.fr-fr/issues/222


Where does the manifest.yml need to be within the app.

I have created a deployment file like the one you have in your readme. The main change being to the command line:
command: push -f manifest.yml

However, when the deployment runs I get the error Incorrect Usage: The specified path 'manifest.yml' does not exist..
There is a manifest.yml file in my app root. I have tried copying it to ./github and .github/workflows but still get the same error.
So - where does the manifest file need to be located or is there a way of specifying the path to it?

I have found the solution. I needed to include - uses: actions/checkout@v2 in the steps for this action. So my action now has the steps:
    steps:
    - uses: actions/checkout@v2
    - uses: citizen-of-planet-earth/cf-cli-action@master

I have found the solution. I needed to include - uses: actions/checkout@v2 in the steps for this action. So my action now has the steps:
    steps:
    - uses: actions/checkout@v2
    - uses: citizen-of-planet-earth/cf-cli-action@master


Added Splash effect and arranged the folders

Issues:
Other mode are broken now. They don't behave as before, there is fade animation to them and there is massive performance issue.Animation mode works as usual.The splash mode works amazingly.
If you are able to fix the modes to the state they were before I don't see why this new mode wouldn't be part of new versions of PianoLED app

Please try new version, effects are fixed now and performance should be better as well

I noticed few issues still.
Biggest one is performance in modes really.
You hardly can press one or few keys which is not ideal for just basic note on and off for default,random and velocity modes.
Default mode still is very different it only reacts note on, it can't hold the led until you un press the key.
The fade effect is very slow even in your mode it doesn't feel smooth anymore.(maybe because of the default values need to use config parameters to check if its smooth as before)
The rgb sliders are still not working correctly. If you select full red it displays green, if you select full green it displays red, blue works as intended .
Animation also works as intended.
I see red compiler errors while you start the app.
The open/close idea is cool. And I like that it gets the devices(my pc has more coms so I still have to select correct com).
I can give you one tip to somehow fix the modes.
They should use note on and note off. Your mode can still use only note on, being able to sense note off as well for that mode will be hard.

Amazing job. I will accept this pull request now.


Add bash completion for all dcos cli commands

Bash auto completion added for Linux/Darwin based systems,
where the script will be added automatically upon installing the
cli package. All commands for autocompletion added with the help
of :
https://docs.mesosphere.com/using/cli/

@hayderimran7 - awesome, we've been wanting this for a while :).

You've got a typo in the name of your script dcos.bash_comletion-> dcos.bash_completion.

@hayderimran7 Thanks for submitting this PR!
We have been looking to implement autocomplete for a while now. The DCOS CLI uses (docopt)[https://github.com/docopt/docopt] to parse the command line specification at https://github.com/mesosphere/dcos-cli/tree/master/cli/dcoscli/data/help and in the main.py files in https://github.com/mesosphere/dcos-cli/tree/master/cli/dcoscli
and its sub-directory. Have you thought about implementing this by using the docopt parser to generate the AST? We should be able to use this AST to implement auto-completion.
I am concerned that with this implementation we are going to have multiple hard states that need to get updated when we make change to a command.
Also, the CLI supports extension by dynamically adding and discovering subcommands. Ideally, our autocomplete implementation would support that mechanism for adding subcommand and autocompletion for them.
Thanks!

@jsancio  thank you - i have to agree with  you on the flexibility of going this way, i myself have implemented the autocompletion on openstack projects using module inspection and adding those member functions dynamically to the data that needs to be autocompleted.
so thanks for linking me to docopt, I will investigate more on it and try to come up with better solution :)

Thank you @hayderimran7. I am going to close this PR for now. Please submit another PR after your investigation. Looking forward to the new PR!


Causes for this error

Add a list of the possible causes for this error.

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

ID: 3bcd11f1-65ff-4b7c-39ad-bcdade7050a2
Version Independent ID: 4c33cb17-d2ad-f119-a16a-aa47c6e5d2f2
Content: Bug Check 0x2 DEVICE_QUEUE_NOT_BUSY - Windows drivers
Content Source: windows-driver-docs-pr/debugger/bug-check-0x2--device-queue-not-busy.md
Product: windows-hardware
GitHub Login: @DOMARS
Microsoft Alias: domars

@LuigiBruno - I have opened an internal work item to track this work, so closing this issue for now.
As I have mentioned before, we use a process to prioritize the most frequent bug checks out of the hundreds that are currently defined. With our limited documentation team resources, it is likely that we will only be able to do this work for a small sub set of all of the possible stop codes.
Thank you for your interest in improving our stop code docs.


Remove hard-coded special treatment for $path and $bucket

Summary: These special columns are engine-specific and should be handled during engine split generation by setting the corresponding values in split infoColumns.  For example in Prestissimo this is done in https://github.com/prestodb/presto/blob/48f0a0c1d380b1155dfd7c99b134a350627c7260/presto-native-execution/presto_cpp/main/types/PrestoToVeloxConnector.cpp#L1112-L1120.
Differential Revision: D64180231

@xiaoxmeng Yes Prestissimo handles it in split conversion code I mentioned in the PR descriptions.  Other usages also have the special columns they need set up properly in their code.


Have both date and time picker in same dialog?

So I wish to have both pickers in same dialog so user can select date and time (full timestamp).
Is this possible in current build?
Also inline option would be cool to have, so I can put pickers in my own dialog.

Duplicate of #267


add and fix shields in Readmes

Objective
Fix shields
Solution

Correct shield in the Bevy ECS Readme, where only the MIT license is displayed

Add shields to other Readmes.
homogenize shields and titles.

I don't think other readmes than the root one should have shields

I always thought the purpose of dividing bevy into crates was so that you could use the crates separately. Is that not the case?

I don't think other readmes than the ones that can be used independently should have shields

Agreed. I want this for bevy_ecs, bevy_reflect, bevy_tasks, bevy_utils and bevy_mikktspace. Those are the only ones that can be used truly independently, all the others need bevy_ecs in order to function.


Hey! Template works on LocalHost when build and run, but does not work when uploading game on server

Hey ! This really works on localHost, but when I upload the project on server, the project crashes, just small black squire appears and this is error message:
.loader.js:1 wasm streaming compile failed: TypeError: Failed to execute 'compile' on 'WebAssembly': Incorrect response MIME type. Expected 'application/wasm'.
Also I tried to add this in blank project, it works but when I import my  game package, still does not works..
Any ideas? big thanks anyway for this asset!

It's got nothing to do with the template. You have to configure your server
https://docs.unity3d.com/2019.4/Documentation/Manual/Webgl-Server-configuration-for-WebAssembly-streaming.html


littl fix and littl optimization

template.hx doesnt give error in one particular line now + a bit of silly tiny code optimization

btw ternary operators get turned into normal if else statements when compiled

doesn't do nothing BUT compromise the readability of the code

Depends on the person reading it and the code itself.
Also it's actually easier to read, you can even google it and you will get "makes the code cleaner and more readable".

Probably not needed anymore(?)


Update configs to meet the template.yaml

With the newly created template.yaml, update all the configs to meet the specs specified in the template.yaml.

Related to #122, but not fully addressed by it.

Closed by https://github.com/chanzuckerberg/cryoet-data-portal-backend/pull/127


Cannot read/write to characteristic when notifications enabled

Please check all of the platforms you are having the issue on (if platform is not listed, it is not supported)

[] iOS
[check] Android
[] tvOS
[] macOS
[] .NET Standard
UWP IS NOT SUPPORTED DURING THE BETA PERIOD - ONLY PRs ARE WELCOME FOR NOW

Version of OS(s) listed above with issue
Tested on Android 6 and 7
Version of Library
6.2.3
Expected Behaviour
After enabling notifications on a characteristic, I should still be able to read/write to that characteristic
Actual Behavior
If applicable, please include entire exception - type, message, stacktrace
Attempting to read/write to a characteristic with enabled notifications causes the call to hang (and possibly throw TimeoutException if Timeout is set)
A workaround for this is to call DisableNotifications on the characteristic before the read/write, and EnableNotifications in the result + error handlers. Not ideal though.
Code of Conduct

No Library Update Requests
No Timeline Requests
Please read through the documentation and FAQs
If you have a complaint about the docs, FIX IT - DO NOT FILE IT HERE!  I won't guarantee everything is always 100% up-to-date since I am just 1 person.
Please be respectful of my time. I put a lot of effort into my libraries.  I try to support the issue requests within a day.  I'm not psychic, so please take the time to fill out the above form as complete as possible

Please provide some code that I can work with here.

I can't provide a link to the actual code but paraphrasing:
characteristic.WhenNotificationsRecieved().Subscribe( result => { /* do something */} );
characteristic.EnableNotifications();
characteristic.Read().Subscribe(result => { /* do something */ });
This hangs.
If I do:
characteristic.Read().Subscribe(result => { /* do something */ });
characteristic.WhenNotificationsRecieved().Subscribe( result => { /* do something */} );
characteristic.EnableNotifications();
It works fine, at least until I try and read from that characteristic again.

I run code like this all of the time without issue, so I'm definitely going to need some sort of extra details.
Can you define "hang", do you mean subscribe just isn't being called on Read or is that whole line blocking?
Have you tried using the sample app with your host device?
Do you have an error catch in your subscribe?

By hang I mean Read gets called but it never gets a result in Subscribe, it will just timeout after the specified interval (currently 30 seconds)
Not yet, will try that and report back
Yes, it just gets the TimeoutException

The sample app works fine. I'm starting to think there might be something a bit more painful going on that just so happened to manifest itself between when I enabled the notifications and tried to read from the characteristics.
When I add a 1 second delay between when I connect to the device and when I do the first read, all the problems seem to go away. This screams of a race condition somewhere, I'll investigate further and see if I can find anything useful

Ok, I think I've found the culprit, for real this time.
When I was connecting to the device, upon success I would immediately request an MTU size increase. However I didn't wait for the result (my thinking being I don't actually care when the size increases, since the next bunch of reads/writes are < 20 bytes anyway. Turns out this is bad thinking).
This seems to really mess things up down the line. Perhaps a serial execution issue? Anyway, looks like false alarm on the notifications...

On android, it will definitely be an execution order issue.  I manage almost all read/writes with an internal mechanism to prevent things like this.  MTU is not under that guard, but I can fix it.
An immediate workaround is to simply await the MTU request completion as you've said before moving to other commands.  All characteristic operations are already defended against this, so don't worry about them.

@aritchie
I have the following method.
public async Task RequestMTU(ScanResultViewModel selectedDevice)
{
if (!selectedDevice.Device.Features.HasFlag(DeviceFeatures.MtuRequests))
{
userDialogs.Alert("MTU Request not supported on this platform");
}
else
{
var actual = await selectedDevice.Device.RequestMtu(512);
Console.WriteLine("MTU Changed to " + actual);
//userDialogs.Toast("MTU Changed to " + actual);
}
}
var actual = await selectedDevice.Device.RequestMtu(512); this line of code is awaited but I'm not getting any response further. My app gets hang.
Please help me asap.


GraphQl @function generated request resolver invalid.

Note: If your issue/bug is regarding the AWS Amplify Console service, please log it in the
Amplify Console GitHub Issue Tracker

Describe the bug
A clear and concise description of what the bug is.
When using the GraphQL @function directive, the resolver code being generated is invalid and throws the following error on query:
Unexpected character ('t' (code 116)): was expecting comma to separate Object entries
This is the request vtl code being generated:
`
[Start] Invoke AWS Lambda data source: KsiGetLegacyCustomerLambdaDataSource. **
{
"version": "2018-05-29",
"operation": "Invoke",
"payload": {
"typeName": "$ctx.stash.get("typeName")",
"fieldName": "$ctx.stash.get("fieldName")",
"arguments": $util.toJson($ctx.arguments),
"identity": $util.toJson($ctx.identity),
"source": $util.toJson($ctx.source),
"request": $util.toJson($ctx.request),
"prev": $util.toJson($ctx.prev)
}
}
[End] Invoke AWS Lambda data source: KsiGetLegacyCustomerLambdaDataSource. **
The issue seems to be related to"$ctx.stash.get("typeName")"`.  Manually changing the double quotes around typeName and fieldName to single quotes resolves the issue.
Amplify CLI Version
You can use amplify -v to check the amplify cli version on your system
4.41.2
To Reproduce
Steps to reproduce the behavior or terminal output if applicable
Use the @function directive on any defined query.
Expected behavior
A clear and concise description of what you expected to happen.
A valid request mapping template is generated when using the @function directive.  Subsequent use of respective query succeeds without error.
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):
macOs

OS: [e.g. Mac/Windows/Ubuntu]
Node Version. You can use node -v to check the node version on your system
12.16.1
Log output
Include any relevant log output under ~/.amplify/logs/amplify-cli-<issue-date>.log
{
"data": {
"getLegacyChildCustomers": null
},
"errors": [
{
"path": [
"getLegacyChildCustomers"
],
"data": null,
"errorType": "MappingTemplate",
"errorInfo": null,
"locations": [
{
"line": 2,
"column": 3,
"sourceName": null
}
],
"message": "Unexpected character ('t' (code 116)): was expecting comma to separate Object entries\n at [Source: (String)"{\n  "version": "2018-05-29",\n  "operation": "Invoke",\n  "payload": {\n      "typeName": "$ctx.stash.get("typeName")",\n      "fieldName": "$ctx.stash.get("fieldName")",\n      "arguments": {"custid":"SCHTR"},\n      "identity": {"claims":{"sub":"0f0deaea-b240-4ae4-8368-b58b185a0c04","cognito:groups":["Customer"],"email_verified":true,"cognito:preferred_role":"arn:aws:iam::934875256114:role/us-east-1_SSyZoFrEK-CustomerGroupRole","iss":"https://cognito-idp.us-east-1.amazonaws.com/us-east-1_SSyZoFrEK\",\"[truncated 3071 chars]; line: 5, column: 37]"
}
]
}

Additional context
Add any other context about the problem here.

@btweedy2879 could you provide your schema so that we can try reproducing this?

@btweedy2879 could you provide your schema so that we can try reproducing this?

I also experience this issue. Here's extra detail on @btweedy2879  initial report
Amplify CLI Version
You can use amplify -v to check the amplify cli version on your system
4.41.2
To Reproduce
Use the @function directive on any defined query.
Schema Chunk:
...
type Mutation {
...
  createSalarySet(
    input: CreateSalarySetInput!
    condition: ModelSalarySetConditionInput
  ): SalarySet @function(name: "storageTransformerRangeToMonthStaffCosts-${env}")
...
}
...

Expected behaviour

Amplify deploys correctly escaped template

Further details
Error:

Unexpected character ('t' (code 116)): was expecting comma to separate Object entries↵ at [Source: (String)"{↵  "ver

Amplify Generates the following:
{
  "version": "2018-05-29",
  "operation": "Invoke",
  "payload": {
      "typeName": "$ctx.stash.get("typeName")", <---- Error begins here
      "fieldName": "$ctx.stash.get("fieldName")",
      "arguments": $util.toJson($ctx.arguments),
      "identity": $util.toJson($ctx.identity),
      "source": $util.toJson($ctx.source),
      "request": $util.toJson($ctx.request),
      "prev": $util.toJson($ctx.prev)
  }
}

Switching to
{
  "version": "2018-05-29",
  "operation": "Invoke",
  "payload": {
      "typeName": $util.toJson($ctx.info.typeName),
      "fieldName": $util.toJson($ctx.info.fieldName),
      "arguments": $util.toJson($ctx.arguments),
      "identity": $util.toJson($ctx.identity),
      "source": $util.toJson($ctx.source),
      "request": $util.toJson($ctx.request),
      "prev": $util.toJson($ctx.prev)
  }
}

Fixes the issue, however - I'm now going to write deployment code to sub in this fix which is not ideal.

I also experience this issue. Here's extra detail on @btweedy2879  initial report
Amplify CLI Version
You can use amplify -v to check the amplify cli version on your system
4.41.2
To Reproduce
Use the @function directive on any defined query.
Schema Chunk:
...
type Mutation {
...
  createSalarySet(
    input: CreateSalarySetInput!
    condition: ModelSalarySetConditionInput
  ): SalarySet @function(name: "storageTransformerRangeToMonthStaffCosts-${env}")
...
}
...

Wrong "nikname" 😬 😂

Wrong "nikname" 😬 😂

Wrong "nikname" 😬 😂

@nikname my apologies.   @nikhname, please see my comment above with schema.

Wrong "nikname" 😬 😂

@nikname my apologies.   @nikhname, please see my comment above with schema.

 I am seeing the following lines get created, however they are not reproducing this issue when querying.
"typeName": "$ctx.stash.get("typeName")",
"fieldName": "$ctx.stash.get("fieldName")",

Much like you have already noted the following replacements will also work:
"typeName": "$ctx.stash.get('typeName')",  ## single quoted field
"typeName": $util.toJson($ctx.stash.get("typeName")),  ## using toJson to get the value

It appears to parse the values fine now, but we were able to force a similar error message (shown below) by intentionally adding a backslash to the get method's argument "$ctx.stash.get("\typeName")".
Unexpected character ('\\' (code 92)): was expecting comma to separate Object entries\n at [Source: (String)\"{\n  \"version\": \"2018-05-29\",\n  \"operation\": \"Invoke\",\n  \"payload\": {\n  \t  \"typeName\": \"$ctx.stash.get(\"\\typeName\")\",
...


does hazel support bitbucket ?

Hello, wanted to know if Hazel can be used with Bitbucket.
Thanks.

this is my question too


bchunk: 1.2.0 -> 1.2.2

Motivation for this change
Security patches have been merged by upstream: http://he.fi/bchunk/
It also includes a useful Debian patch that fixes multi-track conversions.
For discussion, see: https://github.com/extramaster/bchunk/issues/2#issuecomment-344093904
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option build-use-sandbox in nix.conf on non-NixOS)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[x] Fits CONTRIBUTING.md.

@GrahamcOfBorg build bchunk


Revert "Test action cable"

Reverts bohandley/DataVisualization#15

Coverage decreased (-18.7%) to 76.389% when pulling 923f961a35bfdae28efc90dda749f046522cb910 on revert-15-test-action-cable into 7f31b80acd0b77c6673efdd161ae8e161dcba340 on master.


Test Issue created at Sun, 28 Nov 2021 02:19:51 GMT

Test issue body  Sun, 28 Nov 2021 02:19:51 GMT

Comment on issue at Sun, 28 Nov 2021 02:19:53 GMT


StatusBar.setHidden crashes when passed undefined on Android

Description
StatusBar.setHidden crashes on Android when passed undefined. e.g. StatusBar.setHidden(undefined). I would expect this to have been evaluated as falsy, which seems to be the case in iOS. Looks like it also happens with null.
React Native version:
info Fetching system and libraries information... System:     OS: macOS 10.15.7     CPU: (8) x64 Intel(R) Core(TM) i5-1038NG7 CPU @ 2.00GHz     Memory: 1.09 GB / 16.00 GB     Shell: 5.7.1 - /bin/zsh   Binaries:     Node: 12.16.2 - /usr/local/bin/node     Yarn: 1.19.1 - /usr/local/bin/yarn     npm: 6.14.4 - /usr/local/bin/npm     Watchman: 4.9.0 - /usr/local/bin/watchman   Managers:     CocoaPods: 1.8.3 - /Users/ShaneMcNamara/.rvm/gems/ruby-2.2.0/bin/pod   SDKs:     iOS SDK:       Platforms: iOS 14.4, DriverKit 20.2, macOS 11.1, tvOS 14.3, watchOS 7.2     Android SDK: Not Found   IDEs:     Android Studio: 4.0 AI-193.69<IP_ADDRESS>21437     Xcode: 12.4/12D4e - /usr/bin/xcodebuild   Languages:     Java: 1.8.0_222 - /usr/bin/javac     Python: 2.7.16 - /usr/bin/python   npmPackages:     @react-native-community/cli: Not Found     react: 16.13.1 => 16.13.1      react-native: https://github.com/expo/react-native/archive/sdk-39.0.2.tar.gz => 0.63.2      react-native-macos: Not Found   npmGlobalPackages:     *react-native*: Not Found
Steps To Reproduce
Put this code in App.js: StatusBar.setHidden(undefined)
https://snack.expo.io/@ontraccr/grumpy-chocolates

Closing as stale


Update @oacore/design

Fixes images in the header when the CSS is not loaded accidentally.

The PR is outdated and conflicting already.


Issue with logger

Describe the bug
Error log seems to not show completely instead shows text "error"

To Reproduce
Create any kind of error and log it using logger library.
Expected behavior
It should show a full error object.

Can't really find a fix. A workaround is to do logger.error(JSON.stringify(error))

Added a fix at #63


Wrong message logged when a JDBC user store is created

Steps

Create a JDBC user store (tried in the tenant domain)
Verify logs

Issue
It says an LDAP connection is created instead of JDBC
[2018-02-20 14:18:38,506] @abc.com [1] [IS] INFO {org.wso2.carbon.user.core.ldap.ReadWriteLDAPUserStoreManager} -  LDAP connection created successfully in read-write mode

Above log is not related to the user store creation process. It is printed while verifying whether the logged in user is authorized to perform the operation. For that, IS requires user realm. IS first checks whether realm is available in the realm cache and if not available, IS will initialize a new user realm. In that case, you will see the above log which related to your primary user store(LDAP).


Es6 import

Import ("something") does not work but import "something" works. Was wrong?

import ( is not valid syntax. If you want normal synchronous imports, use import; if you want asynchronous imports, use import( (no space)
Closing, since this is not enzyme-related.

Okay, I know that. was typos.
the problem remains I do not know why !!!


Adding new images to an existing task

The issue of adding additional images to a task was raised before here.
Are there currently any updates on this issue ?
I agree that it would be very useful and time-saving if there is an option to add new images later, is this possible now? Unfortunately, I am not able to find this option.
Otherwise, is there a work around, for ex. is it possible to load a new dataset (i.e. including previous images and newly added images), and in parallel load the text files with bounding boxes for those images that were already annotated ?

@RRighart , please use project feature. You can think that a project is a dataset. Every task in the project can be in a specific subset (e.g., train, test, val). Jobs help you to annotate a task in parallel by several annotators. If you want to add a couple of images to a task, just create a project and move both tasks into the project.

The suggestion to use a project instead does not necessarily serve as good workaround here. This is because an annotation schema is modeled per project to allow multiple tasks to share this schema. When modeling tasks as separate projects there is no function to use a common annotation schema.
So having the option to add new images to an existing dataset would be a useful enhancement.

@holgerbrandl , you can create multiple projects. One project for each dataset. I'm not sure which scenario isn't covered. Could you please explain?

Sure, I can create multiple projects. But there is no mechanism to ensure that they share the same common annotation model.
Tasks on the contrary share the annotation model of the project.

@holgerbrandl
Could you clarify what is the same common annotation model?

Sure thing. We have a common set of annotation that we use to annotate images across different data-sets. These can be defined on project level in cvat and then are propagated into the indivdual tasks/jobs within the project.
Example (just to illustrate where those annotations are defined)

Okay, I see. You are speaking about labels specification, right?

But there is no mechanism to ensure that they share the same common annotation model.

You can copy the specification from one project to another using Raw tab (just with Ctrl+C, Ctrl+V).
In this case specification are identical.

That's nice workaround for an intial setup. Still, it requires quite some effort to keep them in sync. That's why I'd think this ticket is valid/open.

Personally I do not have ideas how it could be implemented. Maybe I do not truly understand the use-case and why you can't use one project with a certain labels specifications.
If the community is ready to provide a common solution, it would be great.
We are not planning to implement it for now.

@holgerbrandl , I agree with Boris. Need to understand why you think it is a workarond but not a solution for your problem. Basically in CVAT

A project is a dataset
A task is a portion of data (you can mark some images as deleted now)
A job is an annotation work (way to parallel tasks between multiple labelers)

It's all about keeping projects well organized. Assuming I have complex set of annotations defined for a project, and have separate 2 tasks (e.g. for different types of objects, let's say planes and cars), and I happen to find another important image of a car, we currently have to create a new task in the project for just this single image, leading to redundancy in the project layout.
That's why it would imho be a nice feature in CVAT if a user could simply add an image to an existing task.

We do not provide ability to add images to existing tasks because of current concept. The use-case you described has a solution as a creating a new task (considering a project as a whole dataset). The task in this case includes all the project labels, so you do not need to setup them again.

Was this ever implemented?  I would also like the ability to add images to an existing task.
My use case is that data is submitted from multiple sources and my dataset is growing.  It would be convenient to annotate all of one source's images within one task, and another source's images within another task.  This is because there will be commonalities within a given source's images, and looking at prior annotated images from that source would be helpful in annotating new images.
Our project is still stealthy, so I can't go into great detail, but I will try to answer any clarifying questions.

If there are repeated images in a project across multiple tasks, it seems it does not update them. Rather it simply repeats them, then throws out an error when u try to export. Also makes it harder to annotate and quality check if there are repeated images across a project throughout several tasks

0.5

Was this ever given further consideration or implemented? I would also like the ability to add images to an existing task.
My use case is that data is submitted from multiple sources and my dataset is growing. It would be convenient to annotate all of one source's images within one task, and another source's images within another task. This is because there will be commonalities within a given source's images, and looking at prior annotated images from that source would be helpful in annotating new images.
Our project is still stealthy, so I can't go into great detail, but I will try to answer any clarifying questions.

I agree with this hard. Many use cases fall under this category

@siddagra , @PercipioCorey , please use projects. You can add new tasks into a project. It is how the use case is supported.

HI. I am not understanding this ( as usual). My scenario. I have created a project and added a video. I have used rectangle tracks on various objects. I export as Yolo1 and have a python script that trains the data and produces the best.pt file. Now that I have tested this and the results are ok I need to add a few more videos and product images to the project then annotate them and output all these to Yolo 1. Sorry for being dome but how do I add files to the project. Cheers

@siddagra , @PercipioCorey , please use projects. You can add new tasks into a project. It is how the use case is supported.
@nmanovic

How are duplicates handled in such a case?

+1 for adding images to an existing task. There are many use cases where datasets grow organically. For example, let's say I use a GCP bucket and I have devices that automatically add images to the bucket. There shouldn't be any friction in CVAT to automatically expand a task to annotate latest images.

Hi all, let's discuss and see if we can improve CVAT in the case. But our current model is the following:
Project = Dataset
Task = a part of the project
Job = actual work to annotate a task (a task can be split on multiple jobs and annotated in parallel)
The proposal pipeline:

Create an empty project (dataset)
Create as many tasks as you need. With each task you can add new images. Each task can be assigned to a specific subset (train, test, val, etc)
Annotate tasks in parallel using jobs.

There are multiple issues with extending a task. Let's say you annotate something and mark it as completed. Now you have new data. In which task you want to add new images automatically or manually? Why do you need it if you can create a new task with new data?
When you need to export your dataset, just do that. Export your project with all tasks.

@nmanovic I won't answer for automatic or manual extension because I think each user has different ways to do it (automatic is just a script that performs manual steps using CVAT's APIs or otherwise).
For us the use case was that a project provides the labels (use project's labels when creating task), and each task represents a subset of the data. Let's say as an example that task1 contains images of animals indoors and task2 contains images of animals outdoors.
It's very useful in this case to only have 2 tasks that are extensible so that when new images are collected and added they are separated based on indoor/outdoor categories by default using the task separation.
This is useful because:

When exporting the task annotations, they're all already split by task and they can be further split to train,val without having to manually select and calculate dataset balance (I know the total of images in task1 are 1000 are split 80%-20% and I have 800-200 images of indoors animals in my train-val split, so I can adjust my train-val split percentages in task2 folder to achieve the data proportions as I want).
When annotating teams can be split to these tasks and their sub-jobs knowing how many images they've annotated in total for each category (no need to sum tasks).
You have a clear separation of data divisions in each task (can be anything from indoor vs. outdoor data example to good vs. bad previous annotations, annotations to verify vs. new annotations etc.).
When new images/data is collected and added to the dataset, there can be a separation by default in CVAT (per extensible task) so that the annotated dataset "evolves".

These are just a few of the reasons on top of my head. I also just think that it's natural since removing images from a task/job is already an available feature, so adding is just an expected functionality for the average user (hence the number of issues regarding this).
Thanks for your interest in this and hope we can develop this within the CVAT community!


kitty: 0.8.2 -> 0.9.0

Motivation for this change
kitty: 0.8.2 -> 0.9.0
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option build-use-sandbox in nix.conf on non-NixOS)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[x] Fits CONTRIBUTING.md.

@GrahamcOfBorg build kitty

No attempt on x86_64-darwin (full log)
The following builds were skipped because they don't evaluate on x86_64-darwin: kitty
Partial log (click to expand)

a) For `nixos-rebuild` you can set
  { nixpkgs.config.allowUnsupportedSystem = true; }
in configuration.nix to override this.

b) For `nix-env`, `nix-build`, `nix-shell` or any other Nix command you can add
  { allowUnsupportedSystem = true; }
to ~/.config/nixpkgs/config.nix.

Failure on aarch64-linux (full log)
Attempted: kitty
Partial log (click to expand)
   Compiling rustc_allocator v0.0.0 (file:///build/rustc-1.25.0-src/src/librustc_allocator)
   Compiling rustc_resolve v0.0.0 (file:///build/rustc-1.25.0-src/src/librustc_resolve)
   Compiling rustc_const_eval v0.0.0 (file:///build/rustc-1.25.0-src/src/librustc_const_eval)
   Compiling rustc_typeck v0.0.0 (file:///build/rustc-1.25.0-src/src/librustc_typeck)
building of '/nix/store/7z1kx6f9q94aq3876p65hqq73xvvs2bs-rustc-1.25.0.drv' timed out after 3600 seconds
cannot build derivation '/nix/store/dhvv09cbs47bw6k9kdwlxg4czk4736xs-cargo-0.26.0.drv': 1 dependencies couldn't be built
cannot build derivation '/nix/store/p14363m9a0jm6ay9dbjmf058hyk5pgsp-librsvg-2.42.2.drv': 2 dependencies couldn't be built
cannot build derivation '/nix/store/502ddiji235kxnw83sp6jvm0drg7qxqn-imagemagick-6.9.9-34.drv': 1 dependencies couldn't be built
cannot build derivation '/nix/store/q4a99356g4xdql6qss7j8bj68qyywf1x-kitty-0.9.0.drv': 1 dependencies couldn't be built
error: build of '/nix/store/q4a99356g4xdql6qss7j8bj68qyywf1x-kitty-0.9.0.drv' failed

Success on x86_64-linux (full log)
Attempted: kitty
Partial log (click to expand)
these paths will be fetched (2.87 MiB download, 13.67 MiB unpacked):
  /nix/store/6v9sy026n51p2akmny8467bwnr1x279j-imagemagick-6.9.9-34
  /nix/store/877gfqm6c6m4sj59yq83r6igxhfy8ilg-kitty-0.9.0
copying path '/nix/store/6v9sy026n51p2akmny8467bwnr1x279j-imagemagick-6.9.9-34' from 'https://cache.nixos.org'...
copying path '/nix/store/877gfqm6c6m4sj59yq83r6igxhfy8ilg-kitty-0.9.0' from 'https://cache.nixos.org'...
/nix/store/877gfqm6c6m4sj59yq83r6igxhfy8ilg-kitty-0.9.0


Windows Terminal: Open terminal in current folder via single command

Currently I can open cmd and powershell in the current folder via typing cmd or powershell in the address bar of explorer (which opens via CTRL+D, so it's really neat and quick).
It would be great if this was also possible with the new Windows Terminal. But since it's a Windows Store app I can't find an easy way to add it to PATH. It also doesn't respect the current folder when opening. It always starts in the default folder (C:\WINDOWS\system32 for cmd and ~ for Ubuntu).
It would be great if this was possible:

Make it possible to add Windows Terminal to PATH.
Open the command line in the current folder in Windows Terminal.

It would also be nice if it could be opened with a short command.
The executable currently is called WindowsTerminal. Would be nice if we could simply type something like term.

What happens if you use wt.exe ?
https://github.com/microsoft/Terminal/blob/af7316c130059ba15fe16ff0d13608d956a2b449/src/cascadia/CascadiaPackage/Package.appxmanifest#L51
The alias should already launch a WindowsTerminal, but I'm not sure if it launches in the path that you specify

@joandrsn This is great, I didn't know. Thanks.

@joandrsn Thanks! It even launches in the current directory!

How do you pass a directory path to wt.exe:
wt.exe "C:\GitHub"

Tried but Always opens in Default folder for both CMD and PowerShell.
I can open the WSL Ubuntu shell in the current folder with ubuntu run. but wt always opens in the default folder

Remove startingDirectory from your profiles.json.

Hello @DHowett-MSFT,
is there a way to ask Windows Terminal open new tab in the same folder as current tab? I want the same behavior as exist on Mac OS X: https://apple.stackexchange.com/questions/178017/how-do-i-open-a-new-terminal-window-for-same-directory-as-the-current-window.
Thanks in advance!

Remove startingDirectory from your profiles.json.

@DHowett-MSFT, this doesn't work in the latest version 0.5.2661.0  :(

Remove startingDirectory from your profiles.json.

For me, it doesn't work either :(

As of v0.5, that actually won't work any longer. You'll need to set "startingDirectory": null for this to work actually. That fix regressed unintentionally in #2515.

As of v0.5, that actually won't work any longer. You'll need to set "startingDirectory": null for this to work actually. That fix regressed unintentionally in #2515.

Thank you @zadjii-msft.

I'd also like to open new tabs in the current directory, and in V0.5.2681.0 "startingDirectory": null just takes me to "C:\WINDOWS\system32>"

As of v0.5, that actually won't work any longer. You'll need to set "startingDirectory": null for this to work actually. That fix regressed unintentionally in #2515.

@zadjii-msft , this doesn't work in v0.5.2681.0

As of v0.5, that actually won't work any longer. You'll need to set "startingDirectory": null for this to work actually. That fix regressed unintentionally in #2515.

Does not work with 0.5.2762.0 either..

To be clear, removing startingDirectory instead of setting it to null isn’t a feature that’s coming back; we are looking at alternative approaches regarding when exactly to apply startingDirectory, but the setting will always be able to be suppressed by setting it to null.

As of v0.5, that actually won't work any longer. You'll need to set "startingDirectory": null for this to work actually. That fix regressed unintentionally in #2515.

Does not work with 0.5.2762.0 either..
I have tried removing value, setting to null.. both does not change anything..

"startingDirectory": null  works for me - it needs to be put under a specific profile, rather than being a root-level element

@DHowett-MSFT it seems to me that an approach of having settings in a config file (startingDirectory) which can be overriden by passing in command line params is pretty common in general. Maybe I'm not getting the issue here :)

If I recall the conversation from last month, it was:
Clearing the “startingDirectory” setting by deleting it from your user profile (in the specific case of the two or three default shipped profiles), instead of setting it to null to clear it, is not a feature that will be coming back.
#607 specifies that we will support command line arguments, one of which will be the starting directory override.
This seems to be in line with my understanding of your understanding of this conversation. :smile:

For me setting "startingDirectory": "." does the job.

is there another issue for having the terminal default open to say  "%USERPROFILE%" but null if launched from windows explorer? the current behaviour is quite annoying

@carlinmack I don't think that's necessary.

The Windows Terminal defaults to the user's home directory if you launch it via the Start menu shortcut or via typing "wt" in Win+R. Which means that if you use "startingDirectory": "." they still open in the user's home folder (%USERPROFILE%).
If you launch wt from the Windows Explorer address bar, or via something like cmd.exe (or another shell) navigated to a certain folder, then the "startingDirectory": "."  will ensure that Windows Terminal opens in the directory you were in.

The Windows Terminal defaults to the user's home directory if you launch it via the Start menu shortcut or via typing "wt" in Win+R. Which means that if you use "startingDirectory": "." they still open in the user's home folder (%USERPROFILE%).

It defaults to system32 in those case for me.

Thanks @torpederos
"startingDirectory": "."
"startingDirectory": "%__CD__%"
Checked. Both works fine for me. My solution.
@RickStrahl have written a good blog regarding this issue. Check it out.

In my case this worked.
"profiles":
    {
        "defaults":
        {
            "startingDirectory": "."
        },

"startingDirectory": "." works but when I open terminal from search it defaults to system32.
Is there any way to open in the user directory when the path is not specified?

"startingDirectory": "." works but when I open terminal from search it defaults to system32.
Is there any way to open in the user directory when the path is not specified?

I had the same problem. I fixed it by adding the following line at the end of my .bashrc file.
if [ "$CURR_DIRECTORY" = "/mnt/c/WINDOWS/system32" ]; then     cd ~ fi

Solution of @manishprivet was great, except that In order to work properly, I have changed the system32 to System32. It's a good idea to run pwd and copy the output.

I found a workaround by adding "open terminal here" to right-click.
step-1:-
Remove the starting directory from the settings.json for all profiles.
step-2:-
Add the open terminal to right-click according to this post.
https://github.com/microsoft/terminal/issues/1060#issuecomment-497539461
I changed the 2nd registry value from @="%LOCALAPPDATA%\\Microsoft\\WindowsApps\\wt.exe" to @="C:\Users\[your username]\AppData\Local\Microsoft\WindowsApps\wt.exe -d  ."
Behaviour after modifications:
So whenever I open terminal using search/taskbar/shortcut it will open in my user folder.
Whenever I want to open the terminal using the explorer, I just right-click and select Windows terminal here option.
Note 1: Don't forget to add -d . at the end of the second registry value, otherwise, this will not work.
Note 2: Typing wt in explorer bar still doesn't work. You should still type wt -d . if you want to open terminal in the current folder using the "explorer bar".

Just add
"startingDirectory": null

It works with wt V1.0 properly.
If you prefer making wt shown in SHIFT-Menu just like "Open PowerShell window here" or Open WSL options,
you can merge this registry file to your Registry.
Windows Registry Editor Version 5.00

[HKEY_CLASSES_ROOT\Directory\Background\shell\wt]
@="Open Windows Terminal here"
"ShowBasedOnVelocityId"=dword:00639bc8
"Extended"=""

[HKEY_CLASSES_ROOT\Directory\Background\shell\wt\command]
@="C:\\Users\\LKT\\AppData\\Local\\Microsoft\\WindowsApps\\wt.exe"

Please note the startingDirectory parameter should go in this place in the JSON structure:
{
    //...

    "profiles":
    {
        "defaults":
        {
            // Put settings here that you want to apply to all profiles.

            // Attempt to start in current directory
            // https://github.com/microsoft/terminal/issues/620
            "startingDirectory": "."
        }
    }
}

I'm yet to see a solution that will do the following:

Allow me to select a default directory when I open Terminal from start menu.
When running wt.exe from explorer window will open Terminal to that directory.

Is this possible?

From my investigation, that wasn't something that was technically possible.
If you want both to work, you'll need to use wt -d . in the explorer address bar. This will let launching the Terminal from the start menu and the run box work the same as before, and still let you open the Terminal in the CWD in explorer

@AndeYashwanth That works perfectly, thank you. Now I can have it open in my user directory from the taskbar and only open in the current directory when I right click 😎

Thanks @29kartik approach 1 worked for me. I was able to get GitKraken to use a custom terminal command of wt -d %d so that now it's terminal shortcut launches WT at the current repo's directory. 💯

I've added this to open in this specific folder
 "startingDirectory": "C:\\webdev"

This is my take on it via context menu shortcut: https://gist.github.com/kmantel/9cd6bf9f0fb25694a5b08119817281b7

Remova startingDirectorydo seu profiles.json.

Para mim, também não funciona :(

use:
"profiles":
{
"defaults":
{
// Put settings here that you want to apply to all profiles.
"startingDirectory": "D:/Ws"

@nickraphael:

I'm yet to see a solution that will do the following:

Allow me to select a default directory when I open Terminal from start menu.
When running wt.exe from explorer window will open Terminal to that directory.

Having this in settings.json:
{
    "profiles": {
        "defaults": {
            "startingDirectory": "."
        }
    }
}

makes Windows Terminal start in the current directory for me when launched from Explorer location box, win+r or from other programs (VS Code etc.). However, when starting from Start menu, either by searching or navigating to the shortcut, it starts in C:\WINDOWS\system32.
To fix the Start menu issue, I pinned a shortcut to wt.exe to the Start menu (where wt tells its location), renamed the shortcut to my liking and then modified it to have:
Start in: %USERPROFILE%

Now Windows Terminal starts in my home directory when launched from the Start menu.
It would be nice if Windows Terminal wouldn't change its directory by default to make it more transparent. There aren't many other programs which do that.
I'm also wondering if the shortcut to wt.exe could be made by the installer automatically.

So, none of the above answers worked for my use case. What I'd like to do is open a new tab using alt+shift+- and keep the previous folder. I tried using null, "." and "%__CD__%" as values for "startingDirectory" in different places of the JSON. I'm using version 1.4.2652.0 of Windows Terminal Preview.
One nice solution would be to have a new option like "keepCurrentDirectoryOnNewTab": true or something like that. Other way that Kitty uses is having a special value called current when specifying the directory.

@frankitox You're probably interested in #3158 and the like 20 issues that are duped to that thread

There's been quite the discussion of why this is hard or nearly impossible to do correctly on windows.

VERSION: 1.3.2651.0
in my case it works.
    "profiles":
    {
        "defaults":
        {
            // Put settings here that you want to apply to all profiles.
            "startingDirectory": "."
        },

also, you can use "startingDirectory": "%__CD__%"

VERSION: 1.3.2651.0
in my case it works.
    "profiles":
    {
        "defaults":
        {
            // Put settings here that you want to apply to all profiles.
            "startingDirectory": "."
        },

also, you can use "startingDirectory": "%__CD__%"

This works like a charm!

I am probably very late to the party, but in Windows 10 Pro 20H2, you can just type wt in the address bar and it will do the trick.

How do you pass a directory path to wt.exe. Something like this:
wt.exe "C:\GitHub"

I don't know if you found -d and path

wt -d .

works well in WSL2

You can set up the starting directory using your preferred address, either globally or for a specific profile. To have a context menu to open it in the current folder, create and save a .reg file with the content below:

Windows Registry Editor Version 5.00

[HKEY_CLASSES_ROOT\Directory\Background\shell\windowsterminal]
@="Windows Terminal Here"
[HKEY_CLASSES_ROOT\Directory\Background\shell\windowsterminal\command]
@="\"C:\\Users\\{USERNAME}\\AppData\\Local\\Microsoft\\WindowsApps\\wt.exe\" -d ."

Double click the saved file to add these entries to the registry.

This is working on my laptop
"profiles":
    {
        "defaults":
        {
            // Put settings here that you want to apply to all profiles.
            "startingDirectory" : "%USERPROFILE%"
        }
}

Does anybody know why "startingDirectory": "." in default profil is no longer working on 1.6.10571.0?
Also wt nt will open a new window instead of a new tab.
clicking the + button to open a new tab also no longer reuses the startup directory of the first tab. 😕

Does anybody know why "startingDirectory": "." in default profil is no longer working on 1.6.10571.0?

Nope, you should probably file a new issue so we can follow up with you and figure out what's going on

Also wt nt will open a new window instead of a new tab.

That's how it has always worked - in 1.7 there's windowingBehavior and --window <id> to help control this.

clicking the + button to open a new tab also no longer reuses the startup directory of the first tab. 😕

Pretty sure that's how it's always worked - it'll always use the startingDirectory of the default profile, and if your default profile's startingDirectory is ., then it'll use the directory the terminal was launched from.

Does anybody know why "startingDirectory": "." in default profil is no longer working on 1.6.10571.0?

Nope, you should probably file a new issue so we can follow up with you and figure out what's going on

Also wt nt will open a new window instead of a new tab.

That's how it has always worked - in 1.7 there's windowingBehavior and --window <id> to help control this.

clicking the + button to open a new tab also no longer reuses the startup directory of the first tab. 😕

Pretty sure that's how it's always worked - it'll always use the startingDirectory of the default profile, and if your default profile's startingDirectory is ., then it'll use the directory the terminal was launched from.

I'm using the context menu to open wt in a specific folder (using the entry generated by wt). That will open the first tab in that folder, but new tab will open in system32.
Before i used my own context menu entry:

Yep, that's exactly how it works. You might be interested in #8933

I had the same problem. I fixed it by adding the following line at the end of my .bashrc file.

@manishprivet Is this possible in windows?

I had the same problem. I fixed it by adding the following line at the end of my .bashrc file.

@manishprivet Is this possible in windows?

@kaaax0815 Yes this is for windows only

@kaaax0815 Yes this is for windows only

@manishprivet But bashrc would be wsl not native windows. Or where should I put it

@kaaax0815 Yes this is for windows only

@manishprivet But bashrc would be wsl not native windows. Or where should I put it

@kaaax0815 In the WSL's bashrc file actually

@manishprivet the matter has resolved itself. I changed the cmd search shortcut to wt and this fixed the path problem

You can now just go to settings -> profiles (Powershell / Command prompt) And check the checkbox: 'Use parent process directory'

@KSneijders unfortunately we do not have that on wsl :(

actually we do, but it does not work

power shell also does not work

So, none of the above answers worked for my use case. What I'd like to do is open a new tab using alt+shift+- and keep the previous folder. I tried using null, "." and "%__CD__%" as values for "startingDirectory" in different places of the JSON. I'm using version 1.4.2652.0 of Windows Terminal Preview.
One nice solution would be to have a new option like "keepCurrentDirectoryOnNewTab": true or something like that. Other way (that Kitty uses) is having a special value called current when specifying the directory.

this worked for me:

in windows terminal, under default profile, add startingDirectory value to "."
if you are going with explorer, in the address bar type "wt" and it will open your default profile in that directory
for every profile add a value of "startingDirectory" to "."

If anyone is looking for a solution without changing the startingDirectory, I have placed such a file in %SystemRoot\System32 named wtx.cmd:
@ECHO off
wt -d .
exit /B !ERRORLEVEL!

Remove startingDirectory from your profiles.json.

Thanks @DHowett-MSFT, I was making VSCode when pressing ctrl+ñ the external console wt.exe appears, because the integrated one has problems with UTF8 in windows and, when I did it, it always started in my %USERPROFILE%, your solution worked, now runs in my project directory.
For those who are interested, I used wt --window 0 focus-tab so that if I already have a WindowsTerminal window open, it will be raised instead of creating another instance.

You can now just go to settings -> profiles (Powershell / Command prompt). And check the checkbox: 'Use parent process directory'

thank you! this solution is the best solution. and still working

Current directory in Windows terminal using explorer
You can open current directory in Windows terminal using explorer using
wt -d .

1.15.3465.0
"wt -d ." doesnt work any more for me :-(

Please add wt -d

@jleaders the help text is understandably a little confusing in this particular case, because of the implicit new-tab subcommand that's used when no subcommand is provided explicitly. You'll note, -d is under wt new-tab --help

It's just that CLI11 doesn't know how to wire the args for new-tab up to the help message for the root command's help text.

@nphmuller Referring to the first main discussion of thus topic, you can open a new terminal windows, placed in the current working folder, by typing "cmd" and press Enter in the url   ##bar.

solution wt -d .

[ Settings : "Startup" → "standard terminal application" ] change this to windows terminal -> All Terminals open now in the Windows Terminal.

how to use %USERPROFILE% without Use parent process directory in start menu?

The default behavior of cmd.exe, powershell.exe, and pwsh.exe is to start in the current directory when invoked from any shell or the File Explorer address bar, or to open in %USERPROFILE% when invoked elsewhere (such as Run or Start Menu shortcuts).
wt.exe deviates from this behavior. If you have the starting directory set to .,  it will still start in C:\Windows\System32 when invoked from a shortcut or the Start Menu. Why?
For those frustrated by this, here's a script you can put on your PATH that works from any shell, File Explorer, or Run.
wtd opens a normal window in the current directory.
wtd a opens an elevated window in the current directory.
wtd.cmd:
@echo off
if "%1"=="a" (
    net session >nul 2>&1 || (
        powershell -c "start -v runas '%~f0'"
        exit
    )
)
wt -d .

When you have Terminal set as your default console host, you can also just go back to launching cmd, powershell or pwsh directly from the file explorer address bar or whichever shell...

When you have Terminal set as your default console host, you can also just go back to launching cmd, powershell or pwsh directly from the file explorer address bar or whichever shell...

Yeah but all of those are more verbose than typing wt.
Besides, how would you launch Git Bash? Users should be able to invoke their default console host in the current directory when calling wt from that directory in File Explorer.
And it should never, ever default to opening in a system directory such as System32.


Add missing  environment variable for enabling smtp

So there is actually a missing environment variable from the charts/graylog/_helpers.tpl file, without it the email alerting won't work.
https://go2docs.graylog.org/5-0/downloading_and_installing_graylog/docker_installation.htm
GRAYLOG_TRANSPORT_EMAIL_ENABLED

fixes #1380


Missing back button on lecture details page

Describe the bug
The lecture details page doesn't contain a back button to go the previous page. This leads to an inconsistent user experience since the exercise details page contains a back button to go back to the previous page.
To Reproduce

Go to  a course that contains lectures.
Click on a lecture to open the lecture details page.
See that the back button is missing and there's no other possibility to go back, besides using the navigation elements of the web browser.

Expected behavior
A back button is visible and clickable on the lecture details page that behaves in the same way as the one on the exercise details page.
Screenshots

What browsers are you seeing the problem on?
Chrome, Firefox
Additional context
No response
Relevant log output
No response

The browser contains a back button, so there is no need for Artemis to offer one.
We previously implemented breadcrumbs for a much improved user experience regarding navigation and added it to course administration. We have not been able yet to roll it out to all pages under the section course overview.
We will do that in the coming months and then remove all back button within the Artemis app.

@krusche Do we need to keep this open then?

We can close it


Generate a header in codeowners file so maintainers know where to make edits

Similar to https://github.com/GoogleCloudPlatform/cloud-foundation-toolkit/blob/65d01e40e94e6ee47f9c3f22e6f26accb8cf54cd/infra/terraform/modules/lint_file/lint.yaml.tftpl#L15-L16

We should also tweak the template formating - current there is an extra space if groups, but no users, are included as owners.


Warning : Use of OsiCbc is deprecated

When starting .solve(), I get a warning :
Warning: Use of OsiCbc is deprecated.
To enjoy the full performance of Cbc, use the CbcSolver interface.

Does Rehearse support CbcSolver ?

No, not yet.


Error messages from server are always in English

The Zulip server attempts to localize error messages using the language sent in the HTTP Accept-Language header. Unfortunately, we don't send that when making API calls.
The fix is probably to ensure that the locale value is available in the Auth object, so that apiFetch (or one of its callees) will have it on hand to construct an appropriate Accept-Language header.

The fix is probably to ensure that the locale value is available in the Auth object, so that apiFetch (or one of its callees) will have it on hand to construct an appropriate Accept-Language header.

Hmm. Yeah, something like this makes sense.
What's the appropriate way to construct an Accept-Language header? We'll want to make sure we get the language/locale name into the right form for that.

In theory, something along the lines of Accept-Language: xx[-YY] (case-insensitive). There are reasonably-full docs here, including a multilingual selection feature we probably have neither a use for nor any concern about.
In practice, of course, the appropriate way is "whatever the Zulip server expects", which seems to be "whatever Django expects"; this is documented to be at least xx and xx-yy.


Upgrade to CircleCI v2

What's this PR do?
What the title says.
Why are we doing this? How does it help us?
CircleCI v1 is losing support soon.
How should this be manually tested?

Install the CircleCI command line client by following the instructions here: https://circleci.com/docs/2.0/local-jobs/
circleci config validate -c .circleci/config.yml
circleci build - this step should take a while and you'll see some expected errors like this: Error: FAILED with error not supported. But as long as you see Success! at the end then it worked.

Have automated tests been added?
Tests for the tests? No.
Has this been tested on mobile?
NA.
Are there performance implications?
No.
What are the relevant tickets?
https://3.basecamp.com/3098728/buckets/736178/todos/1181274383
How should this change be communicated to end users?
NA.
Next steps?
Find out what other apps need to be upgraded.
Smells?
NA.
TODOs:
NA.
Has the relevant documentation/wiki been updated?
NA.
Technical debt note
Less.

LGTM.