buildGoModule: use proxyVendor instead of runVend

Motivation for this change
proxyVendor provides the same functionality (with sightly worse performance) as runVend while also addressing another edge case (vendoring with case sensitivity problems). As there is currently only ~10 packages that use either of them there isn't much point in keeping both.
Things done

Built on platform(s)

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

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

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

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

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

[ ] Fits CONTRIBUTING.md.

This PR just flips the switch and can go straight to master, I'll do docs + cleanup in follow up PRs as it'll trigger a rebuild of all buildGoModule packages.

Some of these didn't even need runVend... I'll fix them on master so they can be dropped from this PR.

Some of these didn't even need runVend... I'll fix them on master so they can be dropped from this PR.

Draft as another runVend has been added on master.
I'll merge this in 24hrs, I'll make sure all packages are fixed then.

@ofborg eval

I'd like to note here that proxyVend = true didn't work as a "drop-in" replacement for runVend in case of a package I maintain (I get errors like cannot find package "." in:). I don't have the time or energy to debug this or why it's happpening, but for anyone else looking for a quick-and-dirty solution to get back the old behavior, just get the vend package somehow (e.g. pull an older nixpkgs revision) and then add
    overrideModAttrs = n: {
      postBuild = ''
        rm vendor -rf
        ${vend}/bin/vend
      '';
    };

to your buildGoModule.


fix(3.2): triple AbstractServerCallListener NPE

What is the purpose of the change
NPE bug fix
Brief changelog

response.getValue is null， onReturn(null) will throw Serialize triple response failed NPE
Verifying this change

Checklist

[x] Make sure there is a GitHub_issue field for the change (usually before you start working on it). Trivial changes like typos do not require a GitHub issue. Your pull request should address just this issue, without pulling in other changes - one PR resolves one issue.
[ ] Each commit in the pull request should have a meaningful subject line and body.
[ ] Write a pull request description that is detailed enough to understand what the pull request does, how, and why.
[ ] Check if is necessary to patch to Dubbo 3 if you are work on Dubbo 2.7
[ ] Write necessary unit-test to verify your logic correction, more mock a little better when cross module dependency exist. If the new feature or significant change is committed, please remember to add sample in dubbo samples project.
[ ] Add some description to dubbo-website project if you are requesting to add a feature.
[ ] GitHub Actions works fine on your own branch.
[ ] If this contribution is large, please follow the Software Donation Guide.

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 70.41%. Comparing base (00812ce) to head (54c2df4).

Additional details and impacted files
@@            Coverage Diff             @@
##              3.2   #14009      +/-   ##
==========================================
- Coverage   70.43%   70.41%   -0.02%
==========================================
  Files        1607     1607
  Lines       70074    70077       +3
  Branches    10100    10101       +1
==========================================
- Hits        49356    49346      -10
- Misses      16080    16090      +10
- Partials     4638     4641       +3

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

@icodening @EarthChen PTAL


Add instructions for stopping a host postgres instance

@andy-thomason How does this look to you?

Another alternative is to move the postgres server to a different port. I think @Kixiron has had trouble in the past with using his host server accidentally instead of the one in docker-compose.

Thanks! I hope that avoid further pitfalls.

cc @rust-lang/docs-rs , you'll have to update .env to point to port 15432 instead of the default 5432. See the change I made to .env.sample.


Request for fetching order status

Hello,
it would be great if you API would offer a route for fetching the order status, e.g. "in production", "dispatched", etc.
Suggestion:
Route:
GET /order-status?orderId=<orderId>
or
GET /order-status/<orderId>
Response:
{
  "order": "<placed | in production | dispatched | ... >",
  "payment": "<waiting for payment | paid ...>"
}

Thank you for issue. We will publish this functional tommorow.

Nice, thank you! :)

Example:
https://github.com/ceo-treatstock/apiv2/blob/master/examples/05_PlaceOrder.php
Code: $orderStatusRequest = ...

Thank you for the quick implementation!
Could you provide additional documentation for the different values for orderState, paymentState and attemptState ?
In our workbench I see orders that are "in production" having different values for attemptState, e.g. "printing" and "accepted". Similarly there are "paid" orders with different paymentState values.
Could you document which values there are and their respective meaning? Ideally how they correspond to what is seen in the workbench.
Thank you!

Hi. We have described base statuses: https://github.com/ceo-treatstock/apiv2/blob/master/models/responses/OrderStatusResponse.php

Thank you! :)


Adjust fila report according to the standard format

First this is to know whether of not MoH is comfortable with the current format. This knowledge acquisition is the high priority now


How to Customize Change File Suffix

.mjs - > .js
.cjs -> .cjs
or
.mjs - > ${name}.esm.js
.cjs - > ${name}.cjs.js
Because when I introduced the plugin with the test project, there was an error
Can't import the named export 'useRequestSign' from non EcmaScript module (only default export is available)                                    friendly-errors 13:15:54

Please consider using standard .mjs/.cjs extensions when possible. They are natively supported by node.


Working with xAssets

Changed to Monero plugin to work with xAssets, left function names same to the original from Monero WooCommerce plugin (need to test complications). Changed some table names to Haven. Not finished product yet. Needs some fine tuning.

Thanks. Can you merge our master into you fork and commit and push again? It will resolve the conflicts. I think it's only one commit.


Test web3signer in Gnosis network

Test instructions
You must have at least 2 Gnosis validators.
Install the web3signer gnosis and a client between Prysm and Teku. You must get the hash from the Github latest release "dot".
In the client use the checkpoint sync feature to be able to start validating in minutes.
The web3signer will listen only to one client, you must select the client to listen to requests from at config.
For a deeper test, you may find it useful to check out the metrics from grafana dashboards from the client, web3signer, and docker host. Furthermore, in web3signer config, you can set the logs to DEBUG and get more details about whats going on
Test report
With an editable unique comment report any errors and feedback you may find necessary.
Testers

@pablomendezroyo
@3alpha
@tropicar
@mgarciate

Migration test (Installation of the first prysm version + web3signer, having keys on a previous prysm installation)

No error in the installation of prysm and web3signer.
All my keys were added to the web3signer, and I could check it out in the web3signer UI.
The web3signer with the prysm client keeps attesting

No errors encountered on 2 of my machines

Done!


Support for LaunchDarkly's contexts upgrade

LaunchDarkly plans changes in a way they track monthly usage. They will start the changes from the 1st of April and switch from MAU (Monthly Active Users) to MCI (Monthly Context Instances). You can read more about it here: https://docs.launchdarkly.com/guides/flags/upgrading-contexts.
To use contexts we would have to bump launchdarkly-js-client-sdk to version 3.0.0. I'm not yet sure what would be involved in the addon to start supporting it but just wanted to flag it

It looks it should be as easy as setting an extra property to pass to identify() method:
let customProperties = {
 someKey: 'some-value'
};
let props = {
  key: user.id,
  kind: 'my-new-context',  // "user" by default
  anonymous: false,
  custom: customProps,
};

await identify(props);

I think no changes, besides bumping launchdarkly-js-client-sdk to version 3.0.0, would be needed.

Feel free to close it, or close when we have the SDK upgraded 👌

I validated it on our side and there's no breaking change with the addon as far as I can see so I merged it, it will be part of our new v3 release where we will drop some older ember/node versions.
I'll keep you posted, should be this week

Great stuff @SkoebaSteve 🙌  I'm not super familiar with internals here and probably don't use everything that is possible in this addon but do you think this code:
https://github.com/adopted-ember-addons/ember-launch-darkly/blob/8c06fac44d184abfa9cf29850de7ec9b95e85cac/addon/-sdk/context.js#L112
might be affected by a breaking change and should be tweaked?

LDClient.getUser has been replaced with LDClient.getContext.

@tniezurawski yep you're right, we actually were not relying on the user getter here ourselves but it breaks indeed:

I'll create a fix for this, thanks for spotting!


Add Uzumaki by Machine girl

Song Name
Uzumaki
Artist Name
Machine girl
Source
Youtube
Youtube Link
53ulHedroTk
Direct File Link
No response
Song ID
918276
Start Offset [ms]
-8300
Extra
Created from Auto Nong.
Created for level: 108929162
Downloaded: Yes

Accept

accept
El sáb, 31 de ago de 2024, 12:45 p. m., auto-nong[bot] <
@.***> escribió:

Thanks for contributing!
Someone will soon review your request.
Here is the JSON result for the reviewer:
{
"name": "Uzumaki",
"artist": "Machine girl",
"source": "youtube",
"startOffset": -8300,
"yt-id": "53ulHedroTk",
"songs": [
918276
]
}
To accept the request, a reviewer needs to write "accept".
—
Reply to this email directly, view it on GitHub
https://github.com/FlafyDev/auto-nong-indexes/issues/3507#issuecomment-2323012055,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/BK5UXETJHJPGLMUYFBLSNB3ZUIFMFAVCNFSM6AAAAABNOC4ZP2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGMRTGAYTEMBVGU
.
You are receiving this because you authored the thread.Message ID:
@.***>


Use sub-fields instead of dotted notation

Prior implementations of the metrics filter plugin used dotted field
names.  Elasticsearch does not allow field names to have dots, beginning
with version 2.0.
This PR changes the plugin behavior to be friendly with Elasticsearch 2.0
again by using sub-fields and removes examples with dots.
fixes #19

Overall code LGTM. Haven't tested.

Specs pass for me:
Finished in 0.385 seconds (files took 2.03 seconds to load)
19 examples, 0 failures

Let's call this version 3.0.0, after that, LGTM to merge.


Add exports field for node

While this library targets the browser, it is sometimes helpful to use
it in need for experiments.
For example: https://github.com/status-im/js-waku/pull/588

bors merge

bors merge


TypeError: Cannot read property 'authorization' of undefined

Would be nice to do a safe-check at this line if (request.headers[AUTH_HEADER]) since some requests don't support custom headers (websocket for example) so even though I have an extractor that matches my request, the headers extractor fails because there's no request.headers object present.

I'm not sure I understand the problem.  The provided extractors are just there to cover common cases, if you have a condition where one of the provided extractors doesn't do what you want it to you can simply write your own.
Are you trying to use multiple extractors together? Some code illustrating how you construct the strategy might help me to understand what you're trying to do.

@teckays does writing a custom extractor solve the problem?


fix: address clippy warnings

This commit is all about making clippy happy, and to a lesser extent, Jane.

@yaahallo: Thanks for your help! I think we can safety bump up the minimum rustc version from 1.26 to 1.34, if @hawkw is okay with that?

@davidbarsky I would strongly prefer that we continue to track tokio's minimum Rust version for everything except for the proc-macro crates, though I'm open to negotiation.

@davidbarsky also, if we do bump the minimum Rust version, we shouldn't bump it to 1.34; IIRC tokio's policy is that we should support at least the last six stable releases.

Nevermind, I've been informed that '_ was stabilized in 1.26. So this is fine.


chore: add tabs, expansion, and paginator to kitchen-sink

Hmm, the prerender task fails on Travis. Perhaps this has to do with the Angular version...

It's failing because tabs don't work with server-side rendering (there's a comment about it in the kitchen sink). #5348 will fix it.

@crisbeto Yeah, I had seen that tabs didn't work before (I wrote the comment), but when I ran this PR on my machine everything worked.


Slot not JSON serializable

Rasa Core version: 0.9.4
Python version: 3.5.2
Operating system (windows, osx, ...): Ubuntu
Issue: I'm storing a pandas dataframe in a slot, which fails when doing online learning (as it can't be serialized as JSON using json.dumps)
My suggestion to fix this is the following:

Add a method on the Slot class which serialize a slot in a minimal way. As an example, for TextSlot, we want to have something like Slot{"name": "any"} if the slot's feature is 1, or Slot{"name": null} if its feature is 0.
Use this method for serialization

This would fix this problem without changing too many things, and it'd reduce the size of the training sets generated by online training (which is typically boring when storing a big API result in a slot).
I can PR this if you think it's worth it.
Error stack:
Traceback (most recent call last):
  File "manage.py", line 15, in <module>
    execute_from_command_line(sys.argv)
  File "/usr/lib/python3.5/site-packages/django/core/management/__init__.py", line 371, in execute_from_command_line
    utility.execute()
  File "/usr/lib/python3.5/site-packages/django/core/management/__init__.py", line 365, in execute
    self.fetch_command(subcommand).run_from_argv(self.argv)
  File "/usr/lib/python3.5/site-packages/django/core/management/base.py", line 288, in run_from_argv
    self.execute(*args, **cmd_options)
  File "/usr/lib/python3.5/site-packages/django/core/management/base.py", line 335, in execute
    output = self.handle(*args, **options)
  File "/home/florent/Documents/project/code/chatbot/bot/management/commands/train.py", line 29, in handle
    online_training(options['regex'])
  File "/home/florent/Documents/project/code/chatbot/bot/train.py", line 89, in online_training
    **__create_core_training_args(epochs=5)
  File "/usr/lib/python3.5/site-packages/rasa_core/agent.py", line 300, in train_online
    input_channel)
  File "/usr/lib/python3.5/site-packages/rasa_core/policies/online_trainer.py", line 76, in run_online_training
    input_channel if input_channel else ConsoleInputChannel())
  File "/usr/lib/python3.5/site-packages/rasa_core/agent.py", line 160, in handle_channel
    processor.handle_channel(input_channel)
  File "/usr/lib/python3.5/site-packages/rasa_core/processor.py", line 61, in handle_channel
    input_channel.start_sync_listening(self.handle_message)
  File "/usr/lib/python3.5/site-packages/rasa_core/channels/console.py", line 52, in start_sync_listening
    self._record_messages(message_handler)
  File "/usr/lib/python3.5/site-packages/rasa_core/channels/console.py", line 45, in _record_messages
    self.sender_id))
  File "/usr/lib/python3.5/site-packages/rasa_core/processor.py", line 84, in handle_message
    self._predict_and_execute_next_action(message, tracker)
  File "/usr/lib/python3.5/site-packages/rasa_core/processor.py", line 258, in _predict_and_execute_next_action
    action = self._get_next_action(tracker)
  File "/usr/lib/python3.5/site-packages/rasa_core/processor.py", line 400, in _get_next_action
    idx = self.policy_ensemble.predict_next_action(tracker, self.domain)
  File "/usr/lib/python3.5/site-packages/rasa_core/policies/ensemble.py", line 88, in predict_next_action
    probabilities = self.probabilities_using_best_policy(tracker, domain)
  File "/usr/lib/python3.5/site-packages/rasa_core/policies/online_trainer.py", line 132, in probabilities_using_best_policy
    self.write_out_story(tracker)
  File "/usr/lib/python3.5/site-packages/rasa_core/policies/online_trainer.py", line 190, in write_out_story
    self.stories.append(tracker.export_stories())
  File "/usr/lib/python3.5/site-packages/rasa_core/trackers.py", line 319, in export_stories
    return story.as_story_string(flat=True)
  File "/usr/lib/python3.5/site-packages/rasa_core/training/structures.py", line 188, in as_story_string
    story_content += step.as_story_string(flat)
  File "/usr/lib/python3.5/site-packages/rasa_core/training/structures.py", line 118, in as_story_string
    converted = s.as_story_string()
  File "/usr/lib/python3.5/site-packages/rasa_core/events/__init__.py", line 360, in as_story_string
    props = json.dumps({self.key: self.value})
  File "/usr/lib/python3.5/json/__init__.py", line 230, in dumps
    return _default_encoder.encode(obj)
  File "/usr/lib/python3.5/json/encoder.py", line 198, in encode
    chunks = self.iterencode(o, _one_shot=True)
  File "/usr/lib/python3.5/json/encoder.py", line 256, in iterencode
    return _iterencode(o, 0)
  File "/usr/lib/python3.5/json/encoder.py", line 179, in default
    raise TypeError(repr(o) + " is not JSON serializable")

Any updates on this issue? I am having the same issue when defining a custom slot. In my case I don't ned a pandas df, but still I can't manage to serialize my slot when doing online training.

Thanks for raising this issue, @Ghostvv will get back to you about it soon.

I would suggest to set value to smth serializable, but store your pandas dataframe in different attribute of your custom slot and use this attribute in your custom action.

Hum, nice idea, didn't think of it. And actually, my first proposition would have worked as it isn't the slot serialization that raise exception but the SlotSet serialization (at least in my case).
If I develop a bit your proposition. We have two choices (without changing rasa core implementation). Either we stop to use SlotSet and directly set our slot's values (both with a serialized and raw value, as you say). But in this case this won't appear in the exported stories.
Or, we keep using SlotSet. But, in this case it isn't that easy because it directly sets the value field of our slot (the following code is the Tracker method called when SlotSet is applied).
    def _set_slot(self, key, value):
        # type: (Text, Any) -> None
        """Set the value of a slot if that slot exists."""

        if key in self.slots:
            self.slots[key].value = value
        else:
            logger.error("Tried to set non existent slot '{}'. Make sure you "
                         "added all your slots to your domain file."
                         "".format(key))

So what we can do (i.e. without changing rasa core's code) is:

In our custom action, the one that returns this SlotSet, we should actually set a serializable representation of our pandas (or other non-serialisable stuff). Which would be most likely a dict-based representation.
Then, actions that use it should convert it back to our original representation
(Optionally) Our custom action could cache the recovered representation (which could be done consistently by using python properties)

This would fix the exception (at least in my case) without too many changes from our (my) side (and no one from Rasa Core side).
However, it does not change the issue of having looooong training files when using online training (as the serialization would certainly be big as well). I don't really have a proposition to do it as we are speaking of event serialization and not slot serialization. Furthermore, SlotSet event does not have a lot of contextual information (like the domain) in order to call a custom method.

I agree with the training files, we need to find a solution for that. I don't think though that the serialisation of data formats should be in core though, as there are just to many of them.

An idea could be to create a SetSlot by Tracker's method rather than directly using SetSlot constructor. This new method would handle the linking between a SetSlot event and the slot itself.
Then, define a static/class method for the slot which handles the data transformation.
This would imply that a direct call to SlotSet constructor should be deprecated but, imo, the implementation can be backward-compatible.


Clean task fix (bug 63914)

Description
Clean command did not remove the test.jar file.
This bug was mentioned in Bugzilla https://bz.apache.org/bugzilla/show_bug.cgi?id=63914
Types of changes

Bug fix (non-breaking change which fixes an issue)

Checklist:

[x] My code follows the code style of this project.
[ ] I have updated the documentation accordingly.

@paivanjerry , thanks I think it is valuable, however, I wonder if we want to avoid copying the jars right into /lib to avoid accidental leftovers like in the current issue.
See https://bz.apache.org/bugzilla/show_bug.cgi?id=65237
@FSchumacher , @pmouawad , what do you think?


'include_cached` error even after following documentation

I installed the theme by following Gem based method. Everything runs perfectly on local machine.
But error message from github on page build:
The page build failed for the `master` branch with the following error:

The tag `include_cached` on line 15 in `/_layouts/default.html` is not a recognized Liquid tag. For more information, see https://docs.github.com/github/working-with-github-pages/troubleshooting-jekyll-build-errors-for-github-pages-sites#unknown-tag-error.

Gemfile:
gem "minimal-mistakes-jekyll"
gem "jekyll-include-cache"

_config.yml snippet, the complete file can be accessed at this link
url: "https://riyadhrazzaq.github.io"
baseurl: "/blog"
repository: "riyadhrazzaq/blog"

plugins:
  - jekyll-include-cache
  - jekyll-paginate
  - jekyll-sitemap

I haven't change any _includes or _layouts file. Thanks in advance.

Gem version of the theme doesn’t work with GitHub Pages.
Follow the remote theme method instead. You also don’t need the includes, layouts, and Sass files in your repo.
https://mmistakes.github.io/minimal-mistakes/docs/quick-start-guide/#remote-theme-method

used the starter repo, everything works now. thank you.


ModuleNotFoundError when running the demo

Hi, I am attempting to reproduce the demo provided in your GitHub repository, and I encountered some errors related to the modules.
When I run the ConcentricCricles.ipynb Lilium.ipynb LogSpiral.ipynb, I receive the following error message:
ModuleNotFoundError: No module named 'sparse_matrices'
When I run the ForwardDesign.ipynb，I receive the following error message:
ModuleNotFoundError: No module named 'wall_generation'
Where can I find these modules? Or did I do something wrong?
Thank you very much!

These modules are part of the Python bindings built from the Inflatables/MeshFEM C++ codebase. You should make sure the code built without errors and that the Python bindings are being built for the version of Python you're actually using. You'll know you have a version mismatch if these import errors persist despite the build successfully generating compiled modules with paths like python/wall_generation.cpython-39-darwin.so (the suffix is platform/version dependent).
The correct Python version should automatically be selected if you're using a virtual environment as recommended in the README. But this is for some reason broken, you can manually override the selection by setting PYTHON_EXECUTABLE as documented here.

It works now! Thank you!


Implement the Recursive Least Square algorithm

This PR implements the recursive least square filter described in Lennart Ljung - System Identification: Theory for the User (1999, Prentice Hall), Chapter 11, Section 2
In details:

a new component called Estimators has been added to the repository
The RLS algorithm has been implemented
A Simple test has been implemented
The readme has been updated
The changelog has been updated

The test implemented in the component generates the following result. The expected value of the parameters converges to the ground truth and the confidence region tends to zero.

If everybody agrees I will merge the PR. Don't hesitate so say no.
I will wait for the :+1:

I did nto review the code. If @prashanthr05 or @traversaro did, it is fine for me.

Since @prashanthr05 approved the PR, I think we can merge. if in the future we realize that the interface is not versatile enough we will open a new PR.


Add sha/asm/keccak1600-avx512vl.pl.

I'd say that commit message to<PHONE_NUMBER>2dc5ff5570f02d6b92eeb02a310e18 is sufficient. If concern is that blog leaves OpenSSL in "bad light," then it would be more appropriate to leave comment on the blog (or ask author to update), because nobody will cross-reference it with our git log. I for one don't see that it's necessary, because it does say that it's development version, which implies that problem can be addressed upon release. And it already is. [Modulo fact that capability masking might need to be extended even to Skylake-X successor, basically till Intel resolves the problem.]

You're right.  I posted a note on their blog.  I still approve this PR. :)


Cleanup: delete 152.patch file

This file was unused since https://github.com/conda-forge/pygad-feedstock/commit/4c1d48e988d95adfaa6b8bf4f46764a86c317410, but I forgot to remove it.
Checklist

[x] Used a personal fork of the feedstock to propose changes
[ ] Bumped the build number (if the version is unchanged)
[ ] Reset the build number to 0 (if the version changed)
[x] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[x] Ensured the license file is being packaged.

@conda-forge-admin, please rerender


Invalid Google Maps API Key. Please follow instructions to set API key before login.

Can't find these instructions. What am I missing?

https://github.com/mchristopher/PokemonGo-DesktopMap/wiki/Google-Maps-API:-a-brief-guide-to-your-own-key

You are awesome. Map is awesome.
On Jul 27, 2016 10:16 AM, "PhantonQuad"<EMAIL_ADDRESS>wrote:

https://github.com/mchristopher/PokemonGo-DesktopMap/wiki/Google-Maps-API:-a-brief-guide-to-your-own-key
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/mchristopher/PokemonGo-DesktopMap/issues/315#issuecomment-235598779,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ATueo6llXx35AH8vQ49ekAhOrE-bEB1Gks5qZ2hVgaJpZM4JWPCK
.

@jnewt345 if your problme is solved please close this issue


double loading of HMR script

Seems to happen with version @3.3.1
https://github.com/webpack/webpack-dev-server/issues/1837


Support

how do I access a human account as i would like to test this

It's not really suggested to do so but if you really do want to do so then log in to your account on a web browser and find it in the local storage, I won't say more because I really don't suggest you doing so cause it's against the Discord TOS

Since this is against tos (and I mean the answer has basically already been given by the wonderful dcrime) I'm going to close this issue. Feel free to make another if you need some help with something else!


Only one dc:creator being added to book

Added a test to verify that the bug described is not coming from epub-creator.


Audit code for use of global slots

The replayer uses the global_slot field in the archive db, denoting the slot since the last hard fork, where it should probably be using global_slot_since_genesis, the slot since network launch.
Fix that code, and audit other code to make sure the correct slot value is being used.

For the replayer it may not always make sense to apply transactions across hard forks. For example, when the ledger changes in one of the hard forks, passing the genesis ledger at launch as input may not result in the latest ledger in the archive node

The replayer can start with an arbitrary staged ledger, not just the genesis ledger. If it never replays across hard forks, then using the current slot is OK.
What I want to be sure of is that the slot it uses is unique along the canonical chain. The slot since genesis gives you that.
In the current replayer, you can specify a start slot. If that means a current slot, that's ambiguous. With the slot since genesis, it's unambiguous.

Can we combine both fields into a single record, to make us be more thoughtful about this? Field names like since_genesis and since_last_hard_fork_for_consensus might hopefully make it easier to tell which is the intended for most uses.

I think renaming current_slot to global_slot_since_last_hard_fork is enough to avoid confusion.
For the archive db, that means a migration script to rename the column, and a software update to access the column.

Where in the code do we use a global slot that denotes the slot since the last hard fork?

For the hard fork, see this comment: https://github.com/MinaProtocol/mina/pull/9511#issuecomment-924000192

Also: the replayer should be using the since-genesis slot of the parent block when applying transactions, not the slot of the block in which the transaction occurs.


Ability to block pattern/list of discord users to ignore for bridge transmission

This would be useful to for example block other bots that send walls of text for output so they don't make floods in an IRC channel resulting in ban/kick/timeout etc.

would come in really handy. maybe a whitelist / blacklist and ability to block messages from one side completely, to use it as irc-bot relay only.

+1 this would be very useful in ignoring spammy bots. I might work on this if I get a bit of time.


[Flaky Test] segfault in tests/python/contrib/test_ethosu/test_codegen.py::test_mean

Branch/PR Failing
https://github.com/apache/tvm/commit/534412896e6d39ee4f830d63370d02e8e5f09050
Jenkins Link
https://ci.tlcpack.ai/blue/organizations/jenkins/tvm/detail/main/4188/pipeline
Flakiness
We've been tracking other ethos-u flakiness in https://github.com/apache/tvm/issues/12511, but I'm not sure if this occurrence is actually related to ethos-u.

An update on that issue of random codegen tests intermittently segfaulting in CI that has been causing problems for a while now - it happens during a call to Vela and Vela folks have tracked it down now and the fix will be available in their next release. So when we upgrade the Docker with the new version, it should go away and we can re-enable the tests.

closing this as the version of Vela was updated and the test was re-enabled


build: SPM temp support changes for support on MacOS

This PR is for temporary support for building with SPM instead of Cocoapods.
This change is only going to be merged until the plugin is migrated to use a shared /darwin directory for both iOS and macOS.
PR created on the request from another PR for iOS.
Reference PR : https://github.com/juliansteenbakker/mobile_scanner/pull/1155

@Xa69 Small question, according to Flutter's migration guide, it says "Flutter falls back to CocoaPods for dependencies that do not support Swift Package Manager yet."
Does this mean that, when SPM support is disabled for the Flutter CLI / this plugin, the Cocoapods version still works (because the sources are now just in a different directory, but otherwise unchanged?)
If it still works for Cocoapods, we can go ahead and land SPM support for MacOS already. It will only be widely available when SPM support is available on stable anyway.

@navaronbracke yes it will work even if the SPM config flag is disabled, I’ve observed it in the build step it will install cocoapods dependencies if the flag "—no-enable-swift-package-manager” is set. [This flag will set it back to use Cocoapods instead of SPM]

@navaronbracke Looks like only people with ‘Write’ access to the main repository can merge this PR, I don’t have an option to complete it.
@juliansteenbakker If possible, please review the PR and merge the code please.

As adding SPM support won't affect our users that are using Cocoapods, per the note in the migration guide, I'll merge this already.


Add more sophisticated logging support

For now we just wrap around the OkHttp logging interceptor. It has the following problems today:

No easy connection to other popular Java loggers
No trivial support for file logging, or any other streams
Direct dependency on OkHttp can result in unexpected client-side breaking changes

This is making bug reporting from customers difficult.
Tasks

[ ] Wrap around the log levels to avoid OkHttp import in client-side code
[ ] Allow connecting to external loggers and add tests
[ ] Allow logging to files and streams

Assigned myself for Java runtime GA

slf4j provided all the functionalities we needed.


Pad array elements to have nice table layouts.

For tables of constants such as:
static table: [i8; 256] = [
  0,  1,  6,  6,  21, 21, 21, 21, 21, 21, 21, 21, 21, 21, 21, 21, X,  6,  6, 21, 21, 21, 21, 21, 21, 21, 21, 21, 21, 21, 21, 21, 6,  6,  21, 21, 21, 21,
];

we currently emit:
static table: [i8; 256] = [
    0, 1, 6, 6, 21, 21, 21, 21, 21, 21, 21, 21, 21, 21, 21, 21, X, 6, 6, 21, 21, 21, 21, 21, 21,
    21, 21, 21, 21, 21, 21, 21, 6, 6, 21, 21, 21, 21,
];

Ideally, this should look more like:
static table: [i8; 256] = [
     0,  1,  6,  6, 21, 21, 21, 21, 21, 21, 21, 21, 21, 21, 21, 21,  X,  6,  6, 21, 21, 21, 21, 21, 21,
    21, 21, 21, 21, 21, 21, 21,  6,  6, 21, 21, 21, 21,
];

Bonus points if we omit the prefix space for elements that don't have an entry below them ('X' above.)
This may not work for all arrays, so perhaps we can have annotations for tables of small constants.

Hack: If you turn off a clippy lint you can fix this by having trailing _ on your numbers.


PIN-5661 - POST /consumer/delegations

[x] manual tests
[x] error mapping + improve the bad request mappings and map to more meaningful errors? Also for producer delegations
[ ] Is the IPA tenant check needed also in case of consumer delegations?

Tests
Automated tests pass ✅

Manual tests
Success ✅

Readmodel insert works ✅

Smoke testing some errors

After the review and merge, maybe it's worth porting some of these changes to the develop branch (e.g., fixes to tests, API specs, etc.)


fix: predict for TemplateExpressions

Pull Request Test Coverage Report for Build<PHONE_NUMBER>6
Warning: This coverage report may be inaccurate.
This pull request's base commit is no longer the HEAD commit of its target branch. This means it includes changes from outside the original pull request, including, potentially, unrelated coverage changes.

For more information on this, see Tracking coverage changes with pull request builds.
To avoid this issue with future PRs, see these Recommended CI Configurations.
For a quick fix, rebase this PR at GitHub. Your next report should be accurate.

Details

2 of 2 (100.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.003%) to 95.47%

Totals

Change from base Build<PHONE_NUMBER>6:
0.003%

Covered Lines:
3119

Relevant Lines:
3267

💛  - Coveralls


Enable multiplex feature flag for demo, training, pentest

Enable the multiplex feature flag for the following environments:

demo
training
pentest

Reviewed during backlog grooming on 10/6 and determined that this issue is still needed.

Closing this; instead we will:

Remove the feature flag entirely
Figure out why multiplex devices aren't selectable in demo or training


Can't create a CosmosDB account (any type)

Repro steps:
Action: cosmosDB.createAccount
Error type: object
Error Message: {"key":"1","value":{"_creator":null,"_nextState":null,"_state":{"name":"error","done":null,"then":null},"_value":{},"_listeners":null,"_isException":false,"_errorId":11}}
Version: 0.6.1-alpha
OS: win32

Works now after rebuild.


ERROR 403 FORBIDDEN ConfigError

This a speedtest-cli error due to recent changes that may be due to inavailability and lack of response from speedtest.net
Solution
Try again later or wait for a few moments.

This appears only when you're not connected to the internet, so it should be understood. I will be updating the app with an exception statement.


Add Restart Button for containers

I found it handy to have a restart button for containers that I can push from a dashboard.

moved the button to asyncio based on the work in PR #140

I am happy to merge this one, but can you put the default too disable for this button feature? I think most users will not prefer it, if even more entities are added to HA.
So change:
vol.Optional(CONF_BUTTONENABLED, default=True): vol.Any(
to:
vol.Optional(CONF_BUTTONENABLED, default=False): vol.Any(

my use case is to have an auto entities card that auto-populates with the reboot buttons for all containers, that way as i add/remove containers the reboot button automatically shows up and i don't have to manage it.
maybe this can be added as a configuration option, so the button is disabled by default but can be enabled by default if the user choses it, but that might be to big of a code change. Can probably achieve that with an automation of sorts.

I just merged the change in the master.


MyCarePlanner 2.4.1 - remove SDS from third-party endpoint dropdown

In MyCarePlanner 2.4.1 (and earlier versions), the SDS is represented in the third-party dropdown list:

Users should not be given the opportunity to try to connect directly to the SDS in this manner.

If there's no ClientID, don't add SDS option to the dropdown.


Editor Context Menu Modification

Type: Feature Request
Please move CUT as far away from copy and paste as possible, or add confirmation code for CUT operations. It's close proximity to copy has caused me numerous problems in the past (code is unintentionally deleted without warning).
VS Code version: Code 1.95.3 (f1a4fb101478ce6ec82fe9627c43efbf9e98c813, 2024-11-13T14:50:04.152Z)
OS version: Windows_NT x64 10.0.22631
Modes:

Duplicate of https://github.com/microsoft/vscode/issues/9285


Fix minor typo in services.md

Proposed changes

Fix a minor typo

@gbarr01 I think you've read the diff a little too fast :)

Ha. You're right. Sorry about that.


Invalid Field Access

I'm trying to setup luxe, but the features/draw flow project won't build.
sudo haxelib run flow compile
flow / 1.0.0-alpha.2 (node.js v5.12.0)
flow / target is linux ( arch 64 )
flow / compile only
flow / haxe version 3.1.3

flow / build - luxe.draw 1.0.0 for linux
flow / build - running haxe ...
Error: Invalid field access : __s

Any ideas?

Currently haxe 3.2.1/3.2.0 is the stable release, and known to work great.
You wouldn't happen to be running on the 3.3 RC preview builds of haxe? (haxe -version)

That'd make sense; I have 3.1.3.
It was the default version in NixOs. I'll see if I can upgrade.

I got haxe upgraded to 3.2; now I'm getting this bug.
flow / 1.0.0-alpha.2 (node.js v5.12.0)
flow / target is linux ( arch 64 )
flow / build only
flow / haxe version 3.2.0

flow / build - luxe.draw 1.0.0 for linux
flow / build - running haxe ...
--macro:1: character 0 : Could not parse `snow.Set.main("luxe.Engine")--macro snow.Set.ident("co
m.luxeengine.testdraw")--macro snow.Set.config("config.json")`                                  --macro:1: character 0 : Missing ;

Seems like snow.hxml didn't have new lines before each --macro. After adding those and running haxe bin/linux64.build/blind.hxml, it seems to build fine. Not sure where I can make flow do that by default.

That's the strangest thing, the newlines are generated from this file and the newlines should be in there once templated across.

Just came across that file. What exactly is doing the templating? Could it be some weird linux edge case?

flow runs on a bundled node.js version, with the same code across all targets. It uses handlebars (mustache templates) but, it's also worked all along on my linux builds on ubuntu/mint distros.
I can't imagine what would make it remove a new line character, that seems pretty peculiar.

Ah, I may know what's going on. The bundled node.js binaries weren't working for me, so I quickly modified the flow run script to use my system's node (v5.12.0). What node version is bundled?

here's mine on osx for reference, with it's contents untouched. This is what it should be getting in the default configuration, with regards to new lines .
--macro snow.Set.main("luxe.Engine")
--macro snow.Set.ident("com.luxeengine.testdraw")

--macro snow.Set.config("config.json")

The one bundled is node.js v0.12.7, although their versioning is a bit insane lately. I don't think that would affect newlines of files moved across but who knows?
Here is where the templating and file copy happens with these.
There's no build step for flow, so just poking at the js will change it's behavior directly.
Note you can run flow build --log 4 for way more information on what it's doing.

I should hope it wouldn't, but then again, it is node, and stranger things have happened.
Thanks for all the help.

Doesn't look like I can submit .patch files to GH issues. Oh well, long story short, removing the ~'s worked.
diff --git a/flow/build/snow.hxml b/flow/build/snow.hxml
index 37a0f7d..4ca3a39 100644
--- a/flow/build/snow.hxml
+++ b/flow/build/snow.hxml
@@ -1,20 +1,20 @@
-{{#if snow.main~}}
+{{#if snow.main}}
 --macro snow.Set.main("{{{toString snow.main}}}")
-{{~else~}}
+{{else}}
 --macro snow.Set.main("{{{toString project.app.main}}}")
-{{~/if}}
-{{#if project.app.package~}}
+{{/if}}
+{{#if project.app.package}}
 --macro snow.Set.ident("{{{toString project.app.package}}}")
-{{~/if}}
-{{#if snow.config.log~}}
+{{/if}}
+{{#if snow.config.log}}
 --macro snow.api.Debug.level({{{snow.config.log}}})
-{{~/if}}
-{{#if snow.config.config_path~}}
+{{/if}}
+{{#if snow.config.config_path}}
 --macro snow.Set.config("{{{toString snow.config.config_path}}}")
-{{~/if}}
-{{#if snow.runtime~}}
+{{/if}}
+{{#if snow.runtime}}
 --macro snow.Set.runtime("{{{toString snow.runtime}}}")
-{{~/if}}
-{{#if snow.audio~}}
+{{/if}}
+{{#if snow.audio}}
 --macro snow.Set.audio("{{{toString snow.audio}}}")
-{{~/if}}
+{{/if}}

Well, that will change how whitespace is handled, but it doesn't explain why it works consistently across windows, mac, and my other linux distros! I suspect you wouldn't need to eradicate all of them either, but it's hard to know what is causing the discrepancy here at the root of the delta.

Yeah, it's definitely a strange one. Anywho, this fix works for me for now. I guess we'll see if anyone else runs into it in the future.

Any ideas on this one?
The file it's looking for linux64.build/cpp/obj/linux64/__pch/haxe/hxcpp.h doesn't exist, but hxcpp.h.gch does.
flow / 1.0.0-alpha.2 (node.js v5.12.0)
flow / target is linux ( arch 64 )
flow / haxe version 3.2.0

flow / build - luxe.draw 1.0.0 for linux
flow / build - running haxe ...
flow / build - running hxcpp for arch 64 ...
Creating /home/garrett/draw/bin/linux64.build/cpp/obj/linux64/__pch/haxe/hxcpp.h.gch...
 - Compiling group 'haxe' with flags -Iinclude -I/usr/lib/haxe/lib/linc_ogg/git//lib/ -I/usr/lib/haxe/lib/linc_ogg/git//linc/ -I/usr/lib/haxe/lib/linc_ogg/git//lib//ogg/include/ -I/usr/lib/haxe/lib/linc_ogg/git//lib//vorbis/include/ -I/usr/lib/haxe/lib/linc_ogg/git//lib//theora/include/ -DNATIVE_TOOLKIT_OGG -DNATIVE_TOOLKIT_VORBIS -DNATIVE_TOOLKIT_THEORA -DLINC_OPENAL -I/usr/lib/haxe/lib/linc_openal/git//linc/ -I/usr/lib/haxe/lib/linc_opengl/git//linc/ -I/usr/lib/haxe/lib/linc_opengl/git//lib/glew/include/ -DLINC_OPENGL_GLEW -DGLEW_STATIC -DLINC_SDL -I/usr/lib/haxe/lib/linc_sdl/git//linc/ -I/usr/lib/haxe/lib/linc_sdl/git//lib/sdl/include/ -I/usr/lib/haxe/lib/linc_sdl/git//lib/sdl/include/configs/linux/ -DHAVE_LIBC -DNATIVE_TOOLKIT_SDL -I/usr/lib/haxe/lib/linc_stb/git//lib/ -I/usr/lib/haxe/lib/linc_stb/git//linc/ -I/usr/lib/haxe/lib/linc_timestamp/git//linc/ -c -fvisibility=hidden -O2 -fpic -fPIC -DHX_LINUX -DHXCPP_M64 -DHXCPP_VISIT_ALLOCS(haxe) -DHXCPP_API_LEVEL=321(haxe) -m64 -DHXCPP_M64 -I/usr/lib/haxe/lib/hxcpp/3,3,49/include tags=[haxe,static]
 - Compile : src/snow/systems/io/IO.cpp
 - Compile : src/snow/systems/audio/Audio.cpp
 - Compile : src/snow/systems/audio/AudioSource.cpp
 - Compile : src/snow/systems/audio/AudioInstance.cpp
Error: While running :g++ -I/home/garrett/draw/bin/linux64.build/cpp/obj/linux64/__pch/haxe -Iinclude -I/usr/lib/haxe/lib/linc_ogg/git//lib/ -I/usr/lib/haxe/lib/linc_ogg/git//linc/ -I/usr/lib/haxe/lib/linc_ogg/git//lib//ogg/include/ -I/usr/lib/haxe/lib/linc_ogg/git//lib//vorbis/include/ -I/usr/lib/haxe/lib/linc_ogg/git//lib//theora/include/ -DNATIVE_TOOLKIT_OGG -DNATIVE_TOOLKIT_VORBIS -DNATIVE_TOOLKIT_THEORA -DLINC_OPENAL -I/usr/lib/haxe/lib/linc_openal/git//linc/ -I/usr/lib/haxe/lib/linc_opengl/git//linc/ -I/usr/lib/haxe/lib/linc_opengl/git//lib/glew/include/ -DLINC_OPENGL_GLEW -DGLEW_STATIC -DLINC_SDL -I/usr/lib/haxe/lib/linc_sdl/git//linc/ -I/usr/lib/haxe/lib/linc_sdl/git//lib/sdl/include/ -I/usr/lib/haxe/lib/linc_sdl/git//lib/sdl/include/configs/linux/ -DHAVE_LIBC -DNATIVE_TOOLKIT_SDL -I/usr/lib/haxe/lib/linc_stb/git//lib/ -I/usr/lib/haxe/lib/linc_stb/git//linc/ -I/usr/lib/haxe/lib/linc_timestamp/git//linc/ -c -fvisibility=hidden -O2 -fpic -fPIC -DHX_LINUX -DHXCPP_M64 -DHXCPP_VISIT_ALLOCS -DHXCPP_API_LEVEL=321 -m64 -DHXCPP_M64 -I/usr/lib/haxe/lib/hxcpp/3,3,49/include -x c++ -frtti -Wno-invalid-offsetof ./src/snow/systems/io/IO.cpp -o/home/garrett/draw/bin/linux64.build/cpp/obj/linux64/b41f00c5_IO.o
In file included from include/snow/core/native/io/IO.h:11:0,
                 from ./src/snow/systems/io/IO.cpp:43:
/usr/lib/haxe/lib/linc_sdl/git//linc/linc_sdl.h:6:19: fatal error: /home/garrett/draw/bin/linux64.build/cpp/obj/linux64/__pch/haxe/hxcpp.h: No such file or directory
compilation terminated.
flow /
 build - stopping because of errors in hxcpp compile, while building arch 64

eugh, I think it's backwards incompatibility with the latest hxcpp version (I REALLY don't understand how this 3.3 rc has been a constant struggle!). I hope @hughsando has at least been addressing this.
Try haxelib install hxcpp 3.2.205 it's the latest 3.2.0 aligned release before 3.3.0rc.

Well, that got it farther...
» flow run
flow / 1.0.0-alpha.2 (node.js v5.12.0)
flow / target is linux ( arch 64 )
flow / haxe version 3.2.0

flow / build - luxe.draw 1.0.0 for linux
flow / build - running haxe ...
flow / build - running hxcpp for arch 64 ...
g++ -Iinclude -I/usr/lib/haxe/lib/linc_ogg/git//lib/ -I/usr/lib/haxe/lib/linc_ogg/git//linc/ -I/usr/lib/haxe/lib/linc_ogg/git//lib//ogg/include/ -I/usr/lib/haxe/lib/linc_ogg/git//lib//vorbis/include/ -I/usr/lib/haxe/lib/linc_ogg/git//lib//theora/include/ -DNATIVE_TOOLKIT_OGG -DNATIVE_TOOLKIT_VORBIS -DNATIVE_TOOLKIT_THEORA -DLINC_OPENAL -I/usr/lib/haxe/lib/linc_openal/git//linc/ -I/usr/lib/haxe/lib/linc_opengl/git//linc/ -I/usr/lib/haxe/lib/linc_opengl/git//lib/glew/include/ -DLINC_OPENGL_GLEW -DGLEW_STATIC -DLINC_SDL -I/usr/lib/haxe/lib/linc_sdl/git//linc/ -I/usr/lib/haxe/lib/linc_sdl/git//lib/sdl/include/ -I/usr/lib/haxe/lib/linc_sdl/git//lib/sdl/include/configs/linux/ -DHAVE_LIBC -DNATIVE_TOOLKIT_SDL -I/usr/lib/haxe/lib/linc_stb/git//lib/ -I/usr/lib/haxe/lib/linc_stb/git//linc/ -I/usr/lib/haxe/lib/linc_timestamp/git//linc/ -c -fvisibility=hidden -O2 -fpic -fPIC -DHX_LINUX -DHXCPP_M64 -DHXCPP_VISIT_ALLOCS -DHXCPP_API_LEVEL=321 -m64 -DHXCPP_M64 -I/usr/lib/haxe/lib/hxcpp/3,2,205/include -x c++ -frtti -Wno-invalid-offsetof ./src/snow/modules/openal/ALSound.cpp -o/home/garrett/draw/bin/linux64.build/cpp/obj/linux64/9d017f78_ALSound.o
g++ -Iinclude -I/usr/lib/haxe/lib/linc_ogg/git//lib/ -I/usr/lib/haxe/lib/linc_ogg/git//linc/ -I/usr/lib/haxe/lib/linc_ogg/git//lib//ogg/include/ -I/usr/lib/haxe/lib/linc_ogg/git//lib//vorbis/include/ -I/usr/lib/haxe/lib/linc_ogg/git//lib//theora/include/ -DNATIVE_TOOLKIT_OGG -DNATIVE_TOOLKIT_VORBIS -DNATIVE_TOOLKIT_THEORA -DLINC_OPENAL -I/usr/lib/haxe/lib/linc_openal/git//linc/ -I/usr/lib/haxe/lib/linc_opengl/git//linc/ -I/usr/lib/haxe/lib/linc_opengl/git//lib/glew/include/ -DLINC_OPENGL_GLEW -DGLEW_STATIC -DLINC_SDL -I/usr/lib/haxe/lib/linc_sdl/git//linc/ -I/usr/lib/haxe/lib/linc_sdl/git//lib/sdl/include/ -I/usr/lib/haxe/lib/linc_sdl/git//lib/sdl/include/configs/linux/ -DHAVE_LIBC -DNATIVE_TOOLKIT_SDL -I/usr/lib/haxe/lib/linc_stb/git//lib/ -I/usr/lib/haxe/lib/linc_stb/git//linc/ -I/usr/lib/haxe/lib/linc_timestamp/git//linc/ -c -fvisibility=hidden -O2 -fpic -fPIC -DHX_LINUX -DHXCPP_M64 -DHXCPP_VISIT_ALLOCS -DHXCPP_API_LEVEL=321 -m64 -DHXCPP_M64 -I/usr/lib/haxe/lib/hxcpp/3,2,205/include -x c++ -frtti -Wno-invalid-offsetof ./src/snow/modules/sdl/Runtime.cpp -o/home/garrett/draw/bin/linux64.build/cpp/obj/linux64/7cc13b40_Runtime.o
g++ -Iinclude -I/usr/lib/haxe/lib/linc_ogg/git//lib/ -I/usr/lib/haxe/lib/linc_ogg/git//linc/ -I/usr/lib/haxe/lib/linc_ogg/git//lib//ogg/include/ -I/usr/lib/haxe/lib/linc_ogg/git//lib//vorbis/include/ -I/usr/lib/haxe/lib/linc_ogg/git//lib//theora/include/ -DNATIVE_TOOLKIT_OGG -DNATIVE_TOOLKIT_VORBIS -DNATIVE_TOOLKIT_THEORA -DLINC_OPENAL -I/usr/lib/haxe/lib/linc_openal/git//linc/ -I/usr/lib/haxe/lib/linc_opengl/git//linc/ -I/usr/lib/haxe/lib/linc_opengl/git//lib/glew/include/ -DLINC_OPENGL_GLEW -DGLEW_STATIC -DLINC_SDL -I/usr/lib/haxe/lib/linc_sdl/git//linc/ -I/usr/lib/haxe/lib/linc_sdl/git//lib/sdl/include/ -I/usr/lib/haxe/lib/linc_sdl/git//lib/sdl/include/configs/linux/ -DHAVE_LIBC -DNATIVE_TOOLKIT_SDL -I/usr/lib/haxe/lib/linc_stb/git//lib/ -I/usr/lib/haxe/lib/linc_stb/git//linc/ -I/usr/lib/haxe/lib/linc_timestamp/git//linc/ -c -fvisibility=hidden -O2 -fpic -fPIC -DHX_LINUX -DHXCPP_M64 -DHXCPP_VISIT_ALLOCS -DHXCPP_API_LEVEL=321 -m64 -DHXCPP_M64 -I/usr/lib/haxe/lib/hxcpp/3,2,205/include -x c++ -frtti -Wno-invalid-offsetof ./src/snow/core/native/io/IO.cpp -o/home/garrett/draw/bin/linux64.build/cpp/obj/linux64/4982671b_IO.o
g++ -Iinclude -I/usr/lib/haxe/lib/linc_ogg/git//lib/ -I/usr/lib/haxe/lib/linc_ogg/git//linc/ -I/usr/lib/haxe/lib/linc_ogg/git//lib//ogg/include/ -I/usr/lib/haxe/lib/linc_ogg/git//lib//vorbis/include/ -I/usr/lib/haxe/lib/linc_ogg/git//lib//theora/include/ -DNATIVE_TOOLKIT_OGG -DNATIVE_TOOLKIT_VORBIS -DNATIVE_TOOLKIT_THEORA -DLINC_OPENAL -I/usr/lib/haxe/lib/linc_openal/git//linc/ -I/usr/lib/haxe/lib/linc_opengl/git//linc/ -I/usr/lib/haxe/lib/linc_opengl/git//lib/glew/include/ -DLINC_OPENGL_GLEW -DGLEW_STATIC -DLINC_SDL -I/usr/lib/haxe/lib/linc_sdl/git//linc/ -I/usr/lib/haxe/lib/linc_sdl/git//lib/sdl/include/ -I/usr/lib/haxe/lib/linc_sdl/git//lib/sdl/include/configs/linux/ -DHAVE_LIBC -DNATIVE_TOOLKIT_SDL -I/usr/lib/haxe/lib/linc_stb/git//lib/ -I/usr/lib/haxe/lib/linc_stb/git//linc/ -I/usr/lib/haxe/lib/linc_timestamp/git//linc/ -c -fvisibility=hidden -O2 -fpic -fPIC -DHX_LINUX -DHXCPP_M64 -DHXCPP_VISIT_ALLOCS -DHXCPP_API_LEVEL=321 -m64 -DHXCPP_M64 -I/usr/lib/haxe/lib/hxcpp/3,2,205/include -x c++ -frtti -Wno-invalid-offsetof ./src/snow/modules/interfaces/IO.cpp -o/home/garrett/draw/bin/linux64.build/cpp/obj/linux64/af4c4889_IO.o
Error: In file included from ./src/snow/modules/sdl/Runtime.cpp:4:0:
/usr/lib/haxe/lib/linc_opengl/git//linc/linc_glew.h:4:41: fatal error: ../lib/glew/include/GL/glew.h: No such file or directory
compilation terminated.
flow /
 build - stopping because of errors in hxcpp compile, while building arch 64

Looks like you didn't clone the linc dependencies with submodules. Did you use snowfall?

In other words,
cd /usr/lib/haxe/lib/linc_glew/git/
git submodule update --init
Inside the folder, the lib folder would be empty without the submodules.

It's there now, still no luck. Not sure if it was before running submodules update --init.
» tree /usr/lib/haxe/lib/linc_glew/git/lib       /usr/lib/haxe/lib/luxe/git/tests/features/draw
/usr/lib/haxe/lib/linc_glew/git/lib
└── glew
    ├── include
    │   └── GL
    │       ├── glew.h
    │       ├── glxew.h
    │       └── wglew.h
    ├── README.md
    └── src
        └── glew.c

4 directories, 5 files

curious, the line for the Runtime.cpp has
-I/usr/lib/haxe/lib/linc_opengl/git//lib/glew/include/
So it should be finding it, unless the duplicate slash is somehow an issue?

hold on, linc_glew != linc_opengl, where is linc_glew getting in from, it's not a dependency (since linc_opengl includes the glew)

I vaguely remember installing some sort of linc_ manually. (Using haxelib git) Removing linc_glew doesn't change anything.

Yea I seem to have confused myself, it's getting the linc_glew file from linc_opengl it's the subsequent header it can't find.

Yeah, I guess it's GL/glu.h that can't be found?

no I don't think it's that, ../lib/glew/include/GL/glew.h: No such file or directory is the exact error, relative to linc_glew.h it can't find this

Alright, could it be caused by the double /?

You can remove the slash here and test.
<compilerflag value='-I${LINC_OPENGL_PATH}lib/glew/include/'/>
It's the one after the }

Hmm, doesn't seem to have any effect on the error.
flow / build - running hxcpp for arch 64 ...
g++ -Iinclude -I/usr/lib/haxe/lib/linc_ogg/git//lib/ -I/usr/lib/haxe/lib/linc_ogg/git//linc/ -I/usr/lib/haxe/lib/linc_ogg/git//lib//ogg/include/ -I/usr/lib/haxe/lib/linc_ogg/git//lib//vorbis/include/ -I/usr/lib/haxe/lib/linc_ogg/git//lib//theora/include/ -DNATIVE_TOOLKIT_OGG -DNATIVE_TOOLKIT_VORBIS -DNATIVE_TOOLKIT_THEORA -DLINC_OPENAL -I/usr/lib/haxe/lib/linc_openal/git//linc/ -I/usr/lib/haxe/lib/linc_opengl/git//linc/ -I/usr/lib/haxe/lib/linc_opengl/git//aardvark/glew/include/ -DLINC_OPENGL_GLEW -DGLEW_STATIC -DLINC_SDL -I/usr/lib/haxe/lib/linc_sdl/git//linc/ -I/usr/lib/haxe/lib/linc_sdl/git//lib/sdl/include/ -I/usr/lib/haxe/lib/linc_sdl/git//lib/sdl/include/configs/linux/ -DHAVE_LIBC -DNATIVE_TOOLKIT_SDL -I/usr/lib/haxe/lib/linc_stb/git//lib/ -I/usr/lib/haxe/lib/linc_stb/git//linc/ -I/usr/lib/haxe/lib/linc_timestamp/git//linc/ -c -fvisibility=hidden -O2 -fpic -fPIC -DHX_LINUX -DHXCPP_M64 -DHXCPP_VISIT_ALLOCS -DHXCPP_API_LEVEL=321 -m64 -DHXCPP_M64 -I/usr/lib/haxe/lib/hxcpp/3,2,205/include -x c++ -frtti -Wno-invalid-offsetof ./src/snow/modules/sdl/Runtime.cpp -o/usr/lib/haxe/lib/luxe/git/tests/features/draw/bin/linux64.build/cpp/obj/linux64/7cc13b40_Runtime.o
g++ -Iinclude -I/usr/lib/haxe/lib/linc_ogg/git//lib/ -I/usr/lib/haxe/lib/linc_ogg/git//linc/ -I/usr/lib/haxe/lib/linc_ogg/git//lib//ogg/include/ -I/usr/lib/haxe/lib/linc_ogg/git//lib//vorbis/include/ -I/usr/lib/haxe/lib/linc_ogg/git//lib//theora/include/ -DNATIVE_TOOLKIT_OGG -DNATIVE_TOOLKIT_VORBIS -DNATIVE_TOOLKIT_THEORA -DLINC_OPENAL -I/usr/lib/haxe/lib/linc_openal/git//linc/ -I/usr/lib/haxe/lib/linc_opengl/git//linc/ -I/usr/lib/haxe/lib/linc_opengl/git//aardvark/glew/include/ -DLINC_OPENGL_GLEW -DGLEW_STATIC -DLINC_SDL -I/usr/lib/haxe/lib/linc_sdl/git//linc/ -I/usr/lib/haxe/lib/linc_sdl/git//lib/sdl/include/ -I/usr/lib/haxe/lib/linc_sdl/git//lib/sdl/include/configs/linux/ -DHAVE_LIBC -DNATIVE_TOOLKIT_SDL -I/usr/lib/haxe/lib/linc_stb/git//lib/ -I/usr/lib/haxe/lib/linc_stb/git//linc/ -I/usr/lib/haxe/lib/linc_timestamp/git//linc/ -c -fvisibility=hidden -O2 -fpic -fPIC -DHX_LINUX -DHXCPP_M64 -DHXCPP_VISIT_ALLOCS -DHXCPP_API_LEVEL=321 -m64 -DHXCPP_M64 -I/usr/lib/haxe/lib/hxcpp/3,2,205/include -x c++ -frtti -Wno-invalid-offsetof ./src/snow/api/buffers/_ArrayBuffer/ArrayBuffer_Impl_.cpp -o/usr/lib/haxe/lib/luxe/git/tests/features/draw/bin/linux64.build/cpp/obj/linux64/272b13fd_ArrayBuffer_Impl_.o
g++ -Iinclude -I/usr/lib/haxe/lib/linc_ogg/git//lib/ -I/usr/lib/haxe/lib/linc_ogg/git//linc/ -I/usr/lib/haxe/lib/linc_ogg/git//lib//ogg/include/ -I/usr/lib/haxe/lib/linc_ogg/git//lib//vorbis/include/ -I/usr/lib/haxe/lib/linc_ogg/git//lib//theora/include/ -DNATIVE_TOOLKIT_OGG -DNATIVE_TOOLKIT_VORBIS -DNATIVE_TOOLKIT_THEORA -DLINC_OPENAL -I/usr/lib/haxe/lib/linc_openal/git//linc/ -I/usr/lib/haxe/lib/linc_opengl/git//linc/ -I/usr/lib/haxe/lib/linc_opengl/git//aardvark/glew/include/ -DLINC_OPENGL_GLEW -DGLEW_STATIC -DLINC_SDL -I/usr/lib/haxe/lib/linc_sdl/git//linc/ -I/usr/lib/haxe/lib/linc_sdl/git//lib/sdl/include/ -I/usr/lib/haxe/lib/linc_sdl/git//lib/sdl/include/configs/linux/ -DHAVE_LIBC -DNATIVE_TOOLKIT_SDL -I/usr/lib/haxe/lib/linc_stb/git//lib/ -I/usr/lib/haxe/lib/linc_stb/git//linc/ -I/usr/lib/haxe/lib/linc_timestamp/git//linc/ -c -fvisibility=hidden -O2 -fpic -fPIC -DHX_LINUX -DHXCPP_M64 -DHXCPP_VISIT_ALLOCS -DHXCPP_API_LEVEL=321 -m64 -DHXCPP_M64 -I/usr/lib/haxe/lib/hxcpp/3,2,205/include -x c++ -frtti -Wno-invalid-offsetof ./src/snow/api/Timer.cpp -o/usr/lib/haxe/lib/luxe/git/tests/features/draw/bin/linux64.build/cpp/obj/linux64/dc68e609_Timer.o
g++ -Iinclude -I/usr/lib/haxe/lib/linc_ogg/git//lib/ -I/usr/lib/haxe/lib/linc_ogg/git//linc/ -I/usr/lib/haxe/lib/linc_ogg/git//lib//ogg/include/ -I/usr/lib/haxe/lib/linc_ogg/git//lib//vorbis/include/ -I/usr/lib/haxe/lib/linc_ogg/git//lib//theora/include/ -DNATIVE_TOOLKIT_OGG -DNATIVE_TOOLKIT_VORBIS -DNATIVE_TOOLKIT_THEORA -DLINC_OPENAL -I/usr/lib/haxe/lib/linc_openal/git//linc/ -I/usr/lib/haxe/lib/linc_opengl/git//linc/ -I/usr/lib/haxe/lib/linc_opengl/git//aardvark/glew/include/ -DLINC_OPENGL_GLEW -DGLEW_STATIC -DLINC_SDL -I/usr/lib/haxe/lib/linc_sdl/git//linc/ -I/usr/lib/haxe/lib/linc_sdl/git//lib/sdl/include/ -I/usr/lib/haxe/lib/linc_sdl/git//lib/sdl/include/configs/linux/ -DHAVE_LIBC -DNATIVE_TOOLKIT_SDL -I/usr/lib/haxe/lib/linc_stb/git//lib/ -I/usr/lib/haxe/lib/linc_stb/git//linc/ -I/usr/lib/haxe/lib/linc_timestamp/git//linc/ -c -fvisibility=hidden -O2 -fpic -fPIC -DHX_LINUX -DHXCPP_M64 -DHXCPP_VISIT_ALLOCS -DHXCPP_API_LEVEL=321 -m64 -DHXCPP_M64 -I/usr/lib/haxe/lib/hxcpp/3,2,205/include -x c++ -frtti -Wno-invalid-offsetof ./src/snow/api/buffers/ArrayBufferIO.cpp -o/usr/lib/haxe/lib/luxe/git/tests/features/draw/bin/linux64.build/cpp/obj/linux64/15f28a6e_ArrayBufferIO.o
Error: In file included from /usr/lib/haxe/lib/linc_opengl/git//linc/linc_glew.h:4:0,
                 from ./src/snow/modules/sdl/Runtime.cpp:4:
/usr/lib/haxe/lib/linc_opengl/git//linc/../lib/glew/include/GL/glew.h:1201:24: fatal error: GL/glu.h: No such file or directory
 #    include <GL/glu.h>
                        ^
compilation terminated.
flow /
 build - stopping because of errors in hxcpp compile, while building arch 64

hmm, did you follow all the setup steps in the guide? Steps 4.3:
Linux - some dev libs are required:
libgl1-mesa-dev
libglu1-mesa-dev
And currently OpenAL is required libopenal-dev

Alright, I think I've gotten everything sorted out. Due to my using NixOs, it's a bit more of a hassle.
Anywho, thanks so much for your help!

Glad you got sorted.

p.s I'd be interested to know what the resolution was for your distro, never hurts to know more about other flavours.

Well, NixOs is a bit strange. I need to create a proper build environment with the required libraries and such.
For anyone that comes across this, perhaps this will help.
let
  pkgs = import <nixpkgs> {};
  stdenv = pkgs.stdenv;
in rec {
  haxe = stdenv.mkDerivation rec {
    name = "haxe";
    version = "0.1";
    src = ./.;
    buildInputs = [
      pkgs.mesa
      pkgs.mesa_glu
      pkgs.xorg.kbproto
      pkgs.xorg.libX11
      pkgs.xorg.libXtst
      pkgs.xorg.libxcb
      pkgs.xorg.xkbutils
      pkgs.xorg.libXext
    ];
  };
}

After a little fiddling and some manual ELF patching, I got the linux build to run. I'll need to create a proper nix build in the future if I decide to go the luxe route.

Right, I see here it mentions the rewrites for rpath and ld. It's relatively straight forward to specify these directly from your hx file or from flow with additional build xml meta data.
for flow, there is a project.build.hxcpp.includes node handled here which will inject an <include> node into the final build xml. This might allow you add some linker flags to modify rpath and ld linkage directly configuring gcc or your compiler. I say might, in that there may be an order issue of flags. At the very least, it might allow you to get through that bit quicker.
The alternative is just the regular @:buildXml meta in a haxe file.
More info about the build xml is around online, but I've been writing up a more detailed guide here. That should elaborate on how to specify the linker flags at build time.


Merge clobbers attributes

Merging files clobbers the attributes.  I think this is OK since the main output is a file per year.   But rather that the method I put in demo.ipynb, could be another function merge_years() to do this, and make a choice on the attributes.
An option could be to create a list of names, separated by comma, and then retain only the unique contributor names.  Same for project_id.
geospatial limits could be the overall maximum and overall minimum.
time_cruise* could be the overall max and min.

I create the function merge_dataset to merge all years. The global attributes that depend on the individual cruise are updated within the function:

Task finished


feat: Support uncommon profile structures

Any reason why this is still a draft? It looks like these helper functions would cut down on boilerplate.


NPM scenario support

This may be quick and dirty at first, but I have a need to test  1.13.x >= ember >= 1.7.x, so I'm going to take a stab at it. Let's also let this be a place to start a discussion for "the proper approach" to adding NPM support.
Commands
No changes should be needed to the ember try* commands, although their internals will have to be enhanced
Configuration - config/ember-try.js
////////////////////////
//// EXISTING
////////////////////////

{
  name: 'ember-1.10',
  dependencies: {
    'ember': '~1.10.0'
  },
  resolutions: {
    'ember': '~1.10.0'
  }
}

////////////////////////
//// SUPPORTED
////////////////////////

{
  name: 'ember-1.10',
  dependencies: {
    'ember': '~1.10.0'
  },
  resolutions: {
    'ember': '~1.10.0'
  },
  npm: {
    dependencies: {
      'ember': '~1.10.0'
    },
    resolutions: {
      'ember': '~1.10.0'
    }
  }
}

////////////////////////
//// ENCOURAGED
////////////////////////

{
  name: 'ember-1.10',
  bower: {
    dependencies: {
      'ember': '~1.10.0'
    },
    resolutions: {
      'ember': '~1.10.0'
    },
  }
  npm: {
    dependencies: {
      'ember': '~1.10.0'
    },
    resolutions: {
      'ember': '~1.10.0'
    }
  }
}

Thoughts

The cost of a "npm install" is, for most people, way higher than the cost of a bower install.

It would be fantastic if adding this feature didn't increase the time it takes to run through a set of scenarios by much.
We could probably move the existing node_modules so that it's easy to put back when we want to ember try:reset
We probably do not want to blow the whole node_modules folder away if we don't have to
There's the issue of ember-try its self being in node_modules.

For the use case of dealing w/ various versions of handlebars, some packages will need to be removed from package.json. The current way that bower.json is handled supports only adding.
I see no problem with the approach of backing up the bower.json file to bower.json.ember-try. This should apply equally well to package.json

[x] Basic implementation
[x] Save time by explicitly altering single packages (instead of a broad "npm install")
[x] Test coverage for a variety of npm scenarios
[x] Documentation

I'm still just poking around with the code for now, so it's probably not worth reviewing yet :)

This now works for a bunch of cases that I have tested. Just cleaning stuff up at this point, and potentially logging some more information out so people can feel confident that their scenario is being set up as they expect.

Ok this works now, and is ready for review @kategengler @rwjblue

Found a few cases where there are still problems, and I should be able to address them within the next day or two

Hey @mike-north, whats the status on this?

Got sidetracked on something else. Not sure when I'll be able to pick this back up, but it needs some more love before merge

:+1: This would be very helpful.
Ember 1.13 loads helper automatically, but 1.12 needs another add-on to do this.

This would be a great feature to have merged, is there any way I can help to get this one merged?

it proved to be quite a bit more complicated than I initially thought (I
know, surprise!). While my initial solution works in some cases, it's quite
easy to poke holes and make it fall on its face. It's unclear when I'll
have time to give it some love
On Mon, Dec 21, 2015 at 12:54 AM Marten<EMAIL_ADDRESS>wrote:

This would be a great feature to have merged, is there any way I can help
to get this one merged?
—
Reply to this email directly or view it on GitHub
https://github.com/kategengler/ember-try/pull/26#issuecomment-166239410.

I've been working on npm support, but with a very different approach.

Closing in favor of #45


:white_check_mark: Add unit tests

Seriously.. test everything.
Hasn't been done so far because of the difficulties of testing UI apps, but with Kivy it seems to be easy: https://kivy.org/doc/stable/contribute-unittest.html

https://pypi.org/project/kivyunittest/0.1.0/


chore: namespace and tidy MonCat/GroupCat adjunctions

Let's try again:
maintainer merge

Oops, that was twice. Sorry, I'm still learning :-)

I believe you requested a change. Generally we do maintainer merge after these changes have been incorporated.
bors d+

bors merge

I believe you requested a change. Generally we do maintainer merge after these changes have been incorporated.
bors d+

Makes sense, thanks for letting me know!


add more definitions folder

I have a lot of definition subfolders in different folders, I hope I can add these folders too.

I understand your use case, but I would discourage having multiple large definition folders as it will likely degrade performance.

I'm a little confused because I can create several subfolders in the "definition folder", and why will it degrade performance if I move these subfolders away from the "definition folder" to other folder? Thank you in advance :)

Hmm, I was thinking if multiple folders can be registered as definition folders, it could lead to the situation where users register multiple large folders. And since these folders need to be separately and recursively parsed, it might lead to long load/startup time. But it is a fair point that this could happen even if the user is restricted to only one folder as multiple subfolders can be created.
I'll add this as a possible enhancement.

@dominiclet Would it be possible to include the definition notes in the subfolders of the currently selected definitions folder as well? This would greatly help me in organizing the different definition notes.

Personally, I would vastly prefer if users could simply set multiple unrelated folders as a definition folder compared to using sub-folders within the definitions folder. This way, one can logically separate definitions, by placing them in the area wherein they are used. This makes moving them around vastly easier too, as one only need to move the parent folder, instead of the parent folder and the definitions folder's sub-folder for the given topic if you were moving files to a new vault or something.
E.g. I tend to have asset folders for my projects. And they tend to be nested inside a "shared" folder within a given project's folder. Being able to add project-specific definitions there would be something I'd prefer, over placing them in some centralized location in a named sub-folder like the current implementation.

Hopefully, this will be implemented; this is quite an essential thing to have.


trigger a new build to fix cve problems

Signed-off-by: Wei Liu<EMAIL_ADDRESS>

refer to https://github.com/stolostron/backlog/issues/22153

/cherry-pick backplane-2.0

/assign @zhiweiyin318

/assign @ldpliu

/lgtm


it cannot get text node

to get parent node, it work, but to get text node, not work

Hello @plh97, as a workaround (to solve your problem), try the following:
const firstTextXPath = getXPath( $0.parentNode ) + '/text()[1]'

Support to text nodes added - see v3.2.0


Review a draft of mruby 2.1.2 release note

I made a draft of mruby 2.1.2 release note.
Please review.

mruby 2.1.2
We are announcing the stable release of mruby 2.1 series - mruby 2.1.2.

New Features
Core Language Features

Support for Argument Forwarding, which allows you to forward argyments in the form def foo(...).

mruby VM and bytecode

Add OP_LOADI16 instruction that loads a 16-bit integer into a register.
Remove endian information/flags from compiled binary format.
The version of the mruby binary has changed from 0006 to 0007.

for mruby Developer

Add new C APIs.

mrb_float_to_cstr() - Convert Float to C String.
mrb_singleton_class_ptr() - Get pointer of Singleton class. #4973
mrb_utf8len() - Get size of UTF-8 string. #4712
mrb_utf8_strlen() - Get length of UTF-8 string. #4712
mrb_get_arg1() - Retrieve the first and only argument from mrb_state.

Update Features
Core Libraries

Add to the libraries included by default in the mruby VM.

mruby-eval
mruby-complex
mruby-rational

Support MRB_DISABLE_STDIO for mruby-pack and mruby-sprintf. #4954
Support IO#pread and IO#pwrite on macOS.
Improve Kernel.#eval to call method with the same name as a variable name without any arguments.
IO#readchar supports UTF-8 characters.

Tools

Remove -e / -E options from mrbc.

for mruby Developer

Support width specifier with mrb_float_to_str().
Support integer and float combination in mrb_equal().

Improve mruby build

A mruby can be built without GNU Bison. (a3ec6ede)
Supports GitHub Actions. #4903
Execute CI of the following platforms updating the repository.

Ubuntu 16.04
Ubuntu 18.04 (gcc)
Ubuntu 18.04 (clang)
macOS
Windows (MinGW)
Windows (Cygwin)
Windows (MSVC)

Breaking Changes

IO#readchar returns a UTF-8 character fragment instead of EOFError if EOF is reached in the middle of UTF-8 characters. (86271572)
This behavior is different from CRuby, but it is a mruby specification that supports either ASCII or UTF-8 exclusively.
Remove mrb_run() from C APIs.

Major bug fixes

Segmentation fault at mrb_io_s_select. #4966
Segmentation fault at mrb_vm_exec. #4973
Some Hash methods are inconsistent with values when hash has duplicate key. 181f7b97
Get local variable names from orphan block. #5014
Memory leaks in some places when out of memory. f1523d24
The bug that mrbc generates a.rb.mrb instead of a.mrb. ac836000
Invalid shift width for MRB_ENV_SET_BIDX(). #5038
Heap buffer overflow in mruby interpreter. #5042
Type tag not used when calculating hash code. #5049

We have done 184 commits to 99 files with 14,883 addtions and 1,653 deletions since mruby 2.1.1. For more detail of the updates, see Commit Log.
Thanks all the contributors who have worked on bug fix and improvements in the release of mruby 2.1.2.

We also removed mrb_num_div() and mrb_class_outer_module().

Major bug fixes

The bug that mrbc generates a.rb.mrb instead of a.mrb. ac836000
Invalid shift width for MRB_ENV_SET_BIDX(). #5038

These two items are corrections to the development stage after 2.1.1, so I think they are unnecessary.

@matz
mrb_num_div (0c91da2) and mrb_class_outer_module (da24af3) have been removed, is not it before 2.1.1 release?

Ah, yes. I forgot.

Thank you for the review.
mruby 2.1.2 was released on August 6, 2020.


⚠ Bofrost.fr has degraded performance

In b412ee1, Bofrost.fr (https://www.bofrost.fr) experienced degraded performance:

HTTP code: 200
Response time: 980 ms

Resolved: Bofrost.fr performance has improved in 1050c79 after 6 minutes.


#4741 management deactivate users

Fixed/refactored deactivate multiple users functionality. Fixed and optimized check if a user is deactivated in the security filter. Fixed bug in HttpClientErrorExceptionResponse.

@PawelMiskowiec please fix this


Encoding and Decoding Compound Arrays Does not work with JSON Encoder/Decoder

I currently use the pickle encoder and decoder; however, I've been requested to have the encoding/decoding process be doable through JSON encoder/decoder.
When dealing with compound structures, i.e., structured arrays, I run into a dimension issue. Below reproduces the issue. Is this structure supported and if so is there something I need to change so that the input item is in a specific format?
Minimal, reproducible code sample, a copy-pastable example if possible
import numcodecs
import numpy as np

item = np.array([(1, 'dataset_1', {'source': '.', 'path': '/dataset_1', 'object_id': None, 'source_object_id': None}),
       (2, 'dataset_2', {'source': '.', 'path': '/dataset_2', 'object_id': None, 'source_object_id': None})],
      dtype=[('id', '<i4'), ('name', 'O'), ('reference', 'O')])
cs = numcodecs.JSON()

en = cs.encode(item)
out=cs.decode(en)

This returns:
 File "~./json.py", line 75, in decode
    dec[:] = items[:-2]
    ~~~^^^
ValueError: setting an array element with a sequence. The requested array would exceed the maximum number of dimension of 1.

Version and installation information

numcodecs: the dev branch via git clone and pip install -e .
mac OS
python 3.11

Any ideas?

The trouble is this line: https://github.com/zarr-developers/numcodecs/blob/main/numcodecs/json.py#L62
buf.dtype.str

is '|V20', for a dtype [('id', '<i4'), ('name', 'O'), ('reference', 'O')]. We should be encoding the complex type.


[1669] Rename database in QA and Staging

Context
Use the default database created by terraform
Changes proposed in this pull request
Change the DB connection string in QA and Staging
Guidance to review
The app should have content
Link to Trello card
https://trello.com/c/HSsFc0wX

 Rename apply for TT database


implementation of readable signposts using DialogManager #144

Summary
This PR implements the "Insert signposts on the maps" task and relates to #144.

On the Farm_new map, above signs, there are new rect objects on the Interactions layer named sign with custom property label
This label is used as a key mapped to the character name to trigger DialogManager - a bit hacky, but actually looks clean
the Sprite class has been extended to store custom properties read from TiledMap

Media

Checklist

[* ] I have tested this change locally and it works as expected.
[*] I have made sure that the code follows the formatting and style guidelines of the project.

Labels
type: feature, game-signpost

the read signpost screen (Dialog) is triggered using Interact action (space)

New signpost graphics adde

Thank you, this looks good!

There are many random signs on the minigame map, is this intended? I think we should remove them

Thank you, this looks good!

There are many random signs on the minigame map, is this intended? I think we should remove them

@sloukit which ones do consider random? Please let me know which exactly we should remove,
I've added a few just by the map borders since they seemed to fit naturally with the new emojis.
There were also some signs on the Town map, but on the wrong layer in Tiled, so they didn't show in the actual game (e.g. Merchant). Should I remove those as well?


Switch to using gcloud auth configure-docker instead of gcloud docker -a

While this is failing here (probably due to stale creds), I've verified that the dockercfg-generator tests work with Docker 20.10.


What should we do if points_min=0？

Hello, handsome bro
in trainer.py  ,it is get_next_point
    points_min = min(points_list)
    num_clicks = self.args.num_clicks if mode == 'train' else self.args.num_clicks_validation
    click_size = points_min if num_clicks > points_min else num_clicks
    dynamic_size = random.randint(1, click_size) if self.args.dynamic and mode == 'train' else click_size

Will there be any issues with obtaining dynamic_size? What should we do if points_min=0.

Hi,
if point_min=0, which means you don't provide the point prompt. You can simply comment out that part.
dynamic_size = random.randint(1, click_size), this assumes the clink_size is >=1.
Hao

Handsome bro,
will there be a situation where to_point_mask=0?
If the corresponding value is 0, there will be a problem in
points=torch. argwhere (to_point_mask [i]).
How can this problem be solved to_point_mask=0?

Hi,
It can be custom designed by commenting out this part if you don't want to use point prompt.
I designed to use 1 point for fair comparison for different methods since they all use the 1 point prompt at least.
theoretically, this situation can be appeared. For such situation, the dice score is 100, and no need to provided any prompt.
You need to comment out this part for this situation.


Obsolete    GO:0098933 disruption by symbiont of host cell envelope

Unnecessary grouping class
No annotations, no mappings

After discussion with @SIBVirus, decided to keep


@google-cloud/datastore save seems broken with grpc 1.1.0

With the latest 1.1.0 version datastore save returns an 503 error "connect failed"
Downgrading to grpc 1.0.1 in my project seems to fix the issue.
https://github.com/grpc/grpc/issues/9518
Environment details

OS: ubuntu / appengine nodejs
Node.js version: 6.9.4
npm version: 3.10.10
google-cloud-node version:
"@google-cloud/datastore": "^0.6.1",
"@google-cloud/storage": "^0.6.1",

Steps to reproduce
datastore save method returns error

I haven't reproduced the 503, however, I noticed the request hanging in 1.1.0 and coming back instantly in 1.0.1.
To anyone affected by this, npm install google-cloud and access your sub-services through there.
@murgatroid99 -- any ideas what could have caused this? Currently, it looks like we'd have to roll back and force 1.0.1.
Here's repro code:
$ npm init -y
$ npm install --save @google-cloud/datastore
$ touch index.js

'use strict'

var datastore = require('@google-cloud/datastore')({
  projectId: 'nth-circlet-705'
})

datastore.save({
  key: datastore.key(['Kind', 1]),
  data: { test: true }
}, console.log) // never called in<EMAIL_ADDRESS>

@dskdas thank you for analyzing and reporting this problem. I can confirm that I have the same problem and solution.
I have a question for the developers/maintainers; I have noticed that shrinkwrap is being used for the main google-cloud package, but not for the @google-cloud packages. Is there a specific reason for this? These kind of problems can be prevented if the @google-cloud packages are also shrinkwrapped.

We shrinkwrap the bundled package so that we can minimize duplicated dependencies for users of non-dedupe-ing npm versions (pre npm@3.0). We'd like to not have to shrinkwrap at all, however, it's clear it would have prevented this situation we're in now. The cost is delayed bug fixes from our dependencies and a more complicated release process, which means a slower delivery to the end user. This type of issue is rare, and can be addressed in a short matter of time by us. And users can fix by downgrading or following other specific advice that we share here.
I don't want to squash the idea, but I would prefer we have it in another issue so we can keep this clear for users who might hit the same bug and benefit from related advice. If anyone feels strongly about it, please open a new issue.

I can reproduce this problem. The root cause is a TCP connection failure, though I can't tell yet why it's happening.

I have tracked down the issue, and I will publish<EMAIL_ADDRESS>as soon as our tests pass and we can build the new packages.

@stephenplusplus I had a problem in the past with the main google-cloud package due to a bug in node-forge that was resolved upstream but still shrinkwrapped in google-cloud so I would prefer no shrinkwrap as well. I was just wondering if the decision to differentiate between the main google-cloud package and @google-cloud packages was taken deliberately. Thanks for clearing that up.

Gotcha, it's only because google-cloud wraps so many modules, and they all share so many common dependencies. npm install google-cloud was downloading 800MB+ :(

I have encountered what I think is a related error when deploying to Heroku:
 ><EMAIL_ADDRESS>install /tmp/build_0a211b45cbd6681b8d427f6cfaaeb0d3/node_modules/@google-cloud/compute/node_modules/grpc
       > node-pre-gyp install --fallback-to-build

       node-pre-gyp ERR! Tried to download: https://storage.googleapis.com/grpc-precompiled-binaries/node/grpc/v0.14.1/node-v51-linux-x64.tar.gz
       node-pre-gyp ERR!  System Linux 3.13.0-105-generic
       gyp ERR! command "/tmp/build_0a211b45cbd6681b8d427f6cfaaeb0d3/.heroku/node/bin/node" "/tmp/build_0a211b45cbd6681b8d427f6cfaaeb0d3/.heroku/node/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "build" "--fallback-to-build"<EMAIL_ADDRESS>"--module_name=grpc_node" "--module_path=/tmp/build_0a211b45cbd6681b8d427f6cfaaeb0d3/node_modules/@google-cloud/compute/node_modules/grpc/src/node/extension_binary"
       gyp ERR! cwd /tmp/build_0a211b45cbd6681b8d427f6cfaaeb0d3/node_modules/@google-cloud/compute/node_modules/grpc
       gyp ERR! node -v v7.4.0
       gyp ERR! node-gyp -v v3.4.0
       gyp ERR! not ok
       node-pre-gyp ERR! build error
       node-pre-gyp ERR! stack Error: Failed to execute '/tmp/build_0a211b45cbd6681b8d427f6cfaaeb0d3/.heroku/node/bin/node /tmp/build_0a211b45cbd6681b8d427f6cfaaeb0d3/.heroku/node/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js build --fallback-to-build<EMAIL_ADDRESS>--module_name=grpc_node --module_path=/tmp/build_0a211b45cbd6681b8d427f6cfaaeb0d3/node_modules/@google-cloud/compute/node_modules/grpc/src/node/extension_binary' (1)
       node-pre-gyp ERR! stack     at ChildProcess.<anonymous> (/tmp/build_0a211b45cbd6681b8d427f6cfaaeb0d3/node_modules/@google-cloud/compute/node_modules/grpc/node_modules/node-pre-gyp/lib/util/compile.js:83:29)
       node-pre-gyp ERR! stack     at emitTwo (events.js:106:13)
       node-pre-gyp ERR! stack     at ChildProcess.emit (events.js:191:7)
       node-pre-gyp ERR! stack     at maybeClose (internal/child_process.js:885:16)
       node-pre-gyp ERR! stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:226:5)
       node-pre-gyp ERR! System Linux 3.13.0-105-generic
       node-pre-gyp ERR! command "/tmp/build_0a211b45cbd6681b8d427f6cfaaeb0d3/.heroku/node/bin/node"<EMAIL_ADDRESS>"install" "--fallback-to-build"
       node-pre-gyp ERR! cwd /tmp/build_0a211b45cbd6681b8d427f6cfaaeb0d3/node_modules/@google-cloud/compute/node_modules/grpc
       node-pre-gyp ERR! node -v v7.4.0
       node-pre-gyp ERR! node-pre-gyp -v v0.6.28
       node-pre-gyp ERR! not ok
       Failed to execute '/tmp/build_0a211b45cbd6681b8d427f6cfaaeb0d3/.heroku/node/bin/node /tmp/build_0a211b45cbd6681b8d427f6cfaaeb0d3/.heroku/node/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js build --fallback-to-build<EMAIL_ADDRESS>--module_name=grpc_node --module_path=/tmp/build_0a211b45cbd6681b8d427f6cfaaeb0d3/node_modules/@google-cloud/compute/node_modules/grpc/src/node/extension_binary' (1)```

@dzoba grpc-0.14.1 is way too old. I believe your project is using some older version of @google-cloud/compute -- consider upgrade it to the latest release.

Our v1.1.x branch now contains the fix to the bug, and the package will be published shortly (probably later today, definitely by early tomorrow). I have verified that it works with the provided reproduction case, but it would be very helpful if you guys could verify that it works more generally.

I have now published<EMAIL_ADDRESS>This problem should now be fixed.

thank @murgatroid99  Just to confirm that it works for me.

Please try upgrading to the latest version of google-cloud or @google-cloud/pubsub.

I tested that datastore save works fine with the latest 1.1.1 grpc version (pulled in by @google-cloud/datastore).
Thanks

@stephenplusplus, I just need some clarification. I upgraded locally to @google-cloud/datastore and it seems to be working now.
However, whenever I deploy with gcloud app deploy, it seems to be having the same issue as before with the datastore timing out. Is my deployed version caching the old package somehow?

That could definitely be the case. Is it possible to clear out the cache?

I am also having the same issue on app engine. Investigating...

same here... our server (dev server) has been down for the last 2 days for this issues... I know that it is beta and it is not advised for production, but we are used to google beta that means nearly stable, while alpha means "likely to break".  Should we label it as Alpha instead ?

We found that<EMAIL_ADDRESS>fixed the issues when running locally on Mac OS X and in a Fedora 25 virtual machine, but the issue still seems to occur when running in an ubuntu based docker image.
We're using:

<EMAIL_ADDRESS><EMAIL_ADDRESS>
When running our app with GRPC_VERBOSITY=DEBUG npm start we continuously get these errors printed out at one per second:
I0203 16:19:44.762300262     631 dns_resolver.c:192]         dns resolution failed (will retry): {"created":"@1486138784.762281118","description":"getaddrinfo failed","file":"../src/core/lib/iomgr/resolve_address_uv.c","file_line":66,"os_error":"service not available for socket type"}

And our subscriber code is never called:
  pubsub.subscribe(topicName, subscriptionName, {
    ackDeadlineSeconds: 60
  }, (err, subscription, apiResponse) => {
    // THIS NEVER RUNS
    if (err) return callback(err)
    subscription.on('message', event => {
      // do stuff with event
    })
  })

I would like to investigate that DNS error. Do you have a small complete script that reproduces this error?

@murgatroid99 https://github.com/GoogleCloudPlatform/google-cloud-node/issues/1946#issuecomment-276398600
@djbeaumont I've just deployed on Heroku which is based on Ubuntu and it works..... (and it deploys in a fraction of the time...)

I tried running the reproduction case in that comment in a Fedora 25 docker image, and I successfully got a response with no DNS errors using both Node 6 and Node 7.

I just managed to reproduce it in a clean repository set aside from my company's libraries. Just writing up some instructions now.

@murgatroid99, I've put an example up here: https://github.com/djbeaumont/grpc-issue
Please let me know if you've got any questions.

OK, when I run that, I see exactly the errors that you described.

I believe I have found a solution (or at least a workaround) for the DNS error you are experiencing in the Ubuntu docker image: in the Dockerfile, add the line RUN apt-get install netbase. Among other things, netbase includes the file /etc/services, which is required to resolve the https service to the port 443.

Adding that to our docker image works around the problem for me too 👍

I also noticed that all of my (remote) deployed google cloud functions stopped being able to store data to google cloud datastore about a week ago. At that time, cloud console was logging a grpc network error. After the grpc 1.1.1 update, the network error is no longer logged, but data is still not being stored to cloud datastore for remotely deployed functions. (Note Locally deployed cloud functions do store data to the remote cloud datastore.) Bundling the node_modules directory with the remotely deployed functions doesn't solve the problem either. ((With package.json dependencies: "@google-cloud/datastore": "^0.6.1" and "grpc": "^1.1.1") When the node_modules directory is included with the remote deployed function, the cloud console log shows a "function timeout" error. When the node_modules directory is not included, the cloud function fails (times-out) silently.
It kinda seems like the google cloud functions network is not able to see the google datastore network. Since my local dev server can see both networks, it doesn't have the same problem.
Any fix update or insight would be greatly appreciated. / Thanks.

I have the same problem then @tobeach.

@ofrobots:
Hmmm... there is no issue when the cloud function is run on a local server with the same source tree. (i.e no netbase issue.) But, when the exact same function and node_modules bundle is deployed to the remote google cloud functions environment, it can no longer save data to cloud datastore. - Note that the same remotely deployed function worked perfectly up until a week ago.

@tobeach The above linked workaround in the Node.js docker image should resolve the problem. Cloud Functions is set to pick up the docker image with the fix sometime this week. /cc swalkowski

I believe this has either already been resolved, or will be when you update to google-cloud 0.46.2 which was just released. I'm going to close, but just let me know if this isn't resolved.


"as" prop is breaking rebass component usage

Environment
npx envinfo --system --binaries --npmPackages styled-components,babel-plugin-styled-components --markdown --clipboard
## System:
 - OS: macOS High Sierra 10.13.6
 - CPU: (8) x64 Intel(R) Core(TM) i5-8259U CPU @ 2.30GHz
 - Memory: 138.20 MB / 16.00 GB
 - Shell: 5.3 - /bin/zsh
## Binaries:
 - Node: 8.11.2 - /usr/local/bin/node
 - Yarn: 1.13.0 - /usr/local/bin/yarn
 - npm: 6.7.0 - /usr/local/bin/npm
 - Watchman: 4.9.0 - /usr/local/bin/watchman

Reproduction
https://codesandbox.io/s/56pvp6y5x
Steps to reproduce
I created 2 components directly viewed in the codesandbox link - 1) a custom "passthrough" component that is wrapped by a styled tag, and 2) a Rebass component wrapped by a styled tag. In the codesandbox link, I have a few examples. The issue comes up when the as prop is being used.
Expected Behavior
Both the passthrough and rebass components should be styled when being passed styling props (according to rebass/styled-system documentation), regardless of there being an as prop being passed to either component.
Actual Behavior
The as prop is causing the 1st component to not have any styling, OR render the passthrough component at all.

Please use the new forwardedAs prop introduced in 4.3.x 😄
https://www.styled-components.com/docs/api#forwardedas-prop

So when you wrap a custom component (non primitive, aka "div" or non-styled-component) in our HOC, e.g. styled(CustomComponent) if you use the "as" prop, that actually totally replaces the underlying component being rendered similar to the .withComponent API.
Since rebass components are styled-components, wrapping a rebass Box in styled() is totally fine, however in the case of your BoxOne component which introduces an interim function component, it's no longer a styled-component and you need to use the new forwardedAs prop to send your intended "as" down to the lower component layer.
Here's your sandbox updated:
https://codesandbox.io/s/styled-components-rebass-bug-18fnp?fontsize=14

This will be a lot more straightforward if https://github.com/facebook/jsx/issues/81 was implemented, in which case you could just specify where the "as" prop should be consumed via the namespace key :sigh:

Thanks a lot for updating this @probablyup ! Good to know it was addressed 😃

@probablyup Was the forwardedAs prop reverted or is it still available?

@chasemccoy It's in 4.3.x


Saving sessions with walletconnect v2 flutter package

Hello i have been having issues with getting the session that currently active when a user connects their wallet. I'm using the Flutter SDK.
The Sdk has the function of getActiveSession which returns nothing when I call it.
I posted this on the discord channel but it seems this is the place where I can get responses.

To follow up on this conversation, this is our code.
Future checkSavedWallets() async {
await Future.delayed(const Duration(seconds: 2));
final sessions = AppSignClient.instance.signClient.getActiveSessions();
print('SESSIONS $sessions');
if (sessions.isNotEmpty) {
for (var i in sessions.entries) {
if (i.value.requiredNamespaces!.values.first.chains!
.contains(EthereumConnector.chain)) {
state.connectors.add(
EthereumConnector.walletConnectorFromSessionData(i.value),
);
} else if (i.value.requiredNamespaces!.values.first.chains!
.contains(BinanceConnector.chain)) {
state.connectors.add(
BinanceConnector.walletConnectorFromSessionData(i.value),
);
}
}
state = state.copyWith();
}
}
This function is called everytime the app is opened and even if we have connected to a session before it was closed, getActiveSession still returns an empty map.
class AppSignClient {
AppSignClient._private();
static final AppSignClient _instance = AppSignClient._private();
static AppSignClient get instance => _instance;
late Web3App signClient;
Future initClient() async {
signClient = await Web3App.createInstance(
relayUrl: 'wss://relay.walletconnect.com',
projectId: '<OUR_PROJECT_ID>',
metadata: const PairingMetadata(
name: 'Pouch',
description: 'A dapp that can request that transactions be signed',
url: 'https://walletconnect.com',
icons: ['https://avatars.githubusercontent.com/u/37784886'],
),
memoryStore: true,
);
}
}
This is the content of AppSignClient.
static const String chain = 'eip155:1';
@override
Web3App get signClient => AppSignClient.instance.signClient;
@override
Future initWallet() async {
ConnectResponse response = await signClient.connect(
requiredNamespaces: {
'eip155': const RequiredNamespace(
chains: [chain],
methods: [
'eth_signTransaction',
'eth_sendTransaction'
],
events: [],
),
},
);
Uri? uri = response.uri;
launchUrl(uri!);

try {
  session = await response.session.future;
} catch (e) {
  rethrow;
}

return session.acknowledged;

}

memoryStore: true,

Remove this line from the initialization to make the sessions be persisted to local storage when they update.
memoryStore set to true basically tells the library "Save nothing, delete it all when my app closes"
If removing that line doesn't resolve the issue, let me know, otherwise, please close this issue.

Thanks that solved the issue


BUG: Can't connect to Auth Emulator with Go despite setting env variable

Operating System version: MacOS 13.1
Firebase SDK version: 4.10.0
Firebase Product: auth + storage

I am trying to use the Firebase emulators in an API I'm building with Go. I've got the Firestore emulator working fine, but the Auth one is being ignored and instead my actual Firebase project's Authentication is being used.
// .envrc

export GOOGLE_APPLICATION_CREDENTIALS=./record-dev-sa.json
export FIRESTORE_EMULATOR_HOST=localhost:8080
export FIREBASE_AUTH_EMULATOR_HOST=localhost:9099
export GCLOUD_PROJECT=record-dev-8198f

// serve.go
app, err := firebase.NewApp(ctx, nil)
if err != nil {
  return err
}

client, err := app.Auth(ctx)
if err != nil {
  return nil, err
}

I've tried setting the GCLOUD_PROJECT env variable as well but it isn't changing the results. I expected this to behave the same as the Firestore Emulator, where it automatically picks up the env variable without any other changes required

I've just had the exact same problem... Imagine my delight at finding this issue, and my disappointment that it was closed with no comment. It's OK though, I figured it out.
Still here? Oh, right, sure: There's some out of date gcloud documentation floating about which instructs you to:
go get firebase.google.com/go
But what you really want (at time of writing) is:
go get firebase.google.com/go/v4
You're welcome.


fix(): fix for npm3

npm3 uses dedup and word-warp is not in the node_modules dir from __dirname

Current coverage is 100.00%

Merging #9 into master will not affect coverage as of 8f6508a

@@            master      #9   diff @@
======================================
  Files            2       2
  Stmts          142     142
  Branches         0       0
  Methods          0       0
======================================
  Hit            142     142
  Partial          0       0
  Missed           0       0

Review entire Coverage Diff as of 8f6508a

Powered by Codecov. Updated on successful CI builds.

awesome! thanks @moperacz.


[stable/coredns] Add ReadinessProbe

What this PR does / why we need it:
Adds a readinessProbe
Which issue this PR fixes
(optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close that issue when PR gets merged)

fixes #

Special notes for your reviewer:
Checklist
[Place an '[x]' (no spaces) in all applicable fields. Please remove unrelated fields.]

[x] DCO signed
[x] Chart Version bumped
[x] Variables are documented in the README.md
[x] Title of the PR starts with chart name (e.g. [stable/chart])
[x] Tested and applied the change to a live cluster

@shashidharatd tested it, ptal :)

/retest

/assign @andor44 Would you please have look on this?

/assign @andor44

/assign
/ok-to-test
/lgtm
also added @andor44 as a trusted collaborater


Add SQLite

[x] Have you signed the Contributor License Agreement?
[x] Have you checked that there aren't other open pull requests for the same manifest update/change?

[ ] Does your manifest conform to the 1.2 schema?

Note: <path> is the name of the directory containing the manifest you're submitting.

@microsoft-github-policy-service agree

@microsoft-github-policy-service agree

@msftbot .zip

[Policy] Reset Feedback

@wingetbot run


Added getNumberOfCurrentPlayers

If you don't like the apps.js name, feel free to give me a recommendation for an alternative name.

Rebased onto 0.6.8.


Choosing which display to change

I have a SUW monitor as my main display and just got a dummy HDMI dummy plug for sunshine/moonlight.
When I connect through moonlight to sunshine, the correct screen is streamed (I wrote the correct output name in config-> audio/video) however the resolutionAutomation is changed on my main display.
Is there a way to tell it to work on the same display that is streamed to Moonlight?

Due to various issues with Sunshine in terms of streaming a specific display (it intermittently breaks when windows changes the display names), I do not recommend using it. Instead, use this script in conjunction with the resolution swap, just make sure its installed first, that way the swap happens before the resolution change
https://github.com/Nonary/MonitorSwapAutomation