DB: Migration support and Schema

Already added migration support and schema but that may not be the most appropriate way to handle things.
alter it so that schema is ignored by the app, just filled by a dump from postgresql
May be nicer to clean it a bit so that it get readable.
Thus upon first launch, read all migrations and apply them.

code is actually almost there, as we are reading and inserting migrations in versions, we could also insert them themselves. guess its now beginner code ;)
see db.checkVersion in lib/db/db_handler.go

To sum up:

when database doesn't have a versions table ( presumably clean slate )

create table versions:
 create table versions ( applied timestamp without time zone default (now()  at time zone 'utc') , file varchar(150) );
read all migration files (filepath.Walker already does this ;p )

apply all migrations (done a little bellow )
insert them in versions ( already done )


Wrong display scaling for "Save As" dialog

Issue Type: Bug
I have 3 screens on my developer machine:

full HD screen with 100% scaling (primary)
4k Screen with 200% scaling
4k Screen with 200% scaling

If I have Visual Studio Code open on Screen 3, and I save a file, the "Save As" Filechooser does not open with 200% scaling. Instead it is shown too small to read (with 100%) and I have to manually drag it over to screen 1 to be able to see what I am doing.
"Open File" and "Open Workspace" is also affected by this bug. However other modal dialogs like the "About" version dialog are opened with the correct 200% scaling and keep the proper scaling for the display even if dragged between different displays.
VS Code version: Code 1.53.2 (622cb03f7e070a9670c94bae1a45d78d7181fbd4, 2021-02-11T11:48:04.245Z)
OS version: Windows_NT x64 10.0.18363

System Info

Item
Value

CPUs
AMD Ryzen 9 5900X 12-Core Processor             (24 x 3693)

GPU Status
2d_canvas: enabledgpu_compositing: enabledmultiple_raster_threads: enabled_onoop_rasterization: enabledopengl: enabled_onprotected_video_decode: unavailable_offrasterization: enabledskia_renderer: enabled_onvideo_decode: enabledvulkan: disabled_offwebgl: enabledwebgl2: enabled

Load (avg)
undefined

Memory (System)
63.93GB (41.45GB free)

Process Argv
--crash-reporter-id 9ff9e56c-61e6-4c49-8aaa-46c8cab66152

Screen Reader
no

VM
0%

Extensions (4)

Extension
Author (truncated)
Version

better-toml
bun
0.3.2

go
gol
0.22.1

rust-analyzer
mat
0.2.489

vscode-lldb
vad
1.6.1

A/B Experiments
vsliv368cf:30146710
vsreu685:30147344
python383:30185418
pythonvspyt617cf:30253240
vspor879:30202332
vspor708:30202333
vspor363:30204092
pythonvsdeb440:30248342
pythonvsded773:30248341
pythonvspyt875:30259475
dockersubsetcf:30259262

I just figured that this is probably a duplicate of #85898 (and #88931 and #88708)

/duplicate #85898


User is able to edit FG that was opened from file

Steps to Reproduce

Open file with expanded FG for example
ketcher (21).zip
Edit the FG (drag or apply erase)

Expected behavior
User is not able to apply edit actions to FG.  Edit abbreviation window is shown
Actual behavior
The edit actions are allowed
Screenshots
https://user-images.githubusercontent.com/93334478/143580584-165db7c5-f78e-4beb-aa47-eba38d86bd6d.mp4
Desktop (please complete the following information):

OS: Windows 10
Browser Chrome Version 93.0.4577.63, Firefox Version 94.0.1, Microsoft Edge Version 93.0.961.47

Fixed, tested 2.4


Tutorial leve documentation

MVC description diagram for Voxa with responsibilities
New Alexa developers starting with Voxa
glossary/index

Coverage remained the same at 97.661% when pulling f9354d04cef2c2371959e05384082259e9ec16ab on cvaca7:master into bea4b9111d4cabc17ab439f698bdfc9e4c63151e on mediarain:master.

Coverage remained the same at 97.661% when pulling 86a79164ff9a0419289fe2397a72b95d5bd97483 on cvaca7:master into bea4b9111d4cabc17ab439f698bdfc9e4c63151e on mediarain:master.

Coverage remained the same at 97.665% when pulling 5e46ca02370ca96127b7d359ccfa7b02de1e2301 on cvaca7:master into ff32026c62b2d13a651e8f72bb97e53d7f9d00a5 on mediarain:master.

Coverage remained the same at 97.665% when pulling 5e46ca02370ca96127b7d359ccfa7b02de1e2301 on cvaca7:master into ff32026c62b2d13a651e8f72bb97e53d7f9d00a5 on mediarain:master.

@cvaca7 when creating a new branch always start from the remote master, that way you don't get the huge history, for example in this case it shows as if there were 35 commits on this PR


Add goss test to validate precache image pods are succeeding

Summary and Scope
Add test to detect when we are failing to pre-cache images on worker nodes.
Issues and Related PRs

Resolves CASMPET-4862

Testing
vshasta (success and failure)
Tested on:

Virtual Shasta

Test description:
Ran the test/suite.
Risks and Mitigations
N/A
Pull Request Checklist

[ ] Version number(s) incremented, if applicable
[ ] Copyrights updated
[ ] License file intact
[ ] Target branch correct
[ ] CHANGELOG.md updated
[ ] Testing is appropriate and complete, if applicable
[ ] HPC Product Announcement prepared, if applicable

/backport master


'Acquire Lease' is disabled for one new uploaded ADLS Gen2 blob

Storage Explorer Version: 1.15.0-dev
Build: 20200630.1
Branch: master
Platform/OS: Windows 10/ Linux Ubuntu 18.04/ macOS Catalina
Architecture: ia32/x64
Regression From: Not a regression
Steps to reproduce:

Launch Storage Explorer.
Expand one ADLS Gen2 storage account -> Blob Containers.
Create a blob container -> Upload one blob.
Right click the uploaded blob -> Check the action 'Acquire Lease' on the context menu.

Expect Experience:
The action 'Acquire Lease' is enabled.
Actual Experience:
The action 'Acquire Lease' is disabled.

More Info:

This issue doesn't reproduce for .vhd files.
The 'Acquire Lease' become enabled after changing access tier or renaming the blob.

Find root cause in 1.15 and then we'll go from there.

Find root causes, then move to 1.16

@v-xianya I cannot repro this. Are you still able to reproduce it?

Hi @MRayermannMSFT Verified this issue on build master/20200813.4. Do not reproduce. So we are going to close it.


fix weird var

sorry @xavijam

:ok_woman: :ok: :cool:

Go!

you need a test CI on this repo eh ;)


"Remove global filter from description" makes font very big

Please check that this issue hasn't been reported before.

[X] I searched previous Bug Reports didn't find any similar reports.

Expected Behavior
Enabling "Remove global filter from description" and restarting Obsidian causes global filter tag to be removed from tag lists in views. No other difference in appearance occurs.
Current behaviour
Enabling "Remove global filter from description" and restarting Obsidian causes global filter tag to be removed from tag lists in views - as expected.
Font for the whole view becomes much bigger than normal.
Steps to reproduce

Create a view, in my case:

not done
group by tags

Add some tasks
Font in the view is too big

Which Operating Systems are you using?

[ ] Android
[ ] iPhone/iPad
[X] Linux
[ ] macOS
[ ] Windows

Obsidian Version
1.1.9
Tasks Plugin Version
1.22.0
Checks

[X] I have tried it with all other plugins disabled and the error still occurs

Possible solution
No response

Please supply screenshots, and please run the Debug Info command in Obsidian and paste the output here.
Thanks!

With option disabled:

With option enabled:

Is this the debug info you need?
SYSTEM INFO:
	Obsidian version: v1.1.9
	Installer version: v1.1.9
	Operating system: #1 SMP PREEMPT_DYNAMIC Sat Jan 14 16:55:06 UTC 2023 6.1.6-200.fc37.x86_64
	Login status: not logged in
	Insider build toggle: off
	Live preview: on
	Legacy editor: off
	Base theme: dark
	Community theme: none
	Snippets enabled: 0
	Restricted mode: off
	Plugins installed: 2
	Plugins enabled: 1
		1: Tasks v1.22.0

RECOMMENDATIONS:
	Community plugins: for bugs, please first try updating all your plugins to latest. If still not fixed, please try to make the issue happen in the Sandbox Vault or disable community plugins.

Perfect - thank you!!!

I found the problem. I've set global task filter to task - so I assume the plugin didn't remove # symbol, resulting in this big font. After setting global task filter to #task the problem went away, so this issue can be closed.
Maybe it would be a good idea to add some validation to this field? Or is it intended usage to set it to something not starting with #?

Ah, interesting. I’m glad you figured it out.
The global filter can be any strong you like, including non-hashtags.
I think the the report didn’t say what your global filter was, so I would not have been able to work that out.


♻ Replace String errors with Nil

Currently the library errors with a String message describing what went wrong. This can be useful for user-facing code (eg a form validating library) but becomes much less practical in developer-facing code used internally - which we can imagine a maths library probably is.
Here string errors are difficult to handle because they cannot be easily pattern matched on, often cannot be conveniently reported, and do not compose well with result.try where other functions return a different error type.
This PR adopts the practice of returning Nil to signify "an error has happened, but the details are not important". I know there are some cases where a function was returning different error messages for different kinds of inputs, but I think I'm OK taking the position that Nil is more-than-suitable in these cases too. What do you think?

I resolve these in a bit (was totally expected)

It's fine with me that Nil is returned. Maybe I'll skim through the docs, later, adding a mention of edge-cases that are not obvious and which are not documented already.


Add optional, exhaustive unit test suites that run actual DFT codes

Currently, codes like xTB and EMT that have native Python interfaces are run via GitHub actions directly, whereas codes like Gaussian and ORCA are "mocked" via a fake .get_potential_energy() function. Long-term, we should provide an optional suite of additional tests that actually run all the codes (if hypothetically available) with actual energies being tested. This wouldn't be run regularly or be required for development, but it would help with the robustness and trustworthiness of the code.

This is going to be annoying to debug...


Conditions items become in-removable on PC actor

Condition items become in-removable on PC actor, sometimes creating mess of condition icons. Seems to start when toggling condition multiple times. Issue seems to be limited to PCs. And only in an online environment, such as Forge. Local foundry does not produce this issue.
Exported sheet can have conditions toggled off normally within local foundry.
Addition: Bug might be a latency issue, as cleaning up the server made the issue happen less often.

Tested with all modules disabled, on new actor
SFRPG Version: Dev branch

I saw this in my game on Tuesday, we do not use Forge.
One of my players had this issues. Workaround was to copy his character and removing the conditions from the right click menu on the token. Trying to remove the conditions from the character sheet made them unremovable again.
I'll try to reproduce this and might update with more info.
Technical details:
OS: Windows 10
Browser: I don't know which browser the player used, but it was also reproducible locally on my Foundry App
Foundry Version: 11.302
SFRPG Version: 0.24.2

#1176 partially solves this but it appears to me that this is a core bug: https://github.com/foundryvtt/foundryvtt/issues/9672#issuecomment-1605194277


 Most of the test cases
are now covered by either the Docker Compose tests or the E2E tests -
making the nix tests redundant.
Some of the rebuild test cases that weren't covered have been rewritten
as Docker Compose tests.

bors merge

bors merge

bors try

bors try

bors merge

bors merge


Allow a resource's API token to be updated

Description of change
When the token flag was added to created, it should have been added to update at the same time
Fixes https://github.com/meroxa/cli/issues/679
Type of change

[ ]  New feature
[x]  Bug fix
[ ]  Refactor
[ ]  Documentation

How was this tested?

[x]  Unit Tests
[ ]  Tested in staging
[ ]  Tested in minikube

Demo

before
after

Additional references

Documentation updated

LGTM! I am just wondering why we are moving away from the ID(UUID).

@nassor just to make it more readable on our end.  the customer never has ID, so the argument will only ever be name.  even though the Client function will accept ID, also.


installation error on dotnet

TASK [Ensure powershell is removed through dotnet  before installing] **********************************************************************************************************************************************************************************************************************************************
fatal: [jupyterhub2.hp.local]: FAILED! => {"changed": true, "cmd": ["/usr/share/dotnet/dotnet", "tool", "uninstall", "--global", "powershell"], "delta": "0:00:00.577413", "end": "2022-12-22 18:16:25.341265", "msg": "non-zero return code", "rc": 1, "start": "2022-12-22 18:16:24.763852", "stderr": "A tool with the package Id 'powershell' could not be found. \r\n\r\nTools are uninstalled using their package Id which may be different \r\nfrom the tool name you use when calling the tool. You can find the tool names \r\nand the corresponding package Ids for installed tools using the command\r\n'dotnet tool list'.", "stderr_lines": ["A tool with the package Id 'powershell' could not be found. ", "", "Tools are uninstalled using their package Id which may be different ", "from the tool name you use when calling the tool. You can find the tool names ", "and the corresponding package Ids for installed tools using the command", "'dotnet tool list'."], "stdout": "\nWelcome to .NET 7.0!\r\n---------------------\r\nSDK Version: 7.0.101\n\nTelemetry\r\n---------\r\nThe .NET tools collect usage data in order to help us improve your experience. It is collected by Microsoft and shared with the community. You can opt-out of telemetry by setting the DOTNET_CLI_TELEMETRY_OPTOUT environment variable to '1' or 'true' using your favorite shell.\r\n\r\nRead more about .NET CLI Tools telemetry: https://aka.ms/dotnet-cli-telemetry\n\n----------------\r\nInstalled an ASP.NET Core HTTPS development certificate.\r\nTo trust the certificate run 'dotnet dev-certs https --trust' (Windows and macOS only).\r\nLearn about HTTPS: https://aka.ms/dotnet-https\r\n----------------\r\nWrite your first app: https://aka.ms/dotnet-hello-world\r\nFind out what's new: https://aka.ms/dotnet-whats-new\r\nExplore documentation: https://aka.ms/dotnet-docs\r\nReport issues and find source on GitHub: https://github.com/dotnet/core\r\nUse 'dotnet --help' to see available commands or visit: https://aka.ms/dotnet-cli\r\n--------------------------------------------------------------------------------------", "stdout_lines": ["", "Welcome to .NET 7.0!", "---------------------", "SDK Version: 7.0.101", "", "Telemetry", "---------", "The .NET tools collect usage data in order to help us improve your experience. It is collected by Microsoft and shared with the community. You can opt-out of telemetry by setting the DOTNET_CLI_TELEMETRY_OPTOUT environment variable to '1' or 'true' using your favorite shell.", "", "Read more about .NET CLI Tools telemetry: https://aka.ms/dotnet-cli-telemetry", "", "----------------", "Installed an ASP.NET Core HTTPS development certificate.", "To trust the certificate run 'dotnet dev-certs https --trust' (Windows and macOS only).", "Learn about HTTPS: https://aka.ms/dotnet-https", "----------------", "Write your first app: https://aka.ms/dotnet-hello-world", "Find out what's new: https://aka.ms/dotnet-whats-new", "Explore documentation: https://aka.ms/dotnet-docs", "Report issues and find source on GitHub: https://github.com/dotnet/core", "Use 'dotnet --help' to see available commands or visit: https://aka.ms/dotnet-cli", "--------------------------------------------------------------------------------------"]}

Seems we need to remove powershell before updating dotnet.


Proposal: Some workflow improvements

I think that one of best thing with this extension is that it facilitates very low entry barrier compared CMake's configure->generate->build approach.
If it's not clear the goal is to make CMake Tools extension more robust and behave more expected.
Limitations of current implementation, especially with 'Server Mode':
(not in any particular order)

Changing variant actually requires clean configure, because it assumes different compiler and CMake forbids this. Now it may be just silently ignored, depending on generator and compiler used.
Same for generator: it is either fails to start/configure or will be silently ignored.
Opening a configured is very different form opening an unconfigured one: a very different sets of operations available.
Changing Binary dir in any way (by changing settings or any of variables being substituted) may require clean configuration and now mostly silently ignored by the extension.
CMake Server should be restarted in some of cases above, e.g. when having multiple binary directories with differently configured projects.

The proposal
Introduce clear separation between 'configured' and 'unconfigured' projects.
This is both in API and UI level, for example:

Unconfigured: build & debug targets selectors should not be visible, only "Configure" is possible.
Configured: should be possible to build and debug, but changing variant shouldn't be allowed.

Binary directory should be sufficient to activate project
CMake Tools should "activate" backend with binary directory, which then starts providing metadata.
This means that CMake should store some extra data in binary dir, like environment and variant (likely move .cmaketools.json there).
When changing binary dir CMake Tools should reinitialize all metadata.
It should be also possible to work with externally-configured project.
Introduce simple/advance mode
If opening unconfigured project CMake Tools should ask something like "Hey, it looks like this project is CMake-based. Would you like me to initialize build system for you? (Yes/No)" and then experience should be not different from the current one. This is "simple mode".
In "advanced mode" CMake Tools just keeps registry of known build directories, allowing to switch between them or initialize new. In the latter case UX could be similar to CMake-GUI tool.
Another option is to store registry and essential settings at the same time in json configuration. Something like variants.json or CMakeSettings.json. This is somewhat close to tasks.json.
In case of using json, once initial configuration is done, it is used only to get a user-friendly name for binary directory. As a stretch, CMake Tools may track changes to it and offer clean reconfigure when it detects changes.
Configuration selector
It is required for multi-configuration generator but otherwise full rebuild is needed, which is counter-intuitive and may be dangerous to do automatically (e.g. if project builds for 30 minutes).
On the other hand switching between Debug and Release is quite essential and deserves to be represented in UI so I suggest exposing this functionality in 'simple' mode which will rebuild the project.
Environment selector is available only when configuring project initially
Environment, once detected, should be stored 'by value', i.e. not as a moniker, but rather as all extra variables.
This pursues multiple goals.

As mentioned early, changing environment is a significant change and requires clean configure.
It is very unlikely that detecting environment will return different results. Even if it does, CMake may reject or ignore new values.
Detection takes time (few seconds) and avoiding this every time makes startup faster.
Multiple environments are cumbersome and should not be allowed: if I activate MinGW and VS, which compiler will be used with Ninja generator?

Please up/down vote if this makes sense or leave your comments.
If this sounds useful I would like to implement this.

+1

In my opinion, this project should be refactored before you(or us) implement this.
this source codes... are such as spaghetti, it is pretty hard something to add, implement more.
so, refactor functions, methods, implement more clearly is needed.

I like any proposal for enhancements, but a few things to clarify:

Changing the variant should not require a clean configure. I want to try and emphasize a difference between "variant" and "toolset". A toolset (aka toolchain) encapsulates things like compiler and platform, and would definitely require a clean configure (or new build dir). I had plans to support some form of  cmake-toolsets.json that did similar to cmake-variants.json, but I haven't yet gotten around to implementing it.
Changing the binary dir should already cause a reconfigure (and CMake Server restart). If it doesn't, that's a bug 😦.

There are pros/cons of moving .cmaketools.json. By keeping it with the project, certain options, such as the active environment, get kept between build directories.
Also, if the extension currently behaves differently when using an externally-configure build directory, that's a bug. I wanted to make sure that CMake Tools always worked with a build directory, whether configured using the extension or from the CLI/GUI/TUI.
👍 for caching the env detection. One thing that may change would be Windows SDK and Windows Kits path, so that's something to keep in mind.
Some aspects of your recommendation are still somewhat unclear to me, but I'd be glad to hear them further!

Changing the variant should not require a clean configure. I want to try and emphasize a difference between "variant" and "toolset". A toolset (aka toolchain) encapsulates things like compiler and platform, and would definitely require a clean configure (or new build dir). I had plans to support some form of cmake-toolsets.json that did similar to cmake-variants.json, but I haven't yet gotten around to implementing it.

I see. May be 'clean configure' is exaggeration, but clean build is very likely. Here major surprise is that multi-config generators behaves differently, and switching config/variant just incrementally builds from last state. I would rather simulate this behavior and that's what I meant by 'binary dir registry'. For example, how this could look like:
"common": {
  "generator": "Ninja",
  "buildRoot": "build/${buildType}-${buildPlatform}",
},
"configurations": [
  {
    "name": "x86-release",
    "buildType": "RelWithDebInfo",
    "platform": "x86",
    "activateEnvironment": "MinGW",
  },
  {
    "name": "x64-debug",
    "buildType": "Debug",
    "platform": "x64",
    "activateEnvironment": "MinGW64",
  }
]

Thinking of your proposal of variants, I don't really see how it plays with editing cache. Maybe something like a set of predefined variables which are applied or used to initialize build dir?..
And having different configure options for different binary dirs is useful not only for Build Type and default linkage. For example, with and without tests. Another case I have in mind is cross-compiling for embedded devices: both toolset (i.e. arm vs avr) and variables (for different MCU models) could be different.

Changing the binary dir should already cause a reconfigure (and CMake Server restart). If it doesn't, that's a bug 😦.

I think it's doable even now (especially with other PR which expands variables right in config.ts in 3 lines). But doing it implicitly may lead to surprises, especially when substituted variable changes. Then question is what to do with previous binary dir? Should it be deleted or left? Should it be possible to reuse it? Won't it lead to unexpected results (e.g. when user changes back, some new flags may be assumed, but they aren't updated).

It may be useful to look at how QtCreator does the "toolsets". It switches build directory based on the chosen kit. Switching toolsets is definitely a case where a new build directory is important.

@vector-of-bool So what is your vision (briefly) on how toolsets, variants and editing cache should work together? What responsibilities do they have and when one should be used instead of another?
I'm asking because I have a feeling that they overlap much (plus there few ways to customize via VS Code settings).

Sorry to vanish like I did. I have a habit of doing that, and I think it might be annoying.
I'd like to switch out the term toolset for toolchain since those are two distinct terms when talking to CMake. I think of toolchain as being the actual underlying build tools, but also including things like platform and ABI. For example, Windows 32-bit and Windows 64-bit are different toolchains, because they have different compilers and are not ABI compatible. Same goes for things like Android, Emscripten, iOS, whatever else.
A variant is rather a collection of build options and configurations, and may or may not be ABI compatible, depending on the compiler and platform. A basic example is Debug. This is a variant that includes and embeds debug information, as well as enabling debug assertions and disabling optimizations. Release is a separate variant. Projects can provide their own variants, which let users and developers identify commonly used sets of configuration options. This would be stored in a cmake-variants.json. It's more than just a set of CMake settings, which are a bit more fine-grained. A particular variant is just a set of CMake settings and corresponding values. For example, a Debug variant just has one setting value: CMAKE_BUILD_TYPE=Debug. Release, conversely has a different single setting value: CMAKE_BUILD_TYPE=Release. A more complex set of variants might look like this:
debug: {
  oneWordSummary$: 'Debug',
  description$: 'Emit debug information without performing optimizations',
  buildType: 'Debug',
  settings: {
    DEBUG_ASSERTIONS: true
  }
},
safe_release: {
  oneWordSummary$: 'SafeRelease',
  description$: 'Enable optimizations, but keep debug assertions',
  buildType: 'Release',
  settings: {
    DEBUG_ASSERTIONS: true
  }
},
release: {
  oneWordSummary$: 'Release',
  description$: 'Enable optimizations, omit debug info and assertions',
  buildType: 'Release',
  settings: {
    DEBUG_ASSERTIONS: false
  }
},

Variants aren't specific to a toolchain. It's up to the project to figure out how to apply a specific variant option when using the specific toolchain (ie. set the proper preprocessor definitions).
Editing the cache == editing CMake settings. Like above, editing the cache should be fully supported. This allows users to set particular build settings that may or may not be exposed as a variant.

Just released 0.10.2. I think I want to do some refactoring for 0.11.0 to support toolchains and variants better. I, personally, have usually stuck with a single binary dir for all variants, and this spells a problem in that I don't see the bugs in CMake Tools' support for that workflow. A lot of users prefer to keep multiple binary directories around, and it makes it convenient to switch between toolchains and variants easily, as well as know exactly what a particular binary dir is building for, without the need to inspect the existing project configuration.
I foresee that it may be best to instantiate multiple backends per user toolchain and variant. This would make it extremely easy to switch between toolchains and variants, without needing to completely restart and reconfigure the CMake Tools instance.

@vector-of-bool , FYI: I've started some refactoring of CMakeTools with following principles in mind:

Testing-oriented. I believe that it's a luxury to NOT have automated testing. So I try to cover as many scenarios as possible. To make tests an asset and not burden, I plan to have some good combination of component and integration tests.
Modularity and composition. Split large classes like common or backend into smaller pieces with limited responsibility and independent interface to compose in upper layers. Change some hard dependencies (e. g. backend doing diagnostics and output) into injected. This is essential for testability.
Model-based approach. In the current code there are hard dependencies, say between common and status which prevents components to be tested in isolation. Model on the other hand breaks such direct dependencies and allows mocking / faking different scenarios for component testing.

ATM I plan to keep existing functionality and public API and just cover it with tests to make further improvements more reliable.
WIP is in my branch. I've started a new job so progress is very slow, but I appreciate any comments / suggestions (even if it's completely wrong and not how you see it).

@ytimenkov, after months of stagnation, I've started a rewrite. This will be taking into account quite a few learned lessons and should implement a lot of the features I've wanted from the beginning, and work around some of the common problems and bugs I've been having. All my work is going into a feature/refactor-1.0 branch, which you can take a look at.
ATM, I'm working on improved toolchain selection which will be similar to QtCreator's idea of Kits. This will make it more reliable for people to switch between toolchains on all platforms, not just Windows. A few things I want to keep in mind with a rewrite:

Async initialization everywhere, and invoking commands in the extension is async by default, awaiting on the initialization routines to finish. This means that a user won't be able to request CMake Tools to do anything before initialization has finished. Instead, their commands will await on initialization, so users won't be able to see any torn state.
Use filesystem watchers to see changes in settings. When we save settings, we commit those changes to disk and the filesystem watcher is the one who updates the extension state with the new settings. This means that users' modifications to files and modifications by the extension itself won't fight.
Caching toolchains (Kits) to a user-local data directory. User's will be able to modify this file to add their own kits via toolchains or environment settings. These will behave as first-class build environments in the same way as Visual Studio environments.
No compiling without selecting a Kit.
Event-driven state changes with strong separation of concerns. For example, the KitsManager class entirely controls and presents the user with Kit selection and emits an event when the Kit selection changes, which propagate through the rest of the extension.
Better end-user documentation. I'm going to start work on dedicated documentation based on Sphinx and reStructuredText. I'll host these docs on my GitHub Pages.
Stronger type checking. Added noImplicitAny, noImplicitReturns, noUnusedLocals, and noUnusedParameters to tsconfig.json.
More tests, and more testable code.

Besides reaching feature parity in the rewrite, I want some additional features that I miss from other IDEs:

Project structure view. This can be obtained via CMake Server. The current architecture makes adding this a little hairier than I would like. With VSCode Custom Explorers, this can be done in a fairly nice way.
Better CMake code introspection and autocompletion. The CMake extension provides some of this functionality, but I think it could be much better.
Higher-level project commands. Being able to invoke a command like "Add new C++ class header and implementation" that creates the files and inserts them into the corresponding CMakeLists.txt would be awesome but will require better CMake code introspection.

I want to say thanks for all the interested and -- event better -- work you've put into this project. It's been a great help. I know you've been busy (as have I, hence the recent stagnation), but if you (or anyone else happening to read this) would like to help, feel free to send PRs or just comment on my commits/issues.

@vector-of-bool I've been to RL too recently :) (started a new job), so I'm sad I haven't finished work I started. After you started rewrite I don't see many reasons to continue what I was doing in my branch, but rather try
(https://github.com/ytimenkov/vscode-cmake-tools/commits/feature/backend-refactoring).
However I will be happy if you can find anything useful there (used patterns, pieces of code) to incorporate in your refactoring.
In particular 2 things I work there quite well:

Backend (re)initialization. (I've picked up the idea from typescript extension, I guess), but chaining promises work amazingly well to handle case when you need to restart the backend while some initialization is already in progress.
Tests. Many may be obvious or trivial, but I've recently found myself enjoying building system block by block while getting immediate feedback.

@vector-of-bool I took a look into your refactoring branch. The kit approach looks nice.
I saw in the kit manager class source code is a combination of logic (Kit management, scan for kits...) with the UI control (Update Status bar text). This makes it hard to write unit tests for the kit management logic and make it harder to understand the code. A separation into UI control and buisness logic makes it easier to test the logic of this vscode extension. I think the tests will be important in the long term for maintance and bugfixing.

@KoeMai, you're right. I'm still in early stages and hoping to get it as nice as I can in a reasonable amount of time. I'll be reworking that before finishing. Thanks for the consideration!

@ytimenkov, do you still have any interest in collaborating? I'm looking for more collaborators since I'm pretty bad at keeping up with consistent updates.

Could try. RL has settled down a bit although I won't have as much time I had last summer.
Is there anything particular on your mind?

Take a look at #315 and #274. In general, I'm just getting overloaded as a single person on this project.

My rewrite was mostly about making the extension more testable.
Architecture: I (re)structured code into smaller relatively independent pieces (big abstract classes like current CMakeDriver are hard to test in isolation):

Driver/backend: does only configure/generate and introspection of generated project, being an interface. Server implementation is covered by component tests.
CMake wrapper Contains common calls to CMake and handles build logic with grabbing output, cancellation, etc. Also tested in isolation.
Model: Contains the logical state of extensions (i.e. project, selected target, kit, variant, etc.). Exposes properties and notifications of property changes via events. I saw comment like "Updating status from kit manager makes testing harder". That is a solution.
Glue. That functionality was in old wrapper class. It is responsible for creating and wiring up components. For example assigning buildDirectory property to model triggerred restarting backend, which in turn triggerred updating targets, etc. And this may happen by changing configuration, variant, etc. Automagically.

Reasonig: In my experience approaches with "scenario"-based tests or any tests covering multiple units at once without base of smaller component tests are much easier to write, easy to get true positive result but in long term harder to maintain, harder to get true negative result. That is make the test catching issues when something changes.

yes, I like your next steps. I would help, I was first interested to get a bundle of tests which check the function of the extension. So that a refactoring can be done without breaking the extension functionality. For the following steps I thought about refactoring parts. My ideas go in the same direction like yours. In future I think most tests should only test the small single responsible components.

yes sounds good.
I would add an additional level for construction of cmake version dependent components like the driver for server and legacy mode (Factory?). I do not know if there are other components in the extension which are CMake version dependent.
One question: Is a central cancelation useful? I think each component needs a separate one which is manages by a cancelation component or the extention entry point.
Yes, im with you. Maybe we use a Model, which has for each main component an sub model. In this case not all components have to see all settings.
The notification is a nice way to separate UI from the extension backend.
Is this in Cmake-tools in the refactoring branch?

I like the idea of CMakeSettings.json support. If the file is present, VSCode could simply override variety of the settings using values from this file. (at least, "cmake.buildDirectory" so it does not create build over and over, when my CMakeSettings.json create _build ;-))

@ytimenkov for me it looks like many topics of this proposal have already been addressed? Could this issue be closed?

Sure. I created this issue to get feedback on changes I was working on, but unfortunately didn't have spare time to finish and at my current job we don't use CMake.


Table keys question

Hello,
I have different tables for different environments that need to be dynamically selected, so I cannot use the in-model table field (or can I?). However, this appears to be where I can declare my primary key for the table. Is there any way to declare a primary key that isn't the default 'id' without using the table method, i.e. can I declare that it's the key for the table and declare the table in our AWS config as normal? How can I get around this?
EDIT: also, is there any way to use the native table timestamp management without declaring the name of the table?
If none of these solutions work, I can just environmentally control the String that we use to declare table name... but I'm curious about the possible implementations anyways.

Not sure whether I understand your problem correctly. So provide more details and examples.

Is there any way to declare a primary key that isn't the default 'id' without using the table method

No.

i.e. can I declare that it's the key for the table and declare the table in our AWS config as normal?

Yes, you can declare primary key without declaring table name (in table method call).
Just to be sure you didn't miss it in the documentation. If a table name isn't specified explicitly (in table method) Dynamoid will use table name inferred from a class name. For instance for User class default table name will be users or <configured-namespace>_users where configured-namespace could be test, staging etc configured globally.

is there any way to use the native table timestamp management without declaring the name of the table?

What is "native table timestamp management"?

Hey, thanks for the quick response!
Good to know regarding declaring primary key, which also answers my timestamp question (can I use your created_at & updated_at without declaring a tablename), so nevermind that.
As for the table name conversation:
Okay, thank you, I did miss that - so I can configure the config.namespace conditionally based on the environment and I can allow Dynamoid to infer the table name from the environmentalized namespace. Thanks so much for your help!

Hello, sorry to reopen, but I'm actually having an issue with our configured namespace.
*** Exception Aws::DynamoDB::Errors::ResourceNotFoundException in passenger-irb (Requested resource not found: Table: dynamoid_ContactsCore_production_qa_account_mapping not found) (process 29136, thread 0x007fbf541269a0(IRB worker)):

obviously "dynamoid" isn't in our configured namespace... and I am also technically declaring our tablename explicitly here:
table name: :qa_account_mapping, key: :account_id

In your prior comment you mentioned that dynamodb infers the table name if it is not explicitly declared... is there any way to prevent it from doing so in the case that it is?


Add Kill button in the currently running tab of Executing Flows

@arumugarani, would you mind posting images of before and after UI so that we can view this change more easily?

Added the images

The change proposal looks much sense to me. I often thought we should have this feature.

When will you merge this?


Check for additional eslint rules we want to use

During the last PRs we already noticed that there are some eslint rules we may want to add, e.g. here. The ticket is a reminder to revisit the topic and see what rules are reasonable for us.

added additional eslint rules related to im/exports in this PR #234


Inconsistency: Dot notation failing with custom methods in summary_fields

/**
 * Class Club
 * @package Vulcan\Derp\Models
 *
 * @property string Title
 * @property string Description
 *
 * @property int    ClubOwnerID
 *
 * @method HasManyList Events
 */
class Club extends DataObject
{
    private static $db = [
        'Title'       => 'Varchar(255)',
        'Description' => 'Text'
    ];

    private static $has_one = [
        'ClubOwner' => Member::class
    ];

    private static $has_many = [
        'Events' => Event::class
    ];

    private static $summary_fields = [
        'Title'              => 'Title',
        'ClubOwner.Name'     => 'Club Owner',
        'ActiveEvents.Count' => 'Active Events',
        'ClosedEvents.Count' => 'Closed Events'
    ];

    public function getActiveEvents()
    {
        return $this->Events()->filter([
            'EndDate:GreaterThan' => DBDatetime::now()
        ]);
    }

    public function getClosedEvents()
    {
        return $this->Events()->filter([
            'EndDate:LessThanOrEqual' => DBDatetime::now()
        ]);
    }
}

If I have:
    private static $summary_fields = [
        'ActiveEvents' => 'Active Events',
        'ClosedEvents' => 'Closed Events'
    ];

both methods "getActiveEvents" and "getClosedEvents" are found.
however if I have:
    private static $summary_fields = [
        'ActiveEvents.Count' => 'Active Events',
        'ClosedEvents.Count' => 'Closed Events'
    ];

I get

[Emergency] Uncaught BadMethodCallException: Object->__call(): the method 'ActiveEvents' does not exist on 'Vulcan\Derp\Models\Club'

To resolve this I need to use the entire method name:
    private static $summary_fields = [
        'getActiveEvents.Count' => 'Active Events',
        'getClosedEvents.Count' => 'Closed Events'
    ];

Do you have a full backtrace for

[Emergency] Uncaught BadMethodCallException: Object->__call(): the method 'ActiveEvents' does not exist on 'Vulcan\Derp\Models\Club'

Also, the get prefix on models should only be used when creating pseudo properties - does renaming them break the first example:
    private static $summary_fields = [
        'ActiveEvents' => 'Active Events',
        'ClosedEvents' => 'Closed Events'
    ];

This isn't a bug but it's obviously a bit confusing. It's also discussed in #8837. Recommend we improve the docs.

Closing as duplicate of #8837


miner address incorrect

As mentioned in the README
miner = Ckb::Wallet.from_hex(Ckb::Api.new, "e79f3207ea4980b7fed79956d5934249ceac4751a4fae01a0f7c4a96884bc4e3")

expect miner.address to be 0xcf7294651a9e2033243b04cfd3fa35097d56b811824691a75cd29d50ac23720a, but 6c5b2cd24ce7cbc16ff368d116294b3c8e5e4f33197900396e9a35d52d8c0f83" received.

A few things to check:

Have latest argv_source_entry binary (download, don't build it yourself).
Update your CKB node config to have 0xd7abc1407eb07d334fea86ef0e9b12b2273833137327c2a53f2d8ba1be1e4d85 as miner type hash.
Get latest CKB source code from develop HEAD and cargo build it.

[x] use latest argv_source_entry
[x] update ckb and set 0xcf7294651a9e2033243b04cfd3fa35097d56b811824691a75cd29d50ac23720a to miner.type_hash
[x] build again

still get 0x6c5b2cd24ce7cbc16ff368d116294b3c8e5e4f33197900396e9a35d52d8c0f83 from pk of e79f3207ea4980b7fed79956d5934249ceac4751a4fae01a0f7c4a96884bc4e3

@Keith-CY Looks like your type hash is correct. I'll double check and update.


How does "My components" works?

Been checking around the library and it's great, but I don't get how "my components" section works, it has to be accepted to get into the official component list?

Hi!
The idea of this funcionality is to make a list of community created components.
We are currently working on this feature and only your own components are visible.
We hope you can enjoy and share your components after the hackathon!
PS: In case you didn't see it, you can create a Component in your profile drop-down.

Alright, that's good.
Yes, I see the button on the dropdown, but I think it'll be better to put a create button in the components screen as well.
I might be creating a PR adding this.


cmd/go: Remove support for relative import paths.

Ref the discussion at golang-nuts "Proposal: ban relative import paths".

https://groups.google.com/d/msg/golang-nuts/n9d8RzVnadk/07f9RDlwLsYJ

Posted by Andrew Gerrand on Apr 3:
> See my earlier post in this thread about why relative imports are a bad idea.
>
> The only reason the go tool supports relative imports is to run the compiler tests,
which predate the go tool and the concept of GOPATH. I would prefer to refactor the
compiler tests so that relative imports are not used, and remove support for relative
imports from the go tool entirely.
>
> Andrew

I believe we should keep the limited support that exists today.


[ProviderHub] Update definitions

MSFT employees can try out our new experience at OpenAPI Hub  - one location for using our validation tools and finding your workflow.

Changelog
Please ensure to add changelog with this PR by answering the following questions.

What's the purpose of the update?

[ ] new service onboarding
[ ] new API version
[ ] update existing version for new feature
[ ] update existing version to fix swagger quality issue in s360
[x] Other, please clarify

When you are targeting to deploy new service/feature to public regions? Please provide date, or month to public if date is not available yet.
When you expect to publish swagger? Please provide date, or month to public if date is not available yet.
If it's an update to existing version,  please select SDKs of specific language and CLIs that require refresh after swagger is published.

[ ] SDK of .NET (need service team to ensure code readiness)
[ ] SDK of Python
[ ] SDK of Java
[ ] SDK of Js
[ ] SDK of Go
[x] PowerShell
[ ] CLI
[ ] Terraform
[ ] No, no need to refresh for updates in this PR

Contribution checklist:

[x] I commit to follow the Breaking Change Policy of "no breaking changes"
[x] I have reviewed the documentation for the workflow.
[x] Validation tools were run on swagger spec(s) and errors have all been fixed in this PR. How to fix?

If any further question about AME onboarding or validation tools, please view the FAQ.
ARM API Review Checklist

[ ] Ensure to check this box if one of the following scenarios meet updates in the PR, so that label “WaitForARMFeedback” will be added automatically to involve ARM API Review. Failure to comply may result in delays for manifest application. Note this does not apply to data plane APIs, all “removals” and “adding a new property” no more require ARM API review.

Adding new API(s)
Adding a new API version
[ ] Ensure to copy the existing version into new directory structure for first commit (including refactoring) and then push new changes including version updates in separate commits. This is required to review the changes efficiently.
Adding a new service

[ ] Please ensure you've reviewed following guidelines including ARM resource provider contract and REST guidelines. Estimated time (4 hours). This is required before you can request review from ARM API Review board.

[ ] If you are blocked on ARM review and want to get the PR merged with urgency, please get the ARM oncall for reviews (RP Manifest Approvers team under Azure Resource Manager service) from IcM and reach out to them.

Breaking Change Review Checklist
If there are following updates in the PR, ensure to request an approval from Breaking Change Review Board as defined in the Breaking Change Policy.

[ ] Removing API(s) in stable version
[ ] Removing properties in stable version
[ ] Removing API version(s) in stable version
[ ] Updating API in stable or public preview version with Breaking Change Validation errors
[ ] Updating API(s) in public preview over 1 year (refer to Retirement of Previews)

Action: to initiate an evaluation of the breaking change, create a new intake using the template for breaking changes. Addition details on the process and office hours are on the Breaking change Wiki.
Please follow the link to find more details on PR review process.

@wwendyc please clarify the purpose of this update in PR description, and go through all the checks

@jianyexi This PR is to correct our Swagger for PS Cmdlets, not a breaking change. Please take a look.

@jianyexi Jianye Xi FTE This PR is to correct our Swagger for PS Cmdlets, not a breaking change. Please take a look.

But your change introduced some breaking change , you should follow the below action:

Hi @wwendyc Wendy Chang FTE, one or multiple breaking change(s) is detected in your PR. Please check out the breaking change(s), and provide business justification in the PR comment and @ PR assignee why you must have these change(s), and how external customer impact can be mitigated. Please ensure to follow breaking change policy to request breaking change review and approval before proceeding swagger PR review.
Action: To initiate an evaluation of the breaking change, create a new intake using the template for breaking changes. Addition details on the process and office hours are on the Breaking change Wiki.
If you want to know the production traffic statistic, please see ARM Traffic statistic.
If you think it is false positive breaking change, please provide the reasons in the PR comment, report to Swagger Tooling Team via https://aka.ms/swaggerfeedback.

Need to update


MemcpyContinueCopying

Continues copying memory elements, decrementing the remaining length and setting a flag to continue if more elements are to be copied.
Reference: https://github.com/starkware-libs/cairo-lang/blob/efa9648f57568aad8f8a13fbf027d2de7c63c2c0/src/starkware/cairo/common/memcpy.cairo#L24
Depends on #245

Hey @cicr99, I want to help with this if it's ok!

Hey @danielcdz sure! I just assigned you to it. Let us know if you have any questions

Hey @cicr99 ! this is my first time contributing to OSS, for this issue, I was researching and I think that it is ok to follow the instructions of this readme, and follow as an example this pr, what do you think? and is there another way to communicate and have more context about the project, maybe a Telegram group or chat?

Hello! @cicr99 I opened a draft pr, I'm not sure if I'm solving the issue as we want, here is the pr, it would be great if someone can help me a bit!

Hey @danielcdz sorry for such long answer. I have left some comments on the PR. Overall it looks really good and this is the right direction. If you will still be working on it, try to add some tests as well


Get Kibana variables from tfvars file

https://trello.com/c/cJzG0VYS/132-2-update-log-streaming-lambda-to-send-logs-to-ccss-logit-stacks
It's no longer in JSON format (https://github.com/Crown-Commercial-Service/digitalmarketplace-credentials/pull/370), so we need to change how we extract them.

Yes, this is very fragile. I think that's OK because this script is run very infrequently.

Doesn't work with the CCS Kibana, unfortunately. Not sure why. I can do it manually, though, so it's not worth spending any more time on this


Possible missing IAM role policy - 403 AccessDenied for GET HEAD

Just a heads up, something using the media MediaConvert role is triggering HTTP 403 on both mp4 and abr buckets.
be9fe0fecc654069de91eae291bd5c9ced5738e6ee018e8fe406a46d35a1b5a9 [redacted]-mp4destination-[redacted] [01/Nov/2018:00:28:18 +0000] <IP_ADDRESS> arn:aws:sts::[redacted]:assumed-role/[redacted]-MediaConvertRole-[redacted]/EmeSession_[redacted] 232D99AD8CED877E REST.HEAD.BUCKET - "HEAD /[redacted]-mp4destination-[redacted] HTTP/1.1" 403 AccessDenied 243 - 9 - "-" "-" -

I fixed this by adding the non-wildcard arn of the bucket, and the log was misleading, i believe the permission was ListBucket which fails without the root resource arn
{
    "Version": "2012-10-17",
    "Statement": [
        {
            "Sid": "VisualEditor0",
            "Effect": "Allow",
            "Action": "execute-api:Invoke",
            "Resource": "arn:aws:execute-api:us-east-1:[redacted]:*"
        },
        {
            "Sid": "VisualEditor1",
            "Effect": "Allow",
            "Action": "s3:*",
            "Resource": [
                "arn:aws:s3:::[redacted]-source-[redacted]",
                "arn:aws:s3:::[redacted]-mp4destination-[redacted]",
                "arn:aws:s3:::[redacted]-abrdestination-[redacted]",
                "arn:aws:s3:::[redacted]-source-[redacted]/*",
                "arn:aws:s3:::[redacted]-mp4destination-[redacted]/*",
                "arn:aws:s3:::[redacted]-abrdestination-[redacted]/*"
            ]
        }
    ]
}

@shsenior btw, great job on this solution. extremely helpful as a jumping off point.


GITHUB_PRIVATE_KEY Issue

Hello, i'm trying to run your exporter but i'm having trouble setting up the GITHUB_PRIVATE_KEY , i get the following error:
github_runner_exporter     | INFO:root:Starting metrics server
github_runner_exporter     | Traceback (most recent call last):
github_runner_exporter     |   File "/usr/local/lib/python3.10/site-packages/jwt/algorithms.py", line 350, in prepare_key
github_runner_exporter     |     RSAPrivateKey, load_pem_private_key(key_bytes, password=None)
github_runner_exporter     |   File "/usr/local/lib/python3.10/site-packages/cryptography/hazmat/backends/openssl/backend.py", line 494, in _handle_key_loading_error
github_runner_exporter     |     raise ValueError(
github_runner_exporter     | ValueError: ('Could not deserialize key data. The data may be in an incorrect format, it may be encrypted with an unsupported algorithm, or it may be an unsupported key type (e.g. EC curves with explicit parameters).', [<OpenSSLError(code=503841036, lib=60, reason=524556, reason_text=unsupported)>])

How should this key added into secret? do i need to format it somehow ?
Thanks

Hi @littlej956 ,
Try to create the secret like:
kubectl create secret generic github-secrets --from-literal=GITHUB_PRIVATE_KEY="-----BEGIN RSA PRIVATE KEY-----
123
456
789
-----END RSA PRIVATE KEY-----"

And set the helm chart values with:
env:
...
- name: GITHUB_PRIVATE_KEY
  valueFrom:
    secretKeyRef:
      key: GITHUB_PRIVATE_KEY
      name: github-secrets

Hello, i got it working in kubernetes and i wanted to run this in a docker-compose setup too and had some issues with the file. Got it working now, will leave it here for anyone else who needs this in a docker-compose setup.
services:
    github_runners_exporter:
        image: tchelovilar/github-org-runner-exporter:0.2.2
        container_name: github_runner_exporter
        environment:
        - OWNER=owner
        - GITHUB_APP_ID=12312312
        - |
          GITHUB_PRIVATE_KEY=-----BEGIN RSA PRIVATE KEY-----
          xxxxxxxx
          xxxxxxxx
          xxxxxxxx
          -----END RSA PRIVATE KEY-----
        - LOG_LEVEL=DEBUG


Cannot run example

Hello, when I run your example in the examples folder, I get an error:

/Users/igorganapolsky/workspace/git/Andreww6/gists/venv/bin/python /Users/igorganapolsky/workspace/git/Andreww6/gists/main.py
Traceback (most recent call last):
File "/Users/igorganapolsky/workspace/git/Andreww6/gists/venv/lib/python3.11/site-packages/stix2/datastore/taxii.py", line 163, in init
if collection.can_read:
^^^^^^^^^^^^^^^^^^^
File "/Users/igorganapolsky/workspace/git/Andreww6/gists/venv/lib/python3.11/site-packages/taxii2client/v21/init.py", line 285, in can_read
self._ensure_loaded()
^^^^^^^^^^^^^^^^^^^^^
File "/Users/igorganapolsky/workspace/git/Andreww6/gists/venv/lib/python3.11/site-packages/taxii2client/v21/init.py", line 354, in _ensure_loaded
self.refresh()
^^^^^^^^^^^^^^
File "/Users/igorganapolsky/workspace/git/Andreww6/gists/venv/lib/python3.11/site-packages/taxii2client/v21/init.py", line 368, in refresh
response = self.__raw = self._conn.get(self.url, headers={"Accept": accept})
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/Users/igorganapolsky/workspace/git/Andreww6/gists/venv/lib/python3.11/site-packages/taxii2client/common.py", line 310, in get
raise e
^^^^^^^
File "/Users/igorganapolsky/workspace/git/Andreww6/gists/venv/lib/python3.11/site-packages/taxii2client/common.py", line 300, in get
resp.raise_for_status()
^^^^^^^^^^^^^^^^^^^^^^^
File "/Users/igorganapolsky/workspace/git/Andreww6/gists/venv/lib/python3.11/site-packages/requests/models.py", line 1022, in raise_for_status
raise HTTPError(http_error_msg, response=self)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
requests.exceptions.HTTPError: 403 Client Error: Forbidden for url: http://<IP_ADDRESS>:5000/trustgroup1/collections/91a7b528-80eb-42ed-a74d-c6fbd5a26116/

During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/Users/igorganapolsky/workspace/git/Andreww6/gists/main.py", line 39, in
main()
^^^^^^
File "/Users/igorganapolsky/workspace/git/Andreww6/gists/main.py", line 13, in main
taxii = stix2.TAXIICollectionSource(collection)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/Users/igorganapolsky/workspace/git/Andreww6/gists/venv/lib/python3.11/site-packages/stix2/datastore/taxii.py", line 172, in init
raise DataSourceError(
^^^^^^^^^^^^^^^^^^^^^^
stix2.datastore.DataSourceError: The underlying TAXII Collection resource defined in the supplied TAXII Collection object provided could not be reached. Recieved error: "403 Client Error: Forbidden for url: http://<IP_ADDRESS>:5000/trustgroup1/collections/91a7b528-80eb-42ed-a74d-c6fbd5a26116/"
Process finished with exit code 1

Looks like a permission error.  Did you run it with medallion as the TAXII server?  Did you use the configuration and data included with that project?

I just used the default config.  I did not set up a separate TAXII server.  Do I need to?


Friendly suggestion

It would be great if the volunteer's names can hyperlink to their twitter profiles so that visitors can know more about them instantly :)

Hi @JSinfant, we are planning to add more tags with bio to porfile card for users to know more about the volunteer.


Fixed flags errors

The errors were basically on the app variable in the main.go files. I fixed it by just removing the second argument of value 0 and adding gio.applicationFlags(gio.applicationFlagsNone))(sorry for the repetitive name of the commits!).

Just gio.ApplicationFlagsNone should work; no need for the type conversion.

Done !


Persist assigned scene after map edit

As mentioned in the README, currently any modifications to rooms in the Map Editor will remove assigned scenes. I think having some basic scene persistence will be a good QOL improvement, especially for devs who edits their room often.
Since there's a lot of ambiguity of how to maintain assigned scene when editing cells, I have an outline for how the assign scene can be determined after a map edit. The gist of it is to try to maintain assigned scene even when there is ambiguity based on a few factors, to make it as seamless as possible.
Cells Removed

If any room remains intact, keep the assigned scene.
If any room is split into multiple parts, have a consistent logic to determine how to keep the assigned scene (like always favor the assigned scene of the top-left-most cells).

Cells Moved

Always maintain cell assigned scene after the move.
If cells are moved on top of another room, prioritize the selected room prior to the move. (I forgot if the behavior here merges room or create border, will check and update later)

Cells Added

If any room is expanded, keep the assigned scene.
Prioritize assigned scene id of the room closest to the starting point of the draw action. For example, if you start drawing a line from Room A to Room B into a single large room, the logic will assume that the combined new room is Room A.

An alternative, simpler to implement system could also be to only maintain assigned scene when there is no ambiguity, and clear the scene otherwise. I haven't looked into the Map Editor code yet, so that could be a factor on how difficult this is to implement.
Let me know what you think.

The reason scene is removed is a technical one. The rooms need to maintain consistency, that is a room may have a single scene assigned and each scene can be assigned only to up to one room.

If any room is split into multiple parts, have a consistent logic to determine how to keep the assigned scene (like always favor the assigned scene of the top-left-most cells).

I'd first need to determine that new rooms were created, which currently is not tracked.

Cells Moved

If you mean drag and drop, it should already retain the scenes. It's impossible to change room composition by dragging them, so there are no problems here.

If any room is expanded, keep the assigned scene.

Like in the first case, I'd have to detect that a room is being expanded and it does not interest with any other room.

if you start drawing a line from Room A to Room B into a single large room, the logic will assume that the combined new room is Room A.

That sounds complicated to do >_>
I may look into what you suggested, but no promises here. The code for assign management is already complex, and I didn't want to complicate it even more.

Thanks for the clarification, I was also wondering if there were other technical reasons for this limitation. Wasn't aware rooms are retained when cells are dragged; that was one of the main things I wanted since I was planning on moving a large chunk of my map, so that should already address half of this.


microsoft-edge-beta: 120.0.2210.22 -> 120.0.2210.61

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for microsoft-edge-beta is: The web browser from Microsoft
meta.homepage for microsoft-edge-beta is: https://www.microsoft.com/en-us/edge
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 120.0.2210.61 with grep in /nix/store/jxl0z7y11aq9wim1180pmi12q65z7k07-microsoft-edge-beta-120.0.2210.61
found 120.0.2210.61 in filename of file in /nix/store/jxl0z7y11aq9wim1180pmi12q65z7k07-microsoft-edge-beta-120.0.2210.61

Rebuild report (if merged into master) (click to expand)

3 total rebuild path(s)

3 package rebuild(s)

First fifty rebuilds by attrpath
microsoft-edge
microsoft-edge-beta
microsoft-edge-dev

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/jxl0z7y11aq9wim1180pmi12q65z7k07-microsoft-edge-beta-120.0.2210.61 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A microsoft-edge-beta https://github.com/r-ryantm/nixpkgs/archive/194e8b9d4c7ff41862faa93abd5131c26a3c0109.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/194e8b9d4c7ff41862faa93abd5131c26a3c0109#microsoft-edge-beta

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/jxl0z7y11aq9wim1180pmi12q65z7k07-microsoft-edge-beta-120.0.2210.61
ls -la /nix/store/jxl0z7y11aq9wim1180pmi12q65z7k07-microsoft-edge-beta-120.0.2210.61/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package failed to build:

microsoft-edge-dev

2 packages built:

microsoft-edge
microsoft-edge-beta

Maintainer pings
cc @zanculmarktum @kuwii @rhysmdnz for testing.

done in #273872


Php - JS - HTML mixed code coloring/highlighting doesn't work whil in PHP language mode

VSCode Version: 1.40
OS Version: Linux Ubuntu 18.04

Steps to Reproduce:

Open a php file
Be sure that VS Code is in PHP Language Mode
Write php, js & html in this same file
Notice that only php expressions are highlighted. Js & Html expressions are seen as a plain non-formatted text.

Does this issue occur when all extensions are disabled?: Yes/No
Yes, disabling / re-enabling php extensions didn't change anything.
I have to rollback to VS Code 1.39 update 2 version, in order to continue my coding.

Please share a sample file and a screenshot, and tell me what theme you are using.

I d already explained the re-produce scenario.
I am using at the moment 1.39.2, which is fine. In order to provide you screenshot, I have to re-upgrade my VS Code to 1.40, which is not possible for me because after that I will have to re-downgrade to 1.39.2 in order to continue my work.
I think I was sufficiently clear with the case.


THRIFT-3978: tighten up pthread mutex implementation, removing asserts and replacing them with exceptions

For anybody interested in reviewing this pull request, I pretty much followed the logic that boost::mutex is using with one exception.  In cases where boost ignores an error condition to avoid throwing in a destructor, I have instead preferred to abort the process.  My thought process on this is that should mutex destruction return EBUSY or EINVAL, it is a design flaw in the implementation using the Mutex class.  EBUSY means we tried to delete the mutex while it was locked.  EINVAL means it may have been destroyed twice.  In either case, getting a core is way more useful than silently letting the issue pass by in a release build.


upnp fails with conflicting  mappings

2018/04/24 10:28:38.363906 upnp.go:126: WARN: could not automatically forward port 23112: goupnp: SOAP request got HTTP 500 Internal Server Error:
<s:Envelope xmlns:s="http://schemas.xmlsoap.org/soap/envelope/" s:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/">
<s:Body>
<s:Fault>s:ClientUPnPError718Mapping conflicts</s:Fault> </s:Body>
</s:Envelope>

I noticed this as well today when testing a bit on my home network. Happened once, and disappeared on its own after starting the daemon again.

when the daemon is closed nicely, the mappings are removed.


Can't get microsoft/nanoserver image

Expected behavior
Actual behavior
Kept retrying when doing docker pull microsoft/nanoserver
Information about the Issue
unknown blob shown
Steps to reproduce the behavior

Command "docker pull microsoft/nanoserver"
After sometime, it would timeout and show as unknown blob

Although it is not obvious at first, the image does have the following short:
Nano Server base OS image for Windows containers

This means that unless you're on Windows Pro and have set your preference to be 'use Windows Containers' this image will not work for you.


Options for different modes of documentation are not available when the Help Pane is undocked.

Issue Report Checklist

[ ] Searched the issues page for similar reports
[ ] Read the relevant sections of the Spyder Troubleshooting Guide and followed its advice
[ ] Reproduced the issue after updating with conda update spyder (or pip, if not using Anaconda)
[ ] Could not reproduce inside jupyter qtconsole (if console-related)
[ ] Tried basic troubleshooting (if a bug/error)

[ ] Restarted Spyder
[ ] Reset preferences with spyder --reset
[ ] Reinstalled the latest version of Anaconda
[ ] Tried the other applicable steps from the Troubleshooting Guide

[ ] Completed the Problem Description, Steps to Reproduce and Version sections below

Problem Description
Options for the pane's menu are deactivated when the pane is undocked

What steps reproduce the problem?

What is the expected output? What do you see instead?
Paste Traceback/Error Below (if applicable)

PASTE TRACEBACK HERE

Versions

Spyder version:
Python version:
Qt version:
PyQt version:
Operating System name/version:

Dependencies

PASTE DEPENDENCIES HERE

@ccordoba12 @dalthviz

@dalthviz, please take a look at this one ASAP.


Add soil tutorials

Purpose
Add in soil tutorials demonstrating how to run richards equation alone, and the full problem, and a phase change tutorial.
#118  -- will close
Review checklist
I have:

followed the codebase contribution guide: https://clima.github.io/ClimateMachine.jl/latest/Contributing/
followed the style guide: https://clima.github.io/ClimateMachine.jl/latest/DevDocs/CodeStyle/
followed the documentation policy: https://github.com/CliMA/policies/wiki/Documentation-Policy
checked that this PR does not duplicate an open PR.

In the Content, I have included

relevant unit tests, and integration tests,
appropriate docstrings on all functions, structs, and modules, and included relevant documentation.

[x] I have read and checked the items on the review checklist.

bors r+


654 updated database documentation

Basics

[x] I added a line to /doc/CHANGELOG.md
[x] The PR is rebased with current master.

[x] References to issues, e.g. close #X, are in the commit messages.
[ ] The buildserver is happy.

Checklist

[ ] I have installed and I am using pre-commit hooks
[ ] I fully described what my PR does in the documentation
(not in the PR description)
[ ] I fixed all affected documentation
[ ] I fixed the introduction tour
[ ] I wrote migrations in a way that they are compatible with already present data
[ ] I fixed all affected decisions
[ ] I added unit tests for my code
[ ] I added code comments, logging, and assertions as appropriate
[ ] I translated all strings visible to the user
[ ] I mentioned every code or binary not directly written or done by me in reuse syntax
[ ] I created left-over issues for things that are still to be done
[ ] Code is conforming to our Architecture
[ ] Code is conforming to our Guidelines
(exceptions are documented)
[ ] Code is consistent to our Design Decisions

Review

[ ] I've tested the code
[ ] I've read through the whole code
[ ] Examples are well chosen and understandable

@temmey let us get this done, please request review when you are ready and/or set labels accordingly

@temmey let us do this first, it basically only needs that you reread your own text and rebase it.

I would argue to remove the table descriptions. Ideally they would be somehow automatically generated from the rust table definitions such that we only have a single source of truth, but as it stands I anticipate them to always be out of sync.

If we don't find some minimal descriptions that are still useful to get an overview, we can also get rid of this documentation completely.
What speaks to maybe keep it: It was mostly used to design the relations and might be useful when we do non-trivial extensions.
We can today also speak a bit about how to document GIS systems.


ERROR: 0:5: '' : cannot evaluate offset into the vector

[Shaders, screenshots, error log, etc.] [ZIP]
variant_14_reduced_216_simplified.frag:
#version 440

void triangle(int x)
{
    mat4x3(1.0)[x][2];
}

Compile error log:
ERROR: 0:5: '' : cannot evaluate offset into the vector

Reported:
https://software.intel.com/en-us/forums/graphics-driver-bug-reporting/topic/703555


Select2 4.0.0 beta.3 - dropdown does not follow select2 select box

@kevin-brown Congrats on the the Beta.3 release.
Our testers are reporting an issue with the dropdown on the select2. Note, this is unlikely related to any changes in Beta.3.
Essentially, we have a resizable text area element above the select2. If the dropdown is open, and the textarea is resized, the select2 box moves around the page, but the dropdown seems to float in place.
I'm not sure if this is captured in another open issue - it might be related to the window resize issue reported earlier.
I have created a plunker to demonstrate the issue.
Code from plunker:
<!DOCTYPE html>
<html>

  <head>
    <script data-require="jquery@*" data-semver="2.1.3" src="https://code.jquery.com/jquery-2.1.3.min.js"></script>
    <script src="https://select2.github.io/dist/js/select2.full.js"></script>
    <link href="https://select2.github.io/dist/css/select2.min.css" type="text/css" rel="stylesheet" />
  </head>

  <body>
    <textarea rows="4" cols="50">
    </textarea>

    <select style="width: 100%">
      <option value="0">one</option>
      <option value="1">two</option>
      <option value="2">three</option>
      <option value="3">four</option>
    </select>
    <script type="text/javascript">
      $('select').select2({
  placeholder: "Select a color",
});
    </script>
  </body>

</html>

One quick update: It appears to be isolated to the Chrome browser.

I've confirmed that this issue doesn't happen in IE or Firefox. Chrome does not trigger the mousedown event that we are looking for when it is resized, so Select2 currently has no way of knowing that the size has changed.
The resize even that is most likely triggered also does not bubble, so there isn't much that can be done on our side. I'm going to file a bug with Chromium to see what their thoughts are.

@kevin-brown @fk Seems the Chrome Ticket has been resolved as of December 2015. I think we can close this.

Looks like this finally landed in Chromium 49.0.2587.0 which appears to have become the stable branch a few weeks ago. Closing this off as I can no longer reproduce the issue.


Create schema-rich format for enrich good stream

Use schema-rich format for Enrich stage good stream output
Hi Team,
I think there are multiple threads and discussions around this topic. I could find most of them outdated or cold.
I am personally a big fan of the Snowplow platform and recently started building it for my organization from scratch on the GKE Kubernetes cluster.
It's been a challenging but progressing journey until now. But at this stage, I feel like there are going to be long-term caveats and challenges around the TSV output from the Enrich stream.
We have both batch and stream processing pipelines in the downstream, serving both offline and online teams at a wider level.
Caveats around TSV seem to be crucial due to it's cascaded complexity and bottlenecks downstream.
I am seeking some clarity on roadmaps around this case. Please suggest.
Thank you
Jay

Hi @devorbit,
Could you clarify what you mean by “schema-rich format”?
The TSV output is not meant to be consumed directly. For loading into warehouses, we have dedicated loaders. For real-time apps, we recommend one of our Analytics SDKs that parse the TSV for you. You can also use Snowbridge with TSV to JSON conversion.

Hi @stanch  Thank you for your thoughts on this. Let me explain my case here.
I am using Kafka and GCP for my Snowplow setup. And here are some of the caveats that I have to deal with upfront.

No Kafka to Bigquery Loader:
Currently, the loaders don't include the Kafka source for the BQ destination. So I setup Snowbridge for Kafka to pub/sub replication and this works with additional cost and caveats.

No support for Kafka to GCS BigLake Loader:
The second issue that we are facing is loading TSV events from Kafka/PubSub to GCS as Iceberg tables. Considering the fact the BQ only support Iceberg for BigLake, but Snowplow do not support Iceberg sinks as of now.

Limitations with the Analytics SDK:
If you look into the SDK examples, it seems more friendly to batch pipelines in Spark not for the streaming. And for streaming use cases we need to have some sort of Event's and Contexts' schema for deserialisation and processing.

So my reference to schema-rich format was, to some degree, to develop a direction for simplifying the data processing downstream , by providing a library to create shemas by may be stitching the event and the contexts in some way for simplification.
I could be wrong or may not have very good understanding of the Snowplow sdks. You can suggest me a work-around in that case.


Allow to open workflow logs in new tab

The new logging facility option is really great and super useful (https://github.com/argoproj/argo/pull/2443)
While the pod log link allows to be opened in a new tab (or directly cmd+click), the same doesn't work for the workflow link on the top.
Is it possible to enable this for the top workflow log link as well?

Would you like to submit a PR to fix this?

I'm sorry but having never done any html/javascript/typescript/react and judging from a quick look (seeing that the buttons in the pod links are directly styleable and seeing that the buttons from the workflow links come from some more generic page/toolbar and given your comment here https://github.com/argoproj/argo/pull/2443/files#diff-a19f113f6e39d3f31c1d1e776cdf84b3R388) I fear that I'm not capable of changing the code with reasonable efforts.


Symlink post request

After the symlink is changed (meaning the files have been updated), git-sync sends a POST request to the configured url.
This is useful when using services such as Prometheus, where an action (like a POST request) is necessary in order to refresh configuration.

@diericx I think this looks fine. Are you planning to upstream it to the kubernetes org? If so, we should probably got that process going. PubNub already has a contributor agreement with the CNCF, so that's at least one hurdle already cleared.

@parasyte just sent the PR, but it looks like we haven't signed this specific CLA for google or something. Emailed Adam about it, might take a little while to resolve :/


rettypes: name some return types for convenience

I think this is not something we should include. This bloats the API for no reason (which is already large enough). Thanks nevertheless.


Reorganize templates in subdirectories

Fixes #1.
Needs modifications in the swiftgen CLI code.

@AliSoftware this is the subdir PR that I mentioned. The only thing it does is move the templates, and modify the testing code to handle these changes.
The only annoyance remains the iOS/macOS storyboards thing. Eventually I'd like to somehow merge these two, they are quite similar. But that'd be something for another issue/PR.

Renaming default to swift2 will be handled in a separate PR, right?

The swiftgen branch already points to this one, and I just tried the install, it works correctly.

Regarding your default->swift2 comment, yeah, I'm splitting everything up in small(-ish) steps.


[WIP / DO NOT REVIEW] Store batch errors

pushing up to review one piece of this, still needs changes

replacing with #743


delayed SSL handshakes for SMTP

@an-tao Hi, I am trying to develop a SMTP client with trantor's TCPClient. A delayed SSL handshake is needed for such communicatoin. I am encounting an issue on the SSL handshake part. As long as the transfer from TCP to SSL handshake is needed for authentication, the SMTP server will reject the connection. I am using the function from TCPClient, e.g. "tcpClientPtr_->enableSSL();" which does not work for such connection. The workflow is as following,

Initiate TCP client --> server (OK)
Server --> client (OK)
EHLO client --> server (OK)
Server --> client (OK)  /Server invites an SSL connection/
SSL client --> server (Failed)  /called tcpClientPtr_->enableSSL(); and send information/

My guess would be "enableSSL()" does not actually perform a replacement from the TCP to SSL connection immediately. If not so, how should I perform an upgrade connection at that instant ?

@ihmc3jn09hk Hi, Currently, an SSL connection performs an SSL handshake before any other transmissions, so I have to add some new methods to Trantor to implement a delayed SSL handshake. I'll do this, thanks.

@an-tao Cool thanks. I am looking at it as well. Possible reference here.

@ihmc3jn09hk , I made a new PR to trantor for this issue, please check, thx!

@an-tao Thats quick response. I am still studying trantor, lolz. I will test it sometime soon.

@an-tao Good news, the code for delay SSL is working fine for sending email with SMTP. I modified some of the code in drogon which hopefully you will think is appropreate. please check the PR.
In order to test and use it, I have made a SMTP-Mail plugin with the Drogon framework. It is working and feel free to use the example in the wiki for the plugins tutorial if you wish.

btw, I am going to new an issue for http/2 and http/3 (http/2 + quic) functionality enhancement.

@an-tao The PR is reporting error. The following is part of the log which related to trantor. I did not modify trantor in this PR and it's dead at something unrelated to the project ? Just for noticing the issue should not be related to the PR.
opt/src/get_version.sh: not found
...
[2020-02-14 17:35:54] [build] [ 12%] Building CXX object trantor/CMakeFiles/trantor.dir/trantor/net/inner/TcpConnectionImpl.cc.o
[2020-02-14 17:35:58] [build] [ 12%] Building CXX object trantor/CMakeFiles/trantor.dir/trantor/net/inner/Timer.cc.o
[2020-02-14 17:36:00] [build] [ 13%] Building CXX object trantor/CMakeFiles/trantor.dir/trantor/net/inner/TimerQueue.cc.o
[2020-02-14 17:36:03] [build] [ 14%] Building CXX object trantor/CMakeFiles/trantor.dir/trantor/net/inner/poller/EpollPoller.cc.o
[2020-02-14 17:36:06] [build] [ 14%] Building CXX object trantor/CMakeFiles/trantor.dir/trantor/net/inner/poller/KQueue.cc.o
[2020-02-14 17:36:08] [build] [ 15%] Building CXX object trantor/CMakeFiles/trantor.dir/trantor/net/ssl/SSLConnection.cc.o
[2020-02-14 17:36:11] [build] [ 15%] Building CXX object trantor/CMakeFiles/trantor.dir/trantor/net/inner/AresResolver.cc.o
[2020-02-14 17:36:14] [build] [ 16%] Linking CXX static library libtrantor.a
[2020-02-14 17:36:14] [build] [ 16%] Built target trantor
[2020-02-14 17:36:15] [build] Scanning dependencies of target makeVersion
[2020-02-14 17:36:15] [build] /bin/sh: 1: /opt/src/get_version.sh: not found
[2020-02-14 17:36:15] [build] make[2]: *** [CMakeFiles/makeVersion.dir/build.make:57: makeVersion] Error 127
[2020-02-14 17:36:15] [build] make[1]: *** [CMakeFiles/Makefile2:73: CMakeFiles/makeVersion.dir/all] Error 2
[2020-02-14 17:36:15] [build] make: *** [Makefile:130: all] Error 2
[2020-02-14 17:36:15] [build] + '[' -f setup.py ']'
[2020-02-14 17:36:15] [build] + echo 'Semmle autobuild: no supported build


[B16] Using Salis Mundus to create Workbench, Thaumonomicon, or Cauldron all result in a crash.

Well, the title clears it out pretty well. I tried it without mods, and with them, although its probably an Optifine bug since Optifine is only really good for lag issues, and not mods. But without it, or any other mods in play, using Salis Mundus to turn the bookshelf into the Thaumonomicon, or any such with that ingredient, results in a total crash that causes the game to shut off, and have to be restarted in order to get it working. - Dainn/Einar

are you sure that you are on B16 and not on B15?

Without a log I can't do much so closing this for now.


Prometheus: 2.30.3 -> 2.35.0

Signed-off-by: Julien Pivotto<EMAIL_ADDRESS>Description of changes

Things done

Built on platform(s)

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

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

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

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

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

[ ] Fits CONTRIBUTING.md.

Maybe mark this as draft until stable 2.35 release, just in case?

$ nix build  .#prometheus
error: builder for '/nix/store/vd3zil9bbd6zlj51ahzpkbgsfcibw2pf-prometheus-2.35.0-go-modules.drv' failed with exit code 1;
       last 6 log lines:
       > unpacking sources
       > unpacking source archive /nix/store/lqbah4qvswff5vc065lrcidss9k358jm-source
       > source root is source
       > patching sources
       > configuring
       > building
       For full logs, run 'nix log /nix/store/vd3zil9bbd6zlj51ahzpkbgsfcibw2pf-prometheus-2.35.0-go-modules.drv'.
error: 1 dependencies of derivation '/nix/store/w3gf9pvlsixfva4nrg588l8c5kfv3ssf-prometheus-2.35.0.drv' failed to build

(I don't know why this does not work)

Fixed and ready to go!

Is 2.35 stable yet?

LGTM, tested on x86_64-linux through gh pr checkout 168706 && nix -vL build .#nixosTests.prometheus.

Can this be merged?

please use prometheus (the attribute name) as the commit msg, then ofborg will build the package and tests

like this?

Should we try reenabling tests?

I'd even try enabling Darwin too, it's been almost half a year of new releases, we can always turn it back off if it breaks.

I'd even try enabling Darwin too, it's been almost half a year of new releases, we can always turn it back off if it breaks.

prometheus tests are still broken in darwin.

Is that a known upstream thing?

yes, I remember someone complained a few days ago (without filling a github issue).

Can also confirm aarch64-linux tests pass on my pretty considerably resource constrained Pi4, so we should be good here.


test: (e2e update ) refactor and stablize tests

Closes #
Describe your proposed changes here.

Refactored:

Configuration

More rational use of config profiles with user definitions
Use environment variables for sensitive information

REST calls - now use JS Client library

Updated Selectors to match most recent nightly builds

Latest pro forma results:
https://ec2-13-56-214-192.us-west-1.compute.amazonaws.com:8443/view/Chron-Sel/job/influxdbv2-selenium-bonitoo/37/cucumber-html-reports/overview-features.html

[ ] CHANGELOG.md updated with a link to the PR (not the Issue)
[ ] Well-formatted commit messages
[ ] Rebased/mergeable
[ ] Tests pass
[ ] http/swagger.yml updated (if modified Go structs or API)
[ ] Documentation updated or issue created (provide link to issue/pr)
[ ] Signed CLA (if not already signed)

Don't worry about the semantic commit, that can be done when we merge


when run test driver on android simulator  , can not access internet connection

i used test driver to automate location permission  with android  simulator
, but when i run test driver , application can not access   internet connection,
،
this is the error after run
VMServiceFlutterDriver: Flutter Driver extension is taking a long time to become available. Ensure your test app (often "lib/main.dart") imports "package:flutter_driver/driver_extension.dart" and calls enableFlutterDriverExtension() as the first call in main().
and there is a  warning
Warning: At least one test in this suite creates an HttpClient. When
I/flutter ( 5447): running a test suite that uses TestWidgetsFlutterBinding, all HTTP
I/flutter ( 5447): requests will return status code 400, and no network request will
I/flutter ( 5447): actually be made. Any test expecting a real network connection and
I/flutter ( 5447): status code will fail.
I/flutter ( 5447): To test code that needs an HttpClient, provide your own HttpClient
I/flutter ( 5447): implementation to the code under test, so that your test can
I/flutter ( 5447): consistently provide a testable response to the code under test.
this is my test driver code
flutter drive
--driver=test_driver/main_test.dart
--target=integration_test/unify_test.dart
-d emulator-5554
@darshankawar

Hi @AhkamKhalaaf, please provide a minimal, reproducible example and the output of flutter doctor -v.

Can you provide the code samples you are using? Check this link on how to provide a reproducible sample so that we can investigate


JsonPipe incorrectly translates a json null to a XML string null instead of

❗ please do not add sensitive information in issues, you can provide extra information via email using issue number as reference ❗
Describe the issue
JsonPipe incorrectly translates a json null to a XML string <obj>null</obj> instead of <obj xsi:nil="true" />. This breaks all xslt/xpath functions that do anything based on null or empty nodes, as the translated json null is now not empty anymore and also isn't considered null in XML because the xsi:nil is missing.
Reporter
Marcel

To Reproduce
Steps to reproduce the behavior:

Go to '...'
Click on '....'
Scroll down to '....'
See error

Screenshots
If applicable, add screenshots to help explain your problem.
Configuration
Please provide the configuration of the Pipe or Receiver with the problem.

Input
Please provide an example of the input message.
Alternatively, provide a Ladybug report.

Environment
FF! 7.8-20220607.121930: Frank2zgw
Running on LAPTOP-UKAI1A6 using Apache Tomcat/9.0.56
Java Version: OpenJDK Runtime Environment (1.8.0_292-b10)
Heap size: 727M, total JVM memory: 937M
Free disk space: 271GB, total disk space: 464GB
Up since: 2022-06-08 18:03:55 (30m)

Additional Environment

DBMS: [e.g. Oracle, MSSQL, MariaDB, MySql, PostgreSQL]
Browser: [e.g. Chrome, Safari, Edge, Firefox]

Additional Context
Add any other context about the problem here. (f.e. ladybug report / test adapter with larva test)

it should also wordt the otherway around


Feature Request: Insert Data Using Inspector

Is your feature request related to a problem? Please describe.
Not really.
Describe the solution you'd like
I would like to easily manipulate (Insert/Update/Delete) the data using the inspector
Would be super nice to have this during development :smile:
Describe alternatives you've considered
creating temporary forms in my app to do the insertions.
Version

Platform: Android, Linux
Flutter version: 3.3.0
Isar version: 3.0.1

You can already update and delete data so this is a request to insert data.

so this is a request to insert data

Ah yes, my bad, I just wanted to explain what I meant by "manipulate".

It would be nice if Inspector supports importJsonRaw

This is implemented in the newest version.


chose smtp config

dear friend
in some site we have two or some smtp configuration in web Config.
I prefer to chose smtp config per email category.
who do you think?

Did you ever figure out to use multiple smtp servers?


Investigate why unit tests for backgrounds feature fail in CI but not locally

Some unit tests are skipped in #99 because they fail when running in CI. It looks like the ones that intercept the request for the image file request are the ones that fail, but need to investigate further.
https://github.com/arnellebalane/simple-todo/blob/9cd93926d1146a06af5a6ef8f0db05706e0e0909/src/features/backgrounds/index.spec.js#L6-L9

The unit tests have been migrated to use vitest in #119 and no longer uses Cypress for component testing.


FIX: AttributeError MouseMoveEvent on Qt6

This PR fixes the issue with the position of the event on Qt6.
This also reveals one of the weaknesses of our testing since we do not simulate clicks. I could take the time to address this in here if I can.
Related to https://github.com/pyvista/pyvistaqt/issues/20#issuecomment-1064069790

This is ready to go from my end @pyvista/pyvistaqt-admin


HV-2002 Fixing mod11 check for Titulo Eleitoral

https://hibernate.atlassian.net/browse/HV-2002
BVAL-791 - Fixing mod11 check to use '0' in case the rest of the division is 10, making the function to correct validate a Brazilian Titulo Eleitoral

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on licensing, please check here.

Thanks @marko-bekhta for the review! I added a few more test cases to the class, and fixed the "CPF" typo on the methods names


updates resource to ignore hashes and use main branch

I always feel unsecure about this. Earlier version used pooch with hashes for downloading from the tables master branch. The tables master branch is now fixed and I use main as default and pooch ignores hashes. At least, I don't break earlier versions then when i update the tables...

Codecov Report

Merging #53 (4a6b6c7) into master (cfd25f4) will decrease coverage by 0.13%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##           master      #53      +/-   ##
==========================================
- Coverage   81.24%   81.10%   -0.14%
==========================================
  Files          18       18
  Lines         677      672       -5
==========================================
- Hits          550      545       -5
  Misses        127      127

Flag
Coverage Δ

unittests
81.10% <100.00%> (-0.14%)
:arrow_down:

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

Impacted Files
Coverage Δ

cordex/core/tutorial.py
65.67% <100.00%> (+0.52%)
:arrow_up:

cordex/tables/_resources.py
85.18% <100.00%> (ø)

cordex/regions/_prudence.py
80.00% <0.00%> (-1.58%)
:arrow_down:

cordex/tables/__init__.py
100.00% <0.00%> (ø)

cordex/regions/_germany.py
100.00% <0.00%> (ø)


how to use DPP to start train_single_label.py

1  machine 2 GPUs
I cant use command line to start
how to start in the wInternal code  to use DDP
i cant find where to save mode, how to save in the DDP

give more details when you open an issue. what have you tried ?
Anyway, for DDP use stanard PyTorch multi-GPU command:
python -u -m torch.distributed.launch --nproc_per_node=2 train_single_label.py
currently, the script does not save the model. there is no special saving of DDP model, just torch.save(...) (on rank==0 only of course).
you are welcome to open a merge request for adding the saving feature.

when i use the above command
`
root@1ebda974bc7a:/home/ImageNet21K# python -u -m torch.distributed.launch --nproc_per_node=2 train_single_label.py --batch_size=4 --data_path=/mnt/dataset --model_name=mobilenetv3_large_100 --model_path=/home/ImageNet21K/mobilenetv3_large_100_miil_21k.pth --epochs=10

Setting OMP_NUM_THREADS environment variable for each process to be 1 in default, to avoid your system being overloaded, please further tune the variable for optimal performance in your application as needed.

creating model mobilenetv3_large_100...
creating model mobilenetv3_large_100...
done
done
`
the progarm seems block   stop and not  continue

By using "python -u -m torch.distributed.launch --nproc_per_node=2 train_single_label.py",I encounter the same problem

@jaffe-fly thanks for the feedback
i changed the order,  'torch.distributed.init_process_group' should be before model initialization.
please update and let me know if it was fixed.

@mrT23 Now it works well,Thanks alot!

@mrT23  its ok   thank you
but one warining
UserWarning: Detected call of `lr_scheduler.step()` before `optimizer.step()`. In PyTorch 1.1.0 and later, you should call them in the opposite order: `optimizer.step()` before `lr_scheduler.step()`.  Failure to do this will result in PyTorch skipping the first value of the learning rate schedule. See more details at https://pytorch.org/docs/stable/optim.html#how-to-adjust-learning-rate

thanks @jaffe-fly and @Stephen-Hao
the warning on lr_scheduler does not hurt the training results.


Ubuntu Support & user configurable wait/sleep time

Thank you for a great product.

Flintrock version: latest from git pull
Python version: 3.6
OS: ubuntu

Tried launching clusters (ubuntu AMI) failed launches many times. So upon investigation into the code these were the bottle-necks:

waiting to ssh to clusters (3 secs is way too less.) Can it be given from command/config?
It assumes that python already exists to download hadoop. Won't work if python does not exist. Could you please allow user given set of command we can pre-execute for dependencies.
assumes "yum install/remove"  can we make this user-driven optionally (to support apt install/remove)

still ran into issues for java based dependencies in ubuntu, so I dropped that route. But for Amazon linux at least user-driven wait-time and number of tries would be helpful.
thank you
Deb

Hi @pani6me!

Can you elaborate on what the issue is here? Flintrock polls for SSH availability every few seconds so it can start work as soon as possible. I don't understand what the problem is or why someone would want to control the polling interval.
Flintrock works best with Amazon Linux, but if you want to use an AMI that doesn't have Python installed by default, you can install Python as part of instance launch using the --ec2-user-data option.
Ubuntu support is tracked in #95. My comment there still captures my attitude towards Ubuntu: I'd support it if it didn't add much complexity or maintenance burden. But I doubt that is possible, which is why my default position is not to expand Flintrock's support matrix.

Thanks for the info @nchammas

No longer an issue when I used amz-linux.
I agree supporting ubuntu would be a constant support overhead, especially custom built AMIs.  --ec2-user-data is a great concept. If you could extend the concept of --ec2-user-data to include the install file for master and slave separately, then that would give the responsibility/power on the users to specify the correct commands for any linux system. I'll probably make this temporary hack for my use in local area. Then flintrock can put the installation logs for master and slave in some tmp area without reading into the logs/runs success/failure.
If above options for master/slave are available ubuntu support may not be needed.

I've reported #223 to capture the feature request for separate --ec2-user-data options.