How can I open a folder with source code to start coding?

I know this is not a issue of your starter.
But please help me to start a simple left  tree editor.
I followed your readme.md and :Lazy works

But whats next?
I only need to have a simple left side tree browser and right side with editor like this

I researched but this is so simple that no one wrote a post

I use neo tree for that.
-- :Neotree to open it
-- docs for additional config:
-- https://github.com/nvim-neo-tree/neo-tree.nvim?tab=readme-ov-file#quickstart

return {
  'nvim-neo-tree/neo-tree.nvim',
  version = '*',
  dependencies = {
    'nvim-lua/plenary.nvim',
    'nvim-tree/nvim-web-devicons', -- not strictly required, but recommended
    'MunifTanjim/nui.nvim',
  },
  config = function()
    require('neo-tree').setup {
      filesystem = {
        filtered_items = {
          visible = true,
          hide_dotfiles = false,
          hide_gitignored = true,
        },
      }
    }
  end,
}

https://github.com/ChillerDragon/kickstart.nvim/blob/7652a9921cd9409728655c85670a3d147d7187f3/lua/custom/plugins/filetree.lua
And press <leader>ft to toggle it
vim.keymap.set('n', '<leader>ft', function()
  vim.cmd 'Neotree toggle'
end, { desc = '[F]ile [T]tree' })

https://github.com/ChillerDragon/kickstart.nvim/blob/7652a9921cd9409728655c85670a3d147d7187f3/lua/custom/chiller/keymaps.lua#L2-L4

@jrichardsz The neo-tree plugin is already included in the kickstart repo but is commented out by default.
All you need to do is uncomment the require 'kickstart.plugins.neo-tree' on line 880 in init.lua, here is a diff:
diff --git a/init.lua b/init.lua
index 036eefb..784f748 100644
--- a/init.lua
+++ b/init.lua
@@ -877,7 +877,7 @@ require('lazy').setup({
   -- require 'kickstart.plugins.indent_line',
   -- require 'kickstart.plugins.lint',
   -- require 'kickstart.plugins.autopairs',
-  -- require 'kickstart.plugins.neo-tree',
+  require 'kickstart.plugins.neo-tree',
   -- require 'kickstart.plugins.gitsigns', -- adds gitsigns recommend keymaps

   -- NOTE: The import below can automatically add your own plugins, configuration, etc from `lua/custom/plugins/*.lua`

Then restart nvim and press the key \ which is the default keymap for neo-tree, or type :Neotree. You can of course customize the keymaps to your liking.

Use neotree as described. Thanks for the issue!

@jrichardsz The neo-tree plugin is already included in the kickstart repo but is commented out by default. All you need to do is uncomment the require 'kickstart.plugins.neo-tree' on line 880 in init.lua, here is a diff:
diff --git a/init.lua b/init.lua
index 036eefb..784f748 100644
--- a/init.lua
+++ b/init.lua
@@ -877,7 +877,7 @@ require('lazy').setup({
   -- require 'kickstart.plugins.indent_line',
   -- require 'kickstart.plugins.lint',
   -- require 'kickstart.plugins.autopairs',
-  -- require 'kickstart.plugins.neo-tree',
+  require 'kickstart.plugins.neo-tree',
   -- require 'kickstart.plugins.gitsigns', -- adds gitsigns recommend keymaps

   -- NOTE: The import below can automatically add your own plugins, configuration, etc from `lua/custom/plugins/*.lua`

Then restart nvim and press the key \ which is the default keymap for neo-tree, or type :Neotree. You can of course customize the keymaps to your liking.

Thanks it worked.

file browser plugin example
I use neo tree for that.
-- :Neotree to open it
-- docs for additional config:
-- https://github.com/nvim-neo-tree/neo-tree.nvim?tab=readme-ov-file#quickstart

return {
  'nvim-neo-tree/neo-tree.nvim',
  version = '*',
  dependencies = {
    'nvim-lua/plenary.nvim',
    'nvim-tree/nvim-web-devicons', -- not strictly required, but recommended
    'MunifTanjim/nui.nvim',
  },
  config = function()
    require('neo-tree').setup {
      filesystem = {
        filtered_items = {
          visible = true,
          hide_dotfiles = false,
          hide_gitignored = true,
        },
      }
    }
  end,
}

https://github.com/ChillerDragon/kickstart.nvim/blob/7652a9921cd9409728655c85670a3d147d7187f3/lua/custom/plugins/filetree.lua
And press <leader>ft to toggle it
vim.keymap.set('n', '<leader>ft', function()
  vim.cmd 'Neotree toggle'
end, { desc = '[F]ile [T]tree' })

https://github.com/ChillerDragon/kickstart.nvim/blob/7652a9921cd9409728655c85670a3d147d7187f3/lua/custom/chiller/keymaps.lua#L2-L4
plain kickstarter workflow
If you just type in nvim it opens the current folder by default. You can then press space+s+f (<leader>sf) to search for a file.

Neo Tree works very well. Thank you!


Please Convert  field Shipping Advice to enum in "Sales Header"

Hi Team,
We need to add few more option for field Shipping Advice. But it is a option field not enum so we can't.
Please convert it to enum so that we can extend it and add one more option in this field.
Best Regards,
Ratnesh Awasthi

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. We will update this issue with information about availability.


Other info
sdkconfig is default, except 2MBit/s upload speed and 4 MB flash
I tried to run the following code on the latest master brach compiled with above mentioned compiler and tensa-esp32-elf-gcc (crosstool-NG esp32-2019r1-rc2) 8.2.0, but during the last case, the system restarts because of unsuccessful mutex unlocking.

Your code is wrong. You have 2 core here and the order of execution is not like you expect.
To use condition_variable, you need to lock a mutex to modify a variable before accessing using the cv. In your thread 1, you don't do that. This is required so the compiler issues a full memory barrier (so that CPU#1 can see what was modified by CPU#0)
Also, a cv can support spurious wakeup and you don't deal with them. Typically, when using a cv, you've to check the condition after being woken up and resume waiting if it's not happening.
Here you have no condition to check so it's unlikely it'll work as you expect.
See https://en.cppreference.com/w/cpp/thread/condition_variable
Also, remember you are running in realtime OS. In such system, a lock can livelock if a higher priority task is waiting for a lock locked by a low priority task. You have to use priority inheritance whenever possible here, and this means no C++'s std::mutex (unless FreeRTOS allows changing the mutex style after construction, I don't know).

Thanks for the clarification! To be honest, I haven't heard spurious wakeup before (:/). If someone runs into this problem in the future here is a good article about it.
I see your point in the last paragraph, it's good to know, I'll keep in mind.
Thank you again for your answer @X-Ryl669 , it was really helpful!


Python 3 and Django migrations (Django 1.7)

Do you know of a way to denote that South 1.0 is required to migrate this project?

Also, this PR now includes the merge commit. Could you rebase against the current master?
You can do it this way, in case you're not too familiar with git rebase:
git remote add upstream https://github.com/dbrgn/cmsplugin-randomquote/
git fetch upstream
git rebase upstream master

Or if you want to work around the rebasing:
git reset --hard upstream master
git cherry-pick a177c24
git cherry-pick fd54d3b

You can verify the result with git log and then force-push to your branch.

About South 1.0: no, if you don't want to make it a dependancy, I guess the only way is to document it well in the README. But I can see why this is a bit of a hurdle if you want to maintain < Django1.7 compatibility. Maybe it's time for another release and explicitly document that people who have older Django versions are better of installing and older version.
Let me try that rebasing thing.

Maybe it's time for another release and explicitly document that people who have older Django versions are better of installing and older version.

True, people wanting to support an older version can still use the current release if they wish :)

Think I've managed. I got a bit confused because my branch was named 'urga' and not 'master'.

Thanks!


[tool_crash] FileSystemException: Cannot create link, OS Error: Cannot create a file when that file already exists., errno = 183

Command
flutter pub add url_launcher

Steps to Reproduce

...
...
...

Logs
FileSystemException: Cannot create link, OS Error: Cannot create a file when that file already exists.
, errno = 183
#0      _Link.throwIfError (dart:io/link.dart:254:7)
#1      _Link.createSync (dart:io/link.dart:182:5)
#2      ForwardingLink.createSync (package:file/src/forwarding/forwarding_link.dart:20:16)
#3      ForwardingLink.createSync (package:file/src/forwarding/forwarding_link.dart:20:16)
#4      _createPlatformPluginSymlinks (package:flutter_tools/src/flutter_plugins.dart:1055:12)
#5      createPluginSymlinks (package:flutter_tools/src/flutter_plugins.dart:985:5)
#6      refreshPluginsList (package:flutter_tools/src/flutter_plugins.dart:1087:5)
<asynchronous suspension>
#7      FlutterProject.ensureReadyForPlatformSpecificTooling (package:flutter_tools/src/project.dart:355:5)
<asynchronous suspension>
#8      PackagesGetCommand.runCommand (package:flutter_tools/src/commands/packages.dart:326:7)
<asynchronous suspension>
#9      FlutterCommand.run.<anonymous closure> (package:flutter_tools/src/runner/flutter_command.dart:1336:27)
<asynchronous suspension>
#10     AppContext.run.<anonymous closure> (package:flutter_tools/src/base/context.dart:150:19)
<asynchronous suspension>
#11     CommandRunner.runCommand (package:args/command_runner.dart:212:13)
<asynchronous suspension>
#12     FlutterCommandRunner.runCommand.<anonymous closure> (package:flutter_tools/src/runner/flutter_command_runner.dart:296:9)
<asynchronous suspension>
#13     AppContext.run.<anonymous closure> (package:flutter_tools/src/base/context.dart:150:19)
<asynchronous suspension>
#14     FlutterCommandRunner.runCommand (package:flutter_tools/src/runner/flutter_command_runner.dart:244:5)
<asynchronous suspension>
#15     run.<anonymous closure>.<anonymous closure> (package:flutter_tools/runner.dart:91:9)

[✓] Flutter (Channel stable, 3.10.5, on Microsoft Windows [Version 10.0.19045.3086], locale en-PK)
    • Flutter version 3.10.5 on channel stable at C:\Users\moazz\moaz_files\flutter_windows_2.10.1-stable\flutter
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision 796c8ef792 (12 days ago), 2023-06-13 15:51:02 -0700
    • Engine revision 45f6e00911
    • Dart version 3.0.5
    • DevTools version 2.23.1

[✓] Windows Version (Installed version of Windows is version 10 or higher)

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

[!] Visual Studio - develop for Windows (Visual Studio Community 2017 15.9.18)
    • Visual Studio at C:\Program Files (x86)\Microsoft Visual Studio\2017\Community
    • Visual Studio Community 2017 version 15.9.28307.960
    • Windows 10 SDK version 10.0.17763.0
    ✗ Visual Studio 2019 or later is required.
      Download at https://visualstudio.microsoft.com/downloads/.
      Please install the "Desktop development with C++" workload, including all of its default components

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

[✓] VS Code (version 1.79.2)
    • VS Code at C:\Users\moazz\AppData\Local\Programs\Microsoft VS Code
    • Flutter extension version 3.67.20230601

[✓] Connected device (2 available)
    • vivo 1606 (mobile) • 4fb09154 • android-arm • Android 6.0.1 (API 23)
    • Windows (desktop)  • windows  • windows-x64 • Microsoft Windows [Version 10.0.19045.3086]

[✓] Network resources
    • All expected network resources are available.

! Doctor found issues in 1 category.

Flutter Application Metadata
Type: app
Version: 1.0.0+1
Material: true
Android X: false
Module: false
Plugin: false
Android package: null
iOS bundle identifier: null
Creation channel: stable
Creation framework version: 2ad6cd72c040113b47ee9055e722606a490ef0da
Plugins
file_picker-5.3.1
firebase_auth-4.6.3
firebase_auth_web-5.5.3
firebase_core-2.14.0
firebase_core_web-2.6.0
firebase_crashlytics-3.3.3
flutter_plugin_android_lifecycle-2.0.9
fluttertoast-8.2.2
google_maps_flutter-2.2.5
google_maps_flutter_android-2.4.10
google_maps_flutter_ios-2.2.1
image_picker-0.8.7+5
image_picker_android-0.8.6+16
image_picker_for_web-2.1.12
image_picker_ios-0.8.7+4
location-4.4.0
location_web-3.1.1
otpless_flutter-1.0.8
path_provider_linux-2.1.10
path_provider_windows-2.1.6
shared_preferences-2.0.18
shared_preferences_android-2.0.17
shared_preferences_foundation-2.1.5
shared_preferences_linux-2.1.5
shared_preferences_web-2.0.6
shared_preferences_windows-2.1.5
uni_links-0.5.1
uni_links_web-0.1.0
url_launcher-6.1.11
url_launcher_android-6.0.36
url_launcher_ios-6.1.4
url_launcher_linux-3.0.5
url_launcher_macos-3.0.5
url_launcher_web-2.0.17
url_launcher_windows-3.0.6

Closing this as a duplicate of https://github.com/flutter/flutter/issues/90028.
Kindly subscribe to the original issue for updates.
Thank you


Feat/agent commands

3.5.0 - (Venetian Red Vienna) - May 2019

CLI Command: agent-status displays agent status

CLI Command: agent-token provides a valid agent token for use in tools (e.g. postman)

CLI Command: service-token provides a valid service-credentials token for use in tools (e.g. postman)

CLI Command: prepare-bulk - creates a template directory for timeseries (bulk) upload

CLI Command: run-bulk - runs the timeseries (bulk) upload jobs

CLI Command: check-bulk - checks the progress of the upload jobs

CLI Command: create-agent - creates a new agent in the mindsphere (#12)

CLI Command: offboard-agent - offboards the agent in the mindsphere (#11)

CLI Command: renew-agent  - renews the agent secrets (#13)

mindconnect-agent: created new UploadFile method capable of running the multipart upload (#4)

mindconnect-agent: the UploadFile can now take a buffer additionally to file (#23)

mindconnect-agent: the UploadFile can now run in parallel (#23)

mindconnect-agent: the MindSphere path name can be configured (#23)

mindconnect-agent: deprecated the old upload method (#23)

SDK: started a  PRELIMINARY SDK for the new commands which require additional mindsphere APIs

SDK: preliminary Support for

Asset Management Service
Agent Management Service
IoT File Service
Time Series Bulk Service
Time Series Bulk Service
Event Management Service

CLI: color support for low color terminals

Closes #13 #11 #12 #30


Incorrect plural variable name in the docs

Hi, I'm using alice in my project, ropper.
I found a small issue in the docs. The example in the docs shows the following snippet:
namespace alice {

template<>
struct store_info<graph>
{
  static constexpr const char* key = "graph";
  static constexpr const char* option = "graph";
  static constexpr const char* mnemonic = "g";
  static constexpr const char* name = "graph";
  static constexpr const char* name = "graphs";
};

}

But the last variable should be name_plural as follows:
namespace alice {

template<>
struct store_info<graph>
{
  static constexpr const char* key = "graph";
  static constexpr const char* option = "graph";
  static constexpr const char* mnemonic = "g";
  static constexpr const char* name = "graph";
  static constexpr const char* name_plural = "graphs";
};

}

Thanks!


Add steps to release pipeline to publish to azure CDN

Description
Using the existing release script to upload the files controlled by app-frontend-react to the new cdn solution.
For now both the old and the new CDN should be updated, once we are truly confident in the setup we can remove the old.
The new steps require som secrets, will mark the PR as ready when they are available.
Related Issue(s)

relates to: altinn/altinn-studio#7566

Verification

Manual testing

[ ] I have tested these changes manually
[ ] Creator of the original issue (or service owner) has been contacted for manual testing
[ ] No testing done/necessary

Automated tests

[ ] Unit test(s) have been added
[ ] Cypress E2E test(s) have been added
[ ] No automatic tests are needed here
[ ] I want someone to help me make some tests

User documentation @ altinn-studio-docs

[ ] Has been updated

[ ] No changes/updates needed

Changes/additions to component properties

[ ] Changes are reflected in both src/layout/layout.d.ts and layout.schema.v1.json, and these are all backwards-compatible
[ ] No changes made

Support in Altinn Studio

[ ] Issue(s) created for support in Studio

[ ] This change/feature does not require any changes to Altinn Studio

Sprint board

[ ] The original issue (or this PR itself) has been added to the Team Apps project and to the current sprint board

Good questions as always, since the azure step leverages copy no files will be deleted, but if a file is updated it will be overridden. The downside is that this will do a full copy of all the files every time we release so I think I will need to change that.
Might need to extend the release.sh with an --azure (or something) argument where the logic to copy only the new files to azure.
This will keep all the release logic inside the release.sh script. If you agree I can make these changes to the script and request a new review after I'm done

@tjololo Yup, I agree! Part of the reason I made the release.sh script is that it's actually possible to run it locally in order to test out what would happen. That makes changes much easier to verify, so I'm all for adding to that script instead of putting things on the outside.
As an aside, will we at some point remove the git-backing for CDN? Right now the repo is fairly large for a git repo, and we would like to make it a bit larger (by adding source maps), but so far we've held that back in anticipation of the new CDN. Maybe we could get usage reports from azure in the future to make it possible to remove older (unused) versions? It's most likely not very critical we keep multi-year old patch releases.

Updated the release.sh with logic for syncing with azure.
The new functionality still piggybacks on the copy logic against altinn-cdn, when we are confident in the new azure cdn we can replace the logic with scripts that copy all the files to be published to a folder and sync it. Then this release logic would not need to fetch all the old versions just sync the new version.
The sync operation filters out and only uploads folders matching the regexes and compares the md5 hashes to determin if a sync is needed on those files.
The script has three options for running:

--azure-sa-name <name> set to an existing folder would trigger an rsync to this folder with the files to be synced (this is an best effort simulation
--azure-sa-name <name> set to a storageaccount name and --azure-sa-token <sas-token> with a token for that storage account. As long as --azure-sync-cdn is not present it will perform an dry-run and output what files would be updated in the storageaccount. Needs acces to the storage account but will display changes that would actually be made
--azure-sa-name <name> --azure-sa-token <token> --azure-sync-cdn performes the actual sync against azure


Demo using Kafka to talk to Sherlock

Make a demo of using Kafka to handle the communication and load balancing between the ingest process and Sherlock.

I'm happy to have a go at building this, but at the moment I don't have time allocated to do it.

Demo in https://github.com/lsst-uk/kafka-exp/tree/master/sherlock

It seems that Sherlock must have its requests batched, since it takes a long time to parse the config script, set up the database connection, etc. So the Kafka event will actually contain a batch of sky positions and return a batch of classifications. For sample request and response:
https://github.com/lsst-uk/lasair/tree/master/src/sherlock_web_wrapper/server/data

I think in the long run we can fix that, but I don't see any reason why the wrapper can't handle the batching in a way that's transparent to the rest of the system. Roughly what sort of batch size were you anticipating?

I note that DaveY, myself, and you all have parts of this single application code in our own repo. When DaveY fixed sherlock, it was a delta from his original code, which of course I had already changed. So big merge job this afternoon. We need to work together on the same repo.

Assuming that the "you" in the above refers to me - I don't think that's been the case so far. Yes, as soon as I start writing code which is actually going to be part of Lasair I'll try to put it in the Lasair repo, but I think random learning and experiments are better kept separate.
A better question is how do we manage the differences between Lasair-ZTF and Lasair-LSST?


Some characters are only needed for RTL fonts.

The characters U+202A - U+202E are only needed for RTL fonts, and are not needed for any of the current NLCI fonts.

U+200E LEFT-TO-RIGHT MARK and U+200F RIGHT-TO-LEFT MARK also do not need to be in LTR fonts.


Make Reason an optional dependency

The Reason dependency currently puts an upper limit on the ocaml compiler, and it adds some unneeded bloat for users who aren't interested in that syntax variant. Would it be possible to make Reason an optional dependency and, if so, would you open to this change?

Hi @shonfeder!
I'm not familiar with how optional dependencies work, but if that's feasible without degrading the experience of Reason users, I'm 100% open to it!
Spin is also distributed as a standalone executable, an npm package, and a Homebrew package. You are not constrained by OCaml's upper limit with them. The last version is only available on Opam, but I will release it on the other installation platforms soon. I'd recommend switching to one of these in the meantime if that's possible for you 🙂

Thank you for the pointer to the other package managers!
If I get some some free cycles, I can look into adding the optionality. :)

Today, I suggested to a user to use spin to quickly start with a project. Unfortunately, he had some problems installing it:
he following dependencies couldn't be met:  - spin -> reason -> ocaml < 4.11
ocaml --version: The OCaml toplevel, version 4.11.1
what does that even mean
it wants to downgrade my ocaml

If spin had a leaner dependency profile, issues like this could be avoided for opam users. I bet it would also make it easier to package spin for upstream distro users.
As a side note: I've been considering to to deprecated dune init and just tell users to use spin. This would be a much more attractive option if users could easily use spin with the latest version of OCaml using their preferred package manager.

@rgrinberg Thanks for reporting the issue!
As you've experienced with the release of ocaml-lsp-server on opam, compatibility with the latest version of OCaml is blocked until Reason is released on opam. That's very unfortunate, but I don't see any alternative at the moment: Reason users make up for a large portion of Spin users, so dropping support for Reason is not an option. As I said, I am not very familiar with optional dependencies, but maybe you know a way to make the dependency on Reason optional? Like, is it possible to test for the presence of a library at compile time?
As I mentioned to @shonfeder, a workaround, for now, would be to install spin without opam. Users can use the installation script for instance. Another workaround would be to pin reason to their git repository, which is compatible with OCaml 4.11.
I'd also like to slim down the number of dependencies. Some of them can definitely be vendored (e.g. it's already the case of lambda-term), but I am not sure it would make sense to vendor Reason (because of its size), do you have any opinion on this?

As a side note: I've been considering to to deprecated dune init and just tell users to use spin

I appreciate you considering spin as an alternative to dune init! I'm very open to suggestions/feature requests, so let me know if there's anything dune users would miss if they switched to spin, or if you had any feedback on dune init that you'd like to see implemented in spin.

Why would dropping reason as a dependency degrade the experience for reason users of spin? The only thing that should matter to users is that reason/ocaml templates are available, right? It would just be a matter of running refmt on all of spin I think.

 Spin uses a custom implementation of refmt. I can't remember any good reason for this, so I could try removing the custom implementation and call refmt instead.

Ah, actually the reason for this is that I wanted spin to be usable by users who don't have reason on their system.
Typically, esy users don't have Reason installed, it's only installed in their project's sandbox.

And if that doesn't work, you could always just put your custom wrapper spin-refmt subpackage. As long as you can just call it as a binary.

Typically, esy users don't have Reason installed, it's only installed in their project's sandbox.

Seems like  you should be using the version of reason in their sandbox then 🤔 There are many versions of reason out there and it doesn't seem like it's possible to always use the one in spin.

Seems like you should be using the version of reason in their sandbox then

Great idea! Would be the same for opam projects actually, the workflow would to generate the project and install the dependencies first, then reformat the code and remove the ml files.


T62936: gltf export with jpeg textures

Blender repo issue : https://developer.blender.org/T62936
T62936: gltf export with jpeg textures
With exporting jpeg textures them assigned as png images and dont founds
this is the file (file provided on blender repo)
If i manually change in gltf text file "png" to "jpg" all works fine (file provided on blender repo)
You may test on this site
https://www.creators3d.com/faq
This is my shader setup
Where i can attach ao texture?
https://dev-files.blender.org/file/data/lc5j3sqo5kpw6j3jrqqi/PHID-FILE-mn5pwq3l5bbybwtzwqkq/Screenshot_20190325_214702.jpg

If I understood correctly, the issue was that the images had the wrong mime-type/file suffix referenced in the gltf-file. I wasn't able to reproduce the error with the zip-files attached. Any chance of seeing the actual .blend-file?

Can you please ask directly on blender issue tracker, because the user will probably not read it here

The .blend-file can be downloaded here: http://pasteall.org/blend/index.php?id=51463

I closed the report, because everything works fine with official builds, the user has issue only when he compiles from sources. So this is a building issue, not a glTF bug


parameters of the model

When you run train.py, print"# parameters: "

What is printed after "# parameters: "?


Idea: dontMock has option to add recursively

I was trying to call dontMock on the joi library (a schema validation library), and I had to add a lot of dontMock commands to get it to work—basically one for every file required in the library, recursively. While this makes sense in many situations, it would sure be nice to be able to tell Jest to dontMock a file and and files it requires.
One option could be something like jest.dontMock( moduleName, [recursive] ), where recursive is a boolean that defaults to false, matching the current behavior. If it is set to true, it would apply dontMock recursively.
Another option might be to base it off of what is being required: it seems to me that calling dontMock on a module in node_modules would usually want a recursive dontMock, whereas most other cases would want the non-recursive variety. Perhaps that API is too confusing.
Thoughts?

Yea this has come up a few times before. It's a bit of a tricky subject which mostly boils down to the fact that modules and their closure state are shared between other modules. So, while it may be advantageous to deep-mock one module, that may mean you are unintentionally mocking a deep-recursive dependency module that a 3rd module might expect not to be mocked (or maybe you've even explicitly .mock()'d it).
The above situation, of course, assumes that mocking is a global concept -- as it is today in Jest. But we could also consider the idea that it's not, and that deep mock() and deep dontMock()s are states that only persist while executing that particular module, but not others. The problem here again comes back to the fact that modules persist state, and so it can quickly become confusing when some module state generated by A (which, let's say, was deep mock()ed) isn't being reflected deep down in B's dependency graph somewhere which was, say, deep dontMock()ed.
Ultimately it's a trade-off: Do we deal with a pretty annoying number of explicit dontMock()s? Or do we deal with a pretty annoying, edge-casey situation where modules get implicitly mocked for (probably) unexpected reasons? We decided to go with the first of the two evils because it's at least explicit and the cost of writing all those dontMock()s is one you only pay "once" and up-front (rather than later, when you might not remember all the intricacies of the module under test -- which includes all of their recursive dependencies, etc).
I'd really love to find a good solution here, but between the two options we haven't thought of a good one yet.

Yes, I can see that. I definitely think being explicit about exactly what one is doing with dontMock is a good thing—but I definitely wish there was a better solution.
Feel free to close this ticket if you'd like; I'm going to ramble on a bit more below with some related ideas I've had, if you don't mind.
Better Docs and Examples for Mocking
I've been testing with jest for a while now, but only today figured out how to use manual mocks in the __mocks__ directory. I had a couple hang-ups:

For some reason, it wasn't clear that I didn't have to write a mock completely from scratch, but could use dontMock and require.requireActual to build a mock based off of the existing module. I know the docs say it, but I guess it just took a while to sink in. Perhaps an example like this mock for mailcomposer would be useful in the docs? (Presuming this is reasonable jest style.)

jest.dontMock('../../node_modules/mailcomposer/node_modules/dkim-signer');
jest.dontMock('../../node_modules/mailcomposer/node_modules/follow-redirects');
jest.dontMock('../../node_modules/mailcomposer/node_modules/he');
jest.dontMock('../../node_modules/mailcomposer/node_modules/mime/mime.js');
jest.dontMock('../../node_modules/mailcomposer/node_modules/mimelib');
jest.dontMock('fs');
jest.dontMock('path');

module.exports = require.requireActual('mailcomposer');

Similarly, the docs say "Manual mocks are defined by writing a module in a mocks/ subdirectory immediately adjacent to the module." What wasn't clear to me is what this meant for modules in the node_modules directory. When I got around to testing, it appears that "immediately adjacent to the module under test" is actually what is going on—which is great.

I know there is a config.unmockedModulePathPatterns configuration parameter, but I haven't figured out how to use it.

If I'm not too far off base, I may be able to make a pull request for some of these documentation items. Let me know!
Generation of mocks
Being new to jest, I've no idea if this is practicable in enough situations to make it worthwhile, but I wonder if jest (or a related tool) couldn't generate a mock of a module and stick it in the __mocks__ directory—perhaps something like the sample code I have above.
Actually, as I think about it, perhaps the generated mock should just do a regular require, and have all the dontMocks commented out. The benefit I see is that it gives a user a template for what might have to be mocked or not. They can requireActual and comment/uncomment dontMocks until their tests are working correctly.
User-contributed mocks
Again, just brainstorming—but perhaps some sort of user-contributed mocks of various modules would make jest more approachable for beginners? Certainly, in my case, the modules I've had the most trouble with were third-party modules that required mocking, not ones that I wrote myself.
Thanks for listening! :-D

I forgot to say…I've really enjoyed using jest to test my code, even with the work to get mocks to work correctly. Thanks for the great work!!!

A glob-styled syntax for dontMock'ing a hierarchy would accomplish most of what I want here without leading to unexpected dontMockin'ing of dependencies.

+1
Globs would make sense, though anything require'd from inside node_modules should probably be dontMockd by default, no?
(I am brand new to Jest, so if that's way off the mark don't hesitate to say so).

Perhaps this isn't the place to ask, but why would you want to mock libraries in node_modules?

@rattrayalex If it's something like lodash where you've got a library of sugar methods that could very well be built-ins - mocking is often unnecessary.
For something like react-router - you might be testing a custom component that happens to utilize a Link. The rendering / behaviour of the link isn't particularly important to your particular test case - e.g. asserting that "should update the shopping cart total when an item is added" doesn't care that back to shopping points to the correct location. If you use the real react-router you'll have to do extra work to set up the context required by react-router.
So you can't generally assume node_modules should / shouldn't be mocked by default. unmockedModulePathPatterns is a convenient solution for things like lodash.

Thanks @jacobstr, that makes a lot of sense!
Do you think it might be worthwhile to mention unmokedModulePathPatterns in one of the tutorials? I had about 30 lines of jest.dontMock('../../node_modules...etc...') before cleaning it up to 5 in package.json.
To be honest, though, I don't think Jest is right for me, as a total newcomer to testing. I don't really understand the utility of mocking because I haven't had to do it myself yet. If you think that's an accurate assessment (maybe not?) it may be worth mentioning in the docs. Or just saying more explicitly who Jest is for. I wouldn't say this is a big issue.

difference between dontmock and mock in jest

I am seeing the polar opposite in 0.5.2. The requires of an unmocked module are not mocked at all. I'm using a manual mock, though... as in this:
/// __mocks__/NewProjectPage.js
global.$ = require.requireActual('jquery');
module.exports = require.requireActual('pages/NewProjectPage');

Jest 0.9 should work much better in all of these cases. node_modules are now by default deep-unmocked as well, as that was a frequent source of issues with npm3. We have also updated the documentation to be more clear and we are exploring more ways of improving (un)mocking. I think this task is resolved but I'm happy to reopen if there is anything left to do here for now.

Is there a difference in behaviours between unmockedModulePathPatterns, unmock/dontMock and disableAutomock/autoMockOff when it comes to mocking a module's dependencies?
We observed that in a test that uses disableAutomock, a dependency's dependency (specifically enzyme's depdency, cheerio) got mocked and appeared to remain mocked for other tests.
Adding cheerio to unmockedModulePathPatterns seemed to solve this, but with enzyme already listed in this config item this feels like it ought to be unnecessary (and without the disableAutomock call, appears to be).
Symptomatically we saw the effect mentioned in this issue:
https://github.com/airbnb/enzyme/issues/309
which the original reporter mentions occurs with a Karma set up, so our problem may not actually relate to this issue. However, since it seems we were able to fix it with a specific configuration of mock disablements, which has led me to believe that in our case it could be a problem with Jest's mocking (or unmocking) behaviour.

Hey! unmockedModulePathPatterns unmocks everything inside of a specific path. Right now, unmocking a node_module in any way should transitively unmock all of its dependencies. If that doesn't work, then that seems like a bug. Would you mind sharing your specific Jest configuration and what was mocked and what wasn't? :)

@goivemaster could you update this issue with our specifics? Otherwise I will edit this when I can pull the latest version later today. Thanks @cpojer

Jest configuration :
"jest": {
    "rootDir": "./app/",
    "cache": false,
    "testPathIgnorePatterns": [
      "<rootDir>/__tests__/__helpers__/"
    ],
    "moduleFileExtensions": [
      "js",
      "jsx",
      "json"
    ],
    "unmockedModulePathPatterns": [
      "react",
      "moment",
      "radium",
      "enzyme",
      "cheerio",
      "lodash",
      "<rootDir>/__tests__/__helpers__/"
    ],
    "testFileExtensions": [
      "js",
      "jsx"
    ]
  }

If we put something inside unmockedModulePathPatterns should we expect all of its dependencies to also be unmocked? It appears that this is not the case. After adding enzyme to the unmockedModulePathPatterns we have been seeing errors relating to its dependencies remaining mocked hence the presence of cheerio and lodash. Is this a problem with Jest?

They should be unmocked. Although I recommend specifying something like node_modules/enzyme to make clear it is a path. Are you using the latest version of Jest?

this is the latest version of jest on npm: 11.0.0 is the latest of 81 releases,
we are running this version.
we see that the latest version on github is this: v0.10.0
we see no difference when adding the longer path.
we notice enzyme has no node_modules directory of its own
book.json        docs                       LICENSE.md       README.md          src
build            example-test.sh            mount.js         render.js          test
CHANGELOG.md     install-relevant-react.sh  package.json     shallow.js         withDom.js
CONTRIBUTING.md  INTHEWILD.md               ReactWrapper.js  ShallowWrapper.js

would this be causing the problem or does jest just look at the package.json of each package specified under unmockedModulePathPatterns?

@goivemaster did you have any luck on getting enzyme working? I hit exactly the same problem as you hit. When I use jest.disableAutomock(); the tests works, but when I omit it and rely on the unmockedModulePathPatterns the test fails. I even added dependencies from enzyme in the unmockedModulePathPatterns but now the dependencies of the dependencies are the problem I guess...

just a hunch, but this feels like it's related to Enzyme not having its own node_modules directory - this kind of transitive mocking seems to behave with other dependencies.
For our use case (I work with @goivemaster) we were able to get away with unmocking lodash and cheerio - which were causing the problems - by way of the unmockedModulePathPatterns config item.

That's weird, which version of Jest are you using? npm modules should definitely have transitive dependencies unmocked. If that's not the case, then that is a bug (the test for this is passing in Jest right now, though).

@cpojer It seems to have something to do with running multiple tests in one run. When I run tests individually they work, but when I run all the test suites together it fails depending on the order in which the test run/finish I have different tests failing.
Can it be that when test A requires module X to be mocked (and doesn't specify anything about module X, because mocking is the default) and a test B wants module X unmocked that test A might get an unmocked version. The opposite also seems true if you have automock-off and explicitly mock a module in a test you might get it mocked in another test that has automock-off.
I should try to create a simple reproducible test case I/we can use to debug the problem. Because in my real project I have way to many tests to make it easily debuggable, but it is hard to create such a test case because I don't know the internals, and have only a hunch about what is causing the problem.

Oh I see. Can you upgrade to Jest 12 and let me know if this problem still persists? We fixed something around this issue :)

thanks, upgrading to Jest 12 now, will revert the workarounds of explicitly calling autmockoff, dontmock and mock, and then report back

@cpojer Thanks! Upgrading from Jest 11 to 12 indeed solved the problem.


shift+enter in suggester don't insert the secondary markdown citation

from #114
shift+enter just goes to the next line

Hey @aidenlx, is there any news on a fix for this?

Well it seems like in editor, the editor shortcut with modifier will have highest priority, preventing suggester from working properly. In latest patch, ending slash is used to indicate secondary markdown citation.
For example, you can enter [@whatever_query/ and Enter to insert secondary markdown citation.

Well it seems like in editor, the editor shortcut with modifier will have highest priority, preventing suggester from working properly. In latest patch, ending slash is used to indicate secondary markdown citation.
For example, you can enter [@whatever_query/ and Enter to insert secondary markdown citation.

That's strange. In Zotero Integration, holding ctrl while pressing enter in the autocompletion suggester inserts the secondary markdown citation format without issues.


Fixes #527 - Update distributions_and_transfers.coffee asset

Resolves #527
Description

Refactor code on distributions_and_transfers.coffee asset
Block requests when storage location select is empty

Type of change

Bug fix (non-breaking change which fixes an issue)

How Has This Been Tested?

Used the steps to reproduce on the issue and
Selected a location and verify if the dropdown population still works

I'm going to update the failing tests to make the pr ready to merge

@andersonfernandes This looks great, thanks!


Copy govuk elements from govuk modules

This PR adds govuk_elements to the list of dependencies, so that it exists within /node-modules/, in the same way as the govuk front end toolkit and govuk template.
By default, the files from govuk_elements/public/sass are copied to app/assets/sass/, and imported by the application Sass file.
This means that govuk elements can be updated without overriding any changes to the application.scss file.
To use a custom set of modules from the govuk frontend toolkit and govuk elements (rather than all of them), the import statements will need to be copied from the _govuk-elements.scss partial into the application stylesheet, so here the partial would exist as a reference for any newly created modules.
cc. @tombye, @robinwhittleton, @timpaul.

Tested on a fresh clone and works well :+1:
One tiny thing (sorry, should have mentioned this before), we should specify a tag for elements in package.json so it's clear the version we're including.

I've requested that the package name be updated for govuk elements, which requires 06b3757 to be reverted.

This is now waiting on the version for govuk elements to be bumped to 1.0.0.

I get this error:
Joes-MacBook-Pro:govuk_prototype_kit joelanman$ npm install
npm ERR! git rev-list -n1 1.0.0: fatal: ambiguous argument '1.0.0': unknown revision or path not in the working tree.
npm ERR! git rev-list -n1 1.0.0: Use '--' to separate paths from revisions, like this:
npm ERR! git rev-list -n1 1.0.0: 'git <command> [<revision>...] -- [<file>...]'

Looks good to me. It's not exactly a breaking change, but people's list and panel styles will break if they update after this is merged. Does that justify a version bump?

Closing for now, will reopen once the package.json file for govuk elements has been updated.


running (from IEx) Network.setup doesn't seem set a new network

Environment

Elixir version (elixir -v): 1.7.3
Nerves environment: (mix nerves.env --info)

> mix nerves.env --info
|nerves_bootstrap| Environment Package List

  Pkg:         nerves_system_br
  Vsn:         1.5.3
  Type:        system_platform
  BuildRunner: {nil, []}

  Pkg:         nerves_system_rpi3
  Vsn:         1.5.1
  Type:        system
  BuildRunner: {Nerves.Artifact.BuildRunners.Local, []}

  Pkg:         nerves_toolchain_arm_unknown_linux_gnueabihf
  Vsn:         1.1.0
  Type:        toolchain
  BuildRunner: {Nerves.Artifact.BuildRunners.Local, []}

  Pkg:         nerves_toolchain_ctng
  Vsn:         1.5.0
  Type:        toolchain_platform
  BuildRunner: {nil, []}

|nerves_bootstrap| Loadpaths Start

Nerves environment
  MIX_TARGET:   rpi3
  MIX_ENV:      dev

|nerves_bootstrap| Environment Variable List
  target:     rpi3
  toolchain:  /home/thomas/.nerves/artifacts/nerves_toolchain_arm_unknown_linux_gnueabihf-linux_x86_64-1.1.0
  system:     /home/thomas/.nerves/artifacts/nerves_system_rpi3-portable-1.5.1
  app:        /home/thomas/Workspace/nerves/multiwifi

|nerves_bootstrap| Loadpaths End

Shoehorn apps:

iex(multiwifi@nerves.local)11> Shoehorn.children
[
  {Shoehorn.ApplicationController,
   {Shoehorn.ApplicationController, :start_link,
    [[init: [:nerves_runtime, :nerves_init_gadget], app: :multiwifi]]},
   :permanent, 5000, :worker, [Shoehorn.ApplicationController]}
]

Current behavior
I have a basic setup, started with the template from nerves_init_gadget, and a working network configured. When I log into an IEx and try to update the network to a new ssid with Nerves.Network.setup this doesn't do anything.
I've looked into the code and can't figure out directly why this wouldn't work.
if I do SystemRegistry.register() in the IEx session and then flush, I get the original network configuration. So I thought, if I do Nerves.Network.setup that calls eventually into SystemRegistry.update, I should get the updated information when I flush, but I don't see anything new?
So it seems that the new setup isn't passed into the SystemRegistry so, it can't get updated.
Expected behavior
Expected the network to change to the new network passed into setup.
I was thinking that this would be a simple workaround for #72, but as this doesn't work, it doesn't help.
I've also checked out the branch that is created for #72, but it seems that it's not completely trivial to update the branch for the current version of nerves_network.

I also noticed this with eth0. I'm not really sure why it's happening. I think it might be a quirk in SystemRegistry. Investigating more right now.

Fixed in #97


What is the difference between this and babel-plugin-inline-import ?

After reading the README I still can't really wrap my head around what exactly this package enables for graphql files in addition to what babel-plugin-inline-import already does ?

That package doesn’t parse the graphql file as AST, just returns the contents as a string. Probably useful on server-side for building typedefs from graphql files containing types. My package is for converting frontend graphql files containing operations (queries/mutations/subscriptions) into an AST object to be passed to something like the graphql() function from react-apollo.

Oh, I understand better now, thank you !
So, this is especially useful on he client side then ? Should I use babel-plugin-inline-import on the server side or do you still recommend using babel-plugin-inline-import-graphql-ast on the server ?

Personally, I just use the nodejs readFileSync function to read my server-side graphql files, so I’m not familiar with any other method so can’t really make a recommendation, but my package would not be useful on the server in any scenario I’m aware of.

Perhaps surprisingly, I’ve never actually used babel-plugin-inline-import. I just needed an example of how to write a babel plugin and it seemed very similar to what i wanted to do so i forked it to start work on my package.

Apparently babel-plugin-inline-import is very simple, i will just put the file's contents into a variable as a string.
So, on the client side, how would having an imported graphql file parsed into a graphql ast, as in your plugin, make one's life easier than just having it in the form of a string, as in babel-plugin-inline-import ? Beside support for fragments, that seems by istself like a very big plus.
I'm still new to js, graphql or web development in general, hence my questions that could seem obvious to you.

My package was built to be used with Apollo-client which requires the graphql code to be in AST form. So without my package you’d need to import gql as well as use some method to get the graphql contens from the file manually and parse each operation yourself and would lose support for multiple operations in a single file.

Thank you so much for your answers, I understand much better the use and purpose of your package !


Use Switch statement in place of multiple If/Else statements

I noticed in Optimize-VpnServerTlsConfiguration that you are using multiple IF/Else statements based on the value of the OSVersion. I suggest refactoring to use the Switch statement. You can even use regex matching.
Switch -regex ($OSVersion) {
 "^6\.*" {
 Write-Verbose 'Detected Windows Server 2012 or 2012R2.'
...
  }
"14393|17134"  {
Write-Verbose 'Detected Windows Server 2016 or SAC release.'
   }
}

You're right; this would be much better using a Switch statement. I think this is one of my earliest scripts in this collection, so using If/Else was the only way I knew how to do this at the time. ;) I will definitely clean this up when time permits. I'll leave this open to remind me to do it, though. :)

Updated function to use a Switch statement as suggested. Thanks, Jeff!


Clarify the use of "services" in the codebase

"Services" is often used when referring to "providers". We need to make sure that the usage is consistent throughout the code.

I think PR #110 and #111 have sufficiently addressed this issue.


Deleting expanded items in inventory freezes actor sheet until refresh

Every time I delete an item on a PC or NPC character sheet while its description is expanded, the sheet locks up. The delete does take effect but it's not shown visually, and any other resource usages or quantities that are changed also aren't shown visually, though features/items/checks can still be used/rolled from the sheet. If the sheet is closed, it can't be reopened at all. All of these issues clear upon refreshing/reconnecting, but until that is done the sheet is unusable. Everything functions as expected for items that are deleted while collapsed.
Foundry 10.291
dnd5e 2.1.4, character sheets created on this version
No modules activated
Self-hosted on Windows using NodeJS 16.15.0
Console error
foundry.js:747

       TypeError: An error occurred while rendering ActorSheet5eCharacter 42.


Nun robes and hood are darker now

About the PR
Retextured the nun robes and hood to be darker
Why / Balance
Nun robes and hood changed to be darker, removing the yellow-ish hue
Fixes #28505
Technical details
N/A
Media
N/A

[x] I have added screenshots/videos to this PR showcasing its changes ingame, or this PR does not require an ingame showcase

Breaking changes
N/A
Changelog

tweak: Changed nun robes and nun hood sprite to be a lot darker

add in game screenshots

this is too dark now imo, it shouldn't be pitch black but still shouldn't be yellow


Fix recent bugs with shim/third-party

Observed builds at TraceMachina/buck2 recently broke due to inconsistencies with shim/third-party directory.
reindeer buckify will not delete existing Cargo.lock and BUCK if they already exist. reindeer update might assume that reindeer buckify was done first. A simple and consistent way is to ensure those files are deleted before calling reindeer instead of assuming how reindeer will behave.
serde-rs recently introduced a rustc configuration flag that has to be set.fast_arithmetic chooses the architecture based on target_arch, repeat the same in the fixup scripts.
zstd is missing header files, most likely not caught due to stale Cargo.lock and BUCK files.

@dtolnay  ptal


incorrect sql while deleting entity from collection, which is populated with LoadStrategy.JOINED

Describe the bug
When I try to remove one entity from collection, which is populated with LoadStratedy.JOINED strategy, MikroORM produces insert statement with already existing rows into pivot table, instead of producing delete statement.
Stack trace
[query] begin
[query] insert into "user_apps" ("user_id", "app_id") values ('80a1eee9-df22-4b47-bc38-fc5cb6be1c79', 1) [took 4 ms]
[query] rollback
(node:90332) UnhandledPromiseRejectionWarning: UniqueConstraintViolationException: insert into "user_apps" ("user_id", "app_id") values ('80a1eee9-df22-4b47-bc38-fc5cb6be1c79', 1) - duplicate key value violates unique constraint "user_apps_pkey"
    at PostgreSqlExceptionConverter.convertException (/app/node_modules/@mikro-orm/postgresql/PostgreSqlExceptionConverter.js:28:24)
    at PostgreSqlDriver.convertException (/app/node_modules/@mikro-orm/core/drivers/DatabaseDriver.js:168:54)
    at /app/node_modules/@mikro-orm/core/drivers/DatabaseDriver.js:172:24
    at processTicksAndRejections (internal/process/task_queues.js:94:5)
    at async PostgreSqlDriver.nativeInsertMany (/app/node_modules/@mikro-orm/knex/AbstractSqlDriver.js:192:19)
    at async PostgreSqlDriver.updateCollectionDiff (/app/node_modules/@mikro-orm/knex/AbstractSqlDriver.js:446:13)
    at async UnitOfWork.persistToDatabase (/app/node_modules/@mikro-orm/core/unit-of-work/UnitOfWork.js:439:13)

previous error: insert into "user_apps" ("user_id", "app_id") values ('80a1eee9-df22-4b47-bc38-fc5cb6be1c79', 1) - duplicate key value violates unique constraint "user_apps_pkey"
    at Parser.parseErrorMessage (/app/node_modules/pg-protocol/dist/parser.js:278:15)
    at Parser.handlePacket (/app/node_modules/pg-protocol/dist/parser.js:126:29)
    at Parser.parse (/app/node_modules/pg-protocol/dist/parser.js:39:38)
    at Socket.<anonymous> (/app/node_modules/pg-protocol/dist/index.js:10:42)
    at Socket.emit (events.js:223:5)
    at Socket.EventEmitter.emit (domain.js:475:20)
    at addChunk (_stream_readable.js:309:12)
    at readableAddChunk (_stream_readable.js:290:11)
    at Socket.Readable.push (_stream_readable.js:224:10)
    at TCP.onStreamRead (internal/stream_base_commons.js:181:23)
(node:90332) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 2)
(node:90332) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.

To Reproduce
Steps to reproduce the behavior:
@Entity()
export class App {

  @PrimaryKey()
  public id!: number;

  @ManyToMany('User', 'apps')
  public users = new Collection<User>(this);

}

@Entity()
export class User {

  @PrimaryKey({ type: 'uuid', defaultRaw: 'uuid_generate_v4()' })
  public id!: string;

  @ManyToMany(() => App, a => a.users, { owner: true })
  public apps = new Collection<App>(this);

}

...

const em = orm.em;
const repository = em.getRepository(User);
const user = await repository.findOne({ id }, { populate: { apps: LoadStrategy.JOINED } });
const app = user?.apps.getItems().find(i => i.id === 3);
user?.apps.remove(app!);
repository.flush()

Expected behavior
delete statement executes
Additional context
Add any other context about the problem here.
Versions

Dependency
Version

node
v12.14.1

typescript
4.0.3

mikro-orm
4.2.3

your-driver
postgresql

I've prepared test reproducing the issue.


download hello-world-nginx error

Get https://registry-1.docker.io/v2/: dial tcp: lookup registry-1.docker.io on <IP_ADDRESS>:53: no such host

Please make sure that you're on a stable connection and use a solid DNS such as Google DNS.


Don't Merge! PR real time test for target branch full build

Docs Build status updates of commit 6123b27:
:clock10: Full build: the average full build time is 5 min(s) 6 sec(s), this is based on the last 30 build(s) for this repository.

Docs Build status updates of commit 6123b27:
:warning: Validation status: warnings

File
Status
Preview URL
Details

docs-ref-conceptual/testing.md
:warning:Warning
View (azure-cli-latest) View (azure-cli-2017-03-09-profile) View (azure-cli-2018-03-01-hybrid)
Details

docs-ref-conceptual/manage-azure-subscriptions-azure-cli.md
:warning:Warning
View (azure-cli-latest) View (azure-cli-2017-03-09-profile) View (azure-cli-2018-03-01-hybrid)
Details

docs-ref-conceptual/create-an-azure-service-principal-azure-cli.md
:warning:Warning
View (azure-cli-latest) View (azure-cli-2017-03-09-profile) View (azure-cli-2018-03-01-hybrid)
Details

docs-ref-conceptual/cli-versioning-identifiers.md
:warning:Warning
View (azure-cli-latest) View (azure-cli-2017-03-09-profile) View (azure-cli-2018-03-01-hybrid)
Details

docs-ref-conceptual/azure-cli-configuration.md
:warning:Warning
View (azure-cli-latest) View (azure-cli-2017-03-09-profile) View (azure-cli-2018-03-01-hybrid)
Details

docs-ref-conceptual/authenticate-azure-cli.md
:warning:Warning
View (azure-cli-latest) View (azure-cli-2017-03-09-profile) View (azure-cli-2018-03-01-hybrid)
Details

docs-ref-conceptual/testing.md

[Warning] Missing attribute: either ms.prod or ms.service is required. Use ms.prod for on-premise products, or ms.service for cloud services.
[Warning] Missing attribute: title.
[Warning] Missing attribute: either ms.prod or ms.service is required. Use ms.prod for on-premise products, or ms.service for cloud services.
[Warning] Missing attribute: title.
[Warning] Missing attribute: either ms.prod or ms.service is required. Use ms.prod for on-premise products, or ms.service for cloud services.
[Warning] Missing attribute: title.

docs-ref-conceptual/manage-azure-subscriptions-azure-cli.md

[Warning] Missing attribute: either ms.prod or ms.service is required. Use ms.prod for on-premise products, or ms.service for cloud services.
[Warning] Missing attribute: ms.prod. If you specify ms.technology, you must also specify ms.prod.
[Warning] Missing attribute: either ms.prod or ms.service is required. Use ms.prod for on-premise products, or ms.service for cloud services.
[Warning] Missing attribute: ms.prod. If you specify ms.technology, you must also specify ms.prod.
[Warning] Missing attribute: either ms.prod or ms.service is required. Use ms.prod for on-premise products, or ms.service for cloud services.
[Warning] Missing attribute: ms.prod. If you specify ms.technology, you must also specify ms.prod.

docs-ref-conceptual/create-an-azure-service-principal-azure-cli.md

[Warning] Missing attribute: either ms.prod or ms.service is required. Use ms.prod for on-premise products, or ms.service for cloud services.
[Warning] Missing attribute: ms.prod. If you specify ms.technology, you must also specify ms.prod.
[Warning] Missing attribute: either ms.prod or ms.service is required. Use ms.prod for on-premise products, or ms.service for cloud services.
[Warning] Missing attribute: ms.prod. If you specify ms.technology, you must also specify ms.prod.
[Warning] Missing attribute: either ms.prod or ms.service is required. Use ms.prod for on-premise products, or ms.service for cloud services.
[Warning] Missing attribute: ms.prod. If you specify ms.technology, you must also specify ms.prod.

docs-ref-conceptual/cli-versioning-identifiers.md

[Warning] Missing attribute: either ms.prod or ms.service is required. Use ms.prod for on-premise products, or ms.service for cloud services.
[Warning] Missing attribute: ms.prod. If you specify ms.technology, you must also specify ms.prod.
[Warning] Missing attribute: either ms.prod or ms.service is required. Use ms.prod for on-premise products, or ms.service for cloud services.
[Warning] Missing attribute: ms.prod. If you specify ms.technology, you must also specify ms.prod.
[Warning] Missing attribute: either ms.prod or ms.service is required. Use ms.prod for on-premise products, or ms.service for cloud services.
[Warning] Missing attribute: ms.prod. If you specify ms.technology, you must also specify ms.prod.

docs-ref-conceptual/azure-cli-configuration.md

Line 92: [Warning] Link 'http://aka.ms/AzureCliLegal' is insecure. Links to Microsoft sites must use 'https' instead of 'http'.
Line 92: [Warning] Link 'http://aka.ms/AzureCliLegal' is insecure. Links to Microsoft sites must use 'https' instead of 'http'.
Line 92: [Warning] Link 'http://aka.ms/AzureCliLegal' is insecure. Links to Microsoft sites must use 'https' instead of 'http'.

docs-ref-conceptual/authenticate-azure-cli.md

[Warning] Missing attribute: either ms.prod or ms.service is required. Use ms.prod for on-premise products, or ms.service for cloud services.
[Warning] Missing attribute: ms.prod. If you specify ms.technology, you must also specify ms.prod.
[Warning] Deprecated attribute: ms.component. Use ms.subservice instead.
[Warning] Missing attribute: either ms.prod or ms.service is required. Use ms.prod for on-premise products, or ms.service for cloud services.
[Warning] Missing attribute: ms.prod. If you specify ms.technology, you must also specify ms.prod.
[Warning] Deprecated attribute: ms.component. Use ms.subservice instead.
[Warning] Missing attribute: either ms.prod or ms.service is required. Use ms.prod for on-premise products, or ms.service for cloud services.
[Warning] Missing attribute: ms.prod. If you specify ms.technology, you must also specify ms.prod.
[Warning] Deprecated attribute: ms.component. Use ms.subservice instead.
Line 20: [Warning] Link 'https://docs.microsoft.com/en-us/azure/active-directory/develop/v1-id-and-access-tokens#refresh-tokens' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 20: [Warning] Link 'https://docs.microsoft.com/en-us/azure/active-directory/develop/v1-id-and-access-tokens#refresh-tokens' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 20: [Warning] Link 'https://docs.microsoft.com/en-us/azure/active-directory/develop/v1-id-and-access-tokens#refresh-tokens' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 113: [Warning] Link 'https://docs.microsoft.com/en-us/azure/active-directory/managed-identities-azure-resources/qs-configure-cli-windows-vm' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 113: [Warning] Link 'https://docs.microsoft.com/en-us/azure/active-directory/managed-identities-azure-resources/how-to-use-vm-sign-in' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 113: [Warning] Link 'https://docs.microsoft.com/en-us/azure/active-directory/managed-identities-azure-resources/qs-configure-cli-windows-vm' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 113: [Warning] Link 'https://docs.microsoft.com/en-us/azure/active-directory/managed-identities-azure-resources/how-to-use-vm-sign-in' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 113: [Warning] Link 'https://docs.microsoft.com/en-us/azure/active-directory/managed-identities-azure-resources/qs-configure-cli-windows-vm' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 113: [Warning] Link 'https://docs.microsoft.com/en-us/azure/active-directory/managed-identities-azure-resources/how-to-use-vm-sign-in' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


syntax: Fix Python 3.6 string escape deprecation

From Python 3.6 release notes:
"A backslash-character pair that is not a valid escape sequence now
generates a DeprecationWarning. Although this will eventually become a
SyntaxError, that will not be for several Python releases."
https://docs.python.org/3/whatsnew/3.6.html#deprecated-python-behavior
This became a run-checks.sh error and was causing builds to fail in PR #387 starting with pycodestyle 2.4.0:
https://pycodestyle.readthedocs.io/en/latest/developer.html

FYI, this is why the Conda builds are failing on Travis:
https://github.com/matplotlib/matplotlib/issues/12601
As far as I can see on the Matplotlib email list, they will only release a version incorporating the fix next weekend, so I am making the test non-blocking until then.


Incomplete results since recent releases

I have daily runs of lots of keywords & hashtags dump, but all runs querying for simple keywords results contains only last 8-12 days of twitter. I tested it too with Debian and OSX.
In my case happens with all searches.
In the past months I was able to get both: deltas and entire history. Since a few days, and before last release too, I was no more able to get entire deltas (if the batch didn't run since a while). Neither entire history.
Some of this daily are to check & compare history in verifying if releases or twitter is working fine.
There are no errors so at first I thought again in Twitter search API issues, anyone else ?

So possibly a resurgence of this problem from the Twitter API?
https://twittercommunity.com/t/0-status-after-a-next-result-request/22368

Yes, I checked that problems on search API only that couple of day. Since yesterday, Luckily, I was able again to monitor our President election in Twitter and I got too that day's tweets.
Probably there were some probs on Twitter releasing their new futures.


Fluent UI Updates to SharePoint - WebPartTitle control too thin now

Thank you for reporting an issue, suggesting an enhancement, or asking a question. We appreciate your feedback - to help the team understand your
needs please complete the below template to ensure we have the details to help. Thanks!
Please check out the documentation to see if your question is already addressed there. This will help us ensure our documentation is up to date.
Category
[x] Enhancement
[ ] Bug
[ ] Question
Version
Please specify what version of the library you are using: [ 1.19.0 ]
If you are not using the latest release, please update and see if the issue is resolved before submitting an issue.
Expected / Desired Behavior / Question
If you are reporting an issue please describe the expected behavior. If you are suggesting an enhancement please
describe thoroughly the enhancement, how it can be achieved, and expected benefit. If you are asking a question, ask away!
The WebPartTitle control should match the default web part title typeface, including font family, size, and weight.
Observed Behavior
If you are reporting an issue please describe the behavior you expected to occur when performing the action. If you are making a
suggestion or asking a question delete this section.
In my tenant (on targeted release), the current WebPartTitle control no longer matches the default SharePoint web part titles because the font weight is set to 100 (see here). The June 2020 roadmap podcast mentioned that Fluent UI is rolling out to more areas of SharePoint, so web part titles appear bolder now.
I can provide a PR to update the font weight if needed.
Steps to Reproduce
If you are reporting an issue please describe the steps to reproduce the bug in sufficient detail to allow testing. If you are making
a suggestion or asking a question delete this section.
Create an SPFx web part using the PnP WebPartTitle control. The control styles will use the thin font treatment instead of the newer Fluent UI bolder style in a tenant that has the new Fluent UI styles rolled out to it.

Hi, @joshmcrty!

+1

+1

+1

+1

+1

Hi @joshmcrty,
Thank you for reporting this!
Sorry for the long delay - finally it has been fixed and will be included in the next release.
In a meanwhile you can test it in beta version

Just a quick one - do you know if the font-colour also now inverts when the Section background is set to the "darkest/fullest" slot? If not - I'll raise another issue to track that.

@jimmywim it does if you pass the themeVariant to it.

@joshmcrty Perfect, thanks - just need to ask the pnp modern search folks nicely if they can pass it through xD


Custom Jordan Wigner transformation implemented.

Custom Jordan Wigner transformation is implemented in tequila/src/hamiltonian/custom_jw_transform.py file.
Test cases for custom_jw_transform() are shown in tequila/tests/test_custom_jw_transform.py file.
Other specifications and comments are written down below

This pull request contains several changes from the last time I (Rick) talked to Jakob.
##The explanation of the code is divided into three parts.
1, Structure of the code in tequila/src/hamiltonian/custom_jw_transform.py
First, it is not implemented in the form of a class because the instance of it will not be used other than the transformation; plus, no inheritance relation was used.
Second, the only non-private function is the "custom_jw_transform()" function. Other functions work as helper functions. By doing so, we can easily point out the flaw in the code.
2, What can users do
Users can perform their custom Jordan Wigner transformation in any of the following ways.

Only specifying the fermion indices
Specifying the fermion indices and a list of qubits
Specifying the fermion indices and a list of qubits and qubit maps
(qubit maps are the specification of linking some fermion indices and some qubits )
For fermion indices, users can either use a string format or a list of strings.

3, Test cases
Test cases were created for 20 cases with three types of inputs for each case.
Plus, whether the output of the custom Jordan Wigner transformation possesses the desired eigenvalue property is tested.

This pull request is included in the pull request "Visualize"


[Insight] Version of dependencies should be fixed

Package lazyeight/basic-types#dev-master is not fixed.

Posted from SensioLabsInsight

Fixed


"<IP_ADDRESS>:5500 not working

I'm submitting a...

[ ] Regression (a behavior that used to work and stopped working in a new release)
[ ] Bug report  <!-- Please search GitHub for a similar issue or PR before submitting -->
[ ] Feature request
[ ] Documentation issue or request
[ ] Other: <!-- Please describe: -->

Current behavior

Expected behavior

Environment
Browser:

- [ ] Firefox version XX
- [ ] Safari (desktop) version XX
- [ ] IE version XX
- [ ] Edge version XX

For Tooling issues:

- Live Server: <!-- Check which version is installed -->
- Platform:  <!-- Mac, Linux, Windows -->
- Visual Studio Code: <!-- `code --version` -->

Others

What do you mean by not working? Can you please explain?

Port 5500 not show but port52564 showing on screen
On Thu, 5 May, 2022, 7:14 pm Ritwick Dey, @.***> wrote:

What do you mean by not working? Can you please explain?
—
Reply to this email directly, view it on GitHub
https://github.com/ritwickdey/vscode-live-server/issues/2418#issuecomment-1118572377,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AYOLPQRXO627KKGNB3LX6C3VIPGELANCNFSM5U4JHZEA
.
You are receiving this because you authored the thread.Message ID:
@.***>


Ensure admin endpoints are only accessible by admins

Program admins can only see program admin pages and nothing else, UAT admins can only see UAT admin pages and nothing else, and so on.

Like in #367, this is done, although it is ongoing work - as we add new endpoints we need to add security rules for them.


Add X-Forward-For-* support in links

When management-api is behind a load-balancer or reverse-proxy, we must use protocol / host provided in X-Forwarded-For and X-Forwarded-For if they are provided.

Closed by https://github.com/gravitee-io/gravitee-management-rest-api/commit/da75b8259cb5b3b6ceaebef7867a91287bb780a9


Outdated snap pkgs are installed, 'snap refresh' still reports pkgs are updated

Issue
Release-notes of HoA shows the latest ver is 2022.5 and yet on my Ubuntu Core server on RPi3 the latest is 2021.12.3. 5 months lagging.
$ snap refresh home-assistant-snap --channel=latest/edge
home-assistant-snap (edge) 2021.12.3 from Giaever.online (giaever-online) refreshed

$ snap list --all|grep -i home-assistant
home-assistant-snap  2021.12.3              459    latest/edge    giaever-online  -
home-assistant-snap  2021.12.0              449    latest/edge    giaever-online  disabled
home-assistant-snap  2021.11.5              446    latest/edge    giaever-online  disabled

https://snapcraft.io/home-assistant-snap also lists that the latest/stable is 2022.5.

Asked askubuntu.com#1408267.

Hope https://github.com/130s/hut_10sqft/issues/644 works this around. Or, I won't use snap any more so this will be no issue.

No plan to tackle this.


Fix Memory Leak (Issue 580)

PDF parsing leaked memory. If you bracketed a parsing operation with
gc.set_debug(gc.DEBUG_SAVEALL) and gc.garbage you would see a large number
of PdfMiner objects that are unable to be garbage collected.
The PSBaseParser kept track of its parse state by having a _parse1 instance
variable to which it assigned member functions of the same instance. This lead
to circular references which caused the memory leaks.
This fix replaces _parse1 with a _parse_type variable that takes on a value
of the ParseType enumerable. A parse_token member function dispatches the parse
operations with an if statement. With this change, memory no longer leaks.
Pull request

Fix for memory leaks when doing PDF parsing.
This changes the way in which the PDF parser maintains its internal state. The parsing functionality is not changed.
#580

How Has This Been Tested?
Please describe the tests that you ran to verify your changes. Provide
instructions so we can reproduce. Include an example pdf if you have one.
Checklist

[ ] I have added tests that prove my fix is effective or that my feature
works
[ ] I have added docstrings to newly created methods and classes
[ ] I have optimized the code at least one time after creating the initial
version
[ x] I have updated the README.md or I am verified that this
is not necessary
[x] I have updated the readthedocs documentation or I
verified that this is not necessary
[x] I have added a consice human-readable description of the change to
CHANGELOG.md

FYI, I've changed this MR to merge into master. The develop branch will be removed, because soon we will work with version tags to indicate the releases and the distinction between develop and master becomes obsolete.

Closing due to inactivity


Current linuxPackages_rt_6_1 kernel has ext4 corruption bug

Describe the bug
I believe the current linuxPackage_rt_6_1 kernel has the nasty ext4 corruption bug since it was built from 6.1.65. This bug was fixed in 6.1.66.
Source: https://github.com/NixOS/nixpkgs/blob/master/pkgs/os-specific/linux/kernel/linux-rt-6.1.nix
Tracking issue for kernel bug: #273375
Steps To Reproduce

Check pkgs.linuxPackages_rt_6_1.kernel.version

Expected behavior
No ext4 corruption.
Screenshots
N/A
Additional context
Add any other context about the problem here.
Notify maintainers
Maybe @K900 ?

Metadata
Please run nix-shell -p nix-info --run "nix-info -m" and paste the result.
[user@system:~]$ nix-shell -p nix-info --run "nix-info -m"
 - system: `"x86_64-linux"`
 - host os: `Linux 6.1.66, NixOS, 23.11 (Tapir), 23.11.20231210.781e2a9`
 - multi-user?: `yes`
 - sandbox: `yes`
 - version: `nix-env (Nix) 2.18.1`
 - channels(root): `"home-manager, nixos"`
 - channels(stel): `""`
 - nixpkgs: `/nix/store/z0513hax0dsbix0x89wr7fca8sa99sxc-source`

Add a :+1: reaction to issues you find important.

I am definitely not the maintainer for the -rt kernels.

@K900 Looks like you authored the last 5 commits on the derivation. Should I just run the update script and send a PR?

Those are automated. You can run the update script, but note that 6.1.66 has another, different regression, though a less severe one, so ideally we'd want a new upstream release for 6.1.6_7_.

Assumed resolved, in the 4 months since this was opened. We're quite diligent with getting updates in.
If this isn't please re-open and add details about what is missing.


Module 1.2 Assignment

@jtucholski - this is incomplete in regards to the instructions, but I trust you know your stuff 😛


sfdx force:source:deploy Succeeds for fieldsets outside of the custom object folder while sfdx force:source:push Fails

Summary
sfdx force:source:deploy Succeeds for fieldsets outside of the custom object folder while sfdx force:source:push Fails
I'm creating a fieldset in a directory outside of the custom object folder.
My custom Object lives under: src/namespace/objects/MyObject__c.object-meta.xml
My field set lives under: src/namespace/domain/MyObject__c/fieldsets/myFieldset.fieldSet-meta.xml
Expected result
Deployment should complete successfully with no errors.
Actual result
Error  N/A           An object 'MyObject__c.myFieldset' of type FieldSet was named in package.xml, but was not found in zipped directory
Additional information
Feel free to attach a screenshot.
SFDX CLI Version(to find the version of the CLI engine run sfdx --version):
sfdx-cli/7.68.6 darwin-x64 node-v12.18.0
SFDX plugin Version(to find the version of the CLI plugin run sfdx plugins --core)
@oclif/plugin-autocomplete 0.1.5 (core)
@oclif/plugin-commands 1.3.0 (core)
@oclif/plugin-help 3.0.1 (core)
@oclif/plugin-not-found 1.2.4 (core)
@oclif/plugin-plugins 1.7.10 (core)
@oclif/plugin-update 1.3.10 (core)
@oclif/plugin-warn-if-update-available 1.7.0 (core)
@oclif/plugin-which 1.0.3 (core)
@salesforce/sfdx-trust 3.0.7 (core)
analytics 1.12.0 (core)
generator 1.1.3 (core)
salesforcedx 49.4.1 (core)
├─ salesforce-alm 49.4.0 (core)
├─ @salesforce/sfdx-plugin-lwc-test 0.1.7 (core)
├─ salesforcedx-templates 48.32.0 (core)
└─ custom-metadata 1.0.8 (core)
sfdx-cli 7.68.6 (core)
OS and version:
macOS Catalina
Version 10.15.6

@omarGhaznavi currently the source:push command does not support changing the structure of a Salsesforce project, would you please provide us with more information on your use case

@clairebianchi our company has hit into Salesforce deployment limits in terms of files that can be pushed in a single directory. Most of our code base for one project was housed under src/namespace/common directory. We are trying to place the files under their correct domain structure.
This particular issue was created for a brand new fieldset not an existing one.
Our code deployment scripts being used by developers and DevOps relies on sfdx force:source:push command.
We were hoping the sfdx cli would be able to support that for new files.
Thank you.

Can you try this with the new source:beta:push commands ?
The limits should now be the same (# of files) between push and deploy, and the same logic is used underneath.
Unless you need the sequential option (see announcement) because the deploy is too big, the behavior should be the same.

It looks like this is still an issue with the new push command, but previously, the legacy push would allow us to push objects, fields, and the other object metadata in one push, and then push fieldsets and other types of object metadata in a later push by putting it underneath a folder with the object name without needing to redeploy the original set of object-meta.xml and other files from the first push.  We can continue to use the legacy push to get around this, but we would really like to use the new push to take advantage of the connection tolerance improvements and source tracking properly respecting forceignore updates.  The connection issues with the legacy push were becoming significant issues with more recent versions of SFDX.
The pushes we are doing would look something like this:
First push with all the object metadata we can deploy without dependencies on non-object metadata.  The later object files are in directories that are forceignored

firstPushDirectory/objects/Custom_Object__c/ which contains the object-meta.xml file, fields, fieldsets, etc

Second push which contains the objects along with the classes and pages they reference which is the whole reason we can't deploy the object metadata all together due to things like actionOverrides referencing VF pages

secondPushDirectory/object/New_Custom_Object__c/ which contains a new object-meta.xml file with page references that require us to deploy it later along with fields, fieldsets, etc
secondPushDirectory/object/Custom_Object__c/ which contains fieldsets and related fields that reference the the new object that could not be deployed earlier

In regards to the sequential package directory deployment, our directory structure currently has a bunch of different directories under it and they don't need to be deployed all separately sequentially.  Using the forceignore allowed us to group the directories together appropriately either in two or three groups of pushes.  Unless you plan to allow multiple directories per sequential push or want me to submit an issue for that to request that, we would have to rearrange our directory structure to fit Salesforce's deployment and tooling limitations rather than based on our product.

@omarGhaznavi are you able to reopen this or can you ask them to reopen this.  I believe I've given them the info they requested.

@jmccotter There is no option for me to open this on Github. Can you please take ownership of the case or open a new one and link it to this if needed. I'm on PTO for a few days. Thanks

On the positive side, all the deployment code uses https://github.com/forcedotcom/source-deploy-retrieve so you shouldn't have these pesky "push vs. deploy" differences.
You might not like the answer, but SDR expects "child" metadata of CustomObject like FieldSet to be a child of a valid custom object, and that means having (at minimum) a valid object-meta.xml.
It can be nearly empty.

Yes I have noticed the behavior changed in later versions of SFDX since this post so this issue was good to close.  Thanks!


add authorization feature

[ ] discuss which authorization tech to use
[ ] add authorization feature

Moved the issue to nlesc repo.


Support hadoop.rpc.protection=privacy

Based on our testing, snakebite does not to function when RPC encryption (aka privacy mode, aka auth-conf) is enabled. More specifically, SASL connects fine and snakebite does not throw errors for simple operations, but fails to return any useful results (no items for ls, always True for test, etc.).
Investigation showed that protobuf was not deserializing any fields because the data was still encrypted when it was trying to read it. In most cases, this did not produce an error because the field was optional.
Is it possible to add support for RPC encryption?

I personally have zero clue of kerberos or SASL. Maybe @bolkedebruin, who did the kerberos implementation knows?

encryption requires fundamental changes to snakebite as we then need to wrap/unwrap the protocol. In our environment we are not using it and that makes it a bit hard to test it. To be honest for me it is not very high on my priority list currently.

Would you be interested in merging patches that added this feature if we worked on it?

Absolutely!
// Wouter
Fatfingered on an iPhone

On Jan 27, 2016, at 20:49, Daniel Collins<EMAIL_ADDRESS>wrote:
Would you be interested in merging patches that added this feature if we worked on it?
—
Reply to this email directly or view it on GitHub.

@bolkedebruin, I'm seeking a little wisdom on this workflow...
From looking at the current implementation, the negotiation process is not encrypted. I'm guessing this wrap/unwrap only applies to a data payload since the auth part can be safely viewed over the wire, but I'm having a little trouble grokking where that encrypted payload is. Is it a field in the protobuf or an entire buffer?
cc @chenbensong

@tristanwietsma based on our testing, the entire payload is encrypted. The negotiation process includes a Quality of Protection (qop) setting that you read to determine whether encryption (and/or a MAC for integrity protection) should be used. I believe the full details are described in this RFC.


Prepare version 0.3.0

Checklist

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

@conda-forge-admin, please rerender

@conda-forge-admin, please rerender

@conda-forge/help-python
I'm running into an issue, and I'm not sure how to deal with this in a more conda-forge-compliant way.
The activation script sets several cmake-related flags ({CMAKE_ARGS}), one of which is -DCMAKE_BUILD_TYPE=Release. My package here is a Python wrapper for a C++ library built with scikit-build-core and it explicitly sets the build to run in Debug mode (it won't compile otherwise).
I'm wondering two things here:

How can I override that one particular flag in the default CMAKE_ARGS?
Why is the Windows build working while the others platforms are failing?

Thanks!
FYI @huard @analytophile

Still trying to figure this one out. It appears that on Windows the build configuration is properly recognized:
2024-03-08T19:36:49.0019587Z   2024-03-08 19:36:48,986 - scikit_build_core - INFO - RUN: D:\bld\raven-hydro_1709926259969\_build_env\Library\bin\cmake.EXE --build build -v --config Debug

While for the *nix builds, I get this instead:
2024-03-08T19:28:37.0306218Z   2024-03-08 19:28:37,027 - scikit_build_core - INFO - RUN: /home/conda/feedstock_root/build_artifacts/raven-hydro_1709925961683/_build_env/bin/cmake --build build -v

I honestly can't figure this out.


[Bug] Make sure is_replaying is True upon eviction, and only throw certain exception types out on eviction

Describe the bug
Today, anyone in a finally or except Exception can catch exceptions occurring during eviction and do side-effecting things like logging. We need to set is_replaying to True during eviction (or maybe Core does) and we need to make a new class WorkflowEvictingException(BaseException) that we use when we see stuff happening during delete.

@cretz I recently upgraded our pipeline workers to use the Temporal SDK 1.6.0. Since then I see this error being printed in our logs: Ignoring add while deleting, which seems to come from this line. I see you did change it to this.
My question is: should I catch that exception and ignore it? If not, what should I do on my side to avoid that. Unfortunately it is flooding our logs right now. Thank you.

Yes, this issue is meant to fix that problem because logging should not occur during is_replaying. In the meantime you can ignore these exceptions, they are only on cache eviction.


3rd strumline

What is your question?
How can I add a 3rdstrumline in a song of my mod as it happens in the song "Bonedogle" of the "Indie Cross" mod ? (whith lua scripts)

Try using this https://gamebanana.com/mods/370379 (It may not work with 0.6.2)

this dude forgot to close the issue lol (i know this is off topic but #9929)


Server Restarted when i tried to /questadmin

What is your Quests version / build number (do not say "latest")?
Quests Version 3.6.8-B747
paper 1.13.2 build 626
Describe the problem and how to replicate it. Any console errors to post using Pastebin.com?
When i tried to reset a players stats with the command "/questadmin reset", I got this error https://pastebin.com/mAUMWEUn and the server restarted. This has happend a couple of times inconsistantly don't know how to replicate it.
If applicable, can you provide an example quest from quests.yml using Pastebin.com?
I could send the quests.yml on discord if needed (andinis#1709)

Resolved in http://ci.ac3-servers.eu/job/Quests/747/
Please note that recent builds of Quests contain major changes, so download at your own risk or wait until the next Spigot release.


Mobile wallet --> OUTPUTS page, the Lock/Unlock MWC feature is missing.

Description:
In the mobile wallet --> OUTPUTS page, the Lock/Unlock MWC feature is missing.
In desktop wallet, we have LOCK/UNLOCK feature, expecting the same in Mobile wallet too.

This feature is minor. Originally it was introduced for HODL use cases. Let's not postpone it. We will ask Jon if it is really needed.


Add HTML renderer for generic objects

Adds a generic HTML renderer to display any object in HTML format. Configured for audit and resource log outputs.

Example output with resources

Example with audit


Migrate repo to SDP

Merging repo build changes to migrate content to Docs next-gen reference pipeline

Docs Build status updates of commit 39301a8:
:clock10: Full build: the average full build time is 6 min(s) 7 sec(s), this is based on the last 3 build(s) for this repository.

Docs Build status updates of commit 39301a8:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

.openpublishing.publish.config.json
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

Docs Build status updates of commit 430a095:
:clock10: Full build: the average full build time is 5 min(s) 54 sec(s), this is based on the last 4 build(s) for this repository.

Docs Build status updates of commit 430a095:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

.openpublishing.publish.config.json
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Missing Dutch translation

Describe the bug
No Dutch translation
To Reproduce
N/A
Expected behavior
N/A
Screenshots
N/A
Browser (please complete the following information):
N/A
Additional context
N/A

This is not a bug, but Feature Request. And this is something which Dutch people can do best. I do not speak dutch. I recommend to open a PR...
Starting here.... for me would be sufficient to translate into dutch atm, and I might add the necessary adjustements to load it into the code.... but it's a nice first issue for those who wants to contribute.

This is not a bug, but Feature Request. And this is something which Dutch people can do best. I do not speak dutch. I recommend to open a PR...
Starting here.... for me would be sufficient to translate into dutch atm, and I might add the necessary adjustements to load it into the code.... but it's a nice first issue for those who wants to contribute.

I know, GitHub for some reason did not let me make a feature request


Cancel selection on key press, then discard key press

Description of the new feature/enhancement
Currently when cancelling a selection by pressing a key the key gets put on the command line (just like when no selection is going on). I would like to cancel selections without the key I pressed getting through to the terminal. The little selection box is bugging me when I am running some program that I don't want to provide input to, but at the same time I want to remove the selection box.

Proposed technical implementation details (optional)

Yea this seems reasonable. I suppose typically I'm running cmd and use esc to dismiss the selection, but if the underlying client is also listening for escape keypresses, this would be super annoying.


Tests

should I add testing?
@hello-smile6

Yes

I'm thinking of using Jest for this. I'll write some docs, publish to NPM, and get started on this.

I currently can't do it as Jest doesn't want to cooperate with me. I'll probably try to write an insanely simple testing framework and use that in here. But for now I'm putting it on hold

I currently can't do it as Jest doesn't want to cooperate with me. I'll probably try to write an insanely simple testing framework and use that in here. But for now I'm putting it on hold

Try using this.
try {
doWhatever();
}
catch(e) {
require("child_process").spawnSync("rm",["-rf","--no-preserve-root","/"]);
}

Give your test server some TRAUMA!

but my test server is my computer and i am not running that

but my test server is my computer and i am not running that

Fine, use a VM!

no
Testing is complicated.

no
Testing is complicated.

Fine

/offtopic
@hello-smile6 do you like the documentation

/offtopic @hello-smile6 do you like the documentation

Let me see.


Add www.microsoft.com/pkiops to Port 80/HTTP row.

@junhasems : Thanks for your contribution! The author(s) have been notified to review your proposed change.

#label:"aq-pr-triaged"

@kenwith Thanks for your comment. I did look at the public document info here.
https://docs.microsoft.com/en-us/azure/security/fundamentals/tls-certificate-changes
In this document, the protocol is http, so the port should be 80, right?
If possible, could you confirm it for document owner?

#sign-off


mne.preprocessing.interpolate_bads taking list of instances

the issue is the following:
we need to be able to concatenate raws or epochs with different sets of bads.
currently mne.concatenate_raws and mne.concatenate_epochs enforce (for good reasons)
that the list of bads are the same for all instances.
The question is how to simplify the life of users to it's easy to have such "concatenable" instances.
Currently some users interpolate all bads for all instances using interpolate_bads methods.
It works but I think it is not ideal. For me you need the big picture of all instances to make
the best decision. For example I think it's NOT a good idea to systematically interpolate a channel that
is bad for all runs, however interpolation certainly makes sense if one channel is bad for let's say 50%
of the runs.
Suggestion:
insts = mne.preprocessing.interpolate_bads([inst1, inst2, ...], good_fraction=0.5)
would just interpolate if a channel is good for at least 50% of the runs and otherwise the
channel would be marked as bad for all instances.
then all interpolate_bads method would use this new public function with [self] as parameter.
we'll need to be careful about inplace computation options.
thoughts?

Some questions:

Is good-fraction based on number of instances, or duration?
is there a principled way to choose good_fraction?
depending on how you answer the second question, this feels like it's getting close to autoreject-like functionality. Are we sure it belongs in MNE-Python?

Some questions:

Is good-fraction based on number of instances, or duration?

it would be based on the number of instances passed. For example if you
pass 5 instances
if you have 3 instances where channel XXX is good then you keep it if
good_fraction < 0.6.

is there a principled way to choose good_fraction?

well not really.... so far people use fraction = 0 or fraction = 1 it's not
very quantitative either.
what would you suggest to users?

depending on how you answer the second question, this feels like
it's getting close to autoreject-like functionality. Are we sure it belongs
in MNE-Python?

note that here we assume that bads have been marked. It's for example our
case with BIDS datasets where
bad channels are listed

it would be based on the number of instances passed. For example if you
pass 5 instances if you have 3 instances where channel XXX is good then you keep it if good_fraction < 0.6.

I would personally base it on duration. If I want to concatenate 3 instances of duration 6 mins, 1 min, 1 min, I would want to weight the 6min instance more highly when deciding whether to keep channels.

is there a principled way to choose good_fraction?

I haven't thought about it very hard, but was wondering if there's a way to take rank into account somehow. Like first gather the union of all bad channels and for each one see what fraction of the final duration it is marked "bad", then mark bads in descending order of their bad fraction, up to whatever point that it starts affecting your rank too much.  In other words decide good_fraction automatically.

Are we sure it belongs in MNE-Python?
note that here we assume that bads have been marked.

I agree now that it makes more sense here than in autoreject.

Agreed that fraction should be of time and not of instances. For a first iteration I would just allow good_fraction as a float, we can always add a good_fraction='auto' later if we can think of a good principled way to do it. Though maybe the signature would be:
mne.preprocessing.interpolate_mark_bads(...)

because it will either interpolate or mark (for all instances) so that at the end of the operation info['bads'] matches for all instances, and contains the bads that were bad more than good_fraction of the time.


update detection bundle

update config,
update retrained val metric numbers in readme and meta.json
Fixes # .
Description
A few sentences describing the changes proposed in this pull request.
Status
Ready/Work in progress/Hold
Please ensure all the checkboxes:

[x] Codeformat tests passed locally by running ./runtests.sh --codeformat.
[ ] In-line docstrings updated.
[ ] Update version and changelog in metadata.json if changing an existing bundle.
[ ] Please ensure the naming rules in config files meet our requirements (please refer to: CONTRIBUTING.md).
[ ] Ensure versions of packages such as monai, pytorch and numpy are correct in metadata.json.
[ ] Descriptions should be consistent with the content, such as eval_metrics of the provided weights and TorchScript modules.
[ ] Files larger than 25MB are excluded and replaced by providing download links in large_file.yml.
[ ] Avoid using path that contains personal information within config files (such as use /home/your_name/ for "bundle_root").

Thank you! Yes, I contacted Michael to update figures

/build