Can't work in ST4

Nothing happens after pressing enter. No line breaks.

I'm also having this issue.

ignoring plugins in package DocBlockr_Python, version file Packages/DocBlockr_Python/.python-version contains an invalid version: "3.4.3\n"
Looks like an issue with .python-version

I'm also having this issue.

I think I solved this issue.
The 93rd line of the source code file commands.py is raise Exception, which will cause this raise under any circumstances, commenting it out can solve this issue.

I think I solved this issue.

I just tried to use it, and I'm still having the problem. I do the """ and press enter... and nothing.
Nothing in the console, nothing happens in the pane.

Sample video:
https://user-images.githubusercontent.com/51874567/120216254-5b0f0e00-c269-11eb-83f5-d8df05971988.mov
Remove the .zip in the following file name, and put it in:
-Mac: $HOME/Library/Application Support/Sublime Text/Installed Packages
-Linux: $HOME/.config/Sublime Text/Installed Packages
-Windows: %APPDATA%\Sublime Text\nstalled Packages
These paths are not necessarily accurate, you need to find the directory of sublime text Installed Packages.
DocBlockr_Python.sublime-package.zip

DocBlockr_Python.sublime-package.zip

__MACOSX/._commands.py in /home/trefmanic/.config/sublime-text-3/Installed Packages/DocBlockr_Python.sublime-package is not utf-8 encoded, unable to load plugin
After removing __MACOSX directory from the package file DocBlockr works.

After change to 3.3 in https://github.com/adambullmer/sublime_docblockr_python/blob/master/.python-version, it works for me.

This also works, thanks!

DocBlockr_Python.sublime-package.zip

I optimized some functions and modified some codes of this package. If you are interested, you can clone the following warehouse locally and put it in the Packages directory. You can use it without packaging.
But it can only be used in ST4.
https://github.com/thep0y/sublime_docblockr_python

This still hasn't been fixed for me at all, why was this closed?


Remove functions.py

Necessary pieces moved into MLIRFunctionBuilder
Remove hard-coded headers as much as possible

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

61 of 63 (96.83%)  changed or added relevant lines in 5 files are covered.
10 unchanged lines in 4 files lost coverage.
Overall coverage decreased (-0.4%) to 83.15%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

mlir_graphblas/types.py
10
12
83.33%

Files with Coverage Reduction
New Missed Lines
%

mlir_graphblas/engine.py
1
75.29%

mlir_graphblas/ops.py
2
85.89%

mlir_graphblas/mlir_builder.py
3
93.09%

mlir_graphblas/tests/test_profile.py
4
51.95%

Totals

Change from base Build<PHONE_NUMBER>:
-0.4%

Covered Lines:
2724

Relevant Lines:
3276

💛  - Coveralls

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Warning: This coverage report may be inaccurate.
This pull request's base commit is no longer the HEAD commit of its target branch. This means it includes changes from outside the original pull request, including, potentially, unrelated coverage changes.

For more information on this, see Tracking coverage changes with pull request builds.
To avoid this issue with future PRs, see these Recommended CI Configurations.
For a quick fix, rebase this PR at GitHub. Your next report should be accurate.

Details

56 of 58 (96.55%)  changed or added relevant lines in 5 files are covered.
9 unchanged lines in 3 files lost coverage.
Overall coverage decreased (-0.3%) to 83.303%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

mlir_graphblas/types.py
10
12
83.33%

Files with Coverage Reduction
New Missed Lines
%

mlir_graphblas/ops.py
2
85.89%

mlir_graphblas/mlir_builder.py
3
93.09%

mlir_graphblas/algorithms.py
4
98.65%

Totals

Change from base Build<PHONE_NUMBER>:
-0.3%

Covered Lines:
2729

Relevant Lines:
3276

💛  - Coveralls

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Warning: This coverage report may be inaccurate.
This pull request's base commit is no longer the HEAD commit of its target branch. This means it includes changes from outside the original pull request, including, potentially, unrelated coverage changes.

For more information on this, see Tracking coverage changes with pull request builds.
To avoid this issue with future PRs, see these Recommended CI Configurations.
For a quick fix, rebase this PR at GitHub. Your next report should be accurate.

Details

56 of 58 (96.55%)  changed or added relevant lines in 5 files are covered.
9 unchanged lines in 3 files lost coverage.
Overall coverage decreased (-0.3%) to 83.303%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

mlir_graphblas/types.py
10
12
83.33%

Files with Coverage Reduction
New Missed Lines
%

mlir_graphblas/ops.py
2
85.89%

mlir_graphblas/mlir_builder.py
3
93.09%

mlir_graphblas/algorithms.py
4
98.65%

Totals

Change from base Build<PHONE_NUMBER>:
-0.3%

Covered Lines:
2729

Relevant Lines:
3276

💛  - Coveralls


Disk usage graph not reporting correctly

When viewing in transfer status or worker screen with many drives there is an issue with the graph.  I believe the
"For legibility, the chart shows only a random selection of paths when a worker has many of them."  is changing the path names at the bottom but not updating the chart. The bars are just showing the 1st 20 drives not aligning with the labels at the bottom
What is shown in web ui

Output from in container df -h

Confirmed, I've reverted to showing the first X number of paths ensuring path aligns with correct used/free value.  Thanks for the report.  Available in the machinaris:develop image now.

Released in Machinaris v2.1.2


[Suggestion] Ability to favorite items

The idea
It would be nice if there was a way to favorite specific items in NEI to allow for quicker and easier searching of specific items recipes.
In order to favorite an item an action such as a middle click (changeable in configuration) could be used and the background of item could be a different color or possibly have an outline of some sort around it.
There would be a few ways to potentially implement it:

Page or pages between page 0 and the final pages.
Have all favorited recipes sticky similar to a forum where they all appear at the top of the list.
Have it so the page number can be clicked to toggle between favored and the search terms. (Personally my favorite thought of implementation)

How it would be helpful
At the moment I'm attempting to play through FTB Infinity on Expert mode and a large number of recipes require an additional items or steps before them in order to craft a single item. I constantly have to click through to see the results, often multiple deep, to find out that I need another machine and need to know how to craft that. The ability to keep track of all of the items in the current process without having to press R on each item multiple steps deep would be nice as well as adding a new search term of the machines would be very helpful.
Additionally common items such as Machine Frames which are odd to remember would be nice to favourite seeing as they come up so frequently and searching them every single time is becoming a pain in the butt.

I apologize, I prematurely hit submit originally and this may have been a blank ticket sent to your email.

Wrong spot to submit an NEI suggestion, sorry. I'm a mess today. :P


[base-ui] v5.0.0-beta.9 Cannot be used as a JSX component

Duplicates

[X] I have searched the existing issues

Latest version

[X] I have tested the latest version

Steps to reproduce 🕹
No response
Current behavior 😯
with "@mui/base": "5.0.0-beta.09" => No error
https://stackblitz.com/edit/vitejs-vite-13hwh2?file=package.json,tailwind.config.js,src%2Fglobal.css,src%2Fmain.tsx,src%2FApp.tsx,src%2FPlayer.tsx,tsconfig.json,postcss.config.cjs,vite.config.ts,index.html&terminal=dev
with "@mui/base": "5.0.0-beta.10" or above =>  Error
https://stackblitz.com/edit/vitejs-vite-ymrn8b?file=package.json,tailwind.config.js,src%2Fglobal.css,src%2Fmain.tsx,src%2FApp.tsx,src%2FPlayer.tsx,tsconfig.json,postcss.config.cjs,vite.config.ts,index.html&terminal=dev
Expected behavior 🤔
No show error
Context 🔦

 ERROR(TypeScript)  JSX element type 'ButtonUnstyled' does not have any construct or call signatures.
 FILE  /home/projects/vitejs-vite-13hwh2/src/Player.tsx:60:6

    58 | ) {
    59 |   return (
  > 60 |     <ButtonUnstyled
       |      ^^^^^^^^^^^^^^
    61 |       {...props}
    62 |       slotProps={{
    63 |         root: (state: ButtonOwnerState) => ({

 ERROR(TypeScript)  'ButtonUnstyled' cannot be used as a JSX component.
  Its type 'typeof import("/home/projects/vitejs-vite-13hwh2/node_modules/@mui/base/Button/index")' is not a valid JSX element type.
 FILE  /home/projects/vitejs-vite-13hwh2/src/Player.tsx:60:6

    58 | ) {
    59 |   return (
  > 60 |     <ButtonUnstyled
       |      ^^^^^^^^^^^^^^
    61 |       {...props}
    62 |       slotProps={{
    63 |         root: (state: ButtonOwnerState) => ({

[TypeScript] Found 4 errors. Watching for file changes.

Your environment 🌎
No response

The imports were changed in https://github.com/mui/material-ui/releases/tag/v5.14.4 but it looks like without backward compatibility

@oliviertassinari Thanks! it works. I missed the changelogs
Maybe we need to update the example here as well
https://mui.com/base-ui/guides/working-with-tailwind-css/

It seems like you're encountering TypeScript errors related to the usage of ButtonUnstyled from @mui/base in your React application when using version "5.0.0-beta.10" or above.
This issue might be due to changes in the API or typings between the versions. To address this, you can try the following steps:
Check MUI Release Notes:
Review the release notes for Material-UI to see if there are any breaking changes or updates related to ButtonUnstyled:
    [Material-UI Release Notes](https://github.com/mui/material-ui/releases)

Update TypeScript Definitions:
If there have been changes in the typings, make sure that your TypeScript definitions are up to date. You can try updating your @types/mui package to the latest version:

bash

npm install --save-dev @types/mui@latest
Ensure that your tsconfig.json has the correct settings for TypeScript:
json
{
"compilerOptions": {
"types": ["mui"],
// other settings...
},
// other settings...
}
Adjust Code for API Changes:
Check the documentation or source code of @mui/base for any changes in the usage of ButtonUnstyled. Adjust your code accordingly based on the latest documentation.
Consider Opening an Issue:
If the issue persists and you believe it's a bug or an unintended breaking change, consider opening an issue on the Material-UI GitHub repository. Provide details about the problem, your versions, and steps to reproduce it.

@oliviertassinari
Now we have two input types like this that are not consistent.
import Button, {buttonClasses} from '@mui/material/Button'; => styles 1
import { Button, buttonClasses } from '@mui/base/Button'; => styles 2

Personally, I like style 2 more.
I think in the future you will probably switch the way you import everything to style 2. Because the import change in @mui/base already shows that intention

I wonder if it shouldn't have been introduced as a backward compatible change.

I thought about this, but ultimately we decided not to introduce legacy (deprecated) code in a library that's not stable yet.

The DX of having different open source projects in the same repository during the alpha and beta phase isn't ideal. It's harder to follow the changelog

I suppose a separate repo comes with as many advantages as disadvantages. I'm generally in favor of introducing clear boundaries and splitting things, but I'm aware that this can impact our DX.
We can start (and have actually started) by isolating individual products within the monorepo so they are as standalone as possible and ready to be extracted to a separate repo at some point. I also think that having a changelog per product could make it easier for developers to track changes in products they're interested in.

Maybe we need to update the example here as well
https://mui.com/base-ui/guides/working-with-tailwind-css/

@mtr1990, we did update this guide. Where do you see the old-style import?

@michaldudak  It' here:

https://codesandbox.io/s/working-with-tailwind-css-dhmf8w?from-embed=&file=/src/Button.tsx

Ah, good catch! It's fixed now.


Bug with menu on site while data loading

Describe the Issue
While the data in the interface is loading on https://tarkov.dev/, the navigation bar on the right side of the screen behaves strangely, you can see an example in the video (Extra Information).
Expected Behavior
When loading page data, the button should not behave as if it does not have enough space on the screen.
To Reproduce
This happens sometimes, you can try reloading the page.
Client
Desktop
Browser
Chrome
Relevant Console Log Output
No response
Extra Information
Link on video with that bug: https://www.youtube.com/watch?v=G1S9IcG5NJU
About soft:
Windows 10
Google Chrome versions: 120.0.6099.110

@PC-Principal I'm having trouble reproducing this issue. What screen resolution are you using?

Nevermind; I've reproduced it.

@the-hideout/reviewers do any of you know why the relevant css selectors wouldn't be working for chromium-based web browsers? It works as it should on Firefox.

This bug only seems to appear in chromium browsers when the site is deployed to main. It does not appear in chromium browsers in local testing.

I use a chromium based browser (Brave) and I just confirmed the behavior on my end as well. As to why this is occurring.. I don't really know unfortunately

Here is a guess though if we think its related to CSS and only occurs on certain browsers (I could be completely wrong).
Each browser is shipped with its own built in (or default) CSS "settings". If some CSS settings fail to load or don't have defined values, sometimes these browser defaults can take over. Perhaps the Firefox defaults do not cause issues here but the chromium based defaults are being applied during page load that is causing this visual artifact.

This is pretty much just a guess but it was my first initial hunch.

For anyone experiencing this bug, it appears only when the width of the browser is set to very specific dimensions. You should be able to make it disappear by resizing the width of the window a bit. That's not a solution, of course, but just a temporary workaround.

This seems easy to reproduce on a 1440p screen set vertically, as that width trigger the bug.

I had this happen on my first page load. Disabling this stopped the flicker in Brave:
nav.navigation ul.menu li:nth-last-child(1 of li.visible-menu-item):not(:nth-last-child(1 of li.overflow-member)) {     /* padding-right: 50px; */ }


"Freeze" a previous state?

Hi,
This is my use case:

User visits secure page (State A)
User clicks menu (State B)
User clicks sign out (State C)
Redirects to Login page (State D)
Upon login, I want them to go back to their most recent page requiring authorisation (State A)

Currently I tried to implement this by way of:
if($previousState.get().state.name != (B || C || D)) {
            $previousState.memo("menucaller");
}

With the hope that the "menucaller" memo will only save states of anything but those I want to exclude.. but it seems to not be the case.
Is there a better way of excluding specific states from registering in $previousState ?

Is there a better way of excluding specific states from registering in $previousState ?

No, there is no way to get $previousState to do what you want, sorry.  I suggest doing it yourself.  Here is an example decorating your state definitions with some custom data, then keeping track and exposing a simple API.
// Decorate the state definitions
.state('stateA', {
  data: { secure: true }
});

module.factory('SecureStates', function($rootScope, $state) {
  // Update service.previous whenever they go to a secure state
  $rootScope.$on('$stateChangeSuccess', function(evt, toState, toParams) {
    if (toState.data.secure) service.previous = { state: toState, params: toParams };
  });

  var service = {
    previous: null,
    goPrevious: function() {
      if (service.previous) $state.go(service.previous.state, service.previous.params);
    }
  };

  return service;
});

module.controller('LoginController', function(SecureStates, $scope, AuthService) {
  $scope.login = function(user, pass) {
    AuthService.authenticate(user, pass).then(SecureStates.goPrevious)(;
  }
});


Vue - Official  The code suggestions are duplicated

Vue - Official extension or vue-tsc version
2.1.10
VSCode version
1.95.2
Vue version
3.5.12
TypeScript version
5.6.3
System Info
Windows 11,Chrome

package.json dependencies
{"dependencies": {
    "vue": "^3.5.12"
  },
  "devDependencies": {
    "@tsconfig/node20": "^20.1.4",
    "@types/node": "^20.17.6",
    "@vitejs/plugin-vue": "^5.1.4",
    "@vue/tsconfig": "^0.5.1",
    "npm-run-all2": "^7.0.1",
    "typescript": "~5.6.3",
    "vite": "^5.4.10",
    "vite-plugin-vue-setup-extend": "^0.4.0",
    "vue-tsc": "^2.1.10"
  }}

Steps to reproduce
Code sample:
export default {
    data() {
        return {
            name: "101"  // Missing a comma here, move the cursor to the error to see the error message
            age: 0
        }
    },
}

Here is the error message:

Duplicate error messages appear
What is expected?
Expect only one error message to remain
What is actually happening?
Here are all the extensions I have enabled:

Link to minimal reproduction
No response
Any additional comments?
No response

The following information might be useful.
1.Start VSCode, and you will see duplicate suggestions.
2.Disable the vueVue - Official extension without starting it.
3.Restart VSCode.
4.Enable the vueVue - Official extension.
// At this point, there will be only one suggestion.
5.Restart VSCode.
// Now, the suggestions are duplicated again.

I've turned it on now.
The problem has been solved.
thank you.


Message ID in response of sendTo()

To edit / delete messages from own scripts, it is essential to have the correct message ID. With reading this from the objects, the result is most likely incorrect. So this change puts messageId and the corresponding chatId in an object and returns everything, so the calling script can use the messageId for further interaction.
Also, I shortened the code a little bit, to avoid having the same few lines 15 times.
Fixes: #280

@Apollon77
Due to the number of changes (26 files changed), please check who can review this PR.
And I'm not sure from the description whether this change is compatible to existing implementation or is a breaking change too.

Existing implementations that are making use of the data in the callback, will be effected, because it is not anymore returning the count, but the full list of message ids and chat ids. I assume that most people are not affected, because the use case of this counter is very little.


Release v0.2.0

@JuliaRegistrator register

Error while trying to register: Changing package repo URL not allowed, please submit a pull request with the URL change to the target registry and retry.

@JuliaRegistrator register

Registration pull request created: JuliaRegistries/General/88408
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a v0.2.0 -m "<description of version>" afe516356c7956ca93debf493098e15c3d5ee4a2
git push origin v0.2.0


Live link is not working.

Hey  @fruitbox12  ,
Can you check the messages I have sent you through discord?

Okay will do

Can we have a call? at discord.


Add a daemon control script of the rancher-server

I'm using some script for rancher-server control. it's includes a selection for HA-mode or standalone

Detail info.: https://github.com/goody80/rancher_server_ctl

For example

service rancher start
or
rancher start

## Automatic check the setup at 1st time
 -- Please insert the "rancher_server_port" information --
8443
 -- Do you have database for Rancher server HA mode ? [ y / n ] --
y
 -- Please insert the "mysql_host" information --
<IP_ADDRESS>
 -- Please insert the "mysql_port" information --
3306
 -- Please insert the "mysql_db_name" information --
rancher_db
 -- Please insert the "mysql_user" information --
rancher
 -- Please insert a mysql "rancher" password --

Thanks for the contribution @goody80 . If you like, we can add your script to the Installation part of the README (https://github.com/rancher/rancher#installation), you can rebase this one or create a new one.

Okay good! Thanks :)

@superseb  I'll make a new "Pull request" for part of README installation as you said :)


Unable to compile pinocchio3-preview branch with hpp-fcl

Hello,
I tried to compile pinocchio3-preview with hpp-fcl on ubuntu 20.04, but I got this error.
/home/mao/Desktop/Third-Party/pinocchio/build/include/pinocchio/multibody/geometry.hxx: In constructor ‘pinocchio::GeometryData::GeometryData(const pinocchio::GeometryModel&)’:
/home/mao/Desktop/Third-Party/pinocchio/build/include/pinocchio/multibody/geometry.hxx:47:75: error: no matching function for call to ‘hpp::fcl::CollisionObject::CollisionObject(const CollisionGeometryPtr&)’
   47 |       collisionObjects.push_back(fcl::CollisionObject(geom_object.geometry));
      |                                                                           ^
In file included from /home/mao/Desktop/Third-Party/pinocchio/build/include/pinocchio/multibody/fcl.hpp:37,
                 from /home/mao/Desktop/Third-Party/pinocchio/build/include/pinocchio/multibody/geometry.hpp:8,
                 from /home/mao/Desktop/Third-Party/pinocchio/build/include/pinocchio/parsers/urdf.hpp:10,
                 from /home/mao/Desktop/Third-Party/pinocchio/src/parsers/urdf/model.cpp:6:

I should have executed cmake correctly, right? This is the output of the cmake step.
mao@mao:~/Desktop/Third-Party/pinocchio/build$ cmake .. -DCMAKE_BUILD_TYPE=Release -DCMAKE_INSTALL_PREFIX=/usr/local -DBUILD_WITH_COLLISION_SUPPORT=ON -DBUILD_PYTHON_INTERFACE=ON
-- Package version (ROS package.xml): 2.9.1
-- Default C++ standard: 201402
-- C++ standard sufficient: Minimal required 11, currently defined: 14
-- Found Boost: /usr/include (found version "1.71.0") found components: filesystem serialization system
-- The Python bindings of Pinocchio will be compiled along the main library. If you want to disable this feature, please set the option BUILD_PYTHON_INTERFACE to OFF.
-- eigenpy FOUND. eigenpy at /opt/ros/noetic/lib/x86_64-linux-gnu/libeigenpy.so
-- PythonLibraryDirs: /usr/lib/x86_64-linux-gnu
-- PythonLibVersionString: 3.8.10
-- Python site lib: lib/python3/dist-packages
-- Python include dirs: /usr/include/python3.8
-- Checking for NumPy
--   NUMPY_INCLUDE_DIRS=/usr/lib/python3/dist-packages/numpy/core/include
--   NUMPY_VERSION=1.17.4
-- NumPy include dir: /usr/lib/python3/dist-packages/numpy/core/include
-- Found Boost: /usr/include (found version "1.71.0") found components: python38
-- Boost_PYTHON_LIBRARY: /usr/lib/x86_64-linux-gnu/libboost_python38.so
-- Python compiler: CPython
-- hpp-fcl FOUND. hpp-fcl at /opt/ros/noetic/lib/x86_64-linux-gnu/libhpp-fcl.so
-- Found Boost: /usr/include (found version "1.71.0") found components: chrono serialization
-- C++ standard sufficient: Minimal required 11, currently defined: 14
-- Found hpp-fcl Python bindings.
-- Found Boost: /usr/include (found version "1.71.0") found components: unit_test_framework
-- Doxygen rendering: using MathJax backend
-- Configuring done
-- Generating done
-- Build files have been written to: /home/mao/Desktop/Third-Party/pinocchio/build

I installed hpp-fcl by installing ros-noetic-hpp-fcl.
For reference, I was able to compile pinocchio3 without HPP-FCL dependency and pinocchio2 with HPP-FCL dependency.
Thank you for your help!

Could you provide a reproducing docker image to analyse your issue?

@jcarpent
I tried it and found that it seems to be very troublesome to do so and the generated image will be very large.
What do you think might be the cause of this compilation problem and can you give me some ideas to solve it? Thank you very much for your guidance.

Please provide the docker image

@MariaBana you can also use https://hub.docker.com/ to share easily your images.

Hello @jcarpent and @MariaBana, I created a docker container with ros-noetic, ros-noetic-hpp-fcl and the source code of Pinocchio on the pinocchio3-preview branch and I can see the same compile errors. You can reproduce it by:
docker pull fabinsch/pinocchio3-preview-hppfcl-ros-noetic
docker run -it fabinsch/pinocchio3-preview-hppfcl-ros-noetic /bin/bash
cmake .. -DCMAKE_BUILD_TYPE=Release -DBUILD_PYTHON_INTERFACE=OFF -DBUILD_TESTING=OFF -DBUILD_WITH_COLLISION_SUPPORT=ON

I think the compile problems that we are experiencing here are related to the discussions in #1798 . The error in the docker image is:
/home/workspace/pinocchio/build/include/pinocchio/multibody/geometry.hxx:47:75: error: no matching function for call to ‘hpp::fcl::CollisionObject::CollisionObject(const CollisionGeometryPtr&)’
   47 |       collisionObjects.push_back(fcl::CollisionObject(geom_object.geometry));
      |                                                                           ^
In file included from /home/workspace/pinocchio/build/include/pinocchio/multibody/fcl.hpp:37,
                 from /home/workspace/pinocchio/build/include/pinocchio/multibody/geometry.hpp:8,
                 from /home/workspace/pinocchio/build/include/pinocchio/parsers/urdf.hpp:10,
                 from /home/workspace/pinocchio/src/parsers/urdf/model.cpp:6:
/opt/ros/noetic/include/hpp/fcl/collision_object.h:229:3: note: candidate: ‘hpp::fcl::CollisionObject::CollisionObject(const std::shared_ptr<hpp::fcl::CollisionGeometry>&, const Matrix3f&, const Vec3f&, bool)’
  229 |   CollisionObject(const shared_ptr<CollisionGeometry>& cgeom_,
      |   ^~~~~~~~~~~~~~~
/opt/ros/noetic/include/hpp/fcl/collision_object.h:229:3: note:   candidate expects 4 arguments, 1 provided
/opt/ros/noetic/include/hpp/fcl/collision_object.h:223:3: note: candidate: ‘hpp::fcl::CollisionObject::CollisionObject(const std::shared_ptr<hpp::fcl::CollisionGeometry>&, const hpp::fcl::Transform3f&, bool)’
  223 |   CollisionObject(const shared_ptr<CollisionGeometry>& cgeom_,
      |   ^~~~~~~~~~~~~~~
/opt/ros/noetic/include/hpp/fcl/collision_object.h:223:3: note:   candidate expects 3 arguments, 1 provided
/opt/ros/noetic/include/hpp/fcl/collision_object.h:217:3: note: candidate: ‘hpp::fcl::CollisionObject::CollisionObject(const std::shared_ptr<hpp::fcl::CollisionGeometry>&, bool)’
  217 |   CollisionObject(const shared_ptr<CollisionGeometry>& cgeom_,
      |   ^~~~~~~~~~~~~~~
/opt/ros/noetic/include/hpp/fcl/collision_object.h:217:56: note:   no known conversion for argument 1 from ‘const CollisionGeometryPtr’ {aka ‘const boost::shared_ptr<hpp::fcl::CollisionGeometry>’} to ‘const std::shared_ptr<hpp::fcl::CollisionGeometry>&’
  217 |   CollisionObject(const shared_ptr<CollisionGeometry>& cgeom_,
      |                   ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^~~~~~

The last line saying:
no conversion from ‘const boost::shared_ptr<hpp::fcl::CollisionGeometry>’} to ‘const std::shared_ptr<hpp::fcl::CollisionGeometry>&’
Maybe @nim65s you have an idea how we could solve this problem here ?

In pinocchio3, we have to make a choice:

use hpp-fcl shared pointers
do not use CollisionObject from hpp-fcl and reimplement them in pinocchio. In pinocchio 2, this was done for the ComputeCollision and ComputeDistance objects.

I am strongly in favor of 2 as it facilitates using hpp-fcl API with objects stored in a Pinocchio geometry model.


What is the purpose of a purpose?

In many of the examples in the document, there is a field purpose which contains a text we need it.
While I can see why it is (currently) there, it sets a bad example, specifically in a text that might become a standard some day, as it condones the behaviour of not taking the time to think for proper content because it doesn't affect the behaviour of the IT.
If the 'purpose' field serves a purpose, please put something in there that adequately demonstrates such purpose. Otherwise, remove it (or leave it blank).

Here is an example of a purpose that impacts a presentation.
The source data is a patient health record.
The purpose is to prescribe medicine.
The result is that the presentation record must include, (e.g.) allergies.
Another would be location.
The purpose of driving direction would mean that location needed to be fine grained.
The purpose of calculating sales tax would mean that the local city or state must be defined.
The purpose is sensitive information would mean what country where the device is operating must be defined.

Here is an example of a purpose that impacts a presentation.
The source data is a patient health record.
The purpose is to prescribe medicine.
The result is that the presentation record must include, (e.g.) allergies.
Another would be location.
The purpose of driving direction would mean that location needed to be fine grained.
The purpose of calculating sales tax would mean that the local city or state must be defined.
The purpose is sensitive information would mean what country where the device is operating must be defined.

Addressed thoroughly and vigorously in #187


chore(deps): update secops orb to v2.0.2

This PR contains the following updates:

Package
Type
Update
Change

secops
orb
patch
2.0.1 -> 2.0.2

Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - "after 8am and before 4pm on tuesday" in timezone Etc/UTC.
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.

[ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

Renovate Ignore Notification
Because you closed this PR without merging, Renovate will ignore this update (2.0.2). You will get a PR once a newer version is released. To ignore this dependency forever, add it to the ignoreDeps array of your Renovate config.
If you accidentally closed this PR, or if you changed your mind: rename this PR to get a fresh replacement PR.


Rails 5.x compatibility

I am getting a bundle conflict due to delayed-web's rails (< 4.3.0, >= 3.2.13) requirement on Rails 5.0.0.rc1

I don't have any current Rails 5 projects that are using Delayed::Job. Would you mind forking this repo, updating the gem requirement, and seeing if it works? I'll gladly accept a PR 😉

Works as expected.

Fixed by #14.

I've deployed a new version of the gem to rubygems.org.
https://rubygems.org/gems/delayed-web/versions/0.4.0

Awesome, that was fast!

Now the same problem with Rails <IP_ADDRESS>
Would it be ok if the dependency for Rails would be specified just as '>= 3.2.13' to avoid similar issues in the future? I could create a PR.


fix Dockerfile for hugo-support image

This should solve:

https://github.com/fluxcd/website/actions/runs/6063171310

I am testing it out locally to be sure nothing else did change

Looks as if somewhere in the distro or upstream rootfs from hugo is creating the symlink from /usr/bin/python to python3 now, so there's no need to do it in the support image anymore. We could also update our ln -s to ln -sf (in case they later decide to put it back and undo what they did, but I doubt that will happen.)

Once this is merged, the push-hugo-support job will run itself again automatically because it updates the Dockerfile 👍


Electron does not spawn from terminal

Version
5.1.1
Browser and OS info
Chrome 76
Ubuntu 18.04
Steps to reproduce
Install Vue Devtools with npm i -g @vue/devtools and run vue-devtools command. Nothing should happen
What is expected?
It should open an electron app with the Vue devtools
What is actually happening?
Nothing at all

same issue im on Arch Linux... with i3wm

@saveroo Mine started working recently, might have been an update :)

Confirmed still not working as of now. On Debian with xmonad, if that makes a difference.

This is essentially https://github.com/electron/electron/issues/17972 workarounds are:
sudo sysctl kernel.unprivileged_users_clone=1

or find the installed node_modules/electron/dist/chrome-sandbox and
sudo chown root chrome-sandbox
chmod 4755 chrome-sandbox


fix(API): Remove irrelevant resamp_rate property

This is only relevant to SignalsWaveform and will be re-added by #161.
Fixes #121.
BREAKING CHANGE: session.signals no longer has a resamp_rate property.
This never worked anyways so it shouldn't impact anyone.

[x] This contribution adheres to CONTRIBUTING.md.
[x] New tests have been created for any new features or regression tests for bugfixes.
[x] tox successfully runs, including unit tests and style checks (see CONTRIBUTING.md).

Coverage increased (+0.009%) to 64.185% when pulling a7b8f654fcad45c99ddc7bab597746d86d83151a on epage:resamp into 5590c92682e9a33adc823396a3565fa4dbb47055 on ni:master.

Coverage increased (+0.009%) to 64.185% when pulling a7b8f654fcad45c99ddc7bab597746d86d83151a on epage:resamp into 5590c92682e9a33adc823396a3565fa4dbb47055 on ni:master.

Coverage increased (+0.009%) to 64.185% when pulling a7b8f654fcad45c99ddc7bab597746d86d83151a on epage:resamp into 5590c92682e9a33adc823396a3565fa4dbb47055 on ni:master.

Coverage increased (+0.009%) to 64.185% when pulling a7b8f654fcad45c99ddc7bab597746d86d83151a on epage:resamp into 5590c92682e9a33adc823396a3565fa4dbb47055 on ni:master.

Coverage increased (+0.003%) to 64.179% when pulling b5b0197864e9efec0e25aea2a6746feb7c0a9713 on epage:resamp into 5590c92682e9a33adc823396a3565fa4dbb47055 on ni:master.


Undefined Property error in ObjectHydrator when using JOIN WITH

I have a pretty strange issue that I can't quite work out, I have a fix but it's affecting code from 8yrs ago which seems pretty stable.
I have a DQL query resembling
    SELECT base, fruits, apples, data
    FROM AppBundle\Base base
    LEFT JOIN base.fruits fruits
    LEFT JOIN AppBundle\Apple apples WITH fruits.id = apples.id
    LEFT JOIN apples.data data

where a Base can have many Fruits of multiple types. The error I get when trying to run this query is just
Undefined property on AppBundle\Base::$data
For some reason, the ObjectHydrator is trying to add the values retrieved from the database to the wrong entity. After doing some debugging, I found something a little odd in ObjectHydrator.php
    // Get a reference to the parent object to which the joined element belongs.
    if ($this->_rsm->isMixed && isset($this->rootAliases[$parentAlias])) {
        $first = reset($this->resultPointers);
        $parentObject = $first[key($first)];

It appears that it can only ever get a reference to the first object that there is a root alias to. After changing the second line to $first = $this->resultPointers[$parentAlias]; in a debug build, my problem is solved and although I didn't run through the unit tests (will do if it's a PR, but it seems more like I'm doing something wrong here) my application elsewhere works fine.
I realise there is a limitation when it comes to downcasting in Doctrine (which is what I am trying to do) but it seems like this issue would have broader implications.

This is a known limitation of the ORM when working with class table inheritance and might not be properly documented.
@SirWaddles would be nice if you could reproduce and implement a good solution for this on a PR.

Fixed by #6367


add pass proc

Since pass proc is in the ast for the optimizer and it's printed by zfmt, it should also be in Z.  So, add a "pass" proc to zql/zql.peg

Already done...
% zc pass
{
    "kind": "Sequential",
    "procs": [
        {
            "kind": "Pass"
        }
    ]
}


⚠ Samsung has degraded performance

In fab0e4d, Samsung (https://samsung.com) experienced degraded performance:

HTTP code: 200
Response time: 2698 ms

Resolved: Samsung performance has improved in 46fccc7.


feat: load command's actions async to improve performance

🎉 Thanks for submitting a pull request! 🎉
Summary
Thanks to @rjbeers investigation, we've found that loading in individual commands' action functions asynchronously leads to faster load time, as we aren't loading in every single package on each command run. I've done this for each command we have in the CLI.
I've also added Typescript types for commands and their actions in this PR.

Before
After

netlify -v - around 2 seconds
netlify -v - just over 0.5 seconds

netlify status - around 4 seconds
netlify status - around 2.75 seconds

For us to review and ship your PR efficiently, please perform the following steps:

[ ] Open a bug/issue before writing your code 🧑💻. This ensures we can discuss the changes and get feedback from everyone that should be involved.
[ ] Read the contribution guidelines 📖. This ensures your code follows our style guide and
passes our tests.
[ ] Update or add tests (if any source code was changed or added) 🧪
[ ] Update or add documentation (if features were changed or added) 📝
[ ] Make sure the status checks below are successful ✅

A picture of a cute animal (not mandatory, but encouraged)

@sarahetter Is it possible that this change could cause some issues with lambda execution timeouts? Tests in https://github.com/netlify/netlify-plugin-gatsby started failing because of errors like:
Function __api has returned an error: Task timed out after 10.00 seconds
    at new TimeoutError (/opt/hostedtoolcache/node/20.9.0/x64/lib/node_modules/netlify-cli/node_modules/lambda-local/build/lib/utils.js:119:28)
    at Context.<anonymous> (/opt/hostedtoolcache/node/20.9.0/x64/lib/node_modules/netlify-cli/node_modules/lambda-local/build/lib/context.js:110:19)
    at listOnTimeout (node:internal/timers:573:17)
    at processTimers (node:internal/timers:514:7)

Downgrading CLI to 17.6.0 "fixes" those timeouts.
Using 17.7.0 test run example - https://github.com/netlify/netlify-plugin-gatsby/actions/runs/6983007552/job/19003322129?pr=722 (above snippet copied from it) - it seems to happen every time now with that version of CLI
Using 17.6.0 test run example is fine https://github.com/netlify/netlify-plugin-gatsby/actions/runs/6982743678/job/19002516599?pr=721
I don't quite know if it's possible this would be the case as this is pretty hefty change in this PR - but would async loading part possibly be part of lambda execution time now, meaning that part of 10s lambda execution timeout would be taken by async loading?

@pieh I just took a look through the netlify-plugin-gatsby tests and it looks like they're using netlify dev - which didn't actually get the async treatment in this PR because I had failing tests, so it was kept as is. So for now, I'm just not sure.
@eduardoboucas I think I'll need your help trying to debug this. I'm not familiar with the dev/functions handling code within the CLI, and can't guess as to what's causing these timeouts


Improve applyArgs error message

It would be useful for users to know the arguments that make applyArgs to fail.
Originally posted by @Luis-omega in https://github.com/Plutonomicon/cardano-transaction-lib/pull/1260#discussion_r1042942466

i wanted to add some description here:
Applying arguments doesn't evaluate the script! It wraps the script in few Apply constructors and thats it (haskell implementation the same and damn was I surprised). Also scripts are untyped. So there's no notion of script evaluation failing when applied to parameters.
So what are the possible errors of "applyArgs"?
Various serialization errors. Both script and param data makes a roundtrip:
Purescript values --csl-serialization--> bytestrings in javascript --pallas-deserialization--> rust values --pallas-serialization--> js/purescript script
For params we start with PlutusData so any error in the roundtrip concerning params would be a ctl bug. With scripts we don't have an ADT representation, scripts are newtypes on bytestrings for us. So user may import an invalid script from a text envelope and then applying params would fail at some step (in "pallas-deserialization" i think).

What do you think about doing a sanity check serialization roundtrip before wraping script bytestrings in PlutusScript constructor? Then we would have the assertion on PlutusScript values being valid scripts. We could then make the type of "applyArgs" be PlutusScript -> [PlutusData] -> PlutusScript as every error would be an actual bug?

Applying arguments doesn't evaluate the script! It wraps the script in few Apply constructors and thats it

@zmrocze does the above mean we don't actually need to have any understanding of UPLC to perform parameter application? Maybe we could just apply script arguments on a binary level - like, we know the byte representation of Apply, right? And the rest is probably just byte array concatenation, isn't it?
If so, would it be feasible to drop the wasm dependency altogether and simply go with some ByteArray manipulations?

@zmrocze

What do you think about doing a sanity check serialization roundtrip before wraping script bytestrings in PlutusScript constructor?

I always considered the fact that CTL is UPLC-blind a good thing, but having one more sanity check is even more good thing if the code is here anyway.
However, I am concerned with Plutus versions compatibility. To what extend does the uplc package validate the script? What happens if there is a new version of plutus with a new supported opcode and the uplc crate hasn't been updated? How can we test that the set of scripts acceptable by the node version we use is the same as the one we can expect uplc to parse?

@klntsky

yes, it looks like we can do this on bytearrays directly.

uplc would fail deserialisation if its not updated to a new plutus version. This could maybe be tested based on node queried plutus cost model, which lists more or less the builtins. This wouldn't be a full test tho, adding completely new term constructors in PlutusV17 or changing the serialization would pass.


Java8 support

Does this work for a java8 project?

@fpedroza Sincere apologies for the delay on responding. This does not. The minimum supported version is Java 11 for v1.x and Java 17 for v2.x.


Refactor rename user and rename organization

This PR is a refactor at the beginning. And now it did 4 things.

[x] Move renaming organizaiton and user logics into services layer and merged as one function
[x] Support rename a user capitalization only. For example, rename the user from Lunny to lunny. We just need to change one table user and others should not be touched.
[x] Before this PR, some renaming were missed like agit
[x] Fix bug the API reutrned from http.StatusNoContent to http.StatusOK

I guess we even do not need ErrUsernameNotChanged, IMO renaming a name to itself could be treated as no error too , just like "ChangeCase" -> "changecase", literally, "no error" is also right.

I think this has been checked out of this function. The function should be invoked only when outside know the name changed.

I do not think it should be "backport/1.19"

Please be aware that this considerably limits the functionality of the user rename API endpoint. This API endpoint was made in order to rename non-local users when their username in the external authentication system changes. As in, the sole reason this endpoint came to be was to support the use case that is now blocked.
How did the review process not catch this?
Note that the original PR that introduced this API endpoint was #22789, which is IMO considerably under-documented, and merged while still mentioning "is not in a mergeable state."

The problem is that #22789 doesn't contain its tests, so ..... it's not a surprise that the code without tests could break again and again ....
TBH, it's really difficult to catch bugs for under-documented or not-well-known behaviors.

Please be aware that this considerably limits the functionality of the user rename API endpoint. This API endpoint was made in order to rename non-local users when their username in the external authentication system changes. As in, the sole reason this endpoint came to be was to support the use case that is now blocked.
How did the review process not catch this?
Note that the original PR that introduced this API endpoint was #22789, which is IMO considerably under-documented, and merged while still mentioning "is not in a mergeable state."

The non-Local users were blocked because the admin web logic is that. To keep consistent with that logic and reuse the same functions between API and Web, the logic has been added.

This happened twice: both #22789 and this one.

Well, IMO only "#22789" seems incomplete. But for this PR, I have fully reviewed it and I think this PR is complete. I didn't know that undocumented behavior .....

I didn't know that undocumented behavior .....

That's my point, the code changes "any user can be renamed" to "only local users can be renamed", and this should be described as a functional change in the PR description. For my own projects, I'd even require that to be a separate PR, as there refactoring (i.e. moving code to other files, merging functions) and functional changes aren't mixed into a single PR. It makes it too easy to miss functional changes, like shown here as well.

Then IMO the underlying problem is still related the lacking of tests. For a large project like Gitea, I do not think there is a person who can 100% understand how it works internally, and even the PR's developer themself might not be able to realize that something is changed. Anyway, I have done my best to review PRs, I can't promise that the PRs reviewed by me is 100% bug-free.

I can't promise that the PRs reviewed by me is 100% bug-free.
Oh for sure, same here. That's why I put much effort into getting a clear picture of all the relevant changes in the PR description, even before I start looking at the code (as a reviewer, that is). If I don't understand the changes going into the code review, there is no way that I can see whether the code is doing the right thing or not.

I "rubber stamp" reviewed this, meaning I did not completely understand or review it, but it looked reasonable overall.
Because we seriously lack reviewers, we sometimes have to do this to get movement on PRs that otherwise tend to go stale otherwise. This involves a certain level of trust with the author of course, and I don't do that for every random author.

I didn't know that undocumented behavior .....

That's my point, the code changes "any user can be renamed" to "only local users can be renamed", and this should be described as a functional change in the PR description. For my own projects, I'd even require that to be a separate PR, as there refactoring (i.e. moving code to other files, merging functions) and functional changes aren't mixed into a single PR. It makes it too easy to miss functional changes, like shown here as well.

Sorry, I should mention in that PR about the change from all users -> non-local users. I couldn't find a quick fix to allow renaming non-local users because it may causes duplicated users described in https://github.com/gogs/gogs/issues/2154.
I'm reviewing the whole user logic and created issue #25153


Default Visualisation Improvements

I have made some modifications to the default visualisation in a separate project which I can incorporate into the main FLAME GPU template without much issue:

[x] Pause

Add the ability to pause the simulation (via a keypress)
and then run a single update at a time, whilst being able to move the camera etc.

Y axis for the camera UP vector

Via a #define in the visualisation.h allow users to use Y as the up axis rather than Z.

[x] add glutReshapeFunc callback so the window can be resized nicely

Skipping the Y axis for UP conversion for now, as model is a sphere so difficult to check correctness.


Is there any easier way to contruct the page layout

Hi
Is there any easier way to contruct the page layout? Stuck in the webparts i want?
thanks
Peter

Hi, can you clarify a bit on what you are after?

Hi @bcameron1231  , i want to know how people construct the xml that use to generate the pnp file for a site page.

@quantrpeter the easiest way is to create a site page in the browser, add webparts, sections, layouts, settings, etc, and then use Get-PnPProvisioningTemplate https://docs.microsoft.com/en-us/powershell/module/sharepoint-pnp/get-pnpprovisioningtemplate?view=sharepoint-ps. By default this will grab everything in a site collection, though with the xml output, you could then trim this to meet you specific needs, and you will have the XML for your particular site page as well.

Dear Mr @eoverfield , thanks for your answer.


Where is version 0.9.1?

In this repository the version in package.json is currently 0.9.0. The most recently published version is 0.9.1.
What has changed between the versions? Why isn't the most recent version in this repository?

Ugh, apologies. I must have forgotten to tag it. My guess is that 0.9.1 matches the current master branch code.
There will be a new release in the next couple of weeks. It will be tagged and have a list of changes.

awesome :)

There were a couple of commits on my machine that were part of the publish. I pushed them and tagged. I am getting v0.9.2 organized now.


con/tinuous archival of the CI logs

We (@jwodder primarily) developed the https://github.com/con/tinuous/ to establish archives of logs from various CIs. Unfortunately circle CI is not yet supported since we did not have a use-case yet so it was not implemented (https://github.com/con/tinuous/issues/124). But even without circle-ci I think it would be good to have such an archive.
Typically I just keep those logs on a server which is accessible to all project members. But BIDS project does not have such a private ssh-able server, so I might better just publish them to github.

Are you aware of any sensitive information in those logs so we might better not share them publicly?
Since there will be "subdatasets" (I usually do one per month), we better not publish as part of this org to not pollute repos, but create a dedicated bids-standard-ci-logs or alike. But then it would be another burden to manage access.  So may be they should all go under this org?  or what other location if any public or not?

Are you aware of any sensitive information in those logs so we might better not share them publicly?

to my knowledge the CircleCI logs are openly accessible anyhow ... and I just tried accessing the GitHub action logs through a non-logged in browser and I think there the steps are not accessible.
More importantly: I don't think there is any sensitive information in these logs, so we may archive them without problems.

Since there will be "subdatasets" (I usually do one per month)

you mean a new repo each month?
Couldn't we just have a single repo and keep pushing the logs there? Or will we run into storage space issues?

transferring to maintenance-tools repo


💡 [REQUEST] -

I am from GSSoC23.
[I would like to be assigned this task.

| Section                            | Description |
|   Concise Description    Add a favicon to the website for a visually appealing and recognizable icon in the browser tab.
| Solution Proposed      Create or choose a suitable favicon image and add it to the website's  code.
Code of Conduct
By submitting this issue, I agree to follow our Code of Conduct.

I follow the Contributing Guidelines of this project.
-I have checked the current issues for duplicate problems.
I have read the readme of this repository.

its already there.


[TRACKER] Navigation test plan

In the upcoming weeks, I'm going to work on test cases for the navigation area. I'm going to use this issue as a progress tracker but also as a place where anyone can propose scenarios to implement.
Please note that many scenarios will be tested in 3D only since quite a lot of navigation code is common for 2D and 3D so we don't need to duplicate test cases in many instances.
Server tests
NavigationServer3D
General

[x] Server should be empty when initialized - checking if the internal state of server is correct after initialization
[x] Server should release valid RIDs

Agent

[x] Server should create a valid agent
[x] Server should not report dangling agent in ProcessInfo
[x] Server should not report removed agent in ProcessInfo
[x] Server should report agent with active map in ProcessInfo
[x] Server should be able to set/get basic agent params
[ ] Server should be able to set/get all agent's params
[ ] (...)

Map

[x] Server should create a valid map
[x] Server should yield default values in response to queries against empty map
[x] Server should report active map in ProcessInfo
[x] Server should not report active map in ProcessInfo
[x] Server should be able to set/get all map's params
[x] Server should report correct number of map's agents
[x] Server should report correct number of map's obstacles
[x] Server should report correct number of map's links
[x] Server should report correct number of map's regions
[ ] Server should emit map_changed
[ ] Server should emit navigation_debug_changed
[ ] (...)

Link

[x] Server should create valid link
[x] Server should not report dangling link in ProcessInfo
[x] Server should report link with active map in ProcessInfo
[x] Server should be able to set/get all link's params
[ ] (...)

Region

[x] Server should create valid region
[x] Server should not report dangling region in ProcessInfo
[x] Server should report region with active map in ProcessInfo
[x] Server should yield default values in response to queries against empty region
[ ] (...)

Obstacle

[x] Server should create valid obstacle
[ ] Server should be able to set/get all obstacle's params
[ ] (...)

NavigationServer2D

[x] Server should be empty when initialized - checking if the internal state of server is correct after initialization
[ ] (...)

Node tests
NavigationRegion3D

[x] New region should have valid RID
[ ] Navigation region should bake navigation mesh correctly
[ ] Navigation region should emit bake_finished
[ ] Navigation region should emit navigation_mesh_changed
[ ] (...)

NavigationRegion2D

[x] New region should have valid RID
[ ] (...)

NavigationAgent3D

[x] New agent should have valid RID
[x] New agent should attach to default map
[ ] (...)

NavigationAgent2D

[x] New agent should have valid RID
[x] New agent should attach to default map
[ ] (...)

NavigationObstacle3D

[x] New obstacle should have valid RID
[x] New obstacle should attach to default map
[ ] Obstacle estimates radius correctly
[ ] Obstacle uses hardcoded radius if not estimated
[ ] Obstacle changes navigation map correctly
[ ] Obstacle is avoided by agent correctly
[ ] (...)

NavigationObstacle2D

[x] New obstacle should have valid RID
[x] New obstacle should attach to default map
[ ] Obstacle changes navigation map correctly
[ ] Obstacle is avoided by agent correctly
[ ] (...)

NavigationLink3D

[ ] (...)

NavigationLink2D

[ ] (...)

PRs

https://github.com/godotengine/godot/pull/73121
https://github.com/godotengine/godot/pull/73700
https://github.com/godotengine/godot/pull/78449
https://github.com/godotengine/godot/pull/78480
https://github.com/godotengine/godot/pull/78667

This issue supplements https://github.com/godotengine/godot/issues/43440

Looking for navigation related benchmark ideas.
Benchmark ideas are written in format like this:
TYPE: [Groups it Belongs]: Name: Description
Examples:

Exclusive:AStar3D: Create random map with 1000 inter connected points (probably using Delaunay3D), Benchmark solving it 1000 times from random 2 points
Exclusive:Navigation:  On a premade map, solve 1000 random paths between two points on the surface of the shapes.
Agents: Benchmark 1000 moving agents in a map with local collision avoidance.

Looking for navigation related benchmark ideas.
Benchmark ideas are written in format like this: TYPE: [Groups it Belongs]: Name: Description
Examples:

Exclusive:AStar3D: Create random map with 1000 inter connected points (probably using Delaunay3D), Benchmark solving it 1000 times from random 2 points
Exclusive:Navigation:  On a premade map, solve 1000 random paths between two points on the surface of the shapes.
Agents: Benchmark 1000 moving agents in a map with local collision avoidance.

Some more examples to consider:

Exclusive:Navigation[Agents]: Benchmark 10 maps with 100 moving agents each and with local collision avoidance.
Exclusive:Navigation[Agents]: Benchmark 100 maps with 10 moving agents each and with local collision avoidance.
Exclusive:Navigation[Agents]: Benchmark 1000 moving agents in a map with local collision avoidance and with 100 triangular, static obstacles spread across the map.
Exclusive:Navigation[Agents/Queries]: Benchmark 1000 moving agents in a map with local collision avoidance while changing desired location (path recalculation) for 100 of them every second for 10 seconds.


Release google-cloud-java v0.95.0

This pull request was generated using releasetool.
06-06-2019 10:21 PDT
Bigtable

Bigtable: Changed title on readme to match external-facing client library name . (#5411)
Bigtable: Using undeprecated Truth methods. (#5237)

BigQuery

BigQuery:Fix deprecated warnings removed (#5240)

BigQuery Storage

Add integration tests for snapshot read and resuming. (#5242)

Compute

Regenerate compute client (#5416)

Container Analysis

Add Container Analysis v1 service (#5364)

DLP

Regenerate dlp client (#5432)

Firestore

Firestore: deprecated warnings removed (#5247)
Refactor firestore conformance tests to be more idiomatic (#5228)

Logging

Logging: Fix deprecation warnings (#5405)

Pub/Sub

Regenerate pubsub client (#5417)
Pub/Sub: Fixing Subscriber's system executor config (#5234)

Redis

Regenerate redis client (#5418)

Scheduler

Cloud Scheduler GA (#5363)

Security Center

Regenerate securitycenter client (#5230)

Spanner

Spanner: Properly end span for ResumableStreamIterator. (#5309)
Spanner: Partitioned DML tx does not need a prepared session (#5188)

Speech

Regenerate speech client (#5419)

Web Security Scanner

Web Security Scanner Beta Client (#5362)

Video Intelligence

Regenerate video-intelligence client (#5401)

Implementation Changes

gax 1.45 uses totalTimeout also when retries have been disabled (#5283)

Dependencies

Update dependency org.easymock:easymock to v3.6 (#5414)
Update dependency org.eluder.coveralls:coveralls-maven-plugin to v4.3.0 (#5415)
Update dependency org.jacoco:jacoco-maven-plugin to v0.8.4 (#5421)
Update dependency org.codehaus.mojo:build-helper-maven-plugin to v3 (#5429)
Update dependency org.codehaus.mojo:appassembler-maven-plugin to v2 (#5428)
Update dependency org.codehaus.mojo:animal-sniffer-annotations to v1.18 (#5314)
Update dependency org.codehaus.plexus:plexus-utils to v3.2.0 (#5361)
Update dependency org.codehaus.mojo:exec-maven-plugin to v1.6.0 (#5360)
Update dependency javax.servlet:javax.servlet-api to v4 (#5426)
Update dependency org.sonatype.plugins:nexus-staging-maven-plugin to v1.6.8 (#5424)
Update dependency org.codehaus.mojo:build-helper-maven-plugin to v1.12 (#5315)
Update dependency org.apache.maven.plugins:maven-javadoc-plugin to v3.1.0 (#5298)
Update dependency org.apache.maven.plugins:maven-project-info-reports-plugin to v2.9 (#5302)
Update dependency org.apache.maven.plugins:maven-plugin-plugin to v3.6.0 (#5299)
Update dependency org.apache.maven.plugins:maven-deploy-plugin to v2.8.2 (#5296)
Update dependency org.apache.maven.plugins:maven-enforcer-plugin to v3.0.0-M2 (#5297)
Update dependency org.apache.maven.plugins:maven-compiler-plugin to v3.8.1 (#5295)
Configure renovate to group grpc, protobuf, opencensus updates together (#5307)
Update dependency org.apache.commons:commons-compress to v1.18 (#5292)
Update dependency org.apache.maven.plugin-tools:maven-plugin-annotations to v3.6.0 (#5293)
Update dependency org.apache.maven.plugins:maven-site-plugin to v3.7.1 (#5310)
Update dependency com.theoryinpractise:googleformatter-maven-plugin to v1.7.3 (#5274)
Import google-oauth-client-bom and google-api-client-bom. (#5306)
Update dependency kr.motd.maven:os-maven-plugin to v1.6.2 (#5291)
Update dependency io.netty:netty-handler to v4.1.36.Final (#5279)
Update dependency io.grpc:grpc-netty-shaded to v1.21.0 (#5278)
Update dependency io.grpc:grpc-core to v1.21.0 (#5277)
Update dependency commons-fileupload:commons-fileupload to v1.4 (#5275)
Update dependency com.google.oauth-client:google-oauth-client to v1.29.0 (#5269)
Update dependency com.google.code.gson:gson to v2.8.5 (#5263)
Update dependency com.google.api:gax-bom to v1.45.0 (#5255)
Updating GAX in clients to 1.45.0 for docs. (#5409)
Update dependency com.google.truth:truth to v0.45 (#5272)
Update dependency com.google.errorprone:error_prone_annotations to v2.3.3 (#5264)
Update dependency com.google.cloud.tools:appengine-maven-plugin to v1.3.2 (#5262)
Update dependency com.puppycrawl.tools:checkstyle to v8.21 (#5273)
Update dependency com.google.api.grpc:grpc-google-common-protos to v1.16.0 (#5253)
Update dependency com.google.apis:google-api-services-cloudresourcemanager to v1-rev20190513-1.28.0 (#5256)
Update dependency com.google.api.grpc:proto-google-common-protos to v1.16.0 (#5254)
Pin python utility dependencies (#5249)
Update dependency com.google.http-client:google-http-client-bom to v1.29.2 (#5289)
Update dependency com.coveo:fmt-maven-plugin to v2.9 (#5250)
Add renovate.json (#5244)
Upgrading grpc and opencensus (#5248)

Internal / Testing Changes

deprecated warnings removed (#5406)
deprecated warnings removed (#5304)
Moving google-cloud-notification to -contrib (#5303)
Clean up test deprecation warnings for google-cloud-core (#5259)
deprecated warnings removed (#5241)
Bump next snapshot (#5239)

Release is at https://github.com/googleapis/google-cloud-java/releases/tag/v0.95.0


updates agenda workflow so it closes older agenda issues automatically

related #3420

How long will it leave the issues open for? I would suggest something over 2 weeks, so we can always look at the previous meeting notes, even if we skip a meeting one week.

@lornajane right now it closes the issue as soon as the date in the title is passed, but runs only every week, so that should give us a week effectively.
We could introduce a delay if the TDC decides it.

Notes from the meeting:

wait 10 days before close the issue.
look into unpinning the issue as we close them.

@lornajane @darrelmiller @MikeRalphson @webron :

added the delay of 10 days before closing the agenda item
added pinning/unpinning the issues

I think this is ready to merge.


[3.x] SpriteFrames: Sort animations alphabetically

Fixes #62143.

Previously they would be serialized in the order they come with in Map. So when adding a new animation, it would be added at the end of the Map in the current process, and thus saved at the last element in the array in the .tscn. But when loading the scene in a new process, the Map could be reordered as it doesn't depend on the serialized array.
This is only used for (de)serialization from scene/res files so I think the performance impact of having to sort the StringNames is minimal.
The unwanted reordering doesn't seem to happen in master but I'll make a PR anyway to force alphabetical ordering, and remove the obsolete frames property.
3.x version of #62978.

Yeah I thought about that too but I noticed that e.g. in AnimationPlayer it's also using a lot of Map<StringName, SomeCustomStruct>.
Might be worth discussing on chat and see if some general rules can be figured out to establish when it's worth it to used OrderedHashMap directly, or when it's preferred to keep it unordered and just sort where needed. In master we could maybe get some kind of way to get an iterator that goes through StringName keys ordered to simplify such code.


On Received Bytes event unable to fire on multiple pawns if Receive Port is the same

I have multiple pawns, each inheriting an UPDComponent from the same parent. If Receive Port is different between the children, the Received Bytes event fires correctly for each of the children; if Receive Port is the same the event fires only on one instead (I suspect the first one that gets instanced).
Is there a way to have multiple children receive packets on the same port?

I believe that's the way UDP works. A workaround would be to add a reference to a single udp component and you should be able to bind multiple targets to the events.
e.g.

Add UDP component to an actor of choice
get a reference to that actor in another actor, ask for its UDP component
bind to its OnReceivedBytes

That said there probably is a way to set the internal architecture such that if components have the same port, then use the same internal receiver and the multicast the bytes receives (also forward emit to the same outbound). That would be a plugin enhancement. Currently not a priority for me so I welcome dev code contributions on the issue.

After further investigation it does seem an inherent protocol limitation.
I'll switch to a master receiving actor like you suggested for now.


cleanup makefile

This PR performs a cleanup of the classic and image driver makefiles. Most notably, we now are using a wildcard selection for *c files in the source directories, greatly reducing the length of the makefiles.

Looking good : @jhamman -- let me know if this is complete and I'll go ahead and merge

Yes, this is good.  Go ahead and merge.


Fix issue related to promotion timer

See issue #574, and comment https://github.com/Automattic/kue/issues/574#issuecomment-93496632 for full explanation.

@jesucarr would you test if promotion timer issues fixed in latest commit?

No, the process is still stuck after "queue closed" is done

Would you please post the code snippet of your shutdown so that I can run & debug it.

you are using 0.9.0 (master) and search indexes are at their default (off), right?

kue = require('../lib/kue');

queue = kue.createQueue({
  disableSearch: true
});

job = queue.create('test job', {
  num: 1
}).attempts(2).delay(1000 * 10).backoff({
  type: 'exponential'
}).save(function(err) {
  if (err) {
    return console.log(err);
  }
  console.log('job added', job.id);
  return queue.shutdown(function(err) {
    return console.log('queue closed');
  });
});

this is because of the extra lock client which warlock uses, and kue cannot end it at shutdown, I saw a bug when you change warlock modules redis client object: https://github.com/TheDeveloper/warlock/issues/11
I should re-implement a distributed lock inspired by warlock, since no response to that issue is seen...
And some points about your code:

in kue 0.9.0 search is off by default, no need to set disableSearch any more
if you are not creating workers (calling .process) there's no need to call shutdown

So this is not related to promotion timer and will be renamed if you don't mind :)

fixed by forking warlock

https://github.com/Automattic/kue/commit/73a8bb7f06c8abb5cf75695c1f23f1676c833893


patch optional unwrapping for swift

Had issues building with swift version 5.7.1. Build is successful after updating the syntax for handling optionals.

Sorry I saw it too late.
Thanks for your contribution.


webpack-dashboard support

Bug Report or Feature Request (mark with an x)
- [ ] bug report -> please search issues before submitting
- [x] feature request

Add webpack-dashboard to ng serve like this:
ng serve --dashboard
 ng serve --host <IP_ADDRESS> --port 4201 --dashboard
Default no use dashboard.

This isn't something we're looking at adding. It would be a nice community addon in the upcoming addon system though.


Update manifests/c/clsid2/mpc-hc/1.9.6/clsid2.mpc-hc.locale.en-US.yaml

Fixes an issue where this package has multiple different monikers
Microsoft Reviewers: Open in CodeFlow

[Policy] Reset Labels


Release CONSUL_SERVER_ADDRESS to support non-local consul agents fix

I see that the issue with non-local consul agents has been resolved, could you please make a release containing this fix?

+1
Without this change I cannot use your great plugin in docker, which is current standard. Release for branch 3.5 of RabittMQ will be good enough.

0.5.0 will be released within a week.


some cuda error when inference

CUDA_VISIBLE_DEVICES=0 python llama_inference.py ../0321_shards/ --wbits 8 --groupsize 128 --load llama7b-8bit-128g.pt --text "this is llama"
Loading model ...
Done.
The tokenizer class you load from this checkpoint is not the same type as the class this function is called from. It may result in unexpected tokenization.
The tokenizer class you load from this checkpoint is 'LlaMATokenizer'.
The class this function is called from is 'LlamaTokenizer'.
/usr/bin/ld: skipping incompatible /usr/lib/libcuda.so when searching for -lcuda
/usr/bin/ld: skipping incompatible /usr/lib/libcuda.so when searching for -lcuda
/usr/bin/ld: skipping incompatible /usr/lib/libcuda.so when searching for -lcuda
/usr/bin/ld: skipping incompatible /usr/lib/libcuda.so when searching for -lcuda

Do not use huggingface checkpoints converted to older versions of Transformers.


Continue to next packet if received broken packet

Same as #1230 .
Sorry, I made a mistake and closed it.
#1166 has avoid panic but cause a silent fail.
This fixes it.
Broken packet should be ignored and continue to next packet.
This goroutine should not exit until close.

Thanks for the contribution!


Use utf-8 as filesystem encoding under UNIX (was: test_shared_data_middleware fails on python2)

this issue is a bit philosophical in nature :)
this is on openbsd (werkzeug 0.9.6, python 2.7.8)
first of all, on openbsd this test fails on both python2 and python3.
i am aware of #428 and maybe if that is fixed, it will also work on openbsd python3.
but i'd like to talk about python2.  here is the trace:
======================================================================
ERROR: test_shared_data_middleware (werkzeug.testsuite.wsgi.WSGIUtilsTestCase)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/usr/ports/pobj/py-werkzeug-0.9.6/Werkzeug-0.9.6/werkzeug/testsuite/wsgi.py", line 47, in test_shared_data_middleware
    app_iter, status, headers = run_wsgi_app(app, create_environ(p))
  File "/usr/ports/pobj/py-werkzeug-0.9.6/Werkzeug-0.9.6/werkzeug/test.py", line 855, in run_wsgi_app
    app_iter = app(environ, start_response)
  File "/usr/ports/pobj/py-werkzeug-0.9.6/Werkzeug-0.9.6/werkzeug/wsgi.py", line 567, in __call__
    cleaned_path = cleaned_path.encode(sys.getfilesystemencoding())
UnicodeEncodeError: 'ascii' codec can't encode characters in position 5-7: ordinal not in range(128)

----------------------------------------------------------------------

on linux this test passes fine.  the whole thing blows up here:
wsgi.py:564:
    def __call__(self, environ, start_response):
        cleaned_path = get_path_info(environ)
        if PY2:
            cleaned_path = cleaned_path.encode(sys.getfilesystemencoding())

sys.getfilesystemencoding on openbsd in python2 does not return 'utf-8',
and that is basically the end of this bug from werkzeug's side.
so now that we have this diagnosed, we can talk about the
test itself: and it seems a bit schizophrenic to me, because the
documentation for SharedDataMiddleware states:
    Currently the middleware does not support non ASCII filenames.  If the
    encoding on the file system happens to be the encoding of the URI it may
    work but this could also be by accident.  We strongly suggest using ASCII
    only file names for static files.

according to this, if it works, it works, good for ya, but the failure of this
test on my machine is expected and well documented :)  in other words,
this test should be allowed to fail, n'est-ce pas?

I think we may already fix this in 0.11. See #674.


Homebrew on Linux seems to ignore EDITOR environment setting

Please note that we will close your issue without comment if you delete, do not read or do not fill out the issue checklist below and provide ALL the requested information. If you repeatedly fail to use the issue template, we will block you from ever submitting issues to Homebrew again.

[x] are reporting a bug others will be able to reproduce and not asking a question. If you're not sure or want to ask a question do so on our Discourse: https://discourse.brew.sh
[x] ran a brew command and reproduced the problem with multiple formulae? If it's a problem with a single, official formula (not cask) please file this issue at Homebrew/homebrew-core: https://github.com/Homebrew/homebrew-core/issues/new/choose. If it's a brew cask problem please file this issue at https://github.com/Homebrew/homebrew-cask/issues/new/choose. If it's a tap (e.g. Homebrew/homebrew-php) problem please file this issue at the tap.
[x] ran brew update and can still reproduce the problem?
[x] ran brew doctor, fixed all issues and can still reproduce the problem?
[x] ran brew config and brew doctor and included their output with your issue?

What you were trying to do (and why)
I was trying to edit a formula(let's say hello in this example) for contribution.
What happened (include command output)
Even though I set $EDITOR to nano, brew still tries to use "edit" which will spawn an error due to no set mailcaps for it.

Command output

  aaron@zenbook:~/lintcode$ brew doctor
Please note that these warnings are just used to help the Homebrew maintainers
with debugging if you file an issue. If everything you use Homebrew for is
working fine: please don't worry or file an issue; just ignore this. Thanks!
Warning: umask is currently set to 000. Directories created by Homebrew cannot
be world-writable. This issue can be resolved by adding "umask 002" to
your ~/.bash_profile:
echo 'umask 002' >> ~/.bash_profile
aaron@zenbook:~/lintcode$ echo 'umask 002' >> ~/.bash_profile
aaron@zenbook:~/lintcode$ brew doctor
Please note that these warnings are just used to help the Homebrew maintainers
with debugging if you file an issue. If everything you use Homebrew for is
working fine: please don't worry or file an issue; just ignore this. Thanks!
Warning: umask is currently set to 000. Directories created by Homebrew cannot
be world-writable. This issue can be resolved by adding "umask 002" to
your ~/.bash_profile:
echo 'umask 002' >> ~/.bash_profile
aaron@zenbook:~/lintcode$ umask 002
aaron@zenbook:~/lintcode$ brew doctor
Your system is ready to brew.
aaron@zenbook:~/lintcode$ brew edit hello
Editing /home/linuxbrew/.linuxbrew/Homebrew/Library/Taps/homebrew/homebrewcore/Formula/hello.rb
Warning: Using edit because no editor was set in the environment.
This may change in the future, so we recommend setting EDITOR,
or HOMEBREW_EDITOR to your preferred text editor.
Error: no "edit" mailcap rules found for type "application/x-ruby"
Error: Failure while executing; `edit
/home/linuxbrew/.linuxbrew/Homebrew/Library/Taps/homebrew/homebrew-
core/Formula/hello.rb` exited with 3.
aaron@zenbook:~/lintcode$ brew config
HOMEBREW_VERSION: 2.1.15-63-g090259b
ORIGIN: https://github.com/Homebrew/brew
HEAD: 090259b97304cd303fb0e4b3cefdf7bf9a2596fd
Last commit: 2 days ago
Core tap ORIGIN: https://github.com/Homebrew/linuxbrew-core
Core tap HEAD: 3a8bdf1a86ee96aa94a665dfb30d41e87965d34b
Core tap last commit: 17 hours ago
HOMEBREW_PREFIX: /home/linuxbrew/.linuxbrew
HOMEBREW_CACHE: /home/aaron/.cache/Homebrew
HOMEBREW_LOGS: /home/aaron/.cache/Homebrew/Logs
HOMEBREW_DEV_CMD_RUN: 1
CPU: octa-core 64-bit skylake
Homebrew Ruby: 2.6.3 => /home/linuxbrew/.linuxbrew/Homebrew/Library/Homebrew/vendor/portable-ruby/2.6.3/bin/ruby
Clang: N/A
Git: 2.17.1 => /usr/bin/git
Curl: 7.58.0 => /usr/bin/curl
Kernel: Linux 4.4.0-18362-Microsoft x86_64 GNU/Linux
OS: Ubuntu 18.04.3 LTS (bionic)
Host glibc: 2.27
/usr/bin/gcc: 7.4.0
glibc: N/A
gcc: N/A
xorg: N/A
aaron@zenbook:~/lintcode$ echo $EDITOR
nano

What you expected to happen
I expected homebrew to edit in nano. git commit -v edits in nano now.
Step-by-step reproduction instructions (by running brew commands)
EDITOR=nano
brew edit hello
#Optional, Just to see that git does.
git init
echo "abc">>abc.txt
git add .
git commit -v

I'm using windows wsl ubuntu.

Try EDITOR=nano brew edit hello and tell what happened.

@dawidd6 That's already in my .profile file. But anyway, here it is.
aaron@zenbook:~$ echo $EDITOR
nano
aaron@zenbook:~$ brew edit hello
Editing /home/linuxbrew/.linuxbrew/Homebrew/Library/Taps/homebrew/homebrew-core/Formula/hello.rb
Warning: Using edit because no editor was set in the environment.
This may change in the future, so we recommend setting EDITOR,
or HOMEBREW_EDITOR to your preferred text editor.
Error: no "edit" mailcap rules found for type "application/x-ruby"
Error: Failure while executing; `edit /home/linuxbrew/.linuxbrew/Homebrew/Library/Taps/homebrew/homebrew-core/Formula/hello.rb` exited with 3.

Did you export it? Closing this as I can't reproduce.


Created Robot Project

Added Advantage Kit Project, Cleaned it, Updated Constants, Added Beta Number, or basically created base project.

Lgtm!


Replace ugettext_lazy with gettext_lazy

@alex-pythonista Please, could you merge this small fix to support Django 4?

I would love to. But merging this pull request requires write access, which I currently don't have.

@andreyrusanov Can you merge this branch? That would be helpful for everyone. Also, Django 4.2 LTS will be released this year.

@alex-pythonista I don't have write access:)

@tomlaszczuk can you merge this pull request?

@tomlaszczuk @toxinu @mariodev could you guys check the MR and merge it that people can continue using this library?


Publish warning for FM1 LO instability

ESA requested a warning on the webpage for a instrumental issue for years 2010-2017 with impact on FM1 data.
@donal-mur write a short note on what what message you want to publish as a comment in this issue.

Users are warned that data  from  FM01 may be unreliable between early 2010 and Jan 2018 due to a misbehaving local oscillator in the instrument. This has manifested itself by introducing asymmetric and broadened line shapes resulting in too low ozone and ClO values. We are looking at ways to mitigate the effect but until then please use FM01 data with caution.


No longer working

Unfortunately it appears they have altered the code significantly. I've downloaded a couple of html files and it doesn't appear there are any links to high res images anymore.
May be dead project ;(

Vinted changes its html files every few months. It's not the first time...
I try to keep up and fix the script every time. I will have a look and try to fix the script.

Found it! :smile:
They have moved the json data from inside the html file to an external .json file that is downloaded alongside the html.
I will try to fix it today or during the week.

Getting the json file requires some auth cookies. I need to change the code a bit.
 I need to change the
code a bit.
In the meantime, here is a bash script which will download the photos in
full res (without save other informations like the python script does):
url=$1
item_id=echo "$1" | grep -oP "(?<=/)\d+(?=-)"
curl
-H "Accept: text/html,application/xhtml+xml,application/xml;q=0.9,image/avif,image/webp,/;q=0.8"
-H "Accept-Encoding: gzip, deflate, br"
-H "Accept-Language: fr-FR,fr;q=0.5"
-H "Connection: keep-alive"
-H "Sec-Fetch-Dest: document"
-H "Sec-Fetch-Mode: navigate"
-H "Sec-Fetch-Site: cross-site"
-H "TE: trailers"
-H "Upgrade-Insecure-Requests: 1"
-H "User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:109.0) Gecko/20100101 Firefox/118.0"
--cookie-jar "vinted_cookies.txt"
--output vinted_home.out "https://www.vinted.fr"
curl
-H "Accept: text/html,application/xhtml+xml,application/xml;q=0.9,image/avif,image/webp,/;q=0.8"
-H "Accept-Encoding: gzip, deflate, br"
-H "Accept-Language: fr-FR,fr;q=0.5"
-H "Connection: keep-alive"
-H "Sec-Fetch-Dest: document"
-H "Sec-Fetch-Mode: navigate"
-H "Sec-Fetch-Site: cross-site"
-H "TE: trailers"
-H "Upgrade-Insecure-Requests: 1"
-H "User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:109.0) Gecko/20100101 Firefox/118.0"
--cookie "vinted_cookies.txt"
--output vinted_item.out "https://www.vinted.fr/api/v2/items/$item_id?localize=false"
count=0for photo_url in cat vinted_item.out | gzip -d | jq -r ".item.photos[] | .full_size_url"do
curl
-H "Accept: text/html,application/xhtml+xml,application/xml;q=0.9,image/avif,image/webp,/;q=0.8"
-H "Accept-Encoding: gzip, deflate, br"
-H "Accept-Language: fr-FR,fr;q=0.5"
-H "Connection: keep-alive"
-H "Sec-Fetch-Dest: document"
-H "Sec-Fetch-Mode: navigate"
-H "Sec-Fetch-Site: cross-site"
-H "Upgrade-Insecure-Requests: 1"
-H "User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:109.0) Gecko/20100101 Firefox/118.0"
--output "vinted_photo_$count.jpg"
$photo_url
((count++)) || truedone
Just save it in a file download_full_size_images.sh and call it with:
bash -e -x download_full_size_images.sh URL_OF_THE_ITEM
—
Reply to this email directly, view it on GitHub
https://github.com/boberle/vinted-downloader/issues/1#issuecomment-1742036432,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/BC5ICPUU6LGTD7CYDPJ6J6TX5FBE7ANCNFSM6AAAAAA5MKM6F4
.
You are receiving this because you authored the thread.Message ID:
@.***>

Oh, perhaps related - do you know if the sold item numbers are also indexed somewhere (relative to the actual username)? I believe that unless the user explicitly deletes it it remains as a viewable page.

The items are definitely stored somewhere. I'm not able to find specific URLs related to the items in the user profiles, however it appears the tag for return is "is_visible" - for example, if you look up item<PHONE_NUMBER>, the is_visible variable is set to 0, whereas a searchable item has it set at 1.  The URL for the item is still a valid link and can be returned although the site has a "view sold item" challenge.
I think from looking at the site structure that the item list is populated server side
https://www.vinted.com/api/v2/users/$userID/items
The basic URL does a request and in effect shows only about 50 items by default, but you can add the suffix
?page=1&per_page=96&order=relevance to get a maximum of 96 at a time. Theoretically perhaps a query for items that are not visible can be formed? Your thoughts?

I've updated the python code to take into account the changes. So I will close the issue. You can create a new one for the sold items if you want.
Regarding the sold items, they are kept, but they seem to be visible only by the user. I think the list of items for a given user includes the sold items only if you are viewing your own list of items, not someone else's. So I don't think you can get the list of sold items of a random user, even if you can view a sold item if you have the URL. I've done some tests using 2 vinted accounts, and was unable to find my sold items when not logged in or logged in with a secondary account.
The is_visible property doesn't refer to a sold item, but to an option the seller has to hide an item ("masquer" in French):


Using different Github accounts for VS Code Setting Sync and for Copilot Chat

VS Code Version:
Version: 1.86.0-insider
Commit: 9621add46007f7a1ab37d1fce9bcdcecca62aeb0
Date: 2023-12-20T05:36:57.756Z
Electron: 27.1.3
ElectronBuildId: 25612240
Chromium: 118.0.5993.159
Node.js: 18.17.1
V8: <IP_ADDRESS>-electron.0
OS: Windows_NT x64 10.0.19045
OS Version: 10 22H2

Steps to Reproduce:

Sign in to VS Code with GitHub for settings sync
Sign in to Copilot extension with a different Github account for Copilot access

(it works at this point)

Enable Chat extension

it complains that my Copilot license is expired.

The account I'm using for VS Code settings sync is my old account, which had Copilot enabled for about a year;
the account I have Copilot license enabled now in is a company-bound account (this one).
Copilot itself and Copilot Labs work, but Chat doesn't and it complains on each VS Code start about that.

This is a critical scenario.
We really need this for enterprise scenarios... Isolation of Enterprise account data for/without copilot enabled...

I'd rather not use chat at all (and currently I'm not using it, despite Copilot extension installs the chat every time, and then Chat disables it if I disable Chat, though the main Copilot extension working flawlessly without Chat).


How to use custom_fields in create()

Hi,
How to use custom_fields in create()?
Could you provide an example please?

You'd pass a dictionary to a named arg of custom_fields. There's an example in the tests here: https://github.com/digitalocean/pynetbox/blob/master/tests/test_dcim.py#L226-L231
That should work.


load_file() - Complete Parquet file is loaded in Memory

Describe the bug
When inferring schema complete Parquet is loaded in memory.
https://github.com/astronomer/astro-sdk/blob/e4111397387e43ba7c8d2c0f5645376c466d271a/python-sdk/src/astro/files/types/parquet.py#L45
Version

Astro: 1.1.1

Expected behavior
Research - if there is a better way to read schema information from parquet instead of not loading them in memory.
Additional context
Add any other context about the problem here.

Removing this from 1.2.1 as per discussion

Refer to how PyArrow implemented this.


Produce and launch borough quiz #1

For next week. We'll talk it through then.

Pick the borough
Put together the photo request
Produce the quiz
[some other things] Profit?
Launch!

Launching on June 1

🍕🍕🍕🍕🍕🍕🍕🍕🍕🍕🍕🍕🍕🍕


azure.mgmt.costmanagement create_or_update() operation fails with 401 unauthorized if authenticated as a service principal

azure.mgmt.costmanagement create_or_update() operation fails with 401 unauthroized if authenticated as a service principal, but works fine if authenticated as an interactive user. Repro provided by email.
Traceback (most recent call last):
File ".\setup_cost_export.py", line 66, in
main()
File ".\setup_cost_export.py", line 62, in main
export = cclient.exports.create_or_update(scope, export_name, parameters)
File "C:\Users\guybo\AppData\Local\Programs\Python\Python37\lib\site-packages\azure\mgmt\costmanagement\operations\exports_operations.py", line 238, in create_or_update
raise models.ErrorResponseException(self._deserialize, response)
azure.mgmt.costmanagement.models.error_response_py3.ErrorResponseException: (401) Unauthorized (Request ID: 658c30ab-ec24-487d-8a51-81f873e35196)

Hi @gbowerman
Tagging @melmullen to the rescue

Hi @Abyssknight , help to have a try on this.

latest azure-mgmt-costmanagement is 3.0.0. Does it work for you?


"hint" on tutorial avatar bleeds out in other locales

"Hint" works in English because it is just 4 character but it gets much large in other locales, like "suggerimento" in Italian. We should use an icon instead.

Can i do this?

You are welcome to send us a PR, yes!

Which files do i need to change? Can you guide me in the right direction.


chore: bump sbt-scalafix from 0.10.2 to 0.10.4

Updates ch.epfl.scala:sbt-scalafix from 0.10.2 to 0.10.4.
GitHub Release Notes - Version Diff
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!

Adjust future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "ch.epfl.scala", artifactId = "sbt-scalafix" } ]

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequests = { frequency = "@monthly" },
  dependency = { groupId = "ch.epfl.scala", artifactId = "sbt-scalafix" }
}]

labels: sbt-plugin-update, early-semver-minor, semver-spec-patch, commit-count:1

Codecov Report

Merging #109 (dd2016c) into master (2df0a87) will not change coverage.
The diff coverage is n/a.

Additional details and impacted files

@@           Coverage Diff           @@
##           master     #109   +/-   ##
=======================================
  Coverage   68.09%   68.09%
=======================================
  Files          79       79
  Lines        1078     1078
  Branches       84       84
=======================================
  Hits          734      734
  Misses        344      344


loadAndTransform throws error when plugin tries to resolve ID to external URL

Describe the bug
When a plugin tries to resolve an ID to an external URL, following error is thrown on the terminal:
Failed to load url<EMAIL_ADDRESS>(resolved id: https://esm.sh/stable/react@18.2.0/es2022/react.js). Does the file exist? (x2)

Related pull request: #10880
Reproduction
https://stackblitz.com/edit/vitejs-vite-sjrjug
Steps to reproduce
Run npm install followed by npm run dev
System Info
System:
  OS: Linux 5.0 undefined
  CPU: (8) x64 Intel(R) Core(TM) i9-9880H CPU @ 2.30GHz
  Memory: 0 Bytes / 0 Bytes
  Shell: 1.0 - /bin/jsh
Binaries:
  Node: 16.14.2 - /usr/local/bin/node
  Yarn: 1.22.19 - /usr/local/bin/yarn
  npm: 7.17.0 - /usr/local/bin/npm
npmPackages:
  @vitejs/plugin-react: ^2.1.0 => 2.1.0
  vite: ^4.0.0 => 4.0.4

Used Package Manager
npm
Logs
No response
Validations

[X] Follow our Code of Conduct
[X] Read the Contributing Guidelines.
[X] Read the docs.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Make sure this is a Vite issue and not a framework-specific issue. For example, if it's a Vue SFC related bug, it should likely be reported to vuejs/core instead.
[X] Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
[X] The provided reproduction is a minimal reproducible example of the bug.

https://stackblitz.com/edit/vitejs-vite-sjrjug
@sagargurtu
I found vite.config.ts

 optimizeDeps: {
    exclude: ['react'],
  }

but<EMAIL_ADDRESS>is cjs.
so optimizeDeps: {  can fixed.
include: ['react'],
}


How to hide "more videos" row when video paused?

Hi it's me again. First of all, thank you very much for creating this library it is really helpful for my current project!
However, I got some question, as mentioned above. I'm using your library to develop a TV app and currently as I pause the video, this "more videos" row will appear (as shown in picture below). Is it possible to make it hidden?
As far as I remembered, this row is not visible at some points of my development progress. I didn't exactly know what triggers it and how to make it hidden back.

Hi, I have noticed the same problem.
This library is built on top of the web version of the YouTube player. It seems that the team at YouTube is making some changes to the player.
My current assumption is that you haven't done anything to trigger the bar, it is there because a different version of the player gets delivered.
There are two possible cases:

my assumption is correct: there is not much we can do about it. Unfortunately this changes are not reported in the player's documentation.
my assumption is not correct: it would be worth investigating why the web player is not behaving in a deterministic way. Maybe there is a problem with the hide ui flag.

I see. No wonder I think I only started to see this change lately. Actually I got a hunch similar as your assumption, and just to make sure I ask about it here.
Anyway, thanks a lot for the fast feedback!  Really appreciate it. :+1:

I have looked at the update notes of the IFrame API, as expected they made changes to the player :/
can't say I'm happy about this.
https://developers.google.com/youtube/player_parameters#release_notes_08_23_2018

Thanks for your hard work on this.

@ghozien unfortunately you cannot. The IFrame player doesn't allow it.

because I will upload my application in the play store, and I don't want my application blocked by the play store because there is a YouTube logo.

@ghozien this is not related to this issue. Open a new one or search for old issue related to this topic.

Yep, rel = 0 behaves differently now.

can you help me
how to use rel parameter ?

You can use IFramePlayerOptions to change its value.

The change to the IFrame API seems permanent and there is no way around it, without using hacks. Therefore I'm closing this issue.
Buy using IFramePlayerOptions is possible to set the recommended videos to come from a single channel instead of from all of YouTube.