Add support "add column statement with 'with values' when nullable" deploy option

I'm always frustrated when add column with default values and is nullable.
I always modify a statement as below.
before
ALTER TABLE [dbo].[TableName]
    ADD [ColumnName] VARCHAR (1) DEFAULT ('0') NULL;

after
ALTER TABLE [dbo].[TableName]
    ADD [ColumnName] VARCHAR (1) NULL DEFAULT ('0') WITH VALUES;

Describe the solution you'd like
Add deploy option that insert 'with values' to "ALTER TABLE ... ADD ..." statement.

@wesrivery Sorry for the delayed response, and Thank you for clear explanation with examples, very much appreciated and I'll get back to you with what my findings! Thanks.

This Issue has been fixed and will be available with the upcoming release of DacFx.
The syntax "WITH VALUES" for adding new column of NULL type to the existing table, the default constraint value will be going to update the rows of the new column. This can be done by the deployment option /p:GenerateSmartDefaults=true, default is false.

/p:
GenerateSmartDefaults=(BOOLEAN 'False')


[Feature Request] in the MessageBox is turned off by default and require different button * to cancel the operation, but only the catch component () and is the default cancel and closing is the same request, want to ask whether there are other ways to deal with the situation or component needs to be optimized?

Existing Component
Yes
Component Name
2.0
Description
谷歌

Closing the MessageBox means to cancel its operation, so we're not going to distinguish them. You can implement your own message box if you have such needs.


Weird hand pose - InputSimulationService

Describe the bug
When recording hand input via the InputRecordingService on the Hololens 2 and playing it via the InputPlaybackService, the joint poses are usually correct while I often observe weird handposes of the hand mesh (screenshot below). I don't observe that weird behaviour during testing in the Unity editor, only when deployed to the Hololens 2.
To reproduce
Record and play hand input on the Hololens 2 using InputRecordingService and InputPlaybackService.

 @RogPodge @cre8ivepark have you ever seen anything like this?

Also to note my comment above, since this is not so clear from the screenshot, only the hand mesh is affected, the joints are correct.

Yikes I never encountered this while recording the new set of hand poses. It might have to do with the joint rotations being weird even though the joint positions are correct? (Since the mesh deforms based on the rotations)
I don't think we have the time currently to dive deep into this, so for now I'd recommend just using the hand joint visualization for recording playback. We're looking to improve our hand pose recording system and expand on using it in the future, so stay tuned!

It is not only the hand pose that is affected, the recorded camera pose also occasionally flips by 180deg.
The hand tracking error can also be observed via holographic remoting.

Here is a video showing both the weird hand poses and the camera flipping back and forth.

Hi, I have tried a few different MRTK setups and am encountering this exact same issue with the head and joint rotations on playback.
Setup
Unity Version 2020.3.11f1
MRTK Version 2.7.0, 2.6.1, 2.5.4
Mixed Reality OpenXR Plugin 0.9.5
Attached is a quick, similar video showing the hand mesh deformations: video demo.

I believe one notable cause for this issue occurs in the optimization of the animation curves:
https://github.com/microsoft/MixedRealityToolkit-Unity/blob/119f16f59e7b4cd54142be29845c846bc2a2db12/Assets/MRTK/Core/Providers/InputAnimation/InputAnimation.cs#L534
Which, in this case, leads to the optimization of rotation curves defined here: https://github.com/microsoft/MixedRealityToolkit-Unity/blob/119f16f59e7b4cd54142be29845c846bc2a2db12/Assets/MRTK/Core/Providers/InputAnimation/InputAnimation.cs#L1216
The RotationW keys are removed during this optimization and the length of the RotationW curves for certain joints become 1. Then, when you playback an animation file, some joints have a repeated w rotation curve leading to this glitch.
I'm wondering if the OptimizeRotationCurve function should have the following small changes:

Replace

https://github.com/microsoft/MixedRealityToolkit-Unity/blob/119f16f59e7b4cd54142be29845c846bc2a2db12/Assets/MRTK/Core/Providers/InputAnimation/InputAnimation.cs#L1240
with outCurveW.AddKey(curveW[curveW.length - 1]);

Replace

https://github.com/microsoft/MixedRealityToolkit-Unity/blob/119f16f59e7b4cd54142be29845c846bc2a2db12/Assets/MRTK/Core/Providers/InputAnimation/InputAnimation.cs#L1250
with outCurveW.AddKey(curveW[j]);

Insert a line under

https://github.com/microsoft/MixedRealityToolkit-Unity/blob/119f16f59e7b4cd54142be29845c846bc2a2db12/Assets/MRTK/Core/Providers/InputAnimation/InputAnimation.cs#L1294
with outCurveW.AddKey(inCurveW[bestIndex]);
Here is a video showing the following scenarios:

Before changes
Before changes AND commenting out animation.Optimize(profile);
After changes

You can find the animation files here: https://drive.google.com/drive/folders/1iF---Gtd78hd6QTnKHgsyaqKIRiVw-3w?usp=sharing
Notice that although the animation performs much smoother with latter two scenarios, the glitch may still occur. It is just much more infrequent. I didn't create a pull request because it doesn't fix all the recorded quaternions, but I hope it's a step in the right direction.

Tested and experiencing the same issue. Attached Recording vs Playing video.
https://user-images.githubusercontent.com/13754172/123022255-60540a00-d38a-11eb-8e03-07d79ffb1520.mp4

Hey @austinbhale sorry for the late response getting to this, I tried out your fix and it works really well. I'll be opening a PR with it today!

@RogPodge Sounds great, thank you!


Missing mime-type configuration

The generated configuration files do not contain the directives:
TypesConfig
DefaultType
These two directives belong to mod_mime.
At least in Apache 2.2, those two entries are necessary to prevent errors in the log file.
Please be careful fixing this; the change should be well documented since it can break some configurations. Some people, like me, may have already implemented a workaround (creating a new configuration file in conf.d that contains these two directives). Simply adding these two directives in httpd.conf would cause these directives to be duplicates.

Hi Kevin!
We can "go crazy" with the breaking fixes until the 1.0.0 release according to semver.org.. we need to have some freedom of exploration before defining the public API.
What is the right thing to do here?
In general, the spirit of these primitives is "users bring their own configuration".. so if they decide to activate a module, they should be responsible for the httpd_config snippet.
However, since this is out-of-the-box on 2.2, it'd be nice to have healthy configuration, and I suspect this goes for more than just mime.
https://github.com/chef-cookbooks/httpd/blob/master/libraries/resource_httpd_service.rb#L79-L98
Thoughts?
-s

Good point about the 0. version.
For this one, I'd say, definitely include it with the default configuration, because mod_mime is one of the core modules that should always be loaded. Also, it may be important to manage the corresponding mime.types file (I think an earlier version of the cookbook dropped it into /etc/httpd/conf but the latest version doesn't. There also is a default /etc/mime.types file that may make more sense to use).
You are right, there probably are other directives; these two are the ones I have found. I'd go with what ships out of the box with the CentOS RPM (all the other distros probably use more or less the same attributes).

I've run into some MIME-type issues with the cookbook as-is, so in my wrapper cookbook, I have:
    file 'use mime.types instead of magic mime' do
      path '/etc/httpd-default/conf.d/mime.conf'
      content 'TypesConfig /etc/mime.types'
      only_if {File.exists?('/etc/mime.types')}
    end

/etc/mime.types comes with the mailcap package; I'm not sure if that ships by default.  If that could be used when available, I think that'd be preferable to most.

Hello,
mime.types generated by cookbook based on magic.erb and placed into conf dir is for mod_mime_magic. not for mod_mime. Still mime_magic is not loading conf/mime.types by default, instead it is looking for MimeMagicFile parameter: http://httpd.apache.org/docs/2.4/mod/mod_mime_magic.html#mimemagicfile
While conf/mime.types is a default for mod_mime:
http://httpd.apache.org/docs/2.4/mod/mod_mime.html
So, there are 3 options how to resolve the issue with mime types:

instead of magic file file generate mime.types in a mod_mime format. So "old" mime mechanism will be used. For that magic.erb just should be replaced with mime.erb which can be collected from any httpd source
keep mime.types as is, but add MimeMagicFile directive so that mod_mime_magic can load it during server startup
Combine 1 and 2, so that mime.types will be generated for mod_mime and magic.type for mod_mime_magic. They can co-exist, just need to have different names.

Are you seeing errors similar to https://blog.phpdeveloper.org/2008/02/25/fixing-cannot-get-media-type-from-0/ ? Thanks


Devnet9 Hive Fail - peering fail on ForkID tests

To reproduce, i use the following setup to debug hive tests:
i hacked a thing: https://github.com/ethereum/hive/compare/master...jflo:hive:local_debug_hacks
which uses this snooper as a fake client
https://github.com/parithosh/json_rpc_snoop/compare/master...jflo:json_rpc_snoop:dualSnoopers
which you'll have to build and tag, so the hive test will use it.
then ran hive like:
./hive -sim ethereum/engine -client-file ./configs/local-client.yaml --sim.limit "engine-cancun/ForkID: Genesis at " --docker.output to isolate a single test, and step through in my debugger.
ForkID: Genesis at * are the tests failing. Suspect peers may be disagreeing over forkId.

This seems to work in their environment. Need to understand what is different

Need to confirm this is still passing in the hive environment.

It is failing in the hive environment. error indicates unable to connect to mock client
FAIL: Error waiting for response: could not rlp decode message: EOF

Removing from the fork_id.go in the engine simulator makes the tests pass. It looks like an issue when waiting for the pong response
```

// Finally wait for the pong response
/*	msg, err := conn.WaitForResponse(timeout, 0)
if err != nil {
t.Fatalf("FAIL: Error waiting for response: %v", err)
}
switch msg := msg.(type) {
case devp2p.Pong:
t.Logf("INFO: Received pong response: %v", msg)
default:
t.Fatalf("FAIL: Unexpected message type: %v", err)
}/

https://github.com/hyperledger/besu/pull/5955

Fixed by https://github.com/hyperledger/besu/pull/5955


derive macro for newtypes

They would be very much like Option (without the None case) and be a general pass-through for all miniconf depths.

Maybe just a flatten attribute is sufficient. As discussed in https://github.com/quartiq/miniconf/issues/166#issuecomment-2252846929

Flatten (#236) should cover this.


How To Change C++ Version Compilation Option For Freestanding Application?

Hello All,
I am developing a Freestanding C++ application in Zephyr RTOS and need to set the C++ version to C++14 or higher. How do I accomplish that?
I am trying to port the state machine library https://github.com/boost-ext/sml which is just a header file include that requires just C++14 support. It is a key component in my application.
Currently I am encountering the errors below which seems to indicate that I may not be compiling with "-std=c++14". Here are the particular parameters of my setup:
~/zephyrproject/zephyr$ git describe --tag
zephyr-v3.2.0-2681-g9cf89603df

~/Zephyr_Freestanding_Applications/led_state_machine$ pwd
/home/.../Zephyr_Freestanding_Applications/led_state_machine

I am building so:
~/Zephyr_Freestanding_Applications/led_state_machine$ west -v build -p always -b nucleo_f207zg

prj.conf is like so:
CONFIG_GPIO=y

CONFIG_PRINTK=y
CONFIG_LOG=y

#CONFIG_CPP=y
CONFIG_CPLUSPLUS=y
#CONFIG_LIB_CPLUSPLUS=y
CONFIG_STD_CPP14=y
CONFIG_CPP_MAIN=y
CONFIG_MINIMAL_LIBC_MALLOC_ARENA_SIZE=128
#CONFIG_GLIBCXX_LIBCPP=y

Based upon some of the forum comments, I have tried several options in the CMakeLists.txt and it now looks like this, below. Perhaps it is because mine is a Freestanding app that is why none of the compiler switches take?
I have also looked at the change request below, but it seems confusing and perhaps is not even applicable to my version of Zephyr RTOS hence my version tag above:
https://github.com/zephyrproject-rtos/zephyr/pull/52946/files/ef932260ea813d40aa0c7b485a3d3de8c803f99a#top
cmake_minimum_required(VERSION 3.20.0)
find_package(Zephyr REQUIRED HINTS $ENV{ZEPHYR_BASE})

project(led_state_machine LANGUAGES C CXX)

set(CMAKE_CXX_STANDARD 14)
set(CMAKE_CXX_STANDARD_REQUIRED True)
set(CMAKE_CXX_EXTENSIONS OFF)
set(CMAKE_BUILD_TYPE DEBUG)

set(CMAKE_C_FLAGS_DEBUG "${CMAKE_C_FLAGS_DEBUG} -std=c++14")
set(CMAKE_CXX_FLAGS_DEBUG "${CMAKE_CXX_FLAGS_DEBUG} -std=c++14")

#zephyr_library_compile_options(-std=c++14)

file(GLOB app_sources "src/*.c" "src/*.cpp")

target_sources(app PRIVATE ${app_sources})

target_compile_options(app PRIVATE -std=c++14)

#zephyr_library_compile_options(-std=c++14)

#set_target_properties(app PROPERTIES COMPILE_FLAGS "-std=c++14")

Anyway that I can set the compiler switch "-std=c++14" and not have it overridden by the west build system, including even just passing it to west or the correct way it ought to be done, kindly let me know.
So ultimately, attached is the error message that I observe.
Regards. And thanks.
Nuertey
https://github.com/nuertey/RandomArtifacts/blob/master/zephyr_Cpluplus_freestanding_application_compile_error_message.txt

@krzysztof-jusiak

It seems like the errror points to the cxa_guard_acquire which requires some additional flags for the arm compiler (since C++11 static variables in the functions are thread safe by default)
I'd try if app is single threaded
 -fno-threadsafe-statics

or
-lstdc++

to avoid the undefined issue

Thank you so much @krzysztof-jusiak. It built with your suggestion. So you will be glad to know that your excellent state machine builds in Zephyr RTOS for STM32s and actually works. I am even actually using its DebugLogger feature per below, per your excellent instructions, so I can actually trace the state machine's progression. Thanks. Much appreciated:
// Just debug logging utilities for the State Machine defined according
// to Boost.SML's Domain-Specific Language (DSL) format:
struct DebugLogger_t
{
    template <class SM, class TEvent>
    void log_process_event(const TEvent&)
    {
        printf("[%s][process_event] %s\n", sml::aux::get_type_name<SM>(), sml::aux::get_type_name<TEvent>());
    }

    template <class SM, class TGuard, class TEvent>
    void log_guard(const TGuard&, const TEvent&, bool result)
    {
        printf("[%s][guard] %s %s %s\n", sml::aux::get_type_name<SM>(), sml::aux::get_type_name<TGuard>(),
               sml::aux::get_type_name<TEvent>(), (result ? "[OK]" : "[Reject]"));
    }

    template <class SM, class TAction, class TEvent>
    void log_action(const TAction&, const TEvent&)
    {
        printf("[%s][action] %s %s\n", sml::aux::get_type_name<SM>(), sml::aux::get_type_name<TAction>(),
               sml::aux::get_type_name<TEvent>());
    }

    template <class SM, class TSrcState, class TDstState>
    void log_state_change(const TSrcState& src, const TDstState& dst)
    {
        printf("[%s][transition] %s -> %s\n", sml::aux::get_type_name<SM>(), src.c_str(), dst.c_str());
    }
};
//...

And to help other folks and engineers struggling with same, here are the lines that I added to my CMakeLists.txt file. I added too many lines than probably needed as I was anxious to get it working quickly, but probably only one line is actually needed, probably the last one. Not sure. An expert in Zephyr RTOS backend tooling should chime in here to correct me for benefit of Posterity and other engineers:
CMakeLists.txt excerpt:
...
set(CMAKE_C_FLAGS_DEBUG "${CMAKE_C_FLAGS_DEBUG} -std=c++14 -fno-threadsafe-statics")
set(CMAKE_CXX_FLAGS_DEBUG "${CMAKE_CXX_FLAGS_DEBUG} -std=c++14 -fno-threadsafe-statics")

zephyr_library_compile_options(-std=c++14 -fno-threadsafe-statics)
...

# And at the end:
target_compile_options(app PRIVATE -std=c++14 -fno-threadsafe-statics)

Thanks
Nuertey

Not sure why this was marked as bug, converting this to a discussion.


Add schema admin api  get schema info with schema version

Motivation
To fix #4854 and support get keyValueSchema
Does this pull request potentially affect one of the following parts:
If yes was chosen, please highlight the changes
Dependencies (does it add or upgrade a dependency): (no)
The public API: (no)
The schema: (yes)
The default values of configurations: (no)
The wire protocol: (no)
The rest endpoints: (no)
The admin cli options: (no)
Anything that affects deployment: (no)
Documentation
Does this pull request introduce a new feature? (yes / no)
If yes, how is the feature documented? (not applicable / docs / JavaDocs / not documented)
If a feature is not applicable for documentation, explain why?


KYLIN-4782 Verify if the query hit the true cuboid in IT - Part 2

fix the concurrent issues
avoid to run test case 'verifySqlStandard' in NBuildAndQueryTest twice

Proposed changes
Describe the big picture of your changes here to communicate to the maintainers why we should accept this pull request. If it fixes a bug or resolves a feature request, be sure to link to that issue.
Types of changes
What types of changes does your code introduce to Kylin?
Put an x in the boxes that apply

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

Checklist
Put an x in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your code.

[ ] I have create an issue on Kylin's jira, and have described the bug/feature there in detail
[ ] Commit messages in my PR start with the related jira ID, like "KYLIN-0000 Make Kylin project open-source"
[ ] Compiling and unit tests pass locally with my changes
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] If this change need a document change, I will prepare another pr against the document branch
[ ] Any dependent changes have been merged

Further comments
If this is a relatively large or complex change, kick off the discussion at user@kylin or dev@kylin by explaining why you chose the solution you did and what alternatives you considered, etc...

Ran IT successfully.


Drop unused createdForResource and createdForResourceType labels

/lgtm from me

I don't think we can remove it. The UI plugin uses it in [1].

also, we don't really drop it here - but remove the places that remain on the backend side. if the standalone UI set those label, it's not that great as it's confusing, but the standalone UI should be used anymore besides some exceptions


error when using Qwen1.5-32B

Hi, I meet some errors when serving Qwen1.5-32B using fp6 quantization, could you please give me a help? Thank you.
My code is below:
import mii
pipe = mii.pipeline('/mymodel/Qwen1.5-32B-fp16', quantization_mode='wf6af16', tensor_parallel=8)
response = pipe(["DeepSpeed is", "Seattle is"], max_new_tokens=128)
print(response)
And the error is:
Using /root/.cache/torch_extensions/py310_cu121 as PyTorch extensions root...
Using /root/.cache/torch_extensions/py310_cu121 as PyTorch extensions root...
python: /root/miniconda3/envs/pytorch22/lib/python3.10/site-packages/deepspeed/inference/v2/kernels/core_ops/cuda_linear/include/weight_prepacking.h:151: void weight_matrix_prepacking(int*, size_t, size_t): Assertion `K % 64 == 0' failed.

Any news on this? I'm facing the same error.


null returning APIs

Many fns on NaiveTime, NaiveDateTime and NaiveDateTime have optional return values and return null on invalid input.
For the case of invalid input, it would be more ergonomic for the user of the library if errors where used instead of optional return values.

I think you're right about this. Starting work on that right now.


feat: support setting custom scheduler profile in podSpec

What type of PR is this?

feat: support setting custom scheduler profile in podSpec

What this PR does / why we need it:
Adds support for configuring a custom kube-scheduler profile in podSpec
Ref: https://kubernetes.io/docs/reference/scheduling/config/
Pods that want to be scheduled according to a specific profile can include the corresponding scheduler name in its .spec.schedulerName.
By default, one profile with the scheduler name default-scheduler is created. This profile includes the default plugins described above. When declaring more than one profile, a unique scheduler name for each of them is required.
If a Pod doesn't specify a scheduler name, kube-apiserver will set it to default-scheduler. Therefore, a profile with this scheduler name should exist to get those pods scheduled.

Which issue(s) this PR fixes:

Fixes #4432

Sounds good


Floating helper for nontech users/total newcomers

Is your feature request related to a problem?
@XyloDrone said

Please tag me in any new PRs/issues being opened that have any relation to UX/UI so I can keep adding these to the mind map accordingly + providing designs so that devs don’t have to bother with this, as it is my duty to sort out UX/UI so you can focus on what you do best.

What i see as a problem when thinking as total newcomer - #1445 the biggest problem is that those people don't know half of the words displayed on the page. To quickly solve this problem, i was thinking to implement a "floating" version of the page, which would basicly transform the page into floating mode and your cursor would work as automatic hint once you move the cursor on some words.
Describe the solution you would like
With this mode you can move your cursor throughout the page and small windows with easy explanations would pop up depending on where would you move your cursor.
It would certainly help total newcomers to find out quickly what are these buzzwords. I've done a little explanation illustration how i'd imagine this. It's just an idea, but definitely it is faster than clicking all the categories and finding out one by one.
Describe alternatives you have considered
Only alternative that comes to my mind is to make the page so simple, nobody will have to think about certain buzzwords. Like i said, this idea is solely for complete newcomers who don't even know what an nft is and somehow made their way to KodaDot.
Screeenshots
This is purely to show what i was thinking, the final solution can be different or worked on.
I know there's redesign on the way and that's why we could consider implementing this, share your thoughts please!
Once clicking on "floating helper" the page would turn into this mode and would like somewhat like this:

As i look further at the Screenshot i posted, the explanation of categories/buzzwords would have to be way simpler and understandable without knowledge of crypto-glossary, as most probably only total newcomers would use this feature.

I think this would be a good addition in some places (if it's everywhere it might be a bit much, so perhaps we can decide which elements are not straight forward).
What if we add an "i" to certain sections?

Feature wise it could be something like:

a feature "tour" guide
or feature Discovery

I vote for "tour guide" and we can structure our FAQ as feature discovery?

I see this is little bit on hold for now, but as part of onboarding experience, like i said i'll have plenty of materials what is understandable for newcomer and what not. But, since there is lot of stuff changing, for now i'd implement a small "i" or once hovered with cursor over these, a little explanation wouldn't be bad:
I can see explanations implemented while clicking on create, that is brilliant!!

would add "i" or something, to explain what is NFSW content to the red frame

here i think it could have some hover frame explanation

same here

It's a little painful to find out one by one what these mean. Since these icons are not that famous ye or not mainstream, it'd deserve some popup information when moving cursor onto them.

@exezbcz is there anything we can recycle to new design?

@exezbcz is there anything we can recycle to new design?

not really, since we've changed it to more useful icons and naming.

for example gift is now transfer and qr and link is under share section.


change tutorial to getting-started

Changes
Change tutorial to getting started doc.
The docs in tektoncd/triggers is pretty similar in content to the tutorial.md in this repo. Since, no other repo has a tutorial.md. I would like to re-purpose this for the getting-started guide. There are some updates that still need to made. I plan to those changes later today in a different pr.
Submitter Checklist
These are the criteria that every PR should meet, please check them off as you
review them:

[x] Includes tests (if functionality changed/added)
[x] Includes docs (if user facing)
[x] Commit messages follow commit message best practices

See the contribution guide for more details.
Double check this list of stuff that's easy to miss:

If you are adding a new binary/image to the cmd dir, please update
the release Task to build and release this image.

Reviewer Notes
If API changes are included, additive changes must be approved by at least two OWNERS and backwards incompatible changes must be approved by more than 50% of the OWNERS, and they must first be added in a backwards compatible way.
Release Notes
Describe any user facing changes here, or delete this block.

Examples of user facing changes:
- API changes
- Bug fixes
- Any changes in behavior

/assign @vdemeester

/assign @abayer

/assign @skaegi

/test pull-tekton-pipeline-build-tests

/test pull-tekton-pipeline-build-tests

This content is referenced as a tutorial in a number of places, so are you proposing to change this?
At a minimum, the existing links in README.md, DEVELOPMENT.md, docs/install.md and docs/README.md will need to be updated to point to the new filename.

This content is referenced as a tutorial in a number of places, so are you proposing to change this?
At a minimum, the existing links in README.md, DEVELOPMENT.md, docs/install.md and docs/README.md will need to be updated to point to the new filename.

I understand that there are other references. Thank you for letting me know. I will double check the other repos to make sure there are not other references. When I said, " Since, no other repo has a tutorial.md". Im referring to the other projects such as triggers, cli, and dashboard. If we want to automate the website there should be some level of consistency. I think I should bring this up in an issue before trying to make this change.


Model update breaks when a request is sent with a 'type' field

like {comment: {id: 1, type: 'photo'}} as the JSON
the model.update function's overwriting this.type with this.attrs.type, so when it calls model.save it looks for a collection based on this.attrs.type.

ahh, good catch. attrs are stored on a attrs hash but I define getter/setters using object.defineProperty, so that's the problem. I suppose I should make that _type or even __type.
Btw the model layer is not ready yet and the api is still undergoing changes, just so you're aware!

57c9ca4dea414eb0479a6c376addbb30078b7635 closes

type has been renamed to modelName

Awesome, thank you very much!


feat: adds nightly run with latest coraza/caddy

A good way to catch bugs earlier is to test again bleeding edge versions. In our case, running the CI, one with latest caddy and one with latest coraza would help us to detect early if it breaks.
We already do this for coraza-proxy-wasm https://github.com/corazawaf/coraza-proxy-wasm/blob/main/.github/workflows/nightly-coraza-check.yaml

Closed by https://github.com/corazawaf/coraza-caddy/pull/61


Diagram the relationship between billing groups and project-sets

Describe the issue
It would help us and our clients understand how billing works to draw some examples.
Additional context
Add any other context, attachments or screenshots
Definition of done

draw.io drawing (original file stored in teams)
present files to team
update pre-reading material to include this

not relevant


Mypy plugin doesn't infer inherited fields' types

Initial Checks

[X] I confirm that I'm using Pydantic V2

Description
Type definitions made in superclass is not respected by the mypy plugin and throws an error error: Untyped fields disallowed  [pydantic-field] if the type is not explicitly redefined in the subclass.
The example provided needs a to be typed (with a consistent type of course) in the subclass for the mypy plugin to accept it.
Shouldn't the field in the subclass infer the type from the base class?
I played around slightly, and the following addition to https://github.com/pydantic/pydantic/blob/main/pydantic/mypy.py#L642 seems to fix it:
        if lhs.is_inferred_def:
            return None

Note that my understanding of MyPy is severely limited, so this could have unintended consequences...
Example Code
from pydantic import BaseModel

class Base(BaseModel):
    a: int

class Sub1(Base):
    a = 1

Python, Pydantic & OS Version
pydantic version: 2.3.0
        pydantic-core version: 2.6.3
          pydantic-core build: profile=release pgo=true
                 install path: /opt/poetry/.venv/lib/python3.11/site-packages/pydantic
               python version: 3.11.5 (main, Sep  7 2023, 13:03:21) [GCC 10.2.1 20210110]
                     platform: Linux-5.15.0-82-generic-x86_64-with-glibc2.31
     optional deps. installed: ['email-validator', 'typing-extensions']

Note that this code raises an error at runtime.
In principle I'm not opposed to changing the mypy plugin to not error in this case, but only if we change pydantic to also not error in this case 😄.
That said, I think we required the annotation be re-specified on purpose. I don't remember the details; if it's easy to change to not require the annotation be repeated when a field is inherited and a default value is set, I'd be happy to review a PR making the change, but I wouldn't be surprised if there was some non-obvious reason that it might be better to require the annotation be repeated.

ah, shit, sorry. That was meant to be a  ClassVar:
from typing import ClassVar

from pydantic import BaseModel

class Base(BaseModel):
    a: ClassVar[int]

class Sub1(Base):
    a = 1

This passes runtime, but fails mypy.
I am curious about the reasoning for requiring overrides to be annotated though, but I'm guessing this goes deep into the core of pydantic.

I was using this with normal attributes pretty heavily with pydantic v1 (which did work at runtime, even for non-ClassVars) to define a bunch of base classes that must be subclassed (often by users of my library) with the fields set. More or less abstract base classes... but for fields. Since users will be creating the subclasses, it's extra annoying to require them to keep type hinting things all the way down.
I don't see anything directly in the migration guide (probably because it's niche :grin:), but I wonder if the reason v2 opted for "always explicit declaration" was to disambiguate between "keep the base class's hint" and "narrow the hint from the subclass's value". I opened a similar issue for mypy, but mypy's behavior is to implicitly narrow rather than require an explicit definition across all subclasses, for example:
class A:
    x: int | str

class B(A):
    x = 5

class C(B):
    x = "5"  # E: Incompatible types in assignment (expression has type "str", base class "B" defined the type as "int")  [assignment]

reveal_type(A.x)  # I: Revealed type is "Union[builtins.int, builtins.str]"
reveal_type(B.x)  # I: Revealed type is "builtins.int"
reveal_type(C.x)  # E: Cannot determine type of "x"  [has-type]

Unless there's another reason for the strict hint on subclasses, perhaps it'd make sense to adopt mypy's behavior here?
That said, keeping the base class's hint for a field and only validating the subclass's value is compatible is probably easier to implement (and preferable to narrowing for my uses, but that's less important haha).

I know this we intentionally made this the current behavior, but I can't remember why we made it required or how good of a reason we had to do so. Unless I'm forgetting something important, in principle I'm not opposed to relaxing this requirement to include a type annotation when overriding the default value on a subclass, I'm just not sure if there might be some complex edge cases to handle (e.g., assigning a call to Field as the new default, assigning a value from model_config['ignored_types'], etc.).
Unless @samuelcolvin or another maintainer objects, I'd be open to a PR making the change.

@JacobHayes Okay, I'm not 100% confident, but looking through the code, I believe the reason we did things this was that it made it easier to build the field for the subclass — in particular, if you have something like x: int = Field(2, alias='my_x', description='something'), and then override it in a subclass to x = 2, we have to both make sure that we retain all that metadata, and also make sure we retain the type annotation.
My guess is that in the interest of getting v2 released more quickly, we decided not to wrestle with this and just require an annotation, and that simplified the relevant code. The more I look though, the more I think it should be possible to eliminate this requirement (both at runtime and in the mypy plugin, using the suggestion in the original issue report).
A PR implementing this would definitely be helpful/appreciated, but I think we can get around to it eventually if you don't have time or find it challenging. I'll just note that we'll probably want to use something like FieldInfo.merge_field_infos to implement the merging of the new default value (which could possibly be a FieldInfo itself) into the parent class field info.

In case someone comes here from Google, an example of using FieldInfo.merge_field_infos is given here.


Upgrade typescript dependency version

Fix typegen incorrectly outputs const for non-readonly fields.
Closes #361

Great! Thanks so much! btw, do you have any links to typescript changelogs where they mention this bugfix?

@xenova I am not familiar with the typescript repo, can only confirm this is fixed in >=5.1.0.
With some investigations, I believe it was a magical side-effect of this PR, just a guess though.

@xenova just noticed there is a second bug (globalThis has no index signature) in #361, I am not sure if this solves that as well.
Let me get back to you later.

@xenova The globalThis problem is not related to this project, for details please refer to my comment on the issue.
This PR should be ready.

I can confirm that this does mark env vars as non-constant (and should fix #361):
5.0.2: types/env.d.ts
export namespace env {
    export namespace backends {
        export { onnx_env as onnx };
        export const tfjs: {};
    }
    export { __dirname };
    export { VERSION as version };
    export const allowRemoteModels: boolean;
    export const remoteHost: string;
    export const remotePathTemplate: string;
    export const allowLocalModels: boolean;
    export { localModelPath };
    export { FS_AVAILABLE as useFS };
    export { WEB_CACHE_AVAILABLE as useBrowserCache };
    export { FS_AVAILABLE as useFSCache };
    export { DEFAULT_CACHE_DIR as cacheDir };
    export const useCustomCache: boolean;
    export const customCache: any;
}
declare const onnx_env: any;
declare const __dirname: any;
declare const VERSION: "2.7.0";
declare const localModelPath: any;
declare const FS_AVAILABLE: boolean;
declare const WEB_CACHE_AVAILABLE: boolean;
declare const DEFAULT_CACHE_DIR: any;
export {};

5.2.2: types/env.d.ts
export namespace env {
    export namespace backends {
        export { onnx_env as onnx };
        export let tfjs: {};
    }
    export { __dirname };
    export { VERSION as version };
    export let allowRemoteModels: boolean;
    export let remoteHost: string;
    export let remotePathTemplate: string;
    export let allowLocalModels: boolean;
    export { localModelPath };
    export { FS_AVAILABLE as useFS };
    export { WEB_CACHE_AVAILABLE as useBrowserCache };
    export { FS_AVAILABLE as useFSCache };
    export { DEFAULT_CACHE_DIR as cacheDir };
    export let useCustomCache: boolean;
    export let customCache: any;
}
declare const onnx_env: any;
declare const __dirname: any;
declare const VERSION: "2.7.0";
declare const localModelPath: any;
declare const FS_AVAILABLE: boolean;
declare const WEB_CACHE_AVAILABLE: boolean;
declare const DEFAULT_CACHE_DIR: any;
export {};

(notice difference between let and const)


[Enhancement] Use one RandomAccessFile to read the index and data of a column

currently, each index of each column will create a new file to read, which is not friendly to cloud native table.
Use one RandomAccessFile to read the index and data of a column, the benefits are as follows:

the indexes of each column of cloud native table may be combined read, and the remote io count will be reduced.
collect index read io statistics can be more easily.

Fixes #issue
What type of PR is this:

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

Checklist:

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

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

Bugfix cherry-pick branch check:

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

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

@Mergifyio backport branch-3.1

@Mergifyio backport branch-3.1


Update pricing on docs.hedera.com for bulk minting NFTs

hi, just checking on what the new bulk minting pricing is for the docs (checking to make sure it matches what I'm expecting).

hi @Ashe-Oro ! For now, we are adding all the Monday board items to GitHub for docs. I would review this issue in the Monday board for more details.


Signals::forever should not consume

There's no actual reason to consume, as repeatedly calling wait is possible on &mut reference. Also, consuming makes it hard to use after a for with break in it.

The tricky thing is the difference between the signal_hook::iterator module and the adapter crates. The former is happy with a mutable reference to the SignalDelivery in the SignalIterator struct because the owner outlives the iterator.
The latter create the SignalDelivery struct in their constructor and pass it on to the SignalIterator. In this case the SignalIterator can't just hold a reference.
But I figured out I could make the SignalIterator more generic and just rely on the BorrowMut trait to achieve both. I already had a working solution but forgot to update my local copy with your latest upstream changes. So I have to do those changes again tomorrow 😅
But I think this will be another breaking change because users of the blocking iterator might have to add a mut to their instance and also use a &mut at the point of iteration.

The latter create the SignalDelivery struct in their constructor and pass it on to the SignalIterator. In this case the SignalIterator can't just hold a reference but must own the SignalDelivery instance.

On a second thought, what is the reason why it can't be a reference and must outlive/must be static? With async/await support, futures and stream that borrow something should be perfectly fine, shouldn't they?

The blocking iterator has a two step approach: First constructing the Signals instance and then getting the iterator through Signals::forever. We decided against a two step construction approach for the async crates because it offers no advantages. Instead the constructor methods create a SignalDelivery instance and pass it to the wrapped SignalIterator. E. g. from the async_std crate:
pub fn with_exfiltrator<I, S>(signals: I, exfiltrator: E) -> Result<Self, Error> {
    let (read, write) = UnixStream::pair()?;
    let inner = SignalDelivery::with_pipe(read, write, exfiltrator, signals)?;
    Ok(Self(SignalIterator::new(inner)))
}

The lifetime of SignalDelivery will be limited to the function call if you do not return it from / move it out of the function. But moving a value isn't possible if there are any outstanding references to it because the memory location the reference is pointing would be invalid after moving. This is why SignalIterator can't take a reference in this case. At least not without something fancy like a  self referential struct.


Bfs

This pull request is:

[x] A new Algorithm
[ ] An update to an existing algorithm.
[ ] An error fix
[ ] Other (Describe below*)

This pull request fixes:
https://github.com/abranhe/allalgorithms-python/issues/23

Changes:
Add bfs algorithm

Hey, can we agree on merging or closing this PR?

Hey, can we agree on merging or closing this PR?

Hey, thanks for reaching out, lately I have been kinda busy and I haven't reviewed any pull request.
I am looking for people who are willing to maintain this project not only to maintain the repository but also to publish it to https://pypi.org/. Please if you are interested in it or know somebody else please, reach out!


Your app has been throttled by AAD

Preflight Checklist

[X] I have installed the latest version of Storage Explorer.
[X] I have checked existing resources, including the troubleshooting guide and the release notes.
[X] I have searched for similar issues.

Storage Explorer Version
1.28.0
Regression From
No response
Architecture
x64
Storage Explorer Build Number
20230214.5
Platform
Linux (snap)
OS Version
Fedora 36
Bug Description
Trying to access blob storage account (ADLS GEN2) within an Azure subscription, I get very often over prolonged time the error message "Your app has been throttled by AAD due to too many requests. To avoid this, cache your tokens see https://aka.ms/msal-net-throttling."
This happens either while navigating to the blob storage, accessing directories or files inside a blob container, in each case necessitating new authentication, or while trying to authenticate again.
Steps to Reproduce

Launch StorageExplorer
Sign in to Azure account
Select one or more storage accounts
Try to navigate to blob storage container

Actual Experience
Over prolonged time span I will get the "Your app has been throttled by AAD" error when trying to access blob storage (i.e. navigating in the tree view to the specific blob container, usually before reaching the blob container at all.
At the same time, it does not happen on the Windows version of StorageExplorer (switching back and forth between StorageExplorer as local Snap and StorageExplorer inside Win10 VM on local system), so it seems to be related to differences between Windows and Linux builds, but may also depend on external factors, as shown by the intermittent nature of the problem:
This usually fixes itself after a while (i.e. access to blob container becomes possible, while console output still shows some of the errors in the attached log), and is intermittent: even after connecting, access to directories / files in the blob container sometime spontaneously fails with the same problem.
Expected Experience
Access to blob storage should be possible using Linux Snap StoragerExplorer without running into AD throttling while it is possible with Windows StorageExplorer without running into AD throttling.
Additional Context
Redacted console output of StorageExplorer:
[2023-02-15T11:56:42.867Z] (storage-account-extension:50418) <INFO> API call for listClassicAndArmStorageAccounts succeeded
  GET https://management.azure.com//subscriptions/<REDACTED>/resources?api-version=2014-04-01&$filter=resourceType%20eq%20%27Microsoft.ClassicStorage%2FstorageAccounts%27%20or%20resourceType%20eq%20%27Microsoft.Storage%2FstorageAccounts%27 - 200
  Credential used: Auth token - accountId: <REDACTED>
  RequestId: b35b03d6-f195-4f78-b961-d6f94a3c040b, Date sent: Wed, 15 Feb 2023 11:56:42 GMT, ApiVersion: undefined, ProxySettings: undefined

[2023-02-15T11:56:44.439Z] (se-managed-disks-extension:50435) <INFO> API call for listResourceGroups succeeded
  GET https://management.azure.com/subscriptions/<REDACTED>/resourcegroups?api-version=2021-04-01 - 200
  Credential used: Auth token - accountId: <REDACTED>
  RequestId: 6144f6c8-1346-48f1-934a-3f60533e7fd8, Date sent: Wed, 15 Feb 2023 11:56:43 GMT, ApiVersion: undefined, ProxySettings: undefined

[2023-02-15T11:56:44.653Z] (storage-account-extension:50418) <INFO> API call for listClassicAndArmStorageAccounts succeeded
  GET https://management.azure.com/subscriptions/<REDACTED>/resources?api-version=2014-04-01&%24filter=resourceType+eq+%27Microsoft.ClassicStorage%2fstorageAccounts%27+or+resourceType+eq+%27Microsoft.Storage%2fstorageAccounts%27&%24skiptoken=<REDACTED> - 200
  Credential used: Auth token - accountId: <REDACTED>
  RequestId: 36a002e2-88c6-40d3-ad91-b9d7586a0cc8, Date sent: Wed, 15 Feb 2023 11:56:44 GMT, ApiVersion: undefined, ProxySettings: undefined

[2023-02-15T11:56:46.343Z] (storage-account-extension:50418) <INFO> API call for listClassicAndArmStorageAccounts succeeded
  GET https://management.azure.com/subscriptions/<REDACTED>/resources?api-version=2014-04-01&%24filter=resourceType+eq+%27Microsoft.ClassicStorage%2fstorageAccounts%27+or+resourceType+eq+%27Microsoft.Storage%2fstorageAccounts%27&%24skiptoken=<REDACTED> - 200
  Credential used: Auth token - accountId: <REDACTED>
  RequestId: 7ef8b928-ff19-452f-853a-39f9b5108a81, Date sent: Wed, 15 Feb 2023 11:56:45 GMT, ApiVersion: undefined, ProxySettings: undefined

[2023-02-15T11:56:48.610Z] (storage-account-extension:50418) <INFO> API call for listClassicAndArmStorageAccounts succeeded
  GET https://management.azure.com/subscriptions/<REDACTED>/resources?api-version=2014-04-01&%24filter=resourceType+eq+%27Microsoft.ClassicStorage%2fstorageAccounts%27+or+resourceType+eq+%27Microsoft.Storage%2fstorageAccounts%27&%24skiptoken=e<REDACTED> - 200
  Credential used: Auth token - accountId: <REDACTED>
  RequestId: 8a7cbfa1-b958-4cf6-93c0-23452b2884cd, Date sent: Wed, 15 Feb 2023 11:56:49 GMT, ApiVersion: undefined, ProxySettings: undefined

[2023-02-15T11:56:51.284Z] (storage-account-extension:50418) <INFO> API call for listClassicAndArmStorageAccounts succeeded
  GET https://management.azure.com/subscriptions/<REDACTED>/resources?api-version=2014-04-01&%24filter=resourceType+eq+%27Microsoft.ClassicStorage%2fstorageAccounts%27+or+resourceType+eq+%27Microsoft.Storage%2fstorageAccounts%27&%24skiptoken=<REDACTED> - 200
  Credential used: Auth token - accountId: <REDACTED>
  RequestId: 83ddee5d-0387-42d0-91d9-634379b7e820, Date sent: Wed, 15 Feb 2023 11:56:51 GMT, ApiVersion: undefined, ProxySettings: undefined

[2023-02-15T11:56:52.573Z] (storage-account-extension:50418) <INFO> API call for listClassicAndArmStorageAccounts succeeded
  GET https://management.azure.com/subscriptions/<REDACTED>/resources?api-version=2014-04-01&%24filter=resourceType+eq+%27Microsoft.ClassicStorage%2fstorageAccounts%27+or+resourceType+eq+%27Microsoft.Storage%2fstorageAccounts%27&%24skiptoken=<REDACTED> - 200
  Credential used: Auth token - accountId: <REDACTED>
  RequestId: 8af237d7-ded3-45de-bb78-c09aff18d8c7, Date sent: Wed, 15 Feb 2023 11:56:52 GMT, ApiVersion: undefined, ProxySettings: undefined

[2023-02-15T11:56:53.544Z] (storage-account-extension:50418) <INFO> API call for listClassicAndArmStorageAccounts succeeded
  GET https://management.azure.com/subscriptions/<REDACTED>/resources?api-version=2014-04-01&%24filter=resourceType+eq+%27Microsoft.ClassicStorage%2fstorageAccounts%27+or+resourceType+eq+%27Microsoft.Storage%2fstorageAccounts%27&%24skiptoken=<REDACTED> - 200
  Credential used: Auth token - accountId: <REDACTED>
  RequestId: 86fd4c5d-7642-42b6-be4b-528e92821577, Date sent: Wed, 15 Feb 2023 11:56:52 GMT, ApiVersion: undefined, ProxySettings: undefined

[2023-02-15T11:56:54.492Z] (storage-account-extension:50418) <INFO> API call for listClassicAndArmStorageAccounts succeeded
  GET https://management.azure.com/subscriptions/<REDACTED>/resources?api-version=2014-04-01&%24filter=resourceType+eq+%27Microsoft.ClassicStorage%2fstorageAccounts%27+or+resourceType+eq+%27Microsoft.Storage%2fstorageAccounts%27&%24skiptoken=<REDACTED> - 200
  Credential used: Auth token - accountId: <REDACTED>
  RequestId: 89238ef6-891d-4b32-8ab9-f106cdc7f909, Date sent: Wed, 15 Feb 2023 11:56:53 GMT, ApiVersion: undefined, ProxySettings: undefined

[2023-02-15T11:56:55.530Z] (storage-account-extension:50418) <INFO> API call for listClassicAndArmStorageAccounts succeeded
  GET https://management.azure.com/subscriptions/<REDACTED>/resources?api-version=2014-04-01&%24filter=resourceType+eq+%27Microsoft.ClassicStorage%2fstorageAccounts%27+or+resourceType+eq+%27Microsoft.Storage%2fstorageAccounts%27&%24skiptoken=<REDACTED> - 200
  Credential used: Auth token - accountId: <REDACTED>
  RequestId: 615e2b09-5008-43f1-844c-87700b481de0, Date sent: Wed, 15 Feb 2023 11:56:55 GMT, ApiVersion: undefined, ProxySettings: undefined

[2023-02-15T11:56:56.659Z] (storage-account-extension:50418) <INFO> API call for listClassicAndArmStorageAccounts succeeded
  GET https://management.azure.com/subscriptions/<REDACTED>/resources?api-version=2014-04-01&%24filter=resourceType+eq+%27Microsoft.ClassicStorage%2fstorageAccounts%27+or+resourceType+eq+%27Microsoft.Storage%2fstorageAccounts%27&%24skiptoken=<REDACTED> - 200
  Credential used: Auth token - accountId: <REDACTED>
  RequestId: e83079d2-0b01-40be-858d-b44bb4cff629, Date sent: Wed, 15 Feb 2023 11:56:55 GMT, ApiVersion: undefined, ProxySettings: undefined

[2023-02-15T11:56:56.793Z] (main:50107) <ERRO> Failed to acquire token account <REDACTED>, resource https://management.core.windows.net/, error [object Object], fail silently: false
[2023-02-15T11:56:56.794Z] (storage-account-extension:50418) <ERRO> Failed to get tenant token for credential {"type":"auth","accountId":"<REDACTED>","tenantId":"<REDACTED>"}, error: Your app has been throttled by AAD due to too many requests. To avoid this, cache your tokens see https://aka.ms/msal-net-throttling.

[2023-02-15T11:56:56.809Z] (main:50107) <ERRO> Failed to acquire token account <REDACTED>, resource https://management.core.windows.net/, error [object Object], fail silently: false
[2023-02-15T11:56:56.810Z] (storage-account-extension:50418) <ERRO> Failed to get tenant token for credential {"type":"auth","accountId":"<REDACTED>","tenantId":"<REDACTED>"}, error: Your app has been throttled by AAD due to too many requests. To avoid this, cache your tokens see https://aka.ms/msal-net-throttling.

[2023-02-15T11:56:56.823Z] (main:50107) <ERRO> Failed to acquire token account <REDACTED>, resource https://management.core.windows.net/, error [object Object], fail silently: false
[2023-02-15T11:56:56.824Z] (storage-account-extension:50418) <ERRO> Failed to get tenant token for credential {"type":"auth","accountId":"<REDACTED>","tenantId":"<REDACTED>"}, error: Your app has been throttled by AAD due to too many requests. To avoid this, cache your tokens see https://aka.ms/msal-net-throttling.

[2023-02-15T11:56:56.855Z] (main:50107) <ERRO> Failed to acquire token account <REDACTED>, resource https://management.core.windows.net/, error [object Object], fail silently: false
[2023-02-15T11:56:56.855Z] (storage-account-extension:50418) <ERRO> Failed to get tenant token for credential {"type":"auth","accountId":"<REDACTED>","tenantId":"<REDACTED>"}, error: Your app has been throttled by AAD due to too many requests. To avoid this, cache your tokens see https://aka.ms/msal-net-throttling.

[2023-02-15T11:57:53.743Z] (main:50107) <ERRO> Failed to acquire token account <REDACTED>, resource https://management.core.windows.net/, error [object Object], fail silently: false
[2023-02-15T11:57:53.744Z] (storage-account-extension:50418) <ERRO> Failed to get tenant token for credential {"type":"auth","accountId":"<REDACTED>","tenantId":"<REDACTED>"}, error: Your app has been throttled by AAD due to too many requests. To avoid this, cache your tokens see https://aka.ms/msal-net-throttling.

The authentication library we use does support caching access tokens. There might be something in the snap environment that breaks that mechanism. We can do some testing on a snap to verify if the token caching is broken.

I wasn't able to reproduce the exact issue but I had some interesting finding. I installed Fedora myself and I noticed that the automatic time the system maintains is always ~30minutes away from the more widely accepted time around my region (e.g. Seattle time). As a result, all storage account key related operations fail to authenticate even though everything else is perfectly correct. This significantly increases the number of requests using Azure AD but it hasn't broken my account by issuing too many requests so far. Could you please check your Fedora's system time to see if it drifts from the time of your Windows machine or your phone? If so, try manually adjusting it and see if helps mitigate this issue.

Hi, I have checked system time on my Fedora installation and there is no drift between system time and "correct local time".
However, yesterday I tried to reproduce the issue on a separate Ubuntu 22.04 LTS based test installation: using the same current Snap 1.28 version of StorageExplorer I cannot reproduce the issue on Ubuntu, concurrently trying access at the same time on both Ubuntu and Fedora. I.e. access works on Ubuntu, but fails with "AAD" throttling on Fedora.
So it looks more to be a Fedora or Fedora implementation/configuration of Snap issue than an issue with StorageExplorer implementation itself. Also, it seems like Fedora and Snap have some other issues, too, i.e. some snaps tend not to run as smoothly on Fedora as they should.
I guess there is no difference between the Snap delivered on Ubuntu and on Fedora, right? Are there target platform specific configurations in the Snap that could cause a difference?
Since after all the issue seems not to lie with StorageExplorer after all, please feel free to close this issue if you see that it doesn't lie within the Snap build of StorageExplorer, especially if there shouldn't be a difference in the snaps running on both platforms.
Also, for other reasons I will switch to an Ubuntu based distribution in the near future (hence the test mentioned above), which at least for me seems to fix the issue anyway.

Thanks for double checking on that. Due to limitation of resource, we only test our linux releases on Ubuntu and rely on Snap's cross platform containerization to support other linux distributions hoping they work fine. Currently we only have a small group of linux users among which most are on Ubuntu so unfortunately there is no incentive to expanding our support. Sorry for the inconvenience.


How can i set the tree position

I want to display in top right corner, but i cannot to find it to help

I need to go to a specific size of a certain piece, not the whole column

Sorry, that's not an option. You could always just map a command to open it then :split it and put whatever you want below.

Sorry, that's not an option. You could always just map a command to open it then :split it and put whatever you want below.

Oright, Could  change the position or size of the float mode？

Yes: https://github.com/nvim-neo-tree/neo-tree.nvim/wiki/Visual-Customizations#floating-window-settings

Yes: https://github.com/nvim-neo-tree/neo-tree.nvim/wiki/Visual-Customizations#floating-window-settings

Thank you very much!

I'm going to close this because I think the floating options fit your needs, and I am not going to add a position which would be just the top half of a sidebar.
If anything was added, it would be something like #360

I'm going to close this because I think the floating options fit your needs, and I am not going to add a position which would be just the top half of a sidebar.
If anything was added, it would be something like #360

Perfect!


Inequitable share frontend

Preview Link

Click to demo updates
Description

frontend for #1829
To Do

[x] fix high/low default on ShareTrends
[x] the metric isn't really a share... it's like a "pct_deviation" not sure if it's worth renaming the metric on the backend now? I just don't want to confuse ourselves thinking it represents a share of total cases, it's really "by what percent is the result off from the expected"
[ ] fine-tooth comb to confirm all labels, etc are transferred. We really still need to do #1438 because it's growing more and more confusing and the new title generating functions are kind of crazy. There should be more 1:1 of strings of text in the metric config and the text that appears on the page, and less string manipulation to slice and dice and end up with the right phrasing

Motivation and Context

How has this been tested?

Screenshots (if appropriate):

Types of changes

New feature (non-breaking change which adds functionality or content)

Looks good to me! Just update the col name to https://github.com/SatcherInstitute/health-equity-tracker/pull/1857 and we should be good to go.


Quick access for chemist, parking areas, gas stations, post offices

I think it would be very useful, if you could add quick access (Search around this place) for chemists, parking areas, gas stations, post offices and maybe bicycle shops. Especially the 4 first ones are part of everyday life.

Hi, thank you for your report. We have done a first version only when language settings is french or english. We are still working on this part of code. I don't know if it is a good idea to open this feature for users who has the language setting german because we did not implement it in German..

If you need german translations, here they are:

chemist (shop=chemist) -> Drogerie
parking area -> Parkplatz
gas station -> Tankstelle
post office -> Poststelle
bicycle shop -> Fahrradgeschäft


Support for Cloud SQL Insights

Now that GCP provides the Cloud SQL Insights tool, will it be supported by this module in the near future?

Please request it in the provider first: https://github.com/hashicorp/terraform-provider-google

Insights is now available in the provider :-) .


Go doesn't need anything setup by this buildpack

but it does need the buildpack in the detected list
to flag other systems that metrics are enabled.
Connects to heroku/opex-team#227

Closing for now in favor of checking for data if the flag is on.


"StreamingEngine VOD plays" test timeout on Windows

We had the following test timeout on Firefox and Chrome on Windows in our nightly test run:
Firefox 54.0.0 (Windows 10 0.0.0)
  StreamingEngine VOD plays FAILED
    Error: Timeout - Async callback was not invoked within timeout specified by jasmine.DEFAULT_TIMEOUT_INTERVAL. in node_modules/jasmine-core/lib/jasmine-core/jasmine.js (line 3938)
    attemptAsync/timeoutId<@node_modules/jasmine-core/lib/jasmine-core/jasmine.js:3938:23

Failed 1 tests, passed 1138, skipped 77

Chrome 59.0.3071 (Windows 10 0.0.0)
  StreamingEngine VOD plays FAILED
    Error: Timeout - Async callback was not invoked within timeout specified by jasmine.DEFAULT_TIMEOUT_INTERVAL.

Failed 1 tests, passed 1171, skipped 44

The next day, the same tests were passing again.

This did not reoccur in the subsequent 100+ nightly runs.  I'm running a stress test now to try to reproduce.

Unable to reproduce after 20 more runs.


movie time problem

it's not 1.5s before and after you press the button, it's 3s after you press the button

you can choose the frame you want, it can be anything


How to build the Icons made by Freepik from www.flaticon.com?

hello,
I'm interested in your icons shown there, how to build the apps ? any reference or code available here?

Hi, could you please clarify the question? IF you need the Icons from here just copy them (with the author's credit of course). If you want to create your own icons - go to the websites mentioned.


EDScout Odyssey

Hi,
EDScout is excellent but since upgrading to Odyssey its been stopping more frequantly, it will work for random period of time then freeze.
Issue:
Windows 10 OS
EDscout GUI stops updating, even after jumping etc it does not change,.
Upon investigating (Taskmaster) edScout.exe is no longer running.
Last view of the log file below:
2021-06-05T13:31:07.650Z - EDScoutCore-EDScout - INFO - Storing<PHONE_NUMBER>922 => K
2021-06-05T13:31:07.650Z - EDScoutCore-EDScout - INFO - Reporting: {"timestamp": "2021-06-05T13:31:07Z", "event": "FSDTarget", "Name": "Traikaae FS-I c23-13", "SystemAddress":<PHONE_NUMBER>922, "StarClass": "K", "RemainingJumpsInRoute": 117, "type": "JournalEntry"}
2021-06-05T13:31:07.654Z - EDScoutCore-EDScout - INFO - Reporting: {"type": "System-FSDTarget", "EdsmUplinkValid": true, "charted": false, "StarSystem": "Traikaae FS-I c23-13", "SystemAddress":<PHONE_NUMBER>922, "StarClass": "K"}
2021-06-05T13:31:14.519Z - flaskwebgui-flaskwebgui - INFO - Gui was closed.
Gui is not closed and chrome web page still running.
Has happened 3 times today already.
Thanks
Dave

Also  EDSCout incorrectly reporting wrong system compared to current.

Thanks

I've noticed this too.
Here are the last log lines before I had to task kill it:
2021-08-30T11:21:05.417Z - EDScoutCore-EDScout - INFO - Storing<PHONE_NUMBER>785 => M
2021-08-30T11:21:05.418Z - EDScoutCore-EDScout - INFO - Reporting: {"timestamp": "2021-08-08T16:03:14Z", "event": "FSDTarget", "Name": "Orishis", "SystemAddress":<PHONE_NUMBER>785, "StarClass": "M", "RemainingJumpsInRoute": 1, "type": "JournalEntry"}
2021-08-30T11:21:05.447Z - EDScoutCore-EDScout - INFO - Reporting: {"type": "System-FSDTarget", "id": 16131, "id64":<PHONE_NUMBER>785, "name": "Orishis", "url": "https://www.edsm.net/en/system/bodies/id/16131/name/Orishis", "estimatedValue": 23905, "estimatedValueMapped": 74226, "valuableBodies": [], "EdsmUplinkValid": true, "charted": true, "StarSystem": "Orishis", "SystemAddress":<PHONE_NUMBER>785, "StarClass": "M"}
2021-08-30T11:21:05.447Z - EDScoutCore-EDScout - INFO - Looking up system<PHONE_NUMBER>785
2021-08-30T11:21:05.450Z - EDScoutCore-EDScout - INFO - Reporting: {"timestamp": "2021-08-08T16:04:09Z", "event": "FSDJump", "Taxi": false, "Multicrew": false, "StarSystem": "Orishis", "SystemAddress":<PHONE_NUMBER>785, "StarPos": [-31.0, 93.96875, -3.5625], "SystemAllegiance": "Alliance", "SystemEconomy": "$economy_Industrial;", "SystemEconomy_Localised": "Industrial", "SystemSecondEconomy": "$economy_Refinery;", "SystemSecondEconomy_Localised": "Refinery", "SystemGovernment": "$government_Corporate;", "SystemGovernment_Localised": "Corporate", "SystemSecurity": "$SYSTEM_SECURITY_medium;", "SystemSecurity_Localised": "Medium Security", "Population": 8504929, "Body": "Orishis", "BodyID": 0, "BodyType": "Star", "Powers": ["Edmund Mahon"], "PowerplayState": "Exploited", "JumpDist": 52.479, "FuelUsed": 3.416196, "FuelLevel": 11.100497, "Factions": [{"Name": "Hand Gang of Orishis", "FactionState": "CivilUnrest", "Government": "Anarchy", "Influence": 0.02229, "Allegiance": "Alliance", "Happiness": "$Faction_HappinessBand2;", "Happiness_Localised": "Happy", "MyReputation": 0.0, "ActiveStates": [{"State": "CivilUnrest"}]}, {"Name": "Official Orishis Defence Force", "FactionState": "None", "Government": "Dictatorship", "Influence": 0.069909, "Allegiance": "Independent", "Happiness": "$Faction_HappinessBand2;", "Happiness_Localised": "Happy", "MyReputation": 0.0}, {"Name": "Orishis Company", "FactionState": "CivilWar", "Government": "Corporate", "Influence": 0.118541, "Allegiance": "Alliance", "Happiness": "$Faction_HappinessBand2;", "Happiness_Localised": "Happy", "MyReputation": 0.0, "ActiveStates": [{"State": "CivilWar"}]}, {"Name": "Allied Orishis Order", "FactionState": "None", "Government": "Dictatorship", "Influence": 0.094225, "Allegiance": "Independent", "Happiness": "$Faction_HappinessBand2;", "Happiness_Localised": "Happy", "MyReputation": 0.0}, {"Name": "Workers of Orishis Independents", "FactionState": "CivilWar", "Government": "Democracy", "Influence": 0.118541, "Allegiance": "Independent", "Happiness": "$Faction_HappinessBand2;", "Happiness_Localised": "Happy", "MyReputation": 0.0, "ActiveStates": [{"State": "CivilWar"}]}, {"Name": "Perez Ring Brewery", "FactionState": "None", "Government": "Corporate", "Influence": 0.576494, "Allegiance": "Alliance", "Happiness": "$Faction_HappinessBand2;", "Happiness_Localised": "Happy", "MyReputation": 0.0, "PendingStates": [{"State": "Boom", "Trend": 0}], "RecoveringStates": [{"State": "Expansion", "Trend": 0}]}], "SystemFaction": {"Name": "Perez Ring Brewery"}, "Conflicts": [{"WarType": "civilwar", "Status": "active", "Faction1": {"Name": "Orishis Company", "Stake": "Galactic Mobile Security Chapter", "WonDays": 0}, "Faction2": {"Name": "Workers of Orishis Independents", "Stake": "", "WonDays": 0}}], "type": "System-FSDJump", "StarClass": "M", "id": 16131, "id64":<PHONE_NUMBER>785, "name": "Orishis", "url": "https://www.edsm.net/en/system/bodies/id/16131/name/Orishis", "estimatedValue": 23905, "estimatedValueMapped": 74226, "valuableBodies": [], "EdsmUplinkValid": true, "charted": true}
2021-08-30T11:21:05.454Z - EDScoutCore-EDScout - INFO - Reporting: {"type": "System-FSDJump", "id": 16131, "id64":<PHONE_NUMBER>785, "name": "Orishis", "url": "https://www.edsm.net/en/system/bodies/id/16131/name/Orishis", "estimatedValue": 23905, "estimatedValueMapped": 74226, "valuableBodies": [], "EdsmUplinkValid": true, "charted": true, "StarSystem": "Orishis", "SystemAddress":<PHONE_NUMBER>785, "StarClass": "M"}

I'm not sure if this issue relates to the Odyssee update or to me trying to use EDScout on Win11.
I'm using the diagnostic version, as the installation on Win11 seem to work, as mentioned in issue #201
What did, or rather didn't, happen?

I start EDScout, it's GUID opens up, logfile is being created.
Plotting a route in ED
Nothing happens to the EDScout GUID. I also tried the no_app setting and opening the page directly in Chrome, without any success. The plotted route is not shown.
Doing some jumps, as in earlier versions of EDScout this sometimes fixed the update issue, but still nothing. No information on the plotted route or the current system. Only the edsm_cache.sqlite is being created.
Finally killed EDScout via task manager. Now the (attached) log file contains some data.
EDScout-2021-11-27-16-57-11.log

As I'm going for my next big exploration, EDScout would be a very helpful companion, if only it worked again.


Some of the options in config.toml seem to be ignored

Environmental Info:
K3s Version: v1.19.5+k3s2 (746cf403)
Node(s) CPU architecture, OS, and Version:
Linux 4.15.0-143-generic #147-Ubuntu SMP Wed Apr 14 16:10:11 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux
Cluster Configuration:
5 masters - 15+ nodes
Describe the bug:
When using Google's gVisor for container sandboxing, there is a way to activate certain flags via configuration. That config location can be specified in  [plugins."io.containerd.grpc.v1.cri".containerd.runtimes.runsc.options] but in my case that option is being ignored and I do not know where to see the reason. Logs show nothing in particular.
Steps To Reproduce:

Edit the file /var/lib/rancher/k3s/agent/etc/containerd/config.toml.tmpl
Add:

  [plugins."io.containerd.grpc.v1.cri".containerd.runtimes.runsc.options]
    TypeUrl = "io.containerd.runsc.v1.options"
    ConfigPath = "/etc/containerd/runsc.toml"

Create the file /etc/containerd/runsc.toml
Add something to it like:

[runsc_config]
  net-raw = "true"
[debug]
  level = "debug"

Restart the agent
Run a pod using gVisor runtimeClassName and try to add NET_RAW CAP. This won't be possible since the config is not being picked up.

Expected behavior:
Configuration passed to gVisor being added when calling runsc and loaded from k3s toml template, since I guess that's the only place where it can be configured.
Actual behavior:
gVisor works fine but configuration is being ignored. K3s logs shows no errors or warning messages.

What steps did you follow to install runsc and install the plugin such that the containerd build into k3s can find it?

Well, you can always look at the config file used by containerd - its right next to the template file at /var/lib/rancher/rke2/agent/etc/containerd/config.toml. If you see the sections in there, they should be used. If they're not, then that's an issue with containerd.

Hello @brandond, the file you are pointing out here is dynamically created using the template. I had a look and effectively all the values I put in the template are written in that file during agent's initialization.
If containerd reads configuration from that file and k3s does nothing in the middle, then as you say it is probably related to containerd/gVisor rather than k3s.

Yes, all k3s does is process the template to generate the config file, then runs containerd pointed at that file. Are there any additional logs or behaviors that might suggest where the problem lies?

Hi @brandond,
What I would need to figure out how to do is confirm that effectively contained is picking up those values from /var/lib/rancher/k3s/agent/etc/containerd/config.toml, so where could I see containerd's logs? (not actual logs from containers, but containerd's process logs since maybe there I can find messages regarding the gVisor configuration section).

I have a slightly related question here: https://github.com/k3s-io/k3s/discussions/3507

Yes, @kristofre seems to be the same root problem. As I said the previous comment I am not able to find logs re the config.tml loading process, maybe there resides the key to the problem.

Worked fine for me.
I just copied the default template from to /var/lib/rancher/k3s/agent/etc/containerd/config.toml.tmpl.
Then I added the following lines to the end of it:
[plugins.cri.containerd.runtimes.runsc]
  runtime_type = "io.containerd.runsc.v1"

After I reloaded the service (sudo systemctl restart k3s.service) containerd picked up the new config from /var/lib/rancher/k3s/agent/etc/containerd/config.toml. The configuration can be confirmed by running sudo k3s crictl info |jq '.config.containerd.runtimes' which should now display runsc as additional runtime.

@brumhard, apparently you did not capture the problem.
It clearly says "some of the options" but you say that worked for you just because one thing worked.
Please read the issue's body carefully, there it's explained what the problem is, which is not certainly the one you are describing.

@nsoubelet
containerd logs should be located in /var/lib/rancher/k3s/agent/containerd/containerd.log by default.

@Oats87 yes, that one I know.
What I mentioned in this thread is that I am not able to find logs entries related to config.tml loading process, not the containerd's log file itself.
Thanks

This seems to work for me:
[plugins.opt]
  path = "/var/lib/rancher/k3s/agent/containerd"
[plugins.cri]
  stream_server_address = "<IP_ADDRESS>"
  stream_server_port = "10010"
  enable_selinux = false
  sandbox_image = "rancher/mirrored-pause:3.1"
[plugins.cri.containerd]
  snapshotter = "overlayfs"
  disable_snapshot_annotations = true
[plugins.cri.containerd.runtimes.runc]
  runtime_type = "io.containerd.runc.v2"
[plugins.cri.containerd.runtimes.runsc]
  runtime_type = "io.containerd.runsc.v1"
[plugins.cri.containerd.runtimes.runsc-hostnetwork]
  runtime_type = "io.containerd.runsc.v1"
#gvisor stuff
[plugins.cri.containerd.runtimes.runsc.options]
  TypeUrl = "io.containerd.runsc.v1.options"
  ConfigPath = "/var/lib/rancher/k3s/agent/etc/containerd/runsc.toml"
[plugins.cri.containerd.runtimes.runsc-hostnetwork.options]
  TypeUrl = "io.containerd.runsc.v1.options"
  ConfigPath = "/var/lib/rancher/k3s/agent/etc/containerd/runsc-hostnetwork.toml"

I have two gvisor runsc because one is full isolation and 2nd have host-network capabilities
hostnetwork version config:
[runsc_config]
  network = "host"

And it picks it up correctly and works with host-network.


client: tx and flush timeout

If for any reason the CTS line is stuck high (modem crashing or doing too much work) when sending, the current thread could possibly be stuck indefinitely.
This PR adds optional timeouts for both transmitting and flushing so it's not breaking API retro-compatibility and allows end-user to set timeout depending on their hardware needs.

This is awesome! Thanks for the contribution! :+1:

Huh that's strange, this test pass on my computer...


Put the nginx pid in /tmp

To fix this:
$ kubectl logs nginx-55b9f744d5-bhrtd
2018/08/02 10:37:04 [emerg] 1#1: open() "/etc/nginx/nginx.pid" failed (30: Read-only file system)
nginx: [emerg] open() "/etc/nginx/nginx.pid" failed (30: Read-only file system)

Signed-off-by: Tom Wilkie<EMAIL_ADDRESS>

/cc @aleks-mariusz


Service context for claims

Description
This PR enables services to pass context through the claims in the authorization path. The context
is transparent to Trireme, but allows the creation of services end-to-end above trireme. For example it enables the exchange of ephemeral keys for encryption or any other extensibility mechanism.
Test plan
Correct communication of context needs to be verified.

Codecov Report

Merging #378 into master will increase coverage by 0.03%.
The diff coverage is 87.5%.

@@            Coverage Diff             @@
##           master     #378      +/-   ##
==========================================
+ Coverage   56.03%   56.06%   +0.03%
==========================================
  Files          51       51
  Lines        6152     6157       +5
==========================================
+ Hits         3447     3452       +5
  Misses       2398     2398
  Partials      307      307

Impacted Files
Coverage Δ

enforcer/connection.go
35.84% <ø> (ø)
:arrow_up:

enforcer/datapath_tcp.go
57.21% <87.5%> (+0.37%)
:arrow_up:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 52fb5bf...06f70a8. Read the comment docs.


VERSION is not bumped on release

Summary

The latest version of gopass-jsonapi is 1.15.2 and gopass-jsonapi --version still gives 1.14.5 (the old release) because the VERSION file contains the old version in the new release.
Steps To Reproduce
$ go install<EMAIL_ADDRESS>go: downloading github.com/gopasspw/gopass-jsonapi v1.15.2
$ gopass-jsonapi --version
gopass-jsonapi version 1.14.5

Expected behavior
Release and output of --version match
Environment

OS: Arch Linux
OS version: Linux meterpeter 6.1.0-arch1-1 #1 SMP PREEMPT_DYNAMIC Sun, 11 Dec 2022 23:35:00 +0000 x86_64 GNU/Linux
gopass-jsonapi Version: gopass-jsonapi version 1.14.5
Installation method: Source / ABS

Additional context
https://gopassworkspace.slack.com/archives/C018JEGLZU3/p1671470383332919

Releases that need fixing (maybe incomplete):

[ ]<EMAIL_ADDRESS>[ ]<EMAIL_ADDRESS>[ ]<EMAIL_ADDRESS>

Thanks for fixing this so quickly! 🥳


[clinical-result] Add doc example for header/cell

Summary

What was changed:
We need to add examples for clinical result of the usage for Flowsheet Cell, Time Header Cell, and Name Header Cell within a semantic html table.
I added a semantic table example instead of changing all of the existing examples in case consuming teams continue to use this component in a non-semantic way. We of course want our users to use this with appropriate semantic html, so I will be adding guidance on that in our accessibility page that is being created in another PR.
Why it was changed:
The look/behavior of these cells are different when they are used within semantic html tables, so we need to give examples of what that will look like.
Testing

This change was tested using:

[x] WDIO
[x] Jest
[x] Visual testing (please attach a screenshot or recording)
[ ] Other (please describe below)
[ ] No tests are needed

Reviews
In addition to engineering reviews, this PR needs:

[x] UX review
[x] Accessibility review
[ ] Functional review

Additional Details

This PR resolves:
UXPLATFORM-9205

Thank you for contributing to Terra.
@cerner/terra

Terra site for these changes: https://engineering.cerner.com/terra-clinical/pull/877/home/terra-clinical/home

Have a WDIO issue I'm looking into for flowsheet result cell semantic table, discussing that on this PR here: https://github.com/cerner/terra-clinical/pull/881#issuecomment-1629784839

@RayGunY There is a WDIO test failing. Is it related to your changes?

@RayGunY There is a WDIO test failing. Is it related to your changes?

Kind of, I'm working on it right now - it's being fixed in the defect PR. It's a lot to explain, so a breakdown can be found in this comment: https://github.com/cerner/terra-clinical/pull/881#issuecomment-1629784839
Basically the code on my side is correct and if you go look at the flowsheet semantic table test on the PR site you'll see it looks the way we want it to. The snapshot is failing here because I haven't pushed out the re-generated snapshot. You can ignore that failure for now and take a look at the rest of the code.

Looks good, +1 after resolving the WDIO issue.

@RayGunY There is a WDIO test failing. Is it related to your changes?

@vinaybhargavar Kind of, I'm working on it right now - it's being fixed in the defect PR. It's a lot to explain, so a breakdown can be found in this comment: #881 (comment)
Basically the code on my side is correct and if you go look at the flowsheet semantic table test on the PR site you'll see it looks the way we want it to. The snapshot is failing here because I haven't pushed out the re-generated snapshot. You can ignore that failure for now and take a look at the rest of the code.

Sounds good. +1 after resolving the WDIO issue.

@RayGunY Does this PR have the same wdio issue as #881 ?

@RayGunY Does this PR have the same wdio issue as #881 ?

@sdadn we removed it from this PR since we'll handle it in the other, so this one should be good to go


Pass in broker config in hash form

The Sequencer expects the config in a hash.
{
  :config => config
}

This PR produced the config in the correct format.
https://jira.dev.bbc.co.uk/browse/CONNPOL-2821

@BBCMarkMcDonnell, all of the other caching PRs have been merged. The Lookup cache is working as I am seeing "hit" in the logs. The Sequencer cache is being set as the null cache. I have worked out the Sequencer was expecting a hash with a config option in it. I was just passing the config directly into it.
Can you review this one please?

Note, this will take less than 5 minutes to review...

:cake:


#7793 broke --overlay-triplets

I introduced a scripts variable (like download) to align the acces to it throughout the cmake files. Please test, if it fits also to your --overlay-triplets use case (see #7943).

Added scripts variable to ports file.
Added check if triplet file is not available (NPE).

LGTM, though I would like to see the line ending changes get fixed so changes to the ports.cmake file are more obvious.

Still need to fix --overlay-triplets.

/azp run


Add tests for plist import

The plist import code is not covered by tests at all right now.

At this point, in the subcommand restructuring run, command plist turned into a wrapper. store handles the "plist import" functionality. store is tested by the tests that use check (which wraps over store) to insert runs into the database, which is read later on.

A separate store test might be needed, if we plan to remove or deprecate the check command.

This issue seems to be out-of-date, since we don't have a plist importer. To be precise, store command covers this functionality and that is tested.


implement dss create-notebook command

Adds the create-notebook command as well as unit and integration tests.
Closes #31.
Testing instructions
Do:
KUBECONFIG=~/.kube/config

pip install .
dss initialize --kubeconfig $KUBECONFIG
dss create-notebook test-notebook --image kubeflownotebookswg/jupyter-scipy:v1.8.0 --kubeconfig $KUBECONFIG

connect to the notebook via link printed to the screen, then do:

create a terminal and do pip install mlflow
create a notebook server and do:

import mlflow
c = mlflow.MlflowClient()  # You should not need to specify the tracking_uri - it should be populated automatically
print(c.tracking_uri)  # should print the in-cluster url for dss's mlflow
c.create_experiment("test-experiment")  # Should succeed

go to the mlflow dashboard (http://MLFLOW_SVC_IP:5000) and confirm you can see "test-experiment" in the left menu

We might need to postpone this PR until this issue is resolved https://github.com/canonical/data-science-stack/issues/58

The dss create command has been discussed with UX team please check the DSS spec here  for details about the error messages and parameters.
I have also noticed @ca-scribner that we might have forgotten about gpu support for this command. More details are in the spec.

If this is merged after #55, let's make sure it updates also tests accordingly like here


circt: init at 1.29.0

Circuit IR Compilers and Tools (https://github.com/llvm/circt)
Pending issues:

I am experiencing sporadic internal compiler error when building circt on both my pc and server. The error remains occuring even when switching from stdenv to clangStdenv, but disappears when building with --cores 1. May somebody help testing on his/her machine (nix build github:SharzyL/nixpkgs/circt#circt)?

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/)
23.05 Release Notes (or backporting 22.11 Release notes)

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

[x] Fits CONTRIBUTING.md.

nixpkgs-fmt is done.
It seems that ICE is caused by hardware issue. It disappears when I lower the overclocking configuration. Now it works fine.

And you may with to schedule it as big-parallel:
requiredSystemFeatures = [ "big-parallel" ];

big-parallel done

Result of nixpkgs-review pr 214870 run on x86_64-linux 1

1 package built:

circt

FWIW: https://github.com/dtzSiFive/circt-nix (updated regularly to latest git, backed by cachix).  LLVM is split out so it's not rebuilt on every update and can be built in somewhat smaller pieces (although we bump LLVM weekly so that mostly helps folks using this very actively / cachix-friendliness).  Includes development shell for anyone hacking on CIRCT.
When I get some cycles, I'll try to revive the MLIR PR to nixpkgs and help here as needed :+1:, not sure when that'll be :sweat_smile:.  FWIW CIRCT makes releases roughly weekly now.


fix font-size source. Issue#152

#152
This PR fix the font-size source in SPEC in mode global using attribute

:autofit-option:

https://github.com/asciidoctor/asciidoctor-pdf

pdf attached :
spec.pdf

Just a small comment to help the other reviewers.
This PR enables the AsciiDoc "Auto-Fit" option:
https://asciidoctor.org/docs/asciidoctor-pdf/#autofitting-text

When the autofit option is enabled, Asciidoctor PDF will decrease the font size until the longest line fits without wrapping.

I think this is exactly what we need.


Implement non-volatility of attributes that are supposed to be non-volatile

Problem
The mechanism used for non-volatility in the initial silabs code (see #3623) no longer exists.
Proposed Solution
Need to figure out how to deal with some attributes needing to be non-volatile.

Fixed by https://github.com/project-chip/connectedhomeip/pull/13172


Roadmap for C++ support

Hey,
I would like to use Modelina for C++ and I'm getting ready to contribute to the C++ support.
But before I really get into it, I'd like to hear whether there's already some kind of roadmap?
I think the most important feature, which I'll be mainly working on, is (de)serialisation to and from JSON. I'd like to use the yyjson library for that, because it is fast (to the level of SIMDJSON, but without the SIMD hassles), powerful and MIT licensed.

There is not, so you can see it as a blank slate, your own drawing board 😄
If you want a specific library for serialization go for it, if others want a different one, they can contribute a different preset, so no worries 👍

Hi
Im looking for a way to generate from asyncapi yml, message payloads in json format, similar to what is done for programming languages using modelina.
I saw above that @robinchrist  might have some information on this issue. Is this correct ?
Thanks!

Closing as no further involvement 🙂