TS2615: Type of property 'siteAreas' circularly references itself

Types are cyclically calling each other.
E.g:
Transaction-> site?: Site-> siteAreas?: SiteArea[]-> site: Site;
TS2615: Type of property 'site' circularly references itself in mapped type '{ id: ["id"]; name: ["name"]; address: ["address", "coordinates", number] | ["address", "address1"] | ["address", "address2"] | ["address", "postalCode"] | ["address", "city"] | [...] | [...] | [...]; ... 33 more ...; canReadChargingStations: [...]; }'.  @ ./src/async-task/tasks/BillTransactionAsyncTask.ts 13:53-104  @ ./src/async-task/AsyncTaskManager.ts 7:59-102  @ ./src/start.ts 6:51-91
TS2615: Type of property 'siteArea' circularly references itself in mapped type '{ id: ["id"]; createdBy: ["createdBy"]; createdOn: ["createdOn"]; lastChangedBy: ["lastChangedBy"]; lastChangedOn: ["lastChangedOn"]; coordinates: ["coordinates", number]; issuer: ["issuer"]; ... 56 more ...; oicpData: [...] | ... 59 more ... | [...]; }'.  @ ./src/async-task/tasks/BillTransactionAsyncTask.ts 13:53-104  @ ./src/async-task/AsyncTaskManager.ts 7:59-102  @ ./src/start.ts 6:51-91

I ran into the same. I believe it is related to changes in mongodb. I can detail the exact version that causes the problem and maybe fix the code. If ok, please assign this issue to me.

When do you have this error?
Could you also provide Node/Npm/MongoDB version?

yes, will do but can only do this evening

One type of change that allowed to get the compile through is by the changing the type Transaction in below line to any . Such change is needed in multiple files. I don't know TypeScript good enough to estimate if this is a good fix though.

I did  not manage to test, but pretty sure it is related to mongodb version v4.3.0. This introduced Type inference for nested documents: "... support for key auto-completion and type hinting on nested documents!" . See the documented limitation here:

More details in the release notes here, scroll to version v4.3.0
https://github.com/mongodb/node-mongodb-native/releases

Have a look at this commit to find where the error all occurs: https://github.com/guido4096/ev-server/commit/9cbd2deeebe902e221c762f086f4125cec6c6730

I can share more information on the subject.
I'm working on v2.6.2 tag.

{
'ev-server': '2.6.2',
npm: '8.3.1',
node: '16.14.0',
v8: '<IP_ADDRESS>-node.20',
uv: '1.43.0',
zlib: '1.2.11',
brotli: '1.0.9',
ares: '1.18.1',
modules: '93',
nghttp2: '1.45.1',
napi: '8',
llhttp: '6.0.4',
openssl: '1.1.1m+quic',
cldr: '40.0',
icu: '70.1',
tz: '2021a3',
unicode: '14.0',
ngtcp2: '0.1.0-DEV',
nghttp3: '0.1.0-DEV'
}

I have  "mongodb": "^4.2.2", on package.json file. And I am connecting to mongodb atlas .I would like to point out that I am not working with a local mongodb.
I used any instead of SiteArea and Site on src/types/ChargingStation.ts and src/types/SiteArea.ts to solve the problem and continue using home-server.
Since I don't think this is a good enough solution, I felt the need to open an issue, thinking that you are more familiar with home-server architecture. If you have a diagram that will help me develop a better solution, if you can share it, I would like to support it.

The ^ in the line "mongodb": "^4.2.2" says that version 4.2.2 or higher is allowed. Please run npm list mongodb in the ev-server directory to find the actual version that is used. This is likely 4.3.0 or higher.

npm install<EMAIL_ADDRESS>and then a
npm run build:prod
=> npm list mongodb

Use MongoDB 4.4

My version:
{
  'ev-dashboard': '2.6.3',
  npm: '8.1.0',
  node: '16.13.0',
  v8: '<IP_ADDRESS>-node.13',
  uv: '1.42.0',
  zlib: '1.2.11',
  brotli: '1.0.9',
  ares: '1.17.2',
  modules: '93',
  nghttp2: '1.45.1',
  napi: '8',
  llhttp: '6.0.4',
  openssl: '1.1.1l+quic',
  cldr: '39.0',
  icu: '69.1',
  tz: '2021a',
  unicode: '13.0',
  ngtcp2: '0.1.0-DEV',
  nghttp3: '0.1.0-DEV'
}

mongodb 4.4.13 does not exit. Well, that is not 100% accurate. MongoDB as the actual database server does exist in version 4.4.13:
https://www.mongodb.com/docs/upcoming/release-notes/4.4/
But this error is not about the database itself. It is about the MongoDB Node.js package which contains the javascript/typescript  client interface. https://github.com/mongodb/node-mongodb-native/releases
When using version 4.3.0 or higher, things break.

I have that in my console for the server when I pull the MongoDB image:

For the MongoDB driver, I haven't tested the V4.3 but we can fix it and use 4.2.x only in the package.json.

Limiting the MongdoDB driver to 4.2.2 will fix it short term. But it blocks taking updates of this driver, which might become a problem in the future.
P.S. In my own setup I also have MongoDB server 4.4.x; and that also works well combined with the driver version 4.2.2

Yes I agree, but for the time being this is not a prio for the team.

I just tested it and reproduced the issue with the driver 4.4.1 and I maybe found a simple solution to implement.
I'm working on it and let you know.

I created a branch for migrating to MDB driver 4.4: migration-mongodb-driver-4.4
We still have Unit Tests issues with this error:
MongoServerError: Unsupported conversion from object to string in $convert with no onError value

this is sufficient for my use-case.Thanks for the solution.
3/28/2022, 3:02:23 PM - Rest, Json, Ocpi, Oicp, OData server has been started successfuly in 25.473 secs


fix(ui): render certification on profile page in ul

Checklist:

[x] I have read and followed the contribution guidelines.
[x] I have read and followed the how to open a pull request guide.
[x] My pull request targets the main branch of freeCodeCamp.
[x] I have tested these changes either locally on my machine, or GitPod.

Closes #55574

resolved all the review comments

Do we really need another CSS file just for the UL styles?
I would prefer a couple of tailwind classes (list-none px-0 m-0) on the two UL elements.
Also, I would suggest we replace the <br> on line 74 with a Spacer component with size medium.

We already have three patterns, inline CSS, CSS in files, and tailwind.
I don't really see why changing to tailwind whenever possible shouldn't be the choice. The more CSS we add to files, the harder it becomes switching to tailwind later.
As an aside, if we do want it in files, why are we not using CSS Modules for the component styles?

@huyenltnguyen @lasjorg do we have consensus on the approach for css ?


Link to sphinx_symbiflow_theme repo?

In the bottom right hand corner of the docs is a link to a non-existent "sphinx_symbiflow_theme" repo.

I assume this comes from the theme at https://github.com/SymbiFlow/sphinx_materialdesign_theme ?

I renamed the https://github.com/SymbiFlow/sphinx_materialdesign_theme repo to https://github.com/SymbiFlow/sphinx_symbiflow_theme

@mithro Yea it's meant to link to the theme repository

Well, since I renamed the repo I guess it's all good now.


Consider using xml parser instead of json for parsing plist

Flutter tools rely on plutil to parse plist into json. I assume we do this because dart:core comes with json decoding support.  Unfortunately, certain internal apps are picking up plist configuration that contains <data> tags which are not supported for json conversion.
I tried to extract certain key values but plutil isn't happy with these tags even if their specific conversion is not requested.
Sample plist:
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
        <key>CFBundleDisplayName</key>
        <string>Test (Dev)</string>
        <key>CFBundleLocalizations</key>
        <array>
                <data>
                828fnna
                </data>
                <string>ar</string>
                <string>bg</string>
        </array>
</dict>
</plist>

[14:34] ~$ /usr/bin/plutil -convert json -o - ~/test.plist
/Users/mehmetf/test.plist: invalid object in plist for destination format

package:xml is not a heavy dependency so if we were willing to include it, we could sidestep this problem.

@jonahwilliams in case he has seen this in the wild. I am not sure how unusual it is for plists to not be parseable to json.

We already depend on package:xml for parsing android manifests, so the additional dependency isn't really a concern

@jmagman for thoughts on using xml parsing.

The suggestion is to use plutil -convert xml and parse that, right?  That makes sense to me.

JSON also doesn't have an equivalent for <date>.

I think plist is usually XML itself but relying on -convert xml is probably more robust.

I think plist is usually XML itself but relying on -convert xml is probably more robust.

It's usually a binary on macOS, though the app developer can configure it.  Most first party apps on macOS are binary, for example.

I think plist is usually XML itself but relying on -convert xml is probably more robust.

It's usually a binary on macOS, though the app developer can configure it. Most first party apps on macOS are binary, for example.

"usually" and "most" were exaggerations, I see Xcode, Developer, and some utility apps are binary, most of the rest are XML.

I had it backwards, PLIST_FILE_OUTPUT_FORMAT defaults to binary on iOS, and on macOS is "same as input" which usually means XML.

The Flutter built iOS app uses the OS default and is binary.
$ file build/ios/Release-iphoneos/Runner.app/Info.plist
build/ios/Release-iphoneos/Runner.app/Info.plist: Apple binary property list


Unwanted page break

Hi @motla
I don't want this page break to happen for my sections.
I am unable to prevent this behavior via CSS alone, as it seems that vue-document-editor does not seem to take into consideration page-break-before, page-break-after or page-break-inside. What do I need to do?
Ps.: My sections are in <section> elements.

Hi @guilhermeagirardi,
It is not implemented yet and not trivial to implement. For example we have to handle the case when the section height is higher than the page height. I can't look at it right now, but the starting point would be to detect the <section> element in this line to avoid splitting it:
https://github.com/motla/vue-document-editor/blob/8eaa28b98e1d01274c35415e8e283c4b1975baa3/src/DocumentEditor/imports/page-transition-mgmt.js#L53

Hi @motla !
Thank you for the feedback and the suggestion.
What I did was add a callback at the end of the conditional test of that function.
else if (!sub_child.childNodes.length || sub_child.tagName.match(/h\d/i) || do_not_break(sub_child)) {

<vue-document-editor
    ref="editor"
    v-model:content="content"
    :do_not_break="(sub_child) => sub_child.tagName.match(/section/i)"
/>

This was enough for me at the time to define different breakage prevention situations.

Well done! Great implementation 👍
I may add it to the next release but I'm afraid of edge cases, it needs some testing.

Hi @guilhermeagirardi
For your information I just released v2.3.0 (Vue3) and v1.5.0 (Vue2) which contains your implementation. I have set you as co-author.

Hi @motla!
It was no big deal. I'm honored to know that. Thankss! 😁


allowEmptyOption does not treat empty options as normal options

According to the documentation allowEmptyOption:true should enable empty value options being treated as normal options. However, it seems they are still not selectable.
This demo is taken straight out of the examples folder:

    Beast:
    <select id="select-beast-empty" class="demo-default" data-placeholder="Select a person...">
        <option value="">None</option>
        <option value="4">Thomas Edison</option>
        <option value="1">Nikola</option>
        <option value="3">Nikola Tesla</option>
        <option value="5">Arnold Schwarzenegger</option>
    </select>

Here none is not actually a clickable option. It disappears once the dropdown is activated, and thus seems more like a placeholder? Is this the wanted behaviour or did I miss something here?

I am having the same issue here, after initialise with allowEmptyOption I was expecting either one of the option below to be selectable:
<select>
  <option value>None</option>
  <option value="">None</option>
</select>

+1

+1

+1 too, this does not seem to work.
As a workaround, we do not use the allowEmptyOption option, and use a select option with a special value <option value="__blank__">None</option>, listen to the change event on the field and reset its value if the value is "__blank__"
Ex :
<select data-selectize>
  <option value="">Select a value ...</option>
  <option value="__blank__">None</option>
  <option value="1">Actual value</option>
</select>

Then initialize selectize and handle the __blank__ value manually :
$field = $('[data-selectize]').selectize()

$field.on('change', function() {
  if($field.val() === '__blank__') { $field.val(''); }
});

+1

+1

+1

This looks like an omission in the logic added in c8f2944a0a1d13db872397623544569379f16d7b to implement allowEmptyOption.
Empty options are parsed from the original <select> tag, but then lost during the call to Selectize.registerOption().
Line 1187 of src/selectize.js should be changed:
-		if (!key || this.options.hasOwnProperty(key)) return false;
+		if (typeof key === 'undefined' || key === null || this.options.hasOwnProperty(key)) return false;

Hopefully I'll find the time soon to set up a pull request with this change.
You can monkeypatch this without modifying the original source by running this code after loading selectize.js:
	var hash_key = function(value) {
		if (typeof value === 'undefined' || value === null) return null;
		if (typeof value === 'boolean') return value ? '1' : '0';
		return value + '';
	};
    $.extend(Selectize.prototype, {
		registerOption: function(data) {
			var key = hash_key(data[this.settings.valueField]);
            // Line 1187 of src/selectize.js should be changed
			// if (!key || this.options.hasOwnProperty(key)) return false;
			if (typeof key === 'undefined' || key === null || this.options.hasOwnProperty(key)) return false;
			data.$order = data.$order || ++this.order;
			this.options[key] = data;
			return key;
		}
    });

If the text of your option is also blank, you may need to modify your CSS or rendering function to ensure that the resulting data-selectable div does not collapse down to an unusable size. I overwrote the default rendering functions as shown below:
    var originalSetupTemplates = Selectize.prototype.setupTemplates;
    $.extend(Selectize.prototype, {
		setupTemplates: function(data) {
    		var self = this;
    		var field_label = self.settings.labelField;
    		var field_optgroup = self.settings.optgroupLabelField;

    		var templates = {
    			'option': function(data, escape) {
    				return '
' + ( $.trim(data[field_label]).length ? escape(data[field_label]) : ' ' ) + '
';
    			},
    			'item': function(data, escape) {
    				return '
' + ( $.trim(data[field_label]).length ? escape(data[field_label]) : ' ' ) + '
';
    			}
    		};
    		self.settings.render = $.extend({}, templates, self.settings.render);
			originalSetupTemplates.apply(this, arguments);
		}
    });

I'm not sure whether there's a more general-purpose way of handling this aspect of the issue.

+1

It's also ignored by the API AFAICT so passing in options with a blank string with allowEmptyOption set to true just discards it. We settled for 'none' as the value but would prefer an empty string (or null) as it's cleaner.

Tentative fix in a12d99f; please test on master


404 not found: browser client (0.7.0)

Description
In-browser query visualiser is returning 404 not found
Steps to reproduce the issue:
brew upgrade cayley

Followed the guide here:
https://github.com/cayleygraph/cayley/blob/master/docs/Quickstart-As-Application.md#quick-preview
I1228 20:03:34.666503   80944 cayley.go:63] Cayley version: 0.7.0 (6f8446e4171ebc84955dd0ff91927510ba1aee16)
I1228 20:03:34.667026   80944 database.go:180] using backend "memstore"
I1228 20:03:34.701608   80944 http.go:51] loadede
I1228 20:03:34.701808   80944 http.go:66] listening on <IP_ADDRESS>:64210, web interface at http://<IP_ADDRESS>:64210

Received results:

Environment details:
Backend database: 0.7.0

Figured it out, need to supply --assets option
cayley http --assets=/usr/local/share/cayley/assets

BTW is it not possible to symlink assets relative to binary so it doesn't need that extra option?

@gauravtiwari Yes, it expects templates, static and docs to be in a local dir.
I think it would be better if we add ./assets and /usr/local/share/cayley/assets to a list of checked paths as well. Reopening.

Will make a PR 👍

@dennwc At the moment if I run cayley like this i.e. not from same directory:
# using download binary from github
# assets inside ./bin/cayley
./bin/cayley

it throws 404. Does it look for assets relative to process root? If I move everything inside root directory and then run cayley like so:
# using download binary from github
# assets next to it
./cayley

it seems to pickup assets fine.
Also, I was wondering may be we add default lookups for config file as well? i.e. ./cayley.yml and ./cayley.json and  ./config/cayley.yml and ./config/cayley.json (something like this?)


Query errors from Grafana using Trickster 1.0.9-beta

We've recently upgrade trickster from 0.1.10 to 1.0.9-beta and we are experienced some errors while loading Grafana dashboards. Errors are intermittent, sometimes it works perfect.
Our setup is built on k8s:

prometheus Statefulset with 1 replica and a cloud storage volume + Service

trickster Statefulset with 5 replicas each with a cloud storage volume using BoltDB + Service

Ingress exposing trickster k8s Service as a Grafana Datasource

prometheus version 2.10.0

trickster version 1.0.9-beta

trickster /etc/trickster/trickster.conf configMap

    [main]
    [proxy_server]
        listen_port = 9092 # To avoid collision with prometheus port 9090. The port 9092 is unallocated by the community to avoid collisions with kafka but we're not going to have this problem inside our replication controller.

    [cache]
        [caches.default]
                # Options are 'boltdb, 'filesystem', 'memory', and 'redis'
                cache_type = 'bbolt'

                # timeseries_ttl_secs defines the relative expiration of cached timeseries. default is 6 hours (21600 seconds)
                timeseries_ttl_secs = 21600

                    # Configuration options when using a BoltDb Cache
                    [cache.bbolt]

                    # filename defines the file where the Trickster cache will be maintained
                    # default is 'trickster.db'
                    filename = '/tmp/trickster/trickster.db'
                    # filename = 'trickster.db'

                    # bucket defines the name of the BotlDb bucket (similar to a namespace) under which our key value store lives
                    # default is 'trickster'
                    # bucket = 'trickster'
                [caches.default.index]

                # reap_interval_secs defines how long the Cache Index reaper sleeps between reap cycles. Default is 3 (3s)
                reap_interval_secs = 3

                # flush_interval_secs sets how often the Cache Index saves its metadata to the cache from application memory. Default is 5 (5s)
                flush_interval_secs = 5

                # max_size_bytes indicates how large the cache can grow in bytes before the Index evicts least-recently-accessed items. default is 512MB
                max_size_bytes = 536870912

                # max_size_backoff_bytes indicates how far below max_size_bytes the cache size must be to complete a byte-size-based eviction exercise. default is 16MB
                max_size_backoff_bytes = 16777216

                # max_size_objects indicates how large the cache can grow in objects before the Index evicts least-recently-accessed items. default is 0 (infinite)
                max_size_objects = 0

                # max_size_backoff_objects indicates how far under max_size_objects the cache size must be to complete object-size-based eviction exercise. default is 100
                max_size_backoff_objects = 100

    # Configuration options for mapping Origin(s)
    [origins]
        [origins.default]
            cache_name = 'default'
            host = 'prometheus-server.prometheus-runtime.svc:9090'
            api_path = '/api/v1'
            ignore_no_cache_header = false
            # 30 days is the max age of specific datapoints in the cache.
            max_value_age_secs = 2592000
            # timeseries_eviction_method selects the metholodogy used to determine which timestamps are removed once
            # the timeseries_retention_factor limit is reached. options are 'oldest' and 'lru'. Default is 'oldest'
            timeseries_eviction_method = 'lru'

    [metrics]
        listen_port = 8082

    [logging]

        # Possible values are 'debug', 'info', 'warn', 'error'
        log_level = 'debug'

I attached trickster debug level logs but I can't see any errors:
trickster_1.0.9-beta.log
It seems like those requests are timing out from client perspective because trickster cannot handled properly. ingress-nginx logs with requests who end up in trickster:
[27/Aug/2019:14:47:02 +0000] "GET /api/v1/query_range?end=2019-08-27T14%3A46%3A32.362558337Z&query=nomad_allocation_memory_rss_bytes%7Bexported_job%3D%22corporate%22%2C+environment%3D%22production%22%7D&start=2019-08-27T14%3A41%3A32.362558337Z&step=15.000 HTTP/1.1" 499 0 "-" "Go-http-client/1.1" 348 29.977 [prometheus-runtime-trickster-9092] <IP_ADDRESS>:9092 0 29.978 - e083e992b05fe983516842c43e94d132 trickster-grafana-prometheus-runtime.otters.xyz
[27/Aug/2019:14:47:02 +0000] "GET /api/v1/query_range?end=2019-08-27T14%3A46%3A32.363149021Z&query=nomad_allocation_memory_rss_bytes%7Bexported_job%3D%22enterprise%22%2C+environment%3D%22production%22%7D&start=2019-08-27T14%3A41%3A32.363149021Z&step=15.000 HTTP/1.1" 499 0 "-" "Go-http-client/1.1" 349 29.995 [prometheus-runtime-trickster-9092] <IP_ADDRESS>:9092 0 29.995 - 5a9582b2459d6f8bdd41c12141b14754 trickster-grafana-prometheus-runtime.otters.xyz
[27/Aug/2019:14:47:02 +0000] "GET /api/v1/query_range?end=2019-08-27T14%3A46%3A32.415138983Z&query=nomad_allocation_memory_rss_bytes%7Bexported_job%3D%22corporate%22%2C+environment%3D%22production%22%7D&start=2019-08-27T14%3A41%3A32.415138983Z&step=15.000 HTTP/1.1" 499 0 "-" "Go-http-client/1.1" 348 29.982 [prometheus-runtime-trickster-9092] <IP_ADDRESS>:9092 0 29.982 - 60fb84b62a890778ec573ea876f75411 trickster-grafana-prometheus-runtime.otters.xyz

trickster_proxy_failed_connections_total metric keep it at 0 value all the time.
Could someone give some light about what's happening?
Thanks in advance

trickster_proxy_failed_connections_total is a red herring, that means that no connection failed to be created, not that requests are not failing.
In fact the interesting part is that we keep getting more and more active connections, that is: things are not timing out somewhere, thus requests lock forever.
What I find concerning is that we did not see a single error reported in the logs.
(disclaimer: I'm involved in this testing)

@vitovitolo I noticed you are using bbolt (awesome!). Investigating this, I found a few race conditions in both bbolt and memory cache types that can deadlock the mutex on certain URLs, causing them to hang and time out until trickster is bounced. I have submitted patches (PRs #274 and #277). This could possibly be the root cause for your issue, and possibly not. But if you don't identify a separate root cause before we release the next beta, hopefully you can confirm if this is resolved in the next beta release. Thanks to you and @pcarranza for trying the beta, contributing back to the project with issues and patches. We really appreciate it!

Closing for now, as mentioned above we have made patches that hopefully (uncertain without more info from the reporter) correct this issue. As of now, we cannot reproduce following the mentioned fixes. If the GA release of Trickster 1.0 still exhibits this problem, please re-open the issue and we'll take another look

@jranson sorry for the late response.
We did not update until yesterday because different reasons. Right now we're running trickster 1.12 with BBolt as main cache backend for one of our main production prometheus servers. Seems the bug is fixed. I'll let you know otherwise.
Thanks!


Find Units from Unit Schema

This PR is is combining two older branches to deliver the functionality that allows the frontend to resolve Units obtained from an iModel in the backend.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.0 out of 2 committers have signed the CLA.:x: IvanJK97:x: mergify[bot]You have signed the CLA already but the status is still pending? Let us recheck it.

@christophermlawson  - I am see a build error - looks like a dependency issue
--[ FAILURE: @itwin/ecschema-metadata ]-------------[ 1 minute 28.1 seconds ]--

src/test/Metadata/KindOfQuantity.test.ts(14,34): error TS2307: Cannot find module '@bentley/imodeljs-quantity' or its corresponding type declarations.
src/UnitProvider/SchemaUnitProvider.ts(5,45): error TS2307: Cannot find module '@bentley/bentleyjs-core' or its corresponding type declarations.


/dev/spidev0.0 does not exist

Traceback (most recent call last):
  File "rgb_display_minipitfttest.py", line 14, in <module>
    board.SPI(),
  File "/usr/local/lib/python3.7/dist-packages/board.py", line 186, in SPI
    return busio.SPI(SCLK, MOSI, MISO)
  File "/usr/local/lib/python3.7/dist-packages/busio.py", line 186, in __init__
    self._spi = _SPI(portId)
  File "/usr/local/lib/python3.7/dist-packages/adafruit_blinka/microcontroller/generic_linux/spi.py", line 22, in __init__
    self._spi = spi.SPI(device=(portid, 0))
  File "/usr/local/lib/python3.7/dist-packages/Adafruit_PureIO/spi.py", line 165, in __init__
    raise IOError("{} does not exist".format(device))
OSError: /dev/spidev0.0 does not exist

running rgb_display_minipitfttest.py after installing adafruit-circuitpython-rgb-display, spidev, ttf-dejavu, python3-numpy
please help

Make sure you've enabled SPI:
https://learn.adafruit.com/circuitpython-on-raspberrypi-linux/installing-circuitpython-on-raspberry-pi#enable-i2c-and-spi-2993390-7

Thank you Nelson
can you suggest if I'm missing something else, looking auth the picture

thanks in advance,

Looks like it's working in terms of hardware. Is your concern now the glitchy background?

Looks like you're running a 240x135 demo on a 240x240 display.

The problem is, even if I send 240x240 into constructor, the image comes as 240x135. Do I use right st7789.ST7789 constructor?
# Create the ST7789 display:
disp = st7789.ST7789(
    spi,
    cs=cs_pin,
    dc=dc_pin,
    rst=reset_pin,
    baudrate=BAUDRATE,
    width=240,
    height=240,
    x_offset=0, #53
    y_offset=10, #40
)

try tweaking the y offset!

see here:
https://learn.adafruit.com/adafruit-mini-pitft-135x240-color-tft-add-on-for-raspberry-pi/python-stats#modifications-for-the-1-dot-3-display-3066993-6

cool. y_offset=80 works fine.
thanks for your support!


Recovery Phrase Password

Description
During initial setup, after generating the recovery phrase, if you click cancel on the recovery phrase password box you are allowed to continue. Once inside the app, you are not able to access your recovery phrase as no password is set up.
Steps to reproduce

Start initial setup of Transaction Tool
Generate Recovery Phrase
Click Cancel on Password Box
Click Finish to enter App
Select Keys -> Recovery Phrase
Click Confirm without entering password and confirm nothing opens.

Additional context
No response
Hedera network
other
Version
v0.3.0
Operating system
macOS

The issue also exists during the "Forgot your password" process.

I can reproduce it. I will issue a patch for v0.3.0

fixed


Integer literals out of range for their type are accepted

While I'm not exactly sure what I think syn should do about this, I think it's worth discussing because it affects users of syn as well as consumers of macros built on syn.
Simply put, even with a suffixed integer literal, syn allows values far out of range:
use syn;

fn main() {
    let val = syn::parse_str::<syn::LitInt>(&format!("{}i32", u64::max_value())).unwrap();
    println!("{:?}", val.value() as i32);
}

This prints -1 as you might expect for truncating an integer that's all 1-bits, but there's no error or warning reported to the user that this is out of range. It is on the macro author to check that the literal is in-range. For literals without a suffix this is more than fair enough, as the semantics depend entirely on context, but I feel like syn should provide some easy way to validate this for any given integer width and print a correctly spanned error, and even perform this automatically if the literal has a type suffix.
Now that TryFrom/TryInto is stable, the former is relatively trivial and most of the work involves just emitting a nice error:
// I'm pretty sure this impl is coherent
impl<I> TryFrom<LitInt> for I where I: TryFrom<u64> {
    type Error = syn::Error;

    pub fn try_from(lit_int: LitInt) -> Result<I, syn::Error> where I: TryFrom<u64> {
        lit_int.value().try_into().map_err(/* convert to syn::Error with span */)
    }
}

It actually may be better to have a separate impl per integer type so we can include the expected integer type in the error message as the error type for TryFrom with ints does not contain this information.

Yep, the API of LitInt is not good. I had written about how I want the design to work previously in https://github.com/dtolnay/syn/pull/574#issuecomment-457499745 but forgot to file issues. I filed #663 and #664 now to follow up. Let me know what you think.


It is not clear to user if "Host" and "Base" is part of License subsection

Issue
When License subsection is open in expanded view, it becomes difficult to understand if Host and Base fields are under this. The dividing lines are not clear enough to distinguish Host and Base fields from that under License.
Solution

Indicate if the fields are related to each other with info tip OR
if Host and Base fields are separate from License subsection, make the divider lines more visible. Possibly add the fields under another Subsection.

Fixed with new UI.
Closing the issue


Mentioning the default configuration directory of the tool.

Description:
In the table(please refer highlighted text in below image), It would be better to mention the default config location below the description in [1]

[1] https://docs.wso2.com/display/SP4xx/Removing+Personally+Identifiable+Information+via+the+Forget-me+Tool
Suggested Labels:
Type/Doc Type/Improvement

Corrected as follows:

In [1], mentioned the following.
"If you do not specify a value for this option, the <DAS_HOME>/repository/components/tools/identity-anonymization-tool-x.x.x/conf directory (which is the default configuration directory of the tool) is used."

In [2]. mentioned the following.
"If you do not specify a value for this option, the <SP_HOME>/wso2/tools/identity-anonymization-tool-x.x.x/conf directory (which is the default configuration directory of the tool) is used."

[1] https://docs.wso2.com/display/DAS3xx/General+Data+Protection+Regulations+for+WSO2+Data+Analytics+Server
[2] https://docs.wso2.com/display/SP4xx/Removing+Personally+Identifiable+Information+via+the+Forget-me+Tool

Verified on docs


Fix deprecation and Enum issues for python 3.11; minordoc string fix

IntEnum.str now returns a value rather than the full name. This creates the CoverpointBinEnumModel calling Enum.str to replicate the full name it had before under python 3.10-.
Calling random.sample() on a set was deprecated in 3.11, this now follows the error message recommendation to cast it to sorted.
Minor docstring fix for randsz_list_t.

Many thanks, @alwilson! Looks great to me.


Submit COmplex PAthway SImulator 4.30.233

id: copasi
version: 4.30.233
specificationsUrl: https://raw.githubusercontent.com/biosimulators/Biosimulators_COPASI/a18e42b7596555df172572bd896396ac9a0e89a8/biosimulators.json
specificationsPatch:
version: 4.30.233
validateImage: true
commitSimulator: true

Thank you @biosimulators-daemon for your submission to the BioSimulators simulator validation/submission system!
The BioSimulators validator bot is validating the specifications of your simulator, validating your Docker image and committing your simulator to the BioSimulators registry.
We will discuss any concerns with your submission in this issue.
A complete log of your simulator submission job is available here.

The specifications of your simulator is valid!

Summary of tests

Executed 12 test cases

Passed 6 test cases:

docker_image.BioContainersLabelsTestCase
docker_image.OciLabelsTestCase
published_project.PublishedProjectTestCase:sbml-core/Ciliberto-J-Cell-Biol-2003-morphogenesis-checkpoint
published_project.PublishedProjectTestCase:sbml-core/Tomida-EMBO-J-2003-NFAT-translocation
published_project.PublishedProjectTestCase:sbml-core/Varusai-Sci-Rep-2018-mTOR-signaling-LSODA-LSODAR-SBML
sedml.MultipleTasksPerSedDocumentTestCase

Failed 0 test cases

Skipped 6 test cases:

published_project.PublishedProjectTestCase:bngl/Dolan-PLoS-Comput-Biol-2015-NHEJ
published_project.PublishedProjectTestCase:bngl/test-bngl
published_project.PublishedProjectTestCase:sbml-core/Caravagna-J-Theor-Biol-2010-tumor-suppressive-oscillations
published_project.PublishedProjectTestCase:sbml-core/Parmar-BMC-Syst-Biol-2017-iron-distribution
published_project.PublishedProjectTestCase:sbml-core/Szymanska-J-Theor-Biol-2009-HSP-synthesis
published_project.PublishedProjectTestCase:sbml-core/Vilar-PNAS-2002-minimal-circardian-clock

The image for your simulator is valid!

Your submission was committed to the BioSimulators registry. Thank you!
Future submissions of subsequent versions of copasi to the BioSimulators registry will be automatically validated. These submissions will not require manual review by the BioSimulators Team.


Refactor .SAFE with .zip replacement

Summary
In https://github.com/CDSETool/CDSETool/blob/main/src/cdsetool/download.py#L47
a replacement of .SAFE with .zip is performed. While this is true for e.g. Sentinel 2, it is not valid for Sentinel 3 (which "title" ends with SEN3).
Moreover, a simple refactor could be performed for not replacing .SAFE with .zip, but appending .zip in the end, in order to maintain uniformity with the Copernicus Browser download behavior, which maintains the .SAFE in the filename
Basic example
Motivation
Maintain uniformity along pipelines

Thanks for reporting the bug and the fix. I personally only use Sentinel-1 and -2 data so this was a blindspot for me. I also appreciate the uniformity with the Copernicus browser. Thanks a lot!


[FLINK-6137][cep] Activate strict checkstyle for flink-cep

Thanks for contributing to Apache Flink. Before you open your pull request, please take the following check list into consideration.
If your changes take all of the items into account, feel free to open your pull request. For more information and/or questions please refer to the How To Contribute guide.
In addition to going through the list, please provide a meaningful description of your changes.

[ ] General

The pull request references the related JIRA issue ("[FLINK-XXX] Jira title text")
The pull request addresses only one issue
Each commit in the PR has a meaningful commit message (including the JIRA id)

[ ] Documentation

Documentation has been added for new functionality
Old documentation affected by the pull request has been updated
JavaDoc for public methods has been added

[ ] Tests & Build

Functionality added by the pull request is covered by tests
mvn clean verify has been executed successfully locally or a Travis build has passed

You can rebase this PR now to get rid of the scala import block commit.

You'll have to rebase this again to resolve some conflicts, #3978 has fixed a bug in the CEPOperatorTest and hardened it a bit.
The suppressLoadErrors commit has also been merged.

I've rebased this locally and will merge this after going through the changes once again.


Update navigation-lifecycle.md

Make sure to add your changes to versioned docs
Thanks for opening a PR!
The docs cover several versions of react-navigation, and in some cases there are several files (for version 1, version 2 and etc.) that all describe single page of the docs (eg. "Getting Started").
Please make sure that the edit you're making in docs/file-you-edited.md is also included in the file for the correct version, eg. website/versioned_docs/version-3.x/file-you-edited.md for version 3. :+1:

hi! thanks for the contribution; unfortunately we have a separate process for translations and this cannot be merged directly. Maybe @shixiaoquan can help?

Closing due to no response


CreateDate as token for FileName/AvailabilityGroupFileName

Hi,
I would like to have the ability to include the database creation date as a filename token.
SELECT name,create_date FROM sys.databases
I have a DatabaseBackup job running to make sure we always have a monthly backup sent to Azure Blob Storage whenever we add a new database. With the createdate token in the filename, I could make sure we get a new backup created if another database is restored with the same name as a previously backed up database name.

If I were to follow the same standard as for the backup timestamp, then I would need creation_date tokens for the different parts of the date and time.
https://ola.hallengren.com/sql-server-backup.html#FileName


Initial implementation of the navigation

This PR includes a simple implementation of opening a new screen on top of the previous one.
In LiveView, the basic usage is define a function like below:
  def handle_event("navigate", _params, socket) do
    {:noreply, push_navigate(socket, to: "/counter")}
  end

and call it from the client, like this:
<Button phx-click="navigate">
  <Text>Go to counter</Text>
</Button>

This PR includes a simplified usage of the LiveView composable. Now, you just need to pass the URL:
class MainActivity : ComponentActivity() {
    override fun onCreate(savedInstanceState: Bundle?) {
        super.onCreate(savedInstanceState)

        setContent {
            LiveView(url = "http://<IP_ADDRESS>:4000")
        }
    }
}

But it's still necessary to host the *.aar file somewhere (maybe on Jitpack) in order to use the library in a separate project.

In case someone wants to run this example. It depends on the Scratchboard app (branch "next").

The Navigate button pushes a new view, so if the user presses back, the previous screen is displayed again.
The Redirect button, on the other hand, pops the current view and pushes the new view. So, basically, it replaces the current view.


Suggestion︱Class﹣Property Assertion Detection from Methods in Constructor

Suggestion
🔍 Search Terms

Class
Property
Assertion
Detection
Check
Methods
Constructor

✅ Viability Checklist
My suggestion meets these guidelines:

[X] This wouldn't be a breaking change in existing TypeScript/JavaScript code
[X] This wouldn't change the runtime behavior of existing JavaScript code
[X] This could be implemented without emitting different JS based on the types of the expressions
[X] This isn't a runtime feature (e.g. library functionality, non-ECMAScript syntax with JavaScript output, new syntax sugar for JS, etc.)
[X] This feature would agree with the rest of TypeScript's Design Goals.

⭐ Suggestion
In Classes, add Property Assertion Detection from Methods in Constructor Classes
🧪 Exemple
class Car {

	name: string;

	constructor() {
		this.setName();
	}

	setName() {
		this.name = "famousBrand famousModel";
	}

}

Produces:
Property 'name' has no initializer and is not definitely assigned in the constructor.ts(2564)

💻 Workaround
Use definite assignment assertion (! after the propriety name)

Duplicate of #21132.  Also worth considering: https://github.com/microsoft/TypeScript/issues/50643#issuecomment-1237553642

This issue can be deleted


Cannot build on iOS

I got A function declaration without a prototype is deprecated in all versions of C error

After fix suggestion by Xcode, I got another error
Expression does not compute the number of elements in this array; element type is 'const unichar' (aka 'const unsigned short'), not 'char'

My Xcode version is: 14.3.1
Thank you

@kruyvanna Actually we don't get any these errors on our react native projects in xcode.

@kruyvanna You able to solve this issue? It seems when a project is an expo project then this issue occurs.


Add more support for qt signals in futures

This set of commits adds support for awaiting on PyQt signals, as well as emitting a signal once a future / task is done. While it's a non-standard addition, I believe it's very useful for any code utilizing Qt - with that, interaction with regular signalling Qt code becomes much more convenient. Now we can await on dialogs or signals in user code, and a future can be connected with Qt style code with its 'done' signal.
Fixes #90.

I did not document any of the features yet - I'll do that tomorrow morning.

documentation would be really helpful.
In particular, can you explain how this differs from, this
import functools
from asyncio import Future

# myobject  is an instance of QObject or a subclass of QObject & myobject.mysignal is a signal
future = asyncio.Future()
myobject.mysignal.connect(functools.partial(future.set_result))
await future

(I'd also really prefer if the tests pass in CI before merging, but the tests are quite finicky especially the appveryor tests)

It doesn't actually differ much, beyond being able to await on multiple signals at a time (which can be done just by connecting to multiple signals), and keeping references to lambdas (since PyQt for example doesn't allow us to disconnect them). The example you've provided is probably a better solution than adding an extra method to the event loop.
I'll look at the tests.

I mean... you can await multiple futures with asyncio.wait, but I guess it's kind of awkward.


Support macOS with arm64 architecture

In an arm64 macOS environment (M1 MacBook for example), this package fails to install:
@ocular-d/vale-bin <err> Error: Failed to find source that matches darwin arm64
@ocular-d/vale-bin <err> vale failed to download

I've tested this change locally and can confirm it works as expected on my M1 MacBook Pro.

@mrmckeb 1.0.17 is published!
Thank you!

Thank you for the prompt action!


fix: remove results {} from osco-to-oscal console display

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] My code follows the code style of this project.
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[ ] I have added tests to cover my changes.
[x] All new and existing tests passed.
[x] All commits are signed-off.

Summary
Fix task osco-to-oscal console display - remove: results {}
Key links:

Sonar coverage

Closes #844.


[feature] Cookie consent (#1055)

Cookie consent for compliance
Demo
https://user-images.githubusercontent.com/50227291/186684043-b502d319-2865-4121-9d84-4c7789c17496.mov
Customizable cookies consent banner
https://user-images.githubusercontent.com/50227291/186684374-a7db4ecc-2c1b-4b78-98ba-f9ff680efd58.mov

Should I customize the cookie consent popup from the frontend, or make a commit to this branch containing the cookie consent markup?

@Ayon95 yes and no.
Let me explain-- the code here for the pop up is the default styling and structure. This is what we will ship out of the box. So you will need to create a UI that looks on-brand for Violet Rails and has 2 buttons. Please coordinate with @Pralish on this but I recommend opening a PR against this branch (using this as your base branch, so checkout from here not master) with your changes for the default markup.
That said, once deployed you will immediately go to the Nikean Admin and customize it such that it aligns with Nikean's brand design/language.

Is it necessary to open a PR against this branch with my changes since I will have to customize the markup and styling for Nikean from admin?

@Ayon95 to be clear, you need to do 2 things.
First, submit a default UI for the cookie consent on this branch.
Second, Once deployed you will customize the pop up for clients on a per site basis.

Okay, thanks for clarifying. I'll have to take a look at it later. I'm out at the moment.

Acceptance criteria 📋

General regression pass: API Actions ⌛
General regression pass: API Resource Tracking - visitors and users ⌛
General regression pass: Users Tracking ⌛
General regression pass: Analytics - visitors and users tracking ⌛
General regression pass: Ahoy JS events ⌛
Feature validation: Ahoy JS events/tracking fails gracefully if the user has declined cookies
Feature validation: Ahoy JS events/tracking does not occur if the user has declined cookies
Feature validation: visits are not logged if the user has declined cookies - (as a visitor and signed in user)

❌ blockers (WIP ⌛ )

Redactor is broken on first render (refreshing the page fixes it)-- this should not be the case:

Related to the above, snippet renderer is broken as well:

Default banner should have a solid background for legibility over various interfaces

Okay, I'll implement this layout then. Should I use white for the background color?

@Ayon95 yup, feel free to use white or black depending on your best judgement.
The key is to show user (like in the OMX example I illustrated above) that this pop up is not dismissible without making a choice. Nothing under it should be clickable and everything around it should be grayed out

Does this look fine?
Mobile:

Desktop:

@Ayon95 looks good! Nothing is clickable in that Gray'd out area right?

Yeah, nothing underneath the gray area can be clicked.

@Ayon95 that works. Btw before you open the PR you should git fetch and check out your change branch from the top of this branch (since I merged your last change in already)

@Ayon95 your client-side changes look good on Heroku 🌏

@Pralish you're up next with the server changes 🤖

TODO
@Pralish we will need to document how to customize the popup:

@donrestarone , I have addressed the issue. Can we have another round of alpha testing.

Acceptance criteria 📋

General regression pass: API Actions ⌛
General regression pass: API Resource Tracking - visitors and users ⌛
General regression pass: Users Tracking⌛
General regression pass: Analytics - visitors and users tracking ⌛
General regression pass: Ahoy JS events ⌛
General regression pass: visit/events are tracked after consent ⌛ pending fix
Feature validation: Ahoy JS events/tracking fails gracefully if the user has declined cookies ⌛
Feature validation: Cookie consent is only shown once ⌛
Feature validation: Cookie consent is shown in forum ⌛
Feature validation: Cookie consent is shown in blog ⌛
Feature validation: Cookie consent is shown in web ⌛
Feature validation: Cookie consent is shown in admin ⌛
Feature validation: Ahoy JS events/tracking does not occur if the user has declined cookies ⌛
Feature validation: visits are not logged if the user has declined cookies - (as a visitor and signed in user)⌛
Consent popup is not shown if tracking is not enabled ⌛
General regression pass: Recaptcha V2 and V3 forms ⌛ pending staging

thanks @Pralish @Ayon95 !
⚠ Temporary canary deployment to staging

The default consent popup isn't perfect, here are some examples where it's broken 'out of the box'

When this goes into production we should be ready to address issues as they come up.


feat(nim): added queries

Do you need something else from me to merge this PR or are you just short on time?


How to make it work in Swoole Server

Hi, I'm trying to implement in Swoole Server but it returns nothing in my Network tab of Google Chrome. No Status, No Protocol, No Type and No Size. But it is working fine the terminal.
Here is the code...
$http->on('request', function (Request $request, Response $response) {
    $response->header('Content-Type', 'text/event-stream');
    $response->header('Cache-Control', 'no-cache');
    $response->header('Connection', 'keep-alive');
    $response->header('X-Accel-Buffering', 'no');

    $response->end( (new SSE())->start(new Update(function () {
        $time = date('Y-m-d H:i:s');
        $news = [['id' => $time, 'title' => 'title ' . $time, 'content' => 'content ' . $time]]; // Get news from database or service.
        if (empty($news)) {
            return false; // Return false if no new messages
        }
        return json_encode(compact('news'));
    }), 'news') );
});

Thank you in advance.

v1.1.8 Swoole Demo.

Awesome! Thank you so much. It's working now except that I can't see status SSE status on my Netwok tab :) It's fine for now, since I'm able to see it on my terminal.


Silabs

custom XML loading fixes
few minor improvements

@tecimovic is there a quick summary of the goal of the fixes somewhere?  Hard to review if I don't know what the goal is, hence have no idea whether it's being achieved.

Good point...
1.) Addressing: https://github.com/project-chip/zap/issues/335
(@jingteng25742 , please provide more details if this is wrong. This was mostly your work.)
2.) Adding Cypress test to make sure this doesn't get broken again.
3.) Some minor fixes along the way.


avutil dll will fail certification because Sleep() is not supported in Windows Phone 8.1

The supported APIs test detected the following errors:

This API is not supported for this application type - Api=Sleep. Module=api-ms-win-core-synch-11-2-0.dll. File=avutil-xx.dll.

Did you build avutil-xx.dll using the instructions below?
https://trac.ffmpeg.org/wiki/CompilationGuide/WinRT
If so, could you share the FFmpeg revision you are at along with all configure options you use?

yes.  I used the instructions for "Windows Phone 8.1 ARM" from https://trac.ffmpeg.org/wiki/CompilationGuide/WinRT

RELEASE file says "2.5.git"

note: code will pass msvc certification test but once app is submitted, MS periodic scans will catch the Sleep() call and send you an email about the invalid api usage (maybe my desktop msvc cert test app is outdated).

I used the configure params from the "Windows Phone 8.1 ARM" instruction (see answer#1).  My configure.mak file starts with:

Automatically generated by configure - do not modify!
ifndef FFMPEG_CONFIG_MAK
FFMPEG_CONFIG_MAK=1
FFMPEG_CONFIGURATION=--toolchain=msvc --disable-programs --disable-dxva2 --disable-asm --arch=arm --as=armasm --cpu=armv7 --enable-thumb --enable-shared --enable-cross-compile --target-os=win32 --extra-cflags='-MD -DWINAPI_FAMILY=WINAPI_FAMILY_PHONE_APP -D_WIN32_WINNT=0x0603 -D__ARM_PCS_VFP' --extra-ldflags='//appcontainer -MACHINE:ARM -subsystem:console -opt:ref WindowsPhoneCore.lib RuntimeObject.lib PhoneAppModelHost.lib -NODEFAULTLIB:kernel32.lib -NODEFAULTLIB:ole32.lib' --prefix=Build/WindowsPhone81/ARM --disable-doc --disable-ffplay --disable-ffserver --disable-ffmpeg --disable-postproc --disable-avfilter --disable-avdevice --disable-encoders --disable-hwaccels --disable-indevs --disable-outdevs --disable-devices --disable-filters --disable-bzlib --disable-pthreads --disable-debug --enable-decoder=mjpeg --enable-decoder=h264 --enable-decoder=mp3 --enable-decoder=mp2 --enable-decoder=mpegaudio --enable-parser=h264 --enable-parser=mpegaudio --enable-demuxer=h264 --enable-demuxer=rtsp --enable-demuxer=rtp --enable-protocol=rtsp --enable-protocol=rtp --enable-protocol=udp --enable-protocol=tcp --enable-protocol=http
prefix=Build/WindowsPhone81/ARM
LIBDIR=$(DESTDIR)${prefix}/lib
SHLIBDIR=$(DESTDIR)${prefix}/bin
INCDIR=$(DESTDIR)${prefix}/include
BINDIR=$(DESTDIR)${prefix}/bin
DATADIR=$(DESTDIR)${prefix}/share/ffmpeg
DOCDIR=$(DESTDIR)${prefix}/share/doc/ffmpeg
MANDIR=$(DESTDIR)${prefix}/share/man
Hope that helps,
Thanks, Rob

I didn't manage to get past the desktop certification. All ffmpeg dlls fail.
:◦File avcodec-56.dll has failed the AppContainerCheck check.
◦File avdevice-56.dll has failed the AppContainerCheck check.
◦File avfilter-5.dll has failed the AppContainerCheck check.
◦File avformat-56.dll has failed the AppContainerCheck check.
◦File avutil-54.dll has failed the AppContainerCheck check.
◦File swresample-1.dll has failed the AppContainerCheck check.
◦File swscale-3.dll has failed the AppContainerCheck check.

You cannot use desktop dll directly.
If you want, you can try my fork https://github.com/qyljcy/FFmpeg. It's based on ffmpeg 2.4 and all dlls can past WACK

The linker flag -APPCONTAINER is missing from the compilation guide. You can simply append --extra-ldflags with -APPCONTAINER and rebuild the libraries and apps to fix it. The compilation guide is currently being updated to address the issue.

@Rob (n4spd): Your config seems to have appcontainer linker flag but it may be ignored since it is prefixed with slash (/) instead of dash (-). I.e.
--extra-ldflags='-appcontainer
instead of
--extra-ldflags='//appcontainer
This is possibly ignored during build and the config.log may warn you about it.
Apart from that, you mentioned that this app package passed the Windows App Certification Kit but somehow rejected from the submission. Can you share the Windows App Certification Kit version? Meanwhile could you try the change recommended above?

Ups, forgot to mention i fixed it soon after that post :P

The https://trac.ffmpeg.org/wiki/CompilationGuide/WinRT build instruction has been updated to ensure it builds fine with the latest revision and pass the Windows App Certification Kit.
@n4spd: Are you still having the certification issue?

I am using Windows App Certification Kit 3.4.   Again, WACK 3.4 passes fine, NO AppContainerCheck error or no error about Sleep() usage not available in Phone 8.1 universal app.

will change to -appcontainer for next release and see if that helps.

it's only after 1-2 weeks that I got an email about the Sleep API usage not available on phone 8.1.  The function av_usleep() in file time.c in libavutil calls Sleep() which is not available in windows phone 8.1 universal app.

thx rob

Hi @n4spd, you can try my ffmpeg fork. I have used winrt api instead of sleep().
https://github.com/qyljcy/FFmpeg
Just run the script and take a coffee, hope you can enjoy it.

Thanks for the update Rob (n4spd). Let me know if you still have any problem after adapting the -appcontainer LD flag.


[e2e]: delegator-lowperms tag main default slsa3

Repo: https://github.com/slsa-framework/example-package/tree/v47.0.510
Run: https://github.com/slsa-framework/example-package/actions/runs/12185437949
Workflow file: https://github.com/slsa-framework/example-package/tree/main/.github/workflows/e2e.delegator-lowperms.tag.main.default.slsa3.yml
Workflow runs: https://github.com/slsa-framework/example-package/actions/workflows/e2e.delegator-lowperms.tag.main.default.slsa3.yml
Trigger: push
Branch: v47.0.510
Date: Thu Dec  5 18:07:25 UTC 2024

Repo: https://github.com/slsa-framework/example-package/tree/v47.0.511
Run: https://github.com/slsa-framework/example-package/actions/runs/12203767951
Workflow file: https://github.com/slsa-framework/example-package/tree/main/.github/workflows/e2e.delegator-lowperms.tag.main.default.slsa3.yml
Workflow runs: https://github.com/slsa-framework/example-package/actions/workflows/e2e.delegator-lowperms.tag.main.default.slsa3.yml
Trigger: push
Branch: v47.0.511
Date: Fri Dec  6 18:22:12 UTC 2024
Tests are passing now. Closing this issue.


Company Customfile page - Clear filter is not working when search service filter

Describe the bug

when filter with service clear all button not working

when filter with is rucurring clear all and remove type lable not removing after clear

hey, is that only one issue that the clear button not working


1.87 could not run in ubuntu 22.04 long term support

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

VS Code Version: 1.87
OS Version: ubuntu 22.04

Steps to Reproduce:

just show a white pannel and exit at once

According to https://ubuntu.com/about/release-cycle, ubuntu 22.04 will continue to be LTS standard security maintenance for Ubuntu Main (initial 5 years) utill 2027
google chrome have show the same problem
### Tasks

Thanks for creating this issue! It looks like you may be using an old version of VS Code, the latest stable release is 1.87.0. Please try upgrading to the latest version and checking whether this issue remains.
Happy Coding!

VS Code Version: 1.87

already the latest stable release 1.87.0, it will be ok if I go back to code_1.85.2-1705561292_amd64.deb. according to https://github.com/microsoft/vscode/issues/203375 , at last reply, it should allow VS Code to connect to an OS that is not supported by VS Code (no support for glibc >= 2.28) for 12 more months.

more infomation
$ldd --version
ldd (Ubuntu GLIBC 2.35-0ubuntu3.6) 2.35
Copyright (C) 2022 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
Written by Roland McGrath and Ulrich Drepper

https://github.com/microsoft/vscode/issues/203375 is about our remote development suite and unrelated to the issue you are facing.
Can you provide the output of code --verbose

#203375 is about our remote development suite and unrelated to the issue you are facing.
Can you provide the output of code --verbose

$ code --verbose
[0229/210945.895070:ERROR:directory_reader_posix.cc(42)] opendir /home/ww/.config/Code/Crashpad/attachments/054df6ee-8e8a-4784-bc1d-bbbd9225ad7e: No such file or directory (2)
[215375:0229/210945.985596:WARNING:bluez_dbus_manager.cc(247)] Floss manager not present, cannot set Floss enable/disable.
[main 2024-02-29T13:09:46.199Z] [File Watcher (node.js)] Request to start watching: /home/ww/.config/Code/User (excludes: , includes: , correlationId: ),/home/ww/.config/Code/User/settings.json (excludes: , includes: , correlationId: )
[main 2024-02-29T13:09:46.218Z] Starting VS Code
[main 2024-02-29T13:09:46.218Z] from: /usr/share/code/resources/app
[main 2024-02-29T13:09:46.218Z] args: {
_: [],
diff: false,
merge: false,
add: false,
goto: false,
'new-window': false,
'reuse-window': false,
wait: false,
help: false,
'list-extensions': false,
'show-versions': false,
'pre-release': false,
'update-extensions': false,
version: false,
verbose: true,
status: false,
'prof-startup': false,
'no-cached-data': false,
'prof-v8-extensions': false,
'disable-extensions': false,
'disable-gpu': false,
'disable-chromium-sandbox': false,
sandbox: false,
telemetry: false,
debugRenderer: false,
'enable-smoke-test-driver': false,
logExtensionHostCommunication: false,
'skip-release-notes': false,
'skip-welcome': false,
'disable-telemetry': false,
'disable-updates': false,
'use-inmemory-secretstorage': false,
'disable-workspace-trust': false,
'disable-crash-reporter': false,
'crash-reporter-id': '8a2bcf34-e163-4c59-b650-c7efd7aa5e18',
'skip-add-to-recently-opened': false,
'unity-launch': false,
'open-url': false,
'file-write': false,
'file-chmod': false,
force: false,
'do-not-sync': false,
trace: false,
'preserve-env': false,
'force-user-env': false,
'force-disable-user-env': false,
'open-devtools': false,
'disable-gpu-sandbox': false,
'__enable-file-policy': false,
'enable-coi': false,
'no-proxy-server': false,
'no-sandbox': false,
nolazy: false,
'force-renderer-accessibility': false,
'ignore-certificate-errors': false,
'allow-insecure-localhost': false,
'disable-dev-shm-usage': false,
'profile-temp': false,
logsPath: '/home/ww/.config/Code/logs/20240229T210946'
}
[main 2024-02-29T13:09:46.219Z] Resolving machine identifier...
[main 2024-02-29T13:09:46.220Z] Resolved machine identifier: dd6092725f5ab8c15b5437d5d0f7f3da10daa7c7619fdc26e5a5e060afce50d7
[main 2024-02-29T13:09:46.220Z] Main->SharedProcess#connect
[main 2024-02-29T13:09:46.230Z] [File Watcher (node.js)] Started watching: '/home/ww/.config/Code/User'
[main 2024-02-29T13:09:46.231Z] StorageMainService: creating application storage
[main 2024-02-29T13:09:46.236Z] ElectronURLListener: waiting for window to be ready to handle URLs...
[main 2024-02-29T13:09:46.236Z] lifecycle (main): phase changed (value: 2)
[main 2024-02-29T13:09:46.237Z] windowsManager#open
[main 2024-02-29T13:09:46.240Z] [File Watcher (node.js)] Started watching: '/home/ww/.config/Code/User/settings.json'
[main 2024-02-29T13:09:46.241Z] windowsManager#open pathsToOpen [
{
workspace: { id: '665b819eaea227624e2aa4da6411b503', uri: [v] },
type: 2,
exists: true
}
]
[main 2024-02-29T13:09:46.242Z] windowsManager#doOpenFolderOrWorkspace {
folderOrWorkspace: {
workspace: { id: '665b819eaea227624e2aa4da6411b503', uri: [v] },
type: 2,
exists: true
},
filesToOpen: undefined
}
[main 2024-02-29T13:09:46.244Z] IPC Object URL: Registered new channel vscode:f78f8f1a-47ab-40e0-aac0-b92a1752a638.
[main 2024-02-29T13:09:46.244Z] window#validateWindowState: validating window state on 3 display(s) { mode: 1, x: 1645, y: 1207, width: 1236, height: 614 }
[main 2024-02-29T13:09:46.244Z] window#validateWindowState: multi-monitor working area { x: 1024, y: 1080, width: 1920, height: 1080 }
[main 2024-02-29T13:09:46.244Z] window#ctor: using window state { mode: 1, x: 1645, y: 1207, width: 1236, height: 614 }
[main 2024-02-29T13:09:46.289Z] Setting proxy to 'http://<IP_ADDRESS>:7890', bypassing 'localhost,<IP_ADDRESS>/8,::1,'
[main 2024-02-29T13:09:46.291Z] window#load: attempt to load window (id: 1)
[main 2024-02-29T13:09:46.298Z] StorageMainService: creating workspace storage (665b819eaea227624e2aa4da6411b503)
[main 2024-02-29T13:09:46.299Z] windowsManager#open used window count 1 (workspacesToOpen: 0, foldersToOpen: 1, emptyToRestore: 0, emptyToOpen: 0)
[main 2024-02-29T13:09:46.300Z] lifecycle (main): phase changed (value: 3)
[main 2024-02-29T13:09:46.300Z] resolveShellEnv(): skipped (VSCODE_CLI is set)
[main 2024-02-29T13:09:46.301Z] update#setState idle
[215375:0229/210946.326019:ERROR:gpu_process_host.cc(995)] GPU process exited unexpectedly: exit_code=133
[215375:0229/210946.326035:WARNING:gpu_process_host.cc(1364)] The GPU process has crashed 1 time(s)
[215375:0229/210946.596443:ERROR:gpu_process_host.cc(995)] GPU process exited unexpectedly: exit_code=133
[215375:0229/210946.596465:WARNING:gpu_process_host.cc(1364)] The GPU process has crashed 2 time(s)
[215375:0229/210946.798353:ERROR:gpu_process_host.cc(995)] GPU process exited unexpectedly: exit_code=133
[215375:0229/210946.798383:WARNING:gpu_process_host.cc(1364)] The GPU process has crashed 3 time(s)
[215375:0229/210947.005889:ERROR:gpu_process_host.cc(995)] GPU process exited unexpectedly: exit_code=133
[215375:0229/210947.005909:WARNING:gpu_process_host.cc(1364)] The GPU process has crashed 4 time(s)
[215375:0229/210947.229404:ERROR:gpu_process_host.cc(995)] GPU process exited unexpectedly: exit_code=133
[215375:0229/210947.229423:WARNING:gpu_process_host.cc(1364)] The GPU process has crashed 5 time(s)
[215375:0229/210947.449964:ERROR:gpu_process_host.cc(995)] GPU process exited unexpectedly: exit_code=133
[215375:0229/210947.449983:WARNING:gpu_process_host.cc(1364)] The GPU process has crashed 6 time(s)
[main 2024-02-29T13:09:47.469Z] resolveShellEnv(): skipped (VSCODE_CLI is set)
[215375:0229/210947.569588:ERROR:gpu_process_host.cc(995)] GPU process exited unexpectedly: exit_code=133
[215375:0229/210947.569607:WARNING:gpu_process_host.cc(1364)] The GPU process has crashed 7 time(s)
[215375:0229/210947.686842:ERROR:gpu_process_host.cc(995)] GPU process exited unexpectedly: exit_code=133
[215375:0229/210947.686863:WARNING:gpu_process_host.cc(1364)] The GPU process has crashed 8 time(s)
[215375:0229/210947.804507:ERROR:gpu_process_host.cc(995)] GPU process exited unexpectedly: exit_code=133
[215375:0229/210947.804524:WARNING:gpu_process_host.cc(1364)] The GPU process has crashed 9 time(s)
[215375:0229/210947.804535:FATAL:gpu_data_manager_impl_private.cc(448)] GPU process isn't usable. Goodbye.
[0229/210947.810441:ERROR:elf_dynamic_array_reader.h(64)] tag not found

Are you launching the application as a root user ? Can you follow the steps from https://github.com/microsoft/vscode/wiki/Native-Crash-Issues#creating-a-crash-report and attach the crashdump.

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!

Are you launching the application as a root user ? Can you follow the steps from https://github.com/microsoft/vscode/wiki/Native-Crash-Issues#creating-a-crash-report and attach the crashdump.
dump.tar.GZ


fixing restore to work correctly with prototpyes

Huh, I think Travis is broken. It keeps saying my build is broken...

But for real:
mattlgy:~/workspace/stand-in (prototypes) $ npm test

><EMAIL_ADDRESS>test /home/ubuntu/workspace/stand-in
> belly-button && lab -t 100 -va code

Clean as a whistle! No issues found!

stand-in
  replace
    ✔ 1) replaces a defined method (14 ms)
    ✔ 2) correctly restores a replaced method (3 ms)
    ✔ 3) uses the correct this context (2 ms)
    ✔ 4) provides a mechanism to use the original method (0 ms)
    ✔ 5) provides the stand-in object as the first parameter to the function (3 ms)
    ✔ 6) supports deep paths for replace (1 ms)
    ✔ 7) supports replacing prototype methods (1 ms)
  prototypes
    ✔ 8) replaces a prototype method (0 ms)
    ✔ 9) correctly restores a replaced prototype method (1 ms)
  assertions
    ✔ 10) throws an error if obj is not defined (1 ms)
    ✔ 11) throws an error if obj is not an object (0 ms)
    ✔ 12) throws an error if obj[function] is undefined (1 ms)
    ✔ 13) throws an error if obj[function] is not a function (0 ms)
    ✔ 14) throws an error if fn is not a function (0 ms)
  duplication
    ✔ 15) throws an error if you try to replace without restoring on the same object (1 ms)
    ✔ 16) allows duplication methods if obj is a new instance (7 ms)
    ✔ 17) allows multiple methods to be replaced on a single instance (1 ms)

17 tests complete
Test duration: 47 ms
Assertions count: 45 (verbosity: 2.65)
No global variable leaks detected
Coverage: 100.00%

The build is failing because the old versions of Node don't like the const.

Ah, I see. I updated the travis file to target the newest unstable of node so it should stop complaining about new features. (I switch the consts the vars.)


Step-by-step tutorial for newbies

I wrote a step-by-step tutorial at https://goo.gl/UWKgTu
so anyone can make use of the effort on this repo so far.
There is a lot involved in making this happen, such as using a Terminal, installing Ruby and Git.
So I've separated the tutorial into several phases involving various amounts of preparation.

Test drive a demo site online.
The site is built with Jekyll and can perform text search on pre-defined text content.

Get a sample theme on your local machine working with search queries.
We setup your machine with Jekyll and Ruby, then clone a fork of a famous Jekyll theme adapted with search capabilities.

Edit the repo so your own posts are indexed.
We obtain API keys for a new account on the search service and use it to index new posts we add.

Add search features to another theme.
We deep dive into the theme to add JavaScript, CSS, and HTML.

I'm stuck on #2 on my implementation at
https://github.com/jetbloom/jetbloom.github.io
The site does not resolve publicly from my browser
https://jetbloom.github.io/
But locally, the site does highlight the search word in various posts.
However, when I first bring up the site, I'm getting a "404 Page not found".

Hello,
Thanks for the report.
I have no experience in pushing websites to gh-pages with a repo name being the same as your user name.I don't think this is related to this plugin, but to GitHub pages configuration, so I'll have to let you handle it.
Regarding the 404 page, I cannot reproduce the issue. I cloned your repo and started bundle exec jekyll serve and the website is available on http://<IP_ADDRESS>:4000/jetbloom.github.io/ with no 404 error.
Could you give me an example of the error you're having and the output you are expecting?

Hello @wilsonmar!
I think that there are several issues:

Your repo isn't in the right place. GitHub pages do not support original-flavoured Jekyll and Jekyll plugins so you shouldn't place that code there.
Your configuration of baseurl is wrong: you'll never have a website response on the domain root with a non-empty base url.

What I think you should do:

Create another repo for your Jekyll code
Branch this repo on a CI tool like Travis (I personaly use a free Codeship account) in order to automatize the Jekyll build and the deployment of the generated _site folder on https://github.com/jetbloom/jetbloom.github.io (master branch. gh-pages is useless on the User Homepage repo)

That way:

You'll modify and push your code
Your CI will be notified of the modification, will build and commit the result to https://github.com/jetbloom/jetbloom.github.io
Github will see the commit and deploy the website to https://jetbloom.github.io

Thanks @borisschapira for the input.

GitHub pages do not support original-flavoured Jekyll and Jekyll plugins so you shouldn't place that code there.
I think there's an error here. GitHub pages does understand basic Jekyll commands (vanilla Jekyll) but only a very limited list of plugins. The Algolia plugin is not part of it.

So you should be able to either:

push your Jekyll code (including the _posts, _layouts, etc) directories to gh-pages and let GH build it
locally build your Jekyll website and only commit the ./build directory to gh-pages and push it.

As for the other points, I also think the Travis solution is the most automated way. But @wilsonmar is trying to write a blog post that really starts on the lowest level possible so adding one more layer of CI might be too complex. Maybe manually running git push && jekyll algolia push is enough?


bump ahash crate to fix build

currently, cargo build generates the following error due to the removal of stdsim: https://github.com/rust-lang/rust/pull/117372
error[E0635]: unknown feature stdsimd
--> /home/cmichaud/.cargo/registry/src/index.crates.io-6f17d22bba15001f/ahash-0.8.3/src/lib.rs:99:42
|
99 | #![cfg_attr(feature = "stdsimd", feature(stdsimd))]

Also fixed two errors reported by clippy and ran cargo fmt that updated around 40 files.

the workflow is green in my fork after those changes.

sorry for the commits mess, I was trying to fix my GPG signature. I'm done.

it seems that int tests are broken on windows.

well, it seemed to be a randomness due to the use of rayon. I just disabled it for the get_hyperedges_intersections function to fix the issue.

well, it seemed to be a randomness due to the use of rayon. I just disabled it for the get_hyperedges_intersections function to fix the issue.

Actually this was a bug :) - thanks for tackling it!


Add more operators

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

Project coverage is 66.66%. Comparing base (719b019) to head (52db645).
Report is 1 commits behind head on main.

Files
Patch %
Lines

src/conversion.jl
0.00%
3 Missing :warning:

src/operators.jl
50.00%
3 Missing :warning:

Additional details and impacted files
@@            Coverage Diff             @@
##             main       #6      +/-   ##
==========================================
- Coverage   68.96%   66.66%   -2.30%
==========================================
  Files           5        5
  Lines          87       90       +3
==========================================
  Hits           60       60
- Misses         27       30       +3

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


[api] Enhanced Logging

Logging request start/end time
authentication type, authentication user/token/group
authorization user/group/role/tenant
request
response size, status, time_taken

https://trello.com/c/RnXvC6ic/151-api-improve-logging

@imtayadeway @gtanzillo  please review.  Thanks.

:+1: Looks good. This is a nice enhancement!

:+1: LGTM


use requestIdleCallback in modern browsers

Available in Chrome 47+ and Firefox 52+ it seems to be closest replacement as it yields to browser.

Definitely not. setImmediate is scheduling a task. requestIdleCallback waits until an idle period, then schedules a task. That could be a delay of up to 100 milliseconds.


Fix image url in post_detail template

@hedleyroos Please check

This is against develop, but we're working on feature/django-1.9.


three questions, thanks

Describe the feature or enhancement

How to view the current version of umami on the dashboard page?
Can the dashboard shrink the statistics page? Allow one page to display multiple website information.
The language setting cannot be saved, and the default language is still English after re-login.

There is no way currently. We will provide a way in the future.
I don't know what you mean by this.
The language should be saved since it uses local storage.


gtlike execution fail

Hello, I am running an analysis using ScienceTools-v10r0p5-fssc-20150518-x86_64-unknown-linux-gnu-libc2.12
I'm using Scientific Linux 6.9
Everything was running smoothly with sed till this
************************************************************
***   9     gtlike --- Run likelihood analysis
************************************************************
Traceback (most recent call last):
File "/home/Szakirov7/Desktop/SRMP/enrico/bin/enrico_sed", line 53, in
sed(config,infile)
File "/home/Szakirov7/Desktop/SRMP/enrico/bin/enrico_sed", line 13, in sed
run(infile)
File "/home/Szakirov7/Desktop/SRMP/enrico/enrico/RunGTlike.py", line 115, in run
FitRunner.PerformFit(Fit)
File "/home/Szakirov7/Desktop/SRMP/enrico/enrico/fitmaker.py", line 150, in PerformFit
self.log_like = Fit.fit(0,covar=True, optimizer=self.config['fitting']['optimizer'])
File "/home/Szakirov7/Desktop/SRMP/ScienceTools-v10r0p5-fssc-20150518-x86_64-unknown-linux-gnu-libc2.12/x86_64-unknown-linux-gnu-libc2.12/lib/python/SummedLikelihood.py", line 95, in fit
optObject=optObject)
File "/home/Szakirov7/Desktop/SRMP/ScienceTools-v10r0p5-fssc-20150518-x86_64-unknown-linux-gnu-libc2.12/x86_64-unknown-linux-gnu-libc2.12/lib/python/SummedLikelihood.py", line 184, in _errors
myOpt.find_min(verbosity, tol, self.tolType)
File "/home/Szakirov7/Desktop/SRMP/ScienceTools-v10r0p5-fssc-20150518-x86_64-unknown-linux-gnu-libc2.12/x86_64-unknown-linux-gnu-libc2.12/lib/python/pyLikelihood.py", line 2093, in find_min
return lib_pyLikelihood.Optimizer_find_min(*args)
RuntimeError: vector::_M_range_check
Can you recommend a course of action?

hi
did you ran gtlike in command line?
cheers

Have you checked if your fits files are healthy, they contain events and so? If they look fine, I would try playing a bit with the fitting options (tolerance, spetrum, sources that you put in the XML file and if their parameters are fixed, etc).


{{ env }} template is stripping leading zeros

This bit me because I using a git sha as an environment variable and evaluating it with,
tag: {{ env "DEPLOY_TAG" }}

Running

DEPLOY_TAG=0757192 helmfile build

evaluates as

tag: 757192

requiredEnv behaves the same way.
If this is working as intended I will close this issue, but I wanted to report this just in case anyone else runs into this.

I think that's how YAML works. Please use {{ env "DEPLOY_TAG" | quote}} or "{{ env "DEPLOY_TAG" }}" to make it a string.

Thanks for the reply! That makes total sense now that I think about it more.
Caught me by surprise because I think of environment variables as always being strings but they aren't really and Go treating it as a number didn't matter until, suddenly, it did when I had that leading zero.

Added a PR to update docs. You all can determine if it is needed or not.
Thanks again for the help!


One of the parameter types of function RWKV may be wrong

First of all, my English is not very good, please forgive me.
The type of the mode parameter for this line.
I think it may be Union, because it conflicts with the example in the README.

I think you are correct, good spot!

I think you are correct, good spot!

ok, thank you


doc: Fix Ruff's TD003 check

What type of PR is this? (check all applicable)

[ ] 💾 Refactor
[ ] ✨ Feature
[ ] 🐛 Bug Fix
[ ] 🔧 Optimization
[X] 📝 Documentation
[ ] ✅ Test
[ ] 🐳 Other

Checklist

[ ] Code follows style guide (ruff)
[ ] Tests added
[ ] Documented the changes

thanks for your pr - closing as this has gone out-of-date


Add support for preferredSize with context  in PreferredSizeWidget

We should update preferredSize to support BuildContext so it can use theme-based values instead of hard code values.
This will be useful in widgets such as AppBar and TabBar.
Related https://github.com/flutter/flutter/issues/111962 https://github.com/flutter/flutter/pull/116110

Awesome, thanks for filing this. There is a case in AppBar where it has kinda been implemented as a workaround.
Fixing this also includes

should replace the preferred size quirk in AppBar, and
allow us to update the TabBar preferredSize so it can be inline with M3 based on the theme flag useMaterial3.

#116928 was found to be too breaking since many many customer implement PreferredSize. For now, we are planning to update the TabBar preferredSize when M3 is on by default.

Would love to see this get going, I have a custom appbar widget that needs to change its sized based upon an InheritedWidget and currently there's no way of doing that (other than using slivers really) because the Scaffold only looks to AppBar with its primitive preferredHeightFor method.


OBS web source shows only adventure title image

TL,DR: The interaction menu in the OBS doesn't show the login screen so I cannot login as Streamer.
Hey, I'm not sure if I should try to resolve this here or it's an OBS problem, but I'm having this issue described in the title.
See the image below and please tell me if you have any ideas. I even had to remove the ssl certificates from Foundry config because with them the OBS was showing only blanks screen - via normal browser you can click through "open the page anyway" process but OBS Interact feature doesn't provide any interaction in this matter.
PS. Followed the installation instructions properly I believe.

Unfortunately there's not much I can do from my side to help fix deficiencies in the OBS browser source. It is possible to pass chromium/cef flags on the OBS command-line, for example you can start it with obs --remote-debugging-port=9222 and then open http://localhost:9222 in your browser to gain access to the webview Javscript console and look for errors. You might also be able to do things like force hardware acceleration if it's not working, by using chrome CLI arguments.
As an aside, the SSL certs would either need to be valid for your IP/domain (using LetsEncrypt for example), or you'd need to add the CA to your operating system's trust store if they're self-signed.
An alternative to using the built-in browser source is to just open a new browser session and use window capture.
I'm going to close this issue, because I don't have any real way to troubleshoot problems between OBS and core Foundry, and it works fine for me here (I run Linux though, so there may be differences in how OBS works on other platforms). However if you do manage to work out what's causing this for you, please post your findings here in case someone else runs into the same problem and comes searching.

Since I had another report of this, I booted a Windows install and fired up the debugger. It looks like the problem is that OBS on Windows bundles an ancient version of CEF, because they haven't managed to get texture copying working on that platform, which would otherwise tank performance. Here's the current state of CEF support for the various platforms:
https://github.com/obsproject/obs-studio/discussions/3853
So, until OBS gets their Windows browser source updated to a recent chromium version, best bet is window capture from another browser session.


yo meanjs fail

I try runing "yo meanjs mean", got error in terminal: (I chose meanjs 0.4.1)

This may take a couple minutes.
Error: Command failed: /bin/sh -c cd mean && npm install
npm WARN engine<EMAIL_ADDRESS>wanted: {"node":">=0.8 <=0.12 || >=1 <=2"} (current: {"node":"5.0.0","npm":"3.3.6"})
npm WARN prefer global<EMAIL_ADDRESS>should be installed with -g
npm WARN prefer global<EMAIL_ADDRESS>should be installed with -g
npm WARN prefer global<EMAIL_ADDRESS>should be installed with -g
npm WARN prefer global<EMAIL_ADDRESS>should be installed with -g
In file included from ../src/bufferutil.cc:16:
../../nan/nan.h:261:25: error: redefinition of '_NanEnsureLocal'
NAN_INLINE v8::Local _NanEnsureLocal(v8::Local val) {
^
../../nan/nan.h:256:25: note: previous definition is here
NAN_INLINE v8::Local _NanEnsureLocal(v8::Handle val) {
^
../../nan/nan.h:661:13: error: no member named 'smalloc' in namespace 'node'
, node::smalloc::FreeCallback callback
^
../../nan/nan.h:672:12: error: no matching function for call to 'New'
return node::Buffer::New(v8::Isolate::GetCurrent(), data, size);
^~~~~~~~~~~
================================================================
Some log from npm-debug.log
127150 silly gentlyRm /Users/xxx/work/meanjs/mean/node_modules/.bin/node-inspector is being purged
127151 info build /Users/xxx/work/meanjs/mean/node_modules/node-inspector/node_modules/bufferutil
127152 verbose gentlyRm don't care about contents; nuking /Users/xxx/work/meanjs/mean/node_modules/.bin/node-debug
127153 verbose gentlyRm don't care about contents; nuking /Users/xxx/work/meanjs/mean/node_modules/.bin/node-inspector
127154 info lifecycle<EMAIL_ADDRESS><EMAIL_ADDRESS>127155 silly lifecycle<EMAIL_ADDRESS>no script for preinstall, continuing
127156 info linkStuff<EMAIL_ADDRESS>127157 silly linkStuff<EMAIL_ADDRESS>has /Users/xxx/work/meanjs/mean/node_modules/node-inspector/node_modules as its parent node_modules
127158 verbose linkBins<EMAIL_ADDRESS>127159 verbose linkMans<EMAIL_ADDRESS>127160 verbose rebuildBundles<EMAIL_ADDRESS>127161 info lifecycle<EMAIL_ADDRESS><EMAIL_ADDRESS>127162 verbose lifecycle<EMAIL_ADDRESS>unsafe-perm in lifecycle true
127163 verbose lifecycle<EMAIL_ADDRESS>PATH: /usr/local/lib/node_modules/npm/bin/node-gyp-bin:/Users/xxx/work/meanjs/mean/node_modules/node-inspector/node_modules/bufferutil/node_modules/.bin:/Users/xxx/work/meanjs/mean/node_modules/node-inspector/node_modules/.bin:/Users/xxx/work/meanjs/mean/node_modules/.bin:/usr/local/bin:/usr/local/sbin:/usr/bin:/bin:/usr/sbin:/sbin
127164 verbose lifecycle<EMAIL_ADDRESS>CWD: /Users/xxx/work/meanjs/mean/node_modules/node-inspector/node_modules/bufferutil
127165 silly lifecycle<EMAIL_ADDRESS>Args: [ '-c', 'node-gyp rebuild' ]
127166 silly lifecycle<EMAIL_ADDRESS>Returned: code: 1  signal: null
127167 info lifecycle<EMAIL_ADDRESS>Failed to exec install script
127168 verbose unlock done using /Users/xxx/.npm/_locks/staging-83821a4febaa2415.lock for /Users/xxx/work/meanjs/mean/node_modules/.staging
127169 silly rollbackFailedOptional Starting
127170 silly rollbackFailedOptional Finishing
127171 silly runTopLevelLifecycles Starting
127172 silly runTopLevelLifecycles Finishing
127173 silly install printInstalled
127174 warn EPEERINVALID<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none was installed.
127175 warn EPACKAGEJSON<EMAIL_ADDRESS>No repository field.
127176 verbose stack Error<EMAIL_ADDRESS>install: node-gyp rebuild
127176 verbose stack Exit status 1
127176 verbose stack     at EventEmitter. (/usr/local/lib/node_modules/npm/lib/utils/lifecycle.js:233:16)
127176 verbose stack     at emitTwo (events.js:87:13)
127176 verbose stack     at EventEmitter.emit (events.js:172:7)
127176 verbose stack     at ChildProcess. (/usr/local/lib/node_modules/npm/lib/utils/spawn.js:24:14)
127176 verbose stack     at emitTwo (events.js:87:13)
127176 verbose stack     at ChildProcess.emit (events.js:172:7)
127176 verbose stack     at maybeClose (internal/child_process.js:818:16)
127176 verbose stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:211:5)
127177 verbose pkgid<EMAIL_ADDRESS>127178 verbose cwd /Users/xxx/work/meanjs/mean
127179 error Darwin 14.5.0
127180 error argv "/usr/local/bin/node" "/usr/local/bin/npm" "install"
127181 error node v5.0.0
127182 error npm  v3.3.6
127183 error code ELIFECYCLE
127184 error<EMAIL_ADDRESS>install: node-gyp rebuild
127184 error Exit status 1
127185 error Failed at the<EMAIL_ADDRESS>install script 'node-gyp rebuild'.
127185 error This is most likely a problem with the bufferutil package,
127185 error not with npm itself.
127185 error Tell the author that this fails on your system:
127185 error     node-gyp rebuild
127185 error You can get their info via:
127185 error     npm owner ls bufferutil
127185 error There is likely additional logging output above.
127186 verbose exit [ 1, true ]

I am having the same issue. Some Google searching directed me to an older version (<2.0.0) of nan is used by bson-ext, but I don't see that being used in the meanjs directory.
Environment
OS: UBUNTU 14.04 64bit
Node Version: 5.0
Error Log
$ yo meanjs
undefined
You're using the official MEAN.JS generator.
? What mean.js version would you like to generate? 0.4.0
0.4.0
? In which folder would you like the project to be generated? This can be changed later. mean
Cloning the MEAN repo.......

? What would you like to call your application? MEAN
? How would you describe your application? Full-Stack JavaScript with MongoDB, Express, AngularJS, and Node.js
? How would you describe your application in comma seperated key words? MongoDB, Express, AngularJS, Node.js
? What is your company/author name?
? Would you like to generate the article example CRUD module? Yes
? Would you like to generate the chat example module? Yes
   create mean/package.json
   create mean/bower.json
   create mean/config/env/default.js
Running npm install for you....
This may take a couple minutes.
Error: Command failed: /bin/sh -c cd mean && npm install
npm WARN engine<EMAIL_ADDRESS>wanted: {"node":">=0.8 <=0.12 || >=1 <=2"} (current: {"node":"5.0.0","npm":"3.3.6"})
npm WARN install Couldn't install optional dependency: Unsupported
npm WARN install Couldn't install optional dependency: Unsupported
npm WARN prefer global<EMAIL_ADDRESS>should be installed with -g
npm WARN prefer global<EMAIL_ADDRESS>should be installed with -g
npm WARN prefer global<EMAIL_ADDRESS>should be installed with -g
npm WARN prefer global<EMAIL_ADDRESS>should be installed with -g
In file included from ../src/bufferutil.cc:16:0:
../../nan/nan.h:261:25: error: redefinition of ‘template<class T> v8::Local<T> _NanEnsureLocal(v8::Local<T>)’
 NAN_INLINE v8::Local<T> _NanEnsureLocal(v8::Local<T> val) {
                         ^
../../nan/nan.h:256:25: error: ‘template<class T> v8::Local<T> _NanEnsureLocal(v8::Handle<T>)’ previously declared here
 NAN_INLINE v8::Local<T> _NanEnsureLocal(v8::Handle<T> val) {
                         ^
../../nan/nan.h:661:13: error: ‘node::smalloc’ has not been declared
     , node::smalloc::FreeCallback callback
             ^
../../nan/nan.h:661:35: error: expected ‘,’ or ‘...’ before ‘callback’
     , node::smalloc::FreeCallback callback
                                   ^
../../nan/nan.h: In function ‘v8::Local<v8::Object> NanNewBufferHandle(char*, size_t, int)’:
../../nan/nan.h:665:50: error: ‘callback’ was not declared in this scope
         v8::Isolate::GetCurrent(), data, length, callback, hint);
                                                  ^
../../nan/nan.h:665:60: error: ‘hint’ was not declared in this scope
         v8::Isolate::GetCurrent(), data, length, callback, hint);
                                                            ^
../../nan/nan.h: In function ‘v8::Local<v8::Object> NanNewBufferHandle(const char*, uint32_t)’:
../../nan/nan.h:672:67: error: call of overloaded ‘New(v8::Isolate*, const char*&, uint32_t&)’ is ambiguous
     return node::Buffer::New(v8::Isolate::GetCurrent(), data, size);
                                                                   ^
../../nan/nan.h:672:67: note: candidates are:
In file included from ../src/bufferutil.cc:10:0:
/home/maximmai/.node-gyp/5.0.0/include/node/node_buffer.h:31:40: note: v8::MaybeLocal<v8::Object> node::Buffer::New(v8::Isolate*, v8::Local<v8::String>, node::encoding) <near match>
 NODE_EXTERN v8::MaybeLocal<v8::Object> New(v8::Isolate* isolate,
                                        ^
/home/maximmai/.node-gyp/5.0.0/include/node/node_buffer.h:31:40: note:   no known conversion for argument 3 from ‘uint32_t {aka unsigned int}’ to ‘node::encoding’
/home/maximmai/.node-gyp/5.0.0/include/node/node_buffer.h:43:40: note: v8::MaybeLocal<v8::Object> node::Buffer::New(v8::Isolate*, char*, size_t) <near match>
 NODE_EXTERN v8::MaybeLocal<v8::Object> New(v8::Isolate* isolate,
                                        ^
/home/maximmai/.node-gyp/5.0.0/include/node/node_buffer.h:43:40: note:   no known conversion for argument 2 from ‘const char*’ to ‘char*’
In file included from ../src/bufferutil.cc:16:0:
../../nan/nan.h: In function ‘v8::Local<v8::Object> NanNewBufferHandle(uint32_t)’:
../../nan/nan.h:676:61: error: could not convert ‘node::Buffer::New(v8::Isolate::GetCurrent(), ((size_t)size))’ from ‘v8::MaybeLocal<v8::Object>’ to ‘v8::Local<v8::Object>’
     return node::Buffer::New(v8::Isolate::GetCurrent(), size);
                                                             ^
../../nan/nan.h: In function ‘v8::Local<v8::Object> NanBufferUse(char*, uint32_t)’:
../../nan/nan.h:683:12: error: ‘Use’ is not a member of ‘node::Buffer’
     return node::Buffer::Use(v8::Isolate::GetCurrent(), data, size);
            ^
make: *** [Release/obj.target/bufferutil/src/bufferutil.o] Error 1
gyp ERR! build error
gyp ERR! stack Error: `make` failed with exit code: 2
gyp ERR! stack     at ChildProcess.onExit (/usr/local/lib/node_modules/npm/node_modules/node-gyp/lib/build.js:270:23)
gyp ERR! stack     at emitTwo (events.js:87:13)
gyp ERR! stack     at ChildProcess.emit (events.js:172:7)
gyp ERR! stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:200:12)
gyp ERR! System Linux 3.13.0-67-generic
gyp ERR! command "/usr/local/bin/node" "/usr/local/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild"
gyp ERR! cwd /home/maximmai/webroot/meanjs/mean/node_modules/node-inspector/node_modules/bufferutil
gyp ERR! node -v v5.0.0
gyp ERR! node-gyp -v v3.0.3
gyp ERR! not ok
npm WARN EPEERINVALID<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none was installed.
npm WARN EPACKAGEJSON<EMAIL_ADDRESS>No repository field.
npm ERR! Linux 3.13.0-67-generic
npm ERR! argv "/usr/local/bin/node" "/usr/local/bin/npm" "install"
npm ERR! node v5.0.0
npm ERR! npm  v3.3.6
npm ERR! code ELIFECYCLE

npm ERR<EMAIL_ADDRESS>install: `node-gyp rebuild`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>install script 'node-gyp rebuild'.
npm ERR! This is most likely a problem with the bufferutil package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     node-gyp rebuild
npm ERR! You can get their info via:
npm ERR!     npm owner ls bufferutil
npm ERR! There is likely additional logging output above.

npm ERR! Please include the following file with any support request:
npm ERR!     /home/maximmai/webroot/meanjs/mean/npm-debug.log

    at ChildProcess.exithandler (child_process.js:203:12)
    at emitTwo (events.js:87:13)
    at ChildProcess.emit (events.js:172:7)
    at maybeClose (internal/child_process.js:818:16)
    at Process.ChildProcess._handle.onexit (internal/child_process.js:211:5)

Please post in the generator repo.


Including stdarg.h

It seems #include <stdarg.h> needs to be added to ChipmunkDemo.c, at least for OS X.

Just pushed the fix for that. Apparently I had it in my local repo, but hadn't pushed it. Thanks.