New Resource: AdcsEnrollmentWebService

Currently, there is no way to configure the web service. This is different from the web enrollment.
https://docs.microsoft.com/en-us/powershell/module/adcsdeployment/install-adcsenrollmentwebservice?view=win10-ps

Hi @kungfu71186 - would love to get this one in! Keen to contribute a PR? Otherwise it'll be on the backlog :grin: (I'm waaay behind at the moment :cry:).

@PlagueHO Yeah, leave it on the back burner for now. I got some other things to wrap and then I was going to help finalize ActiveDirectory. If I have some time after that, I'll take a look


Kicad files

I have the latest Kicad files but can't seem to open your files.  What version did you use? A PDF of parts lay out might be really nice!

Hi, good idea! Have added a parts layout here: https://github.com/dawsonjon/PicoRX/blob/master/PCB/pico_rx/component_layout.pdf
Not quite sure which version of Kicad I used originally, but I'm using Kicad7 to work on them and haven't had any issues.

I thank you for the PDF!!! That will help a great deal...
I have Kicad 8.0 and couldn't get a layout.  I then sent your files to my
boardhouse (in Iowa, that builds boards for my business (trying to retire))
and he couldn't read them either.  Well, your PDF layout will be more than
adequate!
I had 5 main board pcb's made.  If you have a friend in the USA that
needs one, let me know and I'll put it in an envelope.....
CHeers,
Jim W0CHL
On Fri, Mar 15, 2024 at 2:04 PM dawsonjon @.***> wrote:

Hi, good idea! Have added a parts layout here:
https://github.com/dawsonjon/PicoRX/blob/master/PCB/pico_rx/component_layout.pdf
Not quite sure which version of Kicad I used originally, but I'm using
Kicad7 to work on them and haven't had any issues.
—
Reply to this email directly, view it on GitHub
https://github.com/dawsonjon/101Things/issues/2#issuecomment-2000282106,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ALHB3QUW4HXTR5LPUHMRZD3YYNA45AVCNFSM6AAAAABEWWTV2WVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMBQGI4DEMJQGY
.
You are receiving this because you authored the thread.Message ID:
@.***>

It's alive!!  I just turned it on and it seems to work!
I found I had no Ferrite 0805, so I replaced them with 10uH 470 MOHM
inductors.
We have guests coming over soon, so I can't test more...
Thanks for a nice design!
Jim W0CHL
On Fri, Mar 15, 2024 at 2:04 PM dawsonjon @.***> wrote:

Hi, good idea! Have added a parts layout here:
https://github.com/dawsonjon/PicoRX/blob/master/PCB/pico_rx/component_layout.pdf
Not quite sure which version of Kicad I used originally, but I'm using
Kicad7 to work on them and haven't had any issues.
—
Reply to this email directly, view it on GitHub
https://github.com/dawsonjon/101Things/issues/2#issuecomment-2000282106,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ALHB3QUW4HXTR5LPUHMRZD3YYNA45AVCNFSM6AAAAABEWWTV2WVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMBQGI4DEMJQGY
.
You are receiving this because you authored the thread.Message ID:
@.***>

Hi Jim,
Very pleased to hear that you have got it running! Best of luck with your testing!
Many Thanks
Jon 2E0GXA

Hi,
Playing more with you PICO RX, I found the LTC6226 preamp was not working
correctly: traced down to the two voltage divider resistors, one of which
seems to be the wrong value.  I relapsed with 1% 10K's and that problem
went away.
It seems to work , although not overly sensitive.  I measured each cap in
the low pass filter and used   2% inductors.  I have an "ever present" TICK
when there is now signal present.  I know it's from the SSD1306 charge
pump: if you remove the display, the tick goes away.  Maybe you have a
display that doesn't have that issue?  If so, let me know where you bought
it...
So I'm still happy, but work on my part, still has to be done.
Thanks again,
Jim W0CHL
On Sun, Mar 17, 2024 at 4:11 AM dawsonjon @.***> wrote:

Hi Jim,
Very pleased to hear that you have got it running! Best of luck with your
testing!
Many Thanks
Jon 2E0GXA
—
Reply to this email directly, view it on GitHub
https://github.com/dawsonjon/101Things/issues/2#issuecomment-2002373417,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ALHB3QWLGPTDKOQTFEVJ43DYYVM2NAVCNFSM6AAAAABEWWTV2WVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMBSGM3TGNBRG4
.
You are receiving this because you authored the thread.Message ID:
@.***>

Only one issue remains: receiving CW on the SSB portion of 20 meter band. (listening 14.237mHz, hearing 14.037)  It seems to be a spur from the bottom of the 20 meter band.  Otherwise the radio works well!

Hi,
That sounds similar to this issue: https://github.com/dawsonjon/PicoRX/issues/3. There are two possible causes.
One possibility is images, caused by an imbalance in I and Q, in the linked example, the Q channel wasn't working at all. You could check for this by comparing the signal level on the I and Q input to the ADC, they should be about equal. If this is the problem, you would expect the signals to have the same signal strength at either frequency.
If this does turn out to be an imbalance in the I/Q channel, I would be interested to know which IC you were using in the Tayloe detector, I suspect that the root cause was a signal integrity issue and I am considering revising the design to include some termination.
The other possibility is aliasing which is a limitation in the current design. The ADC in the pi-pico doesn't have any anti-aliasing filters, and we are relying on the Tayloe detector to remove out of band signals. The Tayloe detector is effectively a second order low pass filter so only has a roll-off of about 12dB/octave. This means that a signal close to, but outside the 250kHz bandwidth would only be attenuated by a couple of S-points.
Thanks very much for your feedback on your build, its been very useful to get another perspective :-)
Kind regards
Jon

I'm using a SN74CBT3253D. In  trying to probe for I & Q A/D input, (pin
31 & 32) I see a great deal of 140 kHz signal when I just hook up the
ground of the scope to the PICO RX.  It's hard to tell what the actual
signal is.  I then carefully resoldered and checked the components around
the LTC6227 op amp. With the antenna input grounded, I seem to  have a
great deal of "birdies" present.
Can you explain the software? How does recall work?  I guess you need to
tell me how to store frequencies for recall? It doesn't remember that last
frequency you  were on?
One more thing: If I feed exactly 5 volts into the unit (drawing .022a),
the A/D reads 9.9 volts at -61C along with the SSD1306 charge pump noise
(ticking when no signal).. BUT if I feed only 4.75 volts in (at .038a) the
"tick sound" is not present!  The voltage still reads 9.9 v and -59C.....
Ideas on that issue?
You privately email me if you want just read my bio on QRZ.com. My email
is at the end.
Thanks,
Jim W0CHL
On Mon, Mar 18, 2024 at 1:35 PM dawsonjon @.***> wrote:

Hi,
That sounds similar to this issue: dawsonjon/PicoRX#3
https://github.com/dawsonjon/PicoRX/issues/3. There are two possible
causes.
One possibility is images, caused by an imbalance in I and Q, in the
linked example, the Q channel wasn't working at all. You could check for
this by comparing the signal level on the I and Q input to the ADC, they
should be about equal. If this is the problem, you would expect the signals
to have the same signal strength at either frequency.
If this does turn out to be an imbalance in the I/Q channel, I would be
interested to know which IC you were using in the Tayloe detector, I
suspect that the root cause was a signal integrity issue and I am
considering revising the design to include some termination.
The other possibility is aliasing which is a limitation in the current
design. The ADC in the pi-pico doesn't have any anti-aliasing filters, and
we are relying on the Tayloe detector to remove out of band signals. The
Tayloe detector is effectively a second order low pass filter so only has a
roll-off of about 12dB/octave. This means that a signal close to, but
outside the 250kHz bandwidth would only be attenuated by a couple of
S-points.
Thanks very much for your feedback on your build, its been very useful to
get another perspective :-)
Kind regards
Jon
—
Reply to this email directly, view it on GitHub
https://github.com/dawsonjon/101Things/issues/2#issuecomment-2004659469,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ALHB3QRCLHKP4BTE4IHQWNLYY4XYNAVCNFSM6AAAAABEWWTV2WVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMBUGY2TSNBWHE
.
You are receiving this because you authored the thread.Message ID:
@.***>


[WIP]feat: init optimizer trace

visit optimizer trace tool page via the specified url: /optimizer_trace

Codecov Report

Merging #1187 (8e05c1d) into master (36e7d2f) will decrease coverage by 3.72%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master    #1187      +/-   ##
==========================================
- Coverage   27.80%   24.07%   -3.73%
==========================================
  Files         286       92     -194
  Lines       16941     9313    -7628
  Branches      646        0     -646
==========================================
- Hits         4710     2242    -2468
+ Misses      12000     6931    -5069
+ Partials      231      140      -91

Flag
Coverage Δ

be_integration_test_latest
?

be_integration_test_v4.0.1
?

be_unit_test
24.07% <ø> (ø)

e2e_test
?

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

Impacted Files
Coverage Δ

pkg/pd/etcd.go
0.00% <0.00%> (-100.00%)
:arrow_down:

pkg/tidb/forwarder.go
0.00% <0.00%> (-78.88%)
:arrow_down:

pkg/tidb/client.go
0.00% <0.00%> (-55.84%)
:arrow_down:

pkg/apiserver/user/auth.go
0.00% <0.00%> (-51.68%)
:arrow_down:

pkg/apiserver/utils/auth.go
0.00% <0.00%> (-50.00%)
:arrow_down:

pkg/apiserver/debugapi/endpoint/models.go
64.70% <0.00%> (-35.30%)
:arrow_down:

pkg/apiserver/user/verify_sql_user.go
51.11% <0.00%> (-22.23%)
:arrow_down:

pkg/apiserver/utils/ngm.go
0.00% <0.00%> (-19.15%)
:arrow_down:

pkg/apiserver/statement/service.go
0.00% <0.00%> (-12.50%)
:arrow_down:

pkg/httpc/client.go
45.16% <0.00%> (-11.30%)
:arrow_down:

... and 197 more

Continue to review full report at Codecov.

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

/cc @breeswish @baurine
PTAL, thanks~

/merge


only serve compatible APIs from synctarget virtual workspace

followup of https://github.com/kcp-dev/kcp/issues/1777
the synctarget virtual workspace should only serve compatible APIs to the synctarget.
This is part of the epic https://github.com/kcp-dev/kcp/issues/912 to support location(compute) workspace.

Fixed in https://github.com/kcp-dev/kcp/pull/1828.


Support for ESRI Vector basemap

Is it a possibility to add support for ESRI's vector basemaps? I am trying to get an example together., and have started a stackoverflow question, which describes the issue in much details and has a partially working example.
Essentially I am stuck on being able to use ESRI styles.
Esri's leaflet port is able to do this in this example. And some information on esri style IDs is available here.
Here's the code I have so far:
var map = new ol.Map({
  layers: [
    new ol.layer.VectorTile({
      source: new ol.source.VectorTile({
        format: new ol.format.MVT(),

        tileGrid: ol.tilegrid.createXYZ({maxZoom: 22}),
        tilePixelRatio: 16,
        url: 'https://basemaps.arcgis.com/v1/arcgis/rest/services/World_Basemap/VectorTileServer/tile/{z}/{y}/{x}.pbf'
      })
    })
  ],
  target: 'map',
  view: new ol.View({
    center: [0, 0],
    zoom: 2
  })
});

Which renders the tiles without any styles for the vector tiles:

With some guidance, on how to get a working example, I am willing to attempt contribute this feature.

ESRI uses Mapbox Style objects for styling. In the Leaflet example you'll see that a resources/styles/root.json file is loaded. That is the style file, and you can use the ol-mapbox-style package create a fully styled OpenLayers map from the information contained in that style file. If you want to apply the style manually, use the mapbox-to-ol-style package instead.

perfect, but with one question.
       esri's root.json,   sprite and glyphs are not full URL, the are only last part as see below

In your example, those not full URL works,  but, I have test it in mapbox js api, it failed, error is can't parse URL,
I have to change those url to a full URL, to make it works.
                                   root_json = {

                                                      "version" : 8,
                                                      "name": "test",

                                                      //"sprite" : original_rootJson.sprite,    // original is not a full URL, not work  "../sprites/sprite"
                                                      // "sprite" : "https://tiles.arcgis.com/tiles/P3ePLMYs2RVChkJx/arcgis/rest/services/2020_USA_Median_Age/VectorTileServer/resources/sprites/sprite",
                                                      "sprite" : _sprite,

                                                      // "glyphs" : original_rootJson.glyphs,      // original is not a full URL, not work  "../fonts/{fontstack}/{range}.pbf"
                                                      // "glyphs" : "https://tiles.arcgis.com/tiles/P3ePLMYs2RVChkJx/arcgis/rest/services/2020_USA_Median_Age/VectorTileServer/resources/fonts/{fontstack}/{range}.pbf",
                                                      "glyphs" : _glyphs,

                                                      // root json  specification :   https://docs.mapbox.com/mapbox-gl-js/style-spec/sources/
                                                      "sources" : {

                                                                                "esri" : {
                                                                                "type" : "vector",

                                                                                //  By supplying TileJSON properties such as "tiles", "minzoom", and "maxzoom" directly in the source:
                                                                                "tiles": [
                                                                                // "https://tiles.arcgis.com/tiles/P3ePLMYs2RVChkJx/arcgis/rest/services/2020_USA_Median_Age/VectorTileServer/tile/{z}/{y}/{x}.pbf"
                                                                                _tile_pbf
                                                                                ],

                                                                                // "maxzoom": 14
                                                                                // By providing a "url" to a TileJSON resource
                                                                                // not work,yet
                                                                                //  "url" : "https://tiles.arcgis.com/tiles/P3ePLMYs2RVChkJx/arcgis/rest/services/Esri_Childrens_Map/VectorTileServer/tile/{z}/{y}/{x}.pbf"
                                                                                //  "url": "http://api.example.com/tilejson.json"

                                                                                }
                                                                  },

                                                      "layers":  original_rootJson.layers

                                      } // root_json

A lot has happened since this issue was closes. With the latest version of ol-mapbox-style, it is now easy to create a map from a Mapbox style document. And it also works for Esri style documents with relative urls. Example with the above style resource: https://codesandbox.io/s/infallible-tdd-h39j9?file=/src/index.js
This is all that's needed:
import createMap from "ol-mapbox-style";

createMap(
  "map",
  "https://tiles.arcgis.com/tiles/P3ePLMYs2RVChkJx/arcgis/rest/services/2020_USA_Median_Age/VectorTileServer/resources/styles/root.json"
);

@ahocevar   very cool, I create another test,  found a possible bug,
Can you take a look if that bug can be fixed?
The feature ID is always undefined, which should be a real id, should not be undefined.
                                        // bug, need fix, feature ID is always undefined
                                        var featureId = features[0].getId();

https://codesandbox.io/s/young-water-uquvh
You can also check the console.log
                                       console.log('feature featureId', featureId, features)

all the features, all id is undefined,

I mean the feature Id should be   ZIP Code/45 - 53 years of age, instead of undefined
I create the code sandbox link,
I try to get feature id, but it always undefined.
Should be a bug with easy fix, but I don't know how, it should be inside openlayers api
this is root.json
from   https://tiles.arcgis.com/tiles/P3ePLMYs2RVChkJx/arcgis/rest/services/2020_USA_Median_Age/VectorTileServer/resources/styles/root.json
                                     {
        "id": "ZIP Code/45 - 53 years of age",
        "type": "fill",
        "source": "esri",
        "source-layer": "ZIP Code",
        "filter": [
            "==",
            "_symbol",
            5
        ],
        "minzoom": 7.21,
        "maxzoom": 9.95,
        "layout": {},
        "paint": {
            "fill-color": "#FAB679",
            "fill-outline-color": "#D6D6D6"
        }
    },
    {
        "id": "ZIP Code/53 - 86 years of age",
        "type": "fill",
        "source": "esri",
        "source-layer": "ZIP Code",
        "filter": [
            "==",
            "_symbol",
            6
        ],
        "minzoom": 7.21,
        "maxzoom": 9.95,
        "layout": {},
        "paint": {
            "fill-color": "#FFDABF",
            "fill-outline-color": "#D6D6D6"
        }
    },

What you're looking at is the layer id, not the feature id. So instead of feature.getId(), you'll want to ask for feature.get('layer').

I test it
feature.get('layer').
I did get layer name, but not get layer id,  above example, layer name is  only "ZIP Code", which is from  "source-layer": "ZIP Code",
I want the layer-id,   should be same as  "id": "ZIP Code/45 - 53 years of age",
 zip code layer have many age group, root.json define which age group use which symbol by

      "filter": [
        "==",
        "_symbol",
        5
    ],

I could loop through root.json, find that age group by layer name and symbol value, extra coding, not good, may fail, if filter format changed.
How can I get layer ID "ZIP Code/45 - 53 years of age",   not the layer name "ZIP Code"

How to get layer id instead of get layer name?
                feature.get('layer').

This only get layer name,  it is "ZIP Code",  I try to get layer id, should be "ZIP Code/45 - 53 years of age",  but don't know how.
The layer id defined in root.json file

I compare with mapbox, this is a feature object in mapbox (vector tile)
                        layer: {id: "County:1/45 - 53 years of age", type: "fill", source: "esri", source-layer: "County:1", minzoom: 3.96, …}
                       properties: {_symbol: 5}
                       source: "esri"
                       sourceLayer: "County:1"
                      state: {}
                      type: "Feature"
                     _vectorTileFeature: Co {properties: {…}, extent: 4096, type: 3, _pbf: Js, _geometry: 7785, …}

This is openlayes ,  feature object (vector tile)
                        0: RenderFeature
                                     ends_: [14]
                                     extent_: (4) [....]
                                      flatCoordinates_: (14) [...]
                                      flatInteriorPoints_: null
                                      flatMidpoints_: null
                                      id_: undefined
                                      ol_uid: "169"
                                      properties_: {_symbol: 4, layer: "County:2"}
                                      type_: "Polygon"
                                      __proto__: Object

You can see, that openlayers put 'layer' inside 'properties_' and only collect source-layer name.
Mapbox, do it differently,   mapbox collect detailed info for 'layer', and you can read the layer's id, fill, color etc...
Openlayers might need improvement by include detailed info into a separated properties named 'layer'  from  feature
Those  'layer' properties, should include all detailed info such as layer id, fill, color etc....(those info can get from root.json layer definition)

@ahocevar
I use work around method to get it works on my local only, when upload to codesandbox, some how not showing map,
not sure why, it was working yesterday without work around.

This is not something that can be changed in OpenLayers. It has to be fixed in ol-mapbox-style. Please create a feature request issue in https://github.com/openlayers/ol-mapbox-style/.

a new feature request created

@ahocevar
Can you add layer similar as mapbox? this is mapbox's layer definition:
                     Each feature includes top-level layer, source, and sourceLayer properties. The layer property is an object representing the style layer to which the feature belongs. Layout and paint properties in this object contain values which are fully evaluated for the given zoom level and feature.

with 6.3.0, it works
codesandbox sample

codesandbox,  working sample:
 arcgis Vector tile, hover, highlight
It has problem, not stable, sometime strange thing happen, special for circle feature, not correct, not properly works
Without hover hightlight, seems works fine,


Ensure TitleComponent is fully implemented

Might be missing some settings.

Remaining to implement:
show_platform
show_region
show_variables  (for these three I need a sample Run with them)
display_as_single_line

Those are implemented in the core code


Update dependent sharp package to fix its m1 (arm64) compatibility issue

This is to resolve #106.

@nicolaspanel If possible, can you please merge this in? It works perfectly for me. Thank you!

see #125


chore: add istanbul inline comments

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 100.0%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
568

Relevant Lines:
568

💛  - Coveralls


chore: remove UIWebView comment and variable

Despite it's not needed because it doesn't cause the Apple warnings, as users do text searches they wrongly point to this two references as causing their issues.
So removing them to give people some comfort.
closes #503

:tada: This PR is included in version 4.2.0 :tada:
The release is available on:

GitHub release
npm package (@latest dist-tag)

Your semantic-release bot :package::rocket:

I am really in need of proper advice as it is really high time .. I deployed app on testflight but getting the same deprecation error. After using the grep command I found the Uiwebview text in few binary files as follows : Binary file ./platforms/ios/build/emulator/myApp.app.dSYM/Contents/Resources/DWARF/myApp matches
Binary file ./platforms/ios/build/sharedpch/Bridging-Header-swift_251ZNACTHE039-clang_175V8IMOEYLRY.pch matches
./platforms/ios/build/sharedpch/SharedPrecompiledHeaders/2958374517825372973/myApp-Prefix.pch.d: ...
./platforms/ios/build/sharedpch/SharedPrecompiledHeaders/15754971778278932505/myApp-Prefix.pch.d: ....
Addition to above files I have the text in readme.md & releasenote.md of few plugin which I believe I can directly remove or edit I  could some on plz help me with above binary files ?? Thanks in advance.

@Pratz007-tech Have you upgraded to cordova-ios 5.1.0 (or later) and set the preference WKWebViewOnly to true
in config.xml?  See https://github.com/apache/cordova-ios/pull/715 and https://github.com/apache/cordova-ios/blob/master/RELEASENOTES.md.  You may also need to upgrade plugins such as in app browser but sounds like you may not be using any plugins with references to UIWebView.

Thanks jh-gh , Yes I have one code base with 5.1.1 --> ionic-wbview-plugin installed --> configurations added in config.xml file. When I did grep I got few binary files,nodemodules,plugin's readme & releasenote.md files with 'UIWebView' I archived and uploaded this ipa on testflight which resulted to deprecation error. Now I upgraded to 6.1.1 --> removed the webview plugin --> and did grep command . List of files are as above (i.e Binary files) . Plugins that I have used are as follows : "cordova-plugin-device": "^2.0.3",
"cordova-plugin-file": "^6.0.2",
"cordova-plugin-file-transfer": "git+https://github.com/dpa99c/cordova-plugin-file-transfer.git",
"cordova-plugin-inappbrowser": "^4.0.0",
"cordova-plugin-whitelist": "^1.3.4",
"cordova-sqlite-storage": "^5.0.1",
"org.nypr.cordova.wakeupplugin": "git+https://github.com/Haggus/cordova-plugin-wakeuptimer.git" . Request to please let me know what going wrong. Thanks & Regards,Pratiksha

Now what I got to observe is binary files are not result of plugins . On removing ios platform and doing grep there was  no list of files . On **addition of<EMAIL_ADDRESS>and building the code got the binary file ** as follows. Binary file platforms/ios/build/emulator/myApp.app.dSYM/Contents/Resources/DWARF/myApp matches
platforms/ios/build/sharedpch/SharedPrecompiledHeaders/12830093453981347961/myApp-Prefix.pch.d:  /Applications/Xcode.app/Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/SDKs/iPhoneSimulator1
3.7.sdk/System/Library/Frameworks/UIKit.framework/Headers/UIWebView.h \


handled publishising replacement

together with this, address this

Now I just check if --replace is part the body or not. No need to deserialize it, good call.
I also added two tests for the error cases.


Automated Package Upgrade

:tada: This PR is included in version 7.0.116 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


asn1_d2i_read_bio() fails on short read

I believe I have found a bug in asn1_d2i_read_bio() when a read is shorter than expected.
I found this when I was reading a DER-encoded message from a socket and the server happened to send a packet of four bytes.
The call fails with error:0680007B:asn1 encoding routines::header too long.
Reproducing such a short read from a socket depends on timing and is not reliable, so I found a way to reproduce the issue with just a memory BIO and a creative callback.  Since the actual DER-encoded message doesn't matter, I use a certificate as the message.  The code below assumes a file with a certificate is present.  I tested with the certificate from www.openssl.org.
I found this issue in OpenSSL 3.0.9 on Win64 and I am also able to reproduce this in master.
Let me know if you agree this is a bug.  I was able to work around this issue using a another creative BIO callback, so this is not urgent.
#include <stdio.h>
#include <openssl/bio.h>
#include <openssl/err.h>
#include <openssl/x509.h>
#ifdef _WIN32
# include <openssl/applink.c>
#endif

#define SHORT_READ 4

long shortReadCallback(BIO* b, int oper, const char* argp, size_t len, int argi,
                       long argl, int ret, size_t* processed)
{
    if (oper == BIO_CB_READ) {
        size_t readbytes;
        char buf[SHORT_READ];
        BIO* arg = (BIO*)BIO_get_callback_arg(b);
        BIO_read_ex(arg, buf, SHORT_READ, &readbytes);
        BIO_write_ex(b, buf, readbytes, NULL);
    }
    return ret;
}

/*-
 * Supply a DER-encoded certificate in file "www.openssl.org.der".
 * A certificate is used only as example.
 * The issue is generic to all d2i methods.
 */
int main()
{
    BIO* certbio = BIO_new_file("www.openssl.org.der", "rb");
    if (!certbio) {
        puts("failure reading test input");
        puts(ERR_error_string(ERR_get_error(), NULL));
        return 1;
    }
    BIO* membio = BIO_new(BIO_s_mem());
    BIO_set_callback_arg(membio, (char *)certbio);
    BIO_set_callback_ex(membio, shortReadCallback);
    /* fails with ASN1_R_HEADER_TOO_LONG */
    X509* cert = d2i_X509_bio(membio, NULL);
    if (cert) printf("OK\n");
    else puts(ERR_error_string(ERR_get_error(), NULL));
    return !cert;
}

Quickly looking - in your callback you do not seem to handle the case when len < SHORT_READ, could it be a problem?

Well spotted. That would be an issue but it does not happen.  The method starts by reading 8 bytes, gets only 4, and fails.
I can adjust the test code...

More complete patch:
diff --git a/crypto/asn1/a_d2i_fp.c b/crypto/asn1/a_d2i_fp.c
index 4af2276a8d..97197ec508 100644
--- a/crypto/asn1/a_d2i_fp.c
+++ b/crypto/asn1/a_d2i_fp.c
@@ -142,12 +142,14 @@ int asn1_d2i_read_bio(BIO *in, BUF_MEM **pb)
                 ERR_raise(ERR_LIB_ASN1, ASN1_R_NOT_ENOUGH_DATA);
                 goto err;
             }
-            if (i > 0) {
+            if (i >= 0) {
                 if (len + i < len) {
                     ERR_raise(ERR_LIB_ASN1, ASN1_R_TOO_LONG);
                     goto err;
                 }
                 len += i;
+                if (i < want && !BIO_eof(in))
+                    continue;
             }
         }
         /* else data already loaded */

Thank you for the quick response.
I have applied your patch into my master build.  The test program still fails, but that is probably because my "creative callback" does not intercept the call to BIO_eof().  I will apply the patch to 3.0.9 and use it in the program that had the original issue with the socket.

I have a strong suspicion that supporting short reads here could have unwanted consequences for other existing (albeit perhaps exotic) use-cases.

I agree, that is a risk.  This "creative callback" is an actually an example.
Adding a buffer: I believe the code correctly handles short reads for the contents.  The issue is "just" for reading the header.

I have tested the patch in the program that had the original issue with the socket. Of course I took out my workaround. Even if the first read is short this is now handled correctly, the error "header too long" no longer appears.  Nice work!
Are you going to apply the patch?  Or are you still thinking about adding some kind of buffering?

I'll submit the patch as a PR - I am not sure it should be merged though as it might have unwanted consequences.

This doesn't make sense. In a read-style API, zero is unambiguously EOF. The reason to return a short read is if you have some data available on the stream, but not the full buffer. You don't want to block the call (perhaps that data is never coming), so you immediately return.

This wouldn't make sense if we could be 100% sure that the BIO follows the semantics you wrote. Also the read could be retryable (i.e., EINTR occured on the blocking call) but the current BIO implementations do not properly support BIO_FLAG_SHOULD_RETRY (except for bio_ssl).


[Performance] Add lots of items to the DOM

Hi,
I'm looking for some informations on how to add lots of items to the DOM.
Here's a jsfiddle example.
Note that in this example I'm using a while loop with 2000 items. It makes the browser freeze.
If I use an interval instead, everything works fine.
Now, in my real use case I'm getting about 6600 items through websockets. When an item is received it's added to the view. I'm seeing the same behavior as with my while loop above, hence the browser freeze until everything is done (too fast? not comparable to setInterval(x, 0)?).
On the other hand, if I use vanillaJS, I've no problem adding my elements to the DOM, for example:
const container = document.getElementById('app')
let list = document.createElement('ul')
container.appendChild(list)

//Get some data from a websocket
fetch()
//reactive stream subscribe (most.js)
.observe((e) => {
    let element = document.createElement('li')
    element.innerText = e.text
    list.appendChild(element)
})
.then(() => {
    console.log(list.children.length) // 6600
})

As Inferno is powerful (which you can see through the many benchmarks) I know I'm doing something wrong. Could you please tell me how I can improve the above jsfiddle to be performant enough?
Thanks!

@soyuka Inferno's setState when used in your case will be sync on each call, thus causing it to do a diff each time. You can however force the setState to by async by passing in a callback as the 2nd parameter. In your case, you don't really need a callback, so you can pass in a NO OP function and get much better performance. As shown:
https://jsfiddle.net/r9g44v7m/

Hi @soyuka,
In general, you want to avoid Component whenever you can because functional components are faster (as opposed to "stateful components").
In your case, since you're just passing static/dummy data, there's no need to use or set a state here. Ergo, I remade your fiddle with functional components.

PS: Another way to think of it is that functional components are one-directional; they do not need to send new data or, aside from the first time, remember what they were told to do. (The exception here is that functional components can "send" data if a prop contained a parent's method... technicalities.)

Here's the fiddle: https://jsfiddle.net/lukeed/htegwjeh/
Another major difference is that you were setting state 2000 times. Each call of setState re-renders the tree & all its children. So, that means that by 5th iteration, you were re-rendering 1->4 and on the 1000th iteration, you were re-rendering 1 -> 999 too.
I can provide a 'stateful' example too if you'd like.

Hi, thanks for both of your answers!
It's kinda hard to find docs/examples about inferno, hope the website will be released soon!
I understand the functional vs stateful, didn't found any functional example though. Also, I must say I dislike JSX, so here's your fiddle with hyperscript:
https://jsfiddle.net/htegwjeh/1/
Though, how would you render the children in an asynchronous way? I don't think that the children arguments accepts a Stream/Observable nor a Promise?

@lukeed  you are comparing one render vs 2000 renders, also using class in given scenario shouldn't make any noticeable difference because there is only 1 class constructed

I created jsfiddle with functional components resulting same as bad performance as with classes.
https://jsfiddle.net/htegwjeh/2/
and now it cannot even be async anymore? (according to my knowledge).
There is no silver bullet to get best performance. It highly depends on usage and requirements

@Havunen thanks for the second example, interesting that indeed it cannot be async anymore (according to you knowledge).
@trueadm Thanks about the setState tip! Works great (even better then my poor vanillajs implementation)
The slowest uses the above vanillajs implementation:

!

@Havunen Correct. I learned something new after looking at @trueadm's answer 😄


Unable to enablemps

Thank you for putting this together.
Testing on a MAC M2 and was not able to enablemps
Also needed to do a pip install cchardet

let me know if not trying correctly

I'm sorry this really was a bug, fixed in the latest update v0.4.7 today, please update.
Bark is not using cchardet AFAIK but perhaps this is needed for Gradio on Mac 🤷


Add Postgres Extension for Geolocation of Location table

Elixir Package: https://github.com/bryanjos/geo
Elixir Package: https://github.com/bryanjos/geo_postgis
Postgres Extension: http://postgis.net/

Preferiblemente que todo las respuestas sean GeoJSON: http://www.postgis.net/docs/ST_AsGeoJSON.html

@yordis what exactly is the end goal with the feature. Depending on what you want to store you need different types on your migrations for geodata.
Simple point-like geo features use the st_point type which I'm sure geo_postgis has it defined. For more complex types you need to use either the generic Geometry type or specifically Polygon or Multipolygon.
Once you have the migration in place, you can store geodata from multiple input sources, for example you could use ST_GeomFromGeoJSON to import geojson data directly into the db, and output it directly as geojson with ST_AsGeoJSON

@CamonZ right now we need the st_point for the location that will represent the lan,lon of the it


Marker gene symbols have different styles depending on their experiment in cell type heatmap with metadata wheel

Marker genes derived from some experiments (e.g. E-ENAD-15, E-EHCA-2 that I've noticed so far) have gene symbols shown in different style (only first letter is upper case) compared to genes from other experiments (all caps)
Therefore e.g. in the pancreatic PP cell marker genes heatmap a gene is shown with a symbol Ppy in the first section of the cell type marker gene heatmap and with PPY in the rest of it (even though both point to the same gene ENSG00000108849)

It really depends if we want gene symbol search to be case-insensitive. I don’t know if this can have nefarious consequences. Again, it’s something that I think we should discuss.


Unexpected  in GraphQL request

When going through the Question Answer example.
with the following toml:
[stepzen.cli]
endpoint = "wxflows-genai/Name"

[wxflows.deployment]
# Example flows.
flows="""
    // myPrompt = ragAnswerInput | topNDocs | promptFromTopN | ragInfo
    myRag = ragAnswerInput | topNDocs | promptFromTopN | completion(parameters:myRag.parameters) | ragInfo
    // myRagWithGuardrails = ragAnswerInput | topNDocs | promptFromTopN | completion(parameters:myRagWithGuardrails.parameters) | ragScoreInfo | hallucinationScore | ragScoreMessage | ragInfo
"""
ai_engine = "WATSONX"

[wxflows.deployment.source.aicore]
# RAG configuration
collection="ColName"
tsv_files = ["OwnSample.tsv"]
embedding_model="ibm/slate-30m-english-rtrvr"
data_type = "md"
data_directory = "./OwnSampleMds"
chunk_size = 500
chunk_overlap = 50
documentstore.type="milvusmt"

It's throwing the following Syntax Error:
wxflows collection deploy

Found flow definition in the configuration

Provisioning the watsonx.ai flows engine environment
Published flow myRag to https://***/wxflows-genai/***/graphql in 4.154s
Deploying the wxflows-genai/OwnSample endpoint... done

Creating or updating the KubevirtDocs1 collection
Using https://***/wxflows-genai/***/graphql for uploading into search engine type: milvusmt

Error: An error occurred while uploading data: Syntax Error: Unexpected <EOF>.

GraphQL request:1:1
1 |
  | ^

Hello @Davo911 is your issue resolved?


Add 'Host' header value to 'hostname' in rule message field, if exists

In case of libmodsecurity3 in the generated message the hostname field always contains the server's IP address.
I had a quick look at how it works in mod_security2 and if the request has a "Host" header it's there, otherwise the server IP is placed.
This field is important, because it shows what was the Host header of the request.
Normally Nginx's log contains the host: ... part, but in some very special cases, when the previous request: ... part is too long, the host part isn't there, because Nginx truncates the log line after 2048 bytes. If a user wants to avoid it, then he needs to recompile the whole Nginx. But in many cases, it's not possible.
With this patch we can provide (almost in all cases) that hostname will be presented.

Is there any question about this PR? We need this patch in our servers.
Please let me know, if any discussion is necessary.

The 'Host' header is untrusted user input. Which means it could be misleading to use it to populate report fields that are not pretty explicitly identifiable as such.

I see your argument, but I think most data in error log are some user input (this is why I sent this PR earlier).
As I described in my first comment, in some cases the error log can be longer than the allowed 2048 bytes, and the hostname field will miss from there. This is a huge problem, because we just see the (local) IP address of the server.
Also I described that with this patch the behavior will be the same as in case of Apache (and mod_security2). For eg. take a look to this request:
GET /dump.php HTTP/1.1
Host: ' UNION SELECT username, password FROM users--
Accept: */*
User-Agent: Mozilla/1.0

In case of Apache, I see this:
[tag "reporting"] [hostname "' union select username, password from users--"] [uri "/dump.php"]

In case of Nginx (with the patched version):
[accuracy "0"] [tag "anomaly-evaluation"]  [hostname "' UNION SELECT username, password FROM users--"] [uri "/dump.php"] [unique_id "168718507414.966399"] [ref ""], client: ::1, server: _, request: "GET /dump.php HTTP/1.1", host: "' UNION SELECT username, password FROM users--"

Please note, that the untrusted user input is already in the log by Nginx, but not in the correct place.
What do you think if I would sanitize this value (as I did in the PR #2854 with other fields)?

Hi @airween ,
My concern was not primarily about any content that might resemble a generic attack (like SQLi or XSS), but, rather, input that looks like a legitimate hostname, but is not the hostname servicing the request.
For example, suppose a request is being serviced by mysiiitemain.com, but the 'Host:' header actually has the false value mysiiitesub.com?
Would it really be a good idea, in this case, for the error.log to claim: hostname: mysiiitesub.sub?

that looks like a legitimate hostname, but is not the hostname servicing the request.

Sorry, now I'm confused a bit - if the given hostname not configured in the server, then it really does not matter what is that, server will server the default config. It's like a request without Host header (more or less). (But correct me please if I'm wrong).

Would it really be a good idea, in this case, for the error.log to claim: hostname: mysiiitesub.com?

Yes, definitely! That's what we need, it's very informative and useful information. We know which virtualhosts are configured, and if we don't have any context with that name, then we shouldn't care about that request (in point of false positives).

I'm afraid I don't follow your line of reasoning.
My main concern is twofold:

there is nothing in the output that suggests 'hostname:' is unreliable; indeed the surrounding information (file, line, id, unique_id, etc.) suggests that it is not a client-manipulatable value
I don't see the positive use case where this untrusted data is safe to use for decision making

You state: "We know which virtualhosts are configured, and if we don't have any context with that name, then we shouldn't care about that request (in point of false positives)."
I don't follow. It could be the case that both the the true host and the false host in the 'Host:' header both represent hosts being protected by ModSecurity -- maybe one is of lower concern (like a host that serves only static content, while another is an administration portal).
In addition to the wariness I've outlined above, it should be noted, that if a particular installation wants the value of the 'Host:' header in output:

as you noted, they already have it (barring truncation, see below) by default
truncation issues are largely under the control of the administrator anyway; truncation can often be eliminated by managing the output items that are requested in the rule (for example, by reducing the number of 'tag' actions)
if that is still a problem, the user may add their own 'msg' action to rules to specifically output the value of the 'Host:' header

there is nothing in the output that suggests 'hostname:' is unreliable; indeed the surrounding information (file, line, id, unique_id, etc.) suggests that it is not a client-manipulatable value

you mean with current behavior there is nothing which suggests the hostname is unreliable? I agree, but now it does not have any information... (I know what's my server's address :), it's unnecessary to show again.). Now it's a worthless information.

I don't see the positive use case where this untrusted data is safe to use for decision making

This untrusted data is in Apache's error.log, and is in Nginx error.log - but unfortunately sometimes it's truncated and does not visible. But it's an important information.
I think the administrator can decide that value is trusted or not - and this is the point.

I don't follow. It could be the case that both the the true host and the false host in the 'Host:' header both represent hosts being protected by ModSecurity -- maybe one is of lower concern (like a host that serves only static content, while another is an administration portal).

Wait: if both hosts being protected by ModSecurity, then why is fake one of them? If ModSecurity protects a configured website, it means that hostname is not fake... Or - sorry, but - I don't see your argument here now.

as you noted, they already have it (barring truncation, see below) by default

yes, but in case one of our customer, about the 20% of total lines (above 300k per day) is truncated. The customer has about 200 virtual hosts.

truncation issues are largely under the control of the administrator anyway; truncation can often be eliminated by managing the output items that are requested in the rule (for example, by reducing the number of 'tag' actions)

First of all, unfortunately this would mean that the administrator should modify the whole rule set. Sorry to say but that makes no sense. (What about after an upgrade? Admin does it again?)
Secondly, the part of ModSecurity error log is limited to 1024 bytes. Tags can use a hundred bytes in extreme cases, then we would win 100 bytes - but I'm talking about few hundred bytes. Total length of Nginx error log is limited in 2048 bytes. The prefix (date, severity, pid) is maximum 50 bytes. Now we are at 1074 bytes. Now imagine that the URI is longer than the remained 974 bytes. The total URI is typically more than 1k - removing tags is not a solution.

if that is still a problem, the user may add their own 'msg' action to rules to specifically output the value of the 'Host:' header

again: really does need the admin to modify the whole rule set and append an extra value to each rule? Instead of replacing a completely useless field value with a useful one?
Here the untrusted as a marker IS THE information.

A similar opinion like mine:
https://github.com/corazawaf/coraza/pull/517#issuecomment-1327821016

"Now it's a worthless information."
Perhaps. But showing no information is almost always better than showing incorrect or misleading information. The same is true for showing information of low utility over against incorrect or misleading information.
And, is it really useless? It may be if there is only a single server IP address involved, but that may not be the case. And if the logs are aggregated somewhere, perhaps some admins would value having a reliable IP address in that field
more than an entirely untrusted string.
"This untrusted data is ... in Nginx error.log"
You mean in the item called "host: ..." after the request? Yes, there is potential for that to be misunderstood as well, but I think less so; at least its name ('host') corresponds directly to a request header, so perhaps people will more easily where it is sourced from.
"I think the administrator can decide that value is trusted or not - and this is the point."
But that presupposes the administrator (even a novice one) has knowledge of how it works. ModSecurity can already involve a lot to learn, and it's generally undesirable to make things harder by assuming even more background knowledge.
"the administrator should modify the whole rule set. Sorry to say but that makes no sense. (What about after an upgrade? Admin does it again?)"
I'm not sure I understand your concern here. ModSecurity includes many tools to modify rulesets for particular needs. In a case like this, for example, one option could be to simply make a change to SecDefaultAction to add something like
tag:'Host-Hdr: %{REQUEST_HEADERS.Host}' . Every rule would not need to modified individually. (Keep in mind that this is simply a possible workaround for those individuals for whom seeing the 'Host:' header value early in the error.log output is a high priority.
More generally, the information in error.log is, by necessity, terse. It seems likely that there are many pieces of information that are valuable to at least some admins but are not contained in that log. The most usual source for more complete info is the audit log.

showing no information is almost always better than showing incorrect or misleading information.

I can't agree with that. If a user sends a fake Host header, that's not an incorrect information - that's THE information, what we need.

perhaps some admins would value having a reliable IP address in that field more than an entirely untrusted string.

Perhaps. Perhaps it would like to see the real request from users. We're just guessing now :)
(Btw Nginx's error.log contains the server field, so administrator can access that information. And that's is before the request field, so it is sure that not truncated, like the host)

But that presupposes the administrator (even a novice one) has knowledge of how it works.

You are right. But what if someone uses both mod_security2 and libmodsecurity3? Now these engines produce different outputs. Doesn't this confuse the user?

to simply make a change to SecDefaultAction to add something like tag:'Host-Hdr: %{REQUEST_HEADERS.Host}'

Sorry, I'm not sure I can follow you. Above you wrote that we should remove tags from rules, then we can make shorter lines. I explained why it is not  a solution (removing tags). If we append a new tag, then in our special cases that will the first what the engine truncates.

More generally, the information in error.log is, by necessity, terse. It seems likely that there are many pieces of information that are valuable to at least some admins but are not contained in that log. The most usual source for more complete info is the audit log.

I would dispute that. First, there are very few cases where we need the audit.log, the error.log is more than enough. Secondly if user follows the default audit.log settings (SecAuditLogRelevantStatus "^(?:5|4(?!04))") that log contains only the rejected requests. If the user use CRS in anomaly scoring mode, the requests with scores below the threshold won't appear in audit.log.
Error.log is good enough.
==%==
I'm afraid our positions are not close to each other, so would it be acceptable if I added some code and the user could choose this feature at compile time? I mean there would be an option for ./configure script, eg.:
./configure --enable-host-header-in-log

and in that case the engine will follow this mechanism, otherwise this code has no effect?

Hi there,
I personally see valid reasonings on both sides. What I'm wondering is, would it be possible to just keep both of them (hostname and Host header) in the error log?
Something like:
[Mon Jun 19 ...] [security2:error] [pid 60:tid<PHONE_NUMBER>4440] [client <IP_ADDRESS>:55555] [client <IP_ADDRESS>] ModSecurity: Warning. [file "..."] [line "..."] [id "..."] [msg "..."] [ver "..."] [tag "modsecurity"] [tag "anomaly-evaluation"] [hostname "<IP_ADDRESS>"] [uri "/"] [host "evillocalhost"] [unique_id "..."]

I see that it would lead to an increased verbosity, but it seems that host is just like like uri, a meaningful part of the request, and somehow it would also make libmodsecurity3 error logs as complete (actually more) as mod_security2.
As a side note, FYI, there are some ongoing discussions around it also in Coraza (Which currently is just providing the IP address, just like libModSecurity):

https://github.com/corazawaf/coraza/pull/517
https://github.com/corazawaf/coraza-caddy/issues/75

No, I don't think making the behaviour helps meaningfully.
I'm going to go ahead and close this for the reasons stated.

No, I don't think making the behaviour configurable helps meaningfully.

And what do you think about @M4tteoP's suggestion? Adding an extra field to the line?


Allow setting input text field font

Customize token font and input text field font.

:+1:

did this ever get merged?

Nope. There would be a purple MERGED icon instead of green OPEN.

When can this get merged?

Please merge this.


Fix client package issue

Now, it is ok to import client package with idlFactory and SERVICE type

Codecov Report

Merging #142 (36e7e50) into main (16fc531) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main     #142   +/-   ##
=======================================
  Coverage   85.06%   85.06%
=======================================
  Files          54       54
  Lines        5150     5150
=======================================
  Hits         4381     4381
  Misses        769      769

Continue to review full report at Codecov.

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


Yuzu seems to crash when loaded through Daijishou

I am using Android 13 on S23 Ultra.
It seems to be crashing when Yuzu is selected as player (Skyline works just fine).

Having the same issue, it launches yuzu rather than launching the rom

I have the same issue, and the same happens with Yuzu Early Access. I assume the configuration for launching the emulator is wrong, but couldn't find the correct way of doing it.

I am using Android 13 on S23 Ultra.
It seems to be crashing when Yuzu is selected as player (Skyline works just fine).

Have you tried launching yuzu on a different Frontend? This could be an issue related to Yuzu, not Daijisho. Something similar happens with official dev and beta builds of Dolphin emulator.
Please try launching a yuzu game on a different frontend and reply with results. Make sure Yuzu is not running in the background before launching the game through a frontend.


Clear out empty object metadata if it exists after conversion

Description of your changes

Builds on https://github.com/crossplane/function-sdk-go/pull/70
Without this change any resource that has no ObjectMeta will end up with an empty metadata (like "metadata": {}) when rendered. This is because json serialization adds the generation field. We then delete it, resulting in an empty metadata object.
This isn't actually so bad because Crossplane will always add a few labels, owner refs, etc before the metadata becomes part of the SSA fully-specified intent. So in reality we'll never ask the API server to make metadata an empty object. It is misleading in unit tests though.
I have:

[x] Read and followed Crossplane's contribution process.
[ ] Run make reviewable to ensure this PR is ready for review.

How has this code been tested

It is misleading in unit tests though.

To elaborate, I mean that if you write a function that calls composed.From on an MR struct with no ObjectMeta and add unit tests, your unit tests are going to show you that the resulting composed resource has the structpb.Struct equivalent of "metadata": {}.


go fmt

Coverage remained the same at 92.453% when pulling 2de4e9fc73da09dba767ebced5284416a5bd3a23 on SchulteMarkus:master into 7ceb900c37ac44d9abc444eda048d6bbccd3cba0 on tarent:master.


Snyk build failing

Please see the following build and it's failing travis log:
https://github.com/Midburn/spark/pull/650

Now it's passing :(


MultiVolumeWorks prompt to copy state and visibility changes to members.

Fixes #721

Coverage decreased (-0.1%) to 99.642% when pulling ee51d774ec50783b0727e1fd7a16cf0c312ed419 on cascading-permissions into 31bbed381d592b06468a94b46ecc1e0990964ad4 on master.


Update High Priority Tooltip Text

Feature Description
Tooltip text that is seen on publish button hover/focus should be updated from:
[For priority issues]: Make updates before publishing to improve discoverability and performance on search engines
to
[HUGE TO PROVIDE]
Acceptance Criteria
Tooltip text is updated.

@BrittanyIRL should we close this? Huge is no longer on the project, so if this wasn't provided, we should just... close and reevaluate when we have a designer looking at this again.

@o-fernandez  Sounds great to me!


AIP-132/158: Disallow field_behavior = REQUIRED on standard pagination fields

The page_size and page_token fields must not be annotated with field_behavior = REQUIRED. In order to initiate a List iterator, a page_token will not be present, so it cannot be required. page_size has strong language for the support of a server default value, so this must not be required either.
We may want to also add an item to AIP-158 that states each of these fields "must not" be annotated as REQUIRED.

AIP-158 has been updated. So we can now enforce this from the AIP-158 linter rule set.


Is this bundle still maintained ?

Hello @avanzu ,
Is this bundle still maintained ?
I have the feeling that PR & issues stays without response ?

I think so as it works well

Ok, just asking, because I see some PR and issues without response for a while.

Oh yes , the forum is far from being dynamic

well... maintained with a grain of salt (or two) but we're working on it, as it seems.


License?

Which license is the handbook using?

Hi @jb33k , we have added one: https://github.com/dOrgTech/Handbook/blob/master/LICENSE.txt


CORS + APACHE + PHP

Congratulations on the project. But someone has a concrete example that works with CORS? apache + php + win7? I found this example http://colonelpanic.net/2014/08/using-pdf-js-web-worker-cross-domain-cors/ but was unable appears error: XMLHttpRequest can not load http://www.education. gov.yk.ca/pdf/pdf-test.pdf. In the 'Access-Control-Allow-Origin "header is present on the requested resource. Origin 'http: // localhost: 8080' is not allowed Therefore access.
TKS

Please refer to https://github.com/mozilla/pdf.js/wiki/Frequently-Asked-Questions#faq-xhr. As outlined there, this is out of scope of the PDF.js project.


Pattern matching cannot detect abnormal matches

source code:
actor {
    let ?a = null;
    public func greet() : async Text {
        ""
    };
};

build error:
Building canisters...
The build step failed for canister 'rwlgt-iiaaa-aaaaa-aaaaa-cai' with an embedded error: The command '"/Users/flyq/.cache/dfinity/versions/0.8.4/moc" "/Users/flyq/workspace/test/motoko_compile_error/src/motoko_compile_error/main.mo" "-o" "/Users/flyq/workspace/test/motoko_compile_error/.dfx/local/canisters/motoko_compile_error/motoko_compile_error.did" "--idl" "--actor-idl" "/Users/flyq/workspace/test/motoko_compile_error/.dfx/local/canisters/idl/" "--actor-alias" "motoko_compile_error" "rwlgt-iiaaa-aaaaa-aaaaa-cai" "--package" "base" "/Users/flyq/.cache/dfinity/versions/0.8.4/base"' failed with exit status 'exit status: 2'.
Stdout:

Stderr:
OOPS! You've triggered a compiler bug.
Please report this at https://github.com/dfinity/motoko/issues/new with the following details:

Motoko 0.6.11 (source csnk04rs-29ns9vgd-y6hkbsaj-hysj0ghq)

Fatal error: exception Invalid_argument("Type.as_opt")
Raised at Mo_types__Type.invalid in file "mo_types/type.ml", line 357, characters 16-54
Called from Mo_frontend__Coverage.match_pat in file "mo_frontend/coverage.ml", line 217, characters 13-35
Called from Mo_frontend__Coverage.check_cases in file "mo_frontend/coverage.ml", line 353, characters 20-71
Called from Mo_frontend__Coverage.check_pat in file "mo_frontend/coverage.ml", line 363, characters 4-80
Called from Mo_frontend__Typing.coverage' in file "mo_frontend/typing.ml", line 174, characters 29-34
Called from Mo_frontend__Typing.coverage_pat in file "mo_frontend/typing.ml" (inlined), line 187, characters 2-69
Called from Mo_frontend__Typing.check_pat_exhaustive in file "mo_frontend/typing.ml", line 1712, characters 4-38
Called from Mo_frontend__Typing.infer_dec_valdecs in file "mo_frontend/typing.ml", line 2437, characters 14-49
Called from Mo_frontend__Typing.infer_block_valdecs.(fun) in file "mo_frontend/typing.ml", line 2410, characters 19-44
Called from Stdlib__list.fold_left in file "list.ml", line 121, characters 24-34
Called from Mo_frontend__Typing.infer_block_valdecs in file "mo_frontend/typing.ml", line 2409, characters 4-166
Called from Mo_frontend__Typing.infer_block in file "mo_frontend/typing.ml", line 2078, characters 14-42
Called from Mo_frontend__Typing.infer_obj in file "mo_frontend/typing.ml", line 1973, characters 17-40
Called from Mo_frontend__Typing.infer_exp' in file "mo_frontend/typing.ml", line 857, characters 10-29
Called from Mo_frontend__Typing.infer_exp in file "mo_frontend/typing.ml" (inlined), line 841, characters 2-31
Called from Mo_frontend__Typing.infer_exp'' in file "mo_frontend/typing.ml", line 1248, characters 12-31
Called from Mo_frontend__Typing.infer_exp' in file "mo_frontend/typing.ml", line 857, characters 10-29
Called from Mo_frontend__Typing.infer_exp in file "mo_frontend/typing.ml" (inlined), line 841, characters 2-31
Called from Mo_frontend__Typing.infer_exp_promote in file "mo_frontend/typing.ml", line 847, characters 10-27
Called from Mo_frontend__Typing.infer_exp'' in file "mo_frontend/typing.ml", line 1256, characters 13-39
Called from Mo_frontend__Typing.infer_exp' in file "mo_frontend/typing.ml", line 857, characters 10-29
Called from Mo_frontend__Typing.infer_exp in file "mo_frontend/typing.ml" (inlined), line 841, characters 2-31
Called from Mo_frontend__Typing.infer_dec in file "mo_frontend/typing.ml", line 2118, characters 4-21
Called from Mo_frontend__Typing.infer_block in file "mo_frontend/typing.ml", line 2091, characters 10-55
Called from Mo_frontend__Typing.recover_opt.(fun) in file "mo_frontend/typing.ml", line 78, characters 55-60
Called from Mo_frontend__Typing.recover_with in file "mo_frontend/typing.ml", line 77, characters 56-59
Called from Diag.with_message_store in file "lang_utils/diag.ml", line 82, characters 10-13
Called from Pipeline.infer_prog in file "pipeline/pipeline.ml", line 168, characters 10-37
Called from Pipeline.check_progs in file "pipeline/pipeline.ml", line 188, characters 22-39
Called from Pipeline.load_progs in file "pipeline/pipeline.ml", line 369, characters 16-40
Called from Diag.bind in file "lang_utils/diag.ml", line 32, characters 27-30
Called from Diag.bind in file "lang_utils/diag.ml", line 32, characters 27-30
Called from Diag.bind in file "lang_utils/diag.ml", line 32, characters 27-30
Called from Pipeline.generate_idl in file "pipeline/pipeline.ml", line 448, characters 27-71
Called from Moc.process_files in file "exes/moc.ml", line 145, characters 24-53
Called from Moc in file "exes/moc.ml", line 214, characters 4-23

The following code can compile and run normally:
actor {
    let b = ?"test";
    let ?a = b;
    public func greet() : async Text {
        a
    };
};

This bug was fixed in 0.6.13/14, as part of the changes to checking patterns. You should now see:
stdin:2.9-2.11: warning [M0145], this pattern of type
  Null
does not cover value
  null

and then get a runtime error due to the failed pattern match.
Please don't hesitate to reopen this bug if you still encounter it in recent Motoko versions.


Generate a highlighting-only slideshow ?

Hello, hello,
Is there any way to have the slideshow generated when only the highlighting screenshots are taken?
Here is my local.properties:
gwen.web.capture.screenshots=false
gwen.web.capture.screenshots.highlighting=true

This way the screenshot generation overhead is limited, capturing only key moments. The screenshots are then available individually as step attachments, but the whole slideshow is not.
The slideshow could be generated if any screenshot is captured, couldn't it?

@dfriquet Done and released in version 2.50.0

Lightning speed, as usual :zap:
Thanks a lot!


Imported glTF meshes always use the Disabled cull mode by default, which is problematic for meshes with negative scale

Godot version
3.4.3
System information
Windows 10, GLES3, Geforce GTX 1070, driver 471.11
Issue description
When mirroring a MeshInstance (scale -1,-1,-1) with a mesh and a material. The light falling on it is inverted

Steps to reproduce
Including simple project that shows this very well. The light is wrong for all types of light, enviromental, directional, spot and omni light.
Minimal reproduction project
mirror_mesh_bug.zip

Duplicate of https://github.com/godotengine/godot/issues/39936 (same cause).
This is because glTF materials are imported with their cull mode set to Disabled by default, which enables double-sided material rendering and breaks on inverted meshes. To fix this, set the Cull Mode to Back on the SpatialMaterial (which is the default on materials other than imported glTF materials).
For reference, this also happens with the FBX importer: https://github.com/godotengine/godot/issues/42294

I dont know if this is the same thing but if i have double sided meshes the setting cull mode to back makes it look very wrong

setting it to Front makes the light go wrong on the inverted mesh

So complex meshes with multiple sides doesnt seem to work for this.

setting it to Front makes the light go wrong on the inverted mesh

Try enabling Ensure Correct Normals in the SpatialMaterial's Flags section.

Double-check if your mesh normals are configured correctly in Blender. Are they pointing outward as expected?

Double-check if your mesh normals are configured correctly in Blender. Are they pointing outward as expected?

I will check ASAP. My initial test looks like it will work, the inside normals might need to point inward though. But the normals seems to be the culprit!

@Calinou Yes! it was the normals!

Closing, as this is actually an issue with the mesh normals and not a rendering issue within Godot.


pub upgrade generates wrong symlink in sample if sample has it's own pubspec.yaml

I think there is still a problem in Analyzer - it has problems with standalone samples. You can see here what I mean with "standalone": https://goo.gl/qeb42u Each sample lives in it's own universe with it's own pubspec.yaml. The only connection to it's parent lib is through something like this: https://goo.gl/R2VqcZ
I borrowed this idea from the Angular guys and it's much more flexible than the default way. (default way = share base pubspec with sample pubspec)
Today I switched back to IntelliJ IDEA (Cassiopeia) IU-141.2552.1
Build #IU-141.2552, built on August 27, 2015
JRE: 1.6.0_65-b14-462-11M4609 x86_64
JVM: Java HotSpot(TM) 64-Bit Server VM by Apple Inc.
(back from IJ 15 EAP)
and made a pub upgrade for my MDL/Dart lib and it generated a package for every sample back to it's parent - this is wrong if the sample has it's own pubspec.yaml!
I think this problem is somehow related to #24238

Sub-projects are just not supported by pub. This is known behavior and they don't intend to change it.
A workaround is to not name the folder example (nor like any other of the known pub top-level directories). example_ works well for me.
I guess this will become a non-issue anyway when the packages folder and symlinks are gone.

See for example #23296

Thanks @zoechi - I'll try your approach. I'm happy if it works but I find the solution still annoying.  The rule should be not so complicated to implement. If a project has it's own pubspec treat it as extra project.
I'm not sure if it's possible to get rid of the packages folder at all. I think we need one but only ONE packages folder per project. Otherwise it becomes impossible for other tools like e.g. SASS to work with dart libs. Or take a simple webserver - it fails with the current (1.12) .packages approach. This approach needs transformers - if you can't use a transformer you will fail.

@MikeMitterer tell me about it ;-). My current approach (example_ directory) works well enough though and I'm satisfied, but yes, it's not perfect.
Again I'm pretty sure this issue will be solved when the packages symlinks are gone, even when a packages directory per project remains (which I hope won't be necessary).

;-) I cross my fingers an hope the best! In the meantime I moved my example to samples and started a new indexing session...


Reloading a vector source when URL changes

Hi,
following Bart's recommendation I open this ticket so the issue can be commented.
It starts with https://groups.google.com/forum/#!topic/ol3-dev/PjFBy5mxwgo and https://groups.google.com/forum/#!topic/ol3-dev/H6tZaFUUO4E topics on the forum.
Once a vector layer with its source pointing to some URL is created, there is no way to update the layer (really the source) content other than loading, cleaning and adding new features by hand.
Although manually loading is the most flexible option, I think it is a bit confusing. I a user loads data initially setting an url property, why we need to load content manually if we want update the source?
It could be easy to have a setUrl() that updates the urlproperty and invokes the loadFeaturesFromURL() method.
Any opinions?
PS: I offer as voluntary to make the code changes. But I don't know when I have enough free time :)

Want to back this issue? Place a bounty on it! We accept bounties via Bountysource.

I ran into this issue and it appears that all is now necessary is:
function reload() {
       var geojsonFormat = new ol.format.GeoJSON();
	vectorLayer.setSource(new ol.source.Vector({
		url: '/my/urlhere,json',
		format: geojsonFormat
	}));
}

I found that calling clear() causes a re-fetch of the remote resources, so the above would load the data twice?

@akrherz note that setting a url and format on the vector source is not mandatory, you can do things  manually if you want to fully control the behavior of your vector source. This is what I would use:
function loadSource(source, url) {
  $.ajax(url, function(response) {
    var geojsonFormat = new ol.format.GeoJSON();
    source.clear(true);
    source.addFeatures(geojsonFormat.readFeatures(response));
  });
}

var vectorLayer = new ol.layer.Vector({
  source: new ol.source.Vector()
});

// initial loading of the vector source
loadSource(vectorLayer.getSource(), initialUrl);

@elemoine when I call source.clear(true); in your example, this causes the source to load the data.  So the code example loads the data twice.

@akrherz in my example the source does not have a url so I don't understand how clear could load the source. What am I missing?

@elemoine I am unsure what to say, when I try your code example in my app (no public access) and simply call vectorLayer.getSource().clear(true); on the chrome devel console, this single action causes the app to refetch the geojson data from the server.

I'd need to see your code.

@elemoine if it does not do this when you try it, it likely means I am doing something wrong.  It isn't worth your bother.  Thanks for the responses and work on openlayers.

Hello. I faced with the same problem.
How use this in ol.source.ServerVector with bbox?
When i call clear() it consumed a lot of resources.

What ol3 version do you use? Note that ServerVector was removed in 3.5.

Oh, I used the last version (v3.2.1).
As I understand the new version does not have this problem?
Then I will update the version of the library, and use an existing solution.
Thank you.


Musescore badge needs some fixing + musescore 4 badge variant

Which badge would you like the changes to be applied to?
The Musescore badge.
What fix would you like to see applied?
Make the "mu" smaller so it isn't touching the circumference of the blue circle.
Provide any preferred icons/text (icons must be SVG)
The musescore repo doesn't contain any SVGs of the musescore 3 or 4 icons so chances are you'll have to trace them and turn them into SVGs.
Example if needed
Musescore 3 icon: https://github.com/musescore/MuseScore/blob/3.6.2/assets/musescore-icon-round-1024.png
Musescore 4 icon: https://github.com/musescore/MuseScore/blob/master/share/icons/AppIcon/MS4_AppIcon_1024x1024.png

how about this

also, ill just update the current badge as it's easier to manage

how about this

looks pretty good, sorry about replying late as i was at school


Provide an iterator over the event loops of an EventLoopGroup

Provide an iterator over the event loops of an EventLoopGroup
Motivation:
We might want to do certain initialisations on a per-event loop basis. Example: initialising ThreadSpecificVariables. It would be handy to have an iterator over the event loops in an event loop group. See #497
Modifications:
Added a new public API class EventLoopGroupIterator implementing sequence. The challenges in making EventLoopGroup itself a sequence have been mentioned here: https://github.com/apple/swift-nio/issues/497#issuecomment-402107940
Result:
Something like this is possible:
let eventLoopGroup = MultiThreadedEventLoopGroup(numberOfThreads: System.coreCount)`
for eventLoop in EventLoopGroupIterator(for: eventLoopGroup) {
    //do something
}

Your current implementation heavily relies on the underlying implementation of MultiThreadedEventLoopGroup and it cannot be guaranteed that other implementations of EventLoopGroup actually implement next() in a similar way. I talked to @weissi already today about this implementation. What do you think about something along these lines?
public struct EventLoopIterator: Sequence, IteratorProtocol {
    public typealias Element = EventLoop
    private var eventLoops: IndexingIterator<[EventLoop]>

    internal init(_ eventLoops: [EventLoop]) {
        self.eventLoops = eventLoops.makeIterator()
    }

    public mutating func next() -> EventLoop? {
        return self.eventLoops.next()
    }
}

public protocol EventLoopGroup: class {
    // ....
    func makeIterator() -> EventLoopIterator
}

extension EventLoop {
    public func makeIterator() -> EventLoopIterator {
        return EventLoopIterator([self])
    }
}

extension MultiThreadedEventLoopGroup {
    public func makeIterator() -> EventLoopIterator {
        return EventLoopIterator(self.eventLoops)
    }
}

@FranzBusch What makes you think this isn't safe? EventLoopGroup is a class-bound protocol, as is EventLoop, so it seems reasonable to me that this iterator should be safe across all possible groups.

@Lukasa on the one side I was getting at your last point, but further more I was going that with this implementation one is reliant that the next function from EventLoopGroup is implemented in such a way that between two ELs every other is returned. So what if there is an eventloopgroup that returns a random Loop as the next one. I hope that makes sense what I’m getting at.

@FranzBusch Thanks! Yeah, you make an interesting point. The only thing that EventLoopGroup.next() promises is that it returns the next EventLoop to use. So we may have an implementation that always returns the same event loop, or as you say, a random event loop. Makes sense to move the iterator implementation into the EventLoopGroup implementation. I'd like to know @Lukasa 's opinion on this understanding.

It's certainly possible to implement next() that way.
Note that moving the implementation to EventLoopGroup will force this to be semver major.

I think we really shouldn't implement the Iterator with the assumptions of the current next() implementation from MultiThreadedEventLoopGroup. Sadly this will require a semver major, but I think we have a more flexible implementation for future EventLoopGroups.

Note that moving the implementation to EventLoopGroup will force this to be semver major.
@Lukasa Does that simply mean we'd need to wait for swift-nio 2, whenever that's decided, to release this? I'd be okay with that.

Yup, that's what it means :)

Incidentally, we could still add the implementation to MultiThreadedEventLoopGroup and make that public, so you can still get the needed effect in your code today. We just can't make it a protocol requirement.

@Lukasa @FranzBusch What we could do is to make the protocol requirement such that it returns an optional EventLoopIterator (and make it non-optional in NIO 2). For MultiThreadedEventLoopGroup we can still implement it non-optional and we'll provide implementations for all currently known EventLoopGroups.

@weissi what benefit would adding a optional over a non-optional protocol requirement make? Doesn‘t adding a new requirement to any public protocol require a semvar major?

@FranzBusch not if we can ship a default implementation for the new requirement. That's why I propose to make it optional (default implementation just has func makeIterator() -> EventLoopIterator? { return nil }) which means that all existing EventLoops conform automatically.

I'm ok with that.

@normanmaurer ^^

@weissi Thanks for clearing that up. Just thought that adding any new public method to a protocol would require a major but makes sense that it doesn't.

@FranzBusch & @pushkarnk do you want to collaborate on a PR that implements that?

@weissi sure, I'll be glad to give it a shot!

@FranzBusch I guess, the implementation will mostly be based on your code from this comment. It'd be great if you do the PR. We can close this one then.

@pushkarnk Sure, I will open a PR sometime during this weekend.

Closing this PR. We have #509 opened.


High-contrast mode: Dashboard icons are hard to see and should use link text color

This is a bug specific to Windows high-contrast mode. cc @kbayliss who did the testing for this. Details from his report:

Icons have a low opacity which makes them difficult to see on dark backgrounds.
Current: opacity: .2; color: #fff
Proposed: opacity: 1; color: LinkText
Current:

Proposed:

Marking as a good first issue – I think the proposed fix could work well with the forced-colors media query, without expert knowledge of Wagtail required. Note testing this does require having access to Windows high-contrast mode.

I would like to work on this issue.


Endpoint Snapshot Popup Page

Pull requests into this repository require the following checks to be completed by the submitter and reviewers.
Changes in this PR:
Created the endpoint snapshot modal popup page and added links to the modal on every table that contains endpoint URLs. Also removed the performance page from the dashboard as we decided it is not necessary now that each endpoint has a performance table.
Submitter:

[x] Administrative tasks are complete.

This pull request describes why these changes were made.
The JIRA ticket links to this PR.
The JIRA ticket for this PR is: Lantern 462 JIRA Ticket

[x] Tests are complete.

Tests are included and test edge cases.
Tests have been run locally and pass.

[x] Code review has been performed.

Code diff has been done and checked to ensure only expected code is being committed.
A linter for the language has been run.

Primary Reviewer:

[ ] Code works.

Code has been run locally and the basic functionality affected by the PR has been checked.
Edge cases have been checked to ensure behavior is as expected.

[ ] Code review has been performed.

Code is maintainable, reusable, efficient, and correct.
Code accomplishes the tasks purpose.
Code follows style guidance appropriate for the language, including passing linter checks.
Code is well commented (which does not mean verbosely commented).

[x] Tests are complete.

Tests are included and test edge cases.
Tests have been run locally and pass.

Merger:
Prior to merging, ensure that all checks have been completed. Delete the branch after the merge
is complete.

This ticket also needs a rebase, but you can wait until the CHPL ticket is merged in!

I got this error on the Products tab, I assume because of the rebase which added the healthit_products_map table:
2022-06-23 19:36:02.355 UTC [179] ERROR:  column f.healthit_product_id does not exist at character 237
postgres_1             | 2022-06-23 19:36:02.355 UTC [179] STATEMENT:  SELECT *
postgres_1             | 	FROM (SELECT
postgres_1             | 	        f.url, h.name, h.version, h.api_url, h.certification_status, h.certification_date, h.certification_edition,
postgres_1             | 	        h.chpl_id, h.last_modified_in_chpl  FROM fhir_endpoints_info f, healthit_products h WHERE f.healthit_product_id = h.id AND
postgres_1             | 	        f.healthit_product_id IS NOT NULL AND f.url = 'https://stofo.providence-waco.org/FHIRProxy/api/FHIR/DSTU2/' AND f.requested_fhir_version = 'None') "q01"
postgres_1             | 	WHERE (0 = 1)
shinydashboard_1       | Warning: Error in : Failed to prepare query: ERROR:  column f.healthit_product_id does not exist


Add /faq/results/ directory to check_links Cypress test

This PR resolves https://github.com/corona-warn-app/cwa-website/issues/2612 "Cypress check_links.js misses issues in FAQ" by adding the directories

/en/faq/results/ and
/de/faq/results/

to
cypress/integration/check_links.js

After this change, the test will find multiple errors listed in https://github.com/corona-warn-app/cwa-website/issues/2611.

Increasing the scope of cypress/integration/check_links.js in this way will greatly assist is finding and resolving link issues introduced by the FAQ restructuring.

@MikeMcC399 Thanks!

@dsarkar

Many thanks for merging this change! It means we can now properly check changes to the links in the FAQs! 👍🏻
I hope that the team can also look at the check_anchor_links.js issue https://github.com/corona-warn-app/cwa-website/issues/2613, as I was not able to solve this on my own.


scraped NY Times data flawed

Original issue https://github.com/covidatlas/coronadatascraper/issues/978, transferred here on Thursday May 07, 2020 at 14:43 GMT

US county data differ from those in the New York Times source file (https://raw.githubusercontent.com/nytimes/covid-19-data/master/us-counties.csv).
E.g. Providence County, Rhode Island:
2020-04-29 - 3431 cases in your data
2020-04-29 - 5967 cases in NY Times data
I don't know if other counties are affected as well.

(Transferred comment)
Thanks for the issue!
We scrape multiple sources and cross check them.  It’s possible that
another source took precedence over the NYT one.
Is this still occurring?  Cheers! Jz
El El jue, may. 7, 2020 a la(s) 10:44 a. m., hannahklauber <
<EMAIL_ADDRESS>escribió:

US county data differ from those in the New York Times source file (
https://raw.githubusercontent.com/nytimes/covid-19-data/master/us-counties.csv
).
E.g. Providence County, Rhode Island:
2020-04-29 - 3431 cases in your data
2020-04-29 - 5967 cases in NY Times data
I don't know if other counties are affected as well.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/covidatlas/coronadatascraper/issues/978, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAMPWDOET2EEZQD26UT4DYDRQLCLPANCNFSM4M3MM2OQ
.

(Transferred comment)
Thank you for building up this great database!
The issue is still occurring.
Best, Hannah

(Transferred comment)
It's possible that RI is reporting current, not cumulative? Because their own website very clearly says 3,913 for Providence... which is less than yesterday, wtf? https://ri-department-of-health-covid-19-data-rihealth.hub.arcgis.com/

(Transferred comment)
Reached out to RI, they said;

Good morning,
Thank you for reaching out. The data is updated every day and cumulative.
Best,
Isabella
COVID-19 Joint Information Center

With that, it does seem that NYT and JHU are wrong, or are counting data differently somehow... Maybe it has to do with RI reporting at a city level for some places?

(Transferred comment)
This is a common NYT problem ... they're counting higher for other locations too.  Perhaps we shouldn't use them.


A10 can't inference this model (512)?

How can I inference this model ?

In the process of Loading checkpoint shards(2/2), the VRAM is bigger than 22G.

出现了一样的问题，这个模型24G的显卡推不起来
感觉这个要做一下模型的压缩
t5d文本embedding消耗太大了

出现了一样的问题，这个模型24G的显卡推不起来 感觉这个要做一下模型的压缩 t5d文本embedding消耗太大了

text_encoder = T5EncoderModel.from_pretrained(path, subfolder="text_encoder").to("cpu") text_encoder = text_encoder.half() text_encoder = text_encoder.eval().to("cuda") text_encoder.save_pretrained(save_path)
I think you can try this code. VRAM for T5 will reduce to 10G.

出现了一样的问题，这个模型24G的显卡推不起来 感觉这个要做一下模型的压缩 t5d文本embedding消耗太大了

text_encoder = T5EncoderModel.from_pretrained(path, subfolder="text_encoder").to("cpu") text_encoder = text_encoder.half() text_encoder = text_encoder.eval().to("cuda") text_encoder.save_pretrained(save_path) I think you can try this code. VRAM for T5 will reduce to 10G.

But I'm not sure whether it will affect the time and effect. especially the time-consuming. For time-consuming, https://github.com/huggingface/transformers/issues/11792

出现了一样的问题，这个模型24G的显卡推不起来 感觉这个要做一下模型的压缩 t5d文本embedding消耗太大了

Sorry, it doesn't work.

Here is an example for 8bit T5. Also, you can try to inference T5 on CPU device.

Here is an example for 8bit T5. Also, you can try to inference T5 on CPU device. Later we will support diffusers to make to whole pipeline easier to inference.

Thanks ~

Here is an example for 8bit T5. Also, you can try to inference T5 on CPU device. Later we will support diffusers to make to whole pipeline easier to inference.
Using this method, it is indeed possible to reduce the GPU memory usage, but it results in a situation where the int8 model is on the CPU, while other parts remain on the GPU. This still requires some handling to address the issue.

RuntimeError: Expected all tensors to be on the same device, but found at least two devices, cpu and cuda:0! (when checking argument for argument mat2 in method wrapper_CUDA_mm)

More details

example

tokenizer = T5Tokenizer.from_pretrained(args.pipeline_load_from, load_in_8bit=True,
subfolder="tokenizer")
text_encoder = T5EncoderModel.from_pretrained(args.pipeline_load_from, load_in_8bit=True,
device_map="auto",subfolder="text_encoder")
change the script this part，then run，when you use gradio ui inference
“RuntimeError: Expected all tensors to be on the same device, but found at least two devices, cpu and cuda:0! (when checking argument for argument mat2 in method wrapper_CUDA_mm)”

More details

I'm OK.

replace with text_encoder = T5EncoderModel.from_pretrained(args.pipeline_load_from, load_in_8bit=True,subfolder="text_encoder") and try.

replace with text_encoder = T5EncoderModel.from_pretrained(args.pipeline_load_from, load_in_8bit=True,subfolder="text_encoder") and try. @liangwq

if 4090，always can‘t


Impossible to send Monero: Key "relayed" missing from object.

I'm still testing lightwallet server daemon and via a workaround (yes, now it's totally a workaround, aka commenting the error) for #15 issue, I tried to send some Monero to another address from stagenet. I'm using OpenMonero frontend with a custom configuration.
The problem is that when daemon receives the transaction from the call submit_raw_tx, the following error appeared:
 E Exception at [connection<t_protocol_handler>::handle_read], what=Key "relayed" missing from object.

The daemon is returning an error response that wasn't being properly handled. The latest version should provide the error message that the server was sending. The daemon logs may also have the issue.
Most likely its a double-spend due to the other issue you are having.

Server returned RPC error: invalid output with code 1 called from rest_server.cpp:643
At least now API throws an error! Last time, the call went into timeout and it was not possible to see if the action was performed successfully from the frontend.

This is likely an issue on the wallet side. Run set_log 2 on the daemon to get some detailed info on why the daemon is rejecting it. There will be lots of stuff spammed to console, so look for an error involving an output. Most likely the wallet you are using has not been upgraded to create CLSAG outputs, which monero-lws can't resolve.

Is this resolved?

I think this was resolved, if not ping to re-open.


First pass implementation for traits folder contents

Provide first pass implementation for the traits folder.
First pass implementation means that all (valid) keys used in vanilla files either:

Have full working implementations OR
Have working placeholder implementations (eg. simple scalars) with status documented on the tracker OR
Have false positives in a placeholder or incomplete implementation that properly covers the majority of use cases. OR
Have false positives or are unimplementable due to bugs or missing features in cwtools core

Additionally, before this issue can be closed, please make sure of the following:

All significant TODO items are documented in the issue tracker
Documentation strings are either present or documented as missing in the tracker

That being said, these are just the criteria for this issue and scope item to be considered finished. In these early days, every new definition is incredibly helpful for end users trying to use cwtools! PRs with partial implementations are more than welcome!
This is an auto-generated issue. It may make sense to close this ticket, combine it with others, or split it into smaller chunks.

This is mostly done, just needs some documentation and cleanup.


Vim(let):E716: Key not present in Dictionary: "headers.subject"

Hi,
I'm using neovim 0.5.0 and recently installed himalaya 0.4.0.
CLI works fine and prints inbox of my Outlook account, but in nvim, if I call :Himalaya, I get:
Vim(let):E716: Key not present in Dictionary: "headers.subject"
Could you please advise?
Thank you,
Tamas

With Vimplug, such as Plug 'soywod/himalaya', {'rtp': 'vim'}

The problem is that the CLI is versioned but not the Vim plugin (since it clones the git repo). For now, I would advise to align the CLI version with the Vim plugin branch. If you use the v0.4.0 of the CLI then use the v0.4.0 branch/tag from the Vim plugin instead. What I could do is to use the master branch as the production one (the last master commit = a tagged version) and develop on a development branch. If you have better idea, let me know!

I just tried making sure they're both aligned. I've got the v0.4.0 versions for both. I'm still getting the same error.

Do you also use vim-plug? If so then could you add the tag entry in your plug command? Sth like Plug 'soywod/himalaya', {'rtp': 'vim', 'tag': 'v0.4.0'} and try again?

I do. Let me give that a try.

Looks like it's working now. I had to totally delete my HImalaya plugin and let it re-download complately. but it's working now. Thank you!

OK, it seems I'm having other issues now. If I try to write a message, for example, I get Vim(call):E716: Key not present in Dictionary: "template, "\r", "", "g"), "\n"))"

@soywod I did what you've advised above (aligning the plugin version to the CLI; both at 0.4.0) and it solved the issue on my end. Himalaya is working as expected. Thank you for the help!

@TamasSmahajcsikszabo No problems writing e-mail or anything? Because I'm having problems with that now.

@wjcagle Inbox search, listing work well, but when writing new messages, I can confirm your error message. I get the same error, such as:
Vim(call):E716: Key not present in Dictionary: "template, "\r", "", "g"), "\n"))"

Then I advise you to wait for the v0.5.0, I should release it in the next days. Sorry for those bugs, the project is still young!

@soywod No worries, thank you, keep up the good work.

Thanks for the kind words. I let you know when the new release is available!

Agreed. Keep up the good work, and I'll look forward to v.0.5.0. :)


Languages in forms

This fixes #822.
@gvwilson please let me know if you want to track language(s) in the TrainingRequest model.

:+1:

I take it as a "no" ;-)
On 06/26/2016 04:05 PM, Greg Wilson wrote:

👍
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/swcarpentry/amy/pull/843#issuecomment-228603047,
or mute the thread
https://github.com/notifications/unsubscribe/AAEcdTZcFL7QQMT2Jv9LD9AUV0UB_eD0ks5qPocSgaJpZM4I-jbR.


Startup Race Condition - Solution I used - Delay Docker Start

Using the Docker method, wg-manager has been running just fine.
However, on server reboots, it wouldn't always work. I was never able to trace the root cause. The web server came up, the wg0 interface showed green, everything seemed to work. Except clients couldn't connect.
My conclusion is that there's some sort of network race condition, but it's not making a lot of sense why. My solution is crude, but it works. I delayed Docker's start by 30 seconds.
In an Ubuntu host, I edited:  /etc/systemd/system/multi-user.target.wants/docker.service
under [Service] right before ExecStart, I added ExecStartPre=/bin/sleep 30
The delay is definitely a band-aid that shouldn't be needed, but hopefully it helps someone.

Perhaps docker starts up before networking? Maybe its possibly to delay this internally.


Error: ENOENT: no such file or directory, open d:\ionic2app\www\index.html'

I am trying to run Ionic project using ionic serve, but facing Error: ENOENT : no such file or directory, open d:\ionic2app\www\index.html
I have update ionic but still no luck.

Hello, thanks for opening an issue with us. Would you mind telling me what version of the ionic-cli you are using? You can just run ionic --version to get the version.

Ionic version is 2.1.0

I believe the reason for this is that the build step isn't being run. I'm still getting errors because ionic serve is looking for a gulpfile

probably this issue happens because of npm version.
ionic requires npm version 3

I updated, uninstalled, and reinstalled
On Wed, Sep 28, 2016 at 3:41 PM comfortme
<
mailto:comfortme<EMAIL_ADDRESS>
wrote:

a, pre, code, a:link, body { word-wrap: break-word !important; }
probably this issue happens because of npm version.
ionic requires npm version 3
—
You are receiving this because you commented.
Reply to this email directly,
https://github.com/driftyco/ionic/issues/8262#issuecomment-250292786
, or
https://github.com/notifications/unsubscribe-auth/ABdfDusJHYANNhX1l2j79cKAVpHeuU1Kks5qutDegaJpZM4KJNO-
.

@junaidahmed93 and @keithmattix what version of nodejs and NPM are you all running? Thanks!

I'm using nvm doing 6.7.0 and 3.10.3

@keithmattix what version of the ionic cli are you using?

Hm, it says 2.0.0-beta.23...I just uninstalled and reinstalled today.

@jgw96 My Node version is 4.5 and npm 3.10.8

@keithmattix can you run npm uninstall -g ionic and npm install -g ionic. The beta flag is no longer required (: @junaidahmed93 are you getting this error with a beta.11 app or an RC.0 app?

@jgw96 I am getting this error with RC.0 app.

Same; mine is an rc.0 app

I am getting this error with RC.0 app.
It seems that the files of pages directory, is not compiling for the build folder.

@bergmito are you running Ionic cli version 2.1.0?

Yes, i'm running Ionic cli version 2.1.0.
Solve my problem, changing template url from components.
Before:  templateUrl: 'build/pages/configs/configs.html',
Now:      templateUrl: 'configs.html',

Ah, I figured out my problem. My old nvm version didn't allow my ionic binary to update

@jgw96 , My problem is solved by updating ionic (nothing changes in version but app is working now strange). Thanks

Tanks for all

@bergmito you can check out our changelog update instructions for all the upgrade instructions. Since it seems like this issue was fixed for everyone I am going to close this issue for now. Thanks!

I am still facing this issue.
I tried multiple times to update ionic but even though my npm list shows ionic version as 2.1.0
my ionic --version command shows beta.25
so even after I updated and created a new project it is still not able to start and getting this same error.

> Terminate batch job (Y/N)? y
> ionic $
> C:\myapps\ionic2-tests\newapp>npm version
> { npm: '3.10.6',
>   ares: '1.10.1-DEV',
>   http_parser: '2.7.0',
>   icu: '57.1',
>   modules: '48',
>   node: '6.2.1',
>   openssl: '1.0.2h',
>   uv: '1.9.1',
>   v8: '<IP_ADDRESS>',
>   zlib: '1.2.8' }

@balasivagnanam I think may be you have to do:
npm uninstall -g ionic@beta (with sudo if you need those permissions)
To get the beta disapear.
Hope this will help you.

@Rafael300890  thannks,
I solved by :
if you get ionic -v even after uninstalling..
run where ionic and find out the location of your installtion.
for me there was a version installed in
C:\>where ionic
C:\Program Files (x86)\nodejs\ionic
C:\Program Files (x86)\nodejs\ionic.cmd

I am not sure how it went there last time. but after manually deleting them, My ionic cli is now updated and my project is able to render in browser.
Thanks a lot

@keithmattix So what did you do with nvm? this may solve for me too as I use nvm.

solved, I also need to uninstall my beta version and reinstall, just done:

npm uninstall -g ionic@beta
npm install -g ionic

"scripts": {
    "build": "ionic-app-scripts build",
    "watch": "ionic-app-scripts watch",
    "serve:before": "watch",
    "emulate:before": "build",
    "deploy:before": "build",
    "build:before": "build",
    "run:before": "build"  },

ensure that u have the above  code in package.json file.......................

There has nothing wrong with the Ionic version, these error cause by the lack of build script in package.json.
I use ionic start myproject tab --v2 and ionic start myproject tutorial --v2 command start two project, i found the package.json file are different.
In tab project, there is no "serve:before": "watch", script in package.json. there won't build the necessary file before you run ionic serve
so make sure you have below script in your package.json:

"scripts": {
"build": "ionic-app-scripts build",
"watch": "ionic-app-scripts watch",
"serve:before": "watch",
"emulate:before": "build",
"deploy:before": "build",
"build:before": "build",
"run:before": "build"
},

Thank you very much Jack, that fixed my issue. I used ionic start --v2 myApp sidemenu. I guess the correct package.json was the one for tutorial ?


upgrade protractor to 3.0.0

Issue #8

Thank you for the PR. I will publish the npm package tonight (NYC Time)


Can I enable CSI/camera for 845c board?

I am building yocto for Qualcomm RB3 ( Dragonboard 845c ).
But its camera cannot work under this version.
I have seen 410c can enable it.
I wonder whether I can do similar for 845c?
I have enabled qcom-camss and ov8856 modules,  but I think what I am missing is correct DTS?

answered on 96boards forum.