Thaumcraft 6 Beta 6 crash with Railcraft 10.3.1

This is my mod list for the test environment:
UCHIJ   mcp{9.19} [Minecraft Coder Pack] (minecraft.jar)
UCHIJ   FML{<IP_ADDRESS>} [Forge Mod Loader] (forge-1.10.2-<IP_ADDRESS>1.jar)
UCHIJ   Forge{<IP_ADDRESS>1} [Minecraft Forge] (forge-1.10.2-<IP_ADDRESS>1.jar)
UCHIJ   Baubles{1.3.13} [Baubles] (Baubles-1.10.2-1.3.13.jar)
UCHIJ   railcraft{10.3.1} [Railcraft] (Railcraft_1.10.2-10.3.1.jar)
UCHIE   thaumcraft{6.0.BETA6} [Thaumcraft] (Thaumcraft-1.10.2-6.0.BETA6.jar)

Here is the latest.log before closing the minecraft client.

It appears to be the Potion aspects attempting to apply aspects to railcraft's creosote potion, me and some friends have had this issue also

I can confirm I am currently using it is ALL THE MODS for 1.10.2 for testing purposes and Beta 6 crashes on load up. The issue seems to stem from the potion aspects like TheBigBear and Ryu have mentioned and shown.

I'm also having this issue. Not on the client but my server won't start. Probably the client won't too didn't had the time to test.
Here's my crash-report if it helps: https://pastebin.com/vsJcK3k6

I am also seeing this issue, with PSI potions and the potion aspect calculations.
Pastebin of crashlog

Oh my me too,I'm a Chinese player and I also experienced it.sign
crash-2018-02-16_11.12.45-client.txt
We should be together and help azanor to make a hotfix.(Tried to type an emoji of smiling.)
But I have no knowledge of coding.(:з)∠)

Similar issue, crash on start due to potion part I expect.
2018-02-16-2.log


Provide a Windows/MSVC build

This took ... a very long time. But I can build glib with MSVC against it, so I think it's more or less working.

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

BTW, one known limitation: the resulting libintl.dll also needs to be linked with libiconv.dll, but I can't figure out how to make automatic linking happen.


allow erasing values in fields

Several issue fields are notn-mandatory but cannot be reset through the redmine-java-api because changes are only added to the JSON output if the value is not null.
Affected fields are:

Assignee
Category
Target Version
Parent Issue Id
Due Date
Estimated time
Description
...?

Sample code from RedmineJSONBuilder:

if (issue.getAssignee() != null) {
			JsonOutput.addIfNotNull(writer, "assigned_to_id", issue
					.getAssignee().getId());
}

As the fix for setting the project went into master, I rebased the change described above onto master and added some javadoc to describe the intended usage.

I created this: http://stackoverflow.com/questions/38335065/how-to-use-camelcase-in-idea-live-templates/38335154#38335154 for the new "is...present" boilterplate generation.

I think most abstraction layers face this problems in some point. Why not stick on solutions from other libraries?.
See hibernate. They flag its updates with dynamicUpdate.
Here configuring dynamicUpdate as true by default, covers backward compatibility for this library behaviour, but opens the gate for a future change, where dynamicUpdate would be false by default.

feel free to checkout and play around with this new branch: https://github.com/taskadapter/redmine-java-api/tree/ask-61-save-nulls-if-set
you can see the list of recent commits - I converted a bunch of classes to use "property storage" which enables tacking "not defined" vs. "explicitly set to null".

I will focus on this test
https://github.com/taskadapter/redmine-java-api/blob/ask-61-save-nulls-if-set/src/test/java/com/taskadapter/redmineapi/internal/RedmineJSONBuilderTest.java#L44

public void fieldsExplicitlySetToNullAreAddedToIssueJSonAsNull()

and split it on two test: One propagate nulls and the other don't. The idea is RedmineJSONBuilder.toSimpleJSON receive a flag for that behaviour, avoiding add optionals on every DTO and massive usage of:
https://github.com/taskadapter/redmine-java-api/blob/ask-61-save-nulls-if-set/src/main/java/com/taskadapter/redmineapi/internal/RedmineJSONBuilder.java#L273
private static void addIfSet(JSONWriter writer, String jsonKeyName, PropertyStorage storage, Property<?> property) throws JSONException {
	if (storage.isPropertySet(property)) {
		writer.key(jsonKeyName);
		writer.value(storage.get(property));
	}
}

which seems to be hard to maintain and an extend. Even more using annotations on DTO and custom mapper code would be keeped up to date in no time
http://stackoverflow.com/a/11761975/848072
NON_NULL would be the actual behaviour and non setting that the new behaviour (storing nulls)

hi guys. is anyone interested in trying out the current dev branch (https://github.com/taskadapter/redmine-java-api/tree/ask-61-save-nulls-if-set) and giving feedback?
@albfan please keep in mind that the goal of this change is to distinguish between "explicitly set to null" and "not set" fields. marking fields as "not null" or using "save nulls" flag in the json mapper would not help with that.
feel free to share your technical proposal in a PR in case I misunderstood your idea.

the change was merged to "master".

You are right about explicity set to null.

@alexeyOnGitHub sorry for the late reply. I was busy with other projects. Yesterday I did a first port of the redminenb project to the 3.0.0-SNAPSHOT version and most thinks worked out of the box.
I'm not sure whether I like the fact, that the assignee, project and so on information was flattend into name/id properties on their respective parents, but I can live with that change. Some properties need further work to be unsettable and some functions need getters for the name components (Membership). I'll supply PRs for these.

@matthiasblaesing I'm glad it almost worked for you :)
the flat structure is to support "set to null" feature as well as remove confusion on what fields are set in what circumstances.
I agree that some properties require more changes for "send if  set" mode. I don't use many of those fields in my other project and I cannot easily verify the validity of those...
it would be great if you could find and fix them. thanks!


There is no git tags on GitHub repository

Hi @Fabianlindfors ,
We are cdnjs team, we're going to host this library.
The git auto-updater in cdnjs relies on git tags so that it can recognize the correct version and automatically update the repo.
Could you please add git tags for the repo?
And could you please help me add more information into package.json to upstream?
eg. description, keywords, license, author, repository ... etc.
ref: https://docs.npmjs.com/files/package.json
If you have any suggestions, please let me know.
Thank you.
cdnjs/cdnjs#10550

Hi!
I'm glad you want to add multi.js to your super useful service. I added the information you requested to package.json here 70bca559346552fc5d72f44d1b04e8712a9fed04 and also created a release for version 0.2.3.
Do you need anything else from me?

Wow, It's great!
@Fabianlindfors Thank you very much! 👍


CI: Add timeout for kubectl rollout (#584)

kubectl rollout may get stuck in failure if can not rollout successfully.
This patch add 5 minutes timeout for the operation to make sure CI won't
be blocked by it.

/test-all

Maybe describe the problem briefly in commit message? Then other people know why we need timeout.

/test-all

/test-networkpolicy

/test-all

/test-conformance

Actually, your changes in jenkins yaml files will take effect in current CI check. So you are ok to skip-all.

/skip-all

@ruicao93 actually, your changes in jenkins yaml files will take effect in current CI check. So you are ok to skip-all.

Got it. Thanks Zhengsheng.


Revert "[SourceKit] Don't build an AST if no semantic info is requested"

Cherry-pick https://github.com/apple/swift/pull/40491 to release/5.6.

Reverts apple/swift#40353

The change actually wasn’t correct because we didn’t consider the following scenario:

The client makes an edit and had key_enablesyntaxmap = key_enablesubstructure = key_enablediagnostics = 0 and
syntax tree transfer mode set to off
The request returned immediately without providing semantic information but build an AST in the background
The client would later retrieve diagnostics using a 0,0 replace text request that had key_enablediagnostics = 1. That request doesn’t cause the AST to rebuild but just returns the latest semantic information.

With the PR that is being reverted we wouldn’t build an AST at all and thus we won’t have any diagnostics to return from the 0,0 replace text request.
rdar://86289587

@swift-ci Please smoke test

@swift-ci Please test

Build failed
Swift Test OS X Platform
Git Sha - 5260d65ca0bfe292c1d96540b62fec0c009d6351

@swift-ci Please test macOS


image resolution

I want to keep the resolution of the original dataset (200), I changed it here, will this work, why is the output dataset resolution still 224? thanks!!

You need to resize the image in the _parse_example function before putting it into the dictionary here: https://github.com/kpertsch/rlds_dataset_builder/blob/cff9f536c53518baa744b0f31e66d53ef445d2a1/example_dataset/example_dataset_dataset_builder.py#L112

You need to resize the image in the _parse_example function before putting it into the dictionary here:
https://github.com/kpertsch/rlds_dataset_builder/blob/cff9f536c53518baa744b0f31e66d53ef445d2a1/example_dataset/example_dataset_dataset_builder.py#L112

thanks!!!


Claudio/id quick

Overview
Suggest a faster alternative to obtain the principal of the current actor (avoiding a self send).
Requirements
None
Considered Solutions
Just this one.
Recommended Solution
Use Principal.fromActor(this).
Considerations
Improves performance considerably, avoid latency of await.

Mention here: https://forum.dfinity.org/t/how-to-get-the-canister-identifier-in-the-motoko-code/2195


Improve the variation in the default set of address space and address plans

Address space plans brokered: unlimited-brokered
Address plans brokered: brokered-queue, brokered-topic
Address space plans standard: unlimited-standard
Address plans standard:

Plan name
Router credits
Broker credits

Small Anycast
0.001
N/A

Medium Anycast
0.01
N/A

Large Anycast
0.1
N/A

Small Multicast
0.001
N/A

Medium Multicast
0.01
N/A

Large Multicast
0.1
N/A

Medium Anycast
0.01
N/A

Small Queue
0.001
0.01

Medium Queue
0.01
0.1

Large Queue
0.1
1.0

Extra Large Queue
0.2
2.0

Small Topic
0.001
0.01

Medium Topic
0.01
0.1

Large Topic
0.1
1.0

Extra Large Topic
0.2
2.0

Small Subscription
0.001
0.01

Medium Subscription
0.01
0.1

Large Subscription
0.1
1.0

@grs @k-wall @rgodfrey @vbusch @robshelly Wdyt about the above selection of default plans?


throw redirect() infinite loop

Description
Hello @brillout. I create locale parameters and store the language in a cookie and use throw redirect to redirect using the stored locale. The first time, it worked correctly but I saw my redirect loop error when I switched languages.

Here is my log in **vike/node/runtime/renderPage/createHttpResponseObject/assertNoInfiniteHttpRedirect.ts**

"vike": "^0.4.191"

Thanks for the great project!

What makes you think it's a bug? Closing, but let's re-open if it's potentially a bug.


KON-407: Adding config for CPR service

It's the slack plugin that makes jenkins fail. No other problems is detected.


Add sleep to wait realtime notifications

What does this PR do?
This PR add sleep to wait realtime notifications.

 Snippets tests reports   SDK Version Tests overview      v6        v5                                   :heavy_minus_sign:                    v1        v1        v1


GUI runtime panic caused by window size

Self Checks

[X] This is only for bug report, if you would like to ask a question, please head to Discussions.
[X] I have searched for existing issues search for existing issues, including closed ones.
[X] I have searched for existing pull requests search for existing pull requests, including closed ones.

Environment
📜 Manuscript Core:
  Version:	1.1.0

🏗  Build Information:
  Go Version:	go1.22.5
  Rust Version:	1.83.0
  Git Commit:	1727168
  Built:	2024-12-11:16:18:33

💻 System Information:
  Unix Name:	Linux fedora-workstation 6.11.10-300.fc41.x86_64 #1 SMP PREEMPT_DYNAMIC Sat Nov 23 00:51:20 UTC 2024 x86_64 GNU/Linux
  OS/Arch:	linux/amd64

🐳 Docker Environment:
  Docker:	'27.3.1'
  Docker Desktop:	'4.36.0'

Steps to reproduce

build manuscript-gui
make terminal window small

OR

make terminal window small
build manuscript-gui

✔ Expected Behavior
Successful GUI Launch :rocket:

❌ Actual Behavior
When running the manuscript-gui command with small terminal:
thread 'main' panicked at /home/kagemnikarimu/.cargo/registry/src/index.crates.io-6f17d22bba15001f/ratatui-0.29.0/src/buffer/buffer.rs:253:13:
index outside of buffer: the area is Rect { x: 0, y: 0, width: 80, height: 24 } but index is (65529, 1)
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

When making the terminal small after running the manuscript-gui command:
thread 'main' panicked at alloc/src/slice.rs:565:50:
capacity overflow
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

@youngpriince  Reopening the issue.
I ran into the issue again after building from source on this week's community code :(
log_file_path: /home/kagemnikarimu/.manuscript/logs/manuscript_2024-12-18.log
thread 'main' panicked at /home/kagemnikarimu/.cargo/registry/src/index.crates.io-6f17d22bba15001f/ratatui-core-0.1.0-alpha.0/src/buffer/buffer.rs:253:13:
index outside of buffer: the area is Rect { x: 0, y: 0, width: 80, height: 24 } but index is (65529, 1)
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

log file at log file path is empty; full RUST_BACKTRACE below:
└──> RUST_BACKTRACE=full manuscript-gui
log_file_path: /home/kagemnikarimu/.manuscript/logs/manuscript_2024-12-18.log
thread 'main' panicked at /home/kagemnikarimu/.cargo/registry/src/index.crates.io-6f17d22bba15001f/ratatui-core-0.1.0-alpha.0/src/buffer/buffer.rs:253:13:
index outside of buffer: the area is Rect { x: 0, y: 0, width: 80, height: 24 } but index is (65529, 1)
stack backtrace:
   0:     0x55c37a8772ca - <std::sys::backtrace::BacktraceLock::print::DisplayBacktrace as core::fmt::Display>::fmt::hddb63c9699c7309a
   1:     0x55c37a8a3d83 - core::fmt::write::hc338d61058c0d66c
   2:     0x55c37a872aa3 - std::io::Write::write_fmt::h80dab97476750852
   3:     0x55c37a877112 - std::sys::backtrace::BacktraceLock::print::h8f82e207cdd02441
   4:     0x55c37a87860a - std::panicking::default_hook::{{closure}}::hced8387e9fe5d421
   5:     0x55c37a878450 - std::panicking::default_hook::ha3f6ad90792a97b6
   6:     0x55c37a878ca8 - std::panicking::rust_panic_with_hook::h061c0c1eebc4ec34
   7:     0x55c37a878a6a - std::panicking::begin_panic_handler::{{closure}}::h5e30b0d14d1187f1
   8:     0x55c37a8777a9 - std::sys::backtrace::__rust_end_short_backtrace::h5df085eb7f7be6aa
   9:     0x55c37a8786fc - rust_begin_unwind
  10:     0x55c37a4f1fa0 - core::panicking::panic_fmt::h70cef1aa03d57ac6
  11:     0x55c37a773622 - ratatui_core::buffer::buffer::Buffer::index_of::{{closure}}::h59aee45b374bec56
  12:     0x55c37a773598 - ratatui_core::buffer::buffer::Buffer::index_of::h9401a1b80079d7af
  13:     0x55c37a76925e - <&ratatui_widgets::paragraph::Paragraph as ratatui_core::widgets::widget::Widget>::render::hcd3c7f420bfa540c
  14:     0x55c37a768ffd - <ratatui_widgets::paragraph::Paragraph as ratatui_core::widgets::widget::Widget>::render::h1a2328fd261e17c6
  15:     0x55c37a5780a1 - manuscript_gui::ui::draw::hc41d674a1e4a3e60
  16:     0x55c37a5743b8 - ratatui::terminal::terminal::Terminal<B>::try_draw::h1f98878e4b7c238b
  17:     0x55c37a54075e - manuscript_gui::app::App::run::h9e903345c60ee570
  18:     0x55c37a511269 - tokio::runtime::park::CachedParkThread::block_on::heeee53651d820ccc
  19:     0x55c37a52192c - tokio::runtime::context::runtime::enter_runtime::h63c1f60f9b76ccfe
  20:     0x55c37a52cf1d - tokio::runtime::runtime::Runtime::block_on::h450890ee0cd59afe
  21:     0x55c37a52288a - manuscript_gui::main::h75645e861128985b
  22:     0x55c37a532133 - std::sys::backtrace::__rust_begin_short_backtrace::h7c5be7024bc57e83
  23:     0x55c37a51aba3 - std::rt::lang_start::{{closure}}::hc7fb70e3d4a508c7
  24:     0x55c37a86bdde - std::rt::lang_start_internal::h10052b6af5e10459
  25:     0x55c37a522965 - main
  26:     0x7fd8524fa248 - __libc_start_call_main
  27:     0x7fd8524fa30b - __libc_start_main_impl
  28:     0x55c37a4f27e5 - _start
  29:                0x0 - <unknown>

@KagemniKarimu I'll check it out now.

@KagemniKarimu Kindly check #107
The issue is with the minimum terminal size. Typically, the minimum size for many terminal applications is 80x24. I set the minimum dimensions to 80x28 as a safety threshold.


[Likely Unintended Behaviour] Bouncy Potion Effect allows unbounded accelleration during Elytra Flight.

Minecraft version & Mod Version:
Minecraft 1.12
Cyclic 1.14.1
Single player or Server:
Single Player
Describe problem (what you were doing / what happened):
Flying with elytra while under the influence of a bouncy potion (or the bouncy potion effect of a player launcher) allows one to accellerate to absurd speeds, travelling thousands of blocks in seconds, faster than the game can load or generate terrain.
I thought the player launcher could serve as a handy replacement for fireworks. It exceeded both my expectations and the speed limit.
Even mere creative flight seems to allow one to accellerate in a very difficult to control fashion while under the effects of this potion.
Crash log (if any):
No crash!
Thanks for your time and consideration, and, what continues to be one of my favorite content mods of this era.

"what continues to be one of my favorite content mods of this era." Thank you! Literally nobody has ever said that before.
Yep i just did that too, went a few hundred blocks.  Its intended to keep horizontal momentum to simulate a bounce, so ill just disable it while ElytraFlying action is on

Fix is up https://minecraft.curseforge.com/projects/cyclic/files/2541330


Release ahead of Kubernetes

The main problem is that we vendor Kubernetes, requiring an updated go.mod which is just available after the final Kubernetes release. Therefore we usually lack days/weeks behind Kubernetes, which is not really acceptable from a packaging point of view, because Kubernetes deb/rpm packages have direct requirements on cri-tools.
Given that cri-tools v1.27.1 (latest) may not work 100% correctly with Kubernetes v1.28.0, I'm proposing to:
Release cri-tools before Kubernetes with vendoring the latest release candidate.
@kubernetes-sigs/cri-tools-maintainers thoughts on that? I think this makes things easier from a release flow perspective.

is it possible to do a similar thing to cri-o and commit to a release timeline after kubernetes? or is even a day's lag or something unacceptable from the kubernetes packaging perspective?

since cri-tools has fewer blocking changes than cri-o, we could commit to something short like a day or two?

Hm, we release 1.28.0 on Aug 15 and the rc.1 on Aug 10th. So we can prepare the vendor change on Aug 11th and release cri-tools v1.28.0 right on Monday, Aug 14.

This is making the compatibility "window" really really short, compared to how it used to be (1.19 forever).
It makes it even more important to install cri-tools with the kubernetes version, and not a global installation.

Given that cri-tools v1.27.1 (latest) may not work 100% correctly with Kubernetes v1.28.0,

This sounds like the CRI API is broken.

Given that cri-tools v1.27.1 (latest) may not work 100% correctly with Kubernetes v1.28.0,

This sounds like the CRI API is broken. Changing the dependency would be a rather big change.

It's not. If we assume we add new CRI fields in k8s v1.28.0, which may be required by CRI-O v1.28.0 as well, then a cri-tools v1.27.x is not able to provide the full client data set like a kubelet v1.28, so we cannot guarantee that it 100% works correctly if the runtime does not manually add upgrade paths. So it all depends on the runtime from my point of view.

Stills sounds like a very tight coupling for an external project - but I will go with whatever the kubernetes release does...
Note that if you release cri-tools 1.28 now, there will be many 1.27 installations picking it up (since it is not pinned/held)
Then again, they are current using 1.26.0 (since there was no release for 1.27.0)
And soon, they will have different package repositories for different k8s versions

Done


Trying to use with an asset

Hi Andre
Ok, so I am trying to use preparse to pre-calculate a bunch of common transforms from an image at the time of the save of that image as a new asset.  I've used similar code on entries & products but it seems to be better to do it at the asset save end of things, that way in theory everything in terms of transforms would be ready immediately for all other templates.
I'm getting errors though - my assets never finish uploading, and I get these in the craft logs:
Next Twig_Error_Runtime: An exception has been thrown during the rendering of a template ("HTTP status “404” encountered while attempting to download “https://images.imagescience.com.au/AledaSmallTest3.png”") in "_preparse/preparseImages" at line 14. in /var/www/vhosts/craft/craft/app/vendor/twig/twig/lib/Twig/Template.php:396

(See longer tack trace here - https://gist.github.com/bossanova808/626893f02a5cec2407e9)
(Might be worth adding your own plugin log to help isolate these thing by the way!)
Basically I am trying to trigger the transforms at asset save, and save a log of what happened in the field itself just so I can check what is going on.  Here's the preparse template as an example:
{% if asset|length %}

    {{ asset.filename }}

    {% if asset.width > 1000 %}

        Width over 1000, creating masthead.

        {% set images = craft.imager.transformImage( asset, craft.businessLogic.namedImageFit('masthead') )%}

    {% endif %}

    Creating 500 by 500 fit

    {% set images = craft.imager.transformImage( asset, craft.businessLogic.imageFit(500,500) ) %}

    Creating 40 by 40 thumbnail

    {% set images = craft.imager.transformImage( asset, craft.businessLogic.imageFit(40,40) ) %}

{% endif %}

(The craft.businessLogic just returns a transform array with my standard settings like sharpening etc, that works fine).
Any ideas why that is not working?

Hi,
Sorry for the late reply. I've tested this now, and this works for me. Did you figure out what was wrong? If not, what kind of asset source is this? And are you able to transform the images with imager from your templates?

(Might be worth adding your own plugin log to help isolate these thing by the way!)

Imager has its own log file, but this is an exception being raised, which Craft logs to its log files.

No worries at all!  I haven't solved it, no.
Yes, I can transform them in templates just fine.  And very similar code in an entry works fine, just not on the asset.
Having a few days off for Easter so might not get back to this next week but I'll do another test then and see if I can add anything else useful here!
Have a nice break if you're having one!

Hey Andre
Ok, I just tried this again on my main dev server and it's working fine.  So must be something funky going on with my more basic home dev setup (I use LAMP at work, WAMP at home...should set up a proper LAMP or at least MAMP at home I guess!).
Sorry for the noise, this does appear to work and is awesome :)

Sorry andre, this has popped up again.  It's intermittent though.  The upload itself always works, but then the whirring wheel just keeps on whirring, often, while it's supposed to be doing the transforms.
It appears to occur in sub folders, not the root.  Weirdly, when we then upload the file to the root and manually move it in to an asset subfolder, it tells us the asset exists.
For the moment I am back to letting page load do the transforms, as I'm not far from launch, but if you can think of anything let me know and I will come back to this in a few weeks once I'm past the initial launch.

Ok, I'll have a look.

Wow, this issue has been hanging around for ever. I've tested on several occasions, not being able to reproduce. I've also used it this way on a recent project, without experiencing any bugs. I guess you've probably moved on now, but.. Encountered it recently?
It might be that the way Preparse now works (after the 0.3.0) is better for this kind of scenario, since it parses the fields after save. Also, there were a number of path issues in Imager that was fixed around the time you had this issue, might have had something to do with that.
Closing this for now, let me know if you encounter this again.

I haven't tried it for a bit actually - so many changes of since then, so yep close and I will re-open should I encounter.


feat: finish compare table

Is this ready for @LiuJi-Jim to review?

Is this ready for @LiuJi-Jim to review?

Sure.
@LiuJi-Jim PTAL.


Question: PSR0

I suggest to turn off PSR0 fixer from cascading PSR group (currently using PSR2 uses PSR1 and PSR0 as well). PSR0 was deprecated and in fact when using PSR4 I must disable PSR0 fixer.
This should be done after #857.
What do you think guys ?

I disagree with the point 3 though. the PSR-0 Fixer is currently a risky one (probably the most risky of all our fixers because instead of breaking your code, it has the power of breaking other projects depending on your code by introducing BC breaks in your libraries). The PSR-4 fixer would also be risky for the exact same reasons. So it should stay disabled by default.

We definitely need separate fixers, no question about that - we're all agreed there.
We should definitely disable psr0 by default - we're all agreed there.
We should probably enable psr4 by default - I like this, but I'm not sure if there is total agreement.
I think we should remove the psr0 fixer in 2.0 - other people think we should just keep it.

1,2, :+1:  3,4 :-1:   :)
btw. I think this talk together with https://github.com/FriendsOfPHP/PHP-CS-Fixer/issues/857 comes to a conclusion for: https://github.com/FriendsOfPHP/PHP-CS-Fixer/issues/117

@keradus
:+1:


v1.15 Backports 2024-12-12

[ ] #30624 (@chaunceyjiang)
[ ] #30933 (@pippolo84)

Once this PR is merged, a GitHub action will update the labels of these PRs:
 30624 30933

Superseded by https://github.com/cilium/cilium/pull/36560


Managed Yara Exceptions

I added a managed exception for each of the Yara error codes. I left code 1 to be the standard OutOfMemoryException, as there might be projects out there that depend on this, and it's already pretty appropriate.

Yay 😊
Chris Davies (MSTIC)
Senior Software Engineer
United Kingdom
TI - Science
Mobile: +447960650292
christopher.davies<EMAIL_ADDRESS>[MSFT_logo]
From: stellarbear<EMAIL_ADDRESS>Sent: 09 October 2019 16:27
To: stellarbear/YaraSharp<EMAIL_ADDRESS>Cc: Chris Davies (MSTIC<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>Subject: Re: [stellarbear/YaraSharp] Managed Yara Exceptions (#7)
Merged #7https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fstellarbear%2FYaraSharp%2Fpull%2F7&data=02|01|Christopher.Davies%40microsoft.com|ba64c6ca1ed34c96c3a008d74ccd2735|72f988bf86f141af91ab2d7cd011db47|1|0|637062316325243728&sdata=PJuvL4NEy6lUn13FFXKhhewdLx9lm3I4ekIyHi%2FqHe8%3D&reserved=0 into master.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fstellarbear%2FYaraSharp%2Fpull%2F7%3Femail_source%3Dnotifications%26email_token%3DAK3UDG3IFEUZJRZPGIVZ5EDQNXZ45A5CNFSM4I64ZFC2YY3PNVWWK3TUL52HS4DFWZEXG43VMVCXMZLOORHG65DJMZUWGYLUNFXW5KTDN5WW2ZLOORPWSZGOUDTLYCI%23event-2699475977&data=02|01|Christopher.Davies%40microsoft.com|ba64c6ca1ed34c96c3a008d74ccd2735|72f988bf86f141af91ab2d7cd011db47|1|0|637062316325253687&sdata=YJ8t2ldW56S3GERH5L4ECHddhEKkEXkw391Kt0GhbHU%3D&reserved=0, or mute the threadhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAK3UDG6QSMCGAK7VZ3ON5FLQNXZ45ANCNFSM4I64ZFCQ&data=02|01|Christopher.Davies%40microsoft.com|ba64c6ca1ed34c96c3a008d74ccd2735|72f988bf86f141af91ab2d7cd011db47|1|0|637062316325253687&sdata=Q9bL62eQf8BV%2BNCQaohERpnQ0wnr9E3bKH56SIm4Ljc%3D&reserved=0.


Display the full path of respositories deeper in the directory hierarchy

This resolves #391 and #521 (which is a duplicate of the former), in a clean manner.
This pull request avoids the use of realpath, which was proposed in #536.

@Hologos Sorry, did not see your included patch in #689. You might want to consider whether the here proposed solution is cleaner or not.

@peterverraedt I'll have to search in my memory to find all use cases which were broken to check if your proposal solves them all. @klaussilveira will have to decide which proposal will be merged. :-)

@klaussilveira can you tell us, why this can't be merged. I don't think this is against the policy, keeping GitList simple, as it just adds structure into the list of repositories making GitList useable for larger sets of repositories.

@alehaa This functionality has been included in PR #689 (although it's my implementation).

@alehaa This functionality has been included in PR #689 (although it's my implementation in commit 8dacca4490313305b901ae82589cdb60ab593951)

@Hologos as described in #689, I'm not sure about this PR. I'd prefer to merge just this feature first, so we can discuss the details of the Gitolite integration later.


How to handle absolute path annotations

Opening this issue to spark discussion.
How should we handle full path annotations? By that I mean Top.a.b.c.foo instead of a Module-relative annotation like Top.foo. I'm not sure if Chisel even emits these but they can be specified. I'm also pretty sure that most transforms do not handle them correctly if at all.
In most cases, I think we can convert absolute path annotations into Module-relative. Without deduplication, these are equivalent. With deduplication the question gets a little hairier. Perhaps Modules should not be deduped at all if their annotations are not identical, that would make the problem very simple and mean that we can always safely make the conversion.
Thoughts?

I think most often differing annotations implies the modules should not be de-duped. Only case I can think of where thats not going to be the case is if you were trying to include some physical design information as an annotation. For example, I have two cores that are identical and I want to place and route them once and then instantiate them but I want to mark each one with its top-left corner as a physical co-ordinate. I don't think this kind of annotation is reasonable but its an example I thought of.

What does it mean to de-duplicate in this case, anyhow? If it means that MyFooCore_1 and MyFooCore_2 get de-duped, what stops us from just instantiating two MyFooCore's (de-duped) and then just positioning them differently? Am a bit confused here.

Yeah. I'm saying there are alternative solutions to the core positioning problem that don't involve firrtl annotations.

Closed via Target.


Remote Radio Button Values: Best Practices

I've got radio button values that come from a service call (REST) and was wondering what the "right" way was to tell formly about them.
I can think of two options off the top of my head:

don't set the fields attribute value in the controller until after the data is loaded.
append to the fields array after loading (it appears formly watches both the fields array and each field item in the array)

Maybe there's more?  Thoughts?

Hmmm.... It really depends on the experience that you want to give your user... I wouldn't say that either of those is necessarily the "right" way to tell formly about them...

I'm open to your suggestions/thoughts on this.
Right now I have it making a service call (the second option) when the controller function is loaded and just pushing a new item into the fields array.  I suspect I'll have to wait until we deploy to production to test the full on latency/UX ramifications of this because on my machine and on our QA servers it's loading fine w/ almost no noticeable delay - even using the mobile network throttling feature of the Chrome debuggger - I took it down to 2G and it was still fine.  It's only 848 bytes of uncompressed data and we have compression turned on.

So, what I would recommend is using a router resolve feature which allows you to make requests before a controller is loaded and inject the results into the controller. That way you keep your controllers as synchronous as possible. This is just good practice in general in my opinion.

I'm already doing that for our $modals.  Never occurred to me to do that for remote data.  I like it, thanks.


docs(config): add info about installation steps

Description
This PR contains the steps to install the lib and plugins.
Additional context

What is the purpose of this pull request?

[ ] Bug fix
[ ] New Feature
[X] Documentation update
[ ] Other

Before submitting the PR, please make sure you do the following

[ ] If it's a new feature, provide a convincing reason to add it. Ideally, you should open a suggestion issue first and have it approved before working on it.
[X] Read the Contributing Guidelines.
[X] Read the Pull Request Guidelines and follow the Commit Convention.
[X] Check that there isn't already a PR that solves the problem the same way to avoid creating a duplicate.
[ ] Provide a description in this PR that addresses what the PR is solving, or reference the issue that it solves (e.g. fixes #123).
[ ] Ideally, include relevant tests that fail without this PR but pass with it.

Hello! Thanks for your PR! However, there already are install instructions for each supported frameworks.


feat: save files within combine archive to s3

:tada: This PR is included in version 5.0.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Graphnet, GraphSage comparison

Hi,
Any comment on how NSL positioned with respect to DeepMind's Graphnet, or Graphsage?

Also interested in this topic.

Hey Bora & Lita,
Thank you for your interests in NSL : )
First, NSL is a TF library and part of TF ecosystem, which means users can enjoy all the nice features (eager execution, Keras APIs, distributed training, etc) from TF2.0 when using NSL. NSL also provides graph tools for users to construct & parse the graphs.
In terms of graph algorithms, NSL currently focuses on graph regularization and related techniques.
From my personal understanding, GraphSage focuses more on learning node embeddings by using random walk, and Graphnet is to provide fundamental operations for users to build custom models.
We do have an ambition to include more graph algorithms & models in the NSL framework : ) You are welcome to suggest graph algorithms that you want to play with when using the NSL framework.


Support Nested Json Objects in Angular Translate

@borisyankov  Angular Translate Supports Nested Json  Objects like the example given below
https://angular-translate.github.io/docs/#/guide/02_getting-started
{
"NAMESPACE": {
"SUB_NAMESPACE": {
"TRANSLATION_ID1": "This is a namespaced translation."
}
}
}
But the definition of the ITransitionTable restricts the support of Nested Json Objects
Current definition of ITransitionTable
interface ITranslationTable {
[key: string]: string;
}
Here we can have the value as only string and not Nested Json Objects.
I was wondering if  we can  change the value type to "any" in order to support Nested Json Objects.
interface ITranslationTable {
[key: string]: any;
}

@defaude

@deryl27 thanks mate!


Add a little bit of hierarchical config for converter encryption - previously converters

only looked converter.encrypt.*, but this breaks down if there are
multiple converters in a chain that are doing encryption. This change
allows you to specify config at converter.<ConverterName>.encrypt.*
I think this approach is a little cleaner than a positional approach (converter.0.encrypt.foo), but don't know if you have thoughts @htran1 or @ibuenros . Also definitely want to document this somewhere and/or make the config parsing a little more generic. I know Typesafe Config can handle some of the heirarchy stuff as well.

going to merge this to unblock work but comments still appreciated.


Feature request: Make it possible to enlarge images by clicking on them

I think it would be great if it was possible to open images in the ImageViewer either in the same tab or a new tab by clicking on them.

+1 for this

Resolved by #68.


New loading before rendering

Fix #47: see my comment there.
Content of this PR:

Putting the fallback of <SuspenseEmbed> to <></>: no annoying "Loading..." anymore.
Adding pure CSS skeletons that match perfectly ("at least on my machine") the shape of the <FormLabel> and <FormControl> of the <LoginCustomFormField>: this way, there's no more dependency and the size of the <CenteredCard> is preserved.
Version +2 because I forgot to update it in my previous PR.

We may want some refactoring later for the CSS and the <Suspense>-derived tags...

How the skeletons render on my phone:

I artificially made them last a bit longer here for the video's sake.
If you zoom and use slow motion, it's imperceptibly taller with the skeletons.

https://github.com/user-attachments/assets/9a91f0ef-18bb-4e5d-9a45-1301b30ce4b4

Rendering on phone (see above for comparison): imperceptibly shorter this time
https://github.com/user-attachments/assets/ec1d4df9-83c1-47ad-a228-1f3b08761895


Hanning/ma 334

Android: As a student, I can create a new edX account using Google and Facebook. Break down to two parts for review:

UI and workflow  [for this review],  the service api call is a mocked one for now.
Based on real service response, show different message [TBD]

@BenjiLee @rohan-dhamal-clarice @aleffert

Review finished

@aleffert @rohan-dhamal-clarice  @BenjiLee
Modified code to new workflow.  also some code refactoring based on code review

@aleffert  @BenjiLee  please review.

:+1: for commit 1177242

:+1: except for one last thing I forgot about. We should check the config if google and facebook are enabled to decide whether to show the UI. If they're not, we should hide the social sharing section


Include occupancy sensor from SiLabs

Problem
Occupancy Sensor/Sensing cluster is missing.
Summary of Changes

Imported the cluster from SimplicityStudio_v5 gecko_sdk_suite/v3.1/.
Moved to C++
Adapted to CHIP codebase.

Please check whether this code can accepted. License has been adapted similarly as the other already imported clusters.

FYI @jepenven-silabs @jmartinez-silabs

Should I include a commit with the files changed by ./scripts/tools/zap_regen_all.py?

@markus-becker-tridonic-com looks like conflicts again, but also - can we add reporting to this? Reporting definitely works and is supported today.

@markus-becker-tridonic-com looks like conflicts again, but also - can we add reporting to this? Reporting definitely works and is supported today.

will solve the conflicts.
the commented code is about out-of-the-box reporting. which seems to be bound to SiLabs code. reporting is working (verified with https://github.com/project-chip/connectedhomeip/pull/6138).

The 2 failing CI tests seem unrelated.

@markus-becker-tridonic-com looks like we have merge conflicts + Darwin CI is failing :(

@markus-becker-tridonic-com looks like we have merge conflicts + Darwin CI is failing :(

Fixed now.

/rebase

ping @markus-becker-tridonic-com

@woody-apple conflicts resolved and all checks passed.


[BUGS] Frontend Mobile view bugs

Description

Can we spread out the Where HELP meets NEED. text for mobiles ? It looks to compressed.
Can we hide the marked image in Screenshot 2 only for mobiles.
The words So why not help millions by sharing your love ? can continue in the same line as the Happiness increases when you share your love. ,

Screenshots

Additional information

These changes are only based on mobiles
Make sure they are looking good.

🥦 Browser
Brave
👀 Have you checked for similar open issues?

[X] I checked and didn't find similar issue

🏢 Have you read the Contributing Guidelines?

[X] I have read the Contributing Guidelines

Are you willing to work on this issue ?
No, someone else can work on it

Hi, I'm an open-source newbie and would love to make my 1st code contribution. Can you assign this task to me?

I'd like to work on this issue


user permissions

Hi
What kind of user permissions are needed to set this up? I dont have any admin rights only normal user.
Thanks

Hi @jeanpeus,
No special permissions are needed.
If you can run homebridge you an run this plugin.


add a jsnext:main so we can distribute ES6 modules

Also add modules to the distribution files and relevant docs to README and CHANGES.
See https://github.com/rollup/rollup#can-i-distribute-my-package-as-an-es6-module

I don't think this is a good idea.

Our test coverage runs against the Babel transpiled files, so we don't actually verify functionality when using e.g. rollup directly
The shipped npm package only includes lib/ and doesn't include modules/ at all
The source uses ES7 features like class property initializers and would still need to go through Babel again anyway, so it's not sufficient to just use a ES6-aware bundler
rollup has minimal adoption next to e.g. Browserify and webpack and I think pointing to it in our README is just going to confuse users

We do have to resolve this to let users take full advantage of webpack 2.0, but I'm not sure this PR is a good way forward.

As it stands, I think if we wanted to do this, we'd have to ship e.g. a es6/ build that transpiles everything except for the module system. It's not a good idea to ship the raw source instead of the transpiled source; packages in general should not make users deal with transpiling their code.
Additionally, I'd much rather point users at webpack v2.0.0-beta rather than rollup, just because webpack has a lot more adoption and people who otherwise haven't already made a choice of package bundler would likely be quite a lot better served by going there, in terms of e.g. their ability to get help or find examples or documentation.
I'm going to close this PR for now and open a new issue for discussion. I like the idea on paper of shipping an ES6 module build that allows users to both import from react-router and not include modules that they don't use, but just exporting our raw source is not the correct way to do this.

We'd appreciate hearing your thoughts on #2524. If we do decide to go with exposing modules/, I'd be happy to re-open this PR, but I think there are better options available toward this end. It'd be good to get some discussion before just adding another build target, though.


Rainbow incompatible with vendor/bundle and rubocop styling gems

When installing rainbow (From other gems), to vendor bundle. It is copying down the extra files, such as rubocop config e.t.c.
Because these files are copied, they are being lazily loaded in (I'm using a custom rubocop config), when using other gems, there is a conflict in TargetRubyVersion.
This then causes the entire build to crash with something like
error: RuboCop found unsupported Ruby version 2.1 in `TargetRubyVersion` parameter (in vendor/bundle/ruby/2.7.0/gems/rainbow-3.0.0/.rubocop.yml). 2.1-compatible analysis was dropped after version 0.58.
Supported versions: 2.4, 2.5, 2.6, 2.7
rake aborted!

Solution: Remove all non-necessary files in the gemspec. This is a blocking change meaning we've had to uninstall rubocop for now.

The issue has been fixed, but not yet released.

https://rubygems.org/gems/rainbow/versions/3.1.0 has been released, so I will close this issue. Thanks for the patience!


Change mirror glass texture

Great work !
Thank you Ataron, we will try this texture for the next server update ! :)


[Question] OWSLib can have dots in typename parameter?

Hi,
the OWSLib support name with dots in typenameparameter?
I test with the default links with underscores but when i do the same test with a WFS service with dots in the typename i have the 404 error response.
The  code:
from owslib.wfs import WebFeatureService

wfs11= WebFeatureService(url='https://ows.isip.ifap.min-agricultura.pt/isip.data/ows', version='1.1.0')

response= wfs11.getfeature(typename='isip.data:ocupacoes.solo.aml.2016jun10')
out= open(r'C:\Users\User1\Desktop\oc_solo_aml_2016jun10.gml', 'wb')
out.write(bytes(response.read(),'UTF-8'))
out.close()

The result:
Traceback (most recent call last):
  File "ifap_parcelario.py", line 5, in <module>
    response= wfs11.getfeature(typename='isip.data:ocupacoes.solo.aml.2016jun10'
)
  File "C:\OSGEO4~1\apps\Python27\lib\site-packages\owslib\feature\wfs110.py", l
ine 243, in getfeature
    username=self.username, password=self.password)
  File "C:\OSGEO4~1\apps\Python27\lib\site-packages\owslib\util.py", line 189, i
n openURL
    req.raise_for_status()
  File "C:\OSGEO4~1\apps\Python27\lib\site-packages\requests\models.py", line 90
9, in raise_for_status
    raise HTTPError(http_error_msg, response=self)
requests.exceptions.HTTPError: 404 Client Error: Not Found for url: https://ows.isip.ifap.min-agricultura.pt/isip.data/wfs?typename=isip.data%3Aocupacoes.solo.aml.2016jun10&propertyname=%2A&version=1.1.0&request=GetFeature&service=WFS

Cheers,
João

Please post questions to the OWSLib mailing list. OWSLib's GitHub issues are for software bugs/enhancements and related tasks.


[NG] Datagrid: selection behavior on state change

Select one ...  (check one with "x")
[x] bug
[ ] feature request
[ ] enhancement

Expected behavior

What should be the behavior of the current selection when the state of the datagrid changes in any way? State change includes page change, filters change, data refresh from the server, ...
Once UX settles on the most natural behavior for the user, we can start implementing it.
A few use cases to consider, but please note that this list is absolutely not exhaustive!

User moves to a different page. Most natural behavior here is that the items selected in the previous page stay selected.
User stays on the same page, but adds a filter. Already selected items might be filtered out. Do they stay selected? I believe this would be very unexpected to the user.
User selects an item, then moves to the next page, then modifies a filter. The selected item from the previous page is not visible on the screen, the user doesn't know if it has been filtered out or not. Does the item stay selected?
User selects items and moves to different pages, but the datagrid refreshes its data from the server (either automatically through a "heartbeat" or based on some user action), deleting and adding new items all over the datagrid. What should become of the current selection? Especially items that completely disappeared from the dataset?

Actual behavior

Currently, since the behavior hasn't been decided on, we've literally had a TODO in the code since v1 of the datagrid. I can't believe this issue hasn't been posted on GitHub yet. We simply erase the whole selection whenever anything changes. This has been raised as an issue for apps that need to preserve the selection across pages.
Reproduction of behavior

See the current behavior on the live "full demo" example in our documentation: https://vmware.github.io/clarity/documentation/datagrid
Environment details

Angular version: 2.X

Clarity version: 0.8.X

Browser: all

If a user makes a row selection and navigates to another page (pagination), the selection should persist. There should also be a visible system status of the count of selections made, incrementing as a user makes more.
If a user selects something and filters against the data, the selection is lost. The complexity of designing to and handling those edge cases seems overly unnecessary.
User selects an item, then moves to the next page, then modifies a (an existing) filter. The selection is lost, only modified filtering is done
If a user selects and there is a data refresh (heartbeat), if we can, we should persist the selection (assuming it is still available)
That said, if it is possible, I could see persisting the selection after filtering if it is still available. We could possibly even go further to notify that selections not in the filtering were lost. Both of these things seem to complicate things unnecessarily.

Say we do 1-4 above and wait to see what happens. If we then get a lot of feedback about people needing the 5th item, we could then look to implement it.
or something similar to #5, some message saying that some selections were lost in the refresh

@youdz you had mentioned two different implementations for the count indicator: icon & number, and text & number. Here are screens for each.

I think we can go with the "icon & number" version
If we go with "text & number", it would need to have override hooks built into it for internationalization
Count indicator would show after one row selection, hide after all rows have been deselected

Just realized Count Indicator sounds like a vampire name...

Hi. This is a critical feature for our VMWare project. Rddolan's 1-4 would be  great. We need to be able to paginate across 1000-2000 items (VMs) and retain selected items. Would like to allow sorting without losing selection, but I suppose if there s a filter change we would be ok losing selection. We need this in the next few weeks. Any ETA or predicted version for this fix ? Also is there a recommended hack for us to get around this issue until then ? Otherwise we may have to bail on datagrid :(

I have a workaround for preserving selection:
https://plnkr.co/edit/C9SzUi?p=preview
In its current implementation it will not work well with filters and sorting. But you can build on it, if this is hard requirement, and you don't get satisfactory ETA.
Note that I am not part of the core Clarity team, so consider this as a peer hint, not as a Clarity "recommended hack" 😃

Hi @reddolan @youdz
Shouldn't we have a broader discussion before stating that you are going ahead and implementing something right now and only changing it afterwards if there is "a lot" of bad feedback?
I could give you many examples with datagrids containing thousands of items. The user's only help in these situations is the ability to filter to find the items they need (otherwise they'd have to page through literally hundreds of pages). Losing the selection would basically be a stopper for these workflows. Most probably whenever a grid has more than 2 pages, people would tend to use filtering instead of paging...
Since you are planning to have an indicator in the footer, is preserving the selection of "not visible" items really an issue at all?

@halachliyskid Users have an idea of what they are looking for in thousands of rows in dataset, and filtering/sorting to start off will help make the data more manageable. Selection and filtering both have unique goals. These actions aren’t necessarily tied to one another at the same time. Users would be doing themselves a favor by filtering the data down, and then making selections. Here are a couple things to think about:
First complexity: A user wanting to select a bunch of items and then filter would be a confusing interaction. Are they expecting data to be filtered against just their selection or across the entire dataset? I could see both use cases arising. This means that we would need to figure out how those independent experiences are handled, both in datagrid design and experience.
Second complexity: If a user were to make selections, then filter, and all selections show up after filtering, then no problem. However, what happens if one or many selections are not part of that filter criteria? We need to notify the user of those instances. If it is only a few, not a huge issue. But if several are lost? The user will specifically want to know which ones are lost?
We made a conscious decision on how to handle selections being made before filtering. This decision was to reduce the complexity in design and development work needed for this. Also, the need to select and then filter is more of an edge case than the majority of cases.
I understand your comment on “changing it afterwards if there is 'a lot' of bad feedback”. That is why I said previously, if we get a lot of feedback about people needing it, then we can look into it. The feedback will help us understand if this isn’t an edge case and is a higher use case than we had anticipated. In the meantime, users are still able to use the datagrid with filter and selection without poor experience.

Hi guys,
It's great that you decided to have a public discussion on this, based on user feedback.
I am an engineer, not a UX expert (although everyone considers himself an expert in football, politics and UX nowadays 😈).
So I will present you with my point of view, which is the engineering and dev point of view.
The data of a grid should be considered as something monolithic, something basic and predictable.
As it can be large, we can't see all the data at once and we might want to make it easier to find items in it. Our view of the data is limited. All sorting, filtering, pagination, are operations on the view. They don't change the data itself.
Selection on the other hand is operation on the data. I select many items to perform a single operation on them. I may apply one or more view operations, simultaneously or subsequently, to easily find/navigate to my items, but when I select an item, my expectation is to be doing this on the data layer, not on the view layer.
Losing the selection comes as a surprise to me.
That's my 2 bitcoins 😄

@Jinnie thanks for the comments - I absolutely support that.
@reddolan
You're saying that sorting and filtering are two very distinct things - then why are we making a hard connection between them (using filter removes selection)? If they are unique operations, then they have to be able to work at the same time. I do not see this as an edge case - I'd ask the question: "Why is someone filtering?".
Is it because they just want to read the info from a datagrid? I wouldn't agree with this.
Datagrids are typically used by our users to either navigate to a single object, or perform an action on a single object, or perform an action on multiple objects at the same time.
Multiple selection using checkboxes (our case) is aimed exactly at allowing to easily perform actions on multiple objects.
The most common filter criteria I can think of is "Name". It's obviously unique and if I have to search for 2 objects using the filter (instead of going manually though 10 pages), I'll never be able to perform the action on these 2 objects at the same time.
I do not think this qualifies as an edge case.
First complexity: I don't recall a UI which behaves in the way you describe. Is there user research data suggesting that if people need to use selection + filtering, they get confused thinking that filtering only works on the selected items?
Second complexity: In your design, there is a selection counter in the datagrid footer. Couldn't it be used to handle this?
I fear that by reducing the complexity on the design and development part, we are increasing the complexity for the user and in fact breaking some workflows.

There is one case, though, that I am uncertain about.
Performing "Select All" on filtered (and possibly paged) content.
@reddolan, @halachliyskid, what are your thoughts about that?

@Jinnie, I agree with you that datasets can be large and our view of the data is limited. That’s why sorting and filtering help users narrow down what they are looking for and interact with that subset of the larger view. We spent a lot of time discussing this topic and made a conscious decision to not persist the selection after operations such as sorting and filtering have been applied, post-selection. The decision to do this is largely based on usability problems that arise in these cases, and not around the debate that this can satisfy edge (or possibly a bigger set of) use cases.
There’s no question that filtering will narrow down a single object, or multiple objects that a user can perform an action on at the same time; that is the purpose of batch selection. However, it is problematic to allow the user to perform actions that affect other pages that the user can’t see and has to rely on memory to recall what was selected – this is an anti-pattern. It is important that the user is aware of the consequences of their actions and has the ability to view and undo selections that they have made. Otherwise they will need to start over and redo everything, especially if the action is destructive. In this scenario, the selection count loses meaning and becomes guesswork. For example, if the filtered view is the only visible set of data and nothing is selected but my count displays 40 selected items, again I may not remember or be able to verify what it is that I’m performing an action against.
While I see the possibility that a user may rely on filter and re-filtering to locate what they’re looking for to perform a batch action, I don’t think that this case justifies the complexity in the experience and the additional cognitive load required to figure out what the count means with no easy way of undoing the selection(s). The risk is minimized by pushing the user to filter the data down first, then make selections and to perform actions against filtered data, versus a lot of upfront work that can result in uncertainty. The compromise is that the user will have to do this in smaller, manageable chunks rather than large, batch actions, but I think the minimized risk is worth it.
Thanks everyone for your thoughts on this, all is greatly appreciated. We’re going to move forward with Red’s original recommendation so that we can release this fix soon, and continue to monitor feedback around this feature.

@yenmade, thanks for the detailed answer.
I understand your point and respect your research and decision.
Popular services like gmail and yahoo mail preserve selections on filtering or paging. On the other hand MS OWA is not preserving selection.
There are different approaches, different solutions, and you've made your choice.
Also, if a user really needs it, there are ways to achieve selection preservation with some additional code outside the component itself.

What @halachliyskid described is a very important case and also a pretty common one. Selecting more than one item with very different names(so that you can't have a common filter for them) among thousands is practically impossible when you lose the selection in case item is filtered out, so I can see that issue as a must fix. I would also vote for including a selected items indicator in the grid footer which will absolutely remove any confusion that some clients might have when they have filter out the selected items. You may also include a very tiny button for example "X" next to the selected items which will clear the selection.
Another aspect that is pretty important for me is restoring the grid selection when new data is set on the grid but the items are practically the same. To implement this and also the suggestion above you may need to have a reliable way for comparing the items from the grid's dataprovider. Since it is actually a client's logic to compare the items then you might solve this issue by providing an option for the clients to provide callback function that should be used for comparison. For example the function might have the following signature:
function areEqual(first: any, second: any): boolean;
Then all you have to do is check if the function is provided and if that's the case then use it to check each of the objects in the selected array for equality against the new data array. In case equality is fact then you just replace the "old" object in the selected array with the corresponding object from the new data array and I believe this should be enough for this feature.

Closed by #632.

Looking at this thread it tells me that filtering will remove my current selection.
My use case is that I have a property in my object that I want to bind the selection to using the approach described in the docs:
<clr-dg-row *clrDgItems="let item of items" [clrDgItem]="item" [(clrDgSelected)]="item.selected">     <-- ... --> </clr-dg-row>
Now, I think filtering should not affect me in this case since the model would persist the selection and not the datagrid itself. But it still removed the selection.
Is there anyway this can be achieved?
Luis

Guys,
I see this closed, but this is a blocker for us.
Here is our use-case:

We I have a bunch of items in a grid (300)
When the grid is loaded there are preselected items. Let's say 10.
Then I want to select a specific item and I know it's name, but I don't know on which page it is.
Now I can filter, but I will lost the selection or I can go through the pages and search for the item.
This is very inconvenient.

My expectation is that the selection is persisted. I would expect that after removing the filter I would have my items selected again.

For those following this issue, we have opened a new issue with the intent of solving this scenario. Please subscribe to the new issue for updates


Represent Virtual/Physical Clusters In Model

I think we need to make virtual and physical clusters first class in the model.  This is required to allow kroxy to support clusters with more than 1 broker, multiple clusters.  It is also an enabler for multi-tenant.

Thanks for the PR @k-wall :bow:

It's not clear to me whether we really need virtual and physical brokers to be things surfaced in the configuration. I can see that doing it that way starts out simpler, but that's because you've hand-waved some of the essential complexity into an operator which will need to orchestrate reconfiguration, coordinating with orchestration of the broker cluster(s).

One possible alternative would be to allocate endpoints automatically, based on the information about Nodes which propagates to clients via MetadataResponse, DescribeClusterResponse and FindCoordinatorResponse. You'd need a suitable function (a bijection, actually) for allocating the SNI matcher and port (in particular it needs to guarantee that no two brokers, even from different physical clusters, can map to the same endpoint). But that's relatively trivial. You'd also need the machinery to trigger the socket bind based on that. However, I think this might significantly simply operations:

Scaling in a broker cluster doesn't require external orchestration of the proxy cluster. New endpoints get created automatically.
There is less validation of the configuration (i.e. you can assume the known+tested properties of the endpoint allocation bijection)
Even under the brokers-as-configurables model, this bijection would eventually need to exist anyway, except it would be in the operator.

I think we need to support mapping Kafka clusterIds. I.e. A clusterId needs to be a property of both virtual and physical clusters, with support for mapping between the two. This is necessary so you can't infer multitenancy from observing the same clusterId (e.g. in MetadataResponse) for two distinct virtual clusters which happen to (currently) share the same physical cluster.

It's not clear to me whether what's proposed here makes it harder to implement "simple proxies". I think it would be good to think about how minimal we could make the configuration for the simple proxy case.

Thanks for the great reply.

One possible alternative would be to allocate endpoints automatically, based on the information about Nodes which propagates to clients via MetadataResponse, DescribeClusterResponse and FindCoordinatorResponse. You'd need a suitable function (a bijection, actually) for allocating the SNI matcher and port (in particular it needs to guarantee that no two brokers, even from different physical clusters, can map to the same endpoint). But that's relatively trivial. You'd also need the machinery to trigger the socket bind based on that.
The design was avoiding the need to dynamically bind the listening port for the virtual brokers.  That's what lead to statically defining the virtual brokers, and as a consequence lead, to static definition of the physical brokers too.  I'd love to avoid that configuration too.
Why do I think dynamic ports are a problem?  If we have kroxy dynamically assigning ports, does that not present problems exposing a service at a kube level?  I imagine a kroxy operator will add kube services corresponding to each virtual broker to route the traffic to the kroxy pod.  We will want to be able to scale kroxy replicas.  If we have a reliance on  dynamically assigned ports, different kroxy instance will likely bind to different port.   I'm not aware of a way to express that at Kubernetes service.   The targetport for tenant A's broker1 needs to be the same for every kroxy replica.
So I think for good kube integration, kroxy needs to support a statically defined port binding.
If we were willing to accept that kroxy's downstream exclusively supported TLS, we could use a statically defined listening port and use SNI to route to the different virtual cluster and their brokers.  I think it is likely production use-cases will be TLS, so I don't really see that as a problem to production users.
However, the development/testing/demos on a laptop, having plain connections without the faff on TLS certs and /etc/hosts munges is really appealing.
We could try to find a way to express both binding models.  WDYT?
1
If you had kroxy dynamically assigning

I think we need to support mapping Kafka clusterIds. I.e. A clusterId needs to be a property of both virtual and physical clusters, with support for mapping between the two. This is necessary so you can't infer multitenancy from observing the same clusterId (e.g. in MetadataResponse) for two distinct virtual clusters which happen to (currently) share the same physical cluster.

That's a good point, I hadn't thought of that.  We could have a filter that intercepts the DescribeClusterResponseand produces a stable clusterid from the digest of the physical cluster's cluster id and some immutable property(s) of the upstream cluster definition.  That might be the FQDN of the cluster's bootstrap or in the case of multi-tenant a tenant prefix).   We'd need to ensure upstream cluster id stability across kroxy replicas and pod restarts.

You'd also need the machinery to trigger the socket bind based on that.

I think that's doable.  Kroxy would need to bind listening sockets corresponding for the upstream clusters' bootstrap addresses.  Kroxy would somehow need to snoop the describecluster or metadata response and use that as a signal to bind the listening sockets (for the brokers). Then on each subsequent connection it needs to validate if the set of required set of listening sockets has changed.

One possible alternative would be to allocate endpoints automatically, based on the information about Nodes which propagates to clients via MetadataResponse, DescribeClusterResponse and FindCoordinatorResponse.

I think this is pointing, however much better expressed, to the same place as my suggestion of providing Kroxylicious with a set of credentials and a bootstrap address for the physical cluster and using that to generate the physical broker topology. I know we have said dealing with subsets of brokers in the Multi tenant case is out of scope but would this change make that substantially harder? I'm not sure I
Removing the definition of virtual brokers from the configuration model also implies that Kroxylicious becomes the arbiter of the broker hostname, the domain comes from the virtual cluster definition. I guess we could add some sort of plug-able name generation scheme.

It'll be cleaner if I start I new PR.


allow to specify includes in singular get endpoints; add base filters for scenarios, projects and organizations [MARXAN-212] [MARXAN-213]

See https://vizzuality.atlassian.net/browse/MARXAN-212 and https://vizzuality.atlassian.net/browse/MARXAN-213

Ok includes for the specific relations works for me; said that users retrieve me an empty array; not sure if that should be the case. Apart from that tada

yes and no - the array should be empty because we don't actually have any code that associates users directly to other entities right now, except a few INSERTS in the test data seed that gives users roles on seed organizations and projects...
In this phase we'll only support granting users roles on organizations, but my plan is to create implicit roles on projects (maybe not scenarios) that are part of each organization, so this property may eventually get populated for projects too. For now it is expected for the users prop to always be empty.


Allen Heath AHM updates

Chasing some more control in the Allen & Heath AHM control like 48v, volume control, etc.

Lots of features have been added to the module since this request, including level adjustments.
If there are still specific features not addressed, please submit a new issue for the specific feature.


add db_id as primary key to auth databases

Overview
We'd like to keep the primary IDs of our databases immutable and safe from users.
Currently, roles and projects have a db_id column, but only roles uses it as the primary ID. Policies, teams, and tokens all use the id as the primary ID, and they have no db_id column.
Let's make our databases consistent, with each resource table (policies, roles, projects, teams, tokens) using an integer db_id as the primary ID. All relational tables should be updated as necessary.
Use db_id internally.
Subtasks

[x] update tokens table
[x] update teams table
[x] update members
[x] add db_id to policy table and change related tables/constraints
[ ] add db_id to projects table and modify related tables/constraints

[x] iam_projects <-> iam_[staged_]project_rules ✔#862
[X] iam_projects <-> iam_role_projects ✔#878
[ ] iam_projects <-> iam_policy_projects:construction: @srenatus
[ ] iam_projects <-> iam_statement_projects
[ ] flip PRIMARY KEY constraint of iam_projects from id to db_id (when these ☝four are done)

[ ] add db_id, policy_id to iam_statements/ remove iam_policy_statements 🚧 @blakestier (#855)

I'm quite sick of this, but a statement's role also doesn't use the role's db_id, but its ID:
chef_authz_service=# \d iam_statements;
                              Table "public.iam_statements"
  Column   |    Type    |                           Modifiers
-----------+------------+----------------------------------------------------------------
 id        | uuid       | not null
 effect    | iam_effect | not null
 actions   | text[]     |
 resources | text[]     |
> role     | text       |
 db_id     | integer    | not null default nextval('iam_statements_db_id_seq'::regclass)
 policy_id | integer    |
Indexes:
    "iam_statements_pkey" PRIMARY KEY, btree (db_id)
    "iam_statements_id_key" UNIQUE CONSTRAINT, btree (id)
Foreign-key constraints:
    "iam_statements_policy_id_fkey" FOREIGN KEY (policy_id) REFERENCES iam_policies(db_id) ON DELETE CASCADE DEFERRABLE
Referenced by:
    TABLE "iam_statement_projects" CONSTRAINT "iam_statement_projects_statement_id_fkey" FOREIGN KEY (statement_id) REFERENCES iam_statements(id) ON DELETE CASCADE DEFERRABLE

chef_authz_service=# \d iam_roles;
                               Table "public.iam_roles"
 Column  |      Type       |                         Modifiers
---------+-----------------+-----------------------------------------------------------
> db_id  | integer         | not null default nextval('iam_roles_db_id_seq'::regclass)
 id      | text            | not null
 name    | text            | not null
 type    | iam_policy_type | not null default 'custom'::iam_policy_type
 actions | text[]          |
Indexes:
    "iam_roles_pkey" PRIMARY KEY, btree (db_id)
    "iam_roles_id_key" UNIQUE CONSTRAINT, btree (id)
Referenced by:
    TABLE "iam_role_projects" CONSTRAINT "iam_role_projects_role_id_fkey" FOREIGN KEY (role_id) REFERENCES iam_roles(db_id) ON DELETE CASCADE


Error when running CLI installation

Package version (if known): v6.0
Describe the bug
During installation using the CLI it fails: Failed to install dependencies.
Steps to Reproduce

Follow instructions from: https://inveniordm.docs.cern.ch/install/
When prompted choose S3 storage option (not sure if this is related)
Install from CLI: invenio-cli install
Get error

Expected behavior
Installation runs without issue
Traceback

Additional context
This seems to be an issue related to the versions of jinja and markupsafe being used. The newest version of markupsafe, 2.1.0, no longer uses soft_unicode but jinja 2.11.3 is looking for it. Jinja is no longer supporting this version, so they aren't going to do anything on their end. I can see these mismatched versions being used pipfile.lock but I'm not sure how those are being generated. I think the version of markupsafe just needs to be set to 2.0.1. I'm not sure how to test this, because it's not clear to me where the information is coming from that creates pipfile.lock.

A quick fix is to add MarkupSafe<2.1 to your Pipfile

The problem we earlier tracked down to Flask 2 not being installed even though it's supported for v6.0.

Thanks that did the trick. I needed to do something similar with ipython -- ipython = "==8.0.1" -- for a recent issue there that seems to have cropped up. After that everything went smoothly.


Add pip specifiers

This PR adds details on the pip specifiers and how to use them in conjunction with pipenv
This is related to #2816

Thanks for putting time into this, I love it! I do wonder however whether it is a little bit too long. Most people would only need >= and <= (plus their open-ended counterparts), and maybe ≠. It might be better to just “give a taste” of what is possible, and encourage people to read PEP 440 if they want more.
Using == is strongly discouraged since it prevents you from getting any updates at all, so it might be a good idea to intentionally leave it out (again, people can read PEP 440 if they need it). I also feel ~=X.Y should be preferred to ==X.*.
Finally, some of the commands in the write up are not very compatible across various platforms. pipenv install requests> 2.19, for example, would result in pipenv install requests and outputting stdout to a file named 2.19, since > is the special character for output redirection. It is best practice to always put quotes around the requirement, like this:
$ pipenv install "requests>=1.4"
$ pipenv install "requests!=2.*"  # Not strictly required, but best practice to ALWAYS quote.

It would be nice if there is a little text explaining why quotes are recommended (since PEP 440 does not cover it).

👌🏼 thanks for the feedback @uranusjr, based on this I will apply the following changes:

Remove the use of '=='
Add " " around the specifiers (along with a note saying why this is advised)
Reword the last text (ref to pep 440) so that people actually check this for more advanced/specific cases

I have made the changes now and this should be less verbose while still being able to provide a good idea of how this work, let me know what you think

Waiting for CI to pass before I hit merge…


GPU Scheduling Code Walkthrough in the Hami Project

Recently, while using the Hami project, I ran into quite a few issues with GPU scheduling. As I dug into the source code to figure things out, I realized the scheduling logic was pretty interesting. So, I decided to write down my findings—hopefully, this will help others who are exploring or working with Hami!
https://github.com/elrondwong/elrond.wang/blob/master/_posts/2024-12-24-HAMI项目GPU POD调度流程源码走读.md

wow，that's amazing, would you mind me to upload your essay to HAMi website?

Sure, it would be my pleasure! 😊


Use robot icon for github copilot labs

This is the same problem as https://github.com/misolori/vscode-fluent-icons/issues/21#issuecomment-984999896 and as long as they are using an SVG image I can't overwrite their icon


Clone entity

It would be super useful to be able to clone a entity.

Should we clone the entity in the same level of the previous entity?
<a-scene>
  <a-house>
    <a-door/>
  </a-house>
</a-scene>

If I clone <a-door> should the new created entity be placed next to the cloned item inside the a-house or just added at the end of a-scene ?

I would expect it to show up adjacent to the cloned entity.
So it would look like:
<a-scene>
  <a-house>
    <a-door/>
    <a-door/><!-- copy of a-door -->
  </a-house>
</a-scene>

This is also consistent with other layer based aops i've used.


fix: clean pending usage when dry run validate_create_data

What this PR does / why we need it:
fix: clean pending usage when dry run validate_create_data

Does this PR need to be backport to the previous release branch?:

release/3.10
release/3.9
release/3.8

/cc @zexi @ioito @wanyaoqi

/lgtm


Related to V-for WMS layer and ref for layer

I have a problem when I created a series of WMS. But when I use this.ref.mapObject It's undefined.
This's my WMS infos

This's my Vue2leaflet v-for

And This is the error.

Can anybody help me ? Thank you
PS: When I create it individual, Its oke

@hulauwa how are you accessing mapObject of the elements created in the v-for?

Closing due to inactivity, feel free to re-open


[Package] - Link to dndR website

I created a standalone website for the dndR package.
I need to embed it into the short blurb about dndR that exists in my personal website

Done!
See this commit: https://github.com/njlyon0/njlyon0.github.io/commit/a7aa7e86d774a34d13325cc893ff13249dcbdff8


blueprint in a blueprint

it woul be great if it would be possible to register a blueprint inside of an other blueprint
to increase modularity

Modularity can be achieved by proper project structure rather than functionality.
You can place the 'register` statement in the blueprint module. Something like:
blueprints/__ini__.py
from .auth import auth_bp
from .api import api_bp

def init_app(app):
    app.register_blueprint(auth_bp, prefix="/auth")
    app.register_blueprint(api_bp, prefix="api")

app.py
def create_app():
    from . import blueprints
    blueprints.init_app(app)


NextDevice Fix

This patch fixes an issue where the NextDevice function of the Executor
was not being invoked prior to calling VolumeAttach. No value was being
provided in the VolumeAttachOpts.NextDevice field. Now the executor
should properly gather that information and provide it to the server in
the event of an attach call.

Current coverage is 26.03% (diff: 0.00%)

Merging #268 into master will decrease coverage by 0.04%

@@             master       #268   diff @@
==========================================
  Files            39         39
  Lines          2420       2420
  Methods           0          0
  Messages          0          0
  Branches          0          0
==========================================
- Hits            631        630     -1
- Misses         1721       1722     +1
  Partials         68         68

Powered by Codecov. Last update f072fd1...f4960be


I want to use IRNet to convert Chinese into SQL, what should I use to substitute for english_RelatedTo.pkl and english_IsA.pkl?

I want to use IRNet to convert Chinese into SQL, what should I use to substitute for english_RelatedTo.pkl and english_IsA.pkl?

Did you find the IsA file and the RelatedTo file in Chinese?


Error while running wasm intergration tests on Node 18

TypeError: The "source" argument must be an instance of Response or an Promise resolving to Response. Received an instance of Response
Happens on Node 18.

Might have sth. to do with the fact, that fetch is included in the Node 18 - and is not compatible with the fetch from redstone-isomorphic.
As a first step - update undici-fetch in the redstone-isomorphic and then update redstone-isomorphic in the SDK.
Remember to verify in Node 18!

seems to be a Jest problem, I upgraded it (withing redstone-isomorphic and typescript) and it works fine.


Fix 'base 17' typo, correct id bucketing

MD5.hexdigest provides a flat (but noisy) distribution of hex digits, but the typo converting them back to integers with base 17 adds a very slight bias to the results, increasing the size of some low-order buckets. eg this calculation using a range instead of MD5 to provide the evenly distributed input: (0..9999999).each_with_object(Hash.new(0)) {|d, h| h[d.to_s(16).to_i(17) % 100 < 5] += 1 } => {true=>500025, false=>9499975} . It's only a slight loading of the dice, and would be very hard to spot in real experiments because it's lost in the noise of the MD5 distribution. Spotted via code review not tests.

Thanks!


socket hangup error (ECONNRESET)

Hi,
Wonder if you could shed some light on the issue I'm running into where I get the socket hangup error:
Made the following changes to the library code to allow for null domain:

Commented out the following code in proxying-agent.js starting on line 26.
/*  if (!this.options.ntlm || !this.options.ntlm.domain) {    throw new Error('NTLM domain must be provided');  }*/

Modified code in ntlm.js as below:
function createType1Message(options){ var domain = ''; if(options.domain && options.domain.length > 0) {  domain = escape(options.domain.toUpperCase()); }
function createType3Message(msg2, options) { <br/> ...  if(options.domain && options.domain.length > 0) {  domainName = escape(options.domain.toUpperCase()); }
HTTP_PROXY environment set as such:
http://username:password@10.x.x.x:8080/

Below is the options object passed to the globalize function:
`
var proxyOptions = {
proxy: process.env.HTTP_PROXY,
authType: 'ntlm',
ntlm: {
domain: null //Made changes to library code to ignore domain
}
};
require('proxying-agent').globalize(proxyOptions);
let req = https.get({host: options.host, port: options.port, timeout: 60000}, callback);
`
where options.host: gmail.com and port: 443. I've tried some other hosts as well but they all fail.
    req.on('socket', function(socket) {
        this.logger.info(`Got socket response`);
        req.write('DATA');
        req.end();
    });

    req.on('response', (response) =>  {
        this.logger.info(`Got response, ${response.toString()}`);
        if (response.statusCode !== 200) {
            let err = new Error('Unable to get successful response: ' + [response.statusCode]);
            return callback(err);
        }
    });

    req.on('finish', () => {
        this.logger.info(`finish`);
        callback();
    });

    req.on('error', (err) => {
        this.logger.info(`request error ${err}`);
        callback(err);
    });

`
Added some log statements to the proxying-agent.js (startProxying method) to dump the values being passed:
tunnelOptions :

{"path":"gmail.com:443","tunnel":true,"ntlm":{"domain":null,"workstation":"myDesktop","username":"username","password":"password"},"authType":"ntlm","proxy":{"protocol":"http:","slashes":true,"auth":"username:password","host":"10.x.x.x:8080","port":"8080","hostname":"10.x.x.x","hash":null,"search":null,"query":null,"pathname":"/","path":"/","href":"http://username:password@10.x.x.x:8080/"},"ssl":false,"host":"10.x.x.x","port":"8080","method":"CONNECT","hostname":"10.x.x.x","headers":{}}

tunnelOptions headers:

{"Proxy-Authorization":"NTLM base64 encoded string","Proxy-Connection":"Keep-Alive"}

And this is the exception I get:
The 'error' handler in the startProxying method gets invoked first followed by the 'close' handler. I do not see the 'connect' handler getting invoked at all.

Tunnel creation failed. Socket error: code- ECONNRESET, Error: socket hang up
at createHangUpError (_http_client.js:330:15)
at Socket.socketCloseListener (_http_client.js:362:23)
at Socket.emit (events.js:164:20)
at TCP._handle.close [as _onclose] (net.js:568:12), JSON: {"code":"ECONNRESET"}

I've also gotten a wireshark trace and as far as I can tell the connection is established with the proxy but soon thereafter the connection gets reset. All I see is the [RST] ACK from my client machine.
Would really appreciate any help you can offer, I've been trying to debug this issue for a couple of days now and running out of things to try.
Also if possible could you please share a simple working example of the code containing the GET and POST calls.

Note that in the above scenario the proxy is HTTP & the server is HTTPS

Unfortunately I no longer have access to an environment with an NTLM proxy so there is little I can do to check issues.
If you like, I can try to find some time to debug with you in a shared session. Would that work?

@fujifish, what would I need to have a shared session ?. If there is any logs I can collect please let me know. I've tried to capture a Wireshark before and can do it again first thing tomorrow morning.


Getting errors on multi site setup

When trying to add the 'Documentation' widget to the dashboard after installing the plugin, it throws an error if there is more that one site set up in Settings > Sites.

Work around for this is to save the settings, and it'll add the site.
Will look into checking on install


optimize test_vm.py for random test simulations

implemented alternative, which checks if arg[1] is a file.


Add copyright info

I want to use your code and attribute copyright to you properly :)

These are really great improvements - thanks!


Add latest CVES count to each version as gobrew ls --cves && gobrew ls-remote --cves

Hi!
What do you mean? What is it CVES?

Sorry
https://www.cvedetails.com/vulnerability-list/vendor_id-14185/product_id-29205/Golang-GO.html

When a new version of golang is released, I only use Gobrew to install it and switch to it. What can information about existing vulnerabilities in the version be used for?

Mostly the use case I imagined was to have it on the CI, similar to dependabot.
As many of projects don’t update their versions on CI and go.mod upon EOL. I wanted those CI to fail when a limit of cve score has crossed.
It was just an idea at the moment.


QCxMS prediction tutorial

A new tutorial leveraging QCxMS tools suite.
First draft by @hechth

I made use of "Choose your own adventure" feature to introduce two tracks of analysis - first starting from single SMILES input (fewer pre-processing steps, better for teaching purposes), and second starting from SMILES of several molecules (works better as a workflow though, might need an update when openbabel convert tool is also updated).

@foellmelanie thank you very much for the review - I'll push some updates and fixes today to respond to the comments :)

See https://github.com/wee-snufkin/training-material/pull/15 for upcoming changes @foellmelanie , @melpetera and @wee-snufkin

@foellmelanie could you re-review this please? :)


Set length of versionEndExcluding, versionEndIncluding, versionStartExcluding and versionStartIncluding to 60

Fixes Issue
See issue https://github.com/jeremylong/DependencyCheck/issues/3483
closes #3483
Description of Change
Set length of columns versionEndExcluding, versionEndIncluding, versionStartExcluding and versionStartIncluding to 60
Set schema version to 5.2
Have test cases been added to cover the new functionality?
no

Should I also revert the other file change then? I previously also changed core/src/main/resources/data/initialize.sql to a lenght of 60:
CREATE TABLE software (cveid INT, cpeEntryId INT, versionEndExcluding VARCHAR(60), versionEndIncluding VARCHAR(60),
versionStartExcluding VARCHAR(60), versionStartIncluding VARCHAR(60), vulnerable BOOLEAN

But if the table gets upgraded by the sql instructions in upgrade_5.1.sql later on, shouldn't this be 50?


Wrong datatype error

⚠ Please verify that this bug has NOT been raised before.

[X] I checked and didn't find similar issue

🛡 Security Policy

[X] I agree to have read this project Security Policy

Description
There is an error causing a problem when saving certain values. Even if the datatype of the input is correct, there is an error saying "Wrong Datatype?" The error appears most consistently when adding a Steam API key via the settings but I have also seen it with other values. I am using the No Auth mode if that matters,
Steam key has the form A89A....... and is copied and pasted from steam directly, so it is 100% correct.
👟 Reproduction steps
Go to Settings and add a Steam API key
After inserting the Steam API key press save buttton
👀 Expected behavior
Steam API Key should be saved
😓 Actual Behavior
Error popup saying "Wrong data type?"
🐻 Uptime-Kuma Version
1.15.0
💻 Operating System and Arch
Windows 10 21H2 newest Updates as of posting date
🌐 Browser
Google Chrome 101.0.4951.41 64 bit
🐋 Docker Version
Docker Standalone 20.10.14
🟩 NodeJS Version
No response
📝 Relevant log output
No response

Saw this too, I think there is a bug with the authentication code but I'm not sure exactlly what's going on. Please try to logout and login again and the problem should go away.

Saw this too, I think there is a bug with the authentication code when using No Auth mode, but I'm not sure exactly what's going on. Please try to enable auth and login again and the problem should go away.

Yep you are right, working fine with auth

The problem is that doubleCheckPassword(socket, currentPassword) is called when auth is disabled which should not be the case. There is only one occurrence where there is a check before it if authentication is disabled, maybe the check could be added to other occurrences as well.


Update README.md

add Pettersson-Edström's Ethereum thesis

Is there a page with an abstract rather than linking straight to the pdf?
Also, I have realised my scheme to have
authors
paper
venue
on separate lines did not work. I'll add the appropriate 2 spaces at the end of
lines in the existing README, can you do the same?

If there is, I couldn't find it, all the links lead directly to pdf.


calculation of mean counts is wrong

In step1/plot.py line 195 (extract data)

This has been solved.


Does not work on fedora 21.

Fedora 21 provides doxygen-<IP_ADDRESS>-2.fc21.x86_64 and bash-argsparse package actually have no documentation in it.
It means either the filter does not work with new doxygen, or that doxygen configuration needs to be additionnally tweaked to make it work. So I need to fix either the code or a documentation.

Fedora 20 provides doxygen-1.8.6-1.fc20.x86_64 and the filter was working back then.

Doxyfile needs : EXTENSION_MAPPING      = sh=C


fixed handling not a number values

Coverage increased (+0.002%) to 98.592% when pulling 39a735cef270a1cb9a7eea597ab7a19f41cd2f7d on bugfix/mean_add_nan into 5c88cd849a87b4aa15af373041d9cfded281fe57 on 1.0-dev.


Failed to submit hudi task

Search before asking

[X] I had searched in the issues and found no similar issues.

What happened
insert into  t1 select * from kafka_ods_orders
我执行了这一条语句，将kafka的数据插入到一个hudi表中
但是hudi表并没有数据
然后我去flinkweb中看了相关记录 也没有出现什么报错 不知道什么原因
What you expected to happen
我想知道如何解决
我之前在本地的flink-sql-client写了同样的建表语句，是可以成功的
How to reproduce
就是创建一个kafka表，然后执行我上面所述的sql，flink是stanalone模式的
Anything else
No response
Version
0.7.3
Are you willing to submit PR?

[X] Yes I am willing to submit a PR!

Code of Conduct

[X] I agree to follow this project's Code of Conduct

Add checkpoint to your task.


Handle 'post' dependencies

Post dependencies must be installed after other dependencies and are often used to break dependency cycles.
This patch only detects 'post' dependencies that are directly required by the root packages.
Installing the released version of current package is now allowed.
Because of this, the pinning of root packages must be done after installing dependencies.
We must now handle pin-depends from root packages explicitly (it was done implicitly by opam).
This is very adhoc but it seems to be working as expected.

As context, this is needed by odoc.

Odoc depends on Mdx (with-test) which depends on Odoc. With the post flag, opam install -t . works as expected but --deps-only would not install Mdx.
With this changes, the released version of Odoc then Mdx will be installed. This is not equivalent to opam install -t . but is more cache-friendly and avoid unrelated errors in building Mdx with the dev version of Odoc.
This is how I setup my local environment for Odoc: opam install --deps-only -t ., Mdx is not installed, opam install mdx, the released version of Odoc and Mdx are installed.

Thanks for the example. I see there was some discussion on the #opam slack channel too on the 11th Sep. That seemed to conclude with:

if pinning works this looks like a better solution, compared to adding a post dependency in opam-repository

Does that affect this PR?
In general, it seems concerning that the CI can now install a different version of the package being tested. e.g. a passing test for odoc only says that the previous version of odoc works with mdx, not the one under test.
But if this is still needed, perhaps the refactoring parts could be moved to a separate PR so they can be reviewed and merged first? e.g. it looks like this PR switches to using JSON for communicating solver-worker results. And there's a new No_solution in the solver API. Is that related to the post-dependencies problem?

if pinning works this looks like a better solution, compared to adding a post dependency in opam-repository

Does that affect this PR?

Possibly. There is an other solution that I'm investigating: Install the released version of the current package, if required.
This might not work as easily on Irmin, which has post dependencies on root packages, which this PR handles.
This PR is doing that too but only for dependencies marked post to avoid changing the way the CI works for other packages.
In Odoc's case, the post flag is working as expected in the case of opam install -t, but the CI is doing the equivalent of --deps-only -t, which in Opam, doesn't work with the post flag (deps marked post are not installed, meaning the tests cannot run).
The behavior added in this PR doesn't exist in Opam and is only what I expect, in the case of Odoc.
I really don't want to build Mdx with the version of Odoc that is currently being tested. This would break caching but more importantly, would make the CI unusable in case of breaking changes.
I had to use a richer type to pass the additional field. The No_solution case is because calling code cannot just test if the list is empty because there is now 2 lists. I'll split PRs if this solution is still useful.

Summary of slack discussion:

The CI wants to install (and cache) all dependencies before building and testing.
It can't do that if it has to download the mdx dependency after building odoc.
It might be possible to build the new version of odoc using an mdx built with the previous version in some cases, but not if they have incompatible dependencies. Also, it would be useful to know that odoc changes don't break mdx (otherwise it will only work in CI, but not once released).
odoc wants to use mdx because the OCaml top-level printer is useful in its unit tests.
A simple short-term fix is to use git-submodule to add mdx to the odoc repository. Then the CI will treat odoc and mdx as a single project and there won't be a problem. This is similar to the case for Irmin (a cyclic dependency within the repository, where one edge is a test edge), and that works OK.
A longer-term solution is to move the odoc parser (which is the bit mdx needs) to a separate repository. In fact, it was imported originally from octavius, so it could just go back there.

Thanks for the help !


Update Lab_3_1_Createformsandpages.md

Module: 00
Lab/Demo: 00
Fixes # .
Changes proposed in this pull request:

Please merge changes.


Error at path

hi there seems to be an error in your sidebar.js and a few more.
i tried it with running your project directly from your sources.
the error i get is the follwing
uncaught at reactOnSourceSet TypeError: Cannot read property 'path' of undefined
On example is at the follwing
  <React.Fragment>

{file.path}

    <Copy copyText={file.path} />

</React.Fragment>

in sidebar js
https://github.com/Bogdan-Lyashenko/codecrumbs/blob/master/src/public/js/components/sideBar/component/SideBar.js

Hi, can you please show how you run codedrumbs, especially -e param for entry file. I assume it can’t resolve it (and, yeah, I need to add better error handling). Thanks.

sure i have to add that i ran it using npm
"start:cc": "codecrumbs -e src/scripts/index.js -d src"
is my starting command

Alright, you use windows os, right? Looks like there is an issue with paths handling. This is top prio, I will have a look ASAP. Will ping you when it’s fixed. Thanks again)
P.S. yeah.. I did all development on Mac, haven’t tested it on windows yet ;)

Sure glad to find these bugs.
it basically Looks like a very promising project so I'm Glad to help :)

@Motytheultimate I fixed all (I hope 😸) bugs related to windows specifics, try version "1.0.22" (make sure to clear cache). Let me know if you still have issues. Thanks again, this was a really important issue to get aware of before 'going live". 👍

:) i'll try it later today

Looks like the path issue is fixed.
but now it throws an error at the dependecies option:
uncaught at reactByUpdatingFoldersState TypeError: Cannot read property 'dependencies' of undefined
at utils.js and on Tree.js
i think i should create a new issue?