FactoryGuy.hasMany fails with error 'undefined' is not an object (evaluating 'traits[trait]')

I'm running into this issue with trying to test a model that has an association on it. I found a temporary solution but I've yet to understand the root cause or how to test it (I'm new to ember). Anyway, here is what I hope is all of the relevant info
The models
// app/group/model.js
import DS from 'ember-data';

export default DS.Model.extend({
  name: DS.attr('string'),

  users: DS.hasMany('user')
});

// app/user/model.js
import DS from 'ember-data';

export default DS.Model.extend({
  name: DS.attr('string'),
  email: DS.attr('string'),
  role: DS.attr('string'),
  last_signed_in_at: DS.attr('datetime')
});

The factories
// tests/factories/group.js
import FactoryGuy from 'ember-data-factory-guy';
import faker from 'faker';

FactoryGuy.define('group', {
  default: {
    name: faker.company.companyName()
  },

  traits: {
    with_users: { users: FactoryGuy.hasMany('user', 4) }
  }
});

// tests/factories/user.js
import FactoryGuy from 'ember-data-factory-guy';
import faker from 'faker';

FactoryGuy.define('user', {
  default: {
    name: faker.name.findName(),
    email: faker.internet.email(),
    role: 'member',
    last_signed_in_at: Date.now()
  },

  admin_user: {
    role: 'admin'
  }
});

The test
// tests/unit/group/model-test.js
import Ember from 'ember';
import startApp from 'client/tests/helpers/start-app';
import { module, test } from 'qunit';

import { make } from 'ember-data-factory-guy';

var application;

module('Group model', {
  beforeEach: function() {
    application = startApp();
  },

  afterEach: function() {
    Ember.run(application, 'destroy');
  }
});

test('it exists', function(assert) {
  let group = make('group');
  assert.ok(!!group);
  assert.ok(group.get('name'));
});

test('it can have user', function(assert){
  let group = make('group','with_users');

  assert.equal(group.get('users.length'), 4, '4 of them');
});

The error
not ok 3 PhantomJS 1.9 - Group model: it can have user
    ---
        actual: >
            null
        message: >
            Died on test #1     at http://localhost:7357/assets/test-support.js:2809
                at http://localhost:7357/assets/client.js:3188
                at http://localhost:7357/assets/vendor.js:150
                at tryFinally (http://localhost:7357/assets/vendor.js:30)
                at http://localhost:7357/assets/vendor.js:156
                at http://localhost:7357/assets/test-loader.js:29
                at http://localhost:7357/assets/test-loader.js:21
                at http://localhost:7357/assets/test-loader.js:40
                at http://localhost:7357/assets/test-support.js:5578: 'undefined' is not an object (evaluating 'traits[trait]')
        Log: >
    ...

What causing the error is the association line in my group factory trait for users. If I remove the hasMany, I receive no error.
traits: {
 with_users: { users: FactoryGuy.hasMany('user', 4) }
}

What fixes it
So what's bombing out there is model-definition.js
  this.build = function (name, opts, traitArgs) {
    var traitsObj = {};
    traitArgs.forEach(function (trait) {
      $.extend(traitsObj, traits[trait]);
    });
...

For some reason, the extractArguments method is actually setting traits = undefined which is then causing that traitArgs argument in build() to equal an array with a single value of undefined ([undefined])
Now, I have no idea if that is desired or not, i've only dug around trying to get this to work for an hour or two. What got things to work for me was putting in a guard clause.
traitArgs.forEach(function (trait) {
  if (!trait) return;
  $.extend(traitsObj, traits[trait]);
});

If that really does fix it, great. Otherwise, I hope all of this rambling is enough to point you in the right direction of fixing the bug or telling me what obvious thing I missed. Thanks!
Versions
DEBUG: -------------------------------
ember.debug.js:5197DEBUG: Ember                     : 1.11.1
ember.debug.js:5197DEBUG: Ember Data                : 1.0.0-beta.16.1
ember.debug.js:5197DEBUG: jQuery                    : 1.11.3
ember.debug.js:5197DEBUG: Ember Simple Auth         : 0.8.0-beta.2
ember.debug.js:5197 DEBUG: Ember Simple Auth Devise  : 0.8.0-beta.2
ember.debug.js:5197 DEBUG: Ember Simple Auth Testing : 0.8.0-beta.2
ember.debug.js:5197 DEBUG: -------------------------------
    "ember-data-factory-guy": "1.0.5",

@mattmcmanus, I pushed a fix for that case and it is on v1.0.7 .. so can you upgrade to that version of factory guy and let me know if that fixes it for you. Thanks for the rambling report .. it helps to see the whole story, even though in this case I could not quite recreate it.

Works for me.
Thanks Daniel. I knew this one would be hard to reproduce, which usually means there is something that I was missing but I working solo on this. I figured the best thing was to get another set of eyes on it. Thanks for the quick turn around!

No problem @mattmcmanus , and there are always these little edge cases that just poke their noses in every once in a while, so even though I could not reproduce, ( and your tests looked fine to me btw .. pretty straighforward, no funny business ) , so it was good to address it and so the next person does not find it.


chore: release main

:robot: I have created a release beep boop
baggie: 2.1.2
2.1.2 (2023-08-04)
Bug Fixes

core: Fix bug in nonNumberFallback (dc66902)

core: 1.4.2
1.4.2 (2023-08-04)
Bug Fixes

core: Fix bug in nonNumberFallback (dc66902)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/saxofonsolo/baggie/releases/tag/baggie-v2.1.2 :sunflower:


EID 828 - Move extraction logic for MSA version from request id and add extraction for eidas/sha1

See commits for further information.

Erm... Codacy isn't happy about a bunch of stuff. Can we look into fixing them please?


Support unimplemented HostedMode MCE

Issue: https://github.com/stolostron/backlog/issues/25920
Creating a Multiclusterengine with the annotation deploymentmode: Hosted will tell the operator to perform a hosted-mode deployment of mce, which currently does nothing.

/lgtm


Close this bad boy

I figured it out.

Well done :grinning:

Did you end up adding bbcfmt.vo.llnwi.net to zones.override or were there additional domains?


Size mismatch for embeddingnet.masks.weight in pretrained model

Hi, I have a question about the number of type spaces in the pre-trained model.
As in the main.py, the default num_rand_embed is 4. But when I load the pre-trained model, it shows that the shape of embeddingnet.masks.weight is [66,64], while my current tnet is [4, 64]. May I know if the num_rand_embed in the pretrained model is 66?
Many thanks!

add -> keepdim=True <- in norm = torch.norm(masked_embedding, p=2, dim=2) + 1e-10 so that it becomes norm = torch.norm(masked_embedding, p=2, dim=2, keepdim=True) + 1e-10

But using this ,
sample_images = next(iter(test_loader)).to(device)
sample_embeddings = tnet.embeddingnet(sample_images)

I get sample_embeddings of shape [256, 67, 64] if sample_images is of [256, 3, 112, 112]
Do you get the same shape? (emphasis on the 67)
Also I get  len(test_loader.dataset.typespaces) as 66,
keepdim=True makes it 67?


MacOS Version

Just a question about the ModpackManager: Would you ever consider making a Mac app or something?

It will be hard as I do not have a Mac computer
Json1040 @.***> 於 2024年9月23日 週一 13:02 寫道：

Just a question about the ModpackManager: Would you ever consider making a
Mac app or something?
—
Reply to this email directly, view it on GitHub
https://github.com/Dimserene/ModpackManager/issues/2, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AHTHUTTBRYL5BCC4FZFYM6TZX6OFRAVCNFSM6AAAAABOVIO7ZWVHI2DSMVQWIX3LMV43ASLTON2WKOZSGU2DCNJXHE4DGOA
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

Can you try to do this for me? This is a rather rough way to utilize the manager, but it should work on every system as intended.
First, download this script:
https://github.com/Dimserene/ModpackManager/blob/main/ModpackManager - qt22.py
And install python on your device:
https://www.python.org/downloads/
then use this method to install required libraries and run the script:
1.open terminal in the same directory as manager
2.create virtual environment in python: python3 -m venv myenv
3.start the virtural environment: source myenv/bin/activate
4.install all dependancies: pip install PyQt6 GitPython requests
5.run the manager script: python 'ModpackManager - tk22.py'
6.download and manually install the modpacks (copy paste Mods folder into the correct directory), and launch game
after that, next time if you wish to use the manager, just do step 3&5

I can check it out momentarily, and get back to you on it.

Didn’t mean to press that button.


Add slack-sdk 3.19.5

Changelog: https://github.com/slackapi/python-slack-sdk/releases
License: https://github.com/slackapi/python-slack-sdk/blob/v3.19.5/LICENSE
Requirements: https://github.com/slackapi/python-slack-sdk/blob/v3.19.5/setup.py
Actions:

Skip py<36

Remove noarch python for slack-sdk output

Add --no-deps to script

Add host for noarch slack_sdk and add python to run

Add aiohttp to test/requires

Add description

Add license_family

Update doc and dev urls

Linter check found the following problems:
Traceback (most recent call last):
  File "/opt/conda/envs/linter/bin/conda-lint", line 11, in
    sys.exit(main())
  File "/opt/conda/envs/linter/lib/python3.10/site-packages/anaconda_linter/run.py", line 107, in main
    result = linter.lint(
  File "/opt/conda/envs/linter/lib/python3.10/site-packages/anaconda_linter/lint/__init__.py", line 620, in lint
    msgs = self.lint_file(
  File "/opt/conda/envs/linter/lib/python3.10/site-packages/anaconda_linter/lint/__init__.py", line 692, in lint_file
    messages = self.lint_recipe(
  File "/opt/conda/envs/linter/lib/python3.10/site-packages/anaconda_linter/lint/__init__.py", line 749, in lint_recipe
    res = self.check_instances[check].run(recipe, fix)
  File "/opt/conda/envs/linter/lib/python3.10/site-packages/anaconda_linter/lint/__init__.py", line 258, in run
    self.check_deps(recipe.get_deps_dict())
  File "/opt/conda/envs/linter/lib/python3.10/site-packages/anaconda_linter/lint/check_build_help.py", line 349, in check_deps
    build_file = self.recipe.get(script)
  File "/opt/conda/envs/linter/lib/python3.10/site-packages/anaconda_linter/recipe.py", line 583, in get
    raise KeyError(f"No '{path}' in Recipe {self}") from None
KeyError: "No 'outputs/0/script' in Recipe /tmp/abs_47on798g3f/clone/recipe/"
ERROR conda.cli.main_run:execute(47): conda run conda-lint /tmp/abs_47on798g3f/clone failed. (See above for error)

Linter check found the following problems:
Traceback (most recent call last):
  File "/opt/conda/envs/linter/bin/conda-lint", line 11, in
    sys.exit(main())
  File "/opt/conda/envs/linter/lib/python3.10/site-packages/anaconda_linter/run.py", line 107, in main
    result = linter.lint(
  File "/opt/conda/envs/linter/lib/python3.10/site-packages/anaconda_linter/lint/__init__.py", line 620, in lint
    msgs = self.lint_file(
  File "/opt/conda/envs/linter/lib/python3.10/site-packages/anaconda_linter/lint/__init__.py", line 692, in lint_file
    messages = self.lint_recipe(
  File "/opt/conda/envs/linter/lib/python3.10/site-packages/anaconda_linter/lint/__init__.py", line 749, in lint_recipe
    res = self.check_instances[check].run(recipe, fix)
  File "/opt/conda/envs/linter/lib/python3.10/site-packages/anaconda_linter/lint/__init__.py", line 258, in run
    self.check_deps(recipe.get_deps_dict())
  File "/opt/conda/envs/linter/lib/python3.10/site-packages/anaconda_linter/lint/check_build_help.py", line 349, in check_deps
    build_file = self.recipe.get(script)
  File "/opt/conda/envs/linter/lib/python3.10/site-packages/anaconda_linter/recipe.py", line 583, in get
    raise KeyError(f"No '{path}' in Recipe {self}") from None
KeyError: "No 'outputs/0/script' in Recipe /tmp/abs_3c_ogzeym9/clone/recipe/"
ERROR conda.cli.main_run:execute(47): conda run conda-lint /tmp/abs_3c_ogzeym9/clone failed. (See above for error)

Linter check found the following problems:
Traceback (most recent call last):
  File "/opt/conda/envs/linter/bin/conda-lint", line 11, in
    sys.exit(main())
  File "/opt/conda/envs/linter/lib/python3.10/site-packages/anaconda_linter/run.py", line 107, in main
    result = linter.lint(
  File "/opt/conda/envs/linter/lib/python3.10/site-packages/anaconda_linter/lint/__init__.py", line 620, in lint
    msgs = self.lint_file(
  File "/opt/conda/envs/linter/lib/python3.10/site-packages/anaconda_linter/lint/__init__.py", line 692, in lint_file
    messages = self.lint_recipe(
  File "/opt/conda/envs/linter/lib/python3.10/site-packages/anaconda_linter/lint/__init__.py", line 749, in lint_recipe
    res = self.check_instances[check].run(recipe, fix)
  File "/opt/conda/envs/linter/lib/python3.10/site-packages/anaconda_linter/lint/__init__.py", line 258, in run
    self.check_deps(recipe.get_deps_dict())
  File "/opt/conda/envs/linter/lib/python3.10/site-packages/anaconda_linter/lint/check_build_help.py", line 349, in check_deps
    build_file = self.recipe.get(script)
  File "/opt/conda/envs/linter/lib/python3.10/site-packages/anaconda_linter/recipe.py", line 583, in get
    raise KeyError(f"No '{path}' in Recipe {self}") from None
KeyError: "No 'outputs/0/script' in Recipe /tmp/abs_24ml0k0odw/clone/recipe/"
ERROR conda.cli.main_run:execute(47): conda run conda-lint /tmp/abs_24ml0k0odw/clone failed. (See above for error)


added close_stop.py

Add one simple function to return close bus stops as a panda dataframe. You can simply len() to count the number of stops close by.

Generated CSV files containing 300,000 spots.

Takuya, a few things:

please you put this in a subdirectory of DataGeneration as its sort of a utility, and not necessarily an integrated part of the package at this point (we can integrate it after). I'd like to keep things organized.

can you untrack that 300k line .csv? Although not a huge file, that's something that should probably go in the slack channel.

And could you revert your change to the .gitignore? Having *.csv in the .gitignore is super useful for testing this thing as .csv's tend to accumulate. In the future, if you need to add something to a repository that cannot be added normally because of a .gitignore, you can add it anyway with "git add -f ".

Could you remove the 300k line .csv file from the request? We don't need a file of that size and it doesn't really serve a purpose as far as I can tell.
Also, have you taken a look at UniformMapGenerator in DataGeneration? It seems to do something very similar to what you're doing in close_stop.py. What is the purpose of close_stop.py?


"[error] Unexpected Info" when using modified mongo plugin

Environment

OS: MacOS High Sierra
Erlang/OTP: 20
EMQ: 2.3.1 (built from master branch)

Description
I have done a very simple modification to the emq-auth-mongo plugin in order to make it support expirable subscriptions. For that, I modified the check_acl function to instead of just iterating over the {pubsub} array from the first occurrence of {username} in the ACL collection, iterate over all of existing arrays – using find instead of find_one in the mongo_api call. You can check my modification in here.
To simply illustrate what's been done, in this case:
{ "_id" : ObjectId("5a3d08de0235bce8d4cbdc48"), "pubsub" : [ "ab" ], "username" : "joao" }
{ "_id" : ObjectId("5a3d08de0235bce8d4cbdc49"), "pubsub" : [ "cd" ], "username" : "joao" }
{ "_id" : ObjectId("5a3d08de0235bce8d4cbdc4a"), "pubsub" : [ "zz" ], "username" : "joao" }
Default mongo plugin wouldn't allow user joao to subscribe in topics "cd" and "zz", which is the feature I'm trying to create.
Now, although my modification work as intended, whenever a user subscribes to a room, being allowed or not, I get the following error:
14:16:12.356 [error] Unexpected Info: {ack,<0.2069.0>,{error,normal}}
I tried to debug the code in order to find what was happening, but I didn't get anywhere close. This only happens in subscribe (doesn't happen with publish) and also doesn't happen when ignore is returned. That leads to the conclusion that the Cursor is causing the issue – which only makes things more confusing.
If anyone could help me understand what is happening and how impactful this might be, I would really appreciate.
Thanks in advance!

Hi, @jlgm I has checked your plugin and reproduced the issue.
This error log  printed by emqtt_client.erl  L286
The {ack,<0.2069.0>,{error,normal}} message will be received, when you call the mc_cursor:rest(Cursor) function.

Hi, @HJianBo. Thank you for your reply!
I was able to identify that the Cursor was causing the issue – in fact, even if you don't use mc_cursor:rest but instead use mc_cursor:close, the same error will happen.
Do you think this is something that might crash my application or I can simply ignore it for now?

@jlgm The log mean that an unexpected message sent to the MQTT connection process, and which is ignored. This will not crash EMQ broker.
@HJianBo Please fix the issue in 2.4-beta.1 release, Thanks.

Close as it is probably fixed in https://github.com/emqx/mongodb-erlang v3.0.7


Password Validation

The password field currently shows validation for a minimum of 6 characters. Improve the validation by adding feedback for weak passwords (e.g., suggest using numbers, uppercase letters, and special characters).

i want to work on it

i want to work on it

@fineanmol  Please assign this issue

I would also like to work on this issue

@fineanmol  Please assign this issue to me

I will make sure to put on the constraints for Weak Password such as must include special characters, numbers, caps letters.
Kindly Assign this issue to Me


Pipeline executors don't start causing job execution to fail - 403

rancher/rancher:master-head ff9cf13b9
Opening this out of rancher/rancher#21777 as it is not related to upgrade specifically, and blocks the basic pipeline workflow. This does not occur in v2.2.8.

Deploy Rancher
Create cluster
Create a pipeline
Run a job

The build executors never finish setting up, and in Jenkins pod logs see:

Aug 26, 2019 3:31:46 PM io.fabric8.kubernetes.client.dsl.internal.WatchConnectionManager$1 onFailure
WARNING: Exec Failure: HTTP 403, Status: 403 -
java.net.ProtocolException: Expected HTTP 101 response but was '403 Forbidden'
at okhttp3.internal.ws.RealWebSocket.checkResponse(RealWebSocket.java:229)
at okhttp3.internal.ws.RealWebSocket$2.onResponse(RealWebSocket.java:196)
at okhttp3.RealCall$AsyncCall.execute(RealCall.java:206)
at okhttp3.internal.NamedRunnable.run(NamedRunnable.java:32)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)

I can confirm that this upgrading the kubernetes version is why the current version of the jenkins plugin is no longer working for us. The plugin has been updated to be compatible: https://github.com/jenkinsci/kubernetes-plugin/commit/98b4f430c4c42c5955cfb507dfa1010277915871
Dax's fix upgrades the plugin.

@rmweir can you get this updated in rancher? I think you just need to update here: https://github.com/rancher/types/blob/master/apis/management.cattle.io/v3/tools_system_images.go#L22
cc @loganhz @gitlawr

I have release for it: I have a release for it: https://github.com/rancher/pipeline-jenkins-server/releases/tag/v0.1.4

rancher/rancher:master-head 57508ebba

Created cluster
Enabled pipeline
Pipeline executed successfully


Create darklight.html

#556

@sv410 Why you made 3 different PRs for 3 different files. Please make 1 PR. Otherwise I can't check.


Update Neo4j-Driver Version to 5.5

Add the new interfaces that were added to the IResultCursor and IDriver in 5.5

https://github.com/neo4j/neo4j-dotnet-driver/issues/678


No events logged for the reth::cli=info target in Execution Stage

Describe the bug
when transitioning from SenderRecovery to Execution, default cli logs are stuck at:

2023-03-29T21:02:50.056149Z  INFO Stage committed progress stage=SenderRecovery checkpoint=3185000

however, it moved into Execution Stage
when restarting the node the last thing logged is

INFO Starting consensus engine

seems like there's no reporting from execution that is logged to stdout
this is possibly a dup of #2000
Steps to reproduce

Node logs
No response
Platform(s)
No response
What version/commit are you on?
No response
Code of Conduct

[X] I agree to follow the Code of Conduct

Is it possible that the new thread spawned at every iteration of the stage (https://github.com/paradigmxyz/reth/blob/main/crates/stages/src/stages/execution.rs#L211) blocks the notifications' receivers ? Because logs internal to the stage such as 2023-03-27T20:50:04.147287Z  INFO sync::stages::execution: Sync iteration finished stage_progress=5125000 done=false are written to file.

notifications' receivers

what do you mean exactly?

https://github.com/paradigmxyz/reth/blob/main/crates/stages/src/pipeline/event.rs#L65
Well there is only one listener (the node)

I assume this is an issue with this section
https://github.com/paradigmxyz/reth/blob/6261262a203b35870ad52f22585f14e51adbd7a0/bin/reth/src/node/events.rs#L33-L51
but I don't fully understand the is notable logic yet.
perhaps @rkrasiuk or @onbjerg can yet
in any case, event reporting during execution stage is definitely broken

In my written logs, last message about SenderRecovery is

2023-03-27T20:49:27.158652Z  INFO execute{stage=SenderRecovery}: sync::stages::sender_recovery: Sync iteration finished stage_progress=16921047 done=true
2023-03-27T20:49:27.158659Z  INFO execute{stage=SenderRecovery}: sync::pipeline: Stage made progress stage=SenderRecovery stage_progress=16921047 done=true

At this point a PipelineEvent::Ran is sent to the listeners and result.done is true (as in the log), so a message announcing that the SenderRecovery stage has finished should be printed independently of the Execution stage

@mattsse I cannot reproduce this locally on commit 7263c9a644203d94aeec127221e9484052a44058 and before, so it is something recent. My best guess is that it is most likely that the channel we use here to get the events from the pipeline no longer exists/is broken on some sync controller state changes? I.e. if the pipeline is suspended by the sync controller and then resumed later on

@onbjerg The next commit is this one https://github.com/paradigmxyz/reth/commit/1ecbd55d45431e32f243d3f2156f1702b9ac8972 and even though I don't have the knowledge to understand what's really going on the modifications may be the cause of what's blocking the pipeline events.


big traffic leads to max pool size was reached error in EF Core

When big traffic(telemetry messages) hit, i assigned a task to each message and made the task async-await, in this task there is a long-running method, which wrote some entities in DB, it started to throw these errors. I cannot put thread.sleep or lock because it cause lag in DB. Application is developed in Dotnet core 2 writing data to azure SQL server

System.AggregateException: One or more errors occurred. (Timeout expired. The timeout period elapsed prior to obtaining a connection from the pool. This may have occurred because all pooled connections were in use and max pool size was reached.) ---> System.InvalidOperationException: Timeout expired. The timeout period elapsed prior to obtaining a connection from the pool. This may have occurred because all pooled connections were in use and max pool size was reached. at System.Data.Common.ADP.ExceptionWithStackTrace(Exception e) --- End of stack trace from previous location where exception was thrown --- at Microsoft.EntityFrameworkCore.Storage.RelationalConnection.OpenAsync(CancellationToken cancellationToken, Boolean errorsExpected) at Microsoft.EntityFrameworkCore.Storage.RelationalConnection.BeginTransactionAsync(IsolationLevel isolationLevel, CancellationToken cancellationToken) at Microsoft.EntityFrameworkCore.Storage.RelationalConnection.BeginTransactionAsync(CancellationToken cancellationToken) at Microsoft.EntityFrameworkCore.Update.Internal.BatchExecutor.ExecuteAsync(Tuple2 parameters, CancellationToken cancellationToken) at Microsoft.EntityFrameworkCore.Storage.Internal.SqlServerExecutionStrategy.ExecuteAsync[TState,TResult](TState state, Func4 operation, Func4 verifySucceeded, CancellationToken cancellationToken) at Microsoft.EntityFrameworkCore.ChangeTracking.Internal.StateManager.SaveChangesAsync(IReadOnlyList1 entriesToSave, CancellationToken cancellationToken) at Microsoft.EntityFrameworkCore.ChangeTracking.Internal.StateManager.SaveChangesAsync(Boolean acceptAllChangesOnSuccess, CancellationToken cancellationToken) at Microsoft.EntityFrameworkCore.DbContext.SaveChangesAsync(Boolean acceptAllChangesOnSuccess, CancellationToken cancellationToken) at TT.Core.Services.ProductionService.UpdateOeeActualProduction(Equipment equipment, EquipmentShift equipmentShift, JobEquipment jobEquipment, Job job, EquipmentTelemetryModel telemetryData) in /src/TT.Core.Services/ProductionService.cs:line 1029 at TT.Core.Services.ProductionService.UpdateProductionFromTelemetry(EquipmentTelemetryModel telemetryData, Boolean createDefaultJob) in /src/TT.Core.Services/ProductionService.cs:line 751 --- End of inner exception stack trace --- at TT.Core.Services.ProcessingLiveMessagingService.ProcessTelemetryMQTTMessage(String message, Boolean createDefaultJob, Boolean createJobFromTelemetrys) in /src/TT.Core.Services/ProcessingLiveMessagingService.cs:line 165 at TT.Core.Telemetry.WebJob.TriggerProcessing.ProcessEventsAsync(String item, Boolean createDefaultJob, Boolean createJobFromTelemetry) in /src/TT.Core.Telemetry.WebJob/TriggerProcessing.cs:line 43 at TT.Core.Telemetry.WebJob.Program.<>c__DisplayClass33_1.<b__0>d.MoveNext() in /src/TT.Core.Telemetry.WebJob/Program.cs:line 450 ---> (Inner Exception #0) System.InvalidOperationException: Timeout expired. The timeout period elapsed prior to obtaining a connection from the pool. This may have occurred because all pooled connections were in use and max pool size was reached. at System.Data.Common.ADP.ExceptionWithStackTrace(Exception e) --- End of stack trace from previous location where exception was thrown --- at Microsoft.EntityFrameworkCore.Storage.RelationalConnection.OpenAsync(CancellationToken cancellationToken, Boolean errorsExpected) at Microsoft.EntityFrameworkCore.Storage.RelationalConnection.BeginTransactionAsync(IsolationLevel isolationLevel, CancellationToken cancellationToken) at Microsoft.EntityFrameworkCore.Storage.RelationalConnection.BeginTransactionAsync(CancellationToken cancellationToken) at Microsoft.EntityFrameworkCore.Update.Internal.BatchExecutor.ExecuteAsync(Tuple2 parameters, CancellationToken cancellationToken) at Microsoft.EntityFrameworkCore.Storage.Internal.SqlServerExecutionStrategy.ExecuteAsync[TState,TResult](TState state, Func4 operation, Func4 verifySucceeded, CancellationToken cancellationToken) at Microsoft.EntityFrameworkCore.ChangeTracking.Internal.StateManager.SaveChangesAsync(IReadOnlyList1 entriesToSave, CancellationToken cancellationToken) at Microsoft.EntityFrameworkCore.ChangeTracking.Internal.StateManager.SaveChangesAsync(Boolean acceptAllChangesOnSuccess, CancellationToken cancellationToken) at Microsoft.EntityFrameworkCore.DbContext.SaveChangesAsync(Boolean acceptAllChangesOnSuccess, CancellationToken cancellationToken) at TT.Core.Services.ProductionService.UpdateOeeActualProduction(Equipment equipment, EquipmentShift equipmentShift, JobEquipment jobEquipment, Job job, EquipmentTelemetryModel telemetryData) in /src/TT.Core.Services/ProductionService.cs:line 1029 at TT.Core.Services.ProductionService.UpdateProductionFromTelemetry(EquipmentTelemetryModel telemetryData, Boolean createDefaultJob) in /src/TT.Core.Services/ProductionService.cs:line 751<---

@bilalmalik777 From the way the issue is described is sounds like the app is using too many connections, and hence the pool size is exceeded. This seems by-design to me. However, if you think this is a bug, then please follow up on https://github.com/dotnet/SqlClient which is the repo for SQL connections/pooling issues.


Improve discoverd logging

Sometimes discoverd clusters encounter interruptions that result in consensus failure. We should improve and standardize logging around errors and remove noisy logging that is not useful for debugging.
It would be useful to know easily:

When consensus is established and in what configuration
When communications with a node are disrupted
If those communications were critical to consensus
When communications are resumed
What errors occur when communicating

And so on. Currently the logging is not always sufficient to figure out what went wrong.

Flynn is unmaintained and our infrastructure will shut down on June 1, 2021. See the README for details.


Swift 3 compatibility

Hey, I'd love to see this lib available in Swift 3 so I can implement it in my project.
Thanks 😄

The example projects doesn't compile with Xcode8.0, but the source dir does.
https://github.com/pixelspark/Swift-AI

See #60


Use parenthesis instead of angle brackets for generics

Using parenthesis around the agruments for both generic types and funcions will add more consistency to the syntax.
Unlike angle brackets, parenthesis don't conflict with comparison operators, so you can do Vec(Glyph)::new() instead of Vec::<Glyph>::new, which is:

less cluttered because :: is used less
less confusing because :: no longer has 2 meanings

Using angle backets instead of parenthesis interferes with some behavior in code editors, such as wrapping and auto-closing parenthesis.

This will not and can not happen.
The simplest reason why not is that this would be an extremely breaking change. Even if we switched over in editions, the vast majority of our documentation would have to be updated as well; something that is just not feasible.
Also, we still need the :: disambiguator because now we can't tell if it is a type generic or a function call which is worse. We would need type dependent parsing (like I think C++ does? don't quote me on this) and that's a mess.

To the people leaving negative emoji without giving any rationale: It looks like you're doing it in mean spirits. Please don't.

I just found out that <Foo<Bar>> can be used instead of Foo::<Bar>, which solves the problems about :: that I mentioned. This alternative syntax should be documented better, and the Foo::<Bar> syntax should be removed because it's redundant.
For generic functions, either the syntax described above should be allowed (e.g. <foo<Bar>>()), or the syntax for declaring generic functions should become fn foo::<T>() for better consistency.

less confusing because :: no longer has 2 meanings

:: is path separator and doesn't have two meanings.

the Foo::<Bar> syntax should be removed because it's redundant.

Good frend for Ferys sake forbeare,
to change the code encloased heare.
Bleste be ye one yt spares thes stones,
and cvrst be they yt moves her bones.

:: is path separator and doesn't have two meanings.

:: is part of the turbofish syntax, which is completely different from paths

:: is part of the turbofish syntax, which is completely different from paths

that's wrong. :: is always path separator.
https://doc.rust-lang.org/reference/glossary.html?#turbofish

To the people leaving negative emoji without giving any rationale: It looks like you're doing it in mean spirits. Please don't.

@Havvy You can't know what people think, here you assume people intention, Argumentum ad personam, what you said here is bad. Please don't.

 👎😕👎
   \|/
    |
   / \

I just found out that <Foo<Bar>> can be used instead of Foo::<Bar>, which solves the problems about :: that I mentioned. This alternative syntax should be documented better, and the Foo::<Bar> syntax should be removed because it's redundant.
For generic functions, either the syntax described above should be allowed (e.g. <foo<Bar>>()), or the syntax for declaring generic functions should change from fn foo<T>() to fn foo::<T>() for better consistency.

the turbofish syntax is still required for function calls.
mem::transmute::<Foo, Bar>(foo);

no way () or <transmute<>>` can replace this.

* Using angle backets instead of parenthesis interferes with some behavior in code editors, such as wrapping and auto-closing parenthesis.

If you're having trouble configuring your editor, try the asking in a community forum. I'm sure people will be happy to help. Otherwise if your editor's Rust support is buggy the place for the bug is with that editor (or its Rust plugin), not here.
Most editors should handle angle brackets just fine as they are common in many languages for generics (C++, Java, C#, etc.). The turbofish is more or less unique though, so I can see some editors might have bugs there.

To me, the turbofish operator is confusing (but also cool, and a breath of something new). I'd prefer something like this: mem::transmute<Foo, Bar>(foo); The :: having 2 meanings both as a path separator and part of the turbofish operator makes it confusing.

I'd prefer something like this: mem::transmute<Foo, Bar>(foo)

This has been discussed, and was decided against. See https://github.com/rust-lang/rfcs/pull/2544 if you're interested in the discussion.


Laravel Spark Implementation

How would this work with Spark?

I have no experience of laravel spark, so I don't know straight off.
But it seems that spark is built on top of laravel, (?), it should then allow use of normal laravel extensions like this one.
Please let me know if you give it a try

Another user confirmed he is using Laravel Spark and posted his config here: https://github.com/martinlindhe/laravel-vue-i18n-generator/issues/33#issuecomment-343539660
So I am considering this "working" :-)


Allow specifying -DAMDGPU_TARGETS

We have similar things for rocblas and rocsparse. It speeds up the compilation process if I have only one GPU.

Can you clarify your request?  AMDGPU_TARGETS is already accepted as a CMake parameter.
https://github.com/ROCmSoftwarePlatform/rocFFT/blob/069dff719152196c3d004bb8cec7cbe96907e2c2/CMakeLists.txt#L185
As a cache variable, the value can be overridden when CMake is run.

@evetsso Thank you for the reply - yes it was my mistake. I had this wrong impression because it was not in install.sh


Parallelize generation of formatters

Follow up for #55 - depends on #53
As correctly noted in #55 we can't just parallelize the formatters output/1 as console output might come from multiple formatters (warnings and such) which might get in each others way. But right now there is already the convention of having a format/1 function that is pure and just creates the structure which is then just written out in output/1 - and the writing out can then be done sequentially.

And this is done as well of course :tada:


Inline code style

🐛 Bug Report
Description
In the latest Docusaurus versions, the inline code's background and borders became different from multiline code blocks. It doesn't fit the overall Docusaurus style.
Compare e.g. npx @docusaurus/init@latest init my-website classic to http://localhost:300 block on https://docusaurus.io/docs/next#fast-track.
Have you read the Contributing Guidelines on issues?
Yes.
Expected behavior
I expect the inline code to fit the overall Docusaurus styling and probably look like they looked in previous versions of Docusaurus or at least like version tags on top of the pages.
Actual behavior
The inline code has a different background and borders of a distinctive color from the multiline code blocks.

I'd also like to note that even GitHub changed the inline code styling with the latest themes, so the inline code doesn't have distinctive borders.

Please include screenshot so that we can compare more easily.

became different

Change is expected to happen, but you can override CSS to revert to previous behavior if you prefer it.
I honestly don't have a strong feeling about what is actually better.
It now also looks more coherent with inline code blocks in admonitions

@lex111 was changing the inline code blocks outside admonition made on purpose?

Prod: https://docusaurus.io/docs/installation

Alpha.70: https://deploy-preview-3933--docusaurus-2.netlify.app/classic/docs/installation

It makes some sense inside admonitions, but not outside.

This behavior was changed at least a few months ago and looks perfectly fine to me.
It is a matter of taste and we won't be able to please everyone, and so far you are the only one complaining about this change, that you can revert with custom CSS anyway, so I'm going to close.

I agree that there should be consistency in the styles of different types of code blocks (inline or multiline). However, we should keep in mind that multiline code blocks have syntax highlighting, so that means depending on selected Prism theme by the end-user, the background of multiline code blocks most likely be different from inline code background specified in default styles (i.e. Infima).
Perhaps in this case it makes sense to set the background for inline code the same as in the Prism's GitHub theme. The new color is even better fit for current admonitions. @slorber WDYT?

Before
After

Ok why not


Automated test responses don't include relationships

In my application using this package (latest), I have an automated test that uses Laravel's (5.3 latest) built-in helpers to test a URL like this:
$this->json('GET', "api/users/{$user->id}?include=posts");
It is supposed to give me back a list of users with their posts. When I test the URL in postman or chrome, it works just fine. However, when I run the test on the command line (by running "phpunit") and dump-and-die the output, it just includes the user's information without the "posts" include.
This is happening across the board for me in my automated tests for any endpoint that has a relationship. Based on what I've found by digging into Fractal and dump-and-dying all over the place, it looks like for some reason the "parseIncludes" function doesn't get set correctly when automated tests are run. But like I said, it's fine in a Postman test.
To be honest, I can't tell for sure if this is Laravel's problem, Fractal's problem, or this packages problem. I am continuing to dig into it.

I temporarily switched to https://github.com/spatie/laravel-fractal to see if the issue would still persist, and it did. Which causes me to believe this may not be an issue with this package, and rather with Laravel or Fractal instead.
This is completely perplexing me at this point. I can't imagine why this would work in practice but fail during automated tests. Very odd. Would love to hear from the creator of this package to see if he ever successfully application tested relationships.

I'll try to take a look at it. Thank you dor the report
Le dimanche 30 octobre 2016, John T. Bonaccorsi<EMAIL_ADDRESS>a écrit :

I temporarily switched to https://github.com/spatie/laravel-fractal to
see if the issue would still persist, and it did. Which causes me to
believe this may not be an issue with this package, and rather with Laravel
or Fractal instead.
This is completely perplexing me at this point. I can't imagine why this
would work in practice but fail during automated tests. Very odd. Would
love to hear from the creator of this package to see if he ever
successfully application tested relationships.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/ellipsesynergie/api-response/issues/31#issuecomment-257196423,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ADGIaDH22HExU9vDDJthPOhNkKM3Lp9Rks5q5UWTgaJpZM4KkkG5
.

--
Maxime Beaudoin
418 602-1050
Sans frais:<PHONE_NUMBER>
[image: Ellipse Synergie] http://www.ellipse-synergie.com
Octas 2016, Innovation et Excellence en TI
[image: Facebook] https://www.facebook.com/EllipseSynergie [image:
Twitter] https://twitter.com/EllipseSynergie [image: linkedIn]
https://www.linkedin.com/company/ellipse-synergie [image: Instagram]
https://www.instagram.com/ellipsesynergie/
Avis de confidentialité – Information privilégiée et confidentielle
réservée uniquement à l'usage du destinataire ci-dessus mentionné. Si le
lecteur de ce message n'est pas le véritable destinataire, veuillez prendre
note que toute diffusion, distribution ou copie de cette communication est
strictement interdite. Toute personne qui reçoit cette communication
par erreur est priée de nous avertir immédiatement par courriel et de
détruire le message original. Merci.
Confidentiality Notice – This e-mail is intended for the use of the
addressee(s) only and may contain privileged, confidential, or proprietary
information that is exempt from disclosure under law. If you have received
this message in error, please inform us promptly by reply e-mail, then
delete the e-mail and destroy any printed copy. Thank you.

@imjohnbon I found the problem, but not the solution for now.
The problem is simple, it's because the parsing is triggered on the boot method of the service provider like this : $manager->parseIncludes(explode(',', $this->app['Illuminate\Http\Request']->get('include'))); So at this point, when the http request occur, the content of the request is populate with the include value.
BUT, in the testing process, we are not doing the normal http request. Laravel doing a internal call via $this->call and the value of includes was already loaded and will NOT be refresh.
For now, the only way i see to resolve this is to replace the method in Illuminate\Foundation\Testing\Concerns\MakesHttpRequests::call by this code
    /**
     * Call the given URI and return the Response.
     *
     * @param  string  $method
     * @param  string  $uri
     * @param  array   $parameters
     * @param  array   $cookies
     * @param  array   $files
     * @param  array   $server
     * @param  string  $content
     * @return \Illuminate\Http\Response
     */
    public function call($method, $uri, $parameters = [], $cookies = [], $files = [], $server = [], $content = null)
    {
        $kernel = $this->app->make('Illuminate\Contracts\Http\Kernel');

        $this->currentUri = $this->prepareUrlForRequest($uri);

        $this->resetPageContext();

        $symfonyRequest = SymfonyRequest::create(
            $this->currentUri, $method, $parameters,
            $cookies, $this->filterFiles($files), array_replace($this->serverVariables, $server), $content
        );

        $request = Request::createFromBase($symfonyRequest);

        $response = app(\EllipseSynergie\ApiResponse\Contracts\Response::class);

        $response
            ->getManager()
            ->parseIncludes(explode(',', $request->get('include')));

        $response = $kernel->handle($request);

        $kernel->terminate($request, $response);

        return $this->response = $response;
    }

This code will intercept the new Request object and parse the include value.
Someday i may probably create some Trait to help people resolve that issue.

Thanks for the update! I figured it was something like that. Unfortunately editing core Laravel files isn't an option for me or most people I would assume. Hopefully one day this can be solved within the package.

@imjohnbon You just have to create your own call method in the TestCase class for now if you want a quick fix.

Ah of course, thanks for the tip!

@maximebeaudoin can provide a code snippet on hwo to create m own call method in TestCase

@mehrdaad I have create a trait to resolve this. https://github.com/ellipsesynergie/api-response/blob/master/src/Testing/Laravel/AddTestingSupportForInclude.php

@maximebeaudoin thanks, I had a suggestion for this trait, Could we convert call to a private function and create 3 or 4 protected functions like get, post etc to keep Laravel signature untouched?
One problem I can think of it that it would create confusion for the trait client.
Any suggestions?


'' in designer-generated type '' should call InitializeComponent method

[Enter feedback here]
I get this error is some of my Windows Forms, even if InitializeComponent is the first line after the constructor declaration.
This happens almost every time that I edit the code in Edit and Continue. I have to stop the edit and restart the application in order for the false error to clear.
`	Friend Sub New()
	InitializeComponent()

	MinimumSize = Size

	cboBank.DataSource = Finances.Banks
	cboBank.DisplayMember = "Name"
	cboBank.ValueMember = "ID"
	...`

As you can see, this deals with sensitive information and I cannot upload the complete file.

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 6e557f6a-dabf-dcf7-1b99-f7253c1d5dba
Version Independent ID: 97338ee8-0c6d-acdd-ade2-26b3c81f9da4
Content: '<constructor>' in designer-generated type '<type>' should call InitializeComponent method
Content Source: docs/visual-basic/misc/bc40054.md
Product: dotnet-visualbasic
GitHub Login: @KathleenDollard
Microsoft Alias: kdollard

Found a solution.
Deactivate the "Treat all warnings as error" CheckBox in the Compile tab of the project's properties. Set the individual notifications manually instead.


RuntimeError: Error building custom image

When I use generate_custom_image.py to create custom dataproc image, it throws this error:
  File "dataproc/cloud-dataproc/custom-images/generate_custom_image.py", line 429, in <module>
    run()
  File "dataproc/cloud-dataproc/custom-images/generate_custom_image.py", line 420, in run
    daisy_image_creator.create(args)
  File "/Users/temp/Documents/guess/dataproc/cloud-dataproc/custom-images/daisy_image_creator.py", line 43, in create
    os.path.abspath(args.daisy_path), workflow_script)
  File "/Users/temp/Documents/guess/dataproc/cloud-dataproc/custom-images/daisy_workflow_executor.py", line 42, in run
    raise RuntimeError("Error building custom image.")
RuntimeError: Error building custom image.```

The customization-script is as follows:

#!/bin/bash
pip install numpy==1.15.4
pip install pandas==0.23.4
pip install ujson==1.35
pip install geopandas==0.4.0
pip install lxml==4.3.0

**daisy** is downloaded from here: https://storage.googleapis.com/compute-image-tools/release/darwin/daisy

This issue must be obsolete - we removed Daisy support from custom image build.


[5.7] Improve the left/right arrow navigation inside the Navigator

Rationale: Allows users to user the keyboard left/right arrows to expand/contract the navigator items.
Risk: Low
Risk Detail: A focused change for parent items in the navigator
Reward: High
Reward Details: Users would be able to use the keyboard to navigate more efficiently
Original PR: https://github.com/apple/swift-docc-render/pull/169
Issue: rdar://90865355
Code Reviewed By: @hqhhuang
Testing Details: Manually tested in the browser and with Unit tests

@swift-ci test


how to write to body?

I'd like to write to the body of a response like this:
let res = Response::new();
write!(res.body, "foo");

Of course it doesn't work this way but could you give me a hint how to get the Writer of a new Response?

In Iron, you can use the Modifier trait to provide a response body. The best way to do this is through Response::with. It will accept anything that implements the Modifier trait for a Response.
You can pass in a String, bytes, a File, status codes, etc. And the list of implementors on the Modifier page will show you all that is available in the Iron crate. Of course you can implement your own type which modifies Responses too if you need more functionality.

@flosse Did this solve your question, or perhaps we could expand on the answer in some way?

@Hoverbear It's still unclear for me :(
It would be great to get an working example, so that I can replace my out with something like res.body:
let mut out: Vec<u8> = vec!(); // <--- this should be replaced with the body
write!(out, "foo: {}", 42);

@flosse Can you share a gist or example?

https://gist.github.com/flosse/da963de2bbb466bdca09c23757b070ce

You can just do Response::with(body_buffer).

@flosse any update on this?

Closing due to inactivity, ping if anything is unclear.


chore: Native Stack doc's - header options

React Navigation, Native Stack, v7.x
added screenshots/videos for:

headerTintColor
headerBackground
headerBlurEffect
headerLargeStyle
headerLargeTitle
headerLargeTitleStyle
headerShadowVisible
headerStyle

The extraLight blur effect doesn't seem to have a blur


Fix bug when VCL is not loaded when only the container and not the whole pod is restarted

resolves #67
Also:

Fire an event and log the case when a backend pod is found but couldn't fine the port definition we're looking for.
Fire an event if both a templated and not templated version of a VCL file is set in the VCL ConfigMap.

Signed-off-by: Tomash Sidei<EMAIL_ADDRESS>

@tomashibm @cin Thanks for moving on this so quickly. When can we expect a release?

We'll have a release out here in the next couple of days. We're trying to get a PR for omitting non-ready backends in the release as well.


NETOBSERV-1533: refine metrics for dashboard creation

Use just two shared metrics for eviction counters: on for eviction events and one for flows; shared across ringbuf/map implementations and labelled as such
Report more errors via metrics

@msherif1234 as I'm working on the dashboard and I'm bringing a few changes here.
Here's a screenshot of what I get with these metrics:
Some text counters in the top bar:

Some ebpf stats:

(something looks wrong in the eviction rate when it evicts because of full map)

/lgtm

@msherif1234 I think this task is done I've got all metrics needed to build a nice dashboard - can you take a second look & review please?

overall looks great to me small comments/questions inline up to you to address nothing critical
/lgtm

/approve


Attempted import error: 'react-canvas-js' does not contain a default export

install
$ npm install --save react-canvas-js

then in App.js:
import Canvas from 'react-canvas-js'

See react build error
Attempted import error: 'react-canvas-js' does not contain a default export (imported as 'Canvas').

@MichaelZelensky - Hey thanks for raising an issue. Try importing it like so in App.js -
import { Canvas } from  'react-canvas-js'

@MichaelZelensky - you can checkout examples out here - https://shalomsam.github.io/react-canvas-js/

You should probably update the readme then. The example given there clearly imports it as default: import Canvas from 'react-canvas-js'. Also, the options prop passed in that example is an array when it should be an object.


Flaky build-cross-qemu-alpha buildbot

not ok 84 - fs_partial_read
# timeout
# Output from process `fs_partial_read`: (no output)
not ok 85 - fs_partial_write
# timeout
# Output from process `fs_partial_write`: (no output)

It's always the same two tests. Seems to happen frequently as of today (yesterday?), I've been able to repeat it three times in a row.
The .deb from http://archive.ubuntu.com/ubuntu/pool/universe/q/qemu/ hasn't changed recently. There's also no v1.x commit that's an obvious culprit.

One difference between, e.g.

https://github.com/libuv/libuv/actions/runs/3578637576/jobs/6019001850 (passed)
https://github.com/libuv/libuv/actions/runs/3591703370/jobs/6050221769 (failed)

is that the runs are now on the Ubuntu 22.04 runner whereas they were previously running on Ubuntu 20.04. That's part of a rolling update by GitHub: https://github.com/actions/runner-images/issues/6399


Improve route finding performance

Replace the list with a generator for lazy evaluation

Closed in favor of #72


Manually reposition an agent?

Is it possible to manually change the position of an agent without navigation? This would be useful for handling characters that are not using navigation, or are being controlled on a different navigation mesh.  Is it safe to just edit the dtCrowdAgent::npos[3] value for this?

Bsaically, this is why:
https://www.youtube.com/watch?v=QIqJrdqntRQ
It seems to work for small distances, but there may be some issues when traversing tiles. I would appreciate an explanation of any potential problems.

According to documentation of dtCrowd:

Some agent configuration settings can be updated using updateAgentParameters(). But the crowd owns the agent position. So it is not possible to update an active agent's position. If agent position must be fed back into the crowd, the agent must be removed and re-added.

And dtCrowd.addAgent():

The agent's position will be constrained to the surface of the navigation mesh.

So you'll likely get conflicts if you just update the position of agents (e.g. via getEditableAgent()).
But if characters do not use navigation, would you even want to insert them into the crowd? Is it primarily to maintain collision/separation from other agents?

But if characters do not use navigation, would you even want to insert them into the crowd? Is it primarily to maintain collision/separation from other agents?
Yes.


Supporting arrays (repeating params) in URL

It is ok to use arrays in koa.js in a query string, e.g. /something?param=1&param=2
this.request.query will return in this case an array:
[ param: [1, 2] ]
Why not to support this also in koa-router:
/something/param/1/param/2
for URL pattern like /something/param/:param
It could return an array also in the same style as this.request.query

Interesting. What is the use case?
this.captures array might be useful for your use case, which is an array of all URL parameter values.

The use case is a GET request that should receive an array through query string.
E.g. if you want to get prices for few products at the same time:
/products?product-id=1&product-id=2
This is used e.g. in Rails and PHP, when you use square brackets after variable: product-id[]=1&product-id[2]. It also works apparently in koa.js for product-id=1&product-id=2

Neat. It's a little magical for my taste but it makes sense. If there's only one parameter given, how does the router know it should be an array? Code would always have to check if req.query.product-id is an array or not.
My 2cents from my own experience building APIs... I recommend going with ?json= and using JSON.stringify() and JSON.parse() for simpler, more robust, and reliable queries compared to the various express-style query parameter parsing schemes. It removes a whole layer of unnecessary abstraction imho.

Hi gents,
Any update on this topic?

Neat. It's a little magical for my taste but it makes sense. If there's only one parameter given, how does the router know it should be an array? Code would always have to check if req.query.product-id is an array or not.
My 2cents from my own experience building APIs... I recommend going with ?json= and using JSON.stringify() and JSON.parse() for simpler, more robust, and reliable queries compared to the various express-style query parameter parsing schemes. It removes a whole layer of unnecessary abstraction imho.

That's not always working as supposed to, for ex. if you have a + sign in the stringified JSON it will never get url encoded and you'll loose that sign when retrieving the ?json value.
So the OP's question is still actual

any updates on that? I think it's useful feature +1


Update microsoft-spark-utilities.md

the output  of the mssparkutils.env.help() is incorrectly cased at least for python

@jasonhorner : Thanks for your contribution! The author(s) have been notified to review your proposed change.

@ruixinxu - Can you review this PR?
IMPORTANT: When this content is ready to merge, you must add #sign-off in a comment or the approval may get overlooked.
#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

#sign-off

@Jak-MS Please merge this PR.


⚠ Bofrost.be has degraded performance

In f61d06d, Bofrost.be (https://www.bofrost.be) experienced degraded performance:

HTTP code: 200
Response time: 945 ms

Resolved: Bofrost.be performance has improved in 0f5a332.


NullReferenceException in Orchard.OpenId's Create view when the model state is invalid

The root cause was quite easy to find: when the model state is invalid, AdminController.Create redisplays the form but doesn't add OpenIdSettings in the ViewData bag, which causes the NRE in the Create view.

Fixed at https://github.com/OrchardCMS/Orchard2/commit/8033a01ec51c434a317a2b2f20bbf98de4da0063


kill G altogether

this is another crack at #8746, but rebased and using other PRs for LoadUserArg refactors, and client de-G-ification

@patrickxb  you've already reviewed this, but it's a thinner PR now due to other PRs that went in ahead (like LoadUserArg and client-de-G-ificiation)

Replaced #8746


Readme: fix imports

The code is incorrect (import from is invalid) and browsers don't actually support the suggested line, you'd have to specify the whole import path including ./node_modules, but most people don't use it that way, so there's no need to specify that.

Maybe replaced by:

https://github.com/kenchris/urlpattern-polyfill/pull/77

@fregante I think I handled this in #77, can you check if that works for you?

The new readme still uses import from

I don't know how more specific I can get: import from "name" is not valid syntax. You need to use import "name". Try running your examples and you'll see the error.


sequential issue

when i use  "projects/configs/panoptic-flashocc/panoptic-flashocc-r50-depth4d-longterm8f.py"  to train and infer , found bellow picture sequential  always  False,  when should be True ? Why not use it during temporal training and inference

This is not used in training and inference. It follows the detection pipeline in real-world applications where the BEV features of the previous frame have already been computed. It will be turned on in benchmark_sequential.py.

This is not used in training and inference. It follows the detection pipeline in real-world applications where the BEV features of the previous frame have already been computed. It will be turned on in benchmark_sequential.py.

get it!   thanks a lot


Need to add community profile

I will take care of this in my current PR, e.g.,:

It should be easy / obvious to know how to contribute and ask for help.

Will not fix


chore(master): release 2.1.1

:robot: I have created a release beep boop
2.1.1 (2024-01-09)
Bug Fixes

should not throw error when query is undefined (515fa20)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/keq-request/keq/releases/tag/v2.1.1 :sunflower:


REVERT Function

Is your feature request related to a problem? Please describe:
Needs a revert function.  It sometimes deletes features out of nowhere.

Describe the solution you'd like:
Go back before the last prompt was run.

Describe alternatives you've considered:

Additional context:

Thank you for the great feedback! We completely agree and are working rapidly to implement this feature. The resolution will be tracked under #35!


[File Explorer] File Explorer Add-Ons folder and namespace naming inconsistency

Description of the enhancement
The naming of the folders and the files for the "File Explorer Add-Ons" are inconsistence. Also the folder name is incorrect because the files for the preview handlers and the thumbnail provider are in that same folder.
Current naming
The name of the source folder:
src\modules\previewpane
The build output folder for the projects:
$(Platform)$(Configuration)\modules\FileExplorerPreview\
The C# Namespace:
Microsoft.PowerToys.PreviewHandler.Pdf / Svg
Microsoft.PowerToys.ThumbnailHandler.Pdf / Svg
SvgPreviewHandlerUnitTests / PdfPreviewHandlerUnitTests
SvgThumbnailProviderUnitTests / PdfThumbnailProviderUnitTests
The project names:
MarkdownPreviewHandler / PdfPreviewHandler / SvgPreviewHandler
PdfThumbnailProvider / SvgThumbnailProvider
UnitTests-MarkdownPreviewHandler / UnitTests-PdfPreviewHandler / UnitTests-SvgPreviewHandler
UnitTests-PdfThumbnailProvider / UnitTests-SvgThumbnailProvider
Suggested naming:
The Source folder and Build output folder should have the same name:
src\modules\FileExplorer
$(Platform)$(Configuration)\modules\FileExplorer\
The C# Namespaces for the preview handlers:
Microsoft.PowerToys.FileExplorer_PreviewHandler.Pdf
Microsoft.PowerToys.FileExplorer_PreviewHandler.Svg
Microsoft.PowerToys.FileExplorer_PreviewHandler.Markdown
The namespace of the thumbnail providers should be named ThumbnailProvider:
Microsoft.PowerToys.FileExplorer_ThumbnailProvider.Pdf / Microsoft.PowerToys.FileExplorer_ThumbnailProvider.Svg
The test project should be named *.UnitTests
MarkdownPreviewHandler.UnitTests / PdfPreviewHandler.UnitTests / etc.

Seems like #9343 to me.

Not the same but definitely related. The naming suggested at that one is even better.

@stefansjfw we did work here, do you feel this has been addressed?

@crutkas No, this is yet to be done. We should agree what the correct naming would be first


Autodeploy Error: 'Buffer' is not assignable to parameter of type 'BinaryLike'.

Full error stack
   ▲ Next.js 15.0.3
   Creating an optimized production build ...
 ✓ Compiled successfully
   Linting and checking validity of types ...
Failed to compile.
.sst/platform/src/components/aws/function.ts:1943:23
Type error: Argument of type 'Buffer' is not assignable to parameter of type 'BinaryLike'.
  Type 'Buffer' is not assignable to type 'Uint8Array | DataView'.
    Type 'Buffer' is not assignable to type 'Uint8Array'.
      The types returned by 'entries()' are incompatible between these types.
        Type 'IterableIterator<[number, number]>' is missing the following properties from type 'ArrayIterator<[number, number]>': map, filter, take, drop, and 9 more.
  1941 |           // Calculate hash of the zip file
  1942 |           const hash = crypto.createHash("sha256");
> 1943 |           hash.update(await fs.promises.readFile(zipPath));
       |                       ^
  1944 |           const hashValue = hash.digest("hex");
  1945 |           const assetBucket = region.apply((region) =>
  1946 |             bootstrap.forRegion(region).then((d) => d.asset),
node:internal/errors:865
  const err = new Error(message);
              ^
Error: Command failed: npm run build
    at __node_internal_genericNodeError (node:internal/errors:865:15)
    at checkExecSyncError (node:child_process:890:11)
    at Object.execSync (node:child_process:962:15)
    at buildNextjsApp (file:///root/.npm/_npx/e014fccbbe7e583d/node_modules/@opennextjs/aws/dist/build.js:95:8)
    at build (file:///root/.npm/_npx/e014fccbbe7e583d/node_modules/@opennextjs/aws/dist/build.js:44:5)
    at async file:///root/.npm/_npx/e014fccbbe7e583d/node_modules/@opennextjs/aws/dist/index.js:9:1 {
  status: 1,
  signal: null,
  output: [ null, null, null ],
  pid: 601,
  stdout: null,
  stderr: null
}
Node.js v18.20.3
|  Error       abay sst:aws:Nextjs → abayBuild sst:Run
|  command exited with code 1
✕  Failed
   abay sst:aws:Nextjs → abayBuild sst:Run
   command exited with code 1
Error: Failed to run: /tmp/repo/application/node_modules/.bin/sst deploy --stage production
    at shell (file:///tmp/buildspec/index.mjs:238:13)
    at deploy (file:///tmp/buildspec/index.mjs:191:5)
    at workflow (file:///tmp/buildspec/index.mjs:161:59)
    at async runWorkflow (file:///tmp/buildspec/index.mjs:164:5)
    at async handler (file:///tmp/buildspec/index.mjs:48:5)
    at async file:///tmp/buildspec/[eval1]:1:122

Any pointers?
This happens both auto deploy and terminal deploy

My bad, issue is gone after adding "sst.config.ts" back to tsconfig.


feat: garbage collection note

Fixes #422

@kyranjamie would love a quick review 🙏🏼

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


[Question] D3D9SwapChainEx: Failed to recreate swap chain: -13 on 6700 XT

About a half year ago all works fine, but now it's just show white or black screen in all games. What could happen? Original DXVK still works with Dx9 games without issues mostly.
Tried to test with integrated intel, but result is same. By identical log can presume what Windows Graphic Settings just ignoring, and discrete card is used anyway.
System information

OS: WIndows 10
GPU: AMD Radeon RX 6700 XT
Driver: 2.0.294
Vulkan: 1.3.270

Morrowind_d3d8.log
Game_d3d8.log

Hmmm... -13 is VK_ERROR_UNKNOWN, so that doesn't say much about what's going on. No idea why you're getting this, but in all fairness AMD drivers don't get a lot of testing (if any) on Windows with d8vk. Something may have broken on that end, though I'd expect d3d9 games run with dxvk to exhibit the same issues if that's the case.

Something may have broken on that end, though I'd expect d3d9 games run with dxvk to exhibit the same issues if that's the case.

FarCry with dxvk runs perfectly, what i can prove by log.
FarCry_d3d9.log

For experiment I produced a clean install of Windows 11 to another physical drive. Nothing changed, so that's exactly the latest AMD drivers is guilty. Crosire's dx9 wrapper works fine, just in case.
game_d3d8.log

fwiw some other dxvk games have the same crash issue with Windows AMD drivers froms 23.10.2 and above. See https://github.com/doitsujin/dxvk/issues/3723 as an example.
23.8.2 should work


How to check the position of front camera ?

hi,
I am trying to train the policy with go1, but I do not know how to check whether the position of the front camera is in correct position. In other words, after setting a  position in the config file, how can I know the position of the front camera in the Isaac gym environment?

I mean that it seems that I can't see the camera in the simulated environment

There is a debug option in the config file. By setting env_cfg.viewer.draw_debug_vis = True and making sure forward_depth is in one of your obs_components during play.py, you will see a RGB axis near the robot in the visualization.
For the visualization implementation, please check line 737 _draw_sensor_vis in legged_robot_field.py.

thanks a lot


JMX plugin defaults to null host

Output of the info page (if this is a bug)
● datadog-agent.service - Datadog Agent
   Loaded: loaded (/usr/lib/systemd/system/datadog-agent.service; enabled; vendor preset: disabled)
   Active: active (running) since Fri 2019-12-20 15:22:18 UTC; 7min ago
 Main PID: 4224 (agent)
   CGroup: /system.slice/datadog-agent.service
           ├─4224 /opt/datadog-agent/bin/agent/agent run -p /opt/datadog-agent/run/agent.pid
           └─4300 java -Xmx200m -Xms50m -classpath /opt/datadog-agent/bin/agent/dist/jmx/jmxfetch.jar org.datadog.jmxfetch.App --ipc_host localhost --ipc_port 5051 --check_period 15000 --thread_pool_size 3 --collection_timeout 60 --reconnection_timeout 10 --reconnectio...
Dec 20 15:29:06 ip-172-18-2-142.eu-west-1.compute.internal agent[4224]: 2019-12-20 15:29:06 UTC | CORE | INFO | (pkg/jmxfetch/jmxfetch.go:249 in func1) | 2019-12-20 15:29:06,127 | INFO | App | Started instance initialization...
Dec 20 15:29:06 ip-172-18-2-142.eu-west-1.compute.internal agent[4224]: 2019-12-20 15:29:06 UTC | CORE | INFO | (pkg/jmxfetch/jmxfetch.go:249 in func1) | 2019-12-20 15:29:06,127 | INFO | Instance | Trying to connect to JMX Server at null:7199
Dec 20 15:29:06 ip-172-18-2-142.eu-west-1.compute.internal agent[4224]: 2019-12-20 15:29:06 UTC | CORE | INFO | (pkg/jmxfetch/jmxfetch.go:249 in func1) | 2019-12-20 15:29:06,127 | INFO | Instance | Connection closed or does not exist. Attempting to cre...new connection...
Dec 20 15:29:06 ip-172-18-2-142.eu-west-1.compute.internal agent[4224]: 2019-12-20 15:29:06 UTC | CORE | INFO | (pkg/jmxfetch/jmxfetch.go:249 in func1) | 2019-12-20 15:29:06,127 | INFO | ConnectionFactory | Connecting using JMX Remote
Dec 20 15:29:06 ip-172-18-2-142.eu-west-1.compute.internal agent[4224]: 2019-12-20 15:29:06 UTC | CORE | INFO | (pkg/jmxfetch/jmxfetch.go:249 in func1) | 2019-12-20 15:29:06,127 | INFO | Connection | Connecting to: service:jmx:rmi:///jndi/rmi://null:7199/jmxrmi
Dec 20 15:29:06 ip-172-18-2-142.eu-west-1.compute.internal agent[4224]: 2019-12-20 15:29:06 UTC | CORE | INFO | (pkg/jmxfetch/jmxfetch.go:249 in func1) | 2019-12-20 15:29:06,128 | INFO | App | Completed instance initialization...
Dec 20 15:29:06 ip-172-18-2-142.eu-west-1.compute.internal agent[4224]: 2019-12-20 15:29:06 UTC | CORE | INFO | (pkg/jmxfetch/jmxfetch.go:249 in func1) | 2019-12-20 15:29:06,128 | INFO | App | Could not initialize instance: jmx: java.util.concurrent.ExecutionException:...
Dec 20 15:29:06 ip-172-18-2-142.eu-west-1.compute.internal agent[4224]: 2019-12-20 15:29:06 UTC | CORE | INFO | (pkg/jmxfetch/jmxfetch.go:249 in func1) |         java.net.UnknownHostException: null]
Dec 20 15:29:06 ip-172-18-2-142.eu-west-1.compute.internal agent[4224]: 2019-12-20 15:29:06 UTC | CORE | INFO | (pkg/jmxfetch/jmxfetch.go:249 in func1) | 2019-12-20 15:29:06,135 | WARN | App | Unable to instantiate or initialize instance null:7199. Is the target JMX Se...
Dec 20 15:29:06 ip-172-18-2-142.eu-west-1.compute.internal agent[4224]: 2019-12-20 15:29:06 UTC | CORE | INFO | (pkg/jmxfetch/jmxfetch.go:249 in func1) |         java.net.UnknownHostException: null]

Describe what happened:
JMX plugin default configuration says that default host is localhost. When this field is left , like in the default configuration, the agent tries to connect to null host.
  -

    ## @param host - string - optional - default: localhost
    ## JMX host to connect to.
    #
    # host: localhost

    ## @param port - integer - required
    ## JMX port to connect to.
    #
    port: 7199

Describe what you expected:
Agent is unable to initialize due to connecting to null host.
Steps to reproduce the issue:
Copy the default configuration file /etc/datadog-agent/conf.d/jmx.d/conf.yaml.example to /etc/datadog-agent/conf.d/jmx.d/conf.yaml
Additional environment details (Operating System, Cloud provider, etc):
Amazon Linux 2
AWS eu-west-1
Agent version 6.16.0 installed from Yum repository
Was tempted to fix this with an alias <IP_ADDRESS> null in /etc/hosts

any nes on this?

Hi folks -- if one (or more!) of you can contact datadog support regarding this issue, that would help to get this prioritized.  Thanks!

+1


Fix violations of Sonar rule 2142

Hi,
This PR fixes 1 violations of Sonar Rule 2142: '"InterruptedException" should not be ignored'.
The patch was generated automatically with the tool Sorald. For details on the fix applied here, please see Sorald's documentation on rule 2142.

@khaes-kth, thanks for your proposals here! I wonder, integration test are failed in this PR, would you be so nice to make them green?

Are you sure it is caused by changed in this PR?

I just saw the previous versions all pass all the checks, so the failure should be caused by changes in this PR. I'll try to figure out what causes the problem.

Is it really a good idea to enable automated code changes from such a tool in this code base? KTB is a critical component when used in a mission critical Kafka cluster. So I think it is very important to have a special focus on bugs and clean code in this code base. However, as this PR illustrates, automated code changes can make the code less clean and that will only in the end introduce new bugs. So I think the right way to go is to make the tool generate warnings/alerts, but the handling of the findings should be done manually.

Is it really a good idea to enable automated code changes from such a tool in this code base?

Hi @akselh , this is not an automated code change enabled for KTB. This is a community PR created by the @khaes-kth that I think is based on his Phd thesis. 😄

Ok. Ref the comment on the PR, "The patch was generated automatically with the tool Sorald.", it definitively seems to be an automated code change. So it is not generated as part of a CI job in this project, but I still think my comment is relevant. :-)

Thank you @purbon and @akselh
The patch is generated by Sorald, which is a tool that I am working on as a part of my PhD. Since we are still in experimentation phase, the PR was opened manually so that we could make sure the generated patch made some sense before creating an actual PR. We also have the option to open the PR fully automatically using Github API, but that's for later.
I am very grateful for the comments by @akselh . He is mentioning a point that we will definitely discuss in our paper. The short answer is that previous studies show most static warnings are just ignored by developers (partly) because they do not have the time or motivation to understand and resolve the issue. Therefore, we believe automatically generating a patch that fixes static issues could increase the number of warnings that get addressed by developers. At the end, developers can decide to manually check the code before merging it, and if there is a quality issue with the generated code, we should improve it and it is surely possible to do that.
We are happy that we have already had several merged PRs for Sorald and we hope that we can have more after applying your thoughtful comments.

Thank you @purbon and @akselh
The patch is generated by Sorald, which is a tool that I am working on as a part of my PhD. Since we are still in experimentation phase, the PR was opened manually so that we could make sure the generated patch made some sense before creating an actual PR. We also have the option to open the PR fully automatically using Github API, but that's for later.
I am very grateful for the comments by @akselh . He is mentioning a point that we will definitely discuss in our paper. The short answer is that previous studies show most static warnings are just ignored by developers (partly) because they do not have the time or motivation to understand and resolve the issue. Therefore, we believe automatically generating a patch that fixes static issues could increase the number of warnings that get addressed by developers. At the end, developers can decide to manually check the code before merging it, and if there is a quality issue with the generated code, we should improve it and it is surely possible to do that.
We are happy that we have already had several merged PRs for Sorald and we hope that we can have more after applying your thoughtful comments.

@khaes-kth, sorry for the delay in my response here. I definitively agree with your comments that just warnings have a risk of not getting attention in a busy developer's life. So suggesting a PR will be better with respect to drawing attention.
The risk is that because it is an automated patch many developers will think that this the right/only way and just approve it as long as the tests are green. With multiple patches like this one the code will actually get worse because code is patched instead of the root causes being fixed with the result of cleaner and less buggy code.
So care should be taken on what kind of patches are suggested, some will be straight forward and some (like this one) is not. I guess working on this subject is core to your PhD and why you create these manual PRs :-)
Keep up the good work @khaes-kth! Will be interesting to see how this can function when you have tuned it a bit more.

Thanks again for your insightful comments @akselh. You mentioned a good point that we had not considered. If the users assume that they can always accept our Bot's PRs as they are, it may cause some issues depending on their projects in the long-term.
Though we hope that someday all of our PRs get accepted without any modifications, we have to make it more clear for users that our current goal is to reduce the time they need to spend to fix SonarQube violations, hence a manual review is still required.

Based on our discussions on this page, I think this PR should be closed without merging. Please feel free to close it if you think the same; we will report it as a rejected PR in our paper and it will still provide very useful information for us.
Thanks,

closing this PR as of now. Thanks, everyone for the nice discussion here, appreciate the help and contribution.


Armada 619 down sync jobbergate prod data to staging

What
Down-sync Jobbergate prod data to staging.
Since we should only down-sync the applications and job_scripts table and not sync the job_submissions table, a new option was added to slurp-cli to ignore job_submissions table.
Why
We will need to "down-sync" the Jobbergate production data to staging on a regular basis. This will involve creating a pseudo-copy of all the data in the production database. We will need to preserve relationships between entities (applications➝job_scripts, for example) and ownership (owner_email). Relationship references will need to be reflective of the ids in staging after the down-sync.
Task: https://app.clickup.com/t/18022949/ARMADA-619

Peer Review
Please follow the upstream omnivector documentation concerning
peer-review guidelines.

Task linked: ARMADA-619 Down-sync Jobbergate prod data to staging


Refactor device interface from enum to string

This commit removes the enum for the device interface and replaces it with a plain string. This is due to the fact the the orchestrator http protocol transports the interface as a string anyway. In addition new interfaces where introduced and it was decided that we want to do the parsing of the string within the orchestrator. The client should therefore no longer care about the user input.
In addition the default was set to an empty string, which will result in the orchestrator detecting the right interface by its own. This works in most cases since only one interface is connected most of the times. If more than one interface is present an internal priority list is applied.

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

Comparison is base (fb2b3ad) 85.44% compared to head (f25ee89) 85.40%.

Additional details and impacted files
@@            Coverage Diff             @@
##             main      #23      +/-   ##
==========================================
- Coverage   85.44%   85.40%   -0.05%
==========================================
  Files          16       16
  Lines        1292     1288       -4
  Branches      218      218
==========================================
- Hits         1104     1100       -4
  Misses        179      179
  Partials        9        9

Files
Coverage Δ

src/labone/core/connection_layer.py
100.00% <100.00%> (ø)

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


Convert rule.pp from class to define so we can instantiate it multiple times

Hi,
With this change you can add specific rules to every case (webserver, database, monitoring, ...) rather than bit lists of nearly the same rules for every role.

Hello hathoward and forgodssake I have 2 questions.
First, @hathoward why would this change not be committed if it's providing a real benefit to the module and thus the Puppet community that consumes on it?
Second, @forgodssake I am confused by the use of $rule_key in the init.pp file and then $title in the rule.pp file. Would you be so kind to provide examples?
Thank you.

His PR is probably fine, just have not made time to provide unit and integration tests to  properly maintain this module. If I were to commit time to this module again I'd rather contribute it to the official puppet firewall module by adding a windows FW provider that implements/extends their type. Motivation for the above has been lacking due to my professional time now being consumed by Linux based solutions.

Good day @hathoward I appreciate your time to reply. I too wish the official puppet/windows_firewall forge module was better performing however it lacks the basic functionality to maintain and enforce state of the Windows firewall.
Such as:
When you try to enable the firewall, it does not enable all the profiles. ie. the domain profile.
When a rule with the same name already exists, it has no affect. So when you want to change an existing rule, this will not work.
When ensure => absent is used, it gives error and does not work correctly.
So this module is good only to add new rules.
As you mentioned you are very busy, if you do find free time could you provide a simple example of what @forgodssake is doing with $title is it referencing the $title of the hiera manifest name?
Thank you and have a great day!


Problem during compilation

When I attempt to compile with npx graph-compiler I get the following error in regard to the first entry in the datasources array in the sample.json. However, the .gql.json files exist in that directory.
Cannot find module 'erc721.gql.json'
Require stack:
-<EMAIL_ADDRESS>-<EMAIL_ADDRESS>
npx: 6.14.13
Ubuntu 20.04

Try installing @openzeppelin/subgraphs:
npm install @openzeppelin/subgraphs

Then running again

You might be trying to compile a config without the --include flag.
Please have a look at the scripts/deploy.sh script.

Side-note: if you're yarn workspaces (like (scaffold-eth)[https://github.com/austintgriffith/scaffold-eth/] does), you may need to adjust the nohoist directive in the root package.json file. Otherwise, the --include path won't match.

Try installing @openzeppelin/subgraphs:
npm install @openzeppelin/subgraphs

Then running again

I was running the command in this raw repository, I guess it's supposed to be executed only when it's a dependency?

I ran this command in the raw repository:
npx graph-compiler \
  --config configs/sample.json \
  --include node_modules/@openzeppelin/subgraphs/src/datasources \
  --export-schema \
  --export-subgraph

Hello @marceljay
This repo is designed to be "included" by doing npm install @openzeppelin/subgraphs in your working directory. If you do so, then the command you wrote should work.
If you use git clone instead, you'll need to run npm run prepare yourself, and change the include path to point to ./src/datasources


Update and move game template

It has a CMakeLists and should be a good base for out-of-tree projects. The VS solution is a pain to move however (You need to adjust the project paths in the sln and the include/library paths in the vcxproj). Still working on those docs...

Thank you! Visual Studio is wholly terrible in this respect- hand-editing the config files is just painful. I think it's possible to create a template in its native format, but I haven't played with that since waaay back in early 32Blit pre-alpha days.


Version endpoint in Miniflux API

Hello,
as far as I can see the Miniflux API exposes no endpoint to get the version of Miniflux.  Would you mind to add such an endpoint?  Or perhaps extend the existing health check endpoint to include the miniflux version in its response?  If you agree I'd give a pull request a shot (will take a while though since I'm not familiar with Go).
I have an Ansible role which provisions Miniflux on a server, and I'd like to somehow check that Miniflux runs in the expected version after an upgrade.  My idea was to use the Miniflux API to check, but I'm also open for any alternatives (particularly any that don't need any changes in Miniflux itself).
Cheers

There is no API endpoint to expose the application version. But you could run miniflux -v from your Ansible role.
Adding an API endpoint for the version should be straightforward.

But you could run miniflux -v from your Ansible role.

Testing the endpoint would confirm that the expected version really runs :)

Adding an API endpoint to get the version should be straightforward.

I'll try to make a PR :)


Switching camera modes causes UI flicker/glitch

Hey
First off, great library.
I've found a glitch when switching camera modes. When switching from photo mode to video mode, the preview appears to shrink to around half the size, then flick back to full size again in a split second. Is there any way to mitigate this? It's most noticeable on older hardware (4s) but still visible on iphone 6.
You can test this with the following code:
@interface ViewController () <PBJVisionDelegate>
@property (nonatomic) PBJVision *camera;
@end

@implementation ViewController

- (void)viewDidLoad {
    [super viewDidLoad];

    self.camera = [PBJVision sharedInstance];
    self.camera.cameraMode = PBJCameraModePhoto;
    self.camera.cameraOrientation = PBJCameraOrientationPortrait;
    self.camera.focusMode = PBJFocusModeContinuousAutoFocus;
    self.camera.captureSessionPreset = AVCaptureSessionPresetMedium;
    self.camera.previewLayer.frame = self.view.bounds;
    [self.view.layer addSublayer:self.camera.previewLayer];

    [self.camera startPreview];

    [self performSelector:@selector(swapModes) withObject:nil afterDelay:3.f];
}

-(void)swapModes{
    self.camera.cameraMode = PBJCameraModeVideo;
}

@end

[self.view layoutIfNeeded] before start preview?
You should probably be calling startPreview on viewWillAppear:

This is just sample code, but yes you are correct, however even with that, the flicker still occurs. In my app im switching the mode whilst the preview is already running, as above (after 3s delay)

thanks @oligriffiths @markst will check it out

Any news about this?

Hey guys, this probably not exactly related to your mode switch issues, but i just want to let you know that you may never solve this problem with modern day hardware and SDK when it comes to mode switching. This plagues all video libraries including GPUImage  If you look on the market, no one is able to achieve this. Even Apple. If you look at most photo capture apps that also do video, they almost always will require the user to do a "mode switch". There is workaround however, if you don't care about the quality of your photos (you're ok with not using AVCaptureSessionPresetPhoto), for example snapshat, where you can simply take a frame from the live preview buffer #183 without ever having to call a preset change.
There are other "clever" tricks you can do to distract the user, for example, a long "warm up" animation, but from my 5 years trying to accomplish smooth preset changes...it has been futile. The example i'm talking about here is long press to record while single press to capture high resolution photo. It can be done,  but not without a very visible hiccup from the hardware.

Up, that's exactly what I did, used #183 to achieve what I'm looking for. Thanks


"Publish with CLI tools" redirects to tutorial on how to use Visual Studio for publishing

The "Publish with CLI tools" sub-section redirects to https://docs.microsoft.com/en-us/azure/app-service/app-service-web-get-started-dotnet?view=aspnetcore-2.1 which is all about using Visual Studio and there is not  even a single use of the CLI
Please provide an explanation of how to use CLI together with the publishing profile XML files generated by Visual Studio. If this is a no-go then explain how to map the .pubxml file to CLI arguments

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: a2eab542-a420-d6c5-d314-a420837cf602
Version Independent ID: 48c12168-54f3-0b83-f136-565f483a03e9
Content: Deploy ASP.NET Core apps to Azure App Service
Content Source: aspnetcore/host-and-deploy/azure-apps/index.md
Product: aspnet-core
GitHub Login: @guardrex
Microsoft Alias: riande

I believe what happened is that the target changed and the link wasn't updated. The target used to have those instructions.
This is probably what ur looking for ...
https://docs.microsoft.com/aspnet/core/host-and-deploy/visual-studio-publish-profiles#publish-profiles
For example from the topic ...
dotnet publish WebApplication.csproj /p:PublishProfile=<FolderProfileName>

I'll get this squared away ASAP ... thanks for reporting it.

@guardrex Thank you for a very quick and very, very helpful reply

Sure thing ... sorry that link was busted. I'll have it patched up in a few minutes.


Allow hardcoded debug/optimization '/Zi' & '/O2' compiler options to be overridden by user

Issue #884
There were hard coded visual studio compiler options '/Zi' (debug information format) & '/O2' (optimization level). This commit provides the capability to override these hard coded values.
debugInfoFormat='/Z7'
optimizationLevel='/o3'

Signed-off-by: Kent Fletcher<EMAIL_ADDRESS>Context

Contributor Checklist

[x] Review Contribution Guidelines
[x] Make sure that all commits are signed off to indicate that you agree to the terms of Developer Certificate of Origin.
[x] Check "Allow edit from maintainers" option in pull request so that additional changes can be pushed by Gradle team
[x] Provide integration tests (under <subproject>/src/integTest) to verify changes from a user perspective
[x] Provide unit tests (under <subproject>/src/test) to verify logic
[ ] Update User Guide, DSL Reference, and Javadoc for public-facing changes
[x] Ensure that tests pass locally: ./gradlew <changed-subproject>:check

Gradle Core Team Checklist

[ ] Verify design and implementation
[ ] Verify test coverage and CI build status
[ ] Verify documentation
[ ] Recognize contributor in release notes

@lacasseio @big-guy Just reaching out to see where we are on this PR?  Haven't heard anything new since I made the requested changes per the discussion on https://github.com/gradle/gradle-native/issues/884#issuecomment-431923636

Sorry @fletcher-sumglobal for the delay. We discussed this PR internally and rolled a POC according to what we discussed. We don't want to have the override on the compiler task itself, but on the tool chain instead. I was waiting for feedback of @gradle/native before communicating so consider this as just a progress update and not necessarily the final implementation we are aiming for (still waiting for the feedback). It aligns better with what we currently have where overrides are registered at the toolchain level. The branch still considers the optimized model as a boolean (optimized or not).
If we move forward with such implementation, a second PR can be done to change the model to something closer to what we are doing with operating system and architecture.


Ctrl/Cmd click to remove anchor points and waypoints

Thanks to have taken this into account for a next enhancement !


Refactor user and group checks

Use goss's methods, relying on runc's library or goss itself
Fixes #119 (hopefully). If not, then it's a bug in runc.
Progress on #113

CI failures are unrelated.


update to output stdout

Signed-off-by: Wenqi Li<EMAIL_ADDRESS>Fixes # .
Description
A few sentences describing the changes proposed in this pull request.
Checks

[ ] Notebook runs automatically ./runner [-p <regex_pattern>]

option included in https://github.com/Project-MONAI/tutorials/pull/1164


fix: failover to ws if wss fails

High Level Overview of Change
This PR adds a failover for the streams, so that if wss fails, then it attempts to use ws.
Context of Change
Some sidechains may not have certs set up, and may have only ws set up. But the Explorer currently expects them to be wss.
Type of Change

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

TypeScript/Hooks Update
N/A

[ ] Updated files to React Hooks
[ ] Updated files to TypeScript

Before / After

Test Plan
CI passes. Tested locally and it works
Future Tasks
The startup for the stream takes a bit of time. We should see if we can make it faster somehow.

Does not work in prod:
Mixed Content: The page at '<URL>' was loaded over HTTPS, but attempted to connect to the insecure WebSocket endpoint 'ws:<URL>/'. This request has been blocked; this endpoint must be available over WSS.

This problem might require using the backend as a WS proxy


[docker] Added Dockerfile for the Move CLI #130_75

Motivation
Added Dockerfile for Move command-line interface for getting started
easier. This Dockerfile is based on the CI image found in docker/.

Also added building instructions to README.

Providing an easier way to get started with Move.

This Dockerfile can later be used with automated packaging solutions, such as Docker Hub.

Have you read the Contributing Guidelines on pull requests?
Yes
Test Plan
CI/CD Tests are covered

/canary

:sunny: Canary successful

/land


nixos/binfmt: Add QEMU wrapper to preserve argv[0]

Motivation for this change
This PR enables argv[0] preservation for the QEMU binfmt-misc rules generated by boot.binfmt.emulatedSystems. It allows certain packages that rely on argv[0] in their build process (e.g., coreutils for its tests) to correctly build under binfmt.
Traditionally, the emulator invoked by binfmt-misc doesn't know what the original argv[0] is when running an executable, because only the absolute path to the foreign executable is passed. Currently, the emulator will simply use the full path as argv[0]. This leads to problems with multi-call executables as well as diff-based test methodologies used in various packages. For example, coreutils relies on output comparison in many test cases:
uniq: test 145.p: stderr mismatch, comparing 145.p.3 (expected) and 145.p.E (actual)
*** 145.p.3     Mon Oct 18 07:11:43 2021
--- 145.p.E     Mon Oct 18 07:11:44 2021
***************
*** 1,7 ****
! uniq: invalid argument 'badoption' for '--group'
  Valid arguments are:
    - 'prepend'
    - 'append'
    - 'separate'
    - 'both'
! Try 'uniq --help' for more information.
--- 1,7 ----
! /build/coreutils-8.32/src/uniq: invalid argument 'badoption' for '--group'
  Valid arguments are:
    - 'prepend'
    - 'append'
    - 'separate'
    - 'both'
! Try '/build/coreutils-8.32/src/uniq --help' for more information.

binfmt-misc now has the "P" flag that, when enabled, will add an extra argument after the absolute path to the foreign binary containing the original argv[0]. However, this also means that CLI compatibility with existing emulator executables is broken. SUSE has been carrying a patch since 2011 to add -binfmt wrappers that translate the new arguments into ones that regular QEMU accepts (-0 for overriding argv[0]). There have been attempts to resolve this issue upstream, but so far there seems to be no consensus.
This PR adds a statically-linked wrapper for QEMU that translates the arguments. It's possible to rewrite the arguments in the wrapper script that we use (#118926), but that still leaves some remaining issues (e.g., extraneous output when setting LD_PRELOAD).
Tested by building coreutils for riscv64-linux on x86_64-linux under binfmt (before, after).

Things done

Tested on platform(s)

[x] riscv64-linux on x86_64-linux
[x] aarch64-linux on x86_64-linux

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[x] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
21.11 Release Notes (or backporting 21.05 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

[x] Fits CONTRIBUTING.md.

Looks like extra-sandbox-path cannot contain the path to the executable itself, otherwise there will be some
interesting conflicts when you try to build nix.conf.
To reproduce:

Activate emulatedSystems using the previous commit
After activation, run nix-build --check $(nix-store -qd /etc/nix/nix.conf) on the same machine

riscv64-linux coreutils built and passed all tests with QEMU wrapper from this PR now.

True to your word this does appear to fix the LD_PRELOAD error message with binfmt - would you mind adding a test such as the following for this?
  ldPreload = makeTest {
    name = "systemd-binfmt-ld-preload";
    machine = {
      boot.binfmt.emulatedSystems = [
        "aarch64-linux"
      ];
    };
    testScript = let
      helloAarch64 = pkgs.pkgsCross.aarch64-multiplatform.hello;
      libredirectAarch64 = pkgs.pkgsCross.aarch64-multiplatform.libredirect;
    in ''
      machine.start()

      assert "error" not in machine.succeed(
          "LD_PRELOAD='${libredirectAarch64}/lib/libredirect.so' ${helloAarch64}/bin/hello 2>&1"
      ).lower()
    '';
  };

@ofborg test systemd-binfmt


Implement GodotSynchronizationContext.Send and use ConcurrentQueue

Fixes https://github.com/godotengine/godot/issues/73025 and simplifies unneeded usage of BlockingCollection into the more modern ConcurrentQueue which also gets rid of the need for managing IDisposable. For more context on this, IDisposable used to be erroneously implemented on classes that didn't use any unmanaged resources, even by Microsoft, so that potential implementers could get the implementation for free. This is no longer recommended and is mainly a holdover from the old .NET days and doesn't really match the current best practices. ConcurrentQueue is also more performant since it makes use of lock-free methods for thread consistency (although technically, newer version of .NET have switched to using ConcurrentQueue in the implementation of BlockingCollection anyway😁)

Since BlockingCollection uses ConcurrentQueue as the default implementation, what's the benefit of using ConcurrentQueue directly?
Removing the IDisposable implementation breaks compat, I'm not sure if we'd be OK with it given how this class is likely not used directly by most users.

Since BlockingCollection uses ConcurrentQueue as the default implementation, what's the benefit of using ConcurrentQueue directly?
Removing the IDisposable implementation breaks compat, I'm not sure if we'd be OK with it given how this class is likely not used directly by most users.

So I had actually queued up the rough version of this change locally back in October before the implementation of IDisposable was added, and then just got busy and forgot to actually follow up 😁
But yeah you're 100% right that this is technically a breaking public interface change if anyone decided to write code around the implementation. I figured it might be alright since the change is technically all still within the 4.x beta and only lived for under 6 months? If not, I can push another commit to put it back, no worries.
As for the actual benefit, it's just more clear to the reader on the usage of the data structure (ConcurrentQueue is pretty well-known in the .NET community to be the best choice for a multithreaded FIFO queue and BlockingCollection is pretty well-known to be obsolete). I actually didn't realize myself that BlockingCollection had been changed to use ConcurrentQueue under the hood until I was source-diving a while back on some other projects.

Thanks! And congrats for your first merged Godot contribution :tada: