Annotation to specify multiple UnexpectedResponseExceptionType

Is your feature request related to a problem? Please describe.
The REST Proxy should be able to throw richer exception depending on the error code returned by service.
Describe the solution you'd like
Define an annotation, that can be used to define multiple exception types and map each exception type to error codes.
An example usage looks like:
@UnexpectedResponseExceptionTypes({
    @UnexpectedResponseExceptionTypes.Type(code = {333}, value = Exception333.class),
    @UnexpectedResponseExceptionTypes.Type(code = {345, 346}, value = RestException.class),
    @UnexpectedResponseExceptionTypes.Type(value = ServiceRequestException.class)
})

The annotation looks like:
public @interface UnexpectedResponseExceptionTypes {
    public Type[] value();

    public @interface Type {
        public int[] code() default { };
        public Class<?> value();
    }
}

Reference: see this discussion.
Information Checklist
Kindly make sure that you have added all the following information above and checkoff the required fields otherwise we will treat the issuer as an incomplete report

[x] Description Added
[x] Expected solution specified

Why not have multiple annotations (of the same type) on the same method like in my code snippet, rather than a single annotation containing multiple values and the new Type type?

it's because Java don't allow duplicating annotations.

Yes it does :-) https://docs.oracle.com/javase/tutorial/java/annotations/repeating.html

You're right, starting from source - 8 or above it is allowed to repeat. With source targeting 7 it gives this error: java: repeated annotations are not supported in -source 7   (use -source 8 or higher to enable repeated annotations)

Let's get repeating! :)

agree, repeating is easy from code generating point of view as well.

@anuchandy  - is this on your todo list before you go on leave? If not, let me know and we'll get someone else working on this.

@JonathanGiles it's not on my list because @mayurid want @alzimmermsft to do it, see the old issue https://github.com/Azure/azure-sdk-for-java/issues/3139 you you referred in your previous comment.

@jianghaolu will work on this.


CRC do not work in circleci or travisci

CRC do not work in circleci or travisci unlike kind cluster which can be used in many CI environments.
https://app.circleci.com/pipelines/github/kaovilai/reliable-ci/15/workflows/e65e2e00-0e06-44da-9598-a0d1a0e593a3/jobs/22

@kaovilai CRC needs virtualization enable to work with any platform. Since OCP only allow RHCOS for control nodes https://docs.openshift.com/container-platform/4.11/architecture/architecture.html#architecture-custom-os_architecture .

OCP and therefore CRC depends on Red Hat CoreOS to be the base OS. For this reason you need nested virtualization to make this work. Unfortunately this means that most free tier CI services will not be sufficient.


Assertion failure on 'realxtend scene' in OgreAxisAlignedBox.h

Happens at least on 'realxtend scene' from login.realxtend.org
Assertion failed: ((min.x <= max.x && min.y <= max.y && min.z <= max.z) && "The minimum corner of the box must be less than or equal to maximum corner"), function setExtents, file /Users/cvetan/workspace/ogre-safe-nocrashes/OgreMain/include/OgreAxisAlignedBox.h, line 252.
This is the backtrace for reference.

Could be important to note that if SkyXHydrax plugin is excluded on run-time, there is no crash.

Seems that it's corrupted data (and not just false statements) in 'custom projection matrix' (mProjMatrix) which is created outside Ogre via Frustum::setCustomProjectionMatrix. See http://www.ogre3d.org/forums/viewtopic.php?t=40634
Assertion failed: ((min.x <= max.x && min.y <= max.y && min.z <= max.z) && "The minimum corner of the box must  be less than or equal to maximum corner"), function setExtents, file /Users/cvetan/workspace/ogre-safe-nocrashes/OgreMain/include/OgreAxisAlignedBox.h, line 252.
Program received signal SIGABRT, Aborted.
0x00007fff807a50b6 in __kill ()
(gdb) up
1  0x00007fff808459f6 in abort ()
(gdb) up
2  0x00007fff808329bc in __assert_rtn ()
(gdb) up
3  0x000000011b18fe9a in Ogre::AxisAlignedBox::setExtents (this=0x1252a3550, min=@0x7fff5fbfc4b8, max=@0x7fff5fbfc4a8) at OgreAxisAlignedBox.h:251
251	            assert( (min.x <= max.x && min.y <= max.y && min.z <= max.z) &&
(gdb) up
4  0x000000011b0d18a9 in Ogre::Frustum::updateFrustumImpl (this=0x1252a3220) at OgreFrustum.cpp:589
589			mBoundingBox.setExtents(min, max);
(gdb) print mProjMatrix
$1 = {
{
m = {{-nan(0x400000), -nan(0x400000), -nan(0x400000), -nan(0x400000)}, {-nan(0x400000), -nan(0x400000), -nan(0x400000), -nan(0x400000)}, {-nan(0x400000), -nan(0x400000), -nan(0x400000), -nan(0x400000)}, {-nan(0x400000), -nan(0x400000), -nan(0x400000), -nan(0x400000)}},
_m = {-nan(0x400000) <repeats 16 times>}
}
}


Allow logical AND for calls on implicit objects inside case branches

It's a little weird that logical OR is allowed but AND isn't
case 0
when .zero? && .even? then nil # not supported
when .zero?, .even? then nil # supported
end

It was actually a mistake to have the implicit call notation, because it's not composable.

It's still useful, isn't it?

I prefer to remove half baked features that can never be complete.
In Ruby this doesn't exist for a good reason: that's not a complete expression. In Ruby you can compose things so nice, for example allowing splat in when, or in rescue. And it works because everything is an expression.

Actually, it's fine like that. If you want to use AND you can use an if, it's not a big deal, really. Even in the example above .zero? && .even? doesn't make much sense.

There's no real need for this, one can use &&. If one notation can't be used all over the place but there are alternatives, you can use the alternatives.


Add testing (both frontend and backend) for PostGRES feature post 2.0

In the database_assetstore plugin, there is a sample dataset of Massachusetts census data.  The data was taken from http://www.mass.gov/anf/research-and-tech/it-serv-and-support/application-serv/office-of-geographic-information-massgis/datalayers/census2010.html and converted to a PostGIS sql database.  I think I originally followed this guide: http://www.bostongis.com/?content_name=postgis_tut01 .  The sample data is located here: https://midas3.kitware.com/midas/item/319584 .  This is just the census and boundary data with a few of the columns that were irrelevant for testing removed.
As part of the upgrade of database_assetstore to Girder 2.0, the data will be moved from the midas server to data.kitware.com.


ci: Add Default Platform Label to PRs and Issues

#skip-changelog

Codecov Report

Merging #677 (3bd06c8) into main (14203b9) will increase coverage by 5.50%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             main     #677      +/-   ##
==========================================
+ Coverage   90.65%   96.15%   +5.50%
==========================================
  Files          97        2      -95
  Lines        3145       52    -3093
==========================================
- Hits         2851       50    -2801
+ Misses        294        2     -292

Impacted Files
Coverage Δ

dart/lib/src/protocol/span_id.dart

dart/lib/src/sentry_envelope_item_header.dart

dart/lib/src/protocol/sdk_version.dart

dart/lib/src/protocol/sentry_browser.dart

dart/lib/src/diagnostic_logger.dart

dart/lib/src/protocol/sentry_thread.dart

dart/lib/src/platform_checker.dart

dart/lib/src/protocol/contexts.dart

...art/lib/src/enricher/enricher_event_processor.dart

...tter/lib/src/flutter_enricher_event_processor.dart

... and 85 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 14203b9...3bd06c8. Read the comment docs.


Not working in Android WebView

The swiping works, but it is putting all the swiper-slide contents on the first slide and the next two are blank?
The can be seen at www.wnmobileapps.com/standings/ahl
It looks fine in Chrome on the phone, but when that url is loaded inside an Android Webview, that is when the problem occurs.

what about setting an explicit size to the slide?

Hi. Sorry about the delay getting back to you. I don't really have any way of testing in Android WebView. Are you getting any JS errors?

Set dimension:
swiper{
height: 100vh;
width:100vw;
}

Closing based on  Delvezio's response. Please re-open if still an issue.


[nemo-qml-plugin-calendar] Clone existing parent when saving an excep…

…tion.
When moving the dissociation code out of the
save function, it had the drawback that only
properties copied in the CalendarData::Event
structure are preserved in the exception.
This may creates some issues with the sync
plugins that may use properties that are not
part of CalendarData::Event structure.
Ensure that such properties are kept when
creating an exception by cloning the parent
before updating it with the exception
modifications.
@pvuorela, this is correcting an issue introduced in 4e0b556a, when moving the dissociation code out of the save routine. This move simplified the creation of a CalendarEventModification but had the drawback that some properties of the parent (those not duplicated in the CalendarData::Event structure) were lost in the process. This PR should solve this. It would also make sailfishos/buteo-sync-plugin-caldav#20 obsolete.

Going back to my calendar modifications, @pvuorela, may you have a look on this PR when you have the time to, please ? Thank you in advance.

Thanks, no problem. No hurry.


Improve performance for job list

Currently the job list command is extremely slow, this is likely because it is iterating through all of the jobs before taking a slice for the results. cf, demo db is currently ~7GB
We should instead iterate through the list of jobs using the offset and limit to stop processing as soon as possible.  e.g. decrement an offset and ignore the record until we get to 0, then when adding to results decrement the limit until we reach 0. This gets much harder if we need to apply filters but we can at least improve the performance of the default list.

Obvs: measure first before making changes. Also investigate whether compaction might help?

https://github.com/bacalhau-project/bacalhau/pull/3572


Form specializations

@mojowen if you got a few emails then this should be good to go, I already tested the extra MI form data showing up in ActionKit

@mojowen if you got a few emails then this should be good to go, I already tested the extra MI form data showing up in ActionKit

@nexussays I got a bunch! I will move this into production mode - so live emails


New command line option for country as filter

country as filter (default: Germany)
changing to language "English" for tests to avoid translation files since covid19 data are in English.
if a language is specified that does not exist exit with error

done.


Missing documentation for Force Alphabetical Sort Within Sections

https://timothycrosley.github.io/isort/docs/configuration/options/#force-alphabetical-sort-within-sections

Force Alphabetical Sort Within Sections
No Description

It would be helpful if there was a description for this. It reads very similarly to:

Force Alphabetical Sort
Force all imports to be sorted alphabetically within a section

Thanks for reporting!
This has been fixed in the just published 5.0.3 patch version.
Thanks!
~Timothy

That description is much more helpful, thanks!


Small change to let the possibility to remove or not fully NaNs features

Great ! Some questions I have:

Why would one use this (what is the issue)? Nans features will never be used by the feature selection ? memory efficiency ?
From the implementation, one could either set a custom featurizer (with drop nans to true) when creating the MODData or do It later with featurize() function and dropnan to true. What is the recommended usage ?
Should the default behaviour be dropping all nans columns or not ?

I had to do this because of a quite rare situation I faced. I'm featurizing a composition dataset using, among others, features that are predicted with modnet models. I have trained these models on another database (elastic data materials project) and the features have been selected for this model. In order to featurize my dataset with elastic data predicted from these models, I need to have all the features that have been used to predict the elastic data in my dataset (or featurize twice, but I don't want to do that). From time to time, one of the features that was used for the elastic data model disappears from the features of the dataset because they are all NaNs, which leads to an error when predicting the elastic constants. If I set drop_allnan to False, then these features are still present when predicting the elastic data, and I remove them afterwards myself.
With this implementation, I have to set drop_allnan to False when initializing the featurizer, and also when featurizing. This could be simplified with e.g. setting self.featurizer.drop_allnan to True if set to True in MODData.featurize() (something similar to set_n_jobs). Do you want me do to that?
The default should be to remove these fully-NaN features, because indeed they do not bring anything. This is just there to help with a peculiar situation for which I have to modify MODNet, otherwise I cannot proceed easily. Thought it might be useful to others as well, and it's not a big change.


Remove use of prototype extensions.

Not all applications use the prototype extensions, thus making these
components unusable.

Rad, thanks!

Published to npm as<EMAIL_ADDRESS>


added instructions for checkbox

added the problem of checkboxes note and also answered the same in issue

Please approve my pull request so that the future users don't have to worry about the checkbox problem they have raised in issues!!


Remove Directory Evidence type

CompressedDirectory should be used instead since it can be easily managed by the storage manager.

After talking with Wajih a while back we decided that we can keep this evidence type for local only for now.  This should properly error out when attempted to be used with a cloud/hybrid installation.  In the future we could auto-convert this to a CompressedDirectory type and auto-upload it to GCS to cover the cloud use-case.


Contributing credits

[x] Get list of contributors
[x] Write a script to auto-format contributors section accordion (pass-off)
[ ] generate the contributing section

NOTE:
Same PR as before, I just made a fresh fork - couldn't figure out the problem with git.

The auto-generation works, I'd like someone to check the contributing list once more, its int the CONTRIBUTORS file. @ loftwah was missing this time, not sure how many others I missed.
cc: @Silverarmor

The auto-generation works, I'd like someone to check the contributing list once more, its int the CONTRIBUTORS file. @ loftwah was missing this time, not sure how many others I missed.
cc: @Silverarmor

Still need to add comments

Still need to add comments

This will no longer happen

This will no longer happen

Then we'd be dumping everyone's conventions together (not exactly but the difference isn't distinct) - all sections except the latest release are collapsible so it really wouldn't take up all that much space.

@Silverarmor, what is the plan for this PR? Modify and keep or drop?

imo drop it for now, possibly revisit it in the redesign, so don't delete work/the branch


Cannot delete a previously activated profile

Attempting to delete a configuration profile after it has been created results in a foreign key constraint violation with users.  Users should not be deleted in this case, and neither should a DSO.  DSO's should only be deleted after they have been removed from all configuration profiles to which they belong.

@excelsior - I'm getting this error when I try to delete:
Attention: PG::ForeignKeyViolation: ERROR: update or delete on table "mappings" violates foreign key constraint "fk_rails_1ddc7afe0c" on table "alignments" DETAIL: Key (id)=(6) is still referenced from table "alignments".
This is for the Configuration Profile named "Delete Me".

@excelsior  - With your latest deployment, I am now getting this error when attempting to delete "Delete Me 2":
Attention!
Attention: Failed to destroy the record


Need a T-Display-S3 board-specific definition for IDE

T-Display-S3 is pretty much useless in PlatformIO without LilyGo contributing an official board definition for PlatformIO IDE.  Can be configured to work in Arduino IDE, ok, but a total nightmare in PlatformIO, if possible at all.
Can we run basic code, blink demos, and other more fancy demos?  Sure. Yes.  But as soon as you try and run something that needs PSRAM... nope!  You're screwed.
The "official" (current) way to use this board is by selecting  "ESP32S3 Dev Module" (ie esp32-s3-devkitc-1).  But this board is GENERIC, literally titled "Espressif ESP32-S3-DevKitC-1-N8 (8 MB QD, No PSRAM)".  But of course, this default config is WRONG, because right off the bat, we know T-Display-S3 has 16MB Flash, and 8MB of PSRAM (granted, we have NO idea which type, Quad or Octal... lacking docs, that is an entirely other but related problem)
Configuring these things is not too hard from Arduino IDE/Tools menu, but in PlatformIO... a complete disaster, making T-Display-S3 useless for serious projects.
Add a T-Display-S3 board type for use in IDE, and don't leave us hanging with this generic thing we can't use.

If you have read my example carefully you know that T-DISPLAY-S3 is perfectly suitable for platformIO. PSRAM can be used, you can directly refer to my configuration file.
https://github.com/Xinyuan-LilyGO/T-Display-S3/blob/main/example/factory/platformio.ini

When I enable PSRAM (DBOARD_HAS_PSRAM), I get E (219) psram: PSRAM ID read error: 0x00ffffff.
This generally means the wrong board is selected, but considering the correct board is configured (esp32-s3-devkitc-1), it must be some other config issue.  Getting to (and understanding) all the configuration options in PlatformIO to try things is very tedious.  This is largely a fault of PlatformIO and the Espressif extensions for VSCode.  My angle here is... rather than searching the entire web for config settings, why not just bundle it all into a T-Display-S3 specific board definition?

board_build.arduino.memory_type = qio_opi
In addition to enabling, OPI mode also needs to add this option. I understand your idea. If there is a T-Display-S3 model can avoid adding more options.

Recommend close this Issue?

I am trying to use this platformio.ini and it's not working.
The first boot does work, but then on subsequent boots I am stuck in a boot loop like the following :
ESP-ROM:esp32s3-20210327 Build:Mar 27 2021 rst:0xc (RTC_SW_CPU_RST),boot:0x8 (SPI_FAST_FLASH_BOOT) Saved PC:0x420ba45e SPIWP:0xee mode:DIO, clock div:1 load:0x3fce3808,len:0x43c load:0x403c9700,len:0xbec load:0x403cc700,len:0x2a3c SHA-256 comparison failed: Calculated: dcde8d8a4817d9bf5d5d69a7247667264e4e10ac7493514868b61f5aa6146539 Expected: ffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff Attempting to boot anyway... entry 0x403c98d8 Tron-68B6B3231E14 mounted file system opened config file {"boot_num":"1","brightness":"High","config_url":"http://gt.wildc.net:8080/api/v1/gt_MAC_ADDRESS/attributes","d_opts":"p","dtype":"wind+wave","startup_message":"Maui","update_interval_minutes":"5","upsidedown":"true"}xV��?\␁ {   "boot_num": "1",   "brightness": "High",   "config_url": "http://gt.wildc.net:8080/api/v1/gt_MAC_ADDRESS/attributes",   "d_opts": "p",   "dtype": "wind+wave",   "startup_message": "Maui",   "update_interval_minutes": "5",   "upsidedown": "true" } parsed json_config config_url key exists Using config from flash json_to_config Default to WiFi Client config_to_json writing json config to flash in Display Constructor in tdisplay_s3 Constructor out of Constructor in tdisplay setup [  1421][E][esp32-hal-gpio.c:102] __pinMode(): Invalid pin selected [  1421][E][esp32-hal-gpio.c:102] __pinMode(): Invalid pin selected going for println ESP-ROM:esp32s3-20210327 Build:Mar 27 2021


fix probability hang of service destruction

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


Feature request: Display API documentation comment

It would be useful to display the API documentation comment under the file name in the chip preview.
API documentation comment syntax from the HDL documentation:
/** API documentation comment */

The parser does not unfortunately access the api documentation comment.


Wrap nodes before calling {add,remove}EventListener.

This PR is to prepare for webcomponents/polyfills#332, which will manually dispatch all events with targets that are disconnected in the real tree, even if they are connected in the user-facing tree. Before this change, all events (except focus and blur) were dispatched natively, which meant that events dispatched to nodes that were disconnected in the real tree but connected in the user-facing tree would incorrectly propagate only through the disconnected piece of the tree containing the node. Dispatching these events manually in Shady DOM fixes this issue, but only if it's aware all of the listeners it needs to call, which requires wrapping with ShadyDOM.wrapIfNeeded before calling addEventListener/removeEventListener.
These particular changes were needed to fix some failures that showed up in internal testing of webcomponents/polyfills#332, but there are other places in Polymer that use addEventListener/removeEventListener without wrapping first. AFAIK, these weren't wrapped originally as a perf optimization and I think that some of them could stay that way if necessary, but I'm not sure about all of them. Particularly:
https://github.com/Polymer/polymer/blob/master/lib/utils/flattened-nodes-observer.js#L286-L312
This one seems relatively likely to need to be wrapped given that slotchange bubbles.
https://github.com/Polymer/polymer/blob/master/lib/utils/gestures.js
The addEventListener on window is only used for testing if passive is supported, so that doesn't need to be wrapped, but addEventListener is also called on document and other nodes in general to listen for mouse events. I don't think it's likely that these need to be wrapped because the user can't interact with disconnected nodes.

I think dispatchEvent also requires wrap and there are a few places in Polymer that don't wrap things they're dispatching events to, should I update those here?


Use material theme

I see the theme has been updated. I guess the extensions are dependencies to the theme.


API Logging

Add more information on route access. E.g.
"POST /user/create HTTP/1.1" 200 OK should contain the name of the user

What exactly is the problem

Hi @abant07
I think we should extend the logging that it shows the names of users or games when they are created, logging in, or doing something else. For the moment we rely on the builtin logging of Uvicorn (I think) but should use our own logging in all API route methods.
Does this answer your question?

Hi @Segelzwerg
Yes, thank you, the direction make sense, but I had a couple more questions

Is there an existing code that you created where I would need to extend upon or do I make brand new code? Also can I use Python?
I am not familiar with Uvicorn, can I know what exactly is logged into Uvicorn as you mentioned?

(This is my first open source contribution, so I'm sorry if things might go a little slow)

@abant07 thanks for your interest. I tried to answer your questions below, please feel free to ask again if something is not clear yet,

Is there an existing code that you created where I would need to extend upon or do I make brand new code? Also can I use Python?

No, until now we didn't log anything on our own and yes you actually should use Python as it is the only language we use for this repo. Maybe these links help: https://docs.python.org/3/howto/logging.html https://dev.to/tomas223/logging-tracing-in-python-fastapi-with-opencensus-a-azure-2jcm

I am not familiar with Uvicorn, can I know what exactly is logged into Uvicorn as you mentioned?

I guess it is somewhere documented, but in my opinion, we can write additional logs and don't care what Uvicorn does for the moment. So there might be some duplicate logs.

(This is my first open source contribution, so I'm sorry if things might go a little slow)

Not to worry. Ask as much as you want and we work on this project in our free time only. So my understanding is you want to take care of this issue?

Yes, I would be happy to attempt this issue, however, I might frequently pop into this discussion chat if I have questions about the logging.
Thanks

Hi @Segelzwerg
So I just quickly wanted to pop in and clarify the assignment before I go too far. Do you want me to create a file that logs the name of the user when they are created and/or logged-in ? If that is the case, I'm kinda confused on how I would use an API route for this? Could you please advise me?
Thanks

Hi @abant07 there is no log them to a specific file it can be logged to the default logger, which in turn can later be logged to a file.
I hope this clears it up, otherwise please ask again.

so would the default logger just be the console? also am I right about logging the name of the user every time they log in/access the API route?

so would the default logger just be the console?
Exactly. Only in the later stage we will create logging to file for production.

also am I right about logging the name of the user every time they log in/access the API route?
Yes, unless you think it is not required for that route.

Thank you, so just to confirm. I am writing a function that is taking the input of the route access you have given (POST /user/create HTTP/1.1) and then parsing the user information from that route to then log it into the console?
Thanks,

Thank you, so just to confirm. I am writing a function that is taking the input of the route access you have given (POST /user/create HTTP/1.1) and then parsing the user information from that route to then log it into the console?
Thanks,

Yes, that seems about right. You can also do a Draft PR if you want to discuss code.

Hi,
So I think I have got the code, but im not sure where to make the pull request.

Actually, nevermind, I pushed it to the server, let me know if you see it, otherwise, I can try it again. It's called "API Logging"

@abant07 I saw you forked the repo, but it is much easier to review for us when you create a PR. Can you do that?
https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request-from-a-fork

ok i have made pull request

Hi @Segelzwerg
I have made a pull request a few days ago, but I'm not sure if the team is reviewing it. If you are not able to see it, I can try again.
Thanks

see #198

Thank you @Segelzwerg
I think I am understanding after looking at the folders in the "code" section. So to clarify, is the issue that you want to add a log line to log the user game in each one of the files located in the "user" and "games" folder. For example, create.py, join.py, info.py, auth.py, etc.
Thanks

@abant07 Yes that is what were are looking for. You may need to have a look how the user object is constructed in order to get the username.

Hi @Segelzwerg
I have just made the pull request. Please let me know if there is another problem needed to be fixed for this issue.
Thanks

Hi @Segelzwerg @iTitus
Is everything good for this issue or is there still work to be done?
Thanks

@abant07 are you still working on this or can someone else take over?

Hi @Segelzwerg
Someone can take over this.
Thanks


Update cli.md

Adds --silent option documentation.

There seems to be something wrong about this feature:

as for webpack 3.11.0 (docs current version) using it throws an error
Isn't it a duplicate of working --dispalay=none?

This wound up being added to webpack-cli which I believe only lands in<EMAIL_ADDRESS>As far as being a duplicate... on the surface it looks like it. The original feature request and ticket(s) spanned across a few years, and repositories.
For now, I'll open up the revert and open a new PR against next.


Missing "ownerReferences" for PVC

Hi, I'm using ArgoCD to deploy a click-house cluster. After creating PVC ArgoCD Goes to kill them.

Because this resource does not have a binding to the cluster

For example, the rest of the resources have the following values:
ownerReferences:
    - apiVersion: clickhouse.altinity.com/v1
      blockOwnerDeletion: true
      controller: true
      kind: ClickHouseInstallation
      name: repl-04
      uid: f496f792-58a3-47c8-ba8c-dc62d4904f65

In fact, it works and is not deleted because it is attached to the pod, but if the pod dies and remains autoprune, then the data will go with it.
My manifest
---
apiVersion: "clickhouse.altinity.com/v1"
kind: "ClickHouseInstallation"
metadata:
  name: "repl-04"
  namespace: **********
  finalizers:
    - finalizer.clickhouseinstallation.altinity.com
spec:
  defaults:
    storageManagement:
      provisioner: Operator
      reclaimPolicy: Retain
    templates:
      podTemplate: clickhouse-v22.2
      dataVolumeClaimTemplate: default-volume-claim
  configuration:
    users:
      default/k8s_secret_password: kopachev-test/clickhouse-credentials/default
      kopachev/k8s_secret_password: kopachev-test/clickhouse-credentials/kopachev
      kopavhev/allow_databases/database:
        - "kopachev"
        - "system"
    zookeeper:
      nodes:
        - host: zookeeper-0.zookeepers.zoo3ns
          port: 2181
        - host: zookeeper-1.zookeepers.zoo3ns
          port: 2181
        - host: zookeeper-2.zookeepers.zoo3ns
          port: 2181
    clusters:
      - name: replcluster
        templates:
          podTemplate: clickhouse-with-volume-template
          dataVolumeClaimTemplate: default-volume-claim
        layout:
          shardsCount: 1
          replicasCount: 3
  templates:
    podTemplates:
      - name: clickhouse-v22.3
        spec:
          containers:
            - name: clickhouse
              image: clickhouse/clickhouse-server:22.3
              volumeMounts:
                - name: default-volume-claim
                  mountPath: /var/lib/clickhouse
              resources:
                requests:
                  memory: "64Mi"
                  cpu: "100m"
                limits:
                  memory: "64Mi"
                  cpu: "100m"
    volumeClaimTemplates:
      - name: default-volume-claim
        provisioner: Operator
        reclaimPolicy: Retain
        spec:
          storageClassName: kops-csi-1-21
          accessModes:
            - ReadWriteOnce
          resources:
            requests:
              storage: 2Gi
              ```
 Thanks!

try change
    storageManagement:
      provisioner: Operator

to
    storageManagement:
      provisioner: StatefulSet

Thanks, this works, but I need the operator to manage the disk, this allows the pods not to reboot when the disk size changes

We need to make sure that it does not break https://altinity.com/blog/preventing-clickhouse-storage-deletion-with-the-altinity-kubernetes-operator-reclaimpolicy


fix: detectOverflow export

@lainermeister does this fix the issue?
Closes #1130

@lainermeister does this fix the issue?

I'm not able to test as it doesn't seem like 2.4.3 is released yet!


anomaly-detection

basic twitter frequent item set calculation for hashtags in flink as well as anomaly detection

also get some basic unit tests set-up in flink


[ImgBot] optimizes images

Hi! I'm ImgBot. Nice to meet you.
I noticed there were a bunch of images living in your project that weren't totally optimized so I thought I'd make you a PR ;) I use a lossless compression algorithm from ImageMagick so all the images are the same quality and dimensions as before only they take up less space now.
Image processing is tough work, I know, but I never get tired and I never rest - not until all the images on GitHub are totally optimized.
*Total -- 204.18kb -> 179.96kb (11.87%)
/dist/img/logo.png -- 3.61kb -> 2.20kb (39.1%)
/dist/img/cursor-select-mapillary2x.png -- 1.06kb -> 0.79kb (25.53%)
/dist/img/cursor-select-line2x.png -- 1.05kb -> 0.80kb (23.53%)
/docs/img/modes.png -- 2.31kb -> 1.79kb (22.64%)
/docs/img/operations.png -- 97.21kb -> 82.78kb (14.84%)
/docs/img/geocoder.png -- 95.88kb -> 88.66kb (7.53%)
/dist/img/arrow-icon.png -- 1.69kb -> 1.61kb (4.79%)
/dist/img/cursor-select-mapillary.png -- 0.55kb -> 0.53kb (4.75%)
/dist/img/cursor-grab2x.png -- 0.83kb -> 0.80kb (3.17%)

Thanks, kind robot, but we're already working on this over on #4573


Including realtime part of marketing

Merged here: https://github.com/MicrosoftDocs/dynamics-365-customer-engagement-pr/pull/8062
@svejdo1 -- Thanks for the docs update! Make sure to sign the Contributor License:


Using on Databricks

The library is able to parse out JSON documents with no issues on databricks.
However, I get an error when I try to use the fields_csv and only_fields parameters.
I am getting the below error.
File /local_disk0/.ephemeral_nfs/envs/pythonEnv-a1667dce-2743-49e2-8f1e-82ca5c50677f/lib/python3.10/site-packages/flatterer/init.py:153, in flatten(input, output_dir, csv, xlsx, sqlite, parquet, dataframe, path, main_table_name, emit_obj, ndjson, json_stream, force, fields_csv, only_fields, tables_csv, only_tables, inline_one_to_one, schema, id_prefix, table_prefix, path_separator, schema_titles, sqlite_path, preview, threads, files, log_error, postgres, postgres_schema, drop, pushdown, sql_scripts, evolve, no_link, stats, low_disk, gzip_input, json_path, arrays_new_table)
150     if s3:
151         raise AttributeError("s3 output not available when supplying an iterator")
--> 153     iterator_flatten_rs(bytes_generator(input), output_dir, csv, xlsx, sqlite, parquet,
154                main_table_name, tables_csv, only_tables, fields_csv, only_fields,
155                inline_one_to_one, path_separator, preview,
156                table_prefix, id_prefix, emit_obj, force,
157                schema, schema_titles, sqlite_path, threads, log_error,
158                postgres, postgres_schema, drop, pushdown, sql_scripts, evolve,
159                no_link, stats, low_disk, gzip_input, json_path, arrays_new_table)
160 else:
161     raise AttributeError("input needs to be a string or a generator of strings, dicts or bytes")
RuntimeError: sending on a disconnected channel

@laukikpatil
I imagine this issue is not just on Databricks, as there could be bugs with fields_csv and only_fields for certain inputs.
Do you think you could provide as much of the following as possible:  (I understand some data is private, so may not be possible)

some sample data where this fails
the fields_csv you supplied where you get a failure
possibly the fields_csv file that gets produced if you just run the command without the fields_csv or only_fields
the exact arguments used to flatten

It will be very difficult to diagnose without these.
There are definitely cases where removing some fields in fields_csv and using only_fields mean that the table structure created makes no sense any more (i.e when removing intermediate tables in the schema).  These will be unavoidable, but I am more concerned with the error message not explaining that this is the case.
The above error says that the receiver thread died without really reporting why, which is not good.  It looks like you are supplying some kind of python iterator e.g a list or a generator.  If possible, you could also try supplying a file instead  (even as just an experiment) as these are likely to produce better error messages.

closing as hard to diagnose without any further information.


feat(quantic): fix-facets-selected-state

Related Issue
SFINT-3963
Changes Proposed
Added a isChecked @api value to each types of facet values that the parent can set according to the current state of the facet from headless.
~Also allowed clicking on the whole row of a facet value instead of just the checkbox in the facet.~ Removed as out-of-scope
How to test
Select one or multiple facet values and then de-select them using the breadcrumb component, the checkbox next to the right facet value should be un-selected.

If false works then it's the browser that's "fixing" the standard for you.
Find any html checkbox somewhere, edit it in your browser to put checked="false" and it should not uncheck.
Or go to the link I sent there's a live code example.

From: Luc Bergeron @.>
Sent: July 15, 2021 9:45 AM
To: coveo/ui-kit @.>
Cc: Etienne Rocheleau @.>; Author @.>
Subject: Re: [coveo/ui-kit] feat(quantic): fix-facets-selected-state (#964)
@lbergeron commented on this pull request.

In packages/quantic/force-app/main/default/lwc/quanticFacetValue/quanticFacetValue.htmlhttps://github.com/coveo/ui-kit/pull/964#discussion_r670476963:

@@ -1,9 +1,14 @@

 <input type="checkbox" onchange={onSelect} />

 {item.value}

 <template if:true={isChecked}>

   <input type="checkbox" checked/>

false is working as well for me. I guess the LWC implementation of the input is different than the link you posted.
But, let's keep the templates if you prefer.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/coveo/ui-kit/pull/964#discussion_r670476963, or unsubscribehttps://can01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAAS7OW6BD5637TY3T6ZQ5M3TX3RBLANCNFSM5AKEFPHQ&data=04|01|erocheleau%40coveo.com|cc87218cddaf417a30d908d94796e009|f1735c1d9ea143b89aea2e71110c26d5|0|0|637619535599825095|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=bb3W7Qhl6eAPOKosP2k7zdFBHRPfyj8TlEDGnR1q%2Bkc%3D&reserved=0.


sap_client is not easily changed in CI environment

When testing the fuzzer against Odata service on SCP, correct sap_client is 001.
It is cumbersome to edit file under docker container (with copied code); even if /config would be modified to be a volume, configuration files should be principally optional and ideally the tool should be executable correctly with CLI only (so its easier to use in CI environment).

Solved by introducing environment variable ODFUZZ_SAP_CLIENT, which overrides anything from .py/.yaml files.


Fixes build issues when using as a Swift Package

It seems Xcode 11 needs frameworks like CoreGraphics to be explicitly imported for Swift Packages to build properly.
I've gone ahead and imported all the necessary system frameworks in the files where they are used in order to fix the Swift PM experience.
Also added a small blurb in the README about Swift PM... nothing fancy.

Thanks again Sam, I've merged your PR and tagged this as release 2.1.0 👍🏻


Poll error prompted for subscribe command in netopeer2-cli

Hi ,
I am trying to work on the notification aspects in Netopeer2
To subscribe to notifications I gave the command:
subscribe --stream NETCONF --begin 2020-10-26T16:00:00Z
and i encountered 2 errors:
1.

nc ERROR: Session 9: invalid session to send RPCs.
cli_send_recv: Failed to send the RPC.

The Server and Client got disconnected, also that i have encountered this disconnection many times while configuring values to the Yang modules using the command like "user-rpc", but then, i get them up and running using call home procedure and then, upon issuing the same command, it works.
What could be the reason for this disconnection at the first time upon sending RPCs, and is there any fix to avoid this disconnection?

Upon re-connection, and giving the same command:
subscribe --stream NETCONF --begin 2020-10-26T16:00:00Z

I encountered the following error:

OK
nc ERROR: Session 10: poll error (Success).

Since I received a Rpc reply as OK, how should i expect the notification from the server.
Or the notifications are not working due to the poll error.
It will be helpful if i could get any help on this issue

Firstly, what netopeer2 version are you using? Then, can you provide more information about the disconnections? You can run the server (-v3) and client (verb verbose) with increased verbosity to see more messages and then paste them here. Just form this, I have no idea why it would disconnect except for some actual network issues.

The version of Netopeer2-server, i am using is 1.1.27
Restarted the server with verbosity 3, and below is the server logs after the disconnection:
PS: i have trimmed out the yang schema loading logs, FYI.

[INF]: SR: No scheduled changes.
[INF]: SR: Session 32 (user "root") created.
[INF]: LY: Resolving unresolved data nodes and their constraints...
[INF]: LY: There is no leafref

"/ietf-keystore:keystore/ietf-keystore:asymmetric-keys/ietf-keystore:asymmetric-key/ietf-keystore:name" with the value "genkey", but it is not required.

[INF]: LY: There is no leafref "/ietf-keystore:keystore/ietf-keystore:asymmetric-keys/ietf-keystore:asymmetric-key/ietf-keystore:name" with the value "genkey", but it is not required.
[INF]: LY: All data nodes and constraints resolved.
[INF]: SR: Triggering "ietf-netconf-server" "done" event on enabled data.
[INF]: SR: Triggering "ietf-netconf-server" "done" event on enabled data.
[INF]: SR: Triggering "ietf-netconf-server" "done" event on enabled data.
[INF]: SR: Triggering "ietf-netconf-server" "done" event on enabled data.
[INF]: SR: Triggering "ietf-netconf-server" "done" event on enabled data.
[INF]: SR: Triggering "ietf-netconf-server" "done" event on enabled data.
[INF]: SR: Triggering "ietf-netconf-server" "done" event on enabled data.
[INF]: SR: Triggering "ietf-netconf-server" "done" event on enabled data.
[INF]: SR: Triggering "ietf-netconf-server" "done" event on enabled data.
[INF]: SR: Triggering "ietf-netconf-server" "done" event on enabled data.
[INF]: SR: Triggering "ietf-netconf-server" "done" event on enabled data.
[INF]: SR: Triggering "ietf-netconf-server" "done" event on enabled data.
[INF]: SR: Triggering "ietf-netconf-server" "done" event on enabled data.
[INF]: SR: Triggering "ietf-netconf-server" "done" event on enabled data.
[INF]: SR: Ext SHM was defragmented and 4368 B were saved.
[INF]: SR: Triggering "ietf-netconf-server" "done" event on enabled data.
[INF]: SR: Triggering "ietf-netconf-server" "done" event on enabled data.
[INF]: SR: Triggering "ietf-netconf-server" "done" event on enabled data.
[INF]: SR: Triggering "ietf-netconf-server" "done" event on enabled data.
[INF]: SR: Triggering "ietf-netconf-server" "done" event on enabled data.
[INF]: SR: Triggering "ietf-netconf-server" "done" event on enabled data.
[INF]: SR: Triggering "ietf-netconf-server" "done" event on enabled data.
[INF]: SR: Triggering "ietf-netconf-server" "done" event on enabled data.
[INF]: SR: Triggering "ietf-keystore" "done" event on enabled data.
[INF]: SR: Triggering "ietf-truststore" "done" event on enabled data.
[INF]: SR: Triggering "ietf-netconf-acm" "done" event on enabled data.
[INF]: SR: Triggering "ietf-netconf-acm" "done" event on enabled data.
[INF]: SR: Triggering "ietf-netconf-acm" "done" event on enabled data.
[INF]: SR: Triggering "ietf-netconf-acm" "done" event on enabled data.
[INF]: LN: Call Home client "default-client" connecting...

This shows only that you started the server and it attempted to connect to a configured Call Home client. Everything is in order here, what disconnections are you talking about?

As soon as the server gets disconnected, i get the following prompt at netopeer2-server log:

[2020/10/26 18:55:48.394621, 1] ssh_socket_exception_callback:  Socket exception callback: 1 (0)
[2020/10/26 18:55:48.394689, 1] ssh_socket_exception_callback:  Socket error: disconnected

That seems like a normal disconnect from the client, so what is the client printing?

The client prints:

nc ERROR: Session 9: invalid session to send RPCs.
cli_send_recv: Failed to send the RPC.

so i had to reconnect to the server.

Like I said, please increase client verbosity using the command verb verbose and only then connect to the server. The error you posted is too generic.

Okay, so the client prints:

subscribe --stream NETCONF --begin 2020-10-26T16:00:00Z
nc ERROR: Session 3: invalid session to send RPCs.
cli_send_recv: Failed to send the RPC.
[2020/10/26 19:14:34.333284, 3] ssh_packet_need_rekey:  packet: [data_rekey_needed=0, out_blocks=1058, in_blocks=62390
[2020/10/26 19:14:34.333441, 3] ssh_socket_unbuffered_write:  Enabling POLLOUT for socket
[2020/10/26 19:14:34.333479, 3] packet_send2:  packet: wrote [type=96, len=16, padding_size=10, comp=5, payload=5]
[2020/10/26 19:14:34.333497, 3] ssh_channel_send_eof:  Sent a EOF on client channel (43:43)
[2020/10/26 19:14:34.333516, 3] ssh_packet_need_rekey:  packet: [data_rekey_needed=0, out_blocks=1058, in_blocks=62390
[2020/10/26 19:14:34.333551, 3] packet_send2:  packet: wrote [type=97, len=16, padding_size=10, comp=5, payload=5]
[2020/10/26 19:14:34.333576, 3] ssh_channel_close:  Sent a close on client channel (43:43)
[2020/10/26 19:14:34.333618, 3] ssh_packet_socket_callback:  packet: read type 96 [len=16,padding=10,comp=5,payload=5]
[2020/10/26 19:14:34.333639, 3] ssh_packet_process:  Dispatching handler for packet type 96
[2020/10/26 19:14:34.333662, 3] channel_rcv_eof:  Received eof on channel (43:43)
[2020/10/26 19:14:34.333679, 3] ssh_packet_socket_callback:  Processing 36 bytes left in socket buffer
[2020/10/26 19:14:34.333700, 3] ssh_packet_socket_callback:  packet: read type 97 [len=16,padding=10,comp=5,payload=5]
[2020/10/26 19:14:34.333720, 3] ssh_packet_process:  Dispatching handler for packet type 97
[2020/10/26 19:14:34.333742, 3] channel_rcv_close:  Received close on channel (43:43)
[2020/10/26 19:14:34.333761, 3] ssh_packet_need_rekey:  packet: [data_rekey_needed=0, out_blocks=1058, in_blocks=62390
[2020/10/26 19:14:34.333777, 3] ssh_packet_need_rekey:  packet: [data_rekey_needed=0, out_blocks=1058, in_blocks=62390
[2020/10/26 19:14:34.333799, 3] ssh_socket_unbuffered_write:  Enabling POLLOUT for socket
[2020/10/26 19:14:34.333844, 1] ssh_socket_exception_callback:  Socket exception callback: 2 (32)
[2020/10/26 19:14:34.333869, 1] ssh_socket_exception_callback:  Socket error: Broken pipe

Hi Michal,
Any leads on this issue?
also for the second part of the issue regarding notification, am i supposed to expect a notification like this?
https://github.com/CESNET/Netopeer2/issues/120#issuecomment-293258509

Okay, anything printed before the output you provided? There are, again, no hints of any problems, it would seem the client simply got disconnected. What libssh version are you using? Other than that, I think it can only be some library incompatibility.
Also, yes, that is how a normal notification should look like.

Hi Michal, Apologies on the delay with the response,
Libssh version : 0.8.0
There is nothing printed as an output to the subscribe command.
I don't find any outputs like how it is in the link i had attached in my previous comment.

Okay, then I am not able to help you. You may try reinstalling all the libraries and tools.

So, i tried re-installing all the files and again tried with the subscribe command.
This time, it prompted

subscribe
OK

nc ERROR: Session 48: SSH channel unexpected EOF.

Any leads on this ?

In this case it is the other peer (server) that unexpectedly disconnects. What libssh version are you using?

libssh version 0.8.0

On both ends in case you are not connecting to localhost? In any case, you may want to try something more recent, libssh is know to be buggy at times, 0.9.5 is tested and should work.

Okay, So i will try with the latest version and get back


Use await blocks for svelte fetch example

Excellent website!
I want to suggest using Svelte's await blocks for the fetch because I think it's more idiomatic. It's similar to the SolidJS example.

In Component Party, we must ensure snippets must got the closer implementation as possible to the other frameworks.
SolidJS in an exception because it got the native method createResource. Svelte don't have one.
And at scale, I think the actual Svelte implementation is more realistic.

Fair enough, I just assumed it was supposed to show a minimal fetch example and provided the same functionality as createResource. I do agree using writable stores is more flexible.


Support DHE by default, add DHE_PSK

Closes #65
Closes #64

Note that I managed to get interop with my implementation in NSS, but only after adding c709712.


Add Deployment Deletion to Removal Script

Add Deployment Deletion to Removal Script - https://learn.microsoft.com/en-us/cli/azure/deployment/group?view=azure-cli-latest#az-deployment-group-delete

Added removal of subscription level deployments in #189. Closed


sensor-exporter leaks memory

Looks like about 28MB over the last 24 hours.  Evidence:  process_resident_memory_bytes has grown by that much, and the following metrics have all remained stable: go_memstats_alloc_bytes, go_memstats_stack_inuse_bytes, go_memstats_heap_inuse_bytes.  Moreover there's no reason why a simple program with the deterministic behaviour it has should grow, period.

This was a problem in the gosensors package, fixed via a fork.


Reduce error boilerplate using thiserror

During the port from attohttpc to reqwest, I've noticed that there's a bunch of boilerplate code around error handling. A lot of the formatting/From impls etc can be reduced a lot by using stuff like https://lib.rs/crates/thiserror.

I've started taking a jab at this, I've identified a few more problems that I didn't see before:

There's a lot of type information lost in the current error handling. When handling. Each time an error type is converted using the ? operator, it is converted into a string. In my local draft, I've fixed this by having a big enum with the types to convert from kept in variants. All the From impls are generated by thiserror
Context for errors is kept in the same String as the error itself, by using a prefix method, which prepends a string to the error message itself. This means that even with the changes I've made before, when using the prefix method, I have to convert the error to a generic string error type, loosing the type information again. There's crates specialized on adding context to errors, like anyhow.
There's a gigantic amount of error sources that all get dumped into a flat error type. I'd think it would make sure to restructure this a bit and split them into a few smaller error types, similar to what we already have for AcmeError and HttpError, but to extend that to also add a few errors for stuff like config loading etc.

So, now with a bit of my findings documented, there's just one question I have: Do we want to keep type information of the errors we're wrapping? If so, the approach with thiserror I've started with sounds like a sensible option to me, but it's a lot more work to structure it properly. If not, we can get rid of nearly all of the error handling code if we just switch to anyhow.

Regarding the commit that just landed on main last night (e9522df), I think it'd make sense to push changes to a branch and open a PR, even when working on your own projects. This gives people the opportunity to provide feedback before things land on main, and it allows the CI to run, catching things one might have missed locally, such as the MSRV increase in df40cde34c15b8226b3ecc67279331a223580191.


scss syntax highlighting problem

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

VS Code Version: 1.83.1
OS Version: 22H2 19045.3570 windows 10 pro

The syntax highlighting feature is not working for @inculde, @use, and @container, and neither is the new CSS features like custom selectors.

@issam-seghir can you share a copy/pastable code snippet I can use to repro the issue?

p {
	font-size: $text-lg;
	font-weight: $font-normal;
	line-height: 1.75rem;
	color: $text-primary-200;

	&.tag {
		@include pseudo("", 0.5em, 0, -1.5rem) {
			@include circle(13px);
			background-color: currentcolor;
		}
		width: fit-content;
		margin: 0 auto 3rem;
		font-weight: $font-bold;
		color: $text-secondary-100;
	}
       @include pseudo("", -20%, 0, -20%, 0, "after") {
			@include sizer(calc(100% + 5rem));
					z-index: 1;
					background-image: linear-gradient(rgb(5 3 8 / 0%) 74%, #050308 91%);
	}

	@include sizer(11.375rem);

       @container (width < 400px) {
					top: -12.3rem;
				}
}

@include looks ok, but @container is not recognized:

in my experience is not work for include and mixins , i use the default theme so the theme is not the problem

Marking as a duplicate of https://github.com/microsoft/vscode/issues/81038 to be tested again once we find a new scss grammar.


Generating pie / doughnut charts

Currently I haven't been able to find a way to create any graphs other than Line, Scatter, or Bar charts. Are there any plans for adding functionality for additional kinds of charts?
Swapping to a different chart style in Excel is fairly trivial; how different are pie charts (etc), and are they feasible to implement in this lib?
Is there a way I can get a pie chart with the current functionality that I'm missing?

How about create a Excel template with pie chart and fill in the cell data dynamically? Or you can take a look at EPPlus. They have advanced chart feature included.

Yeah, I've used EpPlus in the past, it works fairly well. Depending on how critical the charts are, we might end up using it for this particular case as well, not sure yet myself. Not entirely my call there.
Out of curiosity, how complex is it to add in a different chart style? At least in Excel it seems relatively straightforward to swap between chart styles. I don't know much different they are when dealing with the raw data, though.

Btw, do you have a some specific reason that EPPlus cannot satisfy your needs? Or it's because of the license change of EPPlus?

Pie chart has been supported by NPOI 2.6.1


fix: node nqn field not shown in rest api and grpc

Signed-off-by: Abhinandan Purkait<EMAIL_ADDRESS>

bors merge

bors merge


Fix: Not working after reopen

Steps to reproduce:

Create a simple app that has a button to open the qr reader
Run the app on Android
Click the button and see the camera opens
Use the back button to close the app (NOT FORCE CLOSE)
Reopen the app by clicking the launcher icon
Click on the button again to open the qr reader -> Nothing happens (console says that no plugin is registered on channel qrcodereader).

The reason for that error is:
The plugins are cleaned up after the app is closed. But the instance you keep is not cleaned up. So when the app opens again, it tries to register all plugins. But because you still have the instance, you don't do anything. So the plugin does not get registered.
With the fix it will work correctly (tested it locally).
Would be nice if this gets merged in soon :). Thx!

Thanks for merging it in! Looking forward to a new release at some point soon :)


Docker for v2

Is there a docker build for v2 yet?

At the moment you can access v2 via Docker using the dev branch. https://microbadger.com/images/starbix/synclounge:dev
However it is completely undocumented and not user friendly due to it being a work-in-progress. I'll update the docs when we merge v2 in to master but until then there probably won't be much.


JSON was only assumed and could be overridden

Is it the only place where you need to parse content in json format for the AZ CLI ?

it's the only place I could see - we tend to ask for tsv when we want specific values


add hellaswag and mmlu PyTorch reference eval

it looks pretty bad honestly, the examples themselves, but i'm told it is predictive... hmm
small few examples
Context:
 A person is playing bagpipes out in a park. A man and two boys watching from a far. the camera
Endings:
0 (loss: 2.5237) shoots areas all around the park while the bagpipes play.
1 (loss: 4.7942) is covered to the boy that is playing there.
2 (loss: 4.6865) then goes black and we see a black opening scene.
3 (loss: 2.4973) watching the boy and boy as they play a game of drums.
predicted: 3, actual: 0

Context:
 He then takes the knife and sharpens it against the wood piece. He then notices a little black and green poisonous frog sitting next to him. the frog
Endings:
0 (loss: 3.2555) eventually gets to get up and marches out of the room waving its body about.
1 (loss: 3.0197) then starts to get up from the chair and begins walking towards the camera.
2 (loss: 4.5130) then escapes and jumps away.
3 (loss: 3.8115) is acting crazy and attacking him while he is cooking.
predicted: 2, actual: 2

Context:
 A person is seen throwing plaster onto a wall while the camera follows the person close behind. the person
Endings:
0 (loss: 73.8425) continues throwing ingredients down and leads into a person kicking a dirty toilet.
1 (loss: 49.9995) gradually throws more and more onto the wall and the camera pans over the finished product.
2 (loss: 69.1077) then uses paper to spread it all over the wall followed by others putting paper through with the plaster.
3 (loss: 63.4829) is now seen putting wax all along the wall while still looking back to the camera.
predicted: 1, actual: 1

Context:
 We see a bottle of face wash. we
Endings:
0 (loss: 25.8581) see a newspaper story.
1 (loss: 36.2495) see four cookies in a pan.
2 (loss: 36.0045) see a person holding face wash then putting it on their face.
3 (loss: 28.9292) see a tool on a table.
predicted: 0, actual: 2

Note that the typical style of this eval is multiple choice, i.e. present the 4 candidates and have the model pick the best one among them. So the model gets to reason discriminatively because it sees all 4 options.
Here, because these models are so low capability, they cannot do multiple choice. So instead we just create 4 parallel examples and evaluate the likelihood of each individual choice all by itself, and pick the one with the highest likelihood.
This upper bounds your performance well below the peak performance (by 10-20%) but I am told it is still predictive and smooth.

I added MMLU as well:
gpt2 (124M) ~= 25% (chance)
gpt2-xl (1558M) = 27.00% ...
And HellaSwag:
gpt2 (124M) = 28.2%
gpt2-xl (1558M) = 39.22%
TLDR MMLU is way too hard for this scale, but HellaSwag shows some signal, so it is a likely candidate for our GPT-2 repro eval.

Fixed a bug where the loss was off by 1. We have:
HellaSwag:
gpt2 (124M)

eleuther harness reports acc 28.92%, acc_norm 31.14% (multiple choice style)
this script: 10042 acc: 0.2859 acc_norm: 0.2955 (completion style)

gpt2-xl (1558M)

eleuther harness reports acc 40.04%, acc_norm 50.89% (multiple choice style)
this script: 10042 acc: 0.3842 acc_norm: 0.4893 (completion style)

i..e. the dynamic range is ~ok, in that we have:

25% random chance
124M: 29.55%
1558M: 48.93%

and then GPT-3 also reports on Hellaswag and cites similar balpark numbers, though a bit improved, likely due to the much longer training (100B -> 300B tokens) and better dataset. And also because I think it is doing multiple choice instead of simple completion. GPT-3 paper reports 33.7 for ~124M, and 54.7 for ~1558M size. In Appendix H.
MMLU
MMLU in comparison is:

25% random chance
124M: 27.2%
1558M: 30.35%

The dynamic range here is a bit too low.

Example eleuther harness eval for gpt2-xl command:
lm_eval --model hf     --model_args pretrained=gpt2-xl     --tasks hellaswag     --device cuda:0     --batch_size 16


Docker Image No Such Host for docker.getcollate.io

the image repository is mentioned as docker.getcollate.io/openmetadata/server but there no such host so insted i have used docker pull openmetadata/server:1.1.7

@preetsindhal  docker.getcollate.io/openmetadata/server is correct. Check you are pulling with the appropiated tag version or have a network issue.


Cross-DB update-or-insert support (SQL2003 MERGE statement)

This is a wishlist item.
Would it be possible to support an update-or-insert operation in a way that's portable across databases?  The Postgres driver already has upsert(), is it possible/feasible/desirable to extend this to all drivers, and translate it into either the database-specific version of it or into a slower-but-portable version?
Thank you!

I believe you are looking for replace_into (which was insert_or_replace in 0.16)


emacsql-memory middleware out of memory when attempting to use Magit

What did you expect to happen?
Magit should work as expected.
What actually happened?
Magit does not open, raises emacsql-memory middleware out of memory error each time.
Video: https://streamable.com/wakc0s
Debugger entered--Lisp error: (emacsql-memory "middleware out of memory")
  signal(emacsql-memory ("middleware out of memory"))
  #f(compiled-function (_ code message) "Get condition for MESSAGE provided from SQLite." #<bytecode 0x287b80d>)(#<forge-database forge-database-2cb5ab0> 7 "middleware out of memory")
  apply(#f(compiled-function (_ code message) "Get condition for MESSAGE provided from SQLite." #<bytecode 0x287b80d>) #<forge-database forge-database-2cb5ab0> (7 "middleware out of memory"))
  emacsql-handle(#<forge-database forge-database-2cb5ab0> 7 "middleware out of memory")
  #f(compiled-function (connection) "Parse well-formed output into an s-expression." #<bytecode 0x2878b99>)(#<forge-database forge-database-2cb5ab0>)
  apply(#f(compiled-function (connection) "Parse well-formed output into an s-expression." #<bytecode 0x2878b99>) #<forge-database forge-database-2cb5ab0> nil)
  emacsql-parse(#<forge-database forge-database-2cb5ab0>)
  #f(compiled-function (connection sql &rest args) "Send SQL s-expression to CONNECTION and return the results." #<bytecode 0x287873d>)(#<forge-database forge-database-2cb5ab0> [:pragma (= busy-timeout $s1)] 15000)
  apply(#f(compiled-function (connection sql &rest args) "Send SQL s-expression to CONNECTION and return the results." #<bytecode 0x287873d>) (#<forge-database forge-database-2cb5ab0> [:pragma (= busy-timeout $s1)] 15000))
  #f(compiled-function (&rest cnm-args) #<bytecode 0x2e8cf81>)(#<forge-database forge-database-2cb5ab0> [:pragma (= busy-timeout $s1)] 15000)
  apply(#f(compiled-function (&rest cnm-args) #<bytecode 0x2e8cf81>) #<forge-database forge-database-2cb5ab0> [:pragma (= busy-timeout $s1)] 15000)
  #f(compiled-function (connection sql &rest args) #<bytecode 0x287a4c1>)(#f(compiled-function (&rest cnm-args) #<bytecode 0x2e8cf81>) #<forge-database forge-database-2cb5ab0> [:pragma (= busy-timeout $s1)] 15000)
  apply(#f(compiled-function (connection sql &rest args) #<bytecode 0x287a4c1>) #f(compiled-function (&rest cnm-args) #<bytecode 0x2e8cf81>) (#<forge-database forge-database-2cb5ab0> [:pragma (= busy-timeout $s1)] 15000))
  #f(compiled-function (&rest args) #<bytecode 0x2e8d0c5>)(#<forge-database forge-database-2cb5ab0> [:pragma (= busy-timeout $s1)] 15000)
  apply(#f(compiled-function (&rest args) #<bytecode 0x2e8d0c5>) #<forge-database forge-database-2cb5ab0> ([:pragma (= busy-timeout $s1)] 15000))
  emacsql(#<forge-database forge-database-2cb5ab0> [:pragma (= busy-timeout $s1)] 15000)
  #f(compiled-function (#<forge-database forge-database-2cb5ab0> (:file "~/.emacs.d/.local/etc/forge/forge-database.sqlite"))
  apply(#f(compiled-function
  #f(compiled-function (&rest args) #<bytecode 0x2cb6305>)(#<forge-database forge-database-2cb5ab0> (:file "~/.emacs.d/.local/etc/forge/forge-database.sqlite"))
  apply(#f(compiled-function (&rest args) #<bytecode 0x2cb6305>) #<forge-database forge-database-2cb5ab0> (:file "~/.emacs.d/.local/etc/forge/forge-database.sqlite"))
  initialize-instance(#<forge-database forge-database-2cb5ab0> (:file "~/.emacs.d/.local/etc/forge/forge-database.sqlite"))
  #f(compiled-function (class &rest slots) "Default constructor for CLASS `eieio-default-superclass'.\nSLOTS are the initialization slots used by `initialize-instance'.\nThis static method is called when an object is constructed.\nIt allocates the vector used to represent an EIEIO object, and then\ncalls `initialize-instance' on that object." #<bytecode 0x2752909>)(forge-database :file "~/.emacs.d/.local/etc/forge/forge-database.sqlite")
  apply(#f(compiled-function (class &rest slots) "Default constructor for CLASS `eieio-default-superclass'.\nSLOTS are the initialization slots used by `initialize-instance'.\nThis static method is called when an object is constructed.\nIt allocates the vector used to represent an EIEIO object, and then\ncalls `initialize-instance' on that object." #<bytecode 0x2752909>) forge-database (:file "~/.emacs.d/.local/etc/forge/forge-database.sqlite"))
  make-instance(forge-database :file "~/.emacs.d/.local/etc/forge/forge-database.sqlite")
  #f(compiled-function (class &optional variable file debug) #<bytecode 0x287c3f1>)(forge-database forge--db-connection "~/.emacs.d/.local/etc/forge/forge-database.sqlite" t)
  apply(#f(compiled-function (class &optional variable file debug) #<bytecode 0x287c3f1>) forge-database (forge--db-connection "~/.emacs.d/.local/etc/forge/forge-database.sqlite" t))
  closql-db(forge-database forge--db-connection "~/.emacs.d/.local/etc/forge/forge-database.sqlite" t)
  forge-db()
  forge-sql([:select * :from repository :where (and (= forge $s1) (= owner $s2) (= name $s3))] "github.com" "TahaAhmedRasheed" "doom-config")
  #f(compiled-function (&rest rest) "((host owner name) &optional remote demand)\n\nReturn the repository identified by HOST, OWNER and NAME." #<bytecode 0x25da371>)(("github.com" "TahaAhmedRasheed" "doom-config") "origin" full)
  apply(#f(compiled-function (&rest rest) "((host owner name) &optional remote demand)\n\nReturn the repository identified by HOST, OWNER and NAME." #<bytecode 0x25da371>) ("github.com" "TahaAhmedRasheed" "doom-config") ("origin" full))
  forge-get-repository(("github.com" "TahaAhmedRasheed" "doom-config") "origin" full)
  #f(compiled-function (url &optional remote demand) "Return the repository at URL." #<bytecode 0x25da305>)("https://github.com/TahaAhmedRasheed/doom-config" "origin" full)
  apply(#f(compiled-function (url &optional remote demand) "Return the repository at URL." #<bytecode 0x25da305>) "https://github.com/TahaAhmedRasheed/doom-config" ("origin" full))
  forge-get-repository("https://github.com/TahaAhmedRasheed/doom-config" "origin" full)
  #f(compiled-function (demand &optional remote) "Return the current forge repository.\n\nIf the `forge-buffer-repository' is non-nil, then return that.\nOtherwise if `forge-buffer-topic' is non-nil, then return the\nrepository for that.  Finally if both variables are nil, then\nreturn the forge repository corresponding to the current Git\nrepository, if any." #<bytecode 0x25da2ed>)(full)
  apply(#f(compiled-function (demand &optional remote) "Return the current forge repository.\n\nIf the `forge-buffer-repository' is non-nil, then return that.\nOtherwise if `forge-buffer-topic' is non-nil, then return the\nrepository for that.  Finally if both variables are nil, then\nreturn the forge repository corresponding to the current Git\nrepository, if any." #<bytecode 0x25da2ed>) full nil)
  forge-get-repository(full)
  forge-bug-reference-setup()
  funcall(forge-bug-reference-setup)
  (condition-case e (funcall hook) ((debug error) (signal 'doom-hook-error (list hook e))))
  doom-run-hook(forge-bug-reference-setup)
  run-hook-wrapped(doom-run-hook forge-bug-reference-setup)
  (condition-case e (run-hook-wrapped hook #'doom-run-hook) ((debug doom-hook-error) (if debug-on-error nil (lwarn hook :error "Error running hook %S because: %s" (if (symbolp (car (cdr e))) (symbol-name (car (cdr e))) (car (cdr e))) (car (cdr (cdr e))))) (signal 'doom-hook-error (cons hook (cdr e)))))
  (let ((hook (car --dolist-tail--))) (condition-case e (run-hook-wrapped hook #'doom-run-hook) ((debug doom-hook-error) (if debug-on-error nil (lwarn hook :error "Error running hook %S because: %s" (if (symbolp (car ...)) (symbol-name (car ...)) (car (cdr e))) (car (cdr (cdr e))))) (signal 'doom-hook-error (cons hook (cdr e))))) (setq --dolist-tail-- (cdr --dolist-tail--)))
  (while --dolist-tail-- (let ((hook (car --dolist-tail--))) (condition-case e (run-hook-wrapped hook #'doom-run-hook) ((debug doom-hook-error) (if debug-on-error nil (lwarn hook :error "Error running hook %S because: %s" (if (symbolp ...) (symbol-name ...) (car ...)) (car (cdr ...)))) (signal 'doom-hook-error (cons hook (cdr e))))) (setq --dolist-tail-- (cdr --dolist-tail--))))
  (let ((--dolist-tail-- hooks)) (while --dolist-tail-- (let ((hook (car --dolist-tail--))) (condition-case e (run-hook-wrapped hook #'doom-run-hook) ((debug doom-hook-error) (if debug-on-error nil (lwarn hook :error "Error running hook %S because: %s" (if ... ... ...) (car ...))) (signal 'doom-hook-error (cons hook (cdr e))))) (setq --dolist-tail-- (cdr --dolist-tail--)))))
  doom-run-hooks(change-major-mode-after-body-hook special-mode-hook magit-section-mode-hook magit-mode-hook magit-status-mode-hook)
  apply(doom-run-hooks (change-major-mode-after-body-hook special-mode-hook magit-section-mode-hook magit-mode-hook magit-status-mode-hook))
  run-hooks(change-major-mode-after-body-hook special-mode-hook magit-section-mode-hook magit-mode-hook magit-status-mode-hook)
  apply(run-hooks (change-major-mode-after-body-hook special-mode-hook magit-section-mode-hook magit-mode-hook magit-status-mode-hook))
  run-mode-hooks(magit-status-mode-hook)
  magit-status-mode()
  magit-setup-buffer-internal(magit-status-mode nil ((magit-buffer-diff-args ("--no-ext-diff")) (magit-buffer-diff-files nil) (magit-buffer-log-args ("-n256" "--decorate")) (magit-buffer-log-files nil)))
  magit-status-setup-buffer("c:/Users/brain/.doom.d/")
  magit-status(nil ((4 . 4) (("c:/Users/brain/.doom.d/" "remote" "get-url" "origin") . "https://github.com/TahaAhmedRasheed/doom-config") (("c:/Users/brain/.doom.d/" . magit-toplevel) . "c:/Users/brain/.doom.d/") (("c:/Users/brain/.doom.d/" "rev-parse" "--show-toplevel") . "C:/Users/brain/.doom.d")))
  funcall-interactively(magit-status nil ((4 . 4) (("c:/Users/brain/.doom.d/" "remote" "get-url" "origin") . "https://github.com/TahaAhmedRasheed/doom-config") (("c:/Users/brain/.doom.d/" . magit-toplevel) . "c:/Users/brain/.doom.d/") (("c:/Users/brain/.doom.d/" "rev-parse" "--show-toplevel") . "C:/Users/brain/.doom.d")))
  call-interactively(magit-status nil nil)
  command-execute(magit-status)

The preceding backtrace was produced using the "Doom + modules - private config" sandbox
It's worth mentioning Magit worked fine before (at least for the subset of features I'm in habit of using)... until it decided to automatically compile emacsql:
c:/Program Files/LLVM/bin/clang.exe -Ic:/Users/brain/.emacs.d/.local/straight/build-27.2/emacsql-sqlite/sqlite -O2 -DSQLITE_THREADSAFE=0 -DSQLITE_DEFAULT_FOREIGN_KEYS=1 -DSQLITE_ENABLE_FTS5 -DSQLITE_ENABLE_FTS4 -DSQLITE_ENABLE_FTS3_PARENTHESIS -DSQLITE_ENABLE_RTREE -DSQLITE_ENABLE_JSON1 -DSQLITE_SOUNDEX c:/Users/brain/.emacs.d/.local/straight/build-27.2/emacsql-sqlite/sqlite/sqlite3.c c:/Users/brain/.emacs.d/.local/straight/build-27.2/emacsql-sqlite/sqlite/emacsql.c -o c:/Users/brain/.emacs.d/.local/straight/build-27.2/emacsql-sqlite/sqlite/emacsql-sqlite.exe

Describe your attempts to resolve the issue

Deleting straight, and running doom sync

Deleting the emacsql-sqlite binary in straight\build-27.2\emacsql-sqlite\sqlite to rebuild the binary

Running M-: (emacsql-sqlite-compile) to rebuild the binary

Steps to reproduce
Not sure. Maybe try the following:

Get my version of Doom on Windows 10
Get clang from LLVM for 64-bit Windows
Run (emacsql-sqlite-compile)
Open magit

System Information
https://pastebin.com/BbGdQTbJ

From the module documenation for magit:

=forge= was modified to defer compilation of emacsql-sqlite until you try to
use forge, rather than when magit first loads (which could be as soon as
startup).

The thing is, right now I do not need to use forge, but I can't figure out how to disable it either, since I don't have the +forge flag for magit in my modules.

The issue was found to lie in this particular commit to Doom: https://github.com/hlissner/doom-emacs/commit/2d3a68df496f300ac219db124f44ff1bde90e464

I am experiencing this same issue.

It appears that the code-review lists forge as a dependency, and some of code-review's submodules pull in forge, so it is unavoidable. Here are two suggestions:

Try enabling the +forge flag on :tools magit? There are some hacks in the module's forge config that defer compilation that aren't in effect without this flag. If forge is going to be available either way, may as well enable it.
Alternatively, disable the code-review package:;; add to $DOOMDIR/packages.el
(package! code-review :disable t)

Then run doom sync -u and restart Emacs.

As of f491dd9 code-review is now gated behind the +forge flag, which should resolve this issue. Let me know if that isn't the case and I'll reopen it. Thanks for bringing it to my attention!

I did a "clean" install by deleting .local, then running the following doom commands in order: install, upgrade, sync, build. I can confirm that after opening a source-controlled file that I am no longer getting the "middleware out of memory" bug. (Windows 10)


Terminal is starting up at a size that's different from initialRows/initialCols

Environment
Windows build number: Microsoft Windows [Version 10.0.18362.264]
Windows Terminal version (if applicable): 8ffff8ea 0.2.1991.0
Any other software? WSL

Steps to reproduce
The relevant-looking parts of profiles.json are:
{
    "globals" :
    {
        "defaultProfile" : "{c6eaf9f4-32a7-5fdc-b5cf-066e8a4b1e40}",
        "initialCols" : 80,
        "initialRows" : 40,
    },
    "profiles" :
    [
        {
            "commandline" : "wsl.exe -d Ubuntu-18.04",
            "fontFace" : "DejaVu Sans Mono for Powerline",
            "fontSize" : 9,
            "guid" : "{c6eaf9f4-32a7-5fdc-b5cf-066e8a4b1e40}",
            "padding" : "0, 0, 0, 0"
        }
    ]

Expected behavior
I should see an 80x40 terminal.
Actual behavior
I get an 80x37 terminal, with extra blank horizontal space after the last usable column:

There appears to be two separate issues here.

Created terminal windows are consistently 3 rows smaller than the value for initialRows.
e.g. initialRows 27 gives a terminal size of height 24
Confirmed using powershell's "$Host.UI.RawUI.WindowSize.Height" and Ubuntu bash's "stty size" in their respective tabs.

Extra space appears to the right and bottom of the terminal window, but this isn't part of the terminal's reported size, and doesn't affect output only how the windows looks (at least when checked using an 80x24 (i.e. setting an 80x27, see point 1) terminal window).
I suspect the window is being drawn at the maximum size it can be without becoming an extra column wider or row taller, Perhaps the pixel size is calculated and 1 is subtracted to avoid a fence-post error, but this subtraction is from the size in pixels, and not the the number of rows or columns.

I can't see a style guide for Bug reporting - is the right thing to do to create two new bugs referencing this one (and then close this one)? To spin one issue out into a new bug and keep this bug open for the other one?

a

@culcube I'm fairly certain this is all due to the same root cause, so they can all stay in this issue. I believe the root cause is that we're getting the amount of space we need for the actual terminal pane itself, but then no accounting for the window frame. That window frame rounds up to roughly three characters tall on top/bottom, and one character on the left/right. If we accounted for those dimensions correctly when creating the window, both problems would go away.
I believe the IslandWindow is doing this correctly, but NonClientIslandWindow is where the bug lies.

@zadjii-msft I found the source of the issue.  It's padding, the scrollbar, and the tab UI.  I have tabs, scrollbar, and padding disabled, and I get pixel-perfect accuracy.

I'd say it's just tab UI, because I previously had a scrollbar set as hidden and padding set to 5px each. Disabling the tab UI solved the issue, at least in my case.

Not sure if it's worth mentioning, for me, it's always 2 rows smaller (instead of 3).

This has still not solved the scaling issue with padding (#4077).
I'm testing with terminal v0.10.781.0, which should include commit 0e33d86.
Under 150% DPI:

padding 0 does not cause any issue, console size is at 80x24
padding 50 results in a 76x22 console
padding 100 and it becomes 72x20

Under 100% DPI:

padding 0 is 80x24
padding 100 is 80x24

Huh, thanks.


Implement logging

Implement logging with NLog
Should we log to

Database
Blob Storage
Application Insights
A queue (for storage in a database)

Implemented with ac71af4690b4ef44a8600c6f82fed0693fa83617


Mix formatter for ~Z

I implemented this as an external package: https://github.com/zigler_formatter

Can you pr a link to readme and I'll close the issue?

I believe this should be closed per #294


GitHub Actions version matching

Is your feature request related to a problem? Please describe.
There are 16 entries for ecosystem: GitHub Actions currently in the database, https://osv.dev/list?ecosystem=GitHub+Actions&q=
All entries provide semver-compatible entries

$ for vuln in GHSA-7f32-hm4h-w77q GHSA-ghm2-rq8q-wrhc GHSA-mcph-m25j-8j63 GHSA-99jg-r3f4-rpxj GHSA-8v8w-v8xg-79rf GHSA-hw6r-g8gj-2987 GHSA-h3qr-39j9-4r5v GHSA-rg3q-prf8-qxmp GHSA-6q4m-7476-932w GHSA-p756-rfxh-x63h GHSA-2c6m-6gqh-6qg3 GHSA-f9qj-7gh3-mhj4 GHSA-4xqx-pqpj-9fqw GHSA-634p-93h9-92vh GHSA-g86g-chm8-7r2p GHSA-4mgv-m5cm-f9h7; do curl -s "https://api.osv.dev/v1/vulns/$vuln" | jq -c '.affected[0].ranges'; done
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.1.1"}]}]
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"17"}]}]
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"41"}]}]
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0.6.1"}]}]
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"7.0.7"}]}]
[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}]
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.4.2"}]}]
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2"}]}]
[{"type":"ECOSYSTEM","events":[{"introduced":"4.0.0"},{"fixed":"4.4.1"}]}]
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3"}]}]
[{"type":"ECOSYSTEM","events":[{"introduced":"2.294.0"},{"fixed":"2.296.2"}]}]
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.7.5"}]}]
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.0.1"}]}]
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1"}]}]
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0.0.19"}]}]
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.2.0"}]}]

I know https://osv.dev/vulnerability/GHSA-7f32-hm4h-w77q exists.
I know https://github.com/rlespinasse/github-slug-action/releases/tag/1.0.0 exists, and is affected by the vulnerability.
But I can't query to match the two: $ curl -sd '{"package": {"ecosystem":"GitHub Actions", "name":"rlespinasse/github-slug-action"}, "version":"1.0.0"}'  https://api.osv.dev/v1/query
Describe the solution you'd like
Treat the GitHub Actions ecosystem as (best effort?) SemVer: https://github.com/google/osv.dev/blob/46c25dafc776d429ac46cb112fb1dffb98b9cc90/osv/ecosystems/_ecosystems.py#L51
Describe alternatives you've considered
Querying by the commit referenced by the 1.0.0 tag: curl -sd '{"package": {"ecosystem":"GitHub Actions", "name":"rlespinasse/github-slug-action"}, "commit":"9671420482a6e4c59c06f2d2d9e0605e941b1287"}'  https://api.osv.dev/v1/query
This returns https://osv.dev/vulnerability/GHSA-6q4m-7476-932w - which I don't think impacts 1.0.0, and does not return https://osv.dev/vulnerability/GHSA-7f32-hm4h-w77q, which I think does.
I mostly don't understand the implications of this change. Actions may be referred to commit, tag (i.e. where semver would appear) or branch.
Additional context
The official versioning scheme for Actions is here: https://docs.github.com/en/actions/using-workflows/workflow-syntax-for-github-actions#jobsjob_idstepsuses
Semver is implied/encouraged, but not enforced.

best effort semver

This might look similar to https://github.com/google/osv.dev/blob/46c25dafc776d429ac46cb112fb1dffb98b9cc90/osv/ecosystems/rubygems.py#L33

fwiw I asked GitHub about this a while ago when I was looking to support GHA in my CLI and the scanner (which I'll get back to one day 😅), and they said they expect them to be semver on their end

@thepwagner feel free to send a PR to s/OrderingUnsupportedEcosystem/SemverEcosystem/ for this ecosystem.
I think the challenges we may then run into will be:

reprocessing the records due to #2018
the originating records declaring their ranges as ECOSYSTEM not SEMVER (but if they get changed, that might make the first challenge less of a barrier)

If I recall correctly from https://github.com/bitnami/vulndb/issues/336, changing OSV.dev's expectation overrides the range type, which would then not require any record changes at the source, but then takes us back to my first point here 😃

Was this ever fixed? I see @thepwagner closed it on Aug 12, but I can't find a PR from around then that looks like it addresses it.
In my testing, the current non-semver behavior is still causing issues. For example, I expect this to return at least GHSA-4xqx-pqpj-9fqw:
curl -d '{"package": {"name": "gaatlassian/gajira-create"}, "version": "1.0.0", "ecosystem": "GitHub Actions"}' "https://api.osv.dev/v1/query"

but instead it returns a bare response of {}.

Sorry for the confusion: I closed due to the stalebot and I don't have time to contribute a fix.


Implement simplified homepage

To prepare the Beta for a full production release, we should update the homepage (see #775) to provide additional relevant content and getting started quick links.
Below is an initial design specification for a simplified, streamlined homepage that focusses on:

Search
Brief explanation of the Platform
Getting started quick links

Design specification

For this implementation, please consider the following:

The search box should have a maximum width to ensure that it does not get too wide on large screens
The network motion graphic background should take the entire window space as is the case with the current Beta version
The down arrow acts as a visual cue to encourage the user to click to read the content below the fold
Overall metrics (e.g. number of diseases, targets, associations, data sources) will be moved to a separate data metrics page that provides more robust analytics

Content
Text

The Open Targets Platform is a comprehensive tool that supports systematic identification and prioritisation of potential therapeutic drug targets.
By integrating publicly available datasets along with data generated by the Open Targets consortium, the Platform builds and scores target-disease associations to assist in drug target identification and prioritisation. It also integrates relevant annotation information about targets, diseases, phenotypes, and drugs, as well as their most relevant relationships.
The Platform is a freely available resource that is actively maintained with bi-monthly data updates. Data is available through an intuitive user interface, an API, and data downloads. The pipeline and infrastructure codebases are open-source and the licence allows the creation of self-hosted private instances of the Platform with custom data.

Get started links

FontAwesome icon
Link
Text

download
TBC
Download all of our datasets

laptop-code
TBC
Access data with our GraphQL API

question-circle
TBC
Check out our Platform documentation

file-alt
TBC
Read our latest Platform publications

comment-dots
TBC
Join the Open Targets Community

@LucaFumis I have finalised the relevant URLs for the "Get started" links

FontAwesome icon
Link
Text

download
/downloads/data
Download all of our datasets

laptop-code
https://platform-docs.opentargets.org/data-access/graphql-api
Access data with our GraphQL API

question-circle
https://platform-docs.opentargets.org/
Check out our Platform documentation

file-alt
https://platform-docs.opentargets.org/citation
Read our latest Platform publications

comment-dots
https://community.opentargets.org/
Join the Open Targets Community

Ticket closed as work completed and reviewed and merged into main


Metadata robots noindex causes build error

Have you read the Contributing Guidelines on issues?

[X] I have read the Contributing Guidelines on issues.

Prerequisites

[X] I'm using the latest version of Docusaurus.
[X] I have tried the npm run clear or yarn clear command.
[X] I have tried rm -rf node_modules yarn.lock package-lock.json and re-installing packages.
[ ] I have tried creating a repro with https://new.docusaurus.io.
[ ] I have read the console error message carefully (if applicable).

Description
Faced error when tried to build the application with metadata: [{name: 'robots', content: 'noindex'}] set in docusaurus.config.js. This is a recommended way of hiding the website from search crawlers. I was also able to avoid the issue by using an alternative way of applying noindex in metadata.
Reproducible demo
https://github.com/chernodub/docusaurus-build-issue-repro
Steps to reproduce
With attached demo:

Clone the repo
npm install
npm run build

With clean docusaurus build:

npx create-docusaurus@latest my-website classic
cd my-website
Add metadata: [{name: 'robots', content: 'noindex'}] to docusaurus.config.js
npm run build

Expected behavior
npm run build finishes without errors
Actual behavior
npm run build fails with an error
node:events:505
      throw er; // Unhandled 'error' event
      ^

EmptySitemap: You ended the stream without writing anything.
Emitted 'error' event on SitemapStream instance at:
    at emitErrorNT (node:internal/streams/destroy:157:8)
    at emitErrorCloseNT (node:internal/streams/destroy:122:3)
    at processTicksAndRejections (node:internal/process/task_queues:83:21)

Your environment

Docusaurus version used: 2.0.0-beta.22
Environment name and version (e.g. Chrome 89, Node.js 16.4): Node.js 16.6.0
Operating system and version (e.g. Ubuntu 20.04.2 LTS): macOS Monterey 12.4

Self-service

[ ] I'd be willing to fix this bug myself.

-a^10

motherboard


Export label empty files - yolov8 export confusion

Actions before raising this issue

[X] I searched the existing issues and did not find anything similar.
[X] I read/searched the docs

Steps to Reproduce
We don't have the tags in the exports. I have tried all versions of the tags: https://docs.cvat.ai/docs/manual/advanced/formats/#data-export-formats
the generated .txt label files have no value. yet my jobs are completed.

Expected Behavior
export with dashboard or sdk but the same problem.
Possible Solution
No response
Context
No response
Environment
No response

Which formats do not support tags?

Its ok sry, it was my mistake

hum,  I tested the two latest export formats YOLOv8 Detection 1.0 and YOLOv8 Oriented Bounding Boxes 1.0 but the label files were empty before I used COCO 1.0 (which still works). I have a dataset with maskshape (Oriented Bounding Boxes) for detection.

If you want to export everything (or almost everything), please, use CVAT or Datumaro formats.

I have a dataset with maskshape (Oriented Bounding Boxes) for detection ...... works with YOLOv8 Segmentation 1.0

Oriented bounding box may be easliy converted to a mask. That is why we support such conversion.
We won't add support for an object to a format if specification of that format does not support such objects. For example YOLOv8 does not have unified format structure for all shapes. That is why we devided it to several formats.


Lock enviroment and bindings?

Currently, objects generated from Structs and functions generated from methods of that Struct are not locked, so they may be overwritten by accident.
I suppose it's okay to lock these in the wrapper file.
For example:
`.savvy_wrap_FooWithDefault` <- function(ptr) {
  e <- new.env(parent = emptyenv())
  e$.ptr <- ptr
  lockBinding(".ptr", e)
  e$`default_value_method` <- `FooWithDefault_default_value_method`(ptr)
  lockBinding("default_value_method", e)

  class(e) <- "FooWithDefault"
  lockEnvironment(e)
  e
}

Can't be certain what you want to achieve here, but in nanonext I simply define the methods for  [[<- and $<- as no-ops for the relevant class.
This avoids these cumbersome operations every time, and still allows modification using assign() in case you actually want to do that in other parts of your code.

they may be overwritten by accident.

What accident did you experience?

I simply define the methods for [[<- and $<- as no-ops for the relevant class.

Thanks for the idea, this sounds simple.

What accident did you experience?

I haven't had any real trouble, but I imagine that there might be a case where you might want to allow updates via $ in a dataframe-like object, just as the arrow Table built on R6 allows column updates via $.
In that case I figured something like .ptr would need to be prevented from being overwritten.

I see, thanks for the details.


Simple annoton form suggestion: Add a “clone annotation” option

From @sabrinatoro on October 13, 2017 18:36
It would be useful to add an “clone annotation” option.
This would re-populate the form with the elements of an existing annotation (same as the current “edit” option), then allow curators to change one (or more) of the elements and save as a new annotation.
This is a useful tool when we need to make multiple annotations which differ by only one element.
If it would be helpful, I can demonstrate similar “cloning” options we frequently use in ZFIN.
Copied from original issue: geneontology/noctua#515

Dupe of #5


Wrap NFT request

Native NFT chainid (Andromeda 1088, Stardust 588, Ethereum 1, Rinkeby 4): 4
Native NFT contract address:  0xf1cfb325f6efe0d0542cec391a36c19a30ed33d2
Deployed wrap NFT contract address: 0x97aed93f43eb7353120383585732643f679af579
Transaction hash of the contract deployment: 0xdda99f0b1535e965307c680956bee49ddb29958aa8edd7a505dd9105d5477a61

it's already configured


Resolve aliases arent resolved

Describe the bug
I created an alias to an external folder.
Works fine in code, but seems the auto import doesnt resolve it.
Also the absense of an error due of unabling to identify an existing folder makes the error obscure, like described here:
https://github.com/antfu/unplugin-vue-components/issues/609
the same bug happens in unplugin-vue-components - no aliases are resolved.
that's a big problem because it's impossible to use the auto import and vue components universally in the both
project and frontend directories because the relative path ../../../frontend is resolved differently and doesnt work in the frontend directory
export default defineConfig(({ command, mode, ssrBuild }) => ({
    resolve: {
        alias: {
            '@common': fileURLToPath(new URL('../frontend', import.meta.url)),
        }
    },
    plugins: [
        vue(),
        Components({
            dirs: ['.', '../../../frontend/components'],
            extensions: ['vue'],
        }),
        AutoImport({
            imports: [
                'vue',
                'vue-router',
                {
                    'vue-i18n': ['useI18n'],
                    'axios': [['default', 'axios']],
                    '@common/utils': ['useModel'],
                }
            ],

Reproduction
Provide an alias to an external folder in the imports option
System Info
System:
    OS: Linux 5.4 Ubuntu 20.04.5 LTS (Focal Fossa)
    CPU: (2) x64 Intel Xeon Processor (Icelake)
    Memory: 607.58 MB / 3.84 GB
    Container: Yes
    Shell: 5.0.17 - /bin/bash
  Binaries:
    Node: 14.21.3 - /usr/local/bin/node
    npm: 6.14.18 - /usr/local/bin/npm

Used Package Manager
npm
Validations

[X] Follow our Code of Conduct
[X] Read the Contributing Guide.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Check that this is a concrete bug. For Q&A, please open a GitHub Discussion instead.
[X] The provided reproduction is a minimal reproducible of the bug.

it is a good point, i think the feature requires the author @antfu to see if it is necessary.


Add SharedAsyncSequence & ThrottleAsyncSequence

Not sure why but from forked repo i cannot point to PR which i already created. So i created PR which points to my main which already have throttle changes, so you can take a look here: https://github.com/m1entus/Asynchrone/pull/1/files.
This PR add shread streams in some way, because originally when you try to await same stream (same Iterator) from multiple Tasks, you will get "_Concurrency/AsyncStreamBuffer.swift:253: Fatal error: attempt to await next() on more than one task" because originally they didn't make AsyncStream Sendable.
Using SharedAsyncSequence we can share stream across multiple Tasks, this could be helpfull if for example we might to share State stream publisher to multiple objects.

Thankyou!


508 Bug: New Record MP Focus

https://ecmps-tst.app.cloud.gov/workspace/monitoring-plans
Create/cancel loses focus when creating a new record - focus should go back to create button

Testing complete, focus is now being returned to the create button


FastTypeTag bad conversion?

I wonder why this happens:
case class Map[T, S]( ... )
val tag = implicitly[FastTypeTag[Map[List[Int], List[String]]]]
println(tag) // shows Map[t,s] where t,s are type variables

When using AnyUnpickler one wants to unpickle anything inferred from its type. In this case, reflection fails to create an unpickler for that type because t and s are unknown. Why aren't t and s concrete when they could be List[Int] and List[String]? Is this a bug? Otherwise, why doesn't FastTypeTag constructs the tag from the full type?
/cc @jsuereth since he's been refactoring FastTypeTag lately.

@jvican Looks like that's a bug.   There's a bit of funny-behavior regarding type parameters (usually my fault) in the macros.

Good, tomorrow I'll work on a fix for this.

The problem here is that we create FastTypeTags for type variables. I'm not sure if we should. Let me explain it with a bit of code:
trait Foo
case class Bar[T](v: T)
case class Zaz(i: Int)

Now, let's create a concrete pickler for Foo:
def pickle(f: Foo, b: PBuilder): Unit = {
  f match {
    case b: Bar[t] =>
      // t is a type variable and BarPickle gets a `FastTypeTag`
      // if we do not put a concrete tag here, one will be created for `t`
      barPicklerUnpickler.pickle(b)
    case z: Zaz => ???
  }
}

I'm not very sure if this behavior is intended by scala pickling. But since a FastTypeTag is a witness of a type, and we expect this type to be concrete, wouldn't be sensible to still consider this as a bug?

yes, I agree it looks like a bug.  We shouldn't be able to grab a static type tag without some witness of t's fast type tag


Note X text in pdf

Hey,
I see a lot of Note  fields across my pdf
for example:

What does this mean? There is no Note X in the original sbom json file.
I ran:
sbom2doc --debug --include-license -i sbom.json -f pdf -o sbom.pdf
output with debug:

The note field is because the column width doesn't allow long text. Most download locations have long URLs which overflow the width of the column in the table which is why they are replaced with a note.
Not pretty I know and not perfect as you can see. If anyone has a better idea, please share!


[Bug]: When the OB version is 3. x, the backup database cannot open the table

ODC version
odc430
OB version
ob3.x
What happened?

What did you expect to happen?

How can we reproduce it (as minimally and precisely as possible)?
Create a backup database for ob3. x
Open Table
Anything else we need to know?
No response

fixed:

MySQL backup database unable to open table

the api gives response bug the front end miss it~

fixed in dev-4.3.0

Incorrect error report

Fixed In Commit 5c3a2ebf39c3814e65651b9a605fe2b690f504db
------
xiaokang
Fri Jun 7 11:02:37 2024 +0800

pass