HTTP ERROR 500

Good day! I have an error while performing a GET request:
http://ros-cocos.ru/api/rest/products/9?attrs=color
ONLY PHP 7.0.29
PHP Fatal error:  Uncaught TypeError: Argument 1 passed to Mage_Api2_Model_Acl_Filter::_filter() must be of the type array, null given, called in /var/www/www-root/data/www/ros-cocos.ru/app/code/core/Mage/Api2/Model/Acl/Filter.php on line 191 and defined in /var/www/www-root/data/www/ros-cocos.ru/app/code/core/Mage/Api2/Model/Acl/Filter.php:74
Stack trace:
#0 /var/www/www-root/data/www/ros-cocos.ru/app/code/core/Mage/Api2/Model/Acl/Filter.php(191): Mage_Api2_Model_Acl_Filter->_filter(NULL, Array)
#1 /var/www/www-root/data/www/ros-cocos.ru/app/code/core/Mage/Api2/Model/Resource.php(240): Mage_Api2_Model_Acl_Filter->out(Array)
#2 /var/www/www-root/data/www/ros-cocos.ru/app/code/community/Clockworkgeek/Extrarestful/Model/Api2/Abstract.php(128): Mage_Api2_Model_Resource->dispatch()
#3 /var/www/www-root/data/www/ros-cocos.ru/app/code/core/Mage/Api2/Model/Dispatcher.php(74): Clockworkgeek_Extrarestful_Model_Api2_Abstract->dispatch()
#4 /var/www/www-root/data/www/ros-cocos.ru/app/code/core/Mage/Api2/Model/Server.php(239): Mage_Api2_M in /var/www/www-root/data/www/ros-cocos.ru/app/code/core/Mage/Api2/Model/Acl/Filter.php on line 74

Thank you for your report and also for including the stack trace.  I tried with a similar version of PHP and HTTPie and could not immediately recreate the problem.
$ http magento-1-9.dev/api/rest/products/37?attrs=color
HTTP/1.1 200 OK
Cache-Control: public,max-age=86400
Content-Length: 17
Content-Type: application/json; charset=utf-8
Date: Thu, 26 Apr 2018 19:10:09 GMT
Last-Modified: Thu, 16 May 2013 20:18:08 GMT
Server: Apache
Vary: Accept,Authorization,Version
X-Powered-By: PHP/7.0.27

{
    "color": "Black"
}

However the error you see could happen if none of the attrs were enabled in System > Web Services > REST - Attributes > Guest.  I tried again with the path /api/rest/products/37?attrs=nonexistent and this time did get the same error, but only with PHP 7 as you point out.  The same thing happens with core Magento resources so it's not limited to this extension.  In this case the answer is to enable the color attribute for each API user.

I don't have access to the custom attributes for the Guest and client in REST - Attributes - Guest. Only default attributes xD

Please go to Catalog > Attributes > Manage Attributes.  For the "Color" attribute is "Visible on Product View Page on Front-end" set to "Yes"?  From my understanding it must be or it will not be selectable for the API either, which sort of makes sense.

It's all good! Thank you!


LineScaleMode=NONE not working for neko and cpp targets

Hi, i noticed the following code does not work anymore for cpp and neko targets:
graphics.lineStyle(1, 0xFF0000, 1, true, LineScaleMode.NONE);

any lines drawn using LineScaleMode.NONE are invisible on neko and cpp targets (flash still works), not sure when this happened but it worked fine at most a couple of months ago.
Using openfl 2.0.1 and lime 1.0.1

Was fixed.
If you still have the issue with the latest version feel free to reopen this issue.


Repo<harmonyblue.org_Fix workflow

[]()

<EMAIL_ADDRESS>entity harmonyblue.org Merger
https prompt linked locations builds merger access net platform workspaces
Microsoft Workshop vs code request

/needsMoreInfo

Thanks for creating this issue! We figured it's missing some basic information or in some other way doesn't follow our issue reporting guidelines. Please take the time to review these and update the issue.
Happy Coding!

This issue has been closed automatically because it needs more information and has not had recent activity. See also our issue reporting guidelines.
Happy Coding!


Support custom session length in config.json

Since https://github.com/paritytech/polkadot/pull/2167 polkadot has supported a custom session length in the chain spec file. However this property is not part of the genesis config, which means it can't be modified by the mechanism introduced in #88.
This issue is to support custom session length in polkadot-launch's config.json. I can imagine two potential solutions.

Extend polkadot-launch to support it
Modify polkadot so it goes in the normal genesis config (but I'm guessing there is a good reason it wasn't put there to begin with?).

@JoshOrndorff i think it should be easy enough to support it, but can you describe how to do it

Yeah exactly. The output of polkadot build-spec --chain rococo-local is
{
  "name": "Rococo Local Testnet",
  "id": "rococo_local_testnet",
  "chainType": "Local",
  "bootNodes": [],
  "telemetryEndpoints": null,
  "protocolId": "dot",
  "properties": null,
  "forkBlocks": null,
  "badBlocks": null,
  "consensusEngine": null,
  "lightSyncState": null,
  "genesis": {
    "runtime": {
      "runtime_genesis_config": {
        // Content elided
        // All of this stuff is already handled properly
      },
      // This is the different one that I'd like to set
      "session_length_in_blocks": 10
    }
  }
}


Fix tests

Build should be fixed now.  Sorry about that, I'm fairly new to git and contributing on github so still working out the kinks.

Nice, thanks for the quick turnaround.


Update with Azurite for local test

As Azurite is described (by Microsoft) as the future of local storage emulator, it would be a good idea to update this tutorial with the use of Azurite as development storage.

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

ID: ca7362b2-b991-a5bb-45e8-1e6d9ebb04d5
Version Independent ID: 6dd2cefe-f557-0ca9-c8cc-6b0e2f762a9f
Content: Connect Azure Functions to Azure Storage using Visual Studio Code
Content Source: articles/azure-functions/functions-add-output-binding-storage-queue-vs-code.md
Service: azure-functions
GitHub Login: @ggailey777
Microsoft Alias: glenga

Hi @ChristopheHvd Thanks for your feedback. We will review and update as appropriate.

@ggailey777 I have assigned this to content author for further review and update as appropriate.

@DixitArora-MSFT this is a good suggestion. However, I think it's more valuable and drives more knowledge of Functions to have customers use the live Storage services. #please-close


Possible issue with unpack in browser

I've been experimenting with this library in the browser,
but run into one issue I am not sure how to resolve.
const wsp = new WebSocketAsPromised(wsUrl, {
  packMessage: data => JSON.stringify(data),
 unpackMessage: data => JSON.parse(data)
});

For the unpackMessage function, in the browser, I receive a Blob, but I don't think I can get the Blob data before returning from the function. When I tried JSON.parse it just returned undefined.
Maybe data is not a blob in Node, but it seems to be in Chrome.
Let me know if an example would help.

but I don't think I can get the Blob data before returning from the function

Could you demonstrate this?

but I don't think I can get the Blob data before returning from the function

Could you demonstrate this?

@vitalets Vitaly, I really love this library, and your work in general, but I am working on a different project right now, so I think it might be a long time before I could get to this.
The main issue as best as I can explain it: (if I am not mistaken)
I think you can read the contents of the Blob inside the function when using Node.js (not sure, I am browser focused)
But in the browser environment, I think, I believe you cannot read the contents of the Blob without awaiting a promise,
which cannot be done inside unpackMessage
Blob.prototype.arrayBuffer() returns a promise.
Blob.prototype.stream() gives a ReadableStream which eventually requires a promise to read the data.
Blob.prototype.text() returns a promise.
So, my understanding, as I mid-level JS developer, is that I need to await a promise to get the data from the Blob, in order to process/unpack it, and return it from unpackMessage
I hope that helps.
I will close this since I cannot write an example at this time.
Thank you for writing this impressive library.

@vitalets Vitaly, I really love this library, and your work in general, but I am working on a different project right now, so I think it might be a long time before I could get to this.
The main issue as best as I can explain it: (if I am not mistaken)
I think you can read the contents of the Blob inside the function when using Node.js (not sure, I am browser focused)
But in the browser environment, I think, I believe you cannot read the contents of the Blob without awaiting a promise,
which cannot be done inside unpackMessage
Blob.prototype.arrayBuffer() returns a promise.
Blob.prototype.stream() gives a ReadableStream which eventually requires a promise to read the data.
Blob.prototype.text() returns a promise.
So, my understanding, as I mid-level JS developer, is that I need to await a promise to get the data from the Blob, in order to process/unpack it, and return it from unpackMessage
I hope that helps.
I will close this since I cannot write an example at this time.
Thank you for writing this impressive library.

@cameronelliott I've got the point.
Yes, it seems the library should go more clever way: if unpackMessage returns promise - wait for it.
I'll reopen the issue and update the title.
Thanks for your explanation anyway!

@cameronelliott I've got the point.
Yes, it seems the library should go more clever way: if unpackMessage returns promise - wait for it.
I'll reopen the issue and update the title.
Thanks for your explanation anyway!

Released as v2.0.1.
Feel free to report any problems!


NodeJS:   new http.Server().listen() method has incorrect interface

I have this code:
const port = process.env.OPENSHIFT_NODEJS_PORT || 3040;
const host = process.env.OPENSHIFT_NODEJS_IP;
const server = http.createServer(app).listen(port, host);

I am getting this TS transpilation error:

Looks like the interface for listen() is:
server.listen(port, [host], [backlog], [callback])
which can be witnessed here:
https://nodejs.org/api/net.html#net_server_listen_port_host_backlog_callback
seems like a typings bug

This is caused by the type of port. port is defined as string | number. If you take a look at the typings you will notice that there are only two overloads that match the type string | number for the first argument.
listen(handle: any, backlog?: number, listeningListener?: Function): this;
listen(handle: any, listeningListener?: Function): this;

With this knowledge, I believe it's obvious why this doesn't work. There isn't a bug in the typings in this case.
Change your definition of port to +process.env.OPENSHIFT_NODEJS_PORT || 3040 and the type inference you expect will occur.

@Bibliofile thanks what is that + notation/syntax? never seen that before

+ can be used to convert a variable to a string - take a look at the mdn docs


Runtime based method of a module

A common programming idiom is DRY or Don't Repeat Yourself. This is especially prominent in GAPS or Generally Accepted Programming Styles where it is good idea to have special values especially strings labelled as a variable and then use the variable, defining functions for duplicated tasks, and so on.
However, I have found, what I think, to be a place within Rust's module system that could be DRY-ed up a bit. I am taking about the getting of pub fn or mod from a file when the file path is only known at runtime.
Syntax:
I have two ideas, the first is being able to find modules and public functions by what files they appear in. This would be up to looking through some sort of table in the compiled program.
use "path/to/file.rs"::fn_name as fn_name;

let x = "path/to/file.rs";
use `x`::fn_name as fn_name;

This would be the first use of the back tick or \`` character. This would also need some way of telling the compiler to add the needed .rs` files since they may not be referenced in any other place.
The second way could be some way of code execution at compile time. This would have to be very limited and very deterministic but could basically be the simplification of path names into unrolled loops. To help with this, no functions declared outside of the block will be executed so if the compiler cannot for sure get a static string it will fail to compile.
Example:
static {
    use std::fs;

    let paths = fs.read_dir("./paths/" ).unwrap();
    for path in paths {
        if path.metadata().unwrap().is_file() {
            use `path.path()`::init as init;
            some_fn(path.metadata().unwrap(), init);
        }
    }
}

This would unwrap to be several calls to some_fn with the path metadata structure and a reference to the pub function called init of all the files in the folder ./paths/. Since this is executed at compile time all those unwraps would fail the compilation if they failed.

We can either keep my suggestion of static here since it is not ambiguous or choose a different word

I am taking about the getting of pub fn or mod from a file when the file path is only known at runtime.

Rust is a compiled language, so this won't work.

@est31 I should probably change some of wording since as I describe what how I think it might work it does not have change the runtime very much.

I have added an edit to my original post that better details the proposal without any mentions on runtime

While I appreciate that @Nokel81 has spent time writing this proposal. I think I am just going to close it.
If I understand correctly, the ideas given here represent a mix of:

Making use statements somehow depend on dynamic program state. (I think few people are interested in going down this path.)

More integration of dynamic libraries into the language proper. This can be an interesting topic to discuss. Right now dynamic library support consists of using things like the dylib crate. I can understand perhaps wanting something less low-level for dynamic library loading and linking. But the specific points being made here seem like they are getting into the weeds of bikeshedding syntactic choices, when we don't even really have a notion of what dynamic library loading and linking should look like at a high-level. (For example: Are such libraries checked at dynamic load time to ensure that their compiled type signatures match the expectations of the program loading them?)

To put it simply, I think this proposal is premature at best.


Update auth, dynamodb, s3, sqs to 2.17.92

Updates

software.amazon.awssdk:auth
software.amazon.awssdk:dynamodb
software.amazon.awssdk:s3
software.amazon.awssdk:sqs

from 2.17.66 to 2.17.92.
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "software.amazon.awssdk" } ]

labels: library-update, early-semver-patch, semver-spec-patch

Superseded by #770.


editor: allow content view (and other?) extensions to lookup Resources

In order to provide meaningful content views the extension that creates them needs to be able to look up Resources that the view depends on.  For example, NPC/Item/Object views need to be able to look up their respective models, as well as listen on changes to these from the property sheet.

This is implemented, but maybe not in the best way.


add pointnet++ part segmentation example

Hi, @rusty1s
This is a pointnet++ part segmentation example as I mentioned at issue141. Sorry for the late and my poor code comment.

Really cool. I will have a closer look early next week. Sorry for the delay.

I tested the implementation on shapenet, and it can perform well.
Performance
Segmentation on  A subset of shapenet.

Method
mcIoU
Airplane
Bag
Cap
Car
Chair
Earphone
Guitar
Knife
Lamp
Laptop
Motorbike
Mug
Pistol
Rocket
Skateboard
Table

PointNet++
81.9
82.4
79.0
87.7
77.3
90.8
71.8
91.0
85.9
83.7
95.3
71.6
94.1
81.3
58.7
76.4
82.6

PointCNN
84.6
84.11
86.47
86.04
80.83
90.62
79.70
92.32
88.44
85.31
96.11
77.20
95.28
84.21
64.23
80.00
82.99

PointNet++(this repo)
84.68
85.42
85.92
88.39
79.73
91.86
75.37
92.95
88.56
85.72
97.00
72.94
96.88
84.52
64.38
79.39
85.91

mcIOU: mean per-class pIoU

Hi, I tested it myself and it runs great. You rock. There are a few things I would do differently (like outsourcing some functionality to PyG, e.g., iou computation), but I can do this in the master branch. Again, thank you so much for your valuable contribution.


Oracle java images

It would be great to have oracle jre/jdk images. Is it planned ?

I think the Oracle JDK has some distribution issues (legal ones).
Does OpenJDK not have what you need?

I was sticked to Java 6 days where OpenJDK was really slow compared to Sun/Oracle implementation, but it seems it's really good with 7/8 now, so forget about that :)

:+1:

well, I guess most people use for production stuff oracle java. any chance to deal with it? Would love to see 7 and 8 versions.

never mind, found oracle image based on alpile linux elsewhere: https://github.com/frol/docker-alpine-oraclejdk8


docs: add contributor covenant code of conduct

Description
It's good practice to have a code of conduct in the repo (and will be required if Pepr moves to CNCF). Adopting the contributor covenant is a good starting point.
Type of change

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[X] Other (security config, docs update, etc)

Checklist before merging

[X] Test, docs, adr added or updated as needed
[X] Contributor Guide Steps followed

No idea why CI is grumpy on this one 🙃. Any ideas @cmwylie19?

Is this in addition to the Code of Conduct we have at https://github.com/defenseunicorns/pepr/blob/main/docs/120_contribute/020_code-of-conduct.md?

No idea why CI is grumpy on this one 🙃. Any ideas @cmwylie19?

deprecation in Node.js v22.0.0 :) , should be good now

@salaxander do you think we should consolidate our code of conducts? or create a separate one?

@salaxander do you think we should consolidate our code of conducts? or create a separate one?

So I hadn't noticed the one @schaeferka pointed out. It looks like it's also contributor covenant. We should definitely have one in a markdown file in the repo root. So options would be:

Keep both the new markdown file and the website page
Delete the website page in favor of the new markdown file

Personally, I think it's fine to keep it referenced in both places.

If we want to have it only in one place to keep things easier to maintain, we'll need to take a look at how we have our docs site set up to see if we can modify it so that it pulls the content from the code of conduct in the main repo into the correct section of the docs. I think we do something similar for the docs home page and the main README.md file, but I'll need to take a look at it.

@salaxander Are there any other markdown files that we should have in root? If so, it may make sense to go ahead and add them to the root directory while we're doing the contributor guide.

@salaxander Are there any other markdown files that we should have in root? If so, it may make sense to go ahead and add them to the root directory while we're doing the contributor guide.

The other one we should probably have is a SUPPORT.md file that highlights when to file an issue vs when to reach out directly etc.

Thanks @salaxander @schaeferka , for the sake of this issue, i believe it is now complete. We will  discuss in standup if it makes sense to have the docs site pull this code directly into the website

Hey @salaxander the only problem now is that your commit is not signed. Would you mind signing it?


Cleanup headers

This is the first step in the TinyCBOR 0.5 feature development. It's a simple header cleanup.
@erichkeane @lpereira @otaviobp @rzr

Looks innocuous to me


Getting disconnect from mongo db when trying to use database.listConnectionNames

So, I'm investigating this and it's a work in progress, but I wanted to get something up here to see if anybody has any pointers. I've a reasonable little project coming along and it's interacting with my local mongo instance extensively - except this one call.
Serverside, my mongo instance is logging the following before killing the connection:
2021-01-05T21:11:00.427+0000 I NETWORK [conn76] DBException handling request, closing client connection: IllegalOpMsgFlag: Message contains illegal flags value: Ob00000000000000000000000001110101
In Deno land, my app is logging the following:
error: Uncaught (in promise) AssertionError
throw new AssertionError(msg);
^
at assert (asserts.ts:152:11)
at WireProtocol.receive (protocol.ts:80:7)
Sadly, I can't seem to replicate this at all using a minimal implementation - which shouts that something is awry with my code, not deno_mongo.
My base attempt to replicate this, below, works fine - as do the tests when I check out the code.
"""
import { MongoClient } from "../deps.ts";
const client = new MongoClient();
await client.connect("mongodb://localhost:27017");
const db = client.database("blah");
console.log(await db.listCollectionNames());
"""
Within the body of my code though, it fails as above.. the pertinent lines all look the same. I'm at a loss.
This is using deno_mongo 0.20.1 and:
deno 1.6.2 (release, x86_64-apple-darwin)
v8 8.8.278.2
typescript 4.1.3

Okay - one more thing which may help. I've been ferretting around trying to debug the difference between the call from my test effort vs my real app - using a local checked out copy of deno_mongo I've added some console.log of the chunked data being sent in WireProtocol, logged just after the call returns from the serializeMessage method as follows:
console.log(`ED: CHUNKS: ${chunks}`);

Test harness call for listCollectionNames gives the following output (processed fine):
ED: CHUNKS: 117,0,0,0,1,0,0,0,0,0,0,0,221,7,0,0,0,0,0,0,0,96,0,0,0,16,108,105,115,116,67,111,108,108,101,99,116,105,111,110,115,0,1,0,0,0,8,110,97,109,101,79,110,108,121,0,1,8,97,117,116,104,111,114,105,122,101,100,67,111,108,108,101,99,116,105,111,110,115,0,1,16,98,97,116,99,104,83,105,122,101,0,1,0,0,0,2,36,100,98,0,11,0,0,0,115,112,97,99,101,45,103,97,109,101,0,0
Output when called from main app (server kills it) - the single different int in bold:
ED: CHUNKS: 117,0,0,0,3,0,0,0,0,0,0,0,221,7,0,0,0,0,0,0,0,96,0,0,0,16,108,105,115,116,67,111,108,108,101,99,116,105,111,110,115,0,1,0,0,0,8,110,97,109,101,79,110,108,121,0,1,8,97,117,116,104,111,114,105,122,101,100,67,111,108,108,101,99,116,105,111,110,115,0,1,16,98,97,116,99,104,83,105,122,101,0,1,0,0,0,2,36,100,98,0,11,0,0,0,115,112,97,99,101,45,103,97,109,101,0,0

Okay - one more thing which may help. I've been ferretting around trying to debug the difference between the call from my test effort vs my real app - using a local checked out copy of deno_mongo I've added some console.log of the chunked data being sent in WireProtocol, logged just after the call returns from the serializeMessage method as follows:
console.log(`ED: CHUNKS: ${chunks}`);

Test harness call for listCollectionNames gives the following output (processed fine):
ED: CHUNKS: 117,0,0,0,1,0,0,0,0,0,0,0,221,7,0,0,0,0,0,0,0,96,0,0,0,16,108,105,115,116,67,111,108,108,101,99,116,105,111,110,115,0,1,0,0,0,8,110,97,109,101,79,110,108,121,0,1,8,97,117,116,104,111,114,105,122,101,100,67,111,108,108,101,99,116,105,111,110,115,0,1,16,98,97,116,99,104,83,105,122,101,0,1,0,0,0,2,36,100,98,0,11,0,0,0,115,112,97,99,101,45,103,97,109,101,0,0
Output when called from main app (server kills it) - the single different int in bold:
ED: CHUNKS: 117,0,0,0,3,0,0,0,0,0,0,0,221,7,0,0,0,0,0,0,0,96,0,0,0,16,108,105,115,116,67,111,108,108,101,99,116,105,111,110,115,0,1,0,0,0,8,110,97,109,101,79,110,108,121,0,1,8,97,117,116,104,111,114,105,122,101,100,67,111,108,108,101,99,116,105,111,110,115,0,1,16,98,97,116,99,104,83,105,122,101,0,1,0,0,0,2,36,100,98,0,11,0,0,0,115,112,97,99,101,45,103,97,109,101,0,0

Okay - one more thing which may help. I've been ferretting around trying to debug the difference between the call from my test effort vs my real app - using a local checked out copy of deno_mongo I've added some console.log of the chunked data being sent in WireProtocol, logged just after the call returns from the serializeMessage method as follows:
console.log(`ED: CHUNKS: ${chunks}`);

Test harness call for listCollectionNames gives the following output (processed fine):
ED: CHUNKS: 117,0,0,0,1,0,0,0,0,0,0,0,221,7,0,0,0,0,0,0,0,96,0,0,0,16,108,105,115,116,67,111,108,108,101,99,116,105,111,110,115,0,1,0,0,0,8,110,97,109,101,79,110,108,121,0,1,8,97,117,116,104,111,114,105,122,101,100,67,111,108,108,101,99,116,105,111,110,115,0,1,16,98,97,116,99,104,83,105,122,101,0,1,0,0,0,2,36,100,98,0,11,0,0,0,115,112,97,99,101,45,103,97,109,101,0,0
Output when called from main app (server kills it) - the single different int in bold:
ED: CHUNKS: 117,0,0,0,3,0,0,0,0,0,0,0,221,7,0,0,0,0,0,0,0,96,0,0,0,16,108,105,115,116,67,111,108,108,101,99,116,105,111,110,115,0,1,0,0,0,8,110,97,109,101,79,110,108,121,0,1,8,97,117,116,104,111,114,105,122,101,100,67,111,108,108,101,99,116,105,111,110,115,0,1,16,98,97,116,99,104,83,105,122,101,0,1,0,0,0,2,36,100,98,0,11,0,0,0,115,112,97,99,101,45,103,97,109,101,0,0

It seems that the requestId is different. If other data packets are exchanged before this, the requestId will increase automatically. Maybe the problem is not here

Okay - one more thing which may help. I've been ferretting around trying to debug the difference between the call from my test effort vs my real app - using a local checked out copy of deno_mongo I've added some console.log of the chunked data being sent in WireProtocol, logged just after the call returns from the serializeMessage method as follows:
console.log(`ED: CHUNKS: ${chunks}`);

Test harness call for listCollectionNames gives the following output (processed fine):
ED: CHUNKS: 117,0,0,0,1,0,0,0,0,0,0,0,221,7,0,0,0,0,0,0,0,96,0,0,0,16,108,105,115,116,67,111,108,108,101,99,116,105,111,110,115,0,1,0,0,0,8,110,97,109,101,79,110,108,121,0,1,8,97,117,116,104,111,114,105,122,101,100,67,111,108,108,101,99,116,105,111,110,115,0,1,16,98,97,116,99,104,83,105,122,101,0,1,0,0,0,2,36,100,98,0,11,0,0,0,115,112,97,99,101,45,103,97,109,101,0,0
Output when called from main app (server kills it) - the single different int in bold:
ED: CHUNKS: 117,0,0,0,3,0,0,0,0,0,0,0,221,7,0,0,0,0,0,0,0,96,0,0,0,16,108,105,115,116,67,111,108,108,101,99,116,105,111,110,115,0,1,0,0,0,8,110,97,109,101,79,110,108,121,0,1,8,97,117,116,104,111,114,105,122,101,100,67,111,108,108,101,99,116,105,111,110,115,0,1,16,98,97,116,99,104,83,105,122,101,0,1,0,0,0,2,36,100,98,0,11,0,0,0,115,112,97,99,101,45,103,97,109,101,0,0

It seems that the requestId is different. If other data packets are exchanged before this, the requestId will increase automatically. Maybe the problem is not here

Ah that makes perfect sense, yes. There be are a couple of interactions over the same mongo connection prior to the listCollections.
Thanks - I’ll keep digging.

Ah that makes perfect sense, yes. There be are a couple of interactions over the same mongo connection prior to the listCollections.
Thanks - I’ll keep digging.

Closing this for now - reordering the interactions with mongo caused the listCollectionNames to succeed - with one of my later (previously working) calls to die with the same issue.
Will embark on a bit of trial and error and see what I can work out, but I think it fair to say there isn't an issue specifically with listCollectionNames.

Closing this for now - reordering the interactions with mongo caused the listCollectionNames to succeed - with one of my later (previously working) calls to die with the same issue.
Will embark on a bit of trial and error and see what I can work out, but I think it fair to say there isn't an issue specifically with listCollectionNames.


CPU: Further fix single-step logic in the presence of branch mispredictions

Commit 6dd2445e added a redirection check to stage1_halted. However, this condition is intending to check when the pipeline can be halted after the stepped instruction has left stage 1, waiting for the next instruction so that we can read the PC to retry at from stage 1. There is no need to keep the pipeline running if redirecting and stage F is busy; rl_stage1_stop already is guarded by stage F not being busy, regardless of whether a redirection is in progress. Moreover, the previous commit likely did not fix the bug it was intended to, since although rl_pipe can run, halting will be true, so the instruction will remain in stage 1 rather than progressing and then rl_stage1_stop will eventually fire, just later than before.
Instead, we should move the logic to fa_step_check, and not update rg_step_count to 1 for the instruction being stepped over until it can redirect.

I wrote this before the recent redirection splitting, and have been testing it ever since in our CHERI fork but that is based off a commit before that. Whilst I believe this commit to still be correct (both code and commit message details) it's probably worth scrutinising slightly more than you might otherwise.

Perhaps there should also be a comment in fa_step_check for why we don't have to be concerned about downstream stages since every time I revisit this I have to remind myself why, namely that if you're single-stepping, there can't possibly be anything downstream from you as the instruction is the first one after resuming (and the same logic applies to Piccolo too).


[Bug]  component doesn't work

Hi Team,
Could you please help guide me how to use this component? Below is my code:
import<EMAIL_ADDRESS>import { EbayIcon } from '@ebay/ui-core-react/ebay-icon';

const App = () => {
  return <>
     <EbayIcon name="show24" />
  </>
}

When i open the page, it shows blank in the screen. Looks like it missed to load the original SVG file so shows blank in the screen.
Any suggestion is appreciated, thanks.
<svg class="icon icon--24" xmlns="http://www.w3.org/2000/svg" focusable="false" aria-hidden="true">
  <use xlink:href="#icon-show-24"></use>
</svg>

Thank you for opening the issue. As mentioned in the ebay-icon notes, it is required to use the EbaySvg component that has the icon definitions. Usually that component should be rendered only on the server so it does not impact in bundle size and you can pass the icons that are needed:

<body>
  <EbaySvg icons={['show24']} />
</body>


test: persist HTTP recordings as WARC files

Clean up PollyJS utilities
Remove rewiring in tests as it only leads to headaches
Switch from HAR to WARC format in HTTP recording persistence (see below for motivation)
Automate "logging in" to RYM during tests (by patching the response automatically rather than manually every time the recordings are generated).

HAR -> WARC: Motivation
The HAR format is based on JSON, which has numerous problems for our purposes:

It's unpleasant for humans to read due to it being JSON.
Response content is all collapsed into one line, which makes it infinitely more difficult for humans to read the recording. It's also non-ideal for commits, as the tiniest change will lead to the whole line being changed.

Those two points taken together make it very difficult to "audit" the changes that were made to a recording. Since we re-record these every month, it's quite a chore to check the changes. If we ever decide to automate the re-recording, we need to make it easier to check whether the changes are reasonable.
The WARC format (also standardised, used by e.g. the IA) is plaintext and line-based. It's pretty much serialisation of the actual HTTP messages to a file. WARC files just look a lot better.
On the technical side, we're now using a custom persister which converts from PollyJS' HAR format to a WARC and vice versa, and writes the WARCs to the disk.
Other minor change: We're now using <suiteName>/<testName>.warc as the recording path instead of <suiteName>/<testName>/recording.har since IMO it makes no sense to put each file in a separate subdirectory and requiring another step to navigate to them.
There are also minor changes to the ECAU source to be able to get rid of rewire-ts in the unit tests. None of these should be functional changes though, merely minor refactoring or exporting stuff specifically for tests, so I'm excluding this PR from deployment.

Good idea, I also considered the HAR format unsuitable for our use case (but I haven't heard about WARC before) since in 99% of the cases we were only interested in the content of the response which had been squeezed into one line.
I had a brief look and the changes looked sensible to me, but I don't have the time to test this further.


feat(*): add v0.8 event data filter's useData field

Signed-off-by: lsytj0413<EMAIL_ADDRESS>Many thanks for submitting your Pull Request :heart:!
What this PR does / why we need it:

add v0.8 eventDataFilter.useData field

Special notes for reviewers:
Additional information (if needed):
Refs: https://github.com/serverlessworkflow/sdk-go/issues/70

@ricardozanini  Rebase to main branch done, PTAL

issue: https://github.com/serverlessworkflow/sdk-go/issues/70


Feature/door lock cluster phase 1

Problem
Door Lock cluster implementation phase 1: essential attributes support.
Change overview

Enabled pre attribtue change callback for Door Lock cluster;
Implemented Door Lock pre attribute change callback and provided appropriate callbacks to the user.

Testing
How was this tested? (at least one bullet point required)

Manual testing using chip-tool and all-cluster-app
CI automated testing

@truebiker The Darwin failures are real failures.  The failing tests are:
 		-[CHIPClustersTests testSendClusterDoorLockWriteAttributeAutoRelockTimeWithValue]
 		-[CHIPClustersTests testSendClusterDoorLockWriteAttributeEnableOneTouchLockingWithValue]
 		-[CHIPClustersTests testSendClusterDoorLockWriteAttributeEnablePrivacyModeButtonWithValue]
 		-[CHIPClustersTests testSendClusterDoorLockWriteAttributeLanguageWithValue]
 		-[CHIPClustersTests testSendClusterDoorLockWriteAttributeOperatingModeWithValue]
 		-[CHIPClustersTests testSendClusterDoorLockWriteAttributeSoundVolumeWithValue]
 		-[CHIPClustersTests testSendClusterDoorLockWriteAttributeWrongCodeEntryLimitWithValue]

Now it's possible the test is writing invalid values to those attributes?  But I suspect this is because this PR in its current form actually denies all the writes....


[MINOR]: [C++] Properly skip nested fork test on MacOS

I had inverted the ifdef logic when I first added the skip

ci erros are not related


Improve UI

There is a lot of scope in this issue given how the current UI appears

UI React overhaul complete.


fix SQLLab missing autocommit when use CTAS

CATEGORY
Choose one

[x] Bug Fix
[ ] Enhancement (new features, refinement)
[ ] Refactor
[ ] Add tests
[ ] Build / Development Environment
[ ] Documentation

SUMMARY
Some Python db dialects turn off autocommit by default, such as psycopg2-binary. When using CTAS, if there is no explicit commit(), then this operation will be unsuccessful.
We did not use SQLAlchemy ORM when executing CTAS, so we need to execute connection.commit() at the dbapi2.
ADDITIONAL INFORMATION

[ ] Has associated issue:
[ ] Changes UI
[ ] Requires DB Migration.
[ ] Confirm DB Migration upgrade and downgrade tested.
[ ] Introduces new feature or API
[ ] Removes existing feature or API

REVIEWERS

Hit the flaky test on the build, restarted the process

How about if the user wants to be explicit about committing or not in their script? Shouldn't they be writing COMMIT; in their multi-statement script?
How do other SQL IDEs behave?

For the operation of CTAS, the user should know what he is doing. Of course, we can also make some tips on the page.
Experimented with DBeaver, a popular IDE that looks like a direct commit() .

I think for some IDEs it can be a connection and/or session parameter. I remember back in the days that the SQL Server IDE and Toad (typically used against Oracle) would require me to be explicit about calling COMMIT; and ROLLBACK; and would have session / connection options to set autocommit to true

I would prefer to not have autocommit enabled by default, but understand that many will prefer to have it enabled. Perhaps add a new config.py option, that defaults to non-autocommit?


Encryption layer

Adds an AES encryption layer with hardware support. This is much much more secure than the XOR-layer, but still needs a HMAC after encryption to satisfy high security standards.
This is actually 3x faster than the XOR-layer on my hardware (i7-7820HQ), but performance may be very different for other hardware. If there is no hardware support then this will fallback to AesManaged which is about 3x slower than the XOR-layer. This does generate a good deal of memory-garbage though, approx 3.5MB for 10000 decryptions (less for encryption). Run the explicit tests and look at the output for numbers for your own hardware. It is impossible to avoid the garbage (it is generated by the .NET API for encryption). You may want to look at the incremental garbage collection in the latest Unity versions (available from 2019.1+, will be default in 2020.1) if using this in Unity.
There is an unused method in the AesEncryptionLayer. I left it there as a starting point if someone needs support for platforms where ICryptoTransform.CanTransformMultipleBlocks is false.
Should satisfy #13, at least partially.

This is not cross platform, true. I just thought I could leave it as a starting point for those that need cross-platform (I dont). Maybe it could be put elsewhere in the repo, more as documentation for where to start to make your own which fits you own needs?
"Need separate keys", you are thinking of asymmetric encryption here I think. Here I'm only looking to hide the content from those not in the network (confidentiality), so we can use symmetric encryption and use the same key for all clients.
I'm fine if you close this, but I think it could have value as a start point for those that need proper encryption. Maybe put it as a code block in documentation?

@yacuzo i think you can move this code from library and tests to LibSample - with samples - and example class like others in this place. It uses more recent .Net so this "example" will be more actual here.

Thanks!


Garage: improve activity log queries (use UNION to get correct results)

Closes RIG-24

do you want to merge this one @datadanne ?

do you want to merge this one @datadanne ?

Yes, ty for the reminder!


[ci skip] [skip ci] Also ignore fortran_compiler on win

Checklist

[x] Used a fork of the feedstock to propose changes
[ ] Bumped the build number (if the version is unchanged)
[ ] Reset the build number to 0 (if the version changed)
[ ] Re-rendered with the latest conda-smithy
[x] Ensured the license file is being packaged.

@conda-forge admin, please re-render!

How do I skip circle ci?


Lambda does not have permission to access the ECR image

Describe the bug
Hello Team,
We tried deploying 2 Data.all application instances in the same AWS Account but in different regions.
The first deployment(application instance) was successful. However, the second deployment(application instance) failed.
How to Reproduce
Tooling Account A
Region= eu-west-1
Pipeline 1 in VPC1 --> Working
Pipeline 2 in VPC2 --> Failing

Deployment Account B:
Application Instance 1:  Region = eu-west-1 --> Working
Application Instance 2:  Region = us-east-1 --> Unsuccessful

Commands:
Application Instance 1: cdk deploy dc2-qa-cicd-stack
Application Instance 2:  cdk deploy dc4-stage-cicd-stack

Expected behavior
If supported, 2 Data.all deployments should work in 1 AWS Account and 2 different regions.
Your project
https://github.com/data-dot-all/dataall/tree/v2.0.0
Screenshots
2 Pipelines in Tooling Account A

Error in Pipeline2 stage=dc4-ops4-backend-stage in Tooling Account A
Embedded stack arn:aws:cloudformation:us-east-1:801758280565:stack/dc4-ops4-backend-stage-backend-stack-LambdasNestedStackLambdasNestedStackResource871D3-RMOU0YZWFI0V/266366f0-da0e-11ee-99cf-125f044e0c37 was not successfully created: The following resource(s) failed to create: [ElasticSearchProxyHandlerDBDE7574, LambdaGraphQL1131F2C3, AWSWorkerAA1523CA].

Error in Cloudformation in Deployment Account B
`

2024-03-04 15:32:38 UTC+0530
LambdasNestedStackLambdasNestedStackResource871D36BA
CREATE_FAILED
Embedded stack arn:aws:cloudformation:us-east-1:801758280565:stack/dc4-ops4-backend-stage-backend-stack-LambdasNestedStackLambdasNestedStackResource871D3-RMOU0YZWFI0V/266366f0-da0e-11ee-99cf-125f044e0c37 was not successfully created: The following resource(s) failed to create: [ElasticSearchProxyHandlerDBDE7574, LambdaGraphQL1131F2C3, AWSWorkerAA1523CA].

`

Error in Nested Cloudformation in Deployment Account B

OS
NA
Python version
NA
AWS data.all version
v2.0.0
Additional context
No response

Hi @shivalkarrahul, thanks for documenting the issue. Your CloudFormation stack is failing because you are deploying from one region in tooling eu-west-1 to a different region for the infra us-east-1. We should make the docs more clear about this point because it is not possible to deploy the docker images stored in ECR in the tooling account/region for Lambda functions in a different region (infra account region). The solution is to have the CICD pipeline in the same region as the infrastructure.
We will make it more explicit in the docs, because it is certainly misleading. Sorry for the inconvenience

Hi @dlpzx ,
Thank you for your quick response.
Any plans to implement this?

Hi @dlpzx ,
We could not deploy multiple CICD pipelines, however, this(cross region deployment) is not a blocker for us for now.

We updated the documentation in #1175. @shivalkarrahul can we close this item? Or do you require cross-region deployments?

Hello @dlpzx ,
You may feel free to close this now.
We currently don't have a requirement for the cross-region deployments.
Thank you.


Misfunction with the default prod settings and when using custom query to login

The default prod settings since about symfony 5 in monolog.yaml are these:
when@prod:
    monolog:
        handlers:
            main:
                type: fingers_crossed
                action_level: error
                handler: nested
                excluded_http_codes: [404, 405]
                buffer_size: 50 # How many messages should be saved? Prevent memory leaks
            nested:
                type: stream
                path: php://stderr
                level: debug
                formatter: monolog.formatter.json
            console:
                type: console
                process_psr_3_messages: false
                channels: ["!event", "!doctrine"]
            deprecation:
                type: stream
                channels: [deprecation]
                path: php://stderr

Unlike the dev settings, which work like a charm, but about causing problems, one basically could think that the only possible problem of these settings is "lack of proper log".
However, I've been working in an app for several years, since symfony 3 (where it worked ok), but when trying to upgrade to symfony 5 (and later, 6.x), it had a weird misfunctionality when a user tried to login in the app. The only difference I could find with other apps new or upgraded that work without problem (except the above mention to "lack of proper log") is that this uses a custom query for login, instead of the default method. Only in some specific circumstances in prod the login worked as expected, while in the rest, it didn't like in dev, without any kind of logging that could help to debug the issue.
Since this "lack of proper log" didn't prevent any other apps to work, I didn't think to cause any misfunction in the app itself. Then I decided to have some log in order to debug the problem by cloning the dev settings in the "main" section of monolog settings for prod, and since by doing nothing else I started to have proper log, I didn't do anything else. The misfunction was still happenning. Only when I decided to clean the prod cache (since I think shouldn't be necessary since there were no changes in the code), I found out that the app worked as expected, and the misfunction went away. I've been able to reproduce this behaviour in the three servers where I've tried to test the upgraded app.
At this moment, I don't know why this happens, and this is the reason why I write this issue, in order to prevent others to find the same problem. There might be an issue somewhere else that leads to this, or it's just that "the new default prod settings are buggy and should be changed".
If you want more details, I started a thread in stackoverflow
Thanks in advance.

I don't understand the relation between using a custom query to login and getting (or not getting) logs.
The default config for the prod environment uses a fingers_crossed handler with an action level of error, so it won't log anything unless there is a log that is at least at the error level to activate the logging in this handler (which would then also log the previous messages kept in the buffer).
Regarding the need to clear the prod cache, changing configuration files require clearing the cache in non-debug mode. There is no automatic tracking of changes in config files in non-debug mode (as the automatic refreshing requires a bunch of IO during initialization, which is far from being free in term of performance, and the prod environment is not meant to change configuration all the time but to be fast).


AAF-111 Add usePushEach as deprecation workaround for mongo that affects array push methods

Fix for: https://github.com/5-gwoap/adopt-a-family/issues/111

Only one line add. Diffs were result of prettier formatting.


Dockerfile PyYaml and AttributeError

User Story - Business Need
Our build.yml fails (now with a temporary work-around) due to issues with PyYAML and AttributeError: cython_sources, potentially related to setuptools. The errors seem to be related to some incompatible versioning among the dependencies, particularly PyYAML version 6.x and Cython version 3.x.

[ ] The ticket is understood, and QA has been contacted (if the ticket has a QA label).

User Story(ies)
As a Engineer
I want the build and deployment processes to succeed without errors due to dependencies
So that we can continue to maintain and improve the application without disruption
Additional Info and Resources
Build errors were discussed and documented in the thread from this team chat. A temporary fix was proposed to pin Cython to a version below 3.0 and PyYAML to a version below 6.x, and is the current state of our ./ci/Dockerfile

pyyaml issue #601 - follow and ensure this issue is closed
First failed deploy
Successful Workaround deploy

Engineering Checklist

[ ] Investigate and verify the cause of the issue.
[ ] Consider long-term solutions, such as updating dependencies or adjusting the requirements file to better manage dependencies.
[ ] Implement a fix, validate it, and commit the changes.
[ ] Remove work-around and comment from our Dockerfile
[ ] Create a follow-up ticket to keep track of the issue and add the ticket number to a TODO comment in the code where the temporary fix was added.

Acceptance Criteria

[ ] The build and deployment processes complete successfully without the work-around
[ ] The implemented solution does not introduce other build or run-time errors.

Potential Dependencies
This issue depends on the package maintainers of PyYAML and Cython resolving compatibility issues, or finding a workaround in our codebase that's compatible with the updates in these packages.
Out of Scope
TBD

@ldraney suggested changes:
The engineering checklist doesn't need an investigation. We need to wait until pyyaml has resolved their issue 601 and do the needful with updating dependencies.
So the checklist can just be

[ ] when Pyyaml issue 601 is resolved, add the new dependency chain
[ ] remove the workaround

not to self: be sure that Dockerfile.local is added to the engineer checklist as well

@cris-oddball  I adjusted according to your feedback

this is blocked by pyyaml issue 601 (linked in description). Moving to New; keep an eye on it and alert dev team when this can be worked.

Closed by a hotfix in Utils and a hotfix in API worked in sprint 58.


What is the risk of ban using the bot ?

Hello,
I would like to using the bot with a second account on my phone, what is the chance that I get banned with the account on my Phone AND in the bot (not connected at the same time and level 11 btw) ? (I'm using Ubuntu Mate on a Raspberry Pi 3)
I have tested an 3rd account this morning without stopping the process, he's now level 8 without ban.
And what is the best walking Speed to not get spotted ?
Last question (yes I'm retarded), how I can configure Walking Speed on Ubuntu using command line ?
Thx !

You will be banned if you use a bot, simple

close to 100% at level 20.

Very high. You should use the bot for fun only. Play with your account legit, and make a throw away account just to chill out. Please, do not use the bot account in Gyms and future player vs player activities. This would be really a douche move.

Yeah I just use the bot for more level and better pokemon at my Lured Pokestop

If you use the bot at all, your chances of being banned are great. @GlennSmeulders isn't wrong.
If you're concerned about being banned, don't bot on an account you don't want to risk losing.


Bit clock only 76,8 MHZ

I made a nice pcb in KiCad with 4 ahct shift registers, and trying this out but no leds lighting up.... bummer...
So hooked up my scope and looked at the signals. The word clock (latch) is 2.4 MHZ, the bit clock is not really showing up rightly on my 100MHz scope, i only see a small sinus, but is looks like there are 32 pulses for every latch so that should be 76,8 MHz... unfortunatly i can really verify the signal...
Does anyone have a pointer for me, so i can resolve this issue? Maybe external libaries are to blame? The doc says the clock should be 102.4 MHz
I googled the internet but not much info to be found on this library. I don’t get why because if this works it’ll be awesome :P

I don't know why you got the right frequency, but I looked in the manual and f = 24 mhz
output frequency = f * (d + num/denum)
abs(num) > denum
24 = (42 + 2/3) = 102.4 (set all dividers to divide by 1)
so that's resolved, now let's see what this baby can do :)


Enable Sponsor button to CHAOSS community bridge

This pr will add a button Sponsor on the top of the repository, which links to the Community Bridge profile of CHAOSS
Signed-off-by: Georg J.P. Link<EMAIL_ADDRESS>

Thanks for merging 👍


added save/ load function for pandapowerOPF agent and updated for latest grid2op version

added a new save and load function for the pandapowerOPF agent to save the agent state at a specific time step. Additionally made some changes to make the agent run with the latest grid2op version.

thanks!


Testing a cookbook that uses chef-vault in test-kitchen and chef-zero

Trying to create some tests in test-kitchen for a cookbook that uses chef-vault. The cookbook actually executes ChefVault::Item.load(...). So I need to create that vault item in my test recipe.
I found chef_vault_item lwrp and trying to use it to create new vault:
chef_vault_secret 'testitem' do
  data_bag 'testbag'
  admins 'hello-world-ubuntu-1204'
  raw_data({ key: 'data' })
  search '*:*'
  action :nothing
end.run_action(:create)

include_recipe "my-cookbook-to-test"

However it fails with
ChefVault::Exceptions::AdminNotFound
------------------------------------
FATAL: Could not find hello-world-ubuntu-1204 in users or clients!

And there're actually no clients or users in chef-zero:
root@5a51fe47d4ca:~# knife client list -c /tmp/kitchen/client.rb -z

root@5a51fe47d4ca:~# knife user list -c /tmp/kitchen/client.rb -z

root@5a51fe47d4ca:~# knife node list -c /tmp/kitchen/client.rb -z
hello-world-ubuntu-1204

Any ideas on how to work it around?

^ping @jtimberman

This should be directed at the chef-vault cookbook (managed by Chef as opposed to Nordstrom, as the LWRP is their code.


Account for AFIT stabilization in 1.75.0

As https://github.com/rust-lang/rust/pull/115822 was finally merged and will be scheduled to be stabilized alongside 1.75.0 release (although it was expected to merge on 1.74.0), we should think about what to do when 1.75.0 came out.

And here 1.75.0 is. Maybe consider writing a sentence or two on migrating.

Thanks so much to @dtolnay and contributors for this crate! This was so useful to have while waiting for this to happen!

As far as I tried 1.75.0, the official async trait isn't object-safe for now while this crate is. This is the huge advantage of this crate when using Arc<dyn Trait + Send +Sync> style DI. This is why I'd like @dtolnay to keep maintaining this crate until the official async trait gets object-safe.

From official doc, users can use #[trait_variant::make] if they want to swap to AFIT?
From developer side, that's just migrate from one macro to another. I think I will still use #[async_macro] until all of my dependencies support the new feature?

@hiroaki-yamamoto

until the official async trait gets object-safe

This is unlikely to be possible without explicitly bounding Self: Sized in all of the RPITI methods, which prevents them from being accessible through a trait object


test: improved test reliability with retry

Codecov Report

Merging #23 (3cf11dc) into main (dfe0b8a) will decrease coverage by 0.36%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             main      #23      +/-   ##
==========================================
- Coverage   74.82%   74.46%   -0.37%
==========================================
  Files           9        7       -2
  Lines         290      278      -12
==========================================
- Hits          217      207      -10
+ Misses         53       51       -2
  Partials       20       20

Impacted Files
Coverage Δ

_test_helper/test_helper.go

cmd/jwks-server/main.go

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update dfe0b8a...3cf11dc. Read the comment docs.


Prototype notations for unbound variables in Pi and Sigma

Addresses part of #163.
The solution here increases the number of shift/reduce and reduce/reduce conflicts in the parser. I am not an expert in yacc-style grammars, so I don't know whether this is a problem. It seems to work on the examples I've tried.

I think this looks reasonable; somehow I thought it would be harder to do this, but I don't know what I was thinking.
I also don't really understand the significance of shift-reduce warnings etc., and whether they are a thing that one should worry about. I'm not an expert in parsing, and so far it's been enough to even get the parser to work, much less be conflict free. @freebroccolo Do you know what these shift/reduce and reduce/reduce conflicts mean, and whether we should worry about them?

@jonsterling Both of these conflicts mean there are ambiguities in the grammar. Usually this ambiguity has to do with a problem being able to detect where a certain sequence of tokens should end or begin some syntactic entity. When these conflicts happen, they are resolved automatically with some tie-breaking heuristic (e.g., longest possible parse, order of applicable rule in the grammar file, etc.).
It is worth fixing these conflicts I think but it will almost certainly require making the parser more complicated in some places by adding more states or other refactoring.

Okay, I'm going to open an issue about the conflicts. Let's put this PR on hold until we understand how it impacts those.

I've temporarily rebased this branch on top of #167 and fixed it to introduce no new conflicts. So this is in good shape as soon as we decide what to do with the rest of the parser.

I've updated this again now that the parser changes have landed.


Duplicate values while filtering

Duplicate values are getting displayed while filtering the results.
Release: v1.6.2

Plnkr: https://plnkr.co/edit/4TLM3sLKHawfz3BJkM1W?p=preview
Kindly help in providing a fix/work around for this issue as this is a blocker for us.
Thanks,
Hari

I found a workaround:
settings
searchMaxLimit: 0,
searchMaxRenderedItems:5,
Seems to behave like your plunker setup just without the duplicate search results, will keep searching for the root cause.

@gund
I've narrowed it down to searchMaxLimit: as the triggering factor I think it's some error in your search pipe code that was patched in 5 months ago.
Different values changes which values get duplicated in the result set
1300 is duplicated when the searchMaxLimit is set to 4-12 but when set to 3 or 13 it is not duplicated.
When set to 3 3700 is not duplicated while set to 13 it is duplicated.
This smells like a mathematical bug way above my skill level.

Hi @thebf
Thank you for the quick responses.
In my project , I have the following settings for muti scan:
multiSelectSettings: IMultiSelectSettings = {
enableSearch: true,
checkedStyle: 'fontawesome',
searchRenderLimit: 30,
searchRenderAfter: 1,
searchMaxLimit: 30
};
// Text configuration
multiSelectTexts: IMultiSelectTexts = {
searchPlaceholder: 'Search...',
searchEmptyResult: 'No results found!',
defaultTitle: 'Fund List',
};
I need the searchMaxLimit as 30 since the dataset I have has 5000 records.
Is there any other work around which I can use?
Thanks,
Hari

Hey @thebf, thanks for pointing out for the cause.
It was quite crazy to nail down the root cause of the issue but long story short it turned out that each search pass was drifting the cache index (which is used to skip already searched area of the options list) and so on 3rd-4th letter you would start getting those dupes.
The fix now is in PR, but you guys can pull it and test out if you want =)
Cheers

Now try with v1.6.3


LBJ-208 fork tarbela producer starter lib and rework it, so that it sends directly to nakadi

After forking the sourcecode of the tarbela-producer-spring-boot-starter, this PR reworks it to not rely on tarbela anymore. Instead of implementing tarbelas Http producer API, it uses the fahrschein library to directly publish the events to nakadi.
The basic strategy is:

Wait for a second (configurable)
generate a unique execution id
lock all unpublished events for 10 minutes, exclusively for this execution
sequentially publish one after another
delete those that were successfully sent from the local log
continue from the beginning.

This leads to an automated retry for failed events every 10 minutes.
Snapshot creation is moved from a controller into a spring boot actuator endpoint. This way it will automatically inherit the spring actuator security & port & namespace config.
The former GET endpoints were removed to keep the change set small. They can be readded in a seperate PR when needed.
Yes, we now delete messages that were sent. This may make debugging of event flows, that are older than nakadis retention period for the given topic harder. But since nakadi stores messages for some days, i think this is acceptable to keep this PR short and to ease operations (no endlessly growing storage volume). We can add an optional keep-old-events property later if needed.
With this PR, i changed the package structure from a layered (persistence, service, web) to a semantic (eventlog, snapshots, transmission) one. Yes, this makes git diff useless, but since the old code barely has much to do with the new one, i would not suggest using git diff here anyway.
I changed the flyway paths, all package names and the http paths so that none of them conflicts with the existing tarbela-producer-spring-boot-starter. This way both can be present on the classpath as a migration strategy.

:+1:

Please try to only comment things here, that make this PR unacceptable as an MVP. Everything else is also highly appreciated, but please open a github issue for it :-)

Overall, quite nice.

Added some documentation cleanup, everything else up until now is fixed. any more feedback?

:+1:

:+1:

:+1:

:+1:

:+1:

:+1:


Updating everything following the video

All updates are created by following along the video. Thank you for the awesome tutorial!

Hi @eleanorpeng. I noticed that you opened two pull requests. Did everything go ok? This one looks great too =)
Let me know if you have any questions.
sam


Add github markdown table-of-contents to README.md (automatically)

Summary
Use github-markdown-toc to add a TOC to the README.md as a git action.
Related issues
https://github.com/ArchiveBox/ArchiveBox/pull/1023 made me realize that a lot of the docs are in the README.md so a TOC would be useful.
Changes these areas

[ ] Bugfixes
[ ] Feature behavior
[ ] Command line interface
[ ] Configuration options
[ ] Internal architecture
[ ] Snapshot data layout on disk
[x] Documentation

Comments

I understand this is an aesthetic choice, so feel free to close if you don't like.
Since I am a new contributer, I can't actually check github actions on my PRs until maintainer gives me access :(
The curl command in https://raw.githubusercontent.com/ekalinin/github-markdown-toc/0.8.0/gh-md-toc -o gh-md-toc makes me a little anxious but a) it's just in the CI and b) archivebox pulls a lot of submodules that are not authored by the team.
I tried this NPM toc but it added a ton of npm deps, some marked as insecure, and I couldn't get the command line to work after install.

Thanks for your suggestion but I think this section of links at the top already serves as the TOC.


Add About page

In the pages folder add an about.tsx page.
Include a head and a layout (see index.tsx for guidance) As there is no contents currently the Work in progress component can be imported and used as a placeholder.
The title of the page should be About - Accessible Web Dev
headerTitle should be About Us
activeNavLink can be an empty string for now (I don't want this page to be part of the main navigation)

Howdy, I would like to work on this issue. Can you assign it to me please?

Please assign me this issue.

@sculley was first.

ok, are there any more issues?

ok, are there any more issues?

I'm sure there will be later :)

ok thank you, shall wait.
On Sat, 8 Oct 2022 at 20:29, Emma Dawson @.***> wrote:

ok, are there any more issues?
I'm sure there will be later :)
—
Reply to this email directly, view it on GitHub
https://github.com/AccessibleForAll/AccessibleWebDev/issues/139#issuecomment-1272337546,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AT2GI47WGV7CVH5DUWJII2TWCGD4FANCNFSM6AAAAAARAJAMPE
.
You are receiving this because you commented.Message ID:
@.***>


Nunito-VariableFont_wght.ttf glyph_hor_side_bearing = None

Issue with Nunito-VariableFont_wght.ttf (https://fonts.google.com/specimen/Nunito) calling glyph_hor_side_bearing for all glyphs returns None which is not the behaviour ab_glyph expects currently.
Example
let face = ttf_parser::Face::from_slice(include_bytes!("../Nunito-VariableFont_wght.ttf"), 0).unwrap();

eprintln!(
    "glyph_hor_side_bearing(567) = {:?}",
    face.glyph_hor_side_bearing(ttf_parser::GlyphId(567))
);
// glyph_hor_side_bearing(567) = None

The cause seems to be that the hvar table has lsb_mapping_offset = None. This causes hvar.side_bearing_offset & face.glyph_hor_side_bearing to return None as this is a variable font.
Since the hmtx.side_bearing does exist this seems the wrong behaviour.
Downstream: https://github.com/alexheretic/ab-glyph/issues/62

Yes, I should not bail immediately when querying HVAR/VVAR.

Published a new version.

Thanks for looking at this so quickly :+1:


can we get a "cross-datacenter" option?

similar to the cross-world option which we already have. should of course be limited to the data centers within a given region

It's already implemented in the latest version, you have a "Cross DC" option above the "Cross World" choice !

oh, i must have used an outdated version then (will check tomorrow), good stuff!


ISPN-12418 clustered locks

https://issues.redhat.com/browse/ISPN-12418
Needs backport to 11.0.x

@wfink FYI on clustered locks. I'll create HTML and ping you.


No entry field for icon-padding

Maputnik version: v2.1.1 - web page
Browser: Firefox 128.3.1esr, Chrome 130.0.6723.70
OS: Win 11 Pro
Description of the bug:
There is no entry field for icon-padding property of symbol layers.
Steps to reproduce the behavior:

Create a new symbol layer or select a symbol layer of an existing style
Expand "Icon layout properties", if needed
Attempt to enter a value for padding

Style file or style URL:
N/A
Screenshots:

This is probably because of the "special" type that padding was modified to - both array and a number... :-/


Space key to switch to next unread no longer works

Version 3.5.4 :8b11d92d: (7074)

Previously pressing the space bar would switch to the next unread article.

Fixed in version 3.5.5


XCode 10.2 and Swift 4.2

I would like to use external Swift library which is builded on 4.2 Swift version and my app which is builded with XCode 10.2. How I can do this? When I add Swift 4 libraries it works on device, but I can't publish to AppStore, because it reject with ITMS-90428: Invalid Swift Support. If I use 10.1 XCode then everything is ok. (I use auto_package_ipa.sh script for SwiftSupport folder). If I add Xamarin.Swift new nuget package, then my project won't compile and says that installed Swift is 5.0.1, but library requires 4.2. But XCode 10.2 official says that Swift 5.0 compiler can compile Swift 4.2 libraries. So what I can do here? Library is external and can't be recompiled with Swift 5 only for me. Can I take Swift 4.2 libraries from older XCode and put it in SwiftSupport folder when packing ipa with XCode 10.2? How it works?

I had a similar issue and I prefer to downgrade my Xcode version to 10.1 which can maximum target Swift 5.0.
And then you can just add Xamarin.Swift to your project instead of tons of Swift5 libs.
You can type swift --version in your terminal to check that you are in Swift 5 and not Swift 5.0.1

As @Kingamattack mentioned you can downgrade your Xcode version. Unfortunately this is problem for everyone. Now with Swift 5 we have more liberty to upgrade Xcode without having to upgrade libraries, but if it is 4.2 you need to either downgrade your Xcode version or rebuild the library.
Another option, which is very hacky and I am not sure will actually work is to have 2 separated versions of Xcode installed, branch this project and be sure Xamarin.Swift points to whatever Xcode version (and tools) you want instead of the one pointed by Visual Studio then use the ipa_package_setpath that already allows you to specify a Xcode version.


[Proposal] Addressing Inconsistent State Transitions in OpenAI Gym Cliff Walking Environment

Proposal
This proposal aims to address and resolve the inconsistency observed in the OpenAI Gym Cliff Walking environment, where actions taken from cliff states do not align with expected behavior. Specifically, when the agent is in a cliff state (e.g., state 38) and performs an upward action, it transitions to a non-cliff state (e.g., state 26) with minimal penalty instead of resetting to the starting position with a significant penalty. This behavior undermines the environment's intended reinforcement learning framework for penalizing risky actions.

Motivation
The current implementation of the Cliff Walking environment allows agents to escape cliff penalties by exploiting unintended transitions. This compromises the environment's ability to serve as a robust benchmark for policy iteration and value iteration algorithms. For instance:

The agent moves from state 38 to state 26 instead of returning to the starting state with a high penalty, reducing the effectiveness of learning optimal policies.
This behavior contradicts the intended logic where any action taken from cliff states should lead to significant penalties.

This proposal ensures alignment with the intended design of the environment and improves its utility for reinforcement learning experiments.
Pitch
To resolve this issue, modify the environment's transition logic such that any action performed from a cliff state resets the agent to the starting position (e.g., state 36) with the prescribed high penalty. This ensures:

Consistency in the environment's response to cliff state actions.
Enhanced reliability of the environment as a benchmark for policy optimization algorithms.
Intuitive alignment of the value functions and policies with expected outcomes.

After implementing the fix, the policy iteration and value iteration algorithms will correctly optimize policies that avoid the cliff, reinforcing the environment's educational and experimental value.
Results of the Proposed Fix
Below are heatmaps illustrating the impact of the proposed fix:
Original Setup:
In the current implementation, the agent can exploit unintended transitions, avoiding penalties for risky actions. The value function highlights this inconsistency, as shown below:

Proposed Fix:
After implementing the proposed fix, the environment penalizes risky actions appropriately. The value function reflects this change, as shown below:

Alternatives
No response
Additional context
No response
Checklist

[X] I have checked that there is no similar issue in the repo

Thanks for the detailed issue
Looking at the implementation, currently, the agent receives a reward of -1 for each timestep (that is non-cliff) and a reward of -100 if it moves into the cliffs.
Are you proposing that rather than just receiving a reward of -100, the agent's next state should be the initial state? Just want to confirm I understand
This would be an interesting alternative method for discouraging the agent from moving into the cliff, and I don't think it should significantly negatively impact the policy.
If we proceeded with this, we would add it as a parameter option that is disabled by default.

Thank you for your response and understanding of the issue.
To clarify, my proposal is not about the agent moving into the cliffs; that part is already implemented correctly. Instead, the suggestion focuses on the scenario where the agent starts its turn in a cliff position, regardless of how it got there. For example, in algorithms like Policy Iteration or Value Iteration, where the algorithm iterates through all possible states (as shown in Sutton's algorithm), the environment must correctly handle situations where the agent is already in a cliff state.

Currently, if the agent starts on the cliff, it can take an action without being reset, effectively "escaping" the cliff penalty. My proposal is that if the agent starts its turn already in a cliff position, any action it takes should immediately reset it to the initial state with the appropriate penalty. This ensures consistency in treating the cliff as a failure state, regardless of whether the agent moves into it or starts there.
I believe implementing this change would enhance the environment's behavior without affecting the overall policy learned by the agent.

Ok, thanks for clarifying, I don't think that is necessary as no agent should move onto the cliffs in the first place.
Therefore, what happens from the cliffs doesn't matter in my head.
Either we provide a large negative reward for moving onto it or terminate the agent for doing it
The solution seems to magically transport the agent to the initial state (rather than terminate)

I understand your perspective that agents ideally should never find themselves starting a turn already on a cliff. However, when we consider the environment not just as an interactive setting but also as a testbed for planning-based algorithms—like Policy Iteration or Value Iteration—the environment must handle all theoretically reachable states, including cliff states. Even if an optimal policy never deliberately steps onto a cliff, during the iterative computation of value functions, these states are examined and updated. If the environment’s logic is inconsistent at that point (for instance, allowing an agent to escape a cliff with minimal penalty when it “starts” there), it can distort the computed values and undermine the reliability of the final solution.
The proposed change ensures that the cliff states are treated uniformly, preserving the intended logic: encountering a cliff, under any circumstance, should trigger a reset and a significant penalty. This is in line with the spirit of the environment, where cliffs represent terminal failures rather than intermediate states from which the agent can simply “walk away.” While it may feel like a corner case that doesn’t affect an on-policy learner, it matters for off-policy evaluation, planning, and educational settings where the environment must clearly communicate its rules. One possible compromise is to make this stricter cliff-handling behavior an optional parameter, allowing users to choose the most appropriate logic for their application without sacrificing the environment’s consistency.
In essence, the proposal is less about what an on-policy agent “should” do, and more about ensuring that the environment’s dynamics are both consistent and conceptually aligned with its intended design, thereby strengthening its role as a reliable and educational reinforcement learning benchmark.

Planning algorithms should take into account terminal states,
there do not exist transitions from the hole states to new states, the programming behavior is simply undefined behavior

You're absolutely right that the agent shouldn't transition from a cliff (or hole) state since it's terminal—the episode ends there. This makes sense in real-time interactions, as the agent wouldn't continue after falling off a cliff.
From a planning perspective, however, algorithms like Value Iteration or Policy Iteration iterate conceptually over all states, including terminal ones, without simulating full episodes. In this context, "hole" states remain part of the state space and need clearly defined dynamics to avoid undefined behavior. Defining transitions explicitly—such as resetting the agent with a penalty or applying a deterministic rule—can make the environment more consistent and useful for learning.
Alternatively, cliff states could be entirely removed from the state space. In this approach, reaching a cliff would automatically reset the agent, bypassing "hole" states altogether. This simplifies the environment, ensures well-defined transitions, and aligns with real-world scenarios where falling off a cliff directly resets the process.

I'm going to close this for now as I don't think we can come to a solution that makes sense for the project


Last update 0e23dbb...5b0d0ef


Typescript

TS types and an example. Will update readme if all good.

A good start but needs some improvements:

role in Asssociation != resource type
not all current resource types are in the Resource type definition (e.g., integration is missing)
some ids are typed as string instead of uuid

A small remark: you can also just squash the commits into 1 commit unless each commit has a clear purpose.
I can do this when accepting the pull request as well, so no real problem.

As a next step, it would be great to add definitions for the different resource properties.
This would bring great value as now all properties need to be looked up in the docs.


CS 2.3.0 - For loop AST change

There's a change to for loop AST generation in CS 2.3.0:
https://github.com/jashkenas/coffeescript/pull/4893
This breaks the ScopeLinter, as node.body will now not necessarily contain locationData.
I suspect but am not certain as of yet that just adding a conditional prior the property analysis for loop in the visitFor() method will resolve the breakage. The tests pass and it would be backward compatible, but I need to do more comprehensive testing.
Just bringing this up in case others have the problem and to get the opinions of others at this point.
    visitFor: (node) =>
        # because comprehensions compile to the same AST as regular for blocks
        # we distinguish between the two by checking bounds: a comprehension's
        # body has the same location as the node itself, whereas for a regular
        # for, the body is contained within the for block
        comprehension = true
        if node.body.locationData?
            for prop in ["first_line", "first_column", "last_line", "last_column"]
                if node.locationData[prop] isnt node.body.locationData[prop]
                    comprehension = false
                    break

        if node.name?
            @visitAssignment(node.name, {comprehension})
        if node.index?
            @visitAssignment(node.index, {comprehension})
        node.eachChild(@visit)
        undefined

Thanks!


Create Templated Page from Query does not work without a link column

Steps To Reproduce

create a query categories.sql

SELECT
    category,
    sum(sales) as total_sales
from orders
group by category

run the command, choosing the column category as the identifier
run code

Environment

VSCode Extension version (Check in VSCode Marketplace): 1.3.39

Expected Behavior
a working datatable to create the links is created
---
title: Categories
sources:
   - categories: categories.sql
---

Click on an item to see more detail

<DataTable data={categories} showLinkCol=true link=category/>

Actual Behaviour
generated code
---
title: Categories
sources:
   - categories: categories.sql
---

Click on an item to see more detail

<DataTable data={categories} link=link/>

There is no link column in the query so this does not work as expected
Workarounds
include a link column in the query

Here's an example of that - where it sets up a chained query to produce the link on the user's behalf:
https://github.com/evidence-dev/evidence-vscode/assets/12602440/a84e5fcc-1ecf-4811-83a2-a46c423f6211


UI: long publishers make the window too wide

When a binary is blocked and the publisher string is very long, the publisher field causes the window to grow very wide, which looks a little silly.

Fixed by #116, which will be included in 2024.11


Add "content owner" field and export capability

As part of the M&M sprint, we determined that it would be useful for Wagtail to have a "content owner" field so that we can track which Bureau division owns content, for easier reporting and maintenance in the future (see https://github.local/CFPB/el-camino/issues/559). Right now this kind of process is difficult and entirely manual.
This PR adds a "Content Owner" field to all Wagtail pages. The field is not used in any way for rendering the page; it exists solely for internal tracking and maintenance purposes. To assist in that tracking, I've also added a column for it in the "Page Metadata" report, to make it easy to export and filter based on that information.

Additions

A comma-separated field labeled "Content Owners" on all Wagtail pages, to be used similarly to the Authors and Topic Tags fields.
A column in the "Page Metadata" report with the above field, so that the information can be exported for reporting use.

How to test this PR

./frontend.sh
localhost
Edit any Wagtail page and navigate to the "Configuration" tab; find the new "Content Owner" field.
Once data has been added to that field on any pages, navigate to Reports -> Page Metadata
Click "Download CSV"
In the resulting CSV, note the existence of the "Content Owner(s)" field and any entered data

Screenshots

Checklist

[ ] PR has an informative and human-readable title

PR titles are used to generate the change log in releases; good ones make that easier to scan.
Consider prefixing, e.g., "Mega Menu: fix layout bug", or "Docs: Update Docker installation instructions".

[ ] Changes are limited to a single goal (no scope creep)
[ ] Code follows the standards laid out in the CFPB development guidelines
[ ] Future todos are captured in comments and/or tickets
[ ] Project documentation has been updated, potentially one or more of:

This repo’s docs (edit the files in the /docs folder) – for basic, close-to-the-code docs on working with this repo
CFGOV/platform wiki on GHE – for internal CFPB developer guidance
CFPB/hubcap wiki on GHE – for internal CFPB design and content guidance

Front-end testing

Browser testing
Visually tested in the following supported browsers:

[ ] Firefox
[ ] Chrome
[ ] Safari
[ ] Edge 18 (the last Edge prior to it switching to Chromium)
[ ] Internet Explorer 11 and 8 (via emulation in 11's dev tools)
[ ] Safari on iOS
[ ] Chrome on Android

Accessibility

[ ] Keyboard friendly (navigable with tab, space, enter, arrow keys, etc.)
[ ] Screen reader friendly
[ ] Does not introduce new errors or warnings in WAVE

Other

[ ] Is useable without CSS
[ ] Is useable without JS
[ ] Does not introduce new lint warnings
[ ] Flexible from small to large screens

@schbetsy tagged you here for review since @chosak pointed out to me that the "author byline" work might have some functional overlap here; I don't think it really will but feel free to chime in with thoughts!

@chosak My latest commit attempts to replicate the code in Wagtail's recipes page for a custom tag model. It works properly up until a point: the new field doesn't seem to pull in autocomplete results from either of the other fields. However, right now if you try to add owner(s) to any given page and save or publish, you'll get an IntegrityError that looks something like this:

I've tried a few things but frankly am at a bit of a loss; I'm not familiar enough with the codebase to understand what to try next. Thoughts/suggestions?

@chosak This should be good to merge upon your final review!


Reformat PR template for reading as unformatted markdown

The PR editor opens in  "Write" mode, so developers don't see the text as Markdown formatted when writing the PR desc. Reformatted to reflect this.

Looks great


Sets of testing folders and render tests for components

This closes #17 . The testing suite is setup for unit testing the React components.

👍


Cannot set T key as keyboard press

Whenever you set the action editor to keyboard key, key status as press and try to change the key to T, it changes action type to text.

Issue fixed you can pull updated frmActionEditor.cs
Thank you for feedback.


can I get more details for RFConv2d? Thanks.

from rfconv import RFConv2d
self.conv = RFConv2d(in_channels, channelsradix, kernel_size, stride, padding, dilation,
groups=groupsradix, bias=bias, average_mode=rectify_avg, **kwargs)
What is rfconv?

See details in:
https://hangzhang.org/RectifiedConv/RectifiedConv.pdf
https://github.com/zhanghang1989/RFConv

See details in:
https://hangzhang.org/RectifiedConv/RectifiedConv.pdf
https://github.com/zhanghang1989/RFConv

when I used RFConv2d, it report Error "lib/enclib_cpu.so: failed to map segment from shared object". Could help me to deal with it?Thank you!

I don't have this issue on my machine.

I don't have this issue on my machine.

Thank you for your reply.


fixed profiler dependency on new gftl-v2

Fix profiler dependency on gftl-v2
Description

Related Issue

Motivation and Context

How Has This Been Tested?

Types of changes

[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[x] Trivial change (affects only documentation or cleanup)

Checklist:

[x] I have tested this change with a run of GEOSgcm (if non-trivial)
[x] I have added one of the required labels (0 diff, 0 diff trivial, 0 diff structural, non 0-diff)
[x] I have updated the CHANGELOG.md accordingly following the style of Keep a Changelog

This PR addresses issue #1334

Blocking for just a second so I can fix up the branch for release.

Actually, let me keep blocked as I run a GEOSgcm test.

Zero-diff and builds.

Add label DNA back. I want to understand what happens here

I guess I figure out what happened here. The include path can be inherited from dependence.  Since profiler depends on mapl.shared, it inherits its include path. Mapl.shared depends on pflogger which has all gFTL's paths.  In our GEOSgcm, we build and use pFlogger but in UFS, only pFlogger_stub is used.  That is why in UFS, v2 path is missing. This PR should work for UFS, but we may add fake dependence to pfloger_stub to make it really mimic pFlogger.

@weiyuan-jiang Well done!
And this speaks directly to why it is so important for us to list all the explicit dependencies of each layer.    Otherwise we get surprising results when unrelated layers are changed elsewhere in the model.

I guess I figure out what happened here. The include path can be inherited from dependence. Since profiler depends on mapl.shared, it inherits its include path. Mapl.shared depends on pflogger which has all gFTL's paths. In our GEOSgcm, we build and use pFlogger but in UFS, only pFlogger_stub is used. That is why in UFS, v2 path is missing. This PR should work for UFS, but we may add fake dependence to pfloger_stub to make it really mimic pFlogger.

Dang. Good job figuring this out. CMake is...fun this way!. The question for @tclune is: should @weiyuan-jiang add the fake dependence in pflogger_stub?

@weiyuan-jiang Okay. I talked with @tclune. I think what you should do is this. In both generic/CMakeLists.txt and in profiler/CMakeLists.txt, we should have:
GFTL::gftl-v1 GFTL::gftl-v2

The reason is that both are currently using both! You can see all the v2 uses:
❯ rg 'template.inc'
generic/VarConnVector.F90
8:#include "vector/template.inc"

generic/VarSpecVector.F90
8:#include "vector/template.inc"

profiler/MeterNodeStack.F90
9:#include "vector/template.inc"

but of course they use v1 in many more places!

@weiyuan-jiang Okay. I talked with @tclune. I think what you should do is this. In both generic/CMakeLists.txt and in profiler/CMakeLists.txt, we should have:
GFTL::gftl-v1 GFTL::gftl-v2

The reason is that both are currently using both! You can see all the v2 uses:
❯ rg 'template.inc'
generic/VarConnVector.F90
8:#include "vector/template.inc"

generic/VarSpecVector.F90
8:#include "vector/template.inc"

profiler/MeterNodeStack.F90
9:#include "vector/template.inc"

but of course they use v1 in many more places!

Changed

Thanks. I'll do a build-and-run test to be sure all is well.

Works for me. Approving.

GFTL::gftl and GFTL::gftl-v1 are the same thing.  So one should not specify them both.
Someday GFTL::gftl will be an alias for gftl-v2.    It sort of provides a future-safe way of upgrading, except that the Fortran files still need to change for it to help.    Probably a waste of effort on my part.


Live

Docs Build status updates of commit 9bb002b:
:white_check_mark: Validation status: passed
For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel


Getting "it's" as a keyword

Initial checklist

[X] I read the support docs
[X] I read the contributing guide
[X] I agree to follow the code of conduct
[X] I searched issues and couldn’t find anything (or linked relevant results below)

Affected packages and versions
retext-keyword
Link to runnable example
sqlite> select distinct(tag) from tags where tag LIKE 'it%';
it's
italian
item
items
itext
itoco
it’ll
it’s
it’s-leadership

Here are some urls that parse keyword as "it's" (I'm passing the html to deno-dom then to moz-readability to get article.content and article.title
it's|https://www.bbc.co.uk/news/science-environment-59268393
it's|https://www.cbsnews.com/news/china-grows-as-campaign-theme-during-coronavirus-pandemic/
it's|https://www.cbsnews.com/news/classic-cars-electric-vehicles-london-mechanic/
it's|https://www.cnbc.com/2021/11/18/inside-cornings-new-vaccine-vial-factory-in-north-carolina.html
it's|https://www.cnn.com/travel/article/beautiful-towns-europe/index.html
it's|https://www.cnn.com/travel/article/dead-sea-shrinks-as-jordan-turns-tide-on-tourism/index.html
it's|https://www.cnn.com/travel/article/uk-tourism-decline-restrictions-cmd/index.html
it's|https://www.cracked.com/article_31747_canadian-children-marched-to-protest-the-rising-price-of-candy.html
it's|https://www.euronews.com/green/2021/11/18/climate-misinformation-is-getting-more-sophisticated-and-experts-say-cop26-progress-could-
it's|https://www.firstshowing.net/2021/watch-remember-a-visual-poem-film-about-interconnectedness/
it's|https://www.freep.com/story/news/local/michigan/2021/11/18/ann-arbor-ordinance-tampons-pads-all-public-bathrooms/8652533002/
it's|https://www.globalcryptopress.com/2021/10/bitcoin-network-holds-over-1-trillion.html
it's|https://www.inc.com/anna-meyer/jennifer-fleiss-rent-the-runway-jetblack-volition-brands.html
it's|https://www.inc.com/joe-sanok/psychologist-joe-sanok-reveals-the-best-parts-of-his-new-book-thursday-is-the-new-friday.html
it's|https://www.inc.com/suzanne-lucas/osha-wont-enforce-covid-rules-pending-court-prepare-anyway.html
it's|https://www.neatorama.com/2021/11/18/Every-Picture-Tells-a-Story-This-One-is-a-Romantic-Comedy/
it's|https://www.npr.org/2021/11/16/1056263648/pfizer-says-it-will-share-the-rights-to-its-covid-19-pill
it's|https://www.npr.org/2021/11/17/1056646740/la-palma-volcano-brings-both-destruction-and-renewal-to-the-island
it's|https://www.rt.com/sport/540633-djokovic-covid-vaccine-status/
it's|https://www.slashfilm.com/664323/jennifer-coolidge-will-star-in-ryan-murphys-the-watcher-tv-series-for-netflix/
it's|https://www.wired.com/gallery/25-amazing-holiday-gift-ideas-under-25-2021/
it's|https://www.wired.com/story/best-black-friday-outdoors-deals-rei-2021/
it's|https://www.wired.com/story/best-buy-early-black-friday-deals-2021-2/
it's|https://www.wired.com/story/early-black-friday-deals-2021/
it's|https://wyrk.com/what-would-you-tear-down-in-buffalo-and-why/

Steps to reproduce
    const doc = new DOMParser().parseFromString(body, 'text/html');
    article = new Readability(doc).parse();

    const nodes = await retext()
      .use(retextPos)
      .use(retextKeywords)
      .process(`${article.title} - ${article.textContent}`);

Expected behavior
seems like "it's" is a stop word
Actual behavior
Getting "it's" as a keyword
Runtime
Deno v1
Package manager
Other (please specify in steps to reproduce)
OS
Linux
Build and bundle tools
import retextKeywords from 'https://cdn.skypack.dev/retext-keywords@7.1.0?dts';

I don’t have your setup of sqlite or deno or whatever you’re doing. Could you make the issue small and reproducible?

Please provide a small reproduction to reopen this. Closing as it can’t be produced.


Roots is moving towards framework-agnosticism

As per this issue. Just want to make you aware - after they implement this, we may want to consider transitioning Gromf towards a Foundation-specific plugin; I'm sure we can take a lot of the work we did and just bundle the Foundation stuff.. I believe they've already pulled out some of Bootstrap styling in the markup.

Working on a Sage 8.x version of Gromf now

@schikulski Exciting!


added test for FormattableObject

Moq was removed in place for a concrete Mock class, and also the pattern not is for
FluentAssertions, please update.
Also the person class does not contain a Website Property anymore for 1 and don't add advertisment in your tests, as even i don't do it


about how to generate multi_view video ?

hi thanks for your reply,  i had read your sample code , but i cannot find out how to generate multi_view video, could you tell me how to organize my data or change code in sample.py.   Looking forward to your reply ^_^

Unfortunately, multi-view generation is not a feature of Vista. We focus on front-view generation to leverage diverse data sources.

You are welcome :)


JAVA-2257 Handle autoIndexId without capped option enabled

It's seems that autoIndexId can't be activated without enabling capped option when creating a collection.
Since it is possible using the mongo shell, why blocking this action on the java driver.
Thanks,

Thanks for submitting this pull request.
Please run ./gradlew check on your branch, as it appears from Travis that the patch is violating our Groovy test coding standards.
Also, as per our contributing guidelines, please also open an issue in our JIRA project so that we have an issue to link this pull request to.
Also, please note in our documentation that autoIndexId has been deprecated in the MongoDB server as of the 3.2 release and is scheduled for removal in 3.4.
Thanks,
Jeff

The issue has been created (since even if it will be deprecated, it's still a bug).
Talking about my use case, I'm looking for a way to "archive/restore" a read-only big data collection on the fly when it hasn't been used for a while (because of indexes size). I was thinking about just removing indexes, but since autoIndex=false will be deprecated (I can't get rid of _id index size), do you suggest using mongo dump/restore instead? Do you have some plan on doing such a feature?
Thanks,
Andy.

I suggest that you ask your archiving question in the mongodb-users Google group, as this isn't the right forum for that sort of discussion.
I have a few suggestions about the tests.  After handling those, please
squash the commits and prefix the single commit message with "JAVA-2257: ", and we'll get this merged.
Thanks,
Jeff

Merged via command line.  Thanks again!


Login layout looks wrong

Checkbox and button -> no gap
Forgot password -> another place?
checkbox-text not valigned with checkbox

Added a gap between forgot password and checkbox-text
Also aligned checkbox-text to checkbox


Quickswap v3 mai usdt

Adds:

USDT revenue
MAI revenue
QUICK revenue
value in protocolMetrics
Investment position tracking gross / net apy

@abtheo current Quick value is always 0

@abtheo current Quick value is always 0

ah thanks good catch, resyncing now


fix to VideoQuality.determineClosestSupportedResolution

I was testing the library selecting some less common resolutions like 480 x 360 px (like the examples in the supported media formats) and a resolution of 480 x 800 px was being selected. This version respects the definition of "closest supported resolution" as it minimizes the l2 norm in both dimensions.

Just noticed #50 addresses the same issue.
Also in the code I've submitted there's no real need to compute the sqrt (line 116).


karma-webpack unexpectedly installs<EMAIL_ADDRESS>starting today

I'm submitting a bug report
Webpack version:
1.12.3
Webpack Karma version:
1.7.0
Please tell us about your environment:
OSX 10.x / Linux
Current behavior:
Starting today, on install of karma-webpack, npm resolved its webpack dependency at version 2.1.0-beta.25. This behavior started this afternoon, builds that occurred in the morning installed version 1.13.2. We have made no changes to our package.json, or shrinkwrap file that would have caused this.
Expected/desired behavior:
I would expect that karma-webpack would continue to install<EMAIL_ADDRESS>More info
It appears that webpack published a new webpack version roughly 2 hours ago, which fits within the timeline of our working builds / nonworking builds.

Updating to NPM 2.15.6 fixes this behavior. Closing issue.


Possible to have different colors for public/private fields?

Like title says, is it possible to have semantic offering different colors for private and public fields?

a big +1, this would be a great feature, especially with the recent debate about code stye ane using _underscore for private fields (or not).


Remove aframe-react dependency

aframe-react creates a lot of memory garbage causing the website to lag.
Remove and use "A-Frame and aframe-state-component with static templating" to display volumes

Issue moved to react-volume-viewer library


Warn when partial enumeration values are used

Here's a little known feature that could come back to bite someone later with a broken script:
gsv blah -ea ig
I'm not sure in which version of PowerShell this was added, but you can now use partial enumeration values and as long as that partial value leads to an unambiguous match, it will be accepted.
This may result in errors in scripts that appear to be working correctly if a new emumeration value is added with the same leading characters as those that are in use within a script.  It's the same issue/risk with using partial parameter names in scripts.  Shorthand should be for ad-hoc use only, and PSScriptAnalyzer should have a rule that warns whenever an enumeration value is used in a script in shorthand (such as in the command above).

I suppose I was making an assumption that I should verify: PSScriptAnalyzer already warns when you use parameter aliases or parameter shorthand, does it not?  If not, it definitely should, at least for the latter.

At this point, PSScriptAnalyzer doesn't have a rule that warns if you use parameter aliases or parameter shorthand. So, we now are two taking about two new rules -

Warn when partial enumeration values are used
Warn when parameter aliases or parameter shorthand is used


Upgrade Kitematic (Beta).app to v0.8.3

Thank you for the contribution. It was merged directly as bb092180f28d6cfbb42b463d462bbd33ccc541a6 to keep commit history cleaner. Your contribution is still credited to you.


ESLNote: scroll into view fix

Fixed scrolling esl-note into the viewport when activated

:tada: This PR is included in version 3.13.0-beta.4 :tada:
The release is available on:

npm package (@beta dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Move tests to new dir

Does this organize make sense to you?
I had idea that we have a lots of files in tests dir. We could try organize them better way....

Maybe it would be better to separate integration tests?


Add empty state feedback and animation to scanning process - Updates #4

Updates #4

Added a loading state in the App component and passed it to the table components as prop (loadingRows). In the table component the following have been added to accommodate feedback for the scanning process.

Added text feedback and loading indicator to the table component when rows are loading.

Added initial state placeholder with an icon and text when no scan has been initialized. (if we don't have a response/rows).

Added no results found feedback with an icon and text when the scan results are empty. (if we don't have a response/rows).

Updates #3

I also updated the README with development instructions : - )

@Le-Roi777 Good stuff! Thanks for the PR. I'll review it.