v1.3: Code sample changes

To be transferred to the integration-guides repo on 2023-07-24

Add new code sample facet_search_1 https://github.com/meilisearch/documentation/pull/2472

  -X POST 'http://localhost:7700/indexes/books/facet-search' \
  -H 'Content-Type: application/json' \
  --data-binary '{
    "facetQuery": "fiction",
    "facetName": "genres",
    "filter": "rating > 3"
  }'

Add new code sample facet_search_2 https://github.com/meilisearch/documentation/pull/2472

  -X PATCH 'http://localhost:7700/indexes/books/settings/faceting' \
  -H 'Content-Type: application/json' \
  --data-binary '{
    "sortFacetValuesBy": {
      "genres": "count"
  }
}'

Add new code sample facet_search_3 https://github.com/meilisearch/documentation/pull/2472

  -X POST 'http://localhost:7700/indexes/books/facet-search' \
  -H 'Content-Type: application/json' \
  --data-binary '{
    "facetQuery": "c",
    "facetName": "genres"
}'

Add new code sample search_parameter_guide_show_ranking_score_1 https://github.com/meilisearch/documentation/pull/2476

    -X POST 'http://localhost:7700/indexes/movies/search' \
    -H 'Content-Type: application/json' \
    --data-binary '{
      "q": "dragon",
      "showRankingScore": true
    }'

Add new code sample search_parameter_guide_attributes_to_search_on_1 https://github.com/meilisearch/documentation/pull/2480

    -X POST 'http://localhost:7700/indexes/movies/search' \
    -H 'Content-Type: application/json' \
    --data-binary '{
      "q": "adventure",
      "attributesToSearchOn": ["overview"]
    }'

Update getting_started_faceting https://github.com/meilisearch/documentation/pull/2472

  -X PATCH 'http://localhost:7700/indexes/movies/settings/faceting' \
  -H 'Content-Type: application/json' \
  --data-binary '{
    "maxValuesPerFacet": 2,
     "sortFacetValuesBy": {
       "*": "count"
     }
  }'

Update update_faceting_settings_1 https://github.com/meilisearch/documentation/pull/2472

  -X PATCH 'http://localhost:7700/indexes/books/settings/faceting' \
  -H 'Content-Type: application/json' \
  --data-binary '{
    "maxValuesPerFacet": 2,
    "sortFacetValuesBy": {
      "*": "alpha",
      "genres": "count"
    }
  }'

~8. Add new code sample get_experimental_features_1 https://github.com/meilisearch/documentation/pull/2496~
   -X GET 'http://localhost:7700/experimental-features/'

~9. Add new code sample update_experimental_features_1 https://github.com/meilisearch/documentation/pull/2496~
  -X PATCH 'http://localhost:7700/experimental-features/' \
  -H 'Content-Type: application/json'  \
  --data-binary '{
    "scoreDetails": true
  }'

@maryamsulemani97 we will not have experimental features handling on the SDK, ok? So, no code-samples about them.

Implemented in the tier 1 SDKs. Closing this issue. The remaining SDKs will receive new issues to track this change internally.


Updating readme

So errors needed to be solved. Mainly g++ crashing when building NS-3. This problem was occurring due to g++ not having enough RAM to operate in the VM. Once the RAM was increased to 8.0GB, g++ compiled NS-3 successfully. Added the hardware requirement to the README.md.
Some changes to the formatting of the README.md were also made.

@ardakanian Review of the description of the project needed.


Build UI Error

Hi @thatmattlove , I encountered some issues. When running for the first time with docker compose up, everything was normal. However, when I stopped it and started again with systemctl start hyperglass, I ran into this problem. The output from systemctl status hyperglass showed that it was running normally, but in reality, it was unusable. Later, after stopping the service, I tried running it again with docker compose up and encountered the following error. I believe that when a file already exists, it should be overwritten or skipped instead of throwing an exception.
root@rttw /www/wwwroot/hyperglass # docker compose up
[+] Running 1/1
 ✔ Network hyperglass_default         Created                                                                                0.1s
 ⠋ Container hyperglass-redis-1       Created                                                                                0.1s
 ⠋ Container hyperglass-hyperglass-1  Created                                                                                0.1s
Attaching to hyperglass-1, redis-1
redis-1       | 1:C 21 Apr 2024 00:55:28.963 * oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
redis-1       | 1:C 21 Apr 2024 00:55:28.963 * Redis version=7.2.4, bits=64, commit=00000000, modified=0, pid=1, just started
redis-1       | 1:C 21 Apr 2024 00:55:28.963 # Warning: no config file specified, using the default config. In order to specify a config file use redis-server /path/to/redis.conf
redis-1       | 1:M 21 Apr 2024 00:55:28.963 * monotonic clock: POSIX clock_gettime
redis-1       | 1:M 21 Apr 2024 00:55:28.964 * Running mode=standalone, port=6379.
redis-1       | 1:M 21 Apr 2024 00:55:28.964 * Server initialized
redis-1       | 1:M 21 Apr 2024 00:55:28.964 * Ready to accept connections tcp
hyperglass-1  | [INFO] 20240421 00:55:30 | Starting hyperglass {'version': '2.0.0-dev', 'listening': 'http://<IP_ADDRESS>:8001', 'workers': 16}
hyperglass-1  | [INFO] 20240421 00:55:31 | Starting UI build {}
hyperglass-1  | [CRITICAL] 20240421 00:56:26 | [Errno 17] File exists: '/etc/hyperglass/static/ui' {}
hyperglass-1  | ╭───────────────────── Traceback (most recent call last) ──────────────────────╮
hyperglass-1  | │ /opt/hyperglass/hyperglass/cli/main.py:61 in _start                          │
hyperglass-1  | │                                                                              │
hyperglass-1  | │    58 │   │   │   if build_complete:                                         │
hyperglass-1  | │    59 │   │   │   │   run(workers)                                           │
hyperglass-1  | │    60 │   │   else:                                                          │
hyperglass-1  | │ ❱  61 │   │   │   run(workers)                                               │
hyperglass-1  | │    62 │                                                                      │
hyperglass-1  | │    63 │   except (KeyboardInterrupt, SystemExit) as err:                     │
hyperglass-1  | │    64 │   │   error_message = str(err)                                       │
hyperglass-1  | │                                                                              │
hyperglass-1  | │ ╭───────────────────── locals ─────────────────────╮                         │
hyperglass-1  | │ │    build = False                                 │                         │
hyperglass-1  | │ │ build_ui = <function build_ui at 0x7f75196f9bc0> │                         │
hyperglass-1  | │ │   kwargs = {'workers': None}                     │                         │
hyperglass-1  | │ │      run = <function run at 0x7f75196f9b20>      │                         │
hyperglass-1  | │ │  workers = None                                  │                         │
hyperglass-1  | │ ╰──────────────────────────────────────────────────╯                         │
hyperglass-1  | │                                                                              │
hyperglass-1  | │ /opt/hyperglass/hyperglass/main.py:180 in run                                │
hyperglass-1  | │                                                                              │
................
╰──────────────────────────────────────────────────────────────────────────────╯
hyperglass-1  | FileExistsError: [Errno 17] File exists: '/etc/hyperglass/static/ui'
hyperglass-1 exited with code 1

Can be fixed by deleting the build dir before copying to it. I will open a PR @thatmattlove
diff --git a/hyperglass/frontend/__init__.py b/hyperglass/frontend/__init__.py
index 2fe338e..cd0ce5b 100644
--- a/hyperglass/frontend/__init__.py
+++ b/hyperglass/frontend/__init__.py
@@ -131,6 +131,7 @@ async def build_ui(app_path: Path):
         log.error(err)
         raise RuntimeError(str(err)) from err

+    shutil.rmtree(build_dir)
     shutil.copytree(out_dir, build_dir)
     log.bind(src=out_dir, dst=build_dir).debug("Migrated Next.JS build output")

Hey @maluueu - Apologies for not merging #246 directly; I was working on a number of other changes and forgot to merge your change beforehand. I did modify your change slightly by using the dirs_exist_ok=True argument to shutil.copytree, but the result is the same. This should be fixed now.

Hey @maluueu - Apologies for not merging #246 directly; I was working on a number of other changes and forgot to merge your change beforehand. I did modify your change slightly by using the dirs_exist_ok=True argument to shutil.copytree, but the result is the same. This should be fixed now.

Hey @thatmattlove, no worries. Regarding the issue, are you sure that dirs_exist_ok=True fixes it completely?
Consider the following scenario:

File A exists in source code
project gets build
File A is being removed in source
project gets build for the new version
Wouldn't this cause the File A to still exist in the output dir, rather than being removed fully?

Ya know, you're right. If you don't mind, open another PR against the current commit and I'll merge it. Thank you!

Ya know, you're right. If you don't mind, open another PR against the current commit and I'll merge it. Thank you!

sure, will do!

@thatmattlove
done (#247), also set exist_dir to False as that should never happen


[Bug Report] Recursive scheduling of asynchronous tasks in case of missing messages;

Describe the bug
If no messages are available on the broadcast, the plugin cyclically schedules to process a message queue with no messages in it, which causes constant scheduling.
To Reproduce

Set -Xms=-Xmx=1G
Remove all messages from demo.conf (messages=[])
Wait a while (1 day?)
See the memory leak

Expected behavior
Ignoring scheduling of tasks without messages, or optimizing scheduling
Screenshots

Server Software and Version:

Vendor: Any
Minecraft Version: 1.20.4
Output of /version command: git-Purpur-2176 (MC: 1.20.4)*

Suggestions for solutions
Remove recursive scheduling
diff --git a/src/main/kotlin/xyz/jpenilla/announcerplus/config/message/MessageConfig.kt b/src/main/kotlin/xyz/jpenilla/announcerplus/config/message/MessageConfig.kt
index 699be5b..d4a8fe9 100644
--- a/src/main/kotlin/xyz/jpenilla/announcerplus/config/message/MessageConfig.kt
+++ b/src/main/kotlin/xyz/jpenilla/announcerplus/config/message/MessageConfig.kt
@@ -204,15 +204,13 @@ class MessageConfig : SelfSavable<CommentedConfigurationNode>, KoinComponent {
   @Transient
   private val broadcastQueue = ArrayDeque<Message>()

-  fun broadcast(skipInitialDelay: Boolean = false) {
-    stop()
-    broadcastQueue.clear()
-    broadcastQueue.addAll(shuffledMessages())
-    broadcastTask = announcerPlus.asyncTimer(if (skipInitialDelay) 0L else initialDelay.ticks, interval.ticks) {
+  fun broadcast() {
+    broadcastTask = announcerPlus.asyncTimer(initialDelay.ticks, interval.ticks) {
       if (broadcastQueue.isNotEmpty()) {
         broadcast(broadcastQueue.removeFirst())
       } else {
-        broadcast(true)
+        // Removed recursion to prevent out of memory errors with empty messages
+        broadcastQueue.addAll(shuffledMessages())
       }
     }
   }

Old tasks were already being cancelled, I've removed the redundant scheduling when there is no messages however the real impact is probably next to zero.

If the file is not too large I guess I can take a look, but I do not see any way for a meaningful memory leak (or any memory leak at all) to happen here, the tasks are not capturing the previous task or anything like that.

@jpenilla, here are some screenshots from Eclipse MAT and the dump itself

hprof: https://drive.google.com/file/d/1RMt15DhFI2G-1e9aZ5QXhq1kCJlNHQT8/view

Looks like some sort of bug with the async scheduler or another plugin
f201bb1ef190f0c61385dcaca560f4aa71bb53a1 this will avoid the issue

another plugin
It's also a possibility, I'll continue to look into issue when similar problems arise.

Thanks a lot for the very fast support, you are the best!


(attempt) dbfread takeover

It's done when we are the official maintainers of dbfread, or have a written, unresolvable* rejection from pypi.

unresolvable meaning there is not some reasonable next step to change the outcome.


Add the ability to turn on/off stripTrailingZeros() from eval()

The return of the eval method calls stripTrailingZeros() on the final result of the evaluation (if the result is not null). There are scenarios where one might not want to modify the result returned from EvalEx in order to get those trailing zeros added back in.
Would it be possible to add the ability to "turn on/off" the stripTrailingZeros() in the return so one could control whether the result of eval either has the trailing zeros removed or not?

Yes, should be no problem. I put this on the enhancement list.

I have added it in Release 1.13. See commit 1d2ec46c022ab7da01bb7864000b4c5893dfbb60
The eval() function now has an optional parameter stripTrailingZeros. Default is true.
To strip the zeroes call expression.eval(false).

Thanks!

Thank you for adding this in so quickly!
One minor thing I noticed, shouldn't the return comment of the eval() method say that the trailing zeros are stripped instead of are not stripped?


how many PRs? one per run? just one?

It would be nice if this would group stdlib updates and create a single PR for each batch, in case there are dependencies between the updates (e.g. https://github.com/JuliaLang/julia/pull/38808).
But here's another thought: what if this always pushed to the same branch? Hear me out. If you push to a branch that already has an open PR, then it just updates that PR. Which is fine since if someone updates a bump PR when an older one is already open, we want to close the old one anyway; why not just update it instead? What happens if you push to a PR branch after that PR has been merged? Works just fine and you can create a new PR from the same branch. This would enforce that there is at most one stdlib bump PR at a time.
One tweak that would be needed with that approach is that you'd want stdlib bumps to be done relative to what's already in that branch: i.e. if an old bump updates a stdlib and you trigger a new bump that doesn't include that stdlib, you don't want to accidentally roll it back to what's on master since someone else asked for it to be bumped already. Perhaps the logic could be this: if there's no open bump PR (i.e. the branch doesn't exist or the PR's been closed), then a new bump starts from the master state of stdlibs; if there's an open bump PR, then a new bump starts from there, re-bumping what's requested.

This would enforce that there is at most one stdlib bump PR at a time.

I think this is the right approach.

A simpler alternative would be that it just bumps all stdlibs to the latest every time.

A simpler alternative would be that it just bumps all stdlibs to the latest every time. Then you don't have to worry about the current state of the branch: you always just generate a commit relative to master that bumps everything and force push it.

Yeah this would certainly be the easiest approach.
I guess the question is: is there ever a case in which you explicitly don't want to update a stdlib?

This is kind of a policy decision. While I can imagine a contrived situation where we don't want that, there's a case to be made that if you didn't want it on Julia master, you shouldn't have merged it to master in the stdlib. I would be inclined to go all or nothing with this and see how that goes. My workflow has generally been to bump stdlibs to Julia master first and only after they've proven to be unproblematic there for a while, tag a release of the stdlib.

I guess with ArgTools, we are currently in that situation. I.e. we don't want ArgTools master to be on Julia master.


Separate integration tests from unit tests

What was the problem/requirement? (What/Why)
Currently, the build pipeline isn't set up to be properly licensed to successfully run the Houdini tests. In the meantime, we'd like some way of running the unit test suite from the command line without these.
What was the solution? (How)
The naming structure of the tests have changed to more explicitly move all tests under "Ambit.Unit" while the Houdini tests live under "Ambit.Integration". The "AmbitUtils" tests have moved to "Ambit.Unit.Utils".
When running the tests from the command line, Unreal only does forward string matching - passing in "Ambit" would run all of the tests (both organized under Unit and Integration), while "Ambit.Unit" would run all of the unit tests without running Ambit.Integration.
I didn't want to explicitly list all the tests that should be run, as developers adding new unit tests would have to remember to add them to the pipeline. There is no concept of a negative filter - I can't tell it 'run all tests that match this string, but not these specific tests."
Similarly, the only filter that can be used from the command line is represented by the flags that fall under the FilterMask -- Smoke, Engine, Product, Perf, Stress, and Negative. All Ambit tests are marked as Product tests by default, which is IMO the right place for them - there's no separate category that really suits the integration tests.
What artifacts are related to this change?
Issues: Ambit-10
What is the impact of this change?
Developers running tests will notice that they are organized under a new structure, and will have to expand one more node to view class-specific tests. Otherwise it is just as simple to run all of the Ambit tests.
Are you adding any new dependencies to the system?
None
How were these changes tested?

Visually checked organization of tests in the Editor
Ran just the unit tests from the command line, looked at output to ensure Houdini tests did not run: .\RunUAT.bat BuildCookRun -project="D:\UnrealProjects\ambitdemo\ambit-demo\AmbitDemo.uproject" -unattended -clean -build -package -nullrhi -nosound -run -editortest "-RunAutomationTest=Ambit.Unit"

How does this commit make you feel? (Optional, but encouraged)
Fairly ambivalent

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Is there not a way to specify multiple tests at a time? For example, "Ambit.Unit" and "AmbitUtils.Unit" simultaneously. Otherwise, we may want to formalize how we define tests: "Ambit.{TestType}.{DirectoryName}.{TestSuite}.{MinorTestSuite}" might be better, as our current schema defined here confuses AmbitUtils a bit. This would make the AmbitUtils "Ambit.Unit.AmbitUtils.MathHelpers" and other tests (AmbitWorldHelpers for example) "Ambit.Unit.Ambit.AmbitWorldHelpers" This is a minor concern, ultimately, but worth double-checking before we commit.

@brhook-aws The way I understood this was that running with Ambit.Unit will trigger all Ambit.Unit and Ambit.Unit.Utils tests, since AmbitUtils tests have moved to Ambit.Unit.Utils
@JuliaABurch can correct me if I'm wrong

Unfortunately, Unreal doesn't let you pass in multiple "test paths" from the command line - if you pass it a list, it will only run the first one from the list.
I agree that we should be consistent with test organization and naming, and it's definitely worth discussing! For reference, the change I'm proposing is essentially "Ambit.{TestType}.{TestSuite}" - it's also worth noting that changing test organization/names is fairly easy to do, as this change shows - it's merely changing a string in the test file and only requires a rebuild to reflect changes.
I'm not sure we want to include {DirectoryName} as imo it doesn't make the test more readable (what does knowing the directory name tell me about the test?), and it's something that will be easily missed with refactoring if/when files get moved into different directories.
Similarly, I don't know that repeating "Ambit" (in "Ambit.Unit.Ambit.{TestSuite}" or "Ambit.Unit.AmbitUtils") improves readability. I see that this preserves the original structure - originally, Ambit tests were distinct from AmbitUtils tests - but as they're all packaged in the same "Ambit" plugin, and I don't see customers using "AmbitUtils" separate from the Ambit plugin, I actually didn't see the benefit of completely separating them to begin with.


Initial Release for vSphere Container Storage Interface (CSI) Chart

What this PR does / why we need it:
This introduces the initial release for the vSphere Container Storage Interface (CSI) Chart located at https://github.com/kubernetes/cloud-provider-vsphere. There is a move to take all the external storage providers from in-tree to out-of-tree (link: https://github.com/kubernetes/community/blob/master/contributors/design-proposals/storage/container-storage-interface.md). This Helm Chart will enable users to consume the out-of-tree vSphere CSI driver/implementation easier by providing a simple deployment mechanism via Helm.
Special notes for your reviewer:
Tested using:

vSphere CSI image 0.1.1
Kubernetes cluster 1.11.3, 1.12.2, and 1.13.1 configured for an external CSI implementation
vSphere 6.7

Checklist

[x] DCO signed
[x] ~Chart Version bumped~ Initial release
[x] Variables are documented in the README.md

Yep, going to need to talk with someone in Slack regarding this chart. I am guessing the e2e is failing because the chart requires certain feature gates to be enabled and also installs some CRDs.

/remove lifecycle/stale


Extracting flatten/unflatten into lightweight package?

In the spirit of creating lightweight interface-defining packages (see TuringLang/Bijectors.jl#199 which resulted in InverseFunctions.jl and ChangesOfVariables.jl):
While adding an interface-test utility to ChangesOfVariables.jl today, I needed a helper function _to_realvec_and_back - which does exactly what ParameterHandling.flatten does. And I needed it for exactly what #27 is requesting. :-)
It would be nice not to reinvent this, but ParameterHandling would of course be way to heavy a dependency for ChangesOfVariables - and even if it wasn't, we'd end up with a circular dependency since Bijectors will use ChangesOfVariables soon, so ParameterHandling will too.
I think the flatten/unflatten functionality of ParameterHandling does something very fundamental, and is orthogonal to it's variable transformation capabilities. Would you consider splitting it out into a lightweight package (basically the contents of flatten.jl)?
A truly lightweight recursive flatten/unflatten interface package could IMHO find use in many places in the ecosystem. flatten may be a bit too generic a name for the function (we probably have several flattens in the ecosystem), but how about flatten_and_back or so?
CC @willtebbutt, @paschermayr, @devmotion
Update: ChangesOfVariables.test_with_logabsdet_jacobian now has an additional optional argument to pass a transformation, which solves the dependency problem. Users will be able to use ParameterHandling for variable transformations during the test without a direct dependency between the two packages  (after #27 is solved).

How would you feel about depending on ParameterHandling once #42 goes in?

I think even with #42 it think it would still be too heavy - the idea is to keep ChangesOfVariables super-lightweight, so we can convince packages to depend on it, and the stuff in parameters.jl is really a different thing - here, I think, ParameterHandling would depend on ChangesOfVariables, not the other way round. And ParameterHandling is a more opinionated package than ChangesOfVariables.
But now that I think about it, since it looks like we need flatten/unflatten functionality in ChangesOfVariables, how would you like moving that there? It's not much more than I have in the draft of JuliaMath/ChangesOfVariables.jl#2 anyway, and I think it would fit into the theme of the package - it is a change of variables, after all (with a logabsdet-jacobian of 0, of course).
@devmotion, what do you think?

so one might want to have a way to mark parameters as active/constant.

We actually already have a way to mark parameters as being constant (see fixed), although doing things the other way around (marking things as "active") is something that we don't currently have support for -- although we could almost certainly achieve using a trait-based system.

@devmotion pointed me to https://github.com/JuliaDiff/FiniteDifferences.jl/blob/main/src/to_vec.jl
There's probably equivalents of this in several places in the ecosystem, internally. If we had a nice, lightweight central API for this, people could make their types support it, that would make a lot of AD a bit easier. It's handling integers and constant parameters though that makes it less straightforward than I thought initialy - but I think it could (and maybe should) still be decoupled from actual value transformations.

For the interested, here's how Optimisers.jl handles reverse mode friendly (un)flattening: https://github.com/FluxML/Optimisers.jl/blob/master/src/destructure.jl. We opted for the conservative approach and only consider non-integer numeric arrays (due in part to Flux's design constraints). Something like fixed would be interesting, but the main challenge with such a wrapper is making it transparent to non-parameter handling code.

For the interested, here's how Optimisers.jl handles reverse mode friendly (un)flattening

This is build on top of Functors.jl mainly, right?

 To get full performance and type stability (this needs to be really fast and allocation-free with deeply nested structures, flattening to static vectors), I ended up with

flatten(x)
unflatten(x_orig, x_flat)
unflatten_tangent(x_orig, dx_flat)

An approach like x_flat, reconstruct_function = flatten(x) didn't work out performance/type-stability wise, there was trouble when things were nested more deeply (though maybe I did it wrong, I also tried via Flatten.jl but that also didn't work out). Also the x_flat, re = ... pattern didn't provide tangent-unflatten capability.
The problem is that with these flatten/unflatten capabilities "hidden" in several packages in different ways, it's near impossible for users to specify flatten/unflatten for types that need special handling without creating a dependency nightmare. I wonder if we could come up with a generic lightweight thing similar to ChainRulesCore that would satisfy all use cases?

An approach like x_flat, reconstruct_function = flatten(x) didn't work out performance/type-stability wise

I guess you could make methods in case reconstruct_function is not needed.

I think I should link to the current discussion regarding ConstructionBase.getfields/ConstructionBase.getproperties (JuliaObjects/ConstructionBase.jl#54) here, I feel these issues are very connected.

An approach like x_flat, reconstruct_function = flatten(x) didn't work out performance/type-stability wise, there was trouble when things were nested more deeply (though maybe I did it wrong, I also tried via Flatten.jl but that also didn't work out). Also the x_flat, re = ... pattern didn't provide tangent-unflatten capability.

The implementation isn't type stable because of unrelated factors (mostly caching in Functors.jl), but Optimisers.destructure does basically this. Saving some auxiliary state during flattening pays off when # reconstructions > # of flattenings. What does not work well is returning a plain closure, but I'm preaching to the choir here :)

I wonder if we could come up with a generic lightweight thing similar to ChainRulesCore that would satisfy all use cases?

I've thought about this and it's just genuinely hard because of how broad and nuanced "(un)flattening" is. Some examples to chew on:

Flux wants to flatten arbitrary structs with non-flattenable fields without forcing them to be generic in those fields like Flatten.jl requests.
Accounting for parameters that are "shared" or "tied" is hard. Annotating them with a wrapper in the source parameter collection can work, but messes with dispatch in unsuspecting downstream consumers of that collection. Trying to do so automatically turned out to be a rabbit hole we didn't want to mess with in Optimisers.jl.
The same point about wrappers and dispatch applies to constrained parameters as exist in ParameterHanding.jl or ModelParameters.jl.
It may not be possible to derive the fixed-ness of a given subtree's children via the type alone. Here too we see a range of very distinct solutions, including ParameterHanding.fixed and Optimisers.trainable. The latter brings up another point: for many applications we can not assume that all parameter-visiting traversals of an object tree(/DAG) will care about the same set of fields flattening does. This is the motivation behind StructWalk.jl's WalkStyle.

I agree, it's a tricky, multi-faceted problem. But I still think we have too many competing solutions in the ecosystem right now. Maybe one could somehow factorize this into an API for struct-developers that allows them to "annotate" their structs so we need less heuristics/guesswork, and a set of flatten/unflatten APIs for engine/algorithms-developers that make use of those? I don't have a concrete proposal, I just feel that some ChainRulesCore-like (in spirit, not functionality) standard in this area is really missing in the ecosystem (or possibly the language itself) at the moment.

AFAIK something like https://github.com/rafaqz/FieldMetadata.jl could be that standard, but the note at the top of the README seems to suggest differently :/

@rafaqz can we pull you in here as well?

FieldMetadata.jl is a cool idea, but it sets metadata by defining new functions on an object. So you have method table state to think about if you ever want to change anything during use. Its also a lot of confusing and fragile macros for people to understand, that dont scale to organisation/research group level use very well.
ModelParameters.jl is a better solution. You can do most of the same things but state is contained in the object, and has a Tables.jl interface.
What do you need from this package that you can't do with ModelParameters?

Additionally, truly lightweight recursive rebuilding is possible with my PR to Accessors.jl. And thats probably the most generic place to pit it. It hasn't been merged because Im too busy and we can't get it type stable because of issues with Base no longer inferring recursive methods.

What do you need from this package that you can't do with ModelParameters?

If you have a type that needs a bit of special handling, and you want it to be compatible with a wide variety of Julia ML, statistics & friends packages, and you want GPU + GPU support, you currently have to depend on and specialize functionality defined in: Adapt, ConstructionBase, Functors, ParameterHandling, and possibly a few others. To my knowledge, none of those draw on each other for their default implementations. This doesn't compose well and forces packages to either take on a lot of dependencies or not be compatible with parts of the ecosystem. And it can result in a lot of boilerplate code.
As a type developer, I'll probably just want to implement a simple, closure-free API like
get_raw_contents(x::MyType)::Union{Real,Tuple,AbstractArray,NamedTuple}
get_semantic_contents(x::MyType)::Union{Real,Tuple,AbstractArray,NamedTuple}
reconstruct_from(::Type{<:MyType}, ::ResultOfGetRawContents)
reconstruct_from(::Type{<:MyType}, ::ResultOfGetSemanticContents)

The contract here would be
reconstruct_from(typeof(x), get_raw_contents(x) == x
reconstruct_from(typeof(x), get_semantic_contents(x) == x

reconstruct_from should accept contents with a different numeric precision and array types as the original x, of course, if supported by the type.
A package like ConstructionBase would seem a natural place to host such an API.
get_raw_contents  and get_semantic_contents could return tuples, NamedTuples, Reals (even all Numbers?) and Arrays as-is, and return a NamedTuple for structs - get_raw_contents could use fieldcount/fieldname/getfieldandget_semantic_contentscould usepropertynames/getproperty`.
A package like Adapt would probably want to use get_raw_contents for it's default implementation, whereas packages like Functors and ParameterHandling would want get_semantic_contents I guess.

Yes ConstructionBase.jl is the natural place for this, and sharing these base methods across more packages was the original reason for it to be written. Flatten.jl, Setfield.jl and I think BangBang.jl all needed it. Fixing any inadequacies it has to make it useful in these other packages is surely within scope.
In your schema I guess getrawcontents == ConstuctionsBase.getfields (in the current PR by @jw3126) and get_semantic_contents == ConstructionBase.getproperties ?
Also, Adapt.jl is already kind of redundant. You can replace it with Flatten.jl or Accessors.jl with that PR. I do this in some GPU based packages like DynamicGrids.jl, but the current problem with types stability in base makes this less of an option than it used to be.

how would you foresee handling multiple different versions of get_semantic_contents for the same type?

IMO multiple get_semantic_contents on the same type are not the job of ConstructionBase. Analogous to Base not providing multiple variants of getproperty on a single type. Instead I think lenses are a great abstraction for this, so you could use Accessors.jl or Setfield.jl

@oschulz the closure-free API proposal above looks very interesting, one question for now: how would you foresee handling multiple different versions of get_semantic_contents for the same type?

Thanks!
Multiple different versions of get_semantic_contents for the same type in what respect? Could you give a quick example?

I put a relevant example in the comment above, but the gist is that not all traversals we make over a nested object DAG tree (I'm being cheeky here, but handling "shared" nodes is a big part of the Functors codebase) will want to access the same set of fields. Thus defining a single get_semantic_contents function has limited value for our use cases unless the definition of that function is sufficiently general. But then if it's too general, there doesn't seem to be much of a difference between get_semantic_contents and get_raw_contents, AIUI.
This is why I mentioned StructWalk earlier: by parameterizing the (un)flatten function with the type of traversal being performed (WalkStyle), the traversal code can be decoupled from the code that extracts the contents of each node. Generic fallbacks mean that no convenience is lost for types that return the same contents regardless of the purpose of the traversal.

but handling "shared" nodes is a big part of the Functors codebase

That would be part of the nested walk scheme relevant to the application though, right, and orthogonal to the "get content of this type" API?

by parameterizing the (un)flatten function with the type of traversal being performed

Ah, I think I get it @ToucheSir . So you mean instead of having get_raw_contents(x) and get_semantic_contents(x) we'll need something like get_contents(x, decomposition_style), with a matching reconstruct_from(T, content, decomposition_style)?
Do you think there would be a finite number of such "decomposition styles" and/or a kind of hierarchy between them so a type developer won't need to know (and specialize for) all of them?

Do you think there would be a finite number of such "decomposition styles" and/or a kind of hierarchy between them so a type developer won't need to know (and specialize for) all of them?

Yes. The default could be identical to get_semantic_contents(x). I'll pick up the rest on the ConstructionBase thread.


Travis-ci to use docker for faster builds

Not sure why one build failed and the other passed. Any ideas?

I was under the impression that Travis uses docker containers by default these days and you set sudo = true to disable it.
I could be completely mistaken though.

recheck

I'm not sure why PCCI hasn't figured out to recheck this... Will investigate.

@nibalizer any update?

Since this just has an effect on Travis and Travis said it is good, can we merge?

Can you rebase? Merge conflicts.

No longer needed. See https://github.com/voxpupuli/puppet-module-puppetboard/blob/master/.travis.yml#L5


(gitlab-ci-pipelines-exporter) feat: adds ingressClassName property

Fixes https://github.com/mvisonneau/helm-charts/issues/48
This will allow the users to either use the ingress property  ingressClassName, or to keep using the deprecated annotation.
It is default to empty so that it does not change the behavior of the chart.
README has been updated, and fix version has been bumped. If you'd prefer to see the minor version bumped, just let me know and I'll update the PR.
Hope this gets merged and release soon!
Let me know if there's anything I could add.
Signed-off-by: cebidhem<EMAIL_ADDRESS>

brilliant, thanks a lot @cebidhem 🙇 !


Inconsistency between FMI data and custom component?

I noticed that there are differences in weather data between this custom component and FMI data. How does this component define what weather station is being used when GPS coordinates has been used to define place for weather data? For example there are 3 different weather stations in FMI (Pori) and the integration uses which one of those? Here´s some of the data that are not consistent:

Temperature in custom component in Pori: -0,3C
Temperature in Pori Rautatieasema station: -1,8C
Temperature in Pori lentoasema: -1,9C
Temperature in Pori Tahkoluoto satama: -1,2C

I tried to search where this -0,3C value is coming from but was unable to find anything. Also the forecast temperatures are different.
UPDATE I just found out that FMI API data is different than in https://www.ilmatieteenlaitos.fi/. Is this known issue here?

Hi @reprz : The sensor is using this python library to interface with FMI's open data. This library in turn uses the FMI storedquery_id: fmi::forecast::hirlam::surface::point::multipointcoverage. I am not expert on how the data is collected and processed before being made available by the open API, but I am guessing that the multipointoverage format uses observations from more than one weather station. While configuring the sensor, you could set the forecast interval to 1, in which case it uses the current observation API to retrieve data from FMI. If the forecast interval is > 1, it uses the weather forecast API to retrieve data from FMI. I am not sure if this answers your question, but this is the best I know :)

Closing this, as the component just uses the data provided by the open API.


Docker configuration broken after latest 0.5.0 release

Hey all, wanted to flag that our docker build system failed after the latest 0.5.0 release, this is the Dockerfile:
FROM python:3.12.5-slim

WORKDIR /app

RUN apt-get update && \
    apt-get install -y curl unzip && \
    apt-get clean && \
    rm -rf /var/lib/apt/lists/*

RUN curl -LsSf https://astral.sh/uv/install.sh | sh
ENV PATH="/root/.cargo/bin/:$PATH"

COPY requirements.txt .

COPY . /app

RUN /root/.cargo/bin/uv pip install --system --no-cache-dir -r requirements.txt

EXPOSE 7000

CMD ["uvicorn", "main:app", "--host", "<IP_ADDRESS>", "--port", "7000", "--proxy-headers"]

We fixed it for now by pinning the uv version to v4:
FROM python:3.12.5-slim

WORKDIR /app

RUN apt-get update && \
    apt-get install -y curl unzip && \
    apt-get clean && \
    rm -rf /var/lib/apt/lists/*

RUN curl -LsSf https://astral.sh/uv/0.4.30/install.sh | sh
ENV PATH="/root/.cargo/bin/:$PATH"

COPY requirements.txt .

COPY . /app

RUN /root/.cargo/bin/uv pip install --system --no-cache-dir -r requirements.txt

EXPOSE 7000

CMD ["uvicorn", "main:app", "--host", "<IP_ADDRESS>", "--port", "7000", "--proxy-headers"]

What is the recommended way forward for v5 compatibility?

The uv binary isn't installed in .cargo/bin anymore. Check the release notes for full details on this - https://github.com/astral-sh/uv/releases/tag/0.5.0 . But I think changing to .local/bin will fix this for you.


 So I move empirical variograms to a simple pandas.Dataframe: variance, lag, count.
Multi-range estimation: need specific binning (for now I will test the "kmeans" option added in skgstat, but we might have to resort to our own binning, although skgstat doesn't allow for customized binning so it will be annoying), with multiple runs (to assess the stability/std of the empirical variogram) that can be run in parallel using multiprocessing (typically 10,000 samples will take several minutes, it can go up pretty fast)
Integration of variogram/covariance functions over a spatial support: circular integration (spatially continuous ensembles) & double sum of covar based on centroid coordinates (spatially disconnected ensembles).

Nice!
Another suggestion: It would be really nice to have an example in the README for variogram calculations with default settings. Could this be a worthy addition?

Agreed! There is a lot of things in this PR so it's difficult to check it all, but it would be nice to be able to test the different features. Anyway, at some point we should definitely write some documentation/how-to.


Using a module resolver prevents the filesystem from being read or written in the current process

Hello! 👋
Recently I've ran into an issue where I cannot write or read from any filesystem (or even other classes in the same JVM instance) when adding an module resolver thats even a little functional.
When testing, this configuration still prevents the process to read/write:
// Script.java
javetEnginePool.getConfig().setJSRuntimeType(JSRuntimeType.Node);
  try (IJavetEngine<NodeRuntime> iJavetEngine = javetEnginePool.getEngine()) {
    NodeRuntime nodeRuntime = iJavetEngine.getV8Runtime();
    // removing the line directly below fixed the issue, but I need the resolver
    nodeRuntime.setV8ModuleResolver(new Resolver(
      Paths.get(
        JavetOSUtils.WORKING_DIRECTORY, "plugins/NodeScript/modules", module.getName()
      ).toString(),
      parsedPackage.get("main").toString(),
      commandSender
    ));
    if (commandSender instanceof Player) {
      InterceptUtil util = new InterceptUtil();
      util.intercept(nodeRuntime, "player", new NodePlayer((Player) commandSender));
      nodeRuntime.getExecutor(ConstantJSUtil.initializationJS).setModule(true).executeVoid();

      nodeRuntime.getGlobalObject().delete("player");
      util.javetStandardConsoleInterceptor.unregister(nodeRuntime.getGlobalObject());

      } else {
        nodeRuntime.getExecutor(ConstantJSUtil.consoleInitializationJS).setModule(true).executeVoid();
      }
}

The resolver was as simple as this:
// Resolver.java
public class Resolver implements IV8ModuleResolver {
    public String prefix = "";
    public String mainFile = "";
    private CommandSender player;

    public Resolver(String prefix, String mainFile, @Nullable CommandSender playerOutput) {
        // the old arguments were for when it was more functional
        this.prefix = prefix;
        this.mainFile = mainFile;

        if (playerOutput != null) {
            this.player = playerOutput;
        }
    }

    public IV8Module resolve(V8Runtime v8Runtime, String resourceName, IV8Module v8ModuleReferrer) throws JavetException {
        MiniMessage mm = MiniMessage.miniMessage();

        if ("module".equals(resourceName)) {
                String result = "export default {}";
                return v8Runtime.getExecutor(
                                result
                        )
                        .setResourceName(Paths.get(prefix, mainFile).toString()).compileV8Module();
        } else {
            return null;
        }
    }
}

Here is the crash log if you need it, https://pastes.dev/CJarML0qWk

An engine pool holds a set of engines whose module resolvers are supposed to be set during getEngine(), not like the way you do.
Again, please attach a JVM profiler to your application and dump the heap objects. That will be easier to address the issue. You may share the heap dump with me at discord.

Fixed.
You cannot add the path attribute along with the name or else it will fail in the setResourceName function call.
Definitely an interesting issue.


Is there a way to create calculated Questions?

I'm trying to create a survey where there are some questions that are just the result of previous questions e.g.:
Question 1: How tall are you (cm)?
Question 2: What is your weight (kg)?
then I want to have a
Question 3 (calculated value from expression) = {Question 1} * {Question 2} - {Question1}
Question 3 could or couldn't be displayed (using the visible property) but I need the value of Question 3 be evaluated before send to the backend.
Is there any way to accomplish that requirement?
If not, Can I define those question types in the JSON with visible = false and maybe a new attribute "calculatedQuestion=true" to be evaluated in the backend without affect the survey framework?
Thanks in advance guys, you are doing a great job with this framework!.

@zerovirus23 Here is the demo: http://plnkr.co/edit/ElQzlHdpa2LVE833DD54?p=preview
Thank you,
Andrew

No reply for several months. I am closing the issue.


Show class name for debugging of vue styled components

It's me again.
Just wondering if you have a simple solution for this:
For debugging purposes I'd like to have the component name displayed as a class (or any other helper to show which component is rendered). I found this:
Babel plugin for styled components  BUT https://github.com/styled-components/babel-plugin-styled-components/issues/60 it does not work with vue styled components. If anyone comes up with a solution, let me know 😄

Hi @Jones-S,
I think this is not the work that vue-styled-components should do.
Using Vue DevTools you can have the name of component and the generatedClassName :)


Expand on the Generate at Breakpoints documentation

Consider adding a section specifically dealing with u-spacing?

Yeah I think that's needed. Could you read the current documentation: https://github.com/chris-pearce/scally/blob/master/utilities/README.md#applying-at-breakpoints and let me know what's missing? I think the actual code needs more documentation also.


travis: Automate docker builds

This adds automation for docker builds when a new tag is pushed up. Once a new tag is pushed up, docker build gets run with that tag used as the docker tag that then gets pushed up to docker hub.
This depends on 4 new environment variable to be set up in the settings:

DOCKER_REPOSITORY - digitalocean
DOCKER_IMAGE_NAME - netbox
DOCKER_USERNAME - we have a user set up for this (stored as a secure environment variable)
DOCKER_PASSWORD - password for the aforementioned user (stored as a secure environment variable)

cc @zachmoody @mdlayher

:+1: Looks good here!


feat: add build to npm prepare

So we can easilly npm install v-mapbox from local repository or GitHub branch or fork. This simplifies e.g. local development, testing of fork in our production environment etc.

My usecase is also ability to use branches and forks in npm install. Do you know some other solution?
Honza Pobořil
💬Signal

11. 8. 2022 v 7:47, Vinayak Kulkarni @.***>:

@vinayakkulkarni commented on this pull request.
In package.json:

"prepare": "husky install",

"prepare": "husky install && npm run build",
When you build while prepare, the dist directory is generated & as the CI checks show, the minified etc. versions will have lint issues.

Thanks for opening the PR but I think having a --watch script would be more helpful than having build while prepare
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you were mentioned.


catalog: Remove unused interface function ListMonitoredNamespaces()

The ListMonitoredNamespaces() function in the MeshCatalog interface is not used anywhere.  Here is the definition and the 2 lines that can be deleted:  https://github.com/openservicemesh/osm/blob/main/pkg/catalog/types.go#L117-L118
This can be safely deleted. (go vet ./... tells me it is safe)
We should also update the catalog mock at ./pkg/catalog/mock_catalog_generated.go

ListMonitoredNamespaces() was added to be able to list the monitored namespaces in the debug server, however the work was not complete, so it didn't make it to the debug server.
Please evaluate if this should be exposed in the debug server prior to removing it.

We decided to implement ListMonitoredNamespaces instead of deleting it.

The ListMonitoredNamespace() is already required by MeshCatalogerDebugger.
So we don't need it in MeshCataloger.


Plugin loading from external directories

I'm not sure if there is a way to do this or if this is a feature request or an oversight:
Assume that I have a plugin that works if placed with regular plugins: flexget/plugins/filter/my_filter.py. I now want to this plugin from a custom directory location, for example, assume that it is now located at ~/foobar/flexget/plugins/filter/my_filter.py.
I tried using PYTHONPATH or FLEXGET_PLUGIN_PATH, but neither worked; either all other regular plugins in the flexget plugin directory are no longer found or my plugin cannot be found. Is my use case supported? Or am doing something wrong?
There could be more documentation for this, I found FLEXGET_PLUGIN_PATH by looking at the source of flexget/plugin.py.

The third party plugin directory is usually ~/.flexget/plugins. It should be a folder called plugins in the same directory as your config.

Thanks for the feedback. Is it possible to change this?

Not that I know of.

I just tried your suggested method. I copied the flexget/plugins/filter/accept_all.py to ./plugins/filter/accept_all.py (with . I mean the directory where my config file is and I call flexget execute). Then I renamed it to accept_all2.py and inside I changed the string to 'accept_all2' and the class name in the register call and above as well.
While it seems that this use case is supported as just creating the file changed the behavior without any further configuration; I did not even use the plugin in the configuration. However, the problem now is that I get some error regarding the dependencies:
2016-12-30 14:00 CRITICAL plugin                        Plugin `flexget.plugins.filter.accept_all2` failed to import dependencies
Traceback (most recent call last):
  File "/opt/python27/lib/site-packages/flexget/plugin.py", line 395, in _load_plugins_from_dirs
    __import__(module_name)
ImportError: No module named accept_all2
2016-12-30 14:00 VERBOSE  task_queue                    There are 1 tasks to execute. Shutdown will commence when they have completed.
2016-12-30 14:00 VERBOSE  details       task1      Produced 2 entries.
2016-12-30 14:00 WARNING  task          task1      Task does not have any filter plugins to accept entries. You need at least one to accept the entries you  want.
2016-12-30 14:00 VERBOSE  details       task1      Summary - Accepted: 0 (Rejected: 0 Undecided: 2 Failed: 0)
2016-12-30 14:00 WARNING  task          task1      Task doesn't have any output plugins, you should add (at least) one!

It does not say what the problem is. Do I need to do anything else for this to work?

Sounds like you changed too much/little. Just change https://github.com/Flexget/Flexget/blob/develop/flexget/plugins/filter/accept_all.py#L31 to plugin.register(FilterAcceptAll, 'accept_all2', api_ver=2)

The error remains the same. I just tried to create a minimal working test. I should be able to use an arbitrary in register as long as I still use the same name in the declaration above. If I place the file inside the site-packages/flexget/plugins/filter everything works, if I move the file to ./plugins/filter it breaks for me. Is there anything else I need to do for it to work?

I think I found the problem: In the "plugins" directory, the structure must not mirror the structure of the flexget packages; i.e. you cannot use a "filter" subdirectory as it was used, instead the *.py file for the plugin has to placed directly in plugins.
Nevertheless, this is all not easily accessible or well-documented, or is it? And this is more or less a workaround for what I initially asked, although I guess using the current working directory as it can be done is not a bad solution for using a custom path.

Hmm, yeah. It was never intended to have directory structure in there. Indeed, not very well documented (if at all).

Please reopen in feathub


Table Storage

Right now, we're using Table Storage as the backend storage for the project. Is it the best option? Can we provide alternatives? Maybe create a storage interface?

Effort on remove-table-storage branch to completely get rid of table storage

Table Storage removed in #11


New version: YY.YYAnchor version <IP_ADDRESS>54 (<IP_ADDRESS>)

Created by 🥟 Dumplings in workflow run #7969.

Log
Updated: <IP_ADDRESS> → <IP_ADDRESS>
Submitting WinGet manifests
Creating manifests
Uploading manifests and making commits
Creating a pull request

Microsoft Reviewers: Open in CodeFlow

Automatic Validation ended with:

No errors to post.

(Automated response - build 895.)


Ability to list ignored files

Right now i don't see the ignored files in the macOS Timemachine GUI. Is it possible that tmignore lists the ignored files?

Nvm... no files were added by tmignore.

When using the tmutils command to exclude files (which tmignore does internally), they unfortunately don't show up in the System Preferences: https://apple.stackexchange.com/questions/222346/time-machine-exclusions-added-via-tmutil-do-not-appear-in-tm-options-list.
Right now, you can run tmutil isexcluded FILE_PATH to check whether a file/directory has been excluded, or look at the cache at ~/Library/Caches/tmignore/cache.json.
Adding a tmignore list command or a tmignore run --verbose flag is probably a good idea. I'll look into that :)

The list command will be available in the next release.


Ability to download ones data and notebooks as a zip file

We should probably make it easy for folks to download all their data and notebooks as a zip file with a single click.

Even downloading a single file from the navigation screen would be nice. For example, I have my data saved as a .txt file and wanted to download it but was surprised there wasn't a download button.

Oh, just kidding: I see now that you can do it through the Files tab. I think the Upload symbol threw me off.


fix: China is not showing number of contributors

There was two names for China, I removed one of the since having both of them is not letting the number of contributions be visible on the map.

Thanks for your PR

Thank you for accepting it!


Parenthesis on both sides

Follow-up from #250 .
In #250 I updated isolateSymbolOnLeftSide but neglected to also update removeSymbolFromRightSide.
I think because https://github.com/socraticorg/mathsteps/pull/250/files#diff-2dc14e1c8322de958fc4c52d204c30b5R42-R45, the right side (rightly) returns a node with a symbol, but because I didn't modify removeSymbolFromRightSide, an error was occurring when the right side couldn't handle the parenthesis node.
Thanks @evykassirer !

hm ok so as I was laying in bed last night trying to sleep, I remembered there's a 'removeUnnecessaryParens` that theoretically should solve all these issues, and it's called here https://github.com/socraticorg/mathsteps/blob/master/lib/solveEquation/stepThrough.js#L79 which I think should be before the point where your error comes up?
would you mind looking into this and seeing why you were having those problems despite 'removeUnnecessaryParens`? I remember now that we were trying to avoid putting parenthesis code throughout the codebase, we mostly assumed that unnecessary parens just wouldn't be there

https://github.com/socraticorg/mathsteps/blob/master/lib/solveEquation/stepThrough.js#L58
Set the value of the param "rootNode"  to true can fix it
 equation.leftNode = removeUnnecessaryParens(equation.leftNode, true);
 equation.rightNode = removeUnnecessaryParens(equation.rightNode, true);

hey @evykassirer sorry for the delay! will close this PR and address separately


Update Python.gitignore to include .bak files created by 2to3

The standard Python distribution's 2to3 tool migrates code from Python 2 to Python 3.
The tool will create files with the extension '.bak' when run with -w argument, which appears to be fairly standard usage.
For example:
2to3 -w test.py
will produce:
test.py.bak

It seems to me that it would be a bad idea to have these .bak files hanging around indefinitely. Once you've verified that the automatic conversion was reasonable, you'd delete the files. They aren't going to keep reappearing. So thanks, but I think it's at best unnecessary and at worst encouraging a bad pattern to make this addition.


Wording of telemetry options

VSCode should be 'VS Code' or 'Visual Studio Code'
Should we also advice that extension should follow this setting? In that case we could name it 'Allow usage data and errors to be collected by Microsoft or by extension authors'

I know that we can't enforce that, but good behaving extensions should follow it.

VSCode should be 'VS Code' or 'Visual Studio Code'

Since we also have an insiders flavor of the product I would not mention the product name in the description and just state:
This option requires a restart to take effect


Worflow tries (and fails) to publish rust packages when version is not updated

Assuming libits-client version x.y.z
Both libits-copycat and its-client have a dependency on libits-client on x.y
This means that minor fix on libits-client might bup the corrective z which does not impact the dependency declaration
The tagging workflow tries to push both libits-copycat and its-client even if their version did not change
As shown  in last update to v1.1.1
Two possibilities:

We can consider that every component version should be bumped at the same time
(not very relevant in my own opinion as if nothing changes in the code, the version )
Look up into Github workflow to trigger crates.io publishing only on version change

@tigroo @ymorin-orange Open for discussion

After 2.0.0 refactoring there should be only one crate remaining and this problem not happen anymore
Will close this on refactoring final merge


docs: Fixed Example MessageOptions -> PaginationItem

Please describe the changes this PR makes and why it should be merged: Fixed typo, import that doesn't exist in beginner code example
Package

@discordx/pagination

fixing prettier

Squash it

Can we get contributers role in discord server by docs contribution & #919

Can we get contributers role in discord server by docs contribution & #919

yeah, please leave your discord username or tag me in discord @samar

Can we get contributers role in discord server by docs contribution & #919

yeah, please leave your discord username or tag me in discord @samar

@samarmeena
@arnavk09 ~ Dope : @ArnavK-09

Can we get contributers role in discord server by docs contribution & #919

yeah, please leave your discord username or tag me in discord @samar

@samarmeena
@arnavk09 ~ Dope : @ArnavK-09

Interesting to see we share such a similar username!

Can we get contributers role in discord server by docs contribution & #919

no

Can we get contributers role in discord server by docs contribution & #919

no

Can we get contributers role in discord server by docs contribution & #919

no

@VictoriqueMoe
You D🔑-evil
Trollingmmeeeeee....ԅ( ͒ ۝ ͒ )ᕤ

Can we get contributers role in discord server by docs contribution & #919

no

@VictoriqueMoe
You D🔑-evil
Trollingmmeeeeee....ԅ( ͒ ۝ ͒ )ᕤ

Can we get contributers role in discord server by docs contribution & #919

yeah, please leave your discord username or tag me in discord @samar

@samarmeena
@arnavk09 ~ Dope : @ArnavK-09

Interesting to see we share such a similar username!

@arnavk09
Loll,

Btw u r the reason I had to put extra - in my GitHub user name 🥰


MAINTAINERS: Add kruithofa as collaborator for BT ISO

Added kruithofa as a collaborator as they are familiar with ISO and we should have at least 2 collaborators to perform reviews.

@Thalley would it make sense to just merge this area with Bluetooth Audio?

@Thalley would it make sense to just merge this area with Bluetooth Audio?

Yes and no.
Bluetooth ISO and Bluetooth Audio is not the same. ISO only has 1 BT SIG defined usecase today which is LE Audio, but it's not limited to that, and the majority of the people involved with LE Audio in Zephyr have not been involved with the BT ISO work. Arguably LE Audio is closer to GATT than ISO in that regard :D
If it becomes an issue with reviews then I think we need to revisit it, and perhaps it should just be merged with the host (it's quite similar to L2CAP).


Access Forbidden

Cannot access Sparkle intro talk

grr, sorry 'bout that.
The pdf is here: https://cdn.parleys.com/p/53a7d2cce4b0543940d9e55a/g3ZWPlN7Oj5-SparkleIntroTalk1.pdf (no animations in the pdf though!)
This more recent set of slides is still accessible: https://docs.google.com/presentation/d/1q3upEFivpx-IClqiDlFHl4FQZrLRWAWdYiFI-keJbQU/edit?usp=sharing

I've requested access for the recent slides. Meanwhile I think this video should be added


backport #21933 to 3.0 branch

Checklist

[ ] documentation is added or updated
[x] tests are added or updated

relate to #23018

@nhorman ，is the fips-provider-validation  test failed caused by newly added code snippet in evp_test.c?

Will look as soon as.i get to my desk

@nhorman , help! is the fips-provider-validation test failed caused by newly added code snippet in evp_test.c?

Yes the CI is relevant.

thx, I will fix these.

@nhorman , help! is the fips-provider-validation test failed caused by newly added code snippet in evp_test.c?

Yes the CI is relevant.

Hi @t8m , I have fix these issues. Please review again.

This pull request is ready to merge

This requires another review from @openssl/committers as @nhorman is the original author.

This pull request is ready to merge

Merged to the 3.0 branch. Thank you for your contribution.

I am seeing test failures on 3.0.13 which are related to this merge request.
For the testsuite to pass, I have to revert the following commits:

58a6aa0c9fe6abad996f45c6b452983035db7105
879a853a1dc968fb010e5bf17d2e8888acc70742
0398bc20080de037a8433fe81cfdef3ba0ec9d4c

shlibtest needs to be disabled during the back-port.

I am seeing test failures on 3.0.13 which are related to this merge request.
For the testsuite to pass, I have to revert the following commits:
* [58a6aa0](https://github.com/openssl/openssl/commit/58a6aa0c9fe6abad996f45c6b452983035db7105)

* [879a853](https://github.com/openssl/openssl/commit/879a853a1dc968fb010e5bf17d2e8888acc70742)

* [0398bc2](https://github.com/openssl/openssl/commit/0398bc20080de037a8433fe81cfdef3ba0ec9d4c)

As we do not see the failures in our CI could you please open a  new issue and report the failures that you see?

@adrien-n ^

Sorry for not answering earlier; GH needs a reaction that amounts to "ack, thanks for your answer, I'm currently looking into it and it might take me some time".
I also didn't answer earlier because I had a weird feeling following the comments here. It turns out that the issue happens only when we also patch in a backport of at least one of commits 8a75952ba829784f5cb499c4883a5729c226e38c or 949108dd73de321fb93c8d81b846a2a1d015a9fd . Right now I see several possible causes:

the CPU support patches,
the backport of these patches,
the combination of these patches and the patches I mentioned earlier,
something else.

@t8m I'll therefore open a bug when I can tell which one of these possibilities it is in order to make a proper one; this is taking a while as the builds are LTO (including tests) (and, checking whether the builds should be LTO is already scheduled in the coming weeks).


Support javascript.preferences.quoteStyle as a language specific setting

From this thread:
https://twitter.com/mannieschumpert/status/1475927885156343820
and these docs: https://code.visualstudio.com/updates/v1_63#_jsx-attribute-completions
My best guess is that for the video in the docs, "javascript.preferences.quoteStyle" is set to "single" or it is set to "auto" and there is an import or require statement that we can't see that uses single quotes.
The ask from this twitter thread is support different quote styles for JavaScript and JavaScript React file types.  However, the quoteStyle setting is not supported for per language configurations:

For some clarification of the problem that led to this issue:
It is not actually not just language-specific, but style specific. I would guess that the example in the video is using Airbnb JSX style conventions, as described here: https://airbnb.io/javascript/react/#quotes
In this particular, but very popular, style convention, single quotes are used everywhere in any JSX or TSX file, except for when declaring JSX component attributes.

I'd like to echo @mannieschumpert  comments.
When choosing JSX attribute completion style = auto, i get single quotes despite the fact that the tooltip explicitly says i should get double quotes:

I guess this has to do with the fact that the general quotes style is set to auto (single):

Somehow the two settings need to be combined with a new option to enable using single quotes in the general case, but double quotes in the specific case of JSX attribute completion (as well as any other inline markup fragments such as HTML/XML).
CC: @mjbvz

@mannieschumpert  Can you please file a feature request upstream for that
I only fixed what the original issue here described

Verified that in Insiders:

I can now customize the quote style for the javascriptreact language
Configuring a preference for 'single' will autocomplete attributes with single quotes even if there are double quotes elsewhere in the file
Configuring a preference for 'double' will autocomplete attributes with double quotes even if there are single quotes elsewhere in the file
Configuring a preference for 'auto' will match inferred preference from elsewhere in the file


Check if the extra max is needed and if logsumexp > max  does not hold always due to numerical issues.

Write a test either confirming the numerical issue or confirming the absence of it.
Line:
https://github.com/iesl/box-embeddings/blob/e70e283cbb6bda411ce0bd28ea713abb53b8fae1/box_embeddings/modules/intersection/gumbel_intersection.py#L36

The extra max is needed. See this slack discussion and this.


how to set video pre-loading system

How can I preload multiple Videostreams before playing them

@mahesha2 As mentioned in the chat, need to clarify.
For your information, currently Toro relies on RecyclerView behaviour, so the ViewHolder (ToroPlayer) need to be bound and attached to be prepared. It doesn't support preparing Video before that event.


Remove LLVMExtSetCurrentDebugLocation from llvm_ext.cc

To reflect LLVM's C API, LLVM::Builder itself is no longer responsible for creating debug locations, and they now have to be obtained from LLVM::Context directly.
LLVM::Builder now maintains a reference to its parent LLVM::Context. This is necessary for the deprecated #set_current_debug_location method, and also for the new #current_debug_location= only on LLVM 8.

This is probably wrong, the correct context seems to be that of the LLVM::Module used to create the LLVM::DIBuilder, rather than that of an LLVM::Builder


VirtualBox: error when running restart command to a stopped machine

This is a regression.  When trying to run restart on a stopped machine, an error occurs.  Only tested in VirtualBox.

@ehazlett just checked this and couldn't replicate

@awsmsrc thanks for verifying!  i think this was fixed in #832 just merged.  thanks!


Mono installation issues on Ubuntu 20.04 and 22.04

Description
Running the VM image build for Ubuntu 20.04 and 22.04 has installation issues with Mono (installation is successful on Ubuntu 24.04.
Platforms affected

[X] Azure DevOps
[ ] GitHub Actions - Standard Runners
[ ] GitHub Actions - Larger Runners

Runner images affected

[X] Ubuntu 20.04
[X] Ubuntu 22.04
[ ] Ubuntu 24.04
[ ] macOS 11
[ ] macOS 12
[ ] macOS 13
[ ] macOS 13 Arm64
[ ] macOS 14
[ ] macOS 14 Arm64
[ ] Windows Server 2019
[ ] Windows Server 2022

Image version and build link
Azure DevOps Agent version: 3.238.0
Is it regression?
It probably is, due to change in mono installation location on their end
Expected behavior
Mono should be able to install successfully on Ubuntu 20.04 and 22.04
Actual behavior
Ubuntu20.04.txt
Repro steps

Run build for Ubuntu 20.04 or 22.04
You'll get the error as on the attached file

Hey @ross-bohr!
Our nightly build were successful: ubuntu-20.04, ubuntu-22.04. I'll run it again just in case (ubuntu-20.04, ubuntu-22.04).
Seems to be transitive or related to your Azure org network/firewall settings since the main issue is:
Connection failed [IP: <IP_ADDRESS> 443]

Also regarding ubuntu-24.04 comment:

installation is successful on Ubuntu 24.04

There is no Mono on ubuntu-24.04, so I almost sure that there is a connection issue on your side.

Closing item as not reproducible. Please, check your org network and security configs.


Andrew/change temp dir

Canonical snaps don't let you use system tmp dir (it should really be a config setting or maybe a c group or something).
There is no good solution, we use /home/$USER/.prefix-tmpXXXXX, firefox uses, for example /home/$USER/Downloads/... but its not guaranteed to exist.

GHA sems broken, chromium wont install, that's why it keeps failing. Moving timeout back to 4 minutes and letting it fail before merging.


Is it possible to run Titan on BigTable?

They use the HBase API, but have some slight differences.
HBase differences: https://cloud.google.com/bigtable/docs/hbase-differences

I think it should technically be possible to implement KeyValueStore against BigTable.

This is now a duplicate of 1203.  Recommend we close either this one or 1203, and not sure this needs an issue open against Titan, unless the idea is Titan include a titan-bigtable module, which doesn't seem like a good idea.

Closing in favor #1203 as @graben1437 suggested.

Seems weird since this one was opened/existed first... but anyhow. :smile:

If it makes you feel any better, I suspect the other will be closed as well before we're all done going through issues. :)
When it comes to new backends for Titan, we generally like to see folks develop those externally in their own repositories, get community feedback and then watch how it evolves.  Amazon did this nicely.  I think MapDB has an implementation in the works like that.

I know, mostly kidding.
On Thu, Dec 17, 2015, 10:00 AM stephen mallette<EMAIL_ADDRESS>wrote:

If it makes you feel any better, I suspect the other will be closed as
well before we're all done going through issues. :)
When it comes to new backends for Titan, we generally like to see folks
develop those externally in their own repositories, get community feedback
and then watch how it evolves. Amazon did this nicely. I think MapDB has an
implementation in the works like that.
—
Reply to this email directly or view it on GitHub
https://github.com/thinkaurelius/titan/issues/1117#issuecomment-165493678
.

@jturmel, @graben1437 — you can use JanusGraph (fork of Titan) together with Bigtable; see JanusGraph + Bigtable docs for configuration details.


alternative initialization of Activity(items: ...)

Have you read the Contributing Guidelines?
Yes.
Describe the feature
Clearly and concisely describe what you would like to add.
UIActivityViewController accepts an argument of type [Any] so it would be nice to carry that forward here.  In my case, i'd like to list several PDFs for printing all at once.
Is your feature request related to a problem?
Clearly and concisely describe the problem.
No.
Proposed solution
Clearly and concisely describe the solution you'd like to see. Include implementation details, if possible.
I suggest adding the following init() to ActivityItem.
		/// The
		/// - Parameters:
		///   - items: The array of items to share via a `UIActivityViewController`
		///   - activities: Custom activities you want to include in the sheet
	public init(items: [Any], activities: [UIActivity] = [], excludedTypes: [UIActivity.ActivityType] = []) {
		self.items = items
		self.activities = activities
		self.excludedTypes = excludedTypes
	}

Alternatives considered
Clearly and concisely describe any alternative solutions or features you've considered.
None.  The current implementation accepts only variadic parameters and not an array.
Additional context
Add any other context or screenshots about the feature request here.
None.

Yep, makes sense. Feel free to open a PR 👍

Closing as per https://github.com/SwiftUI-Plus/ActivityView/pull/4#issuecomment-1063114330


Add env flag to not spin up agent

This piece is need as we move towards each config deploying their own agent and not relying on the agency to do it
Signed-off-by: Jacob Saur<EMAIL_ADDRESS>

This is part of security ticket https://github.com/kiva/protocol/issues/906 where the plan is to deploy agents directly via docker/k8s and not by making a call to the agency. The flag will prevent the controller from trying to spin up an agent if one has already been deployed.


Windows - requirement installation errors

Hello,
cffi==1.14.6. installation fails, installation of 1.15.0 works
undetected-chromedriver 3.0.2 installation fails as well, and my windows could install only 1.4.0 version..
So I am not really sure if that's a bug of my python configuration is bad, can you provide some support, please?
Python 3.10.0
Collecting undetected-chromedriver==3.0.2
  Using cached undetected-chromedriver-3.0.2.tar.gz (37 kB)
  Preparing metadata (setup.py): started
  Preparing metadata (setup.py): finished with status 'error'

Use python 3.6 to 3.9

Worked with python 3.9.9.
But still with cffi 1.15.0
Thanks!


Fix a bug where builders of LogFormatter return internal classes

Motivation:
TextLogFormatterBuilder.build() and JsonLogFormatterBuilder.build() return package-private classes that cause compilation errors when using them in different packages.
Modifications:

Make TextLogFormatterBuilder.build() and JsonLogFormatterBuilder.build() return LogFormatter instead of the internal classes.

Result:
You can no longer see compilation errors when using TextLogFormatterBuilder.build() and JsonLogFormatterBuilder.build().

@minwoox PTAL. 🙇♂

Thanks for quick fix
I'll be more careful🙇♂

I'll be more careful

It was not you but me. 🤣


0.2.34

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

@mkw this is going to fail because the containers never built. There weren't any notable server-side changes. Anything in particular you're looking for?

Ah -- I did not realize that there were no real server side changes. We just needed the topology fix; if we just need a new client, we have what we need. Sorry for the noise, and thanks for the fix!

@mkw no worries! I'll reach out when I release v0.3.0. You'll want to roll that one quick as the CLI will cut over to the new version of the API. Should just require a re-run of the indexer. We'll probably also want to chat a little about artifactory support as that's something we've discussed and done in the past.


[vcpkg baseline][libcaer] Disable parallel configure

Fix bug:
CMake Error at include/libcaer/CMakeLists.txt:3 (CONFIGURE_FILE):
  No such file or directory

Confirmed that https://gitlab.com/inivation/dv/libcaer/-/blob/master/include/libcaer/CMakeLists.txt#L3 is an in-source write, thanks!


Library not working with reactive forms #106

Hi there, I'm trying to use your library, exactly as stated in docs, with reactive forms, but it doesn't seem to work at all, it works only with ngModel, which is deprecated for years already and doesn't work together with reactive forms. Can you have a look?
at my form component:
public salvageForm = new FormGroup({
salvageAmount: new FormControl()
});
and the template:
{{ "customerSalvage.salvageAmount" | columnName }}
package.json: "dependencies": { "@angular/animations": "^8.2.14", "@angular/cdk": "^8.2.3", "@angular/common": "^8.2.14", "@angular/compiler": "^8.2.14", "@angular/core": "^8.2.14", "@angular/forms": "^8.2.14", "@angular/platform-browser": "^8.2.14", "@angular/platform-browser-dynamic": "^8.2.14", "@angular/router": "^8.2.14", "@ng-bootstrap/ng-bootstrap": "5.1.5", "@swimlane/ngx-charts": "13.0.1", "bootstrap": "4.4.1", "classlist.js": "^1.1.20150312", "core-js": "^3.6.5", "moment": "^2.25.3", "moment-range": "^4.0.2", "ngx-currency": "^2.3.3", "rxjs": "^6.5.5", "tslib": "^1.13.0", "web-animations-js": "^2.3.2", "zone.js": "~0.10.2" },
app module is exactly as in docs, with global config.
does ahead of time compilation matter?
This library is crucial for me, so I will appreciate any help

You can still use ngModel inside a reactive form, just use the [ngModelOptions]="{ standalone: true }" option.

Hello. The following example uses the library with reactive forms.
https://github.com/cesarrew/ng2-currency-mask/tree/master/projects/library-test

Another option: https://stackblitz.com/edit/angular-ivy-bpn8by


Change DiagnosticInfo to base0D

The normal texts of text documents (txt / README / Latex) usually use base05 (white) color. The DiagnosticInfo is using base05, too. When I use the grammar LSP such as ltex-ls, the inline diagnostic message is hard to identify. Following image shows the example (in base-tomorrow-night colorscheme):

After change to base0D (Blue):

The normal texts are not special keywords. The diagnostic message will be overwhelmed by long normal texts. Changes to base0D can make the diagnostic message more clear.

Tentative merge, I'll try it out for a bit and will see in the future how it holds up.


[s3] fix s3 test_multipart_resend_first_finishes_last

https://github.com/seaweedfs/seaweedfs/pull/5466
What problem are we solving?
Fix s3 test after https://github.com/seaweedfs/seaweedfs/pull/5460
before
> fs.meta.cat /buckets/s3tests-dd5yzog4kxg6oyf0sgvkz-1/mymultipart
{
  "name": "mymultipart",
  "isDirectory": false,
  "chunks": [
    {
      "fileId": "17,274308ee6411",
      "offset": "0",
      "size": "8",
      "modifiedTsNs": "1712310513156040000",
      "eTag": "liHt+a4GC4KwqQsJleGvKA==",
      "sourceFileId": "",
      "fid": {
        "volumeId": 17,
        "fileKey": "10051",
        "cookie": 149840913
      },
      "sourceFid": null,
      "cipherKey": "",
      "isCompressed": false,
      "isChunkManifest": false
    },
    {
      "fileId": "18,274416d812ee",
      "offset": "8",
      "size": "8",
      "modifiedTsNs": "1712310513159642000",
      "eTag": "runjjLTUDsJ5RUJWdTm0yA==",
      "sourceFileId": "",
      "fid": {
        "volumeId": 18,
        "fileKey": "10052",
        "cookie": 383259374
      },
      "sourceFid": null,
      "cipherKey": "",
      "isCompressed": false,
      "isChunkManifest": false
    }
  ],
  "attributes": {
    "fileSize": "16",
    "mtime": "1712310513",
    "fileMode": 504,
    "uid": 501,
    "gid": 20,
    "crtime": "1712310513",
    "mime": "",
    "ttlSec": 0,
    "userName": "",
    "groupName": [],
    "symlinkTarget": "",
    "md5": "",
    "rdev": 0,
    "inode": "0"
  },
  "extended": {},
  "hardLinkId": "",
  "hardLinkCounter": 0,
  "content": "",
  "remoteEntry": null,
  "quota": "0"
}chunks 2 meta size: 177 gzip:205

How are we solving the problem?
add sorting function by modification time
How is the PR tested?
action tests
Checks

[ ] I have added unit tests if possible.
[ ] I will add related wiki document changes and link to this PR after merging.

@chrislusf Done

https://github.com/seaweedfs/seaweedfs/pull/5470/files copied some code that can be refactored together?

https://github.com/seaweedfs/seaweedfs/pull/5470/files copied some code that can be refactored together?

It seems like already

hi, @kmlebedev how to run the seaweefs s3test in local？

hi, @kmlebedev how to run the seaweefs s3test in local？

git clone https://github.com/seaweedfs/seaweedfs
cd seaweedfs
make server

git clone https://github.com/ceph/s3-tests
cd s3-tests
S3TEST_CONF=s3tests.local.conf tox -- s3tests_boto3/functional/test_s3.py::test_multipart_resend_first_finishes_last
or docker run docker.io/kmlebedev/ceph-s3-tests:0.0.2

I run s3test using "docker run docker.io/kmlebedev/ceph-s3-tests:0.0.2 ",  it completed very quickly (1s) without doing anything, and there are no logs in docker logs either， my linux is ubuntu20.04,  do you have any suggestions?


First compositional chart

In this pull request:

Rearranged template views into "chartView", which has the chart and is shown first, and "aboutView", which will be filled in later
Created new D3 chart, Number of Posts by Subreddit, based on a few online resources, plus my own tweaking (including an animated loading indicator!)
The "refresh" button now refreshes both the chart and the total number of comments.

Next steps:

Genericize this code so that it's simple to make new "compositional" charts with existing server JSON
Create other "compositional" charts using the genericized code
Rearrange view/link selection so we're actually using the header bar

Neat! LGTM


feat(fretboard): improve supporting materials

enhance storybook and readmes to reflect fretboard evolution

:tada: This PR is included in version 1.13.0 :tada:
The release is available on:

GitHub release
v1.13.0

Your semantic-release bot :package::rocket:


Make a separate artifacts for "reflection" and "general" approach

I see that the library have the following proguard rule:
https://github.com/kirich1409/ViewBindingPropertyDelegate/blob/48d2e6e561c322d9f02365db388dffa899c8805e/library/proguard-rules.pro#L1
It prevents on obfuscation *ViewBinding classes. If I don't use reflection in delegate I expect that all my classes will be obfuscated.
The proposal is to make separate artefacts:

viewbindingpropertydelegate - regular logic, without reflection under the hood
viewbindingpropertydelegate-reflection - additional extensions for reflection approach + keep rule for ViewBinding classes.

Also with two artefacts, it will be clear for everyone what kind of delegate better to use and etc.

Will be added in 1.2.0


Pop-Up Usabilla at the end of each tutorial (at least in skillmap)

We'd like the usabilla modal to pop-up automatically when the student clicks "Finish".

No plans to implement.


Fix block ordering in dead branch elim

Fixes #1727

If the pass finds any dead branches it can optimize then at the end of
the pass it reorders basic blocks to ensure they satisfy block ordering
requirements
Added some new tests
While investigating this issue, found and fixed a non-deterministic
ordering of dominators
Now the edges used to construct the dominator tree are sorted
according to posorder traversal indices

Note: including multiple ordering functions limited the number of test updates required and kept disassembly reading more naturally.

Rebased, squashed and committed as 28199b80b7c70a03c1002c81503ed480554d9ade


Failed connect to stable.release.core-os.net:443; No error

D:\coreos-vagrant>vagrant up
Bringing machine 'core-01' up with 'virtualbox' provider...
==> core-01: Box 'coreos-stable' could not be found. Attempting to find and inst
all...
core-01: Box Provider: virtualbox
core-01: Box Version: >= 0
==> core-01: Adding box 'coreos-stable' (v0) for provider: virtualbox
core-01: Downloading: https://stable.release.core-os.net/amd64-usr/current/c
oreos_production_vagrant.json
core-01: Progress: 0% (Rate: 0curl:/s, Estimated time remaining: --:--:--)
An error occurred while downloading the remote file. The error
message, if any, is reproduced below. Please fix this error and try
again.
Failed connect to stable.release.core-os.net:443; No error

Moved to https://github.com/coreos/bugs/issues/1353


perf list broken after update

Describe the bug
> perf list >/dev/null && echo ok
ok
> perf list -j
Segmentation fault

Additional context
I am using linuxPackages_latest.perf inside WSL. This was working before a nix flake update, and if I revert that update, it works again. The working version corresponds to this version of nixkpgs
    "nixpkgs": {
      "locked": {
        "lastModified":<PHONE_NUMBER>,
        "narHash": "sha256-ql45o9jOLA9L32NmnYm8eXwhEFe36m91x1q6Kad3FLk=",
        "owner": "nixos",
        "repo": "nixpkgs",
        "rev": "d0a7ba022ef00e015aaf87ae14432d8f6662f0c4",
        "type": "github"
      },
      "original": {
        "owner": "nixos",
        "repo": "nixpkgs",
        "type": "github"
      }
    },

Can you get a gacktrace from perf crash? Should be a matter of running gdb --args perf list and typing bt in gdb session.
I wonder if it's related to libpfm dependency added a while ago in https://github.com/NixOS/nixpkgs/pull/250180


Renaming the processing page to storage

This PR renames processing.md to storage.md and fixes the links.
Fixes:

#61
#54

Marking this as a draft to check the Netlify deployment first.

I'm marking this as ready for review now! The donut image is also updated, and thus this PR will fix #70 as well.


Add one hot op

This PR implements the operator one_hot. The one called onehot_encode in the current code base will be deprecated.

Also, set backward to be zero gradient like https://github.com/dmlc/mxnet/blob/master/src/operator/tensor/broadcast_reduce_op_index.cc#L18


Too small contentType and encoding problems

I have Rails app, which uses utf-8 encoding.
First problem:
Sep  3 10:45:07 localhost mailslurper[61761]: time="2019-09-03T10:45:07+02:00" level=error msg="There was an error while storing your mail item: Error inserting new mail item in StoreMail: Error 1406: Data too long for column 'contentType' at row 1" who="Database Receiver"
appears when column contentType of table mailitem uses VARCHAR(50). After Changing to 255 this error disappear.
Second problem is related with crashed emails encoding.

I had changed database to MySQL (from SQLite) but it did not help. I also changed encoding for database (default was latin1_swedish_ci):
ALTER DATABASE mailslurper CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_ci;
and for tables inside it:
ALTER TABLE attachment CONVERT TO CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_ci;
ALTER TABLE mailitem CONVERT TO CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_ci;
Could you help with this issue?

The Second probleme is the same as https://github.com/mailslurper/mailslurper/issues/126.
I posted there about the quotedprintable encoding package that would help I suppose : https://golang.org/pkg/mime/quotedprintable/


Issue: Cannot see scores in LangSmith dashboard

Issue you'd like to raise.
I cannot see the scores of my evaluations in LangSmith experiments dashboard

Below is the code,
# Grade prompt
from langsmith import EvaluationResult
grade_prompt_answer_helpfulness = prompt = hub.pull("langchain-ai/rag-answer-helpfulness")

def answer_helpfulness_evaluator(run, example) -> dict:
    """
    A simple evaluator for RAG answer helpfulness
    """

    # Get question, ground truth answer, RAG chain answer
    input_question = example.inputs.get("input_question") or ""
    prediction = run.outputs.get("output") or ""

    # LLM grader
    llm = ChatOpenAI(model="gpt-4o", temperature=0)

    # Structured prompt
    answer_grader = grade_prompt_answer_helpfulness | llm

    # Run evaluator
    score = answer_grader.invoke({"question": input_question,
                                  "student_answer": prediction})
    score = score["Score"]
    print(f'score in answer_helpfulness_evaluator: {score}')
    return EvaluationResult(key="answer_helpfulness_score", score=score)

from uuid import uuid4
from langsmith.evaluation import evaluate
from llm import get_ai_response

experiment_results = evaluate(
    lambda inputs: get_ai_response(inputs["input_question"]),
    data=dataset_name,
    max_concurrency=2,
    evaluators=[answer_evaluator, answer_helpfulness_evaluator],
    experiment_prefix="test-run",
    metadata={"version": str(uuid4()), "chunk_count": "2"},
)

Suggestion:
Am I missing a configuration?

Hm thislooks correct at first glance - are there any error logs in your terminal?

i dont see any error logs in the terminal.


Ability to change hover popup size from an extension.

I'm developing an extension which includes a language server and I'd like to be able to change the hover popup size either directly or alternatively through a size hint from the language server along with the Hover content.
Currently the only way to achieve this is to directly modify the CSS.

I'd like to add a bit more about my motivation. My language server generates images from the context and pushes this images to the client as hover popups. Currently Hovers do expand horizontally and show a scrollbar vertically as the maximum size is reached.


[XCM]: Improved fee mechanism

Moved from https://github.com/polkadot-fellows/xcm-format/pull/53.
The idea is to extend the current XCM fee mechanism to support in principle delivery fees, but potentially other types of fees as well.
This is accomplished by having two additions:

PayFees instruction
A fees register, where fees go and stay there until the end of execution. Crucially, separate from the holding register

/rfc propose

/rfc process 0x39efd93063aeaef13afdb2135a775fec4d87fe3ed51e9bf122bc73a336acd509