Issues when running on Linux

Hello, I have a problem, and it is that I am using version 1.8.2 because if I use another version or the most updated one, for some reason the NPCs do not spawn. I have a zombie system, they connect but do not appear. However, when using that version, they do spawn. The problem I have is that when I run this version (1.8.2) on Windows, everything works fine. But when I put it on Linux and the zombies appear, the NPC's death is displayed in the console, and the server freezes, with the CPU at 100%. The player gets frozen or if they try to reconnect, it stays at "connecting to the game" and then displays "server closed." What could this be?
Is there a dependency or something? is a new vps linux (ubuntu)

A lot of crashes was fixed in latest versions of the plugin, so the problem can be in anything.
I think you should find the way how to use latest version. Take a look at breaking changes here and convert your functions for new version of the plugin.

Do you have any idea what the problem is with NPCs connecting but not
appearing? They do appear, but all in the same default position of SA-MP
(x:0, y:0, z:0), but they don't move as they should near a player? However,
using version 1.8.2, they do move as expected.
El mar, 8 ago 2023 a las 13:10, Sergei Marochkin @.***>)
escribió:

A lot of crashes was fixed in latest versions of the plugin, so the
problem can be in anything.
I think you should find the way how to use latest version. Take a look at
breaking changes here
https://github.com/ziggi/FCNPC/releases/tag/v2.0.0-rc.1 and convert
your functions for new version of the plugin.
—
Reply to this email directly, view it on GitHub
https://github.com/ziggi/FCNPC/issues/293#issuecomment-1670073366, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/BBCGO3KRQ7FAVU4EYN5VICDXUJ6IDANCNFSM6AAAAAA3I2KFWE
.
You are receiving this because you authored the thread.Message ID:
@.***>

No, I have no idea. Try to spawn on empty gamemode or try to run something from example scripts.


New minor release

Sorry, @CermakM but you are not stated in maintainers section for this project. Maintainers are @cermakm

Reopen after: https://github.com/CermakM/kebechet/commit/aab2051cba6efed32630ae2bff1eda915f722457


[WIP] chore!: Drop python 3.8. Add python 3.13

Requires https://github.com/actions/python-versions/pull/308
Python 3.13 has been delayed until 2024-10-07

greenlet is having trouble compiling. Will wait until there is an official 3.13 release. Not too worried as we do not have compiled code.

greenlet==3.0.3 is required by playwright v1.47.0. As of this comment v1.47.0 is the latest version on PyPI.
https://github.com/microsoft/playwright-python/pull/2589 has been merged to main two days ago adding python 3.13 support and updating greenlet to a python 3.13 compatible version.
This dependency hell is frustrating to deal with as it is out of our control. 🔔 **shame.png

Getting past playwright, we hit tokenizers failure to build. Related GitHub Issue: https://github.com/huggingface/tokenizers/issues/1639
They're waiting for more upstream changes. ⏳


Annotate global constants that refer to C functions with @convention(c)

Motivation:
This fixes https://github.com/apple/swift-nio/issues/206.
Also see: https://bugs.swift.org/browse/SR-7242.
Modifications:
Annotated global constants that refer to C functions with `@convention(c), and added explcit types.
Results:
https://bugs.swift.org/browse/SR-7242 is worked around.

@normanmaurer @weissi:
This is my first patch - hopefully I haven't done anything wrong/stupid here. My apologies in advance if I have. Please let me know if I have, and I'll fix it!
I'm also not sure how to add tests for this, since it involves looking at the result of the compiler. If you have any ideas, please let me know and I'll take a crack at it.

@swift-nio-bot test this please

Hmm, not sure what part of the validation failed? I ran swift test locally, and it worked. Unfortunately the "details" link seems to point to a Jenkins instance that needs a login (which I don't think I have) so I can't take a look at what failed.

@gps
08:03:56 /code/Sources/NIO/System.swift:63:69: error: use of undeclared type 'CNIODarwin_mmsghdr'
08:03:56 private let sysSendMmsg: @convention(c) (CInt, UnsafeMutablePointer<CNIODarwin_mmsghdr>?, CUnsignedInt, CInt) -> CInt = CNIOLinux_sendmmsg
08:03:56                                                                     ^~~~~~~~~~~~~~~~~~
08:03:56 /code/Sources/NIO/System.swift:64:69: error: use of undeclared type 'CNIODarwin_mmsghdr'
08:03:56 private let sysRecvMmsg: @convention(c) (CInt, UnsafeMutablePointer<CNIODarwin_mmsghdr>?, CUnsignedInt, CInt, UnsafeMutablePointer<timespec>?) -> CInt  = CNIOLinux_recvmmsg
08:03:56                                                                     ^~~~~~~~~~~~~~~~~~
08:03:56 error: terminated(1): /root/.swift/usr/bin/swift-build-tool -f /code/.build/debug.yaml main

Please run the tests in linux as well to check it builds :)
cd docker && docker-compose up test

@gps let me know once I should have a look again and thanks :)

@normanmaurer:

Please run the tests in linux

That explains it. Found the problem and fixed it.

let me know once I should have a look again

Should be good to go now, docker-compose up test works locally for me.

@swift-nio-bot test this please

Nice one @gps , thanks!


[consensus] split round manager into dedicated task

Motivation
This commit splits the round manager into separate task from main loop so that the mempool long poll won't block the main loop.
Also deleted the recovery manager which creates maintainence burden without much benefit.
Have you read the Contributing Guidelines on pull requests?
(Write your answer here.)
Test Plan
(Share your test plan here. If you changed code, please provide us with clear instructions for verifying that your changes work.)
Related PRs
(If this PR adds or changes functionality, please take some time to update the docs at https://github.com/diem/diem/tree/main/developers.diem.com, and link to your PR here.)
If targeting a release branch, please fill the below out as well

Justification and breaking nature (who does it affect? validators, full nodes, tooling, operators, AOS, etc.)
Comprehensive test results that demonstrate the fix working and not breaking existing workflows.
Why we must have it for V1 launch.
What workarounds and alternative we have if we do not push the PR.

/land


Use ethereum-types 0.3

This removes operators which are part of 0.4. In guac we ingest eth-types 0.4 too (althea_types) but also eth-types 0.3 (ethabi). This isn't easily replacable, so probably going back to 0.3 everywhere is safest thing to do.
I tried two approaches:

Remove num256 and use BigInt/BigUint directly. Ran into custom serialization issue for backwards compatibility (default BigInt/BigUint serialization produces array of array bytes and we keep big nums as string, big unsinged nums as hexadecimal etc.). Kinda works, but needs more effort to figure out failing test cases.
Make Uint256 a wrapper too, possibly implementing operators and make it look like a type (just like Int256). Probably the best way to go, just need some effort to write all traits to make Int256/Uint256 usable like normal numbers (and there are a lot of them)

This debt should be paid at some point, possibly could be done as part of #25.
And of course this will move forward #236

looks good to me


update PCRE2 to version 10.31, fixes #15662

Steps to replicate upgrade:

Download version 10.31 (ftp://ftp.csx.cam.ac.uk/pub/software/programming/pcre/pcre2-10.31.tar.gz)
Copied over AUTHORS and LICENCE files.  Some minor changes.
Copy src folder over.
Rename src/config.h.generic to src/config.h (as recommended in the comments at the top of the file)
Rename src/pcre2.h.generic to src/pcre2.h (as recommended in the comments at the top of the file)
Rename src/pcre2_chartables.c.dist to src/pcre2_chartables.c
Remove src/config.h.in (presumably this is taken care of by the generic header?)
Remove src/pcre2.h.in (presumably this is taken care of by the generic header?)

Are there any files that don't need to be included?  Perhaps src/pcre2test.c?
I was able to compile godot but I'm unsure about bugs or regression as mentioned in the original issue request 15662.  If others can review this I would be grateful.
Also, please git squash during merge or let me know and I can rebase.

None of the new files are compiled in modules/regex/SCsub, so either they are not needed, or they should be added to the SCsub. Some of those are arch-specific though and should only be compiled on the relevant arch.
CC @leezh for review/advice.

Also, please git squash during merge or let me know and I can rebase.

We prefer not to use squash on merge on this repo, so it's better if you can do the squash in your branch directly.

I git squashed and made some updates.  I tried to reconcile the files in the current build system in Scons.  In some cases there were files in the git repo that are not listed in the build system.  Thanks for the help/comments.  Here are some notes:
src/dftables.c
Removed
This is a freestanding support program to generate a file containing
character tables for PCRE2.
src/pcre2_extuni.c
Added, unicode is built by default so I added this
https://www.pcre.org/current/doc/html/pcre2unicode.html
https://www.pcre.org/current/doc/html/pcre2build.html
"This module contains an internal function that is used to match a Unicode
extended grapheme sequence. It is used by both pcre2_match() and
pcre2_def_match(). However, it is called only when Unicode support is being
compiled."
src/pcre2_fuzzsupport.c
Removed
standalone program
src/pcre2posix.c
src/pcre2posix.h
"This module is a wrapper that provides a POSIX API to the underlying PCRE2
functions."
src/pcre2demo.c
Demo not needed
src/pcre2grep.c
Seems to be standalone and not used in current build system
src/pcre2_jit_test.c
Not in current build system
src/pcre2_printint.c
For debugging, not in build system
src/pcre2test.c
For testing, not in build system

I have been busy the past few months and totally missed the update. Thanks for doing it for me. They look good but with the added steps in replicating the upgrade you ought to add in a README file with the instructions.

The README file exists already, so instructions should be updated here: https://github.com/godotengine/godot/blob/master/thirdparty/README.md#pcre2 (together with the version number).

Updated thirdparty/README per suggestions.


#bug; Pancakeswap V2 Indexing Error

See: https://okgraph.xyz/?q=messari%2Fpancakeswap-v2-swap-bsc

Same issue occuring, re-opening this issue to track it.

@melotik I made a new one (https://github.com/messari/subgraphs/issues/2400), so going to close this


Update dynamic resource pools and impala admission control

Would it be possible to update dynamic resource pools for YARN and Impala Admission control via cm_api?

I'm also interested in ,did you achieve it?

Would it be possible to update dynamic resource pools for YARN and Impala Admission control via cm_api?

I'm also interested in ,did you achieve it?

Good , I will try it!


Update Ruby 2.3.0 to 2.3.3 and test 2.4.0 on CI.

Happy holidays :)

Apparently we have to wait for https://github.com/rails/rails/commit/47c49242913abbcdb8f798f53324769892d18c97 to get compatibility with Ruby 2.4/Rails 4.2.


Update Keeper's Supported Network Format

update content to be aligned with VRF Contract Address page (../docs/vrf-contracts/)
Update parts of docs to be in html

Rebased to main


Initial pose feature does not work.

Launching with start_trajectory_with_default_topics = false:
catkin_make_isolated --use-ninja
source devel_isolated/setup.bash
roslaunch cartographer_ros demo_backpack_2d_localization.launch \
  load_state_filename:=${SOME_PBSTREAM}

and then
./devel_isolated/cartographer_ros/lib/cartographer_ros/cartographer_start_trajectory \
 --configuration_directory="${CARTOROS}/cartographer_ros/configuration_files" \
 --configuration_basename="backpack_2d_localization.lua" \
 --initial_pose="{ to_trajectory_id=0, relative_pose={translation={1, 0, 0},rotation={0.0,0.0,0.0} }}" \
rosbag play --clock ${SOME_BAG}

does not work.

What exactly doesn't work?
I can confirm that this works at least with an older version of cartographer_ros @ b4e7705159 - we are also using it on our robots.

@pifon2a @MichaelGrupp
In the previous version of cartograoher_ros, it worked. However, at least this commit @ e4bfd557975443c3be71253adde71e153379a258, it showed ERROR message. Error message is related to below code.
`if (srv.response.status.code != cartographer_ros_msgs::StatusCode::OK) {
LOG(ERROR) << "Error starting trajectory - message: '"
<< srv.response.status.message
<< "' (status code: " << std::to_string(srv.response.status.code)
<< ").";
return false;
} '

That's code I added. But this doesn't produce any problems with the version I mentioned. I can take a look at this with the current HEAD the next days.
What's the exact error output?

I could happily send initial poses with the current master. Still an issue for you?

Probably, I was doing something wrong. Closing it.


init() got multiple values for argument "type"

I'm getting this while trying to run against my personal twitter.db database created using https://github.com/dogsheep/twitter-to-sqlite

  File "/usr/local/Cellar/datasette/0.47.1/libexec/lib/python3.8/site-packages/datasette_graphql/__init__.py", line 57, in view_graphql
    schema = await schema_for_database(datasette, database=database)
  File "/usr/local/Cellar/datasette/0.47.1/libexec/lib/python3.8/site-packages/datasette_graphql/utils.py", line 167, in schema_for_database
    graphene.Field(
TypeError: __init__() got multiple values for argument 'type'

Looks like the problem is caused by this table:
CREATE TABLE [since_ids] (
   [type] INTEGER REFERENCES [since_id_types]([id]),
   [key] TEXT,
   [since_id] INTEGER,
   PRIMARY KEY ([type], [key])
);

And this code: https://github.com/simonw/datasette-graphql/blob/e6a8459be9867f79259e930eeaaf76d4df272d0f/datasette_graphql/utils.py#L157-L174

I think I can fix this using args= on the Field class:
https://github.com/graphql-python/graphene/blob/6918db1033269a79d7e2370d51e66da383302f4b/graphene/types/field.py#L47-L49
        args (optional, Dict[str, graphene.Argument]): Arguments that can be input to the field.
            Prefer to use ``**extra_args``, unless you use an argument name that clashes with one
            of the Field arguments presented here (see :ref:`example<ResolverParamGraphQLArguments>`).


404 Not Found link

Previous link redirects to a 404 Not Found. Changed link to point to current "Segmenting your Contacts" doc, which contains info for creating and exporting a segment.
Description of the change: Changed link to point to current "Segmenting your Contacts" doc, which contains info for creating and exporting a segment.
Reason for the change: Previous link redirects to a 404 Not Found.
Link to original source: https://github.com/sendgrid/docs/blob/develop/content/docs/ui/managing-contacts/custom-fields.md

Closes #

Hello @krischoi07,Thanks again for the PR! It's HACKTOBERFEST! We want to show our appreciation by sending                                              you some special Hacktoberfest swag. If you have not already, could you please fill out                                              this form so we can send it to you? Thanks!                                             Team SendGrid DX


creating and hosting sitemap.xml

@fils , in a general sense, is this how you would need sitemap.xml made available? (we have roughly 3 million PIDs at the moment)
https://developers.google.com/search/docs/advanced/sitemaps/large-sitemaps
Is it possible to have nested sitemap indexes?
For example, we have many namespaces, /orgA /orgB /orgC, and each of these might have multiple categories of pids /orgX/sites, /orgX/wells, etc. each of which may have more than 50k urls.
Is it ok to have an overal sitemap index.xml that points to namespace-specific sitemap index.xml that themselves refer to category sitemap index.xml that then point to 50k pages of sitemap.xml?

In general there's probably going to be a lot of noncompliant json-ld from contributing orgs.
https://geoconnex.us/cuahsi/his/NHGS_WOF/LOVOTECS-CAR
contexts with things like : "name": "schema.name" and such

@ksonda so yeah, that is not so good.
That page's JSON-LD not even formed correctly.  Gleaner will log an error for it.
Even when fixed there are other issues as you point out.   This is why I think SHACL may be important sooner than later.  We can combine SHACL shapes with notebooks people can run from mybinder or Google Colab that let them assess their holdings.
Otherwise you are going to have issues in recovery in SPARQL  or you end of with ugly SPARQL to compensate for these issues that has performance issues.   I've seen both. :)


Implement traffic analytics - Use query parameters to understand the sources of where our users are coming from. [2sp]

Pass a query paramter to the order requests (utm-source)
Send parameter to mixpanel
Store the data next to the order
Send info to the slack channel
[2 storypoints]

According to my research:

GA automatically detects the following utm_ parameters:

utm_source: Identify the advertiser, site, publication, etc. that is sending traffic to your property, for example: google, newsletter4, billboard.
utm_medium: The advertising or marketing medium, for example: cpc, banner, email newsletter.
utm_campaign: The individual campaign name, slogan, promo code, etc. for a product.
utm_term: Identify paid search keywords. If you're manually tagging paid keyword campaigns, you should also use utm_term to specify the keyword.
utm_content: Used to differentiate similar content, or links within the same ad. For example, if you have two call-to-action links within the same email message, you can use utm_content and set different values for each so you can tell which version is more effective.

I coudln't confirm that the GA tracking SDK is extracting these parameters. It just sends the whole URL to google-analytics.com which makes sense because then they don't have to update the SDK when they change something. @Dansken needs to confirm that the utm_ parameters are recognized

Same goes for mixpanel. Acccording to this site, the SDK automatically tracks the utm_ parameters. I couldn't confirm that they are sending them to mixpanel.com but they are leaked through the Referer header, so that could be possible. @Dansken also needs to confirm that.

@jhnns Please consult with @stefan-all3dp About this topic.

Please, let us store all of the UTM-Parameters: utm_source, utm_medium, utm_campaign, utm_term, utm_content

Should the utmParams be preserved when the configuration is shared?

Blocked by https://github.com/all3dp/printing-engine/issues/411


Feedback form - check for missing data from first feedback session

Netlify didn't retain the inputs from first feedback session

Can this be closed?


[Discuss] Resolve the Callback Hell

The existing codebase contains many callbacks, obscuring overall readability, bringing much overhead to new developers and development maintenance.
At the language level, Java has provided CompletableFuture, which is so expressive that neat and simplified solutions are possible. Refer to folly future and this blog to see a potential difference.
Additionally, with future-style of code, sync and async APIs are implemented in a unified way.

Opinions are welcome.

Second this. As a contributor who recently start to read the code in detail, I often found the original style of callback code is quite annoyed. The usage of CompletableFuture might erase this kind of obscurity to some extent.

Dismissed


Leaf is not starting.

Leaf Version: 4.4.0 (also tried with latest release 4.4.4 on GitHub)
Description of the Bug
The plugin isn't loading.
Console Errors
https://pastebin.com/QPzbaY3R

Hey @frafol have you tried with a newer release? should be working now :3


Set shorthandOnlyDefinesConfig = false; in hm-config

Description
The home manager module defines the nixvim module with shorthandOnlyDefinesConfig = true;. This means when trying to import a config module, one gets an error unless they make the nixvim config module into a function
https://github.com/nix-community/nixvim/blob/main/wrappers/hm.nix#L24
Minimal, Reproducible Example (MRE)
# as a home-manager module
programs.nixvim = {
  imports = [
    ./nixvim-config.nix
  ]
}

Causes the error error: The option home-manager.users.username.programs.nixvim.imports' does not exist.`
To fix it, one has to declare the home manager to not be "shorthand", which gets rid of the error:
# as a home-manager module
programs.nixvim = {...}:{
  imports = [
    ./nixvim-config.nix
  ]
}

The Fix
Set shorthandOnlyDefinesConfig = false;. I dont see nixvim using a config option, so this should not break anything.
My Usecase
I want to expose nixvim as a package of my config flake as well as be part of the home manager config. Therefore I have one single config that defines the nixvim options which is then imported in my home-manager config and exposed as a package via inputs'.nixvim.legacyPackages.makeNixvim

Wouldn't this prevent someone defining nixvim options as follows:
programs.nixvim = {
  foo = "bar";
  bar = "baz";
};

And they'd instead need to do:
programs.nixvim = {
  config.foo = "bar";
  config.bar = "baz";
};

Or have I misinterpreted the purpose of shorthandOnlyDefinesConfig?

Also, I plan to replace the submoduleWith with (evalNixvim {}).type[^1], are you aware of how that'd fit in with this?
[^1]: evalNixvim is a thin-wrapper for lib.evalModules

Ok, re-reading the docs:

shorthandOnlyDefinesConfig Whether definitions of this type should default to the config section of a module (see Example: Structure of NixOS Modules) if it is an attribute set. Enabling this only has a benefit when the submodule defines an option named config or options. In such a case it would allow the option to be set with the-submodule.config = "value" instead of requiring the-submodule.config.config = "value". This is because only when modules don't set the config or options keys, all keys are interpreted as option definitions in the config section. Enabling this option implicitly puts all attributes in the config section.
With this option enabled, defining a non-config section requires using a function: the-submodule = { ... }: { options = { ... }; }.

You're right, this option only has an effect when the submodule has a config or options sub-option. Historically, until #1324 we used to have an options option, so that is likely the original reason why we set shorthandOnlyDefinesConfig.
It won't be set when using (lib.evalModules {}).type, so I'll likely bundle the fix for this into the PR switching away from submoduleWith.

Alright, thanks 👍


Compatibility with AngularJS ng-repeat

Hello,
It looks like the library as it stands is incompatible with using AngularJS ng-repeat inside of an element with class="list", since the Templater clear() function removes all content within that element. This has the effect of removing the comments that AngularJS uses to know where to begin inserting the elements from its ng-repeat iteration.
(This method involves using list.js by extracting the relevant list information from existing HTML)
The solution I developed just skips over childNodes with the nodeName "#comment" or "#text," which might not be the most graceful workaround, but does produce the intended effect. Any chance for a more official solution?
Great tool, by the way. Thanks!

Hi! I haven't worked anything with Angular myself and my experience is that List.js sometimes becomes a bit superfluous when you use a framework like Angular, Ember, React etx. To the short answer is that I at the moment aren't planning to do a official solution for this problem unfortunately.


Factorial and gamma functions

And fixes for nonfinite values for EDecimal extensions
Resolves #50

Oof that's a huge PR. It seems okay overall, but I need to dig into it a bit deeper. Sorry for the late response

Don't we need some kind of inverse Gamma function for equation solving?

To implement it, we need the Lambert W function (as noted in https://github.com/Happypig375/AngouriMath/blob/d4a7da91c230ed925775f2e11b2093012a0c9c8b/AngouriMath/Functions/Algebra/EquationSolver/Analytical/AnalyticalSolver.cs). I couldn't find an implementation for arbitrary precision evaluation of this function.

Seems like we need to call into the Newton Solver for evaluating this function: https://www.quora.com/How-is-the-Lambert-W-Function-computed?share=1

So we need some kind of inverse for Gamma and Gamma's derivative.


VS code freezes when editing CSS file with emoji.

VSCode Version:

Version: 1.28.2
Commit: 7f3ce96ff4729c91352ae6def877e59c561f4850
Date: 2018-10-17T00:20:56.183Z
Electron: 2.0.9
Chrome: 61.0.3163.100
Node.js: 8.9.3
V8: 6.1.534.41
Architecture: x64

OS Version: Linux (Debian buster/sid)

uname -a
Linux [...] 4.17.0-1-amd64 #1 SMP Debian 4.17.8-1 (2018-07-20) x86_64 GNU/Linux

Steps to Reproduce:

open a new file
paste this in the file:

.🐷-a {
}

save the file as style.css
start editing the first line after checkbox:

.🐷-abbbbb... {
}

VS code hangs (I can type about 1 or two b)

Does this issue occur when all extensions are disabled?: Yes

I have't tried testing with insiders build, I'm trying to figure out now how to do that.


Added support for $translate.instant

Coverage increased (+0.04%) to 96.863% when pulling 9b3e6d1c97042324e258d53f1e823a68dc9a0e30 on setor:master into 7a99fedbb237a08f0e440f14b4b61657d6172d8c on MichaReiser:master.

Coverage increased (+0.04%) to 96.863% when pulling 9b3e6d1c97042324e258d53f1e823a68dc9a0e30 on setor:master into 7a99fedbb237a08f0e440f14b4b61657d6172d8c on MichaReiser:master.

Coverage increased (+0.04%) to 96.863% when pulling 05551c46c73490b14ba1d73491dfabe88b15cd31 on setor:master into 7a99fedbb237a08f0e440f14b4b61657d6172d8c on MichaReiser:master.


Developers can add an "interface" canister type for canisters they don't have wasm (e.g. already deployed)

Currently, people are creating bogus custom canisters, but it would be better to have a dedicated type that is semantically closer to what people want/expect.
It should probably have a DID field and a canister ID field. The canister ID should have a network map.
Something like this:
{
  "type": "interface",
  "did": "some/path/to/file.did",
  "canisterId": {
    "local": "abcde-fghij-aa",
    "ic": "...",
  }
}

The difficulty of this feature is in the mapping to canister ID, which until now we always understood to be in the canister_ids.json file. A potential solution would be to write the same map of canister ID in the file on build.
This new canister type is a no-op for building and installing.

Implemented a while ago as 'remote canister'


add types for flux text to image model

Minor change
Adds missing types @cf/black-forest-labs/flux-1-schnell text to image model.
Ref: https://developers.cloudflare.com/workers-ai/models/flux-1-schnell/

Helps remove multiple @ts-expect-error statements across our internal code base

@cf/black-forest-labs/flux-1-schnell returns json, while other models returns ReadableStream<Uint8Array>
I think you can't simpliy reuse exist types

Agreed @xcaptain, Raised a new PR to address that #3163


Dart mode should handle nested comments

Dart has nested comments, but the highlighter doesn't treat them like nestable. Test in Dartpad.
/*
/*
 Comment

 /* nested comment */

*/ // <-- not highlighted

main() {}

Related: https://github.com/codemirror/CodeMirror/pull/2947#issuecomment-64822887
Related: https://github.com/dart-lang/sdk/issues/25931

@devoncarew Do you want to take a look at this?


[files/scripts/webhook.py] Change default hostname localhost->dev.packit.dev

per CONTRIBUTING.md#running-packit-service-locally

* packit-service-pre-commit : FAILURE in 2m 33s

https://github.com/packit-service/requre/pull/99

recheck


Add support for nested exclusive predicates with JSON index; fix semantics for exclusive predicates

The JSON index currently doesn't support nested (within AND / OR) exclusive predicates (NOT IN, !=, IS NULL) with the JSON_MATCH filter operator.
The reason for this is the existing semantics for exclusive predicates that are inconsistent and confusing.
A document like:

 [
   {
     "key1": "value1",
     "key2": 1
   },
   {
     "key1": "value2",
     "key2": 2
   }
 ]

matches "$[*].key2" = 1, but not "$[*].key2" != 2 for example.

Essentially, the wildcard array access for inclusive predicates means that we match the array when ANY value matches, but for exclusive predicates, we match the array when ALL values match.
Furthermore, a document like:

 [
   {
      "key1": "value1",
   }
 ]

matches "$[0].key2" != 2 which is counterintuitive since the object doesn’t contain key2 at all.

The reason for both of these inconsistencies and confusing semantics is the way that exclusive predicates are implemented. Exclusive predicates are currently handled by finding the flattened doc IDs of the corresponding inclusive predicate, mapping them back to the corresponding unflattened doc IDs, and then inverting / flipping the resultant bitmap. And that is also the reason why nested exclusive predicates aren’t supported currently since the intermediate flattened doc ID results can’t be combined with flattened doc ID results from other child predicates while maintaining the same semantics.
This patch fixes the above inconsistencies so that [*] now means the same for both exclusive and inclusive predicates, and documents where a key doesn't exist aren't matched for the exclusive predicates NOT IN, !=. It also adds support for nested exclusive predicates.
The new implementation for NOT IN, != make use of similar logic to the implementation for the regex and range predicates (https://github.com/apache/pinot/pull/12568).
Essentially, we first get all the values for a corresponding key. Then, we iterate through the values - and for each value that matches the predicate, we add the list of corresponding flattened doc IDs to the result.
The IS NULL predicate is handled by inverting the flattened doc ID bitmap of the corresponding IS NOT NULL predicate.
Suggested labels: feature, backward-incompat, release-notes

Codecov Report
Attention: Patch coverage is 0% with 249 lines in your changes are missing coverage. Please review.

Project coverage is 0.00%. Comparing base (59551e4) to head (031f9b1).
Report is 439 commits behind head on master.

Files
Patch %
Lines

...local/realtime/impl/json/MutableJsonIndexImpl.java
0.00%
127 Missing :warning:

...t/index/readers/json/ImmutableJsonIndexReader.java
0.00%
122 Missing :warning:

Additional details and impacted files
@@              Coverage Diff              @@
##             master   #13139       +/-   ##
=============================================
- Coverage     61.75%    0.00%   -61.76%
=============================================
  Files          2436     2440        +4
  Lines        133233   134269     +1036
  Branches      20636    20795      +159
=============================================
- Hits          82274        0    -82274
- Misses        44911   134269    +89358
+ Partials       6048        0     -6048

Flag
Coverage Δ

custom-integration1
?

integration
0.00% <0.00%> (-0.01%)
:arrow_down:

integration1
?

integration2
0.00% <0.00%> (ø)

java-11
?

java-21
0.00% <0.00%> (-61.63%)
:arrow_down:

skip-bytebuffers-false
?

skip-bytebuffers-true
0.00% <0.00%> (-27.73%)
:arrow_down:

temurin
0.00% <0.00%> (-61.76%)
:arrow_down:

unittests
?

unittests1
?

unittests2
?

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

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Webpack require fails

Requiring the package with Webpack fails in my web-project:
WARNING in ./~/mermaid/src/d3.js
Critical dependencies:
5:4-11 require function is used in a way in which dependencies cannot be statically extracted
 @ ./~/mermaid/src/d3.js 5:4-11

WARNING in ./~/mermaid/src/diagrams/flowchart/dagre-d3.js
Critical dependencies:
7:4-11 require function is used in a way in which dependencies cannot be statically extracted
 @ ./~/mermaid/src/diagrams/flowchart/dagre-d3.js 7:4-11

WARNING in ./~/mermaid/src/diagrams/flowchart/parser/dot.jison
Module parse failed: /Ruse/Nodrium/n-landing/node_modules/mermaid/src/diagrams/flowchart/parser/dot.jison Line 4: Unexpected token %
You may need an appropriate loader to handle this file type.
|
| /* lexical grammar */
| %lex
|
| %%
 @ ./~/mermaid/src/diagrams/flowchart ^\.\/.*$

WARNING in ./~/mermaid/src/diagrams/flowchart/parser/flow.jison
Module parse failed: /Ruse/Nodrium/n-landing/node_modules/mermaid/src/diagrams/flowchart/parser/flow.jison Line 8: Unexpected token %
You may need an appropriate loader to handle this file type.
|
| /* lexical grammar */
| %lex
| %x string
|
 @ ./~/mermaid/src/diagrams/flowchart ^\.\/.*$

WARNING in ./~/mermaid/src/diagrams/classDiagram/parser/classDiagram.jison
Module parse failed: /Ruse/Nodrium/n-landing/node_modules/mermaid/src/diagrams/classDiagram/parser/classDiagram.jison Line 8: Unexpected token %
You may need an appropriate loader to handle this file type.
|
| /* lexical grammar */
| %lex
| %x string struct
|
 @ ./~/mermaid/src ^\.\/.*$

WARNING in ./~/mermaid/src/diagrams/gantt/gant.css
Module parse failed: /Ruse/Nodrium/n-landing/node_modules/mermaid/src/diagrams/gantt/gant.css Line 2: Unexpected token *
You may need an appropriate loader to handle this file type.
|
| * {
|     margin: 0;
|     padding: 0;
 @ ./~/mermaid/src ^\.\/.*$

WARNING in ./~/mermaid/src/diagrams/example/parser/example.jison
Module parse failed: /Ruse/Nodrium/n-landing/node_modules/mermaid/src/diagrams/example/parser/example.jison Line 6: Unexpected token %
You may need an appropriate loader to handle this file type.
|  *  MIT license.
|  */
| %lex
|
| %options case-insensitive
 @ ./~/mermaid/src ^\.\/.*$

WARNING in ./~/mermaid/src/diagrams/gantt/parser/gantt.jison
Module parse failed: /Ruse/Nodrium/n-landing/node_modules/mermaid/src/diagrams/gantt/parser/gantt.jison Line 6: Unexpected token %
You may need an appropriate loader to handle this file type.
|  *  MIT license.
|  */
| %lex
|
| %options case-insensitive
 @ ./~/mermaid/src ^\.\/.*$

WARNING in ./~/mermaid/src/diagrams/sequenceDiagram/parser/sequenceDiagram.jison
Module parse failed: /Ruse/Nodrium/n-landing/node_modules/mermaid/src/diagrams/sequenceDiagram/parser/sequenceDiagram.jison Line 11: Unexpected token %
You may need an appropriate loader to handle this file type.
|  *  Simplified BSD license.
|  */
| %lex
|
| %options case-insensitive
 @ ./~/mermaid/src ^\.\/.*$

WARNING in ./~/mermaid/src/less/default/flow.less
Module parse failed: /Ruse/Nodrium/n-landing/node_modules/mermaid/src/less/default/flow.less Line 1: Unexpected token .
You may need an appropriate loader to handle this file type.
| .mermaid .label { color:#333}
|
| .node rect,
 @ ./~/mermaid/src ^\.\/.*$

WARNING in ./~/mermaid/src/less/default/mermaid.less
Module parse failed: /Ruse/Nodrium/n-landing/node_modules/mermaid/src/less/default/mermaid.less Line 1: Unexpected token ILLEGAL
You may need an appropriate loader to handle this file type.
| @import "variables";
| @import "flow";
| @import "sequenceDiagram";
 @ ./~/mermaid/src ^\.\/.*$

WARNING in ./~/mermaid/src/less/default/gantt.less
Module parse failed: /Ruse/Nodrium/n-landing/node_modules/mermaid/src/less/default/gantt.less Line 2: Unexpected token .
You may need an appropriate loader to handle this file type.
| /** Section styling */
| .section {
|   stroke:none;
|   opacity:0.2;
 @ ./~/mermaid/src ^\.\/.*$

WARNING in ./~/mermaid/src/less/default/variables.less
Module parse failed: /Ruse/Nodrium/n-landing/node_modules/mermaid/src/less/default/variables.less Line 1: Unexpected token ILLEGAL
You may need an appropriate loader to handle this file type.
| @mainBkg: #ECECFF;
| @secondBkg: #ffffde;
| @lineColor: #333333;
 @ ./~/mermaid/src ^\.\/.*$

WARNING in ./~/mermaid/src/less/default/sequenceDiagram.less
Module parse failed: /Ruse/Nodrium/n-landing/node_modules/mermaid/src/less/default/sequenceDiagram.less Line 3: Unexpected token .
You may need an appropriate loader to handle this file type.
|
|
| .actor {
|   stroke: @actorBorder;
|   fill: @actorBkg;
 @ ./~/mermaid/src ^\.\/.*$

WARNING in ./~/mermaid/src/less/forest/classDiagram.less
Module parse failed: /Ruse/Nodrium/n-landing/node_modules/mermaid/src/less/forest/classDiagram.less Line 1: Unexpected identifier
You may need an appropriate loader to handle this file type.
| g.classGroup text {
|   fill:@nodeBorder;
|   stroke:none;
 @ ./~/mermaid/src ^\.\/.*$

WARNING in ./~/mermaid/src/less/forest/gantt.less
Module parse failed: /Ruse/Nodrium/n-landing/node_modules/mermaid/src/less/forest/gantt.less Line 2: Unexpected token .
You may need an appropriate loader to handle this file type.
| /** Section styling */
| .section {
|   stroke:none;
|   opacity:0.2;
 @ ./~/mermaid/src ^\.\/.*$

WARNING in ./~/mermaid/src/less/forest/mermaid.less
Module parse failed: /Ruse/Nodrium/n-landing/node_modules/mermaid/src/less/forest/mermaid.less Line 1: Unexpected token ILLEGAL
You may need an appropriate loader to handle this file type.
| @import "variables";
| @import "flow";
| @import "sequenceDiagram";
 @ ./~/mermaid/src ^\.\/.*$

WARNING in ./~/mermaid/src/less/forest/flow.less
Module parse failed: /Ruse/Nodrium/n-landing/node_modules/mermaid/src/less/forest/flow.less Line 1: Unexpected token .
You may need an appropriate loader to handle this file type.
| .mermaid .label {
|   font-family: 'trebuchet ms', verdana, arial;
| color:#333
 @ ./~/mermaid/src ^\.\/.*$

WARNING in ./~/mermaid/src/less/forest/variables.less
Module parse failed: /Ruse/Nodrium/n-landing/node_modules/mermaid/src/less/forest/variables.less Line 1: Unexpected token ILLEGAL
You may need an appropriate loader to handle this file type.
| @mainBkg: #cde498;
| @secondBkg: #cdffb2;
| @lineColor: #1a3318;
 @ ./~/mermaid/src ^\.\/.*$

WARNING in ./~/mermaid/src/less/forest/sequenceDiagram.less
Module parse failed: /Ruse/Nodrium/n-landing/node_modules/mermaid/src/less/forest/sequenceDiagram.less Line 3: Unexpected token .
You may need an appropriate loader to handle this file type.
|
|
| .actor {
|   stroke: @actorBorder;
|   fill: @actorBkg;
 @ ./~/mermaid/src ^\.\/.*$

WARNING in ./~/dagre-d3/lib/graphlib.js
Critical dependencies:
5:4-11 require function is used in a way in which dependencies cannot be statically extracted
 @ ./~/dagre-d3/lib/graphlib.js 5:4-11

WARNING in ./~/dagre-d3/lib/dagre.js
Critical dependencies:
5:4-11 require function is used in a way in which dependencies cannot be statically extracted
 @ ./~/dagre-d3/lib/dagre.js 5:4-11

WARNING in ./~/dagre-d3/lib/lodash.js
Critical dependencies:
5:4-11 require function is used in a way in which dependencies cannot be statically extracted
 @ ./~/dagre-d3/lib/lodash.js 5:4-11

ERROR in ./~/mermaid/src/diagrams/sequenceDiagram/sequenceDiagram.spec.js
Module not found: Error: Cannot resolve module 'proxyquire' in /Ruse/Nodrium/n-landing/node_modules/mermaid/src/diagrams/sequenceDiagram
 @ ./~/mermaid/src/diagrams/sequenceDiagram/sequenceDiagram.spec.js 1:17-38

If I require the dist min file:
Critical dependencies:
1:437-444 This seems to be a pre-built javascript file. Though this is possible, it's not recommended. Try to require the original source to get better results.
 @ ./~/mermaid/odist/mermaid.min.js 1:437-444

In package.json the entry point is pointing to src/mermaid.js
  "main": "src/mermaid.js",

This is the file that should be required. Hope that pointer helps and let me know how it goes.

I required that file directly as well. Result is the same as I wrote above.
Used node 5.4, Webpack 1.12.10

I'm also having a similar problem using webpack
Module not found: Error: Cannot resolve module 'proxyquire' in ./node_modules/mermaid/src/diagrams/sequenceDiagram

I have a fork that "mostly" works with webpack
https://github.com/mingfang/mermaid/commit/3e1638d9f49971a107d3dbd084f0c52c6421e65f
The key changes are
-removed proxyquire
-avoid names that conflicted with the official modules such as d3
There are still a few warnings but I was hoping this fork would inspire mermaid to become webpack compatible.

Is there any progress with this issue?

has the same issue, any progress?

so apparently this is fixed in webpack 2.0, but now i get a different error:
npm install webpack@beta

[~/dev/rikai/boted/editor]$ webpack
ts-loader: Using<EMAIL_ADDRESS>and /Users/dc/dev/rikai/boted/editor/client/tsconfig.json
Hash: 1be1a3b1eb2fdd341e37
Version: webpack 2.1.0-beta.21
Time: 9059ms
                      Asset     Size  Chunks             Chunk Names
    ./public/dist/bundle.js  4.34 MB       0  [emitted]  main
./public/dist/bundle.js.map   5.3 MB       0  [emitted]  main
    + 667 hidden modules

WARNING in ./~/mermaid/src/d3.js
5:4 Critical dependency: require function is used in a way in which dependencies cannot be statically extracted

WARNING in ./~/mermaid/src/diagrams/flowchart/dagre-d3.js
7:4 Critical dependency: require function is used in a way in which dependencies cannot be statically extracted

WARNING in ./~/dagre-d3/lib/graphlib.js
5:4 Critical dependency: require function is used in a way in which dependencies cannot be statically extracted

WARNING in ./~/dagre-d3/lib/dagre.js
5:4 Critical dependency: require function is used in a way in which dependencies cannot be statically extracted

WARNING in ./~/dagre-d3/lib/lodash.js
5:4 Critical dependency: require function is used in a way in which dependencies cannot be statically extracted

ERROR in ./~/mermaid/package.json
Module parse failed: /Users/dc/dev/rikai/boted/editor/node_modules/mermaid/package.json Unexpected token (2:9)
You may need an appropriate loader to handle this file type.
| {
|   "_args": [
|     [
|       {
 @ ./~/mermaid/src/mermaid.js 134:15-41
 @ ./~/react-mermaid/dist/react-mermaid.js
 @ ./client/src/components/StoryFlow.tsx
 @ ./client/src/components/TopicsPage.tsx
 @ ./client/src/App.tsx
 @ ./client/src/index.tsx

ERROR in ./~/mermaid/src/diagrams/example/parser/example.js
Module not found: Error: Can't resolve 'fs' in '/Users/dc/dev/rikai/boted/editor/node_modules/mermaid/src/diagrams/example/parser'
 @ ./~/mermaid/src/diagrams/example/parser/example.js 624:17-30
 @ ./~/mermaid/src/mermaidAPI.js
 @ ./~/mermaid/src/mermaid.js
 @ ./~/react-mermaid/dist/react-mermaid.js
 @ ./client/src/components/StoryFlow.tsx
 @ ./client/src/components/TopicsPage.tsx
 @ ./client/src/App.tsx
 @ ./client/src/index.tsx

ERROR in ./~/mermaid/src/diagrams/flowchart/parser/flow.js
Module not found: Error: Can't resolve 'fs' in '/Users/dc/dev/rikai/boted/editor/node_modules/mermaid/src/diagrams/flowchart/parser'
 @ ./~/mermaid/src/diagrams/flowchart/parser/flow.js 948:17-30
 @ ./~/mermaid/src/mermaidAPI.js
 @ ./~/mermaid/src/mermaid.js
 @ ./~/react-mermaid/dist/react-mermaid.js
 @ ./client/src/components/StoryFlow.tsx
 @ ./client/src/components/TopicsPage.tsx
 @ ./client/src/App.tsx
 @ ./client/src/index.tsx

ERROR in ./~/mermaid/src/diagrams/flowchart/parser/dot.js
Module not found: Error: Can't resolve 'fs' in '/Users/dc/dev/rikai/boted/editor/node_modules/mermaid/src/diagrams/flowchart/parser'
 @ ./~/mermaid/src/diagrams/flowchart/parser/dot.js 735:17-30
 @ ./~/mermaid/src/mermaidAPI.js
 @ ./~/mermaid/src/mermaid.js
 @ ./~/react-mermaid/dist/react-mermaid.js
 @ ./client/src/components/StoryFlow.tsx
 @ ./client/src/components/TopicsPage.tsx
 @ ./client/src/App.tsx
 @ ./client/src/index.tsx

ERROR in ./~/mermaid/src/diagrams/sequenceDiagram/parser/sequenceDiagram.js
Module not found: Error: Can't resolve 'fs' in '/Users/dc/dev/rikai/boted/editor/node_modules/mermaid/src/diagrams/sequenceDiagram/parser'
 @ ./~/mermaid/src/diagrams/sequenceDiagram/parser/sequenceDiagram.js 758:17-30
 @ ./~/mermaid/src/mermaidAPI.js
 @ ./~/mermaid/src/mermaid.js
 @ ./~/react-mermaid/dist/react-mermaid.js
 @ ./client/src/components/StoryFlow.tsx
 @ ./client/src/components/TopicsPage.tsx
 @ ./client/src/App.tsx
 @ ./client/src/index.tsx

ERROR in ./~/mermaid/src/diagrams/gantt/parser/gantt.js
Module not found: Error: Can't resolve 'fs' in '/Users/dc/dev/rikai/boted/editor/node_modules/mermaid/src/diagrams/gantt/parser'
 @ ./~/mermaid/src/diagrams/gantt/parser/gantt.js 650:17-30
 @ ./~/mermaid/src/mermaidAPI.js
 @ ./~/mermaid/src/mermaid.js
 @ ./~/react-mermaid/dist/react-mermaid.js
 @ ./client/src/components/StoryFlow.tsx
 @ ./client/src/components/TopicsPage.tsx
 @ ./client/src/App.tsx
 @ ./client/src/index.tsx

ERROR in ./~/mermaid/src/diagrams/classDiagram/parser/classDiagram.js
Module not found: Error: Can't resolve 'fs' in '/Users/dc/dev/rikai/boted/editor/node_modules/mermaid/src/diagrams/classDiagram/parser'
 @ ./~/mermaid/src/diagrams/classDiagram/parser/classDiagram.js 735:17-30
 @ ./~/mermaid/src/mermaidAPI.js
 @ ./~/mermaid/src/mermaid.js
 @ ./~/react-mermaid/dist/react-mermaid.js
 @ ./client/src/components/StoryFlow.tsx
 @ ./client/src/components/TopicsPage.tsx
 @ ./client/src/App.tsx
 @ ./client/src/index.tsx

I have the same problem with webpack 2.0 and don't know how to resolve it

@dcsan react-mermaid.js is using  "mermaid": "^0.5.1"
The wrapper is... very minimalistic.  I suggest using the mermaid version current in npm.

It seems to be a dragre-d3 problem - https://github.com/cpettitt/dagre-d3/issues/129
Still not solved.. :(

Why is the main in package.json pointing to src/mermaid.js as noted in https://github.com/knsv/mermaid/issues/277#issuecomment-171652293 ?
I have it working so far by:

Manually changing main to dist/mermaid.js in node_modules/mermaid/package.json
Manually removing all _token_stack: in the broken dist/mermaid.js file. See  https://github.com/zaach/jison/issues/351 for details.

I'll see if I can make a Pull Request to fix this soon.

Ok, so I have it working now.
Step 1: Require from dist not src
We need to fix require first, given the package.json is incorrectly pointing to src/mermaid.js instead of dist/mermaid.js. See https://github.com/knsv/mermaid/blob/master/package.json#L5

Before
After

require('mermaid');
require('mermaid/dist/mermaid.js');

Likewise, I have the CSS working with Webpack using require('mermaid/dist/mermaid.css') and css-loader.
Step 2: Workaround for Jison bug
After step 1 I receive an error Invalid labeled declaration about the _token_start: lines.
Unfortunately, a fix has yet to be applied to Jison. See https://github.com/zaach/jison/issues/351 and https://github.com/zaach/jison/pull/352
For now, we can provide a workaround.
Step 2.1: Create fixMermaid script
Create a file named scripts/fixMermaid.js with the following contents:
#!/usr/bin/env node
const { readFileSync, writeFileSync } = require('fs');
const path = require('path')
const mermaidPath = path.resolve(__dirname, '../node_modules/mermaid/dist/mermaid.js');

console.log(`Fixing Mermaid JS file at ${mermaidPath}`);
const contents = readFileSync(mermaidPath, 'utf8');

// Remove _token_stack label manually until fixed in jison:
// https://github.com/zaach/jison/issues/351
// https://github.com/zaach/jison/pull/352
const fixedContents = contents.split('_token_stack:').join('');

writeFileSync(mermaidPath, fixedContents, 'utf8');
console.log('Fixed Mermaid!');

Of course, you do not need to name it fixMermaid.js or place it within a directory named scripts. If you change this structure, please be sure to change the following steps, too.
Step 2.2: Run Mermaid after npm install has completed
Edit your package.json to include the postinstall script:
{
  "scripts": {
    "postinstall": "node scripts/fixMermaid.js"
  },
}

Step 3: Profit!
Now when you run npm install and then webpack, it should all work! 💥

Problem resolved and this is an official fix: https://github.com/knsv/mermaid/issues/361#issuecomment-306017512
In short: latest version of mermaid has no problem with webpack.

Please also check mermaid-webpack-demo.


feat: add geolines, hatch, outline, rhumbs, scalebar, shadow, square and tissot | docs: add examples

Add geolines, hatch, outline, rhumbs, scalebar, shadow, square and tissot. Also add few examples in vignette from https://observablehq.com/collection/@neocartocnrs/bertin

Thanks!


Update rotate_test.go to use v2 of project

Hi there.  I thought it would be nice for the rotate example to use v2 of the package.

Ha, oops, thanks!


Ethereum messenger contracts

Closes #1494, #1395
Didn't do any manual tests as we lack automated deployment support for Ethereum as another rollup.
This will be tackled in https://github.com/beamer-bridge/beamer/issues/1398

@GabrielBuragev could you please squash your fixup commits?


Fixes balenaFin v1.1 voltage range in docs

Change-type: patch
Signed-off-by: Alex Bucknall<EMAIL_ADDRESS>

fixes #88


Unexpected behavior in Births due to truncated rather than probabilistic equation

https://github.com/starsimhub/starsim/blob/main/starsim/demographics.py#L108
n_new = int(np.floor(sim.people.alive.count() * scaled_birth_prob))
Reproduce with simple example by toggling rel_birth between 33.33 and 33.34 (noting that default CBR is 30 per 1000)
import starsim as ss

people = ss.People(n_agents=1)

sim = ss.Sim(
    people=people,
    diseases=[], networks=[],
    demographics=[ss.Births(rel_birth=33.34))],
    n_years=5)

sim.run()
sim.plot()

I suppose the expected behavior would be a binomial process, but there may be some reason I'm unaware of (e.g. common random number handling) that this isn't implemented here currently.

Note that remnants of previous discussions about moving away from this deterministic approach to births are discussed in #404.

Closed by #724


bug: non-yellow color for carbonfox alacritty configuration file

Neovim version (nvim -v)
NVIM v0.10.0-dev-2050+gc4acbb87b
Operating system/version
Fedora Linux - 39
Describe the bug
The yellow hex code for the carbonfox alacritty config is not exactly yellow, for the normal, bright, and the dim sections the hex code for yellow color is as follows
[colors.normal]
yellow = "#08bdba"

[colors.bright]
yellow = "#2dc7c4"

[colors.dim]
yellow = "#07a19e"

the above hex codes are not exactly yellow but more on the blue side as seen below

have checked that the yellow hex codes for other themes for alacritty config are either shade of yellow or orange
with the above config the yellow color looks like blue(checked with the neofetch color palette), if this is the expected hex code then please close the issue
Steps To Reproduce

replace the current/default alacritty.toml code with carbonfox's config

Expected Behavior
the yellow color should be yellow
Repro
No response

This is expected, carbonfox was a port of oxocarbon when it was originally written in rust. This was ported so that others did not have to have rust installed to use the colorscheme.
You can see that in the screenshots that there is no yellow ex:

The colors come from the palette file:
https://github.com/EdenEast/nightfox.nvim/blob/1e650316680a777fb50e4ab35d82ecf32da485b8/lua/nightfox/palette/carbonfox.lua#L14-L23


[FEATURE] Show available exercises in VSC

Briefly describe the feature idea:
Add an Activity Bar button to show all available exercises & start a new one by clicking on them (instead of having to manually create a new file & paste the link in there).

Forgot to write this in the commit message, but everything is implemented now so this issue was closed in commit 408472c613cd87295bba08f2b9a41bcf16df0713.


[iOS] Initial support for state restoration with CentralManagerDelegate

Use CentralManagerDelegate instead of CentralManager events for handling BLE events on iOS. This will allow overrides of the default BleImplementation, so you can pass a RestorationIdentifier to CentralManager and keep all pending connections alive after the app was terminated due to memory pressure.
BleCentralManagerDelegate maps all the method overrides to the same events from the CentralManager to minimize code changes.
Example of BleImplementation override to pass a RestorationIdentifier:
protected override void InitializeNative()
{
    var cmOptions = new CBCentralInitOptions { RestoreIdentifier = BluetoothStateName };
    var cmDelegate = new BleCentralManagerDelegate();
    CentralManager = new CBCentralManager(cmDelegate, DispatchQueue.CurrentQueue, cmOptions);

    _centralManagerDelegate = cmDelegate;
    _centralManagerDelegate.UpdatedState += (s, e) => State = GetState();
}

Details on the iOS requirements for state restoration can be found here.

Hi @genriquez. Thank you for the contribution :) I will retarget the PR to our 2.0.0 branch as this is our current RC.

Thanks, I completely overlooked that branch. I see there are more usages of CentralManager events there. I'll update the PR with those changes as well.

Do we need to add something to the readme or documentation (advanced topic) regarding the state restoration?

My objective with this was to at least get support for iOS to relaunch my app in background when a pending device connection is resolved. To do so, you need to use a custom BleImplementation class, with the InitializeNative() implementation highlighted in the PR description. This would mean not being able to use the CrossBluetoothLE.Current property, so if you think this should be part of the docs, it should be listed as a workaround for now.
The ideal scenario would be to implement support for this within the plugin, including support for the WillRestoreState event, which should be used to hydrate the plugin instance with the restored device instances. I'm currently not using that event for anything in my app, so I'm not 100% sure what kind of work needs to be done there. More info on the WillRestoreState event here.

@genriquez Thanks for the update, I agree that we need a platform specific method for configuration.
I think it's a good idea to add the suggested static BleImplementation.UseRestorationIdentifier(identifier). Maybe you can also update the Readme.md and add a new link to the Extended topics section with the explanations of how to use this ocnfiguration method.

Let me know if you need any more updates from my side.

Hi Genriquez
I implemented the Bluetooth background  mode on ios in the same manner as you done, but I observed that background works fine one or at least two days after that the app is terminated. I use Xamarin form. Have you ever observed the same issue? It is worth mentioning that WillTerminated method is not called I only see that I do not get a local notification anymore.
I will appreciate for any your help.
Samo
Samo

Hi @samosim,
So the app stops working after 2 days? Just to be clear, we are talking about the app being terminated by iOS, not by the user, right?
We haven't seen any issues with this yet. You must make sure that the BLE connectivity logic does not depends on any UI implementation (like events from Xamarin Forms), since the app is relaunched in background, and the UI is not initialized until the user restores the application to the foreground.
This is just a way to keep BLE connection attempts alive after the app is killed due to memory pressure. If iOS decides to remove the app from memory, when a pending BLE connection is completed you should see an entry in the phone logs like this:
✝🕆🕇 Resurrecting zombie application "your.package.name" 🕇🕆✝
After this, the app executes the entry point in the AppDelegate, and from there you need to restart whatever process you were executing.

Ah, I see. I haven't used it with background scanning, only for direct connections to devices, so I don't have any specific experience for this use case. According to the documentation, state preservation covers scanning.
Are you seeing the Resurrecting zombie application message? If you see it only once, and after that the app stops working, then I would suspect that when the app is restored in background, the DidEnterBackground event is not triggered. In my use case we always fire a Task from the FinishedLaunching event, which attempts to connect to devices. Take into account that the event of the discovered device might be lost, since the current implementation just allows the app to be relaunched, and ignores the restored state.
Other than that, I would try to check the logs for what is happening. You can install some heavy apps and use them intensively to force iOS to terminate your app, so you might not need to wait for days for the app to stop responding. Since you can reproduce the issue without using the BLE plugin, you might want to consider posting this on Stackoverflow as well.

Thanks for your reply. If I am honest I do not know what does Resurrecting zombie application mean. Can you tell me a little bit more about this application?  It is interesting that my application works one or two days after that I do not get a local notification anymore. At the same time, the methods WillRestore and WillTerminate have not been triggered.
Can you tell me what happens when the application is restored in the background? I assume that WillRestore method should be called. I do no understand why DidEnterBackground method should be called. I will appreciate your help.
Thanks in advance.
Samo

The Resurrecting zombie application is a message shown in the logs when your app is re-launched in background after a change in your pending BLE tasks:

Our use case was just waiting for a specific device to be available so we can connect to it. Pending connections are kept alive by iOS after the app is terminated, and relaunches it when the device becomes available. When relaunched, we attempt to connect again to the device.
If the app when re-launched does not execute DidEnterBackground for your scenario, then the scanning process is never restarted. When the app is re-launched after being terminated, it is similar to the user opening it from scratch, but without any UI events/initialization, and with a time limit for it to perform all the required work. You need to "manually" resume all relevant tasks in this scenario (in your case, the scanning).

 Thanks again for your dedicated time and help.  I added in FinishedLaunching method the local notification and when the app is re-launched the local notification is shown. It means that the FinishedLauching method is triggered as you said. At this point I have still one question regarding re-launching procedure. According to your explanation, All relevant tasks which are responsible for scanning have to be called manually. But I do not know how FinishedLaunching method will recognize that these tasks have to be performed only when re-launching is caused by iOS. In other words, how I can separate the code which has to be executed only in the case when the iOS re-launches the application and not user opens the application. In both cases, the FinishedLaunching method is called.
Thanks in advance and happy holidays.
Samo

I'm afraid this is as far as my knowledge goes. We implemented this after we came across memory pressure scenarios in our tests, and noticed that there is support from iOS to keep things running, and the plugin didn't implement the feature yet. According to the documentation it should work, although I read in some forums that you may need to scan with a specific service UUID filter for it to be persisted.


Use EncodeUri() if part of the URL path or EncodeUriComponent() if used as a URL parameter

https://github.com/criteo/gtm-criteo-loader/blob/436584fccebe8b5b15bc6b99e5d00a5e56c39e0e/template.tpl#L153
When reviewing your template we've noticed that it is using parameters to build a url. It's a best practice to use EncodeUri() if part of the URL path or EncodeUriComponent() if used as a URL parameter.

Very good point indeed, thanks for flagging.
Fixed with commit 5d358a13fc68caad41c1ddef2baa1163fe5c4989.


Insert replace adoption is painful

Testing https://github.com/microsoft/vscode/issues/93754
I tried to adopt 6.2.0-next.1 in the JSON language server and it turned out to be quite painful

CompletionItem is no longer compatible to the previous version as the type of textEdit has changed
(a) Passing a CompletionItem to resolveCompletionItem of the old, not-yet adopted version of the JSON language service doesn't compile
(b) If I update the json-language-service with the new API, I break old, not-yet adopted users.

Ideally the change would be a new optional property.
I would suggest CompletionItem.insertReplaceTextEdit

The change is compatible inside the protocol itself. I do see that this is breaking on the level of the API when a diagnostic flows back even if no adoption has been done.
Instead of adding another property, which IMO makes things more confusing, I am in favor of simple raising the version number to 7.0.0 as we always do when these changes happen.

A new version would be correct, but will ripple through my server and services. All that just for a small feature.
Why not CompletionItem.insertReplaceTextEdit or CompletionItem.textEdit2 ?
It's also possible to do this:
CompletionItem.textEdit? : TextEdit | CompletionItemTextEdit;
CompletionItemTextEdit {
newText: string, range: Range, insertRange?: Range, replaceRange?: Range
}
CompletionItemTextEdit is compatible with TextEdit (range needs to stay and is duplicate info)
That way I can have my service work with old and new clients.

But I basically raise the major client / server version number with every protocol version. So I don't think that this is much different than moving from 3.14 to 3.15. The new feature can't go into a 3.15.x protocol version anyways. It will go with all the other new feature (like call hierarchy or semantic coloring) in version 3.16
I am not a fan of  CompletionItem.insertReplaceTextEdit nor CompletionItem.textEdit2. And InsertReplaceTextEdit in its current form has the disadvantage that someone can create an edit with range, insertRange and replaceRange.
One possibility would be
InsertReplaceTextEdit {
    newText: string, range: Range, replaceRange?: range
}

But I am not sure if this makes things easier or harder to understand since we need to write more documentation around it.

Given this is a breaking API change, doesn't that mean the types version would have to go to 4.0?
InsertReplaceTextEdit {
    newText: string, range: Range, insertRange?: Range, replaceRange?: Range
}

we define that range is what the LS thinks should be the preferred range for the currrent proposal.
Depending on the situation, that can be equal to the insertRange or the replaceRange.
VSCode has a setting that says whether insert or replace is the default, so it will just use insertRange  or replaceRange if present and ignore the default range. If insertRange and  replaceRange are not set, it can fall back to the default range.
I think that's equally complicated than the proposed InsertReplaceTextEdit.
I personally have not used insert/replace with proposals unless in testing. It's IMO a small feature that I would rather skip than start a version ripple, which is a big hassle for every LSP API client.

Given this is a breaking API change, doesn't that mean the types version would have to go to 4.0

Yes, but after discussion around this I decided to version types & protocol using the LSP version number and signal any breakage through the LSP client and LSP server. The types and protocol package is hardly used outside of the two.
I have requests from other languages that would like to adopt the insert / replace feature. So IMO we shouldn't skip this. And as said it will got into 3.16 with a lot of other features which very likely will require increasing the version number to 7.x for the client and server anyways.

VSCode has a setting that says whether insert or replace is the default, so it will just use insertRange or replaceRange if present and ignore the default range. If insertRange and replaceRange are not set, it can fall back to the default range.

Good point. But brings us back to square one :-). Do we type things correctly or backwards compatible.

@aeschli is this still an issue for you. I am not very keen on changing this now.

In the meantime I adopted all my language services (I had no choice).

Thanks!! I changed the diagnostic code though to make it non breaking


Linked package paths are not resolved correctly in 6.0.0-rc.4

Versions
Angular CLI: 6.0.0-rc.4
Node: 9.9.0
OS: darwin x64
Angular: 6.0.0-rc.4
... animations, cli, common, compiler, compiler-cli, core, forms
... language-service, platform-browser, platform-browser-dynamic
... router

Package                           Version
-----------------------------------------------------------
@angular-devkit/architect         0.5.6
@angular-devkit/build-angular     0.5.6
@angular-devkit/build-optimizer   0.5.6
@angular-devkit/core              0.5.6
@angular-devkit/schematics        0.5.6
@ngtools/json-schema              1.1.0
@ngtools/webpack                  6.0.0-rc.4
@schematics/angular               0.5.6
@schematics/update                0.5.6
rxjs                              5.6.0-forward-compat.3
typescript                        2.7.2
webpack                           4.5.0

Repro steps

link some package to your Angular app, for example yarn link "@cleverdata/dmpkit"
ng serve

Observed behavior
ERROR in ../cleverdata-dmpkit-common-ui/src/http/index.ts
Module build failed: Error: /Users/akrasman/work/dmpkit/cleverdata-dmpkit-common-ui/src/http/index.ts is missing from the TypeScript compilation. Please make sure it is in your tsconfig via the 'files' or 'include' property.
    at AngularCompilerPlugin.getCompiledFile (/Users/akrasman/work/dmpkit/cleverdata-dmpkit-filemanager-ui/node_modules/@ngtools/webpack/src/angular_compiler_plugin.js:707:23)
    at plugin.done.then (/Users/akrasman/work/dmpkit/cleverdata-dmpkit-filemanager-ui/node_modules/@ngtools/webpack/src/loader.js:41:31)
    at <anonymous>

Desired behavior
Linked folders inside node_modules shouldn't crash build process like in<EMAIL_ADDRESS>with option --preserve-symlinks

I'm not sure how this is different from https://github.com/angular/angular-cli/issues/8284. It looks like you're trying to use some TS files inside your node_modules.
If you want the app to compile TS files you need to add them to the files or include property as the message says.
There is more information in https://github.com/angular/angular-cli/issues/8284#issuecomment-341417325.
If you think that's not the case, can you provide a simple reproduction please?

Marking this as nice to have until we have repro steps and can assess if this is required.

I'm not sure how this is different from #8284. It looks like you're trying to use some TS files inside your node_modules.

Seems like it's the same issue but the thing is that linked packages with TS files worked in CLI 1.7 and I didn't have to add node_modules/@cleverdata/dmpkit to include in tsconfig, I just used  --preserve-symlinks flag.
Will it be useful if I make a repo with 2 branches (CLI 1.7 and CLI 6.0.0-rc.4) for reproducing both cases?

@filipesilva, I've created a demo with repro steps.
As I told before, this case worked well in CLI 1.7.3 with --preserve-symlinks flag which disappeared in 6.0.0 for some  reason.

Well, I found out that --preserve-symlinks flag is still available for ng build command, what is more, my demo builds correctly when I use ng build --preserve-symlinks. Therefore, if we could return --preserve-symlinks for ng serve command it would resolve a problem.

@Iverson if your app needs --preserve-symlinks to build properly, then you should set it in your angular.json for it to always be used.
You can set it in this section:
      "architect": {
        "build": {
          "builder": "@angular-devkit/build-angular:browser",
          "options": {
            "preserveSymlinks": true

This way it will always be used, without needing to use the flag every time.

@filipesilva this option doesn't seem to be available in 6.0.0 with ng serve, although it still works when configured in angular.json. Any chance of bringing back the option in the cli?


add disclaimers to quizzes at course level

What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)

Feature (requested by users)

Please check if the PR fulfills these requirements

[ ] E2E Tests for the changes have been added  via Cypress
[ ] Meaningful rspec tests have been added
[ ] Docs have been added / updated
Linter

[ ] rubocop reports equal or less errors and warnings in total
[ ] yarn lint reports equal or less errors and warnings in total
[ ] coffeelint . reports equal or less errors and warnings in total
[ ] erblint . reports equal or less errors and warnings in total

What is the current behavior? (You can also link to an open issue here)

What is the new behavior (if this is a feature change)?

Quizzees that are associated to a course (not to a lecture) get a disclaimer that informs the students that the notation and material in these quizzes may differ slightly from the material they have had in their lecture.

Does this PR introduce a breaking change? (What changes might users need to make in their application due to this PR?)

Other information:

I think this is contained in test.notation.


POC: Add lazy resolving of command paths

Defer resolving of the actual command path to when the command is called, not when it's imported. This allows providing a custom PATH via _env to customize resolving of the command path.
Remove test case that only tested if the mocker works.
NOTE: this is just a proof of concept of how lazy resolving could work. See discussions in https://github.com/amoffat/sh/pull/602

I think this might have to go into the 2.0.0 branch instead of develop, since it changes the public behavior (though not the interface). If the 1.* users are relying on exceptions to happen on import, this will be unexpected. If you don't disagree, would you mind changing the destination branch to release/2.0.0 please?

Closing for now, but we can revisit in the future. Good work on the POC


debian won't start after windows 10 reboot

Your Windows build number: Microsoft Windows [Version 10.0.17763.615]

What's wrong / what should be happening instead: I installed debian did some programming for arduino uno (school requires us to use linux) and uploaded it. Then I shutdown my laptop and now when I start debian again nothing is showing. The "Debian GNU/linux" shell is opening but the only thin I see in blinking cursor.

Commands done (might not be the full list as I'm doing it from mind):
[account creation stuff]
usermod -G sudo [accountname]
sudo id -a [accountname]
[logout of debian]
sudo apt-get update && sudo apt-get upgrade
sudo apt-get install avr-libc gcc-avr gdb-avr binutils-avr avrdude make arduino-mk
sudo apt-get install git
mkdir src && cd src && mkdir -p opdracht1/blink
nano blink.c
[created a simple blink program]
nano makefile
[created a simple makefile]
sudo chmod 666 /dev/ttyS5
make upload

This seems like a duplicate of https://github.com/microsoft/WSL/issues/2352 or https://github.com/microsoft/WSL/issues/4055 so perhaps some of the comments there might help you.
Could you do a few things:

Run your distro and then query the state of lxssmanager by running sc query lxssmanager in CMD?
Check if your console is running in legacy mode by right clicking on the title of the Window -> Properties -> Options -> Use legacy console and then try turning that on and off.
Gather logs for us by following these instructions.

Thanks!

oops, totally forgot about this.
The issue resolved itself after a quick reboot of the windows computer. After that, the issue never came back.
I was able to replicate the issue again on a different computer, the same solution.


updated readme

@aloisbarreras @beckysteele

Current coverage is 93.25% (diff: 100%)

No coverage report found for master at c36db66.

Powered by Codecov. Last update c36db66...232a8ec


feat(api): Add factory (creation) ops

I have some general question regarding the ops mod that I think we should think through before diving deep into these functions

Should the be associated functions (ie. Array::zeros()) or just regular functions (ie. crate::ops::zeros()), or both?
Should we just forget about zeros() and zeros_device() for now? Maybe just do zeros() and provide a macro that allow variable number of arguments later?

I have some general question regarding the ops mod that I think we should think through before diving deep into these functions

Do we want to impl all ops and merge altogether or do it incrementally?

Should the be associated functions (ie. Array::zeros()) or just regular functions (ie. crate::ops::zeros()), or both? I think the debate here is that mlx itself doesn't make ops associated functions; however, rust primitives like i32 make functions like add, sub associated functions (well, technically through trait)

Should we just forget about zeros() and zeros_device() for now? Maybe just do zeros() and provide a macro that allow variable number of arguments later?

Should we make three versions of each function? Using zeros as an example
a. fn zeros_unchecked() -> Array - does not check the parameter at all. This might have to be unsafe so that the user should use it with caution
b. fn try_zeros() -> Result<Array, Error> - checks parameters, returns an error if parameters are not valid
c. fn zeros() -> Array - checks parameters, panics if not valid
The implementation would be like follows. zeros_unchecked simply wraps around the c binding; then try_zeros checks parameter and call zeros_unchecked; then zeros calls try_zeros but unwrap the result

I'm thinking of doing the ops in parts. This PR is for the factories then I'd make an issue listing the missing ones and we can tackle those in segments.

I think the Rust community is used to associated functions. Plus it's what most other languages python / swift do.

I was working on adding the device variant yesterday. So I'll still do that for these.

I need to think some more about this suggestion and try it out.. it feels like we're still trying to mitigate a lot of the class of issues a typed Array/Tensor API would get rid of and I continue being torn about the direction we're taking. I'll also check out torch-rs and other libs to see how they handle this.

... Plus it's what most other languages python / swift do.

I disagree on this though. numpy and mlx in python clearly doesn't do associated functions. For example
import numpy as np
import mlx.core as mx

a = np.zeros(5)
b = mx.zeros(5)

it feels like we're still trying to mitigate a lot of the class of issues a typed Array/Tensor API would get rid of and I continue being torn about the direction we're taking. I'll also check out torch-rs and other libs to see how they handle this.

I think this feels complicated simply because handling ffi and linear algebra ops are inherently complicated.
The idea about the three variants comes from that try_*/*_checked, and _unchecked are like the typical way of differentiating the hidden cost of assertions. For example, slice have three variants of split_at - split_at, split_at_checked, and split_at_unchecked
A typed array is not free of some of these problems either. One use case for these machine learning library is to load a model from somewhere else and run that model. You don't have any information regarding the type or shape about the tensor or operations at compile time at all. So the dynamic array is something that we have to implement anyway, and these problems won't just disappear.


Add show/hide toggle for secret variables

When we are creating collection/environment variables  that contain secrets , there should be a toggle to show/hide the values
Bruno version:- v0.10.2

@sanbhattdeep Yes, this is on the roadmap.
I imagine an eye icon next to the delete button to toggle the visibility of the value.
When hidden, the value will be masked.
@ajaishankar Need your feedback on the DSL implications of above feature.
Currently, we save envs like below.
vars {
   host: https://api.github.com
   ~token: secret
}

The ~ means the var is disabled. But now, we also need to store if a var is actually hidden in the UI.
I am thinking to add a new tag called as vars:hidden
vars: hidden {
  token: secret
}

@helloanoop sorry for the late reply...
Questions:

What is the purpose of a secret variable

Is it just to be masked in the UI?
Or is it to make sure it is not stored plaintext in source control

When a user adds a secret variable do we expect it to be available to other users
If the main goal is not to store secret variables in plaintext in source control, would it make sense to encrypt it?

In the DSL, we could store secret vars as follows.
vars {
   token: $secret$<encrypted value>
}

The above scheme would allow a team to just share a key with members instead of a .git ignored secret file.

@ajaishankar we want to mask it in the UI. We also don't want to check-in plain text secrets
So we have two options

Store the secret using a strong symmetric encryption (AES256), that can only be decoded after the users enters the right key. This key can be shared across users

The .env-name.secret.bru pattern where the secrets will not be checked in.

We could also do the best of the both worlds where secrets get stored in .secret.bru file
And a meta tag inside that optionally specify the encryption and the encryption algo. Ex:
environments/staging.secret.bru
meta {
   encrypted: true,
   algo: aes256
}

vars {
   token: 2yidjdhye735e6hshsg
}

I do like us to be as less opinionated as possible and give a wide variety options for people on how they want to manage the secrets.
@ajaishankar @inneon thoughts?

IMO the secret.bru might be unnecessary for vars... If we really want users to control the algorithm, similar to bcrypt hash we can simply store a secret var as
vars {
   token: $alg$<encrypted-value>
}

Not sure how vars specified (only) in a secret .git ignored file would work when another dev pulls the collection from git.

Not sure how vars specified (only) in a secret .git ignored file would work when another dev pulls the collection from git.

Let's say that a company has a strict policy of not checking in secrets in git. (even encrypted). The company might be using a centralised secret management to share passwords.
In that case, the .secret.bru file can be added in .gitignore so that devs dont accidentally don't checkin secret variables. The UI will automatically save any secret vars (based on a toggle icon in the UI) in the .secret file.
This was @inneon point in #122

token: $alg$encrypted-value

Nice, I like this simpler approach of specifying algo.

Understood the concept.
My only point was

I add a secret variable
Bruno stores it locally in .secret.bru which is git ignored
Another dev clones the collection
Bruno is not able to list the secret variable in the UI since it's in a git ignored file

if we have to get this to work then Bruno would have to save a secret variable as this.
staging.bru

vars {
  token: $secret$
}

staging.secret.bru

vars {
   token: actual-value
}

Exactly what yourself and @inneon suggested. Took me a while to understand 😄
There is no need for encryption in this approach. Let's avoid it...

To answer the DSL question, imo the following reads nice... There is this variable token whose value is a secret
vars {
  token: $secret$
}

Closing this!
The PR adding this feature has been merged and released in v1.12.3


[BUG]: TypeError: Cannot set property 'props' of undefined

Describe the bug
When trying to integrate Builder.io, we get a strange error
ERROR:  TypeError: Cannot set property 'props' of undefined
    at Component (/Users/---/Desktop/hydrogen-app/node_modules/react/cjs/react.development.js:334:14)

To Reproduce
I have put a reproduction here:

git repo
codesandbox

Steps to reproduce:

checkout the code in the git repo (or use the codesandbox link)
run yarn
run yarn dev
go to http://localhost:3000/landing/foo
observe the error message

The above repo is purely a result of yarn create hydrogen-app this morning, then doing yarn add @builder.io/react and then adding one file in src/pages/landing/[handle].server.jsx:
import {useQuery, useUrl} from '@shopify/hydrogen';
import {builder, BuilderComponent} from<EMAIL_ADDRESS>
builder.init('cda38653c81344cf8859bd15e4d8e30d');

export default function Page() {
  // TODO: not working, says not a function
  // const url = useUrl();

  const content = useQuery('landing-page', async () => {
    return await builder
      .get('page', {
        userAttributes: {
          urlPath:
            '/landing/foo' /* TODO: when working, this should be url.pathname */,
        },
      })
      .promise();
  });

  return !content ? (
    'Loading...'
  ) : (
    <BuilderComponent model="page" content={content} />
  );
}

Expected behaviour
Page can render without error
Screenshots
n/a
Additional context
Add any other context about the problem here. eg.

Hydrogen version: 0.10.1
Node version: 14
Device details: Macbook Pro (not m1)

Thanks @frandiox! That helps a lot. And thank you for dealing with my newness with RSC, I'm sure as more docs are produced I'll be be able to answer these things myself more
The next issue I have is not being able to render this content server side. Is it the case that a .client.jsx component cannot render server side at all? If my understanding is correct, perhaps I need to make the Builder SDK compatible with RSC as a shared component? And if so, do you know of any guidance online for this?
The SDK is easy to update on our side, if we can better understand what specifically is not compatible today and what is required to support what we want here
Huge thanks again, as I know many of these questions are not fully specific to Hydrogen. I'm happy to study up on my own on this stuff, just am not finding a lot out there so far but feel free to point me in the right direction if there are docs on this online that I've missed!

@steve8708 It will be released in 0.11 (next version) so you could subscribe to releases. It's already out in<EMAIL_ADDRESS>but I'm not sure how stable that release is 😅

Great, thanks @frandiox!


Idva6 430 bulk email sender in add association v2

Short description outlining key changes/additions
Integrate bulk email sender into addAssociation endpoint.
JIRA Ticket Number
IDVA6-430
Type of change

[ ] Bug fix
[x] New feature
[ ] Breaking change
[x] Infrastructure change

Pull request checklist

[x] I have added unit tests for new code that I have added
[x] I have added/updated functional tests where appropriate
[x] The code follows our coding standards

An exhaustive list of peer review checks can be read here

CI: Security warnings found!


Why does opening and closing a Dialog remove a style from the body?

In the parent component, I am modifying the document body with a couple of styles when the component mounts:
document.body.style.overflowX = "hidden";
document.body.style.width = "100%";

Under the parent component is the Dialog child component, and when I open and close the Dialog, the overflow style is strangely removed from body, while the width attribute remains. Why?

@ColinTS If you think that its a bug, please fill the template (with a reproduction), otherwise, I'm gonna assume that it's a support question.


Fix more issues with code tags in class reference

Use the param tag when referring to parameters (I left code tag that reference a dictionary key with the same name as a parameter)
Remove two attempts to reference members inside a code block
Remove an outdated reference to the global_class_list being inside project.godot

Thanks!


Error: S4cmd : An error occurred (InvalidArgument) when calling the UploadPart operation: Part number must be an integer between 1 and 10000, inclusive

Hi,
I am trying to upload a 560 GB file to s3 bucket and it's failing with below error.
[Exception] An error occurred (InvalidArgument) when calling the UploadPart operation: Part number must be an integer between 1 and 10000, inclusive
Exception in thread Thread-13:
Traceback (most recent call last):
  File "/usr/lib/python2.7/threading.py", line 801, in __bootstrap_inner
    self.run()
  File "/usr/local/bin/s4cmd.py", line 542, in run
    fail('[Exception] ', exc_info=e)
  File "/usr/local/bin/s4cmd.py", line 189, in fail
    raise RuntimeError(status)
RuntimeError: 1

[Exception] An error occurred (InvalidArgument) when calling the UploadPart operation: Part number must be an integer between 1 and 10000, inclusive
Exception in thread Thread-17:
Traceback (most recent call last):
  File "/usr/lib/python2.7/threading.py", line 801, in __bootstrap_inner
    self.run()
  File "/usr/local/bin/s4cmd.py", line 542, in run
    fail('[Exception] ', exc_info=e)
  File "/usr/local/bin/s4cmd.py", line 189, in fail
    raise RuntimeError(status)
RuntimeError: 1

since this ticket is old, I think I should comment that this appears to still be an issue (just occurred for me today)


Add GHA for package upload

Add a GitHub Action for automated GH package release and PyPI upload. See @knaaptime's example here in geosnap

Original PR: spatialucr/geosnap#221
Conda-forge discussion: spatialucr/geosnap#224

May also tie this into #28


Upgrading typedoc

Using ^ with 0. releases never upgrades to new ones → always prefer using >= instead.
And because of that, we were not able to upgrade typescript to the latest version 5.2.2.
Better even: I'd prefer to not have typedoc being used at all. → We have to manage what 3rd party/OSS tools we use, otherwise cap/dev exceeds all limits, getting ever more heavyweight.

Better even

Then I have great news! As the typedoc dep was an artefact of providing generated HTML docs, which we decided to not use in the end, I have removed the dependency altogether.


Multilang

@nyadla-sys in #12  you pointed me to a multilang bin file, however, both it and the gen file have 50257 words. It actually looks like it supposed to have 51864 (en) or 51865) multilang tokens, so I'm clearly doing something wrong, but I'm not sure what it is. Can you elucidate the issue?

Fixed in 849517e


New Stewards re-provision after existing claim is fulfilled

Setup

Successfully run through a full demo of https://github.com/deis/steward-demo-s3
Wait until the final job is complete
Do the helm install referenced in the README at https://github.com/deis/steward-demo-s3/tree/master/charts/s3-service-provider

Observation
New provisions succeed (and new s3 buckets are created), but the final credentials secret is not successfully created because it already existed. Logs:
18:27:44 DEBUG k8s.claim event_actions.go:58 processProvision for event map[plan-id:EAAD05D8-2E01-11E5-9184-FEFF819CDC9F claim-id:asdasd7234213 action:create status:failed instance-id:57f30fc2-fb09-4725-a7b3-4c89f9026c2d extra: service-id:98FF26D0-2E01-11E5-9184-FEFF819CDC9F status-description:secrets "s3-bucket-secret" already exists bind-id:17420032-d8be-49c9-9933-fc94ecbb2097 target-name:s3-bucket-secret]
18:27:44 DEBUG mode.cf rest_client.go:70 CF client making PUT request to http://username:password@invited-lynx-broker.steward.svc.cluster.local:3000/v2/service_instances/e9c8b044-2405-44a6-986e-36b8ce896faa
18:27:44 DEBUG k8s.claim loop.go:98 wrapper before update: map[action:create extra: target-name:s3-bucket-secret plan-id:EAAD05D8-2E01-11E5-9184-FEFF819CDC9F claim-id:asdasd7234213 instance-id:57f30fc2-fb09-4725-a7b3-4c89f9026c2d bind-id:17420032-d8be-49c9-9933-fc94ecbb2097 service-id:98FF26D0-2E01-11E5-9184-FEFF819CDC9F status:failed status-description:secrets "s3-bucket-secret" already exists] (resource 1384492)

Expected behavior
Claim has already succeeded and should have status: bound, so new stewards should not process it.

Since https://github.com/kubernetes-incubator/service-catalog/pull/31 removes claims from the architecture, this issue is no longer relevant; closing.


Fix EventLogLogger to include the logger name in the message

@davidfowl

Screen shot of how it looks? A beeline might be better

Sure, examples:

New line? sure..but should it say like
Logger: <logger-name-here>
<message-here>

or just
<logger-name-here>
<message-here>

Either way is totally fine.

That is, with a newline, but either format is fine.

<logger-name-here>
<message-here>

updated. @Eilon @davidfowl

:shipit:

commit d89a2abe6d4f0abe271f8b9d68ecc4dec4e4585d


remove unwanted message when changing terapheutic line

fix #495

Coverage remained the same at 60.513% when pulling ddf1b5f1628e3a097d34151414977a2371f72fb6 on Guimino:remove_unwantedMessage_when_changing_terapeutic_line into 058de2fb38d3131991fb51cf34636c8d9e025cea on esaude:master.


Switch localStorage to IDB in SW recommendations

R: @malchata @petele
https://developers.google.com/web/fundamentals/performance/optimizing-content-efficiency/client-hints/#client_hints_in_service_workers suggests using localStorage inside of a service worker, but it's actually not available there. IndexedDB should be used instead.

Whoops!
There were 4 warnings that will prevent this PR from being merged. Please take a look, and either fix, or provide a justification for why they can't be fixed.
WARNINGS
src/content/en/fundamentals/performance/optimizing-content-efficiency/client-hints/index.md#L264 - Common typo found: 'javascript' Should it be 'JavaScript'?
src/content/en/fundamentals/performance/optimizing-content-efficiency/client-hints/index.md#L589 - Common typo found: 'javascript' Should it be 'JavaScript'?
src/content/en/fundamentals/performance/optimizing-content-efficiency/client-hints/index.md#L624 - Common typo found: 'javascript' Should it be 'JavaScript'?
src/content/en/fundamentals/performance/optimizing-content-efficiency/client-hints/index.md#L7 - Line must be at most 100 characters

Thanks for catching this, @jeffposnick, it was clear that I was mistaken.
Can you add yourself at the bottom in the credits in alphabetical order?

Sure thing!

Whoops!
There were 4 warnings that will prevent this PR from being merged. Please take a look, and either fix, or provide a justification for why they can't be fixed.
WARNINGS
src/content/en/fundamentals/performance/optimizing-content-efficiency/client-hints/index.md#L264 - Common typo found: 'javascript' Should it be 'JavaScript'?
src/content/en/fundamentals/performance/optimizing-content-efficiency/client-hints/index.md#L589 - Common typo found: 'javascript' Should it be 'JavaScript'?
src/content/en/fundamentals/performance/optimizing-content-efficiency/client-hints/index.md#L624 - Common typo found: 'javascript' Should it be 'JavaScript'?
src/content/en/fundamentals/performance/optimizing-content-efficiency/client-hints/index.md#L7 - Line must be at most 100 characters

Whoops!
There were 4 warnings that will prevent this PR from being merged. Please take a look, and either fix, or provide a justification for why they can't be fixed.
WARNINGS
src/content/en/fundamentals/performance/optimizing-content-efficiency/client-hints/index.md#L264 - Common typo found: 'javascript' Should it be 'JavaScript'?
src/content/en/fundamentals/performance/optimizing-content-efficiency/client-hints/index.md#L589 - Common typo found: 'javascript' Should it be 'JavaScript'?
src/content/en/fundamentals/performance/optimizing-content-efficiency/client-hints/index.md#L624 - Common typo found: 'javascript' Should it be 'JavaScript'?
src/content/en/fundamentals/performance/optimizing-content-efficiency/client-hints/index.md#L7 - Line must be at most 100 characters

:tada: This has been pushed live to https://developers.google.com/web/


chore(master): release 2.8.3

:robot: I have created a release beep boop
2.8.3 (2024-12-06)
Dependencies

deps: update alpine docker tag to v3.21 (#114) (722aa47)

This PR was generated with Release Please. See documentation.

:robot: Created releases:

v2.8.3
:sunflower:


Check index DDL

What changes were proposed in this pull request?
Add DDL for index checking: check oindex on table
currently, only support checking OAP meta file's existence for a specified table
Output of the checking results:
for partition directory which has no .oap.meta file, output a row:
Meta file not found in partition: partition directory
How was this patch tested?
unit tests

LGTM

LGTM.

thank you @Moonlit-Sailor please continue to the index / data consistency checkings, and let's make it smaller PRs one by one.


#to_hash should use consistent key types

Given an entity:
#<MyEntity id=1 content={"lender"=>{"contact_person"=>{"name"=>""} } "borrowers"=>[{"member_name"=>{"first_name"=>""}}] }>
Calling to_hash will return a hash with a mixture of key types:
{:id=>1, :content={"lender"=>{"contact_person"=>{"name"=>""} } "borrowers"=>[{"member_name"=>{"first_name"=>""}}] }}
which causes access issues later on.
def to_hash
  self.class.schema.keys.each_with_object({}) do |key, result|
    result[key] = Hashify[self[key]]
  end
end

Having a look through the to_hash method implementation, it looks as though the key could be either a symbol or a string depending on what is defined in the entity. Is that right?
I'm wondering if to_hash should recursively symbolise keys (including in arrays) so we can work with a consistent type of key?

Could you show me how MyEntity definition looks like?

Sure, it looks like this:
class MyEntity < Dry::Types::Struct
  attribute :id, Types::Strict::Int
  attribute :client_id, Types::Strict::Int
  attribute :file_handler_id, Types::Strict::Int
  attribute :matter_number, Types::Strict::String
  attribute :type, Types::Strict::String
  attribute :status, Types::Strict::String
  attribute :created_at, Types::Strict::Time
  attribute :content, Types::Coercible::Hash
end

Since you define :content as a simple coercible hash you can't expect it to be coerced into a symbolized hash. This is actually the expected behavior. If you want it to coerce string keys to symbols you need to define it like that:
attribute :content, Types::Coercible::Hash.symbolized(
  # define all the keys here, including nested symbolized hashes
)

Oh nice :) No problems then. I will change my approach and close this issue.
Thanks!


Added SystemLocale to xComputer

Recreated Pull Request.
Creating a pull request to add SystemLocale option in xComputer. I understand that there is another Resource (SystemLocale in SystemLocaleDsc Module), but I think the Locale setting makes more sense in the xComputer resource.
I couldn't find a friendly way of implementing intellisense to help with the locales, so I hard-coded them into the schema.mof. I'm not overly attached to the barbaric approach.
Liam

This change is

Hi @TheFish92, I'm your friendly neighborhood Microsoft Pull Request Bot (You can call me MSBOT). Thanks for your contribution!
You've already signed the contribution license agreement. Thanks!
The agreement was validated by Microsoft and real humans are currently evaluating your PR.
TTYL, MSBOT;

@PlagueHO You should take a look at this

Hi @TheFish92 - thanks for submitting this. Thanks for the tag @kwirkykat .
@TheFish92 - it might be a good idea to raise an issue first for this and get some feedback from the community. If including this function in xComputerManagement makes more sense then we should move this function in here and deprecate SystemLocaleDsc, rather than maintaining two methods of setting it.
Would you be able to open an issue for this change?

No problem at all. Issue is raised. #50

:shipit:

@PlagueHO This PR is on hold until you sign off

@kwirkykat  - I think @LiamFisher92 was going to update xComputerManagement to HQRM before he merges the System Locale functionality in to this resource (I may have misunderstood though).
I don't think this PR should go in as is. The underlying functionality is great and I have no problem with it (except I still think the hard coded ValidateSet() is not right). I do think we need to get this resource to HQRM first and then add the System Locale setting in at that point as per @mgreenegit 's suggestion.
I'm still up for helping @LiamFisher92 to get this resource to HQRM and will have a bit more time free heading into the end of the year.

@PlagueHO As I said, I'm not overly attached to the ValidateSet. It does however raise an interesting feature request for MOF schema's, which is the ability to dynamically inject valid values at runtime. Having the list of possible locales appear in ISE is nice!
I've been crazy busy lately, and haven't had much free time. The only work I've been able to do it small stuff that is directly affecting my actual work. So I think us two chipping away at it throughout Christmas and new year is a good shout! 😄

I'm going to close this one because @ld0614's LanguageDsc module is going to replace SystemLocaleDsc and be incorporated into this resource module (once xComputerManagement -> ComputerManagementDsc). See this issue https://github.com/PowerShell/DscResources/issues/288


Add hidden escape sequence

This adds support for the hidden escape sequence \e[8m, which will
render the text as invisible.
This has also raised a few questions about the rendering of foreground
and background colors and their interaction with the different escape
sequences. Previously, Alacritty has oriented itself after URxvt, which
has some strange and unexpected behavior.
The new implementation of color inversion is modeled after XTerm, which
has a consistent pattern of always inverting the foreground and
background colors. This should hopefully lead to less confusion for the
user and a more consistent behavior.
A full matrix showcasing the new way Alacritty inverses text can be
found here:
https://i.imgur.com/d1XavG7.png
This fixes #1454 and fixes #1455.
@jwilm you've mentioned that things were implemented this way for a reason,
modeling Alacritty after URxvt and allowing transparency to work properly.
I'd be interested to hear what you think about the changes to color inversion,
I'd say this is a pretty clear improvement because it makes things a lot more
consistent.

Wow, nice work! I'm a bit conflicted on modelling after xterm vs urxvt. One one hand, xterm is the standard, but in practice, many use emulators like urxvt or those based on libvte. The debate is about whether to match an actual standard vs expected behavior.
Would you mind posting a few more screens? Specifically, it would be nice to see Alacritty, urxvt, xterm, and a libvte-based emulator like gnome-terminal all with transparency. If you don't have these setup, maybe don't worry about it since it would be a bit onerous.

Oh yeah sure, I'll post a few more screenshots for comparison.
I'd actually say XTerm's behavior here is a lot more coherent than URxvt's, which seems almost arbitrary at some points.

Okay, I've made a few more screenshots for comparison. I've fully configured Termite, which is VTE-based and it seems to match Alacritty and XTerm. The only difference is that it seems to support inverting the background to foreground and I'd actually say that Alacritty does something wrong here. Even though it should be unrelated to my changes, I'll take a look if there's an easy fix.
Here's the comparison:
Alacritty

Termite

URxvt

Rebased and confirmed to be working using the included script. Everything should still be good.