Allow casks to be installed using the cask-source API

[x] Have you followed the guidelines in our Contributing document?
[x] Have you checked to ensure there aren't other open Pull Requests for the same change?
[x] Have you added an explanation of what your changes do and why you'd like us to include them?
[ ] Have you written new tests for your changes? Here's an example.

[x] Have you successfully run brew typecheck with your changes locally?
[ ] Have you successfully run brew tests with your changes locally?

This PR allows casks to be installed using the cask-source API when HOMEBREW_JSON_CORE is set.
Now that this applies to casks, I think it may make more sense for the environment variable to be named HOMEBREW_INSTALL_FROM_API (or similar). Thoughts? This should be a simple change (just replace all occurrences) so I'll do this in a separate PR.
In only somewhat major change is that casks now have Cask::Cask#source method that returns the source code of the cask (or nil if it wasn't set, although I don't know of a situation where this would happen because all casks loaded with Cask::CaskLoader should have it set).

The biggest issue I'm currently having is that checking whether a cask is outdated can be a bit problematic because casks can have different versions based on the operating system (e.g. onyx). Because the versions API is generated on a runner with macOS 10.15.7. This means that for casks like onyx, the version listed in /api/versions-casks-json is only the Catalina version. Therefore, Cask::Cask#outdated? return true for onyx on my Big Sur machine prompting me to upgrade the cask. Yet, when I run brew upgrade, it uses the source which defines a newer version (because it now knows I'm on Big Sur). This means I'm in a cycle where it installs the correct version of the cask, prompts me to upgrade, then upgrades to the exact same version.
Any ideas on how to move forward here? I'm wondering if we need to refine the versions API to include information for every (supported at a minimum) OS. This would also require some work to change how MacOS.version works (unless we actually want to run the versions API generator on every OS.
I wonder if in Homebrew/formulae.brew.sh we could override the MacOS.version method to manually override an check each OS option. Is that the best way to move forward here?

Review period will end on 2021-08-17 at 00:00:00 UTC.

I wonder if in Homebrew/formulae.brew.sh we could override the MacOS.version method to manually override an check each OS option. Is that the best way to move forward here?

This makes sense to me 👍🏻. I think it would be good for brew info --json to be able to output all this information.

Review period ended.

I think it would be good for brew info --json to be able to output all this information.

I agree, but I'm a bit unsure how to convey this without making a backwards-incompatible change. Any thoughts?

I agree, but I'm a bit unsure how to convey this without making a backwards-incompatible change. Any thoughts?

I think we still provide the current version based on the version it's generated on but have a new versions key or similar which has macOS version subkeys. Thoughts?

Yeah, that makes sense. Good thinking. I also know that we may have a few formulae with a similar issue for their dependencies. I'll give some thought to handling those as well.
It might take me some time (I'm moving into school next week so there's a lot to do)

It might take me some time (I'm moving into school next week so there's a lot to do)

No rush, good luck!


screenDistance

Importance: 0
Issue: Isn't this code rather inefficient? And, what does it do?
function screenDistance() {
var temp = f.getScreenDistance();
return temp;
}

That function isn't used anymore. It looks like that for debug purposed. What it did was figure out the distance from the middle of the screen to the closest edge. Then it would know if a cell was off the screen. The problem is that it would break when zooming in or out.

Ok, then you could close it.

When you open an issue, you can also close it yourself. ;)

Ok, there is a button at the bottom... Thanks! :D

:D


Make the setup-device command work right with TriggerResubscriptionCommand.

When an MTRDevice was set up via the setup-device command, not via CHIPCommandBridge::DeviceWithNodeId, we weren't storing sLastUsedDevice, so triggering resubscription would not know to talk to that device instance.

Not needed; SetUpDeviceCommand::RunCommand already calls DeviceWithNodeId on the superclass, which does the right thing.


[Bug?] Cant open anything in linux

hi, ive compiled ctr succesfully on artix linux with dotnet, first cloning the repo with submodules, then running dotnet build --runtime linux-x64 --self-contained inside the "CTR Studio" folder.
the program runs fine, all windows appear
yet i cant seem to open any file
the file picker certainly starts up and i can select files just fine but upon clicking "OK", nothing happens, no matter if its a .bcmdl, .bclim, .szs or .sarc

Matter of fact, i made my own install script that actually installs everything correctly and copies both Plugin folders to where they belong, i will open a pr for this


[WIP] Bulk

Closes #248
Closes #208
Part of #256
This is a work in progress set of .bulk methods on the client. Some of the weirdness around generics are so we can tweak the allocated field types on the response and/or ignore successful bulk operations.
The body is stored as a Vec<u8> and bulk items are written into the body as they're encountered. This is a little different from other methods where we avoid serialising until the last responsible moment but lets us accept bulk operations for documents with different types.
I think one of the main benefits will be the async streaming support, so you can call bulk_stream on an AsyncClient and get a Sink/Stream pair to send operations to and receive responses on. We'll buffer operations until the configured request size fills up, or a configured timeout expires. This would be useful for a logging scenario where you collect logs as they arrive before submitting them in bulk to Elasticsearch.
There's still more work to do, and we'll need to be careful not to end up in situations where the sink can't accept any items, but we also can't send any.

There's a lot of new code in the bulk module. This should probably be split up into sub modules. It's also potentially flaky and re-inventing features that already exist in futures. It might be best to put the bulk stream stuff behind a feature gate.

One question for the streaming API is when you can guarantee a single operation has been sent. Really the only way is to observe its id in the response, but not every operation has an id, and if you're ignoring successful operations then you'll probably never see an id at all.

There are a few other tradeoffs here that should be discussed:

For regular bulk requests, there's no way to know whether an operation failed to be serialized until you try send the request and the whole thing fails. Operations that fail to serialize will probably always fail to serialize. It would be good to find a way around this
For errors_only streamed requests it's not possible to tell for certain when an operation has made its way into Elasticsearch
We've got functions for building operations conveniently but they don't actually save much. We might want doc_ variants of them that take a DocumentType and do something with it.


Problem with running zero-shot ensemble？

Prompt ensembling (n=1)
Traceback (most recent call last):
File "/data1/mazc/LJJ/Ensemble_VLM/train.py", line 290, in
main(args)
··········
File "/home/mazc/anaconda3/envs/envlm/lib/python3.9/site-packages/torch/nn/functional.py", line 1679, in softmax
ret = input.softmax(dim)
RuntimeError: "softmax_lastdim_kernel_impl" not implemented for 'Half'
my question：
I encountered this issue while running ZSEN. Is it due to incorrect parameter settings or incorrect environment? I hope you can answer it, thank you!

It seems you use softmax on a Half tensor. Please show the whole logs for better analyzing the issue. Thanks.


Support SDK v1.0.0

See https://github.com/cozodb/openai-multi-client/issues/2#issuecomment-1934153204.


Parallelise note commitment tree point conversions

Motivation
We can speed up note commitment tree updates by running point conversions in parallel with tree updates.
Designs
Run the following operations in parallel rayon iterators or threads:

each point conversion, or batches of point conversions, in any order, in multiple threads (cm_x.into())
appending notes, in blockchain order, in a single thread (self.inner.append(...))

We can start appending notes as soon as the first point conversion is completed.
This change can be made for Sprout, Sapling, and Orchard. Sprout is a lower priority because it's not currently being used much.
Orchard example:
https://github.com/ZcashFoundation/zebra/blob/267db7f956c741c5f4369722eb9aaa0c49c359ac/zebra-chain/src/orchard/tree.rs#L309-L310

This is currently optional. We've talked about it a few times, so I wanted to write it down so we had a record.
But I think we can close it, unless we decide we need it to fix #5420, and that #5420 is an important enough fix to schedule soon.


Require PTHREAD using cmake canonic way

Pthread was required by included directly findPthread.cmake
then testing for success.
Use the find_package command and require success with the REQUIRED
option.

:+1: @dawagner @Makohoek @OznOg

:+1: @dawagner @Makohoek @OznOg


#392 - Write photos taken via the app into the camera roll and update their location metadata

Ok, it seems to be writing coordinates out in iOS for me now, but it still writes out multiple photos in Android, usually after taking more than 1 photo. I tried to add some logging around this. Can you reproduce that, @budowski?

Weird, cannot recreate this on my PIxel 7 :(
Maybe it's a weird timing issue - can you send out logs from your device?

I've made one fairly significant change here: we're now writing EXIF when you save the observation, not every time we update the coordinates. This seems to prevent the duplicate photo issue in Google Photos on Android, which seemed like it might have been related to updating the photo's EXIF while Google Photos was importing the photo, because the photo never seemed to be duplicated in Files, only in Google Photos.
There still seems to be a problem when landscape photos in Android appearing upside down when written out. I think this is because the way we write them out does not preserve their Orientation metadata. react-native-camera-roll doesn't seem to support this, so we probably need to write the EXIF ourselves, but we can't do it until we update react-native-exif-reader to write arbitrary EXIF tags. If tests pass I'm going to merge despite that bug and deal with it later.


Update and improve chat demo

What kind of change does this PR introduce?
Demo update
What is the current behavior?
The chat demo is outdated.
What is the new behavior?
I cleaned up the code, updated both Supabase and Gradle and improved the UI a little bit:

Additional context
Builds upon #397

Hey, @hieuwu forgot to mention it in the PR. Could you update the demo's README to mention how to run the iOS app? Thanks!

Hey, @hieuwu forgot to mention it in the PR. Could you update the demo's README to mention how to run the iOS app (and also that it even exists)? Thanks!

Yeah sure Jan. I am going to do that


Aggregate recursively

Depends on #4121 - last 2 commits are for this feature
[ch6576]

will merge together with #4121 - so changed label to breaking


Wrap scroll view with refresh options

I think we should probably move our view to the separate package. What is the best name for it? Should we create something only for UI and therefore @kiwicom/mobile-ui? Or something more obvious? I would also like to create "typography" package...

Yes, I think you are right, it could be good to split this package yet again...
Not sure mobile-ui is the best name, could be almost anything? Not sure what is the better name yet though...
´@kiwicom/mobile-typography` is descriptive and good for the text components :)


The function "image_distance_from_dataset" can not be found

Hey @YuxinCHENGPE, I missed this issue until now. I'm including that file just for reference in case people are interested in DreamBooth experiments. However, I don't plan to make this code runnable. So probably best to use look at the code as reference instead of plug-and-play for any of the LORA fine-tuning experiments. :)


[CPF-692] Modelled Scheduling

This PR adds the interface foam.datetime.Schedule, along with some implementations and the ability to use them in the existing Cron scheduler. Implementations added include CronSchedule, TimeOfDaySchedule, IntervalSchedule, and OrSchedule.
Here's an example journal entry for a job executing at 20 minute intervals and at 1PM every day:
{
  "class": "foam.nanos.cron.Cron",
  "id":"hello-cron",
  "enabled": true,
  "schedule": {
    "class": "foam.datetime.OrSchedule",
    "delegates": [
      {
        "class": "foam.datetime.TimeOfDaySchedule",
        "time": {
          "class": "foam.datetime.TimeHMS",
          "hour": 13,
          "minute": 00,
          "second": 00
        }
      },
      {
        "class": "foam.datetime.IntervalSchedule",
        "duration": {
          "class": "foam.datetime.TimeHMS",
          "hour": 0,
          "minute": 20,
          "second": 00
        },
        "start": "2019-01-01T00:00:00.0Z"
      }
    ]
  },
  "description":"Says hello",
  "code":
  """
    System.out.println("Hello, Cron!");
  """
}

Is zero ignored/wildcard for Interval TimeHMS?
The example above would suggest that, but Interval would suggest it's setting 0 to zero hour of day.
next.add(Calendar.HOUR_OF_DAY, getDuration().getHour());

IntervalSchedule holds a duration, so setting hour to zero means "zero hours added between each run"

Added test for IntervalSchedule - more tests pending. A little confused about the CLA thing caused by merging master.

CronSchedule copies the existing logic in Cron.js, so likely doesn't need a test. TimeIntervalSchedule and TimeOfDaySchedule both have tests now. OrSchedule is a simple "find minimum" function and has been tested manually.

@googlebot I consent.

I have no idea how LiveScriptBundler commits ended up in this branch. I looked at the tree and I just can't make sense of this.
I'm closing this PR, rebasing my branch, and opening a new one.


[Question] How to get Cmdline popup shown in README git?

Not really an issue, but I was curious how you got the Cmdline popup that is shown in the example gif in the README?
I apologize if this is not the right place to ask such a question.

All good!
The showcase is using Noice.nvim (https://github.com/folke/noice.nvim) for the cmdline prompt.

Thank you!


Custom point display formatting

Currently the map shows things like
1017° 00' 00" S / 14° 30' 00" W
-1,017.000000 / -14.500000

For one on my map the N/S and E/W are switched over (I think that's the behaviour for any TRS map?), i.e. those coordinates would be 1017 W / 14.5 S. Next part is that we don't even have a degree / minutes / seconds based system, so it really should just show it as 14.5 S / 1017(.0) W. Would be nice if the display of coordinates could be made available as a function that can be passed into the measure constructor to override default behaviour.

Example on http://illy.bz/tmp/measure-test/
Added my coordinates control which shows the N/S and E/W as expected.

Is this still a request? Closing for inactivity. Thanks.


Remove version check as it stops it being run on java 8

sbt-javaversioncheck plugin was already removed in the commit.
Why is enforcing a minimum bytecode version required, and related to this PR? Why cant people build on jdk 1.6?
And if you do enforce a minimum, why not use 1.8 which is what Lambda runs?

This is about what java version the sbt plugin is built with and not about the version of a project that the plugin is used in. Currently the plugin is compiled against Java 7, so it can be used in sbt projects that are at least on that level. Removing that restriction would potentially break the plugin for people that use it in projects on java 7.

Pushed an update, but the conflicting version check changes in build.sbt suggest that supporting people on 1.7 wasn't a goal after all

Actually, I was merging that, and missed the change. I plan to revert it.
Compiling with Java 1.7 is only a cost to the plugin maintainers, not to users of the plugin. In return, it gives potential use of the plugin to a larger set of users.
Once we have to link with a library that is compiled with Java 8 bytecode (or library calls), then the attempt to maintain compatibility is no longer possible, but until then, it still seems useful.
The flags above (changing scalacOptions and javacOptions) is not a "solution" I like, because it doesn't warn one of the possibility of accidentally linking against an API call that only exists on Java 8.

Can you say what the issue is with using Java 1.7? To reiterate, this changes nothing about the runtime environment, just the way in which the plugin is compiled.
Compiling with Java 7: means compatibility for people using Java 7 or Java 8
Compiling with Java 8: means compatibility only for people using Java 8


Dependency not available via standard CRAN repository for R 4.0.0+

This package depends on fractal which is not available anymore in CRAN. Thus, installing mhealthrools from GitHub produces this error:
  ERROR: dependency ‘fractal’ is not available for package ‘mhealthtools’

Hi Julio! Thanks for filing this issue.
Have you tried installing the fractal package using devtools::install_github via the CRAN GitHub mirror? You will need to install the fractal dependencies sapa, wmtsa, and ifultools using devtools::install_github as well but once you do so you can install both fractal and then mhealthtools on R 4.0.0

Thanks for the pointers! I haven't tried that, what I ended up doing was removing it from DESCRIPTION. At the moment I'm only working with accelerometer features and it seems the only dependency is for dfa features, right? No other features will be affected?
https://github.com/Sage-Bionetworks/mhealthtools/blob/6b14637da57829e14da40502930b8c16937f1fa8/R/feature_extraction_functions.R#L41

Correct. That seems to be the case.

Neither fractal nor a number of its dependencies are available on CRAN, so I've decided to remove the dfa feature in order to unblock development on mhealthtools. If you need this feature, either install an older version of mhealthtools or manually include this feature as part of the funs argument to a feature extraction function (like accelerometer_features). For more info on including your own feature extraction functions as part of funs or models, see vignette("extending", "mhealthtools")


Security Fix for Cross-site Scripting (XSS) - huntr.dev

https://huntr.dev/users/mufeedvh has fixed the Cross-site Scripting (XSS) vulnerability 🔨. mufeedvh has been awarded $25 for fixing the vulnerability through the huntr bug bounty program 💵. Think you could fix a vulnerability like this?
Get involved at https://huntr.dev/
Q | A
Version Affected | ALL
Bug Fix | YES
Original Pull Request | https://github.com/418sec/x-editable/pull/1
GitHub Issue | https://github.com/vitalets/x-editable/issues/1130
Vulnerability README | https://github.com/418sec/huntr/blob/master/bounties/npm/x-editable/1/README.md
User Comments:
📊 Metadata *
Bounty URL: https://www.huntr.dev/bounties/1-npm-x-editable
⚙ Description *
The project x-editable validated JSON string with poorly crafted Regex making it easy to bypass the validation and inject JavaScript code to achieve XSS (Cross-site Scripting).
💻 Technical Description *
The implemented Regex to validate JSON was so poor that it only checks whether if the string begins and ends with [ or { and their counterparts ] or }. This means you can give it a string such as []+alert(1)+[] and it will match.
Come on man why would you write a whole Regex to validate JSON semantics lol, and JavaScript's Regex match doesn't have certain expressions implemented making it even harder.
So how do we fix it? Just parse the JSON with the JavaScript function JSON.parse() and if it fails, it's not a valid JSON string.
🐛 Proof of Concept (PoC) *
Refer: https://github.com/vitalets/x-editable/issues/1130
Payload used to bypass the current validation:
[]+alert(1)+[]

🔥 Proof of Fix (PoF) *
Parse the input JSON string and if it fails, it wouldn't proceed dynamically adding it to the HTML code preventing the XSS (Cross-site Scripting) vulnerability.
if (typeof s === 'string' && s.length) {
    try {
        JSON.parse(s);
        if (safe) {
            try {
                /*jslint evil: true*/
                s = (new Function('return ' + s))();
                /*jslint evil: false*/
            } catch (e) {} finally {
                return s;
            }
        } else {
            /*jslint evil: true*/
            s = (new Function('return ' + s))();
            /*jslint evil: false*/
        }
        return s;
    } catch (e) {
        // pass
    }
}

👍 User Acceptance Testing (UAT)
Just added a try/catch block to check for JSON.parse() fails.

@vitalets - let me know if you have any questions or thoughts?
Cheers! 🍰


✨ [REQUEST] Authentik, Authelia or keycloak

Checked

[X] If a new addon, I have checked on  Google that such as addon doesn't already exists
[X] If a new feature, I have searched in the discussions & issues that it was not already covered

Which addon?
I would like to request one of the popular add-ons to be available for identity and access management. (to introduce 2FA for example to the immich app)
https://www.authelia.com/
https://www.keycloak.org/
https://goauthentik.io/
Is your feature request related to a problem? Please describe
No 2FA for some of the add-ons
Describe the solution you'd like
An authentication add-on

To avoid replication I suggest instead https://github.com/BenoitAnastay/authelia-home-assistant-addon and we close this ticket.

Thanks! Indeed he has great addons

Thx for linking his repo!


Minor release: v2.6

Thanks for everyone who contributed/provided input into this!
Bringing in:
#497 Forward-looking erase-state CRCs
#572 Add littlefs-disk-img-viewer to README
#718 Add "chamelon" to the related projects section.
#752 Add test/bench runners, benchmarks, additional scripts
#800 Fix block-boundary truncate issues
#801 Add an assert for truthy-preserving bool conversions
#802 Add explicit assert for minimum block size of 128 bytes
#805 Fix issue where seeking to end-of-directory return LFS_ERR_INVAL
#807 Add littlefs2 crate to README
#809 Adopt Brent's algorithm for cycle detection
#811 Fix issue where lfs_fs_deorphan may run more than needed
#812 Add lfs_fs_mkconsistent
Draft of release notes follows:
Note!
This release bumps the on-disk minor version of littlefs from lfs2.0 -> lfs2.1.
This change is backwards-compatible, but after the first write with the new version, the image on disk will no longer be mountable by older versions of littlefs.
Read-only operations will not change the on-disk version, and the on-disk version can be explicitly bumped with lfs_fs_mkconsistent if desired.
This is the first on-disk minor version bump for littlefs, and is untested waters, so do open a GitHub issue if this creates any problems.
What's new?

FCRCs - forward-looking erase-state CRCs (#497)
Found by @pjsg, littlefs was relying on a bad assumption about the order/atomicity of prog operations to detect incomplete metadata commits. In the case of power-failure, this could lead to littlefs progging the same location multiple times without an erase, leading to best case fixable corruption, worst case significantly reduced data retention.
The solution implemented here is to store a checksum of the next erased prog-size in every commit. This way any incomplete commits that modify the erased state can be detected.
In theory this could be implemented in a forward-compatible way, but littlefs currently treats all CRC tags as commit-ending CRC tags, so only updated versions of littlefs will be able to read metadata blocks containing FCRCs. This is the reason for the on-disk minor version bump. On the bright-side, future CRC-related extensions will be forward-compatible.

A complete overhaul of the testing/bench framework (#752)
This does not affect users, but involves a long list of needed changes to make it easier to develop/bench littlefs:

Tests/benches now run in parallel, and much faster thanks to shared processes.
Tests are more reproducible, and narrow bugs can be reproduced locally repeatedly without leaving GDB.
More options for power-loss testing. Exhaustive testing of all 1 and 2-deep powerlosses have been added to CI.
More scripts related to perf measurements, plotting, tracing, etc.
A make help rule to help use/document the Makefile, which is sort of the entry point for littlefs development.
Added a CI rule to have @geky-bot comment on each PR with CI measurements (examples here). We'll see if this is an improvement over the GitHub statuses.

The increased power-loss coverage has already found a couple of difficult to hit bugs (eba5553 and 0b11ce0), and the bench runner will be useful for evaluating littlefs's performance moving forward.

Added a couple more asserts to help common implementation issues (#801, #802)

Adopted Brent's algorithm for cycle detection (#809)
This should significantly speed up cycle detection in the case the metadata linked-list contains a cycle.

Added lfs_fs_mkconsistent as proposed by @kasper0 (#812)
lfs_fs_mkconsistent allows users to front-load the internal consistency checks littlefs needs to run before it can write to the filesystem.
Conveniently this also allows a way to force littlefs to write the new on-disk minor version if that is desired.

A number of bug fixes, thanks to @ghost, @ajaybhargav, @colin-foster-in-advantage, @rvanschoren, @hgspbs, @sosthene-nitrokey, @kasper0, @Ldd309, and others (#800, #805, #811):

#800 - Fixed issues with truncate around block-aligned boundaries
#805 - Fixed issue where seeking to end-of-directory return LFS_ERR_INVAL
#811 - Fixed issue where lfs_fs_deorphan may run more than needed
eba5553 - Fixed issue where half-orphans can hide full orphans in nested power-loss situations
0b11ce0 - Fixed incorrect calculation of extra space needed in mdir blocks
ba1c764 - Fixed issue where deorphan could get stuck circling between two half-orpans in power-loss situations

And a number of links to useful community projects related to littlefs, thanks to @tniessen, @yomimono, @elpiel (#572, #718, #807):

littlefs-disk-img-viewer
chamelon
littlefs2-rust

If you have a littlefs-related project or a project that uses littlefs, consider opening a PR. Eventually my plan is to move these to a user-contributable wiki.

@geky-bot won't run until this is merged, so here I am pretending to be the bot:

Tests passed ✓, Code: 16556 B, Stack: 1432 B, Structs: 772 B

Code
Stack
Structs

Coverage

Default
16556 B
1432 B
772 B
Lines
2289/2469 lines

Readonly
5990 B
448 B
772 B
Branches
1174/1496 branches

Threadsafe
17362 B
1432 B
780 B

Benchmarks

Migrate
18240 B
1736 B
776 B
Readed
29369693876 B

Error-asserts
17192 B
1424 B
772 B
Proged
1482874766 B

Erased
1568888832 B

Humorously, GitHub now thinks littlefs is a python project


Fix select box event ordering

Fixes https://github.com/microsoft/azuredatastudio/issues/13826
The real issue here is that the extension side was getting the wrong (old) value when updating the properties for the currently selected value. So if they were relying on looking at the value for anything then it would be incorrect.
This is because the component is hooking into the event handler to update its own value - and it's using the value property of the underlying selectBox for that. https://github.com/microsoft/azuredatastudio/blob/main/src%2Fsql%2Fworkbench%2Fbrowser%2FmodelComponents%2Fdropdown.component.ts#L100
But when I added the event I made it fire the event BEFORE setting the value, so when the component checked the value it still saw the old value.
The fix is simple - just have the event fired after the value is updated. But I also fixed up a couple of other things :

Updated the callback to use in the value passed in from the event since that's better practice anyways.
Updated fileConfigPage to use the event value. This isn't strictly necessary anymore but in general again is better practice

(note that I had to use this.value when firing the event for the select box because the event comes from VS Code and so isn't in the form we expect. Using this.value is fine since we set the selected value a couple lines above)

Well unfortunately we can't fix the value the event is sending right now. For non-editable dropdown it's sending the ISelectData which not only isn't typed in our API but is more of internal implementation and so really shouldn't have been sent as the value.
But we already have a couple extensions using it so we can't really change it now without risking breaking them and others. So leaving it as is for now and just documenting that.

Pull Request Test Coverage Report for Build 428530725

0 of 5 (0.0%)  changed or added relevant lines in 2 files are covered.
58 unchanged lines in 1 file lost coverage.
Overall coverage increased (+0.02%) to 43.118%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

src/sql/base/browser/ui/selectBox/selectBox.ts
0
1
0.0%

extensions/schema-compare/src/dialogs/schemaCompareDialog.ts
0
4
0.0%

Files with Coverage Reduction
New Missed Lines
%

src/sql/workbench/contrib/notebook/browser/outputs/renderers.ts
58
5.15%

Totals

Change from base Build 426825454:
0.02%

Covered Lines:
24122

Relevant Lines:
51269

💛  - Coveralls

Well, had to completely undo the typings changes. Extensions were just blindly either treating the value as a string or a Category value without casting which meant they failed to compile. It should be safe to do this regardless from a runtime standpoint since the actual logic isn't changing - but I'm going to leave it as is to reduce the side effects and then probably come back later to fix this up.
Let this be a lesson why just throwing any as a type into something can have long lasting consequences...


Aqara P100 support？

If possible, could you  supports  for Aqara P100

Do you have it?

Do you have it?

yes~

Enable basic and mqtt logs in integration options and send it to me

Enable basic and mqtt logs in integration options and send it to me

Thanks！
My gateway has not arrived yet. I will send you logs after arrival

2021-03-01 21:37:16  DEBUG    main          SysInfo: {'installation_type': 'Home Assistant Supervised', 'version': '2021.2.3', 'dev': False, 'hassio': True, 'virtualenv': False, 'python_version': '3.8.7', 'docker': True, 'arch': 'x86_64', 'os_name': 'Linux', 'os_version': '4.19.0-14-amd64', 'supervisor': '2021.02.11', 'host_os': 'Debian GNU/Linux 10 (buster)', 'docker_version': '20.10.3', 'chassis': 'vm'}
2021-03-01 21:37:17  DEBUG    main          Loaded from MiCloud 50 devices
2021-03-01 21:37:27  DEBUG    gateway3      <IP_ADDRESS> | MQTT | ble/blt.3.1254uhr64lc00 b'{"temperature":22.2,"humidity":88}'
2021-03-01 21:37:27  DEBUG    gateway3      <IP_ADDRESS> | MQTT | ble/blt.3.12552e5qgek00 b'{"humidity":84,"temperature":22.5}'
2021-03-01 21:37:27  DEBUG    gateway3      <IP_ADDRESS> | MQTT | ble/blt.3.1254s7vckeg00 b'{"humidity":88,"temperature":23.3}'
2021-03-01 21:37:53  DEBUG    gateway3      <IP_ADDRESS> | MQTT | gw/BC33ACFFFE4FB178/heartbeat b'{"networkUp":true,"networkPanId":"0x4758","radioTxPower":7,"radioChannel":25}'
2021-03-01 21:37:57  DEBUG    gateway3      <IP_ADDRESS> | MQTT | log/miio b'[20210301 21:37:56] [D] ot_agent_recv_handler_one(): fd:18, msg:{"method":"_async.ble_event","params":{"dev":{"did":"blt.3.1254uhr64lc00","mac":"A4:C1:38:6E:86:9B","pdid":1371},"evt":[{"eid":4100,"edata":"dd00"}],"frmCnt":70,"gwts":1614605876},"id":805} length:189 bytes'
2021-03-01 21:37:57  DEBUG    gateway3      <IP_ADDRESS> | MQTT | ble/blt.3.1254uhr64lc00 b'{"temperature":22.1,"humidity":88}'
2021-03-01 21:38:53  DEBUG    gateway3      <IP_ADDRESS> | MQTT | gw/BC33ACFFFE4FB178/heartbeat b'{"networkUp":true,"networkPanId":"0x4758","radioTxPower":7,"radioChannel":25}'
2021-03-01 21:39:53  DEBUG    gateway3      <IP_ADDRESS> | MQTT | gw/BC33ACFFFE4FB178/heartbeat b'{"networkUp":true,"networkPanId":"0x4758","radioTxPower":7,"radioChannel":25}'
2021-03-01 21:40:53  DEBUG    gateway3      <IP_ADDRESS> | MQTT | gw/BC33ACFFFE4FB178/heartbeat b'{"networkUp":true,"networkPanId":"0x4758","radioTxPower":7,"radioChannel":25}'
2021-03-01 21:41:53  DEBUG    gateway3      <IP_ADDRESS> | MQTT | gw/BC33ACFFFE4FB178/heartbeat b'{"networkUp":true,"networkPanId":"0x4758","radioTxPower":7,"radioChannel":25}'
2021-03-01 21:42:41  DEBUG    gateway3      <IP_ADDRESS> | MQTT | log/miio b'[20210301 21:42:41] [D] ot_agent_recv_handler_one(): fd:18, msg:{"method":"_async.ble_event","params":{"dev":{"did":"blt.3.12552e5qgek00","mac":"A4:C1:38:17:1C:9F","pdid":1371},"evt":[{"eid":4102,"edata":"5003"}],"frmCnt":13,"gwts":1614606160},"id":851} length:189 bytes'
2021-03-01 21:42:41  DEBUG    gateway3      <IP_ADDRESS> | MQTT | ble/blt.3.12552e5qgek00 b'{"humidity":84,"temperature":22.5}'
2021-03-01 21:42:53  DEBUG    gateway3      <IP_ADDRESS> | MQTT | gw/BC33ACFFFE4FB178/heartbeat b'{"networkUp":true,"networkPanId":"0x4758","radioTxPower":7,"radioChannel":25}'
2021-03-01 21:43:53  DEBUG    gateway3      <IP_ADDRESS> | MQTT | gw/BC33ACFFFE4FB178/heartbeat b'{"networkUp":true,"networkPanId":"0x4758","radioTxPower":7,"radioChannel":25}'
2021-03-01 21:44:06  DEBUG    gateway3      <IP_ADDRESS> | MQTT | log/miio b'[20210301 21:44:05] [D] ot_agent_recv_handler_one(): fd:18, msg:{"method":"_async.ble_event","params":{"dev":{"did":"blt.3.1254s7vckeg00","mac":"A4:C1:38:79:1F:39","pdid":1371},"evt":[{"eid":4102,"edata":"7703"}],"frmCnt":120,"gwts":1614606245},"id":865} length:190 bytes'
2021-03-01 21:44:06  DEBUG    gateway3      <IP_ADDRESS> | MQTT | ble/blt.3.1254s7vckeg00 b'{"humidity":88,"temperature":23.3}'
2021-03-01 21:44:53  DEBUG    gateway3      <IP_ADDRESS> | MQTT | gw/BC33ACFFFE4FB178/heartbeat b'{"networkUp":true,"networkPanId":"0x4758","radioTxPower":7,"radioChannel":25}'
2021-03-01 21:45:54  DEBUG    gateway3      <IP_ADDRESS> | MQTT | gw/BC33ACFFFE4FB178/heartbeat b'{"networkUp":true,"networkPanId":"0x4758","radioTxPower":7,"radioChannel":25}'
2021-03-01 21:46:54  DEBUG    gateway3      <IP_ADDRESS> | MQTT | gw/BC33ACFFFE4FB178/heartbeat b'{"networkUp":true,"networkPanId":"0x4758","radioTxPower":7,"radioChannel":25}'
2021-03-01 21:47:05  DEBUG    gateway3      <IP_ADDRESS> | MQTT | log/miio b'[20210301 21:47:04] [D] ot_agent_recv_handler_one(): fd:18, msg:{"method":"_async.ble_event","params":{"dev":{"did":"blt.3.1254s7vckeg00","mac":"A4:C1:38:79:1F:39","pdid":1371},"evt":[{"eid":4106,"edata":"0a"}],"frmCnt":124,"gwts":1614606424},"id":895} length:188 bytes'
2021-03-01 21:47:05  DEBUG    gateway3      <IP_ADDRESS> | MQTT | ble/blt.3.1254s7vckeg00 b'{"humidity":88,"temperature":23.3,"battery":10}'
2021-03-01 21:47:54  DEBUG    gateway3      <IP_ADDRESS> | MQTT | gw/BC33ACFFFE4FB178/heartbeat b'{"networkUp":true,"networkPanId":"0x4758","radioTxPower":7,"radioChannel":25}'
2021-03-01 21:47:57  DEBUG    gateway3      <IP_ADDRESS> | MQTT | log/miio b'[20210301 21:47:56] [D] ot_agent_recv_handler_one(): fd:18, msg:{"method":"_async.ble_event","params":{"dev":{"did":"blt.3.1254uhr64lc00","mac":"A4:C1:38:6E:86:9B","pdid":1371},"evt":[{"eid":4102,"edata":"6903"}],"frmCnt":72,"gwts":1614606476},"id":904} length:189 bytes'
2021-03-01 21:47:57  DEBUG    gateway3      <IP_ADDRESS> | MQTT | ble/blt.3.1254uhr64lc00 b'{"temperature":22.1,"humidity":87}'
2021-03-01 21:48:54  DEBUG    gateway3      <IP_ADDRESS> | MQTT | gw/BC33ACFFFE4FB178/heartbeat b'{"networkUp":true,"networkPanId":"0x4758","radioTxPower":7,"radioChannel":25}'
2021-03-01 21:49:54  DEBUG    gateway3      <IP_ADDRESS> | MQTT | gw/BC33ACFFFE4FB178/heartbeat b'{"networkUp":true,"networkPanId":"0x4758","radioTxPower":7,"radioChannel":25}'
2021-03-01 21:50:54  DEBUG    gateway3      <IP_ADDRESS> | MQTT | gw/BC33ACFFFE4FB178/heartbeat b'{"networkUp":true,"networkPanId":"0x4758","radioTxPower":7,"radioChannel":25}'
2021-03-01 21:51:40  DEBUG    gateway3      <IP_ADDRESS> | MQTT | log/miio b'[20210301 21:51:40] [D] ot_agent_recv_handler_one(): fd:18, msg:{"method":"_async.ble_event","params":{"dev":{"did":"blt.3.12552e5qgek00","mac":"A4:C1:38:17:1C:9F","pdid":1371},"evt":[{"eid":4106,"edata":"32"}],"frmCnt":17,"gwts":1614606699},"id":940} length:187 bytes'
2021-03-01 21:51:40  DEBUG    gateway3      <IP_ADDRESS> | MQTT | ble/blt.3.12552e5qgek00 b'{"humidity":84,"temperature":22.5,"battery":50}'
2021-03-01 21:51:54  DEBUG    gateway3      <IP_ADDRESS> | MQTT | gw/BC33ACFFFE4FB178/heartbeat b'{"networkUp":true,"networkPanId":"0x4758","radioTxPower":7,"radioChannel":25}'
2021-03-01 21:52:54  DEBUG    gateway3      <IP_ADDRESS> | MQTT | gw/BC33ACFFFE4FB178/heartbeat b'{"networkUp":true,"networkPanId":"0x4758","radioTxPower":7,"radioChannel":25}'
2021-03-01 21:53:15  DEBUG    gateway3      <IP_ADDRESS> | MQTT | gw/BC33ACFFFE4FB178/commands b'{"commands":[{"command":"lumi set-UTC-time 0x603cf1cb","postDelayMs":0}]}'
2021-03-01 21:53:15  DEBUG    gateway3      <IP_ADDRESS> | MQTT | gw/BC33ACFFFE4FB178/executed b'{"command":"lumi set-UTC-time 0x603cf1cb"}'
2021-03-01 21:53:15  DEBUG    gateway3      <IP_ADDRESS> | MQTT | gw/BC33ACFFFE4FB178/commands b'{"commands":[{"command":"lumi set-UTC-time 0x603cf1cb","postDelayMs":0}]}'
2021-03-01 21:53:15  DEBUG    gateway3      <IP_ADDRESS> | MQTT | gw/BC33ACFFFE4FB178/executed b'{"command":"lumi set-UTC-time 0x603cf1cb"}'
2021-03-01 21:53:39  DEBUG    gateway3      <IP_ADDRESS> | MQTT | log/miio b'[20210301 21:53:38] [D] ot_agent_recv_handler_one(): fd:18, msg:{"method":"_async.ble_event","params":{"dev":{"did":"blt.3.12552e5qgek00","mac":"A4:C1:38:17:1C:9F","pdid":1371},"evt":[{"eid":4102,"edata":"5b03"}],"frmCnt":19,"gwts":1614606818},"id":960} length:189 bytes'
2021-03-01 21:53:39  DEBUG    gateway3      <IP_ADDRESS> | MQTT | ble/blt.3.12552e5qgek00 b'{"humidity":85,"temperature":22.5,"battery":50}'
2021-03-01 21:53:54  DEBUG    gateway3      <IP_ADDRESS> | MQTT | gw/BC33ACFFFE4FB178/heartbeat b'{"networkUp":true,"networkPanId":"0x4758","radioTxPower":7,"radioChannel":25}'
2021-03-01 21:54:39  DEBUG    gateway3      <IP_ADDRESS> | MQTT | log/miio b'[20210301 21:54:39] [D] ot_agent_recv_handler_one(): fd:18, msg:{"method":"_async.ble_event","params":{"dev":{"did":"blt.3.12552e5qgek00","mac":"A4:C1:38:17:1C:9F","pdid":1371},"evt":[{"eid":4100,"edata":"e000"}],"frmCnt":21,"gwts":1614606878},"id":971} length:189 bytes'
2021-03-01 21:54:39  DEBUG    gateway3      <IP_ADDRESS> | MQTT | ble/blt.3.12552e5qgek00 b'{"humidity":85,"temperature":22.4,"battery":50}'
2021-03-01 21:54:54  DEBUG    gateway3      <IP_ADDRESS> | MQTT | gw/BC33ACFFFE4FB178/heartbeat b'{"networkUp":true,"networkPanId":"0x4758","radioTxPower":7,"radioChannel":25}'
2021-03-01 21:55:04  DEBUG    gateway3      <IP_ADDRESS> | MQTT | log/miio b'[20210301 21:55:03] [D] ot_agent_recv_handler_one(): fd:18, msg:{"method":"_async.ble_event","params":{"dev":{"did":"blt.3.1254s7vckeg00","mac":"A4:C1:38:79:1F:39","pdid":1371},"evt":[{"eid":4102,"edata":"6e03"}],"frmCnt":126,"gwts":1614606903},"id":975} length:190 bytes'
2021-03-01 21:55:04  DEBUG    gateway3      <IP_ADDRESS> | MQTT | ble/blt.3.1254s7vckeg00 b'{"humidity":87,"temperature":23.3,"battery":10}'
2021-03-01 21:55:54  DEBUG    gateway3      <IP_ADDRESS> | MQTT | gw/BC33ACFFFE4FB178/heartbeat b'{"networkUp":true,"networkPanId":"0x4758","radioTxPower":7,"radioChannel":25}'
2021-03-01 21:56:54  DEBUG    gateway3      <IP_ADDRESS> | MQTT | gw/BC33ACFFFE4FB178/heartbeat b'{"networkUp":true,"networkPanId":"0x4758","radioTxPower":7,"radioChannel":25}'

2021-03-01 22:03:04  DEBUG    main          SysInfo: {'installation_type': 'Home Assistant Supervised', 'version': '2021.2.3', 'dev': False, 'hassio': True, 'virtualenv': False, 'python_version': '3.8.7', 'docker': True, 'arch': 'x86_64', 'os_name': 'Linux', 'os_version': '4.19.0-14-amd64', 'supervisor': '2021.02.11', 'host_os': 'Debian GNU/Linux 10 (buster)', 'docker_version': '20.10.3', 'chassis': 'vm'}
2021-03-01 22:03:04  DEBUG    gateway3      <IP_ADDRESS> | Start main thread
2021-03-01 22:03:04  DEBUG    gateway3      <IP_ADDRESS> | Prepare Gateway
2021-03-01 22:03:05  DEBUG    gateway3      <IP_ADDRESS> | Version: 1.4.6_0043
2021-03-01 22:03:05  DEBUG    gateway3      <IP_ADDRESS> | Get devices
2021-03-01 22:03:05  DEBUG    gateway3      <IP_ADDRESS> | Setup Zigbee device {'did': 'lumi.0', 'model': 'lumi.gateway.mgl03', 'mac': '0xbc33acfffe4fb178', 'type': 'gateway', 'init': {'firmware lock': True, 'alarm_did': '408557584'}}
2021-03-01 22:03:08  DEBUG    main          Loaded from MiCloud 50 devices
2021-03-01 22:03:09  DEBUG    gateway3      <IP_ADDRESS> | Gateway time offset: -0.4597911834716797
2021-03-01 22:03:09  DEBUG    gateway3      <IP_ADDRESS> | Prepare Gateway
2021-03-01 22:03:09  DEBUG    gateway3      <IP_ADDRESS> | MQTT connected
2021-03-01 22:03:09  DEBUG    gateway3      <IP_ADDRESS> | gateway <= True
2021-03-01 22:03:09  DEBUG    gateway3      <IP_ADDRESS> | MQTT | ble/blt.3.1254uhr64lc00 b'{"temperature":21.9,"humidity":87}'
2021-03-01 22:03:09  DEBUG    gateway3      <IP_ADDRESS> | BLE device blt.3.1254uhr64lc00 is no longer on the gateway
2021-03-01 22:03:09  DEBUG    gateway3      <IP_ADDRESS> | MQTT | ble/blt.3.12552e5qgek00 b'{"humidity":85,"temperature":22.4,"battery":50}'
2021-03-01 22:03:09  DEBUG    gateway3      <IP_ADDRESS> | BLE device blt.3.12552e5qgek00 is no longer on the gateway
2021-03-01 22:03:09  DEBUG    gateway3      <IP_ADDRESS> | MQTT | ble/blt.3.1254s7vckeg00 b'{"humidity":87,"temperature":23.3,"battery":10}'
2021-03-01 22:03:09  DEBUG    gateway3      <IP_ADDRESS> | BLE device blt.3.1254s7vckeg00 is no longer on the gateway
2021-03-01 22:03:10  DEBUG    mini_miio     Send get_properties 128B, recv 128B in 0.0 sec and 1 try
2021-03-01 22:03:40  DEBUG    mini_miio     Send get_properties 128B, recv 128B in 0.0 sec and 1 try
2021-03-01 22:03:54  DEBUG    gateway3      <IP_ADDRESS> | MQTT | gw/BC33ACFFFE4FB178/heartbeat b'{"networkUp":true,"networkPanId":"0x4758","radioTxPower":7,"radioChannel":25}'
2021-03-01 22:03:54  DEBUG    gateway3      <IP_ADDRESS> | gateway <= {'networkUp': True, 'networkPanId': '0x4758', 'radioTxPower': 7, 'radioChannel': 25}
2021-03-01 22:04:10  DEBUG    mini_miio     Send get_properties 128B, recv 128B in 0.0 sec and 1 try
2021-03-01 22:04:39  DEBUG    gateway3      <IP_ADDRESS> | MQTT | log/miio b'[20210301 22:04:39] [D] ot_agent_recv_handler_one(): fd:18, msg:{"method":"_async.ble_event","params":{"dev":{"did":"blt.3.12552e5qgek00","mac":"A4:C1:38:17:1C:9F","pdid":1371},"evt":[{"eid":4102,"edata":"5203"}],"frmCnt":23,"gwts":1614607478},"id":1072} length:190 bytes'
2021-03-01 22:04:40  DEBUG    mini_miio     Send get_properties 128B, recv 128B in 0.0 sec and 1 try
2021-03-01 22:04:45  DEBUG    gateway3      <IP_ADDRESS> | MQTT | zigbee/recv b'{"cmd":"write","did":"lumi.0","id":4,"params":[{"res_name":"8.0.2109","value":60}],"source":"","time":1614607484698}'
2021-03-01 22:04:45  DEBUG    mini_miio     Send miIO.zb_start_provision 176B, recv 80B in 0.0 sec and 1 try
2021-03-01 22:04:45  DEBUG    gateway3      <IP_ADDRESS> | MQTT | gw/BC33ACFFFE4FB178/commands b'{"commands":[{"command":"lumi open-with-cloud-install-code 0x3c","postDelayMs":0}]}'
2021-03-01 22:04:45  DEBUG    gateway3      <IP_ADDRESS> | MQTT | gw/BC33ACFFFE4FB178/executed b'{"command":"lumi open-with-cloud-install-code 0x3c"}'
2021-03-01 22:04:45  DEBUG    gateway3      <IP_ADDRESS> | MQTT | zigbee/send b'{"cmd":"write_rsp","id":4,"time":1614607484705,"did":"lumi.0","results":[{"res_name":"8.0.2109","value":60,"error_code":0}]}'
2021-03-01 22:04:45  DEBUG    gateway3      <IP_ADDRESS> | lumi.0 lumi.gateway.mgl03 <= {'pairing_start': 60} [0.04]
2021-03-01 22:04:54  DEBUG    gateway3      <IP_ADDRESS> | MQTT | gw/BC33ACFFFE4FB178/heartbeat b'{"networkUp":true,"networkPanId":"0x4758","radioTxPower":7,"radioChannel":25}'
2021-03-01 22:04:54  DEBUG    gateway3      <IP_ADDRESS> | gateway <= {'networkUp': True, 'networkPanId': '0x4758', 'radioTxPower': 7, 'radioChannel': 25}
2021-03-01 22:05:10  DEBUG    mini_miio     Send get_properties 128B, recv 128B in 0.0 sec and 1 try
2021-03-01 22:05:38  DEBUG    gateway3      <IP_ADDRESS> | MQTT | log/miio b'[20210301 22:05:37] [D] ot_agent_recv_handler_one(): fd:18, msg:{"method":"_async.ble_event","params":{"dev":{"did":"blt.3.12552e5qgek00","mac":"A4:C1:38:17:1C:9F","pdid":1371},"evt":[{"eid":4100,"edata":"df00"}],"frmCnt":25,"gwts":1614607537},"id":1082}{"method":"local.query_status","params":"","id":1083} length:243 bytes'
2021-03-01 22:05:40  DEBUG    mini_miio     Send get_properties 128B, recv 128B in 0.0 sec and 1 try
2021-03-01 22:05:54  DEBUG    gateway3      <IP_ADDRESS> | MQTT | gw/BC33ACFFFE4FB178/heartbeat b'{"networkUp":true,"networkPanId":"0x4758","radioTxPower":7,"radioChannel":25}'
2021-03-01 22:05:54  DEBUG    gateway3      <IP_ADDRESS> | gateway <= {'networkUp': True, 'networkPanId': '0x4758', 'radioTxPower': 7, 'radioChannel': 25}
2021-03-01 22:06:01  DEBUG    gateway3      <IP_ADDRESS> | MQTT | log/miio b'[20210301 22:06:01] [D] ot_agent_recv_handler_one(): fd:18, msg:{"method":"_async.ble_event","params":{"dev":{"did":"blt.3.1254s7vckeg00","mac":"A4:C1:38:79:1F:39","pdid":1371},"evt":[{"eid":4102,"edata":"6f03"}],"frmCnt":130,"gwts":1614607560},"id":1086} length:191 bytes'
2021-03-01 22:06:10  DEBUG    mini_miio     Send get_properties 128B, recv 128B in 0.2 sec and 1 try
2021-03-01 22:06:40  DEBUG    mini_miio     Send get_properties 128B, recv 128B in 0.0 sec and 1 try
2021-03-01 22:06:54  DEBUG    gateway3      <IP_ADDRESS> | MQTT | gw/BC33ACFFFE4FB178/heartbeat b'{"networkUp":true,"networkPanId":"0x4758","radioTxPower":7,"radioChannel":25}'
2021-03-01 22:06:54  DEBUG    gateway3      <IP_ADDRESS> | gateway <= {'networkUp': True, 'networkPanId': '0x4758', 'radioTxPower': 7, 'radioChannel': 25}
2021-03-01 22:07:10  DEBUG    mini_miio     Send get_properties 128B, recv 128B in 0.0 sec and 1 try

sorry~ wrong logs~i I don't know how to pair
I tried several times but failed. There is no valid  logs.
My wife was angry when I asked her to re-enter her fingerprints
I'll try again later！

Please reopen the issue if it is still relevant


Can't decrypt generated strings

Using my public key, I generated the letter "a" to be:
EYakv0D9+zM8zTCcQfLI6XBv2ciLEM7sHECNVR2rl0sP4imxyjtYuOUbszxKbYy+guvxKXuU9LTUEQCMoA3ddWhzRdctuREttdUKiKYz++ZO7m3m0/1utnMArjAP1WkN+k/Z7uvjQSQwfccj1uMGxNb8OsFFqM2jy/ZZK0toIfo14ReIj5AWsUhYrztO0GupfNRE57zU8zQgODxnOm+UY6r/rFu5ZcmHuIYzZseepezjxc66BGonmAnhGKXcllwOFp3rvBzSOdXB+XXG5WWgRp5rcavyEjVFOaXgD0rCW28Ie2DlWENJQ2+l/FAGRm9oRTjH7py+bm7319Ob4fgKQw==

However when I try to decrypt it with
return key.decrypt(str, 'base64', 'utf8');

I get this:
return encodeBuffer(rsa.publicEncrypt(buf, padding), outEncoding);
                                ^

Error: error:040A006E:rsa routines:RSA_padding_add_PKCS1_OAEP_mgf1:data too large for key size
    at Error (native)
    at Object.encrypt (/home/admin/cdj-messenger/node_modules/ursa/lib/ursa.js:278:33)
    at RSAencrypt (/home/admin/cdj-messenger/index.js:31:14)
    at Object.<anonymous> (/home/admin/cdj-messenger/index.js:37:13)
    at Module._compile (module.js:425:26)
    at Object.Module._extensions..js (module.js:432:10)
    at Module.load (module.js:356:32)
    at Function.Module._load (module.js:311:12)
    at Function.Module.runMain (module.js:457:10)
    at startup (node.js:136:18)

@viruzx this works for me:
var ursa = require('ursa'),
    key = ursa.generatePrivateKey(),
    msg = key.encrypt('a', 'utf8', 'base64');

console.log(key.decrypt(msg, 'base64', 'utf8'));

Could you paste your code?

Hello. I don't remember the full context of my bug since it was so long ago, but I do remember that I was doing it completely wrong.
I was trying to keep manage large data with rsa instead of aes.
Closing.


Credentials formatted incorrectly - TypeError:Exception: 'NoneType' object is not subscriptable

Hey guys, running the bot for the first time after entering my configurations and i'm getting this error when executing the bot

the PROD is required to have no spaces before it! this was the solution


locale language ( india_Hindi)

I like to contribute in your project ..
If you have any instruction for me ...

You can just see contributions of README.
Thank you.


Use target root element to display adorners

Effect & drag adorners weren't displayed when the target was not on the same root element (Window etc) than the source. This commit fixes the issue.

Hmmm, I don't think my changes caused the AppVeyor failure

@ltrzesniewski no, sorry, it's my build configuration on appveyor. Your changes are good...

Thanks for the great lib by the way :smile:


Create a docker-compose from the gradle file

add a task that will automatically create a docker compose files based on the configuration in the gradle file.
child of #27

Tracked internally by F81665


Github Authentication: Login Failure

Does this issue occur when all extensions are disabled?: Don't know

Version: 1.78.2
Commit: b3e4e68a0bc097f0ae7907b217c1119af9e03435
Date: 2023-05-10T14:47:05.613Z
Electron: 22.5.2
Chromium: 108.0.5359.215
Node.js: 16.17.1
V8: <IP_ADDRESS>-electron.0
OS: Linux x64 5.15.0-72-generic
Sandboxed: No
Steps to Reproduce:

Open vscode
Can't login with the following response

Have tested accordingly to https://github.com/microsoft/vscode/issues/182110
The proxy test output is:
Note: Make sure to replace all sensitive information with dummy values before sharing this output.

VS Code 1.78.2 (b3e4e68a0bc097f0ae7907b217c1119af9e03435)
Network Proxy Test 0.0.7
linux 5.15.0-72-generic x64

Settings:
- http.proxy:
- http.proxyAuthorization: null
- http.proxyStrictSSL: true
- http.proxySupport: override
- http.systemCertificates: true

Environment variables:

Sending GET request to https://vscode.dev/codeExchangeProxyEndpoints/github/login/oauth/access_token...
vscode-proxy-agent: DIRECT
Received response:
- Status: 200 OK
Certificate chain:
- Subject: vscode.dev (Microsoft Corporation)
  Subject alt: DNS:vscode.dev
  Validity: May 20 00:28:26 2023 GMT - Nov 16 00:28:26 2023 GMT
  Fingerprint: B0:B3:AA:59:36:B5:B3:10:57:6B:44:A0:08:3D:75:C9:61:0B:CF:9C
- Subject: Microsoft Azure TLS Issuing CA 06 (Microsoft Corporation)
  Validity: Jul 29 12:30:00 2020 GMT - Jun 27 23:59:59 2024 GMT
  Fingerprint: 30:E0:17:61:AB:97:E5:9A:06:B4:1E:F2:0A:F6:F2:DE:7E:F4:F7:B0
- Subject: DigiCert Global Root G2 (DigiCert Inc)
  Validity: Aug  1 12:00:00 2013 GMT - Jan 15 12:00:00 2038 GMT
  Fingerprint: DF:3C:24:F9:BF:D6:66:76:1B:26:80:73:FE:06:D1:CC:8D:4F:82:A4
  Self-signed
Local root certificates:
- Subject: C=US O=DigiCert Inc OU=www.digicert.com CN=DigiCert Global Root G2
  Validity: Aug  1 12:00:00 2013 GMT - Jan 15 12:00:00 2038 GMT
  Fingerprint: DF:3C:24:F9:BF:D6:66:76:1B:26:80:73:FE:06:D1:CC:8D:4F:82:A4
  Issuer: C=US O=DigiCert Inc OU=www.digicert.com CN=DigiCert Global Root G2

No wonder that their was a domain lookup issue to begin with as it uses NSFP vscode-sync.trafficmanager.net networks, so had to whitelist the unsafe domain in our local RPZ firewall
Time    Client                                          Protocol     Server       ID    Name                      Type  Lat.   TC RD AA Rcode
-2297.1 <IP_ADDRESS>:48220                                 DoUDP                     10497 vscode.dev.               A               RD    Question
-2297.1 <IP_ADDRESS>:48220                                 DoUDP        [::1]:5302   10497 vscode.dev.               A     0.3       RD    Non-Existent domain
-2297.1 <IP_ADDRESS>:60648                                 DoUDP                     29990 vscode.dev.               A               RD    Question
-2297.1 <IP_ADDRESS>:60648                                 DoUDP        [::1]:5302   29990 vscode.dev.               A     0.1       RD    Non-Existent domain
-2297.1 <IP_ADDRESS>:59928                                 DoUDP                     19129 vscode.dev.               A               RD    Question
-2297.1 <IP_ADDRESS>:59928                                 DoUDP        [::1]:5302   19129 vscode.dev.               A     0.2       RD    Non-Existent domain
-2297.1 <IP_ADDRESS>:42328                                 DoUDP                     42226 vscode.dev.               A               RD    Question
-2297.1 <IP_ADDRESS>:42328                                 DoUDP        [::1]:5302   42226 vscode.dev.               A     0.1       RD    Non-Existent domain
-1764.3 <IP_ADDRESS>:42961                                 DoUDP                     1950  vscode.dev.               A               RD    Question
-1764.3 <IP_ADDRESS>:42961                                 DoUDP        [::1]:5302   1950  vscode.dev.               A     0.3       RD    No Error. 2 answers
-930.8  <IP_ADDRESS>:47091                                 DoUDP                     60315 vscode.dev.               A               RD    Question
-930.8  <IP_ADDRESS>:47091                                 DoUDP                     6041  vscode.dev.               AAAA            RD    Question
-930.8  <IP_ADDRESS>:47091                                 DoUDP        [::1]:5302   60315 vscode.dev.               A     0.2       RD    No Error. 2 answers
-930.8  <IP_ADDRESS>:47091                                 DoUDP        [::1]:5302   6041  vscode.dev.               AAAA  0.1       RD    No Error. 0 answer

Despite all this, vscode can still not connect, I have a feeling this is 2FA related issue

Can you follow these steps so that we can get more information on what's going on?

Trigger the sign in
Wait for the issue to happen...
Open the Output pane (ctrl+shift+u I think on Linux)
drop in this issue he contents of the following:

GitHub Authentication Output channel
Main output channel

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


ocr recognition based on crnn

 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.


use the meta package instead of the pattern

the cloud_admin pattern is not in the SLE12 Cloud repo

Well, we could just always use the package (unless it didn't exist in Cloud 4, but I think it did?).
There might be other references (in the backup / restore code, for instance).

Well, we could just always use the package (unless it didn't exist in Cloud 4, but I think it did?).

@vuntz i cant find this package in D:C:4

or we could add the pattern.. afaik its not possible to have an addon product installing a package directly, we need to add the pattern dependency there.

I've added the pattern back to the media in staging.. so this change shouldn't be necessary anymore.

@dirkmueller thanks. i will close this then


cherry-pick: oadp-1.4: OADP-3050: Remove unwanted BSL/VSLs on create/edit DPA (#1525)

(cherry picked from commit fee74a5a7da9625bbe0dc444679a4e0e0718d919)
Why the changes were made
This is a cherry-pick to oadp-1.4 for OADP-3050: Remove unwanted BSL/VSLs on create/edit DPA
How to test the changes made
Use make deploy-olm

/retest


Global Search

Search methods exist for Projects and Groups, but not for the Global Search endpoints
https://docs.gitlab.com/ce/api/search.html#global-search-api

If I am not wrong, existing methods for search are just top level searches for projects and groups by name. The ones mentioned here essentially searches by scope inside particular groups, particular projects or globally. We would need to build the wrapper for all these endpoints, as a separate Search API endpoint


Please add Fritz-Haber-Institute Berlin

le-mail.txt

@EricLiberra First stage of verification passed, official domain is fhi-berlin.mpg.de as far as I verified. This is just an informational note. Pull request is still in the review. I appreciate your patience while waiting for the final decision.

@EricLiberra Please provide us with:

the school official website URL
the school street address, including city and country

@Aguaconsilius Please create a separate pull request for your school.

https://www.fhi.mpg.de/de
Fritz-Haber-Institut der Max-Planck-Gesellschaft
Faradayweg 4-6
14195 Berlin
Germany
Am 07.03.2022 10:49, schrieb Philip Torchinsky:

@EricLiberra [1] Please provide us with:

the school official website URL
the school street address, including city and country

@Aguaconsilius [2] Please create a separate pull request for your
school.
--
Reply to this email directly, view it on GitHub [3], or unsubscribe
[4].
Triage notifications on the go with GitHub Mobile for iOS [5] or
Android [6].
You are receiving this because you were mentioned.Message ID:
@.***>

Links:
[1] https://github.com/EricLiberra
[2] https://github.com/Aguaconsilius
[3] https://github.com/JetBrains/swot/pull/13703#issuecomment-1060402637
[4]
https://github.com/notifications/unsubscribe-auth/AUN2RGQPB4IUOQCPDG67EZTU6XGJPANCNFSM5P7OLQYA
[5]
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
[6]
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub


cmd/compile: BoltDB with SSA crashes with: unexpected fault address 0xc420a00000

What version of Go are you using (go version)?
go version go1.7 darwin/amd64
go version go1.7 linux/amd64

What operating system and processor architecture are you using (go env)?
GOARCH="amd64"
GOBIN=""
GOEXE=""
GOHOSTARCH="amd64"
GOHOSTOS="darwin"
GOOS="darwin"
GOPATH=""
GORACE=""
GOROOT="/usr/local/Cellar/go/1.7/libexec"
GOTOOLDIR="/usr/local/Cellar/go/1.7/libexec/pkg/tool/darwin_amd64"
CC="clang"
GOGCCFLAGS="-fPIC -m64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fdebug-prefix-map=/var/folders/lm/g9hbhwd10gj8g_t64zzm63pm0000gn/T/go-build065044530=/tmp/go-build -gno-record-gcc-switches -fno-common"
CXX="clang++"
CGO_ENABLED="1"

GOARCH="amd64"
GOBIN=""
GOEXE=""
GOHOSTARCH="amd64"
GOHOSTOS="linux"
GOOS="linux"
GOPATH=""
GORACE=""
GOROOT="/usr/local/go"
GOTOOLDIR="/usr/local/go/pkg/tool/linux_amd64"
CC="gcc"
GOGCCFLAGS="-fPIC -m64 -pthread -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build785786852=/tmp/go-build -gno-record-gcc-switches"
CXX="g++"
CGO_ENABLED="1"

What did you do?
When creating a number of nested buckets, my app will intermittently crash. Here is the relevant part of the stack trace. The location of the failure is quite consistent under both Mac OS and Linux.

unexpected fault address 0xc420a00000
fatal error: fault
[signal SIGBUS: bus error code=0x2 addr=0xc420a00000 pc=0xef856]
goroutine 7 [running]:
runtime.throw(0x27f950, 0x5)
/usr/local/Cellar/go/1.7/libexec/src/runtime/panic.go:566 +0x95 fp=0xc42004f210 sp=0xc42004f1f0
runtime.sigpanic()
/usr/local/Cellar/go/1.7/libexec/src/runtime/sigpanic_unix.go:21 +0x1d0 fp=0xc42004f268 sp=0xc42004f210
github.com/boltdb/bolt.(*node).write(0xc420098070, 0xc4209ffff0)
/Users/ebusto/Perforce/mq-watch/src/github.com/boltdb/bolt/node.go:205 +0x86 fp=0xc42004f3a8 sp=0xc42004f268
github.com/boltdb/bolt.(*Bucket).write(0xc42004f4c0, 0xc420098070, 0x9, 0x0)
/Users/ebusto/Perforce/mq-watch/src/github.com/boltdb/bolt/bucket.go:598 +0xb1 fp=0xc42004f408 sp=0xc42004f3a8
github.com/boltdb/bolt.(*Bucket).CreateBucket(0xc4200bec40, 0xc420910600, 0x9, 0x9, 0x9, 0x9, 0x0)
/Users/ebusto/Perforce/mq-watch/src/github.com/boltdb/bolt/bucket.go:181 +0x2bf fp=0xc42004f508 sp=0xc42004f408
pkg/journal.(*TX).set(0xc420152028, 0xc4200bec40, 0xc4209105f6, 0x9, 0x9, 0x237f80, 0xc4205a85a0, 0x15)

What did you expect to see?
Under Go 1.6, and Go 1.7 with SSA disabled (go build -gcflags="-ssa=0"), Bolt will happily create buckets without fail.

What did you see instead?
SIGBUS on Mac OS, and SIGSEGV on Linux.

This may be a duplicate of #16769.  A unsafe pointer conversion produces also the byte sequence c420 unexpectedly.

A helpful fellow in the Gopher slack channel produced this test case.

Looking at this.   I did notice an appearance of the u-word on github.com/boltdb/bolt/node.go:205

Changing the depth from rand.Intn(10) to 100 seems to cause it to more consistently and quickly crash for me. Since I'm basically shooting blind, YMMV. :)

After playing around for a bit, I believe I've found the problem.
BoltDB allocates byte slices for some structs, and uses a marker field on the end of the page type to indicate where the key/value pairs for that page start being stored. In the case that the page has no key/value pairs, it allocates less space than for the entire struct. Later, we construct a slice pointing at that last marker field. Since there were no key/value pairs, the slice is unused, but under the SSA code, something attempts to do a read anyway. When the allocated memory happens to end right at some unmapped memory or something, a SIGBUS happens.
It seems like the main take away is that before it wasn't a problem to create a slice pointing past some allocation, but now it is. No idea if that's intended behavior, or whatever.

Can you provide a minimal test case, or at least a minimal representative sketch of what you think the problem is?

The playground link above is fairly minimal. Most of it is to exercise making as many page writes as possible. The slice is constructed and read from every time, but it will only crash when the bytes after the allocation will cause a fault. If there's a debug flag that puts guard pages around memory allocations that would make this much more deterministic.
I'll do my best with an ascii diagram.
+---------------------------------------+
|Full allocation                        |
+--------------------+------------------+------|
|Some bucket header  |The page struct   |p.ptr |
|--------------------|------------------|------|
|blah fields here    |fields here       |      |
+--------------------+------------------+------+

We construct a slice who's backing array starts at p.ptr, which is outside of the allocation. The slice ends up unused because the for loop has zero iterations, but for some reason, the SSA code dereferences the first byte of the slice (I think. asm output for both here: https://play.golang.org/p/QNYzVjU1ls)
I've added code to Bolt to avoid constructing these slices when it's known the size of the slice will be zero and the crashes go away.

This program demonstrates what the problem is:
package main

import "unsafe"

func main() {
	b := (*[10]byte)(unsafe.Pointer(uintptr(0xdeadbeef)))[0:3]
	_ = b
}

I see, thanks!  (Sorry, I thought the playground link was just a sample application that demonstrated an issue within BoltDB itself.)
So when slicing a pointer-to-array like that, we're supposed to check for and panic on nil.  We used to implement that with an explicit nil comparison; and if we found nil, we would conditional store to it to trigger a SIGSEGV.
It looks like with SSA we've switched to a more implicit nil check by unconditionally trying to load from the pointed-to address, which causes the SIGSEGV now also on non-nil-but-still-invalid pointers.
/cc @randall77

@mdempsky: Yes, that is my understanding as well.

#16727 is essentially the same problem.  So I guess the question is, can we do a nil check by doing a test load from the pointer to-be-nilchecked?  This is a change in behavior since 1.6, but as you can only trigger it by using unsafe, maybe that's ok.  But nevertheless we might want to consider going back to the old way.  Opinions?

Upon reading the rules outlined on https://golang.org/pkg/unsafe/ section 3 for pointer arithemetic states that: "the result must continue to point into the original allocated object. Unlike in C, it is not valid to advance a pointer just beyond the end of its original allocation".
That section is specifically talking about doing pointer arithmetic with unintptr conversions, but it seems that creating these slice headers is implicitly creating a pointer that is not pointing into any allocated object, and so I'd argue that the section still applies and code is invalid.

@zeebo That section starts with "If p points into an allocated object", which is referring to GC managed Go variables.  It's meant to allow pointer arithmetic within a variable, but not to limit us from adopting a moving garbage collector in the future.  (For example, you can't assume the distance between two different variables will remain the same.)  I don't think it's applicable here because in this case p points to unmapped memory.
That said, I do agree that this appears to be unspecified behavior.  I think the first option we should consider is how hard it is for applications to avoid relying on it.  It seems like slicing unmapped memory should be a relatively uncommon operation, whereas a simpler nil check benefits much more code.
Could BoltDB be reasonably modified to avoid creating these problematic slices?

@benbjohnson

@mdempsky I was chatting with @zeebo yesterday and I'm going to make a patch today. I'm happy to fix it on my side. Thanks for all the investigation everybody! 👍

In this case, we are starting with GC managed Go variables. A byte slice is created and we use unsafe to create a pointer to a struct inside of it, but the struct extends past the end of the allocation. We then use field access to essentially do pointer arithmetic to find where we should create the slice, and it is created past the end of the allocation.

On Aug 18, 2016, at 1:10 AM, Matthew Dempsky<EMAIL_ADDRESS>wrote:
@zeebo That section starts with "If p points into an allocated object", which is referring to GC managed Go variables. It's meant to allow pointer arithmetic within a variable, but not to limit us from adopting a moving garbage collector in the future. (For example, you can't assume the distance between two different variables will remain the same.) I don't think it's applicable here because in this case p points to unmapped memory.
That said, I do agree that this appears to be unspecified behavior. I think the first option we should consider is how hard it is for applications to avoid relying on it. It seems like slicing unmapped memory should be a relatively uncommon operation, whereas a simpler nil check benefits much more code.
Could BoltDB be reasonably modified to avoid creating these problematic slices?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

I posted a fix for BoltDB here: https://github.com/boltdb/bolt/pull/584
It now checks for pages which don't extend past the end of the header before building the slice header.

I'm going to close this issue.  It is fixed on the BoltDB side.


Balancer: Consider storing normalized pool weight in state

At the moment, balancer pools store an unnormalized weight for every asset, and re-computes the normalized weight on ~every action.
We should consider storing the normalized weight for each pool asset. At the moment, this would look like the following field going in PoolAsset, but the abstraction for how weights are handled should improve in the future as well.
  // Weight that is normalized s.t. the sum of all pool assets' weights
  // equals 1. If the user provides this value, it is ignored. This should only
  // ever be set by the state machine. This is left as a TODO for a future PR.
  // string normalizedWeight = 3 [
  //  (gogoproto.customtype) = "github.com/cosmos/cosmos-sdk/types.Dec",
  //  (gogoproto.moretags) = "yaml:\"normalized_weight\"",
  //  (gogoproto.nullable) = true
  // ];

The changes in #1343 helped us see that there aren't many cases where normalized weights are needed. Therefore, decided not to pursue this change


Need doc to support users upgrading from KDD on 2.1

Users who have installed according to this doc:
http://docs.projectcalico.org/v2.1/getting-started/kubernetes/installation/hosted/k8s-backend/
Need to continue to be supported when they upgrade to calico 2.2.
The 2.2 KDD docs have manifests which enable BGP routing and don't mention the scenario from the 2.1 docs, leading to confusion about support.
Options:

Continue to maintain a policy-only manifest, OR
Document that the KDD manifest now enables BGP networking by default and include instructions for how to disable it for policy-only

@robbrockbank This is probably related to the other bugs I just assigned you


Bugfix for internal rendering

dspy_driver was undefined, causing internal render crash.

I just commited a similar change!  Thanks though.


Avoid seeking on src when start time is 0

Close: https://github.com/google/shaka-player/issues/3518

Thanks for your contributions!


Best practice to mantain scalarSchemas option

Is ther a way to keep up to date the scalarSchemas option with my zodValidations in a shared package?
The only way that I can think of right now is copying & pasting my zodValidations and setting them in the scalarSchemas as a string but I think there has to be another way like generating the zod string reading the source code of another function (but at the same time that sounds like overengineering to me).
Did anyone face this challenge?

I would think that if the scalarSchemas were out of date, the type-check would give an error, but isn't that what you are talking about?

I would think that if the scalarSchemas were out of date, the type-check would give an error, but isn't that what you are talking about?

No, that isn't what I was talking about in my issue.

What I did to "resolve" this the following:
I did created a scalars package in my monorepo so frontend & backend can share the scalars code.
Then I did added an import line in the codegen generated files with the graphql-codegen add plugin and imported all my scalar package exports with an import alias
Also I configured the schalarsSchema entry for each custom schema that I have I call the mapToScalarSchemasMap to map the schema function reference to a string that is a function call to my custom schema.
Here is my codegen.ts
import { CuitScalarSchema, NameScalarSchema, PasswordScalarSchema, PermissionScalarSchema, UsernameScalarSchema } from;
const GRAPHQL_SCHEMA_URL = process.env.NEXT_PUBLIC_APP_GRAPHQL_API_URL;
const CODEGEN_FOLDER_PATH = "./__generated/";
const SCALARS_MODULE_IMPORT_ALIAS = 'scalars'

const config: CodegenConfig = {
  overwrite: true,
  schema: GRAPHQL_SCHEMA_URL,
  documents: ["./src/**/*.{ts,tsx}"],
  generates: {
    [pathInsideFolder(CODEGEN_FOLDER_PATH, "gql/client/")]: {
      preset: "client",
      plugins: [],
      presetConfig: {
        gqlTagName: "gql"
      }
    },
    [pathInsideFolder(CODEGEN_FOLDER_PATH, "gql/zod-schemas.ts")]: {
      plugins: [
        "typescript-validation-schema",
        {
          add: { // here add an import line in the codegen generated files
            content: `import * as ${SCALARS_MODULE_IMPORT_ALIAS} from '@package/scalars';`
          }
        }
      ],
      config: {
        schema: "zod",
        importFrom: "./client/graphql",
        strictScalars: true,
        scalars: {
          CUIT: "string",
          Name: "number",
          Password: "string",
          Permission: "string",
          Username: "string",
        },
        scalarSchemas: {
          CUIT: mapToScalarSchemasMap(CuitScalarSchema),
          Name: mapToScalarSchemasMap(NameScalarSchema),
          Password: mapToScalarSchemasMap(PasswordScalarSchema),
          Permimssion: mapToScalarSchemasMap(PermissionScalarSchema),
          Username: mapToScalarSchemasMap(UsernameScalarSchema)
        },
      }
    }
  }
};

export default config;

function pathInsideFolder(folderPath: string, subpath: string): string {
  return path.join(folderPath, subpath);
};

function mapToScalarSchemasMap(reference: () => any) {
  return `${SCALARS_MODULE_IMPORT_ALIAS}.${reference.name}()`;
}

so the generated file looks like this:


Enhancement: Merge multiple flightaware links into one output file

This is a low-priority ER, one which I am primarily logging for future users of the tool to comment on if perhaps this becomes a more needed feature.
I have had several cases where a flight including a stop-and-go or a full-stop-taxi-back gets split automatically by Flightaware into two separate flights.
It would be helpful to be able to paste multiple flightaware links and have them all concatenated into a single output file containing the tracklog for the entire flight.

Great suggestion! This actually turned out to be a pretty easy addition. I've tested several example flight sets but definitely open an issue if anything strange makes it way into the output csv.

Awesome work, thanks for doing that! Seems to work great so far!


Replace isA with type for JSON-LD as per new EPCIS JSON/JSON-LD Schema

Update the algorithm & examples to replace isA field with type as per recent changes in EPCIS event schema
Reference: https://github.com/gs1/EPCIS/blob/master/JSON-Schema/EPCIS-Event-JSON-Schema.json
FYI: @Echsecutor , @RalphTro

Many thanks for adding this issue/submitting the PR, @dakbhavesh!
Once the spec is ratified and we have some bandwidth, we can tidy everything up with joint forces.

Closing this issue as PR#64 is approved.


Run E2E tests only for frontend directory

Description

#806 introduced a change where the frontend tests are run on every push. However, it makes more sense to run the E2E tests only when frontend changes are made, so this PR adds an event filter that checks if it's a push to main or to a pull request in the frontend/* directory

@codemonkey800 Are there any scenarios where non-frontend changes might impact functionality tested as part of the e2e tests?

@codemonkey800 Yes, breaking changes to the schema as you've described could be one issue if not coordinated, as well as other unforeseen issues with data validation as we've encountered in the past.  It's also possible someone could do a large refactor and accidentally remove or rename endpoints.
Obviously when it's changes we are knowingly introducing we should do our best to ensure frontend and backend are aligned, but accidents/bugs happen & having tests would be one safeguard against this.
I'm curious if this is motivated due to the time it takes for the CI checks to run, or any other concerns with having it run against backend changes as well?

@codemonkey800 Good point on infra changes - maybe we could just run on only frontend and backend dirs.  @manasaV3 @klai95 curious for your input as well!

@codemonkey800 Good point on infra changes - maybe we could just run on only frontend and backend dirs. @manasaV3 @klai95 curious for your input as well!

@codemonkey800 @richaagarwal I second on running on only frontend and backend dirs, as the frontend E2E test do take up quite some time (7-10 minutes), and at times I'd need to rerun them 1-2 times due to flaky tests.

ooh thanks for the additional context @codemonkey800 ! I was actually wondering about whether this hits backend code at all, so very good to know.  In that case, this PR looks good 👍🏼


I wasn't sure, so here's a PR that detects node core's deepEqual and lets it get the nice diff behaviour. :tada:

@boneskull @glenjamin is there anything holding of a merge?

This PR is currently no longer mergable, and with the inclusion of unexpectedjs I think it's no longer relevant either.
Feel free to update if you think it still adds value though, and thanks for the effort!

Could you point me towards the PR for the unexpected change you're referring to? I tried to search but couldn't seem to find anything.
The specific aim here was to improve formatting when using Node core's assert.deepEqual, I'm happy to rebase the PR.

This one (which was indeed tricky to find): #1349
But now that I'm looking at it, it seems this was only for the HTML reporter. If you'd like to rebase your changes I'd be happy to have an other look at merging them :)

I looked into this a bit more, the change is no longer needed due to #1626 which changes the default behaviour to always show diffs.

@glenjamin :+1: thanks


Use it only on php file

I saw that padawan is executed also on html files, there is a way to disable this behaviour?

Uhm seems more a problem of nvim-yarp that use a lot of memory and not of padawan.


[FR] Include iscrowd attribute when exporting OpenImages in COCO format

Instructions
Thank you for submitting an issue. Please refer to our
issue policy
for information on what types of issues we address.
Please fill in this template to ensure a timely and thorough response.

Place an "x" between the brackets next to an option if it applies. Example:

[x] Selected option

Please delete this section (all content above this line) before submitting
the issue

Proposal Summary
The default exporting of Open Images in the COCO format does not convert 'IsGroupOf' from Open Images to 'iscrowd' in the COCO format.
I also do not see any way to easily do this (e.g. renaming the IsGroupOf field), without writing a custom data exporter.
Motivation

Why is this use case valuable to support for your project(s) or
organization?
Open Images is a popular object detection dataset and COCO is a common format.

Why is it currently difficult to achieve this use case? (please be as
specific as possible about why related FiftyOne features and components are
insufficient)
There is no way to rename 'IsGroupOf' to 'iscrowd' and have it work out of the box.

What areas of FiftyOne does this feature affect?

[ ] App: FiftyOne application
[x] Core: Core fiftyone Python library
[ ] Server: FiftyOne server

Details
(Use this section to include any additional information about the feature. If
you have a proposal for how to implement this feature, please include it here.)
Willingness to contribute
The FiftyOne Community encourages new feature contributions. Would you or
another member of your organization be willing to contribute an implementation
of this feature?

[ ] Yes. I can contribute this feature independently.
[x] Yes. I would be willing to contribute this feature with guidance from
the FiftyOne community.
[ ] No. I cannot contribute this feature at this time.

Hey @mswoff 👋
I agree that it would be useful to allow customizing the iscrowd attribute when exporting in COCO format. Here's the place where iscrowd is currently hard-coded:
https://github.com/voxel51/fiftyone/blob/21b4784c2f55859e5c775cbebdd00c74f7df500f/fiftyone/utils/coco.py#L639-L645
If you were to parameterize this and expose it as a parameter iscrowd="iscrowd" on the COCODatasetExporter class in that module, then you could export via the syntax below:
import fiftyone as fo

dataset = fo.load_dataset(...)

# Pulls crowd annotation from the `IsGroupOf` field/attribute of all Detections
dataset.export(
    "/path/for/export",
    fo.types.COCODetectionDataset,
    iscrowd="IsGroupOf",
)

Are you open to giving it a shot and sharing a PR? We'd be happy to get this out in the next release

Thank you for the suggestion! However, I could not figure out how to make
this change.
But another potential way that is maybe more extensible would be to add the
ability to rename detection fields or dynamically make new fields.
On Mon, Jun 14, 2021 at 7:14 PM Brian Moore @.***>
wrote:

Hey @mswoff https://github.com/mswoff 👋
I agree that it would be useful to allow customizing the iscrowd
attribute when exporting in COCO format. Here's the place where iscrowd
is currently hard-coded:
https://github.com/voxel51/fiftyone/blob/21b4784c2f55859e5c775cbebdd00c74f7df500f/fiftyone/utils/coco.py#L639-L645
If you were to parameterize this and expose it as a parameter
iscrowd="iscrowd" on the COCODatasetExporter class in that module, then
you could export via the syntax below:
import fiftyone as fo
dataset = fo.load_dataset(...)
Pulls crowd annotation from the IsGroupOf field/attribute of all Detections
dataset.export(
"/path/for/export",

fo.types.COCODetectionDataset,

iscrowd="IsGroupOf",

)
Are you open to giving it a shot and sharing a PR? We'd be happy to get
this out in the next release
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/voxel51/fiftyone/issues/1070#issuecomment-861117688,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AFZPTNBV64SZ2BAFPDNJCXDTS2ZSDANCNFSM46WGKXBA
.

@mswoff aha, the latter is already possible! check this out:
import fiftyone as fo
import fiftyone.zoo as foz
from fiftyone import ViewField as F

dataset = foz.load_zoo_dataset(
    "open-images-v6",
    split="validation",
    label_types=["detections"],
    max_samples=10,
)

# Option 1: add new attribute in a loop
for sample in dataset:
    for detection in sample.detections.detections:
        detection.iscrowd = int(detection.IsGroupOf)

    sample.save()

# Option 2 (equivalent): use views
view = dataset.set_field("detections.detections.iscrowd", F("IsGroupOf").to_int())
view.save()

dataset.export(
    "/tmp/export",
    fo.types.COCODetectionDataset,
    label_field="detections",
)

python -m json.tool /tmp/export/labels.json

        ...
        {
            "id": 47,
            "image_id": 9,
            "category_id": 19,
            "bbox": [
                539.2,
                176.0,
                329.6,
                329.6
            ],
            "segmentation": null,
            "area": 108636.2,
            "iscrowd": 0
        }
    ]
}

Renaming and cloning fields is also possible:
# rename fields via loop
for sample in dataset:
    for detection in sample.detections.detections:
        detection.iscrowd = detection.IsGroupOf
        del detection.IsGroupOf

    sample.save()

# batch rename field
dataset.rename_sample_field(
    "detections.detections.IsGroupOf",
    "detections.detections.iscrowd",
)

# batch clone (copy) field
dataset.clone_sample_field(
    "detections.detections.IsGroupOf",
    "detections.detections.iscrowd",
)

Exporting in COCO format currenly ignores other attributes that your Detections may have, since the COCO format spec doesn't include them.
What's your use case for wanting to store other attributes in the COCO format? Its certainly possible, but I'm curious what workflow you have in-mind that you'd want to do that.

Oh amazing!! I thought this must be possible but couldn't figure it out so
thank you!!
I meant that this feature would be useful with other datasets where you
import using one a field with some name (e.g. is IsGroupOf) and then need
to export with a different name (e.g. iscrowd), but it looks like you
already thought that was true too!
On Tue, Jun 15, 2021 at 12:20 PM Brian Moore @.***>
wrote:

Exporting in COCO format currenly ignores other attributes that your
Detections may have, since the COCO format spec doesn't include them.
What's your use case for wanting to store other attributes in the COCO
format? Its certainly possible, but I'm curious what workflow you have
in-mind that you'd want to do that.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/voxel51/fiftyone/issues/1070#issuecomment-861768353,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AFZPTNB6UKCLTAKZTJDIVODTS6RYBANCNFSM46WGKXBA
.

As of fiftyone==0.12.0 this is fully supported:
import fiftyone as fo
import fiftyone.zoo as foz

dataset = foz.load_zoo_dataset(
    "open-images-v6",
    split="validation",
    label_types=["detections"],
    max_samples=10,
)

dataset.export(
    labels_path="/tmp/coco.json",
    dataset_type=fo.types.COCODetectionDataset,
    iscrowd="IsGroupOf",
    extra_attrs=False,
)


Implement Rake task to check REFERENCE.md

I think it's not that beautiful to call a rake task from the module, but modulesync_config templates it and I cannot move the reference task to voxpupuli-release. I did  some local testing and the check seems to work fine.

So I thought a bit more about this. Isn't this something that we should implement in puppet-strings directly so it's usable for the wider community?
There's this definition of the reference generation:
https://github.com/puppetlabs/puppet-strings/blob/5955970a8c7bad66e7b20da344afa4d245f33ab3/lib/puppet-strings/tasks/generate.rb#L50-L52
Can we also modify one that and write it to a temporary file and diff the two as pure Ruby? That way you never overwrite what's on disk (making it non-destructive) and doesn't rely on git.

I like the idea to make this more flexible (move it directly to puppet-strings), but I don't know how to implement this properly in puppet-strings. I thought about making this non-destructive by writing into another file, but I didn't find a proper option in puppet-strings for that. If someone here wants to help out let me know.

Would https://github.com/puppetlabs/puppet-strings/pull/291 address that?


Improve torchserve doc readability

Copy-edits the torchserve README for better readability as well as consistency with https://github.com/kserve/kserve/pull/2531.

Thanks @rafvasq !!
/lgtm
/approve


Uncaught Error: Call to undefined function mb_strlen()

Hello, I've gotten this error:
Fatal error: Uncaught Error: Call to undefined function mb_strlen() in /var/www/html/assets/modules/parsedown/Parsedown.php:170 Stack trace: #0 /var/www/html/assets/modules/parsedown/Parsedown.php(39): Parsedown->lines() #1 /var/www/html/article.php(85): Parsedown->text() #2 {main} thrown in /var/www/html/assets/modules/parsedown/Parsedown.php on line 170

This is the text it was trying to parse: (I replaced "```" with "'''")
Step event:
'''
if(windowHasFocusLast) and (!window_has_focus(())
{
// Window had focus last frame, but lost focus this frame
show_message("The window is no longer in focus. :(");
}
'''

OK well it works now for some odd reason... 🤔


UIPG, UIST: Support Launchpad Page and Space Templates

Objects are implemented in ADT and now we want to implement those in an abapGit:
https://jira.tools.sap/browse/MILANO-515

@ViktoriaFreidel thanks, is this something you would like to open a pull request for?
we cannot see the internal SAP jira

AFAIK both are AFF types
So you can register new object type here https://github.com/abapGit/abapGit/blob/687c91bcf57761edbaf30c9bcd1118ea396bc3bb/src/objects/aff/zcl_abapgit_aff_registry.clas.abap#L49
and implement the object handler inheriting from zcl_abapgit_object_common_aff


clarify further widget activation issue

it's not sufficiently apparent or clear on https://coderefinery.github.io/installation/python/#jupyter

we had a couple of widget problems in Reykjavik, but they were all solved with the procedure described in the installation instructions. I can't see how we can improve the instructions further, so closing the issue


Ability to restore a database - is this available?

ISqlDatabase has a list of IRestorePoint, but I can't find a way to restore a database.  Is this currently supported?

@glaidler are you using Fluent or auto-generated sdk? Fluent does not support it.

Fluent.  Would be great if it did! :)

Restore point in time feature is not yet in the Fluent Azure Management Libraries. Recently, this feature arrived in SQL Database Swagger and is in the library backlog. We are planning to work on it in the in late Summer.

@glaidler as a workaround you can use AutoGenerated SQL library for that part https://www.nuget.org/packages/Microsoft.Azure.Management.Sql


SMTPClient

Error with the send_email and not send, mistmatch in method name.

Was corrected during the video.


Japanese calendar crash

(Required) Version Number: 8.0.3
Description
Crashes for Japanese calendar on JTACMonthView.monthStatus(for:), but unfortunately can't reproduce in debug. Mb some ideas why it could be crashing?
Steps To Reproduce
–
Expected Behavior
–
Additional Context
–

hmm. I merged the fix for the first crash on japanese calendar some years ago.
But another one?
Hmm. Because the Japanese calendar is so different from regular calendars, I need to get a reproducible crash so I can fix. This calendar is just so... different.

Can I at least get the crash log?

Can I at least get the crash log?

Nothing helpful but that:
0x103c55cfc JTACMonthView.monthStatus(for:) +<PHONE_NUMBER> (<compiler-generated>:4365393148), all users with Japanese calendar set, locale vary

ah. ok thats a good clue.
Were in the month of february. So i guess guess i can try setting my calendar to Japanese, and call that function for each date in that month.
Or have you already tried this?

Crashes from users logged even today, but I can't reproduce them, probably month isn't a case

i will look through the code today.

I thought the stack trace would have a list of calls until it got to that function.
So that i can know the stack of calls, but if all the crash has is just that one line, then this is hard to do.

Crashed: com.apple.main-thread
0  JTAppleCalendar                0x103c55cfc JTACMonthView.monthStatus(for:) +<PHONE_NUMBER> (<compiler-generated>:4365393148)
1  CoreUI                         0x104609f90 CalendarViewController.calculateIndexPath(for:) + 395 (CalendarViewController.swift:395)
2  CoreUI                         0x104607394 CalendarViewController.setSelectedState(for:) + 381 (CalendarViewController.swift:381)
3  CoreUI                         0x10462315c DatePickerCalendarViewController.setSelected(range:) + 160 (CalendarViewController.swift:160)
4  App                            0x102c062dc ViewController.viewDidLoad() + 89 (ViewController.swift:89)
5  App                            0x102c070e8 @objc ViewController.viewDidLoad() +<PHONE_NUMBER> (<compiler-generated>:4348342504)
6  UIKitCore                      0x187579550 -[UIViewController _sendViewDidLoadWithAppearanceProxyObjectTaggingEnabled] + 104
7  UIKitCore                      0x18757e184 -[UIViewController loadViewIfRequired] + 952
8  UIKitCore                      0x18757e570 -[UIViewController view] + 32
9  UIKitCore                      0x1874f9108 -[UINavigationController preferredContentSize] + 172
10 UIKitCore                      0x187576eb0 -[UIViewController _formSheetSizeForWindowWithSize:] + 44
11 UIKitCore                      0x1874a5ba0 -[_UISheetLayoutInfo _preferredSize] + 484
12 UIKitCore                      0x1874a60b8 -[_UISheetLayoutInfo _isBottomAttached] + 136
13 UIKitCore                      0x1874a67ac -[_UISheetLayoutInfo _fullHeightUntransformedFrame] + 120
14 UIKitCore                      0x1874a6d44 -[_UISheetLayoutInfo _activeDetentValues] + 160
15 UIKitCore                      0x1874adb30 -[_UISheetPresentationController _containerViewLayoutSubviews] + 628
16 UIKitCore                      0x188034378 -[UITransitionView layoutSubviews] + 92
17 UIKitCore                      0x188075b1c -[UIView(CALayerDelegate) layoutSublayersOfLayer:] + 2156
18 libobjc.A.dylib                0x1837e8a4c -[NSObject performSelector:withObject:] + 68
19 QuartzCore                     0x18a68ba9c -[CALayer layoutSublayers] + 292
20 QuartzCore                     0x18a68beec CA::Layer::layout_if_needed(CA::Transaction*) + 484
21 UIKitCore                      0x18806147c -[UIView(Hierarchy) layoutBelowIfNeeded] + 552
22 UIKitCore                      0x1874ab9e0 -[_UISheetPresentationController presentationTransitionWillBegin] + 1408
23 UIKitCore                      0x1874a1ffc -[_UIFormSheetPresentationController presentationTransitionWillBegin] + 56
24 UIKitCore                      0x18749dc08 __71-[UIPresentationController _initViewHierarchyForPresentationSuperview:]_block_invoke + 2400
25 UIKitCore                      0x18749b6cc __56-[UIPresentationController runTransitionForCurrentState]_block_invoke.478 + 532
26 UIKitCore                      0x18758baac __40+[UIViewController _scheduleTransition:]_block_invoke + 28
27 UIKitCore                      0x187bcc4ac _runAfterCACommitDeferredBlocks + 324
28 UIKitCore                      0x187bbbad0 _cleanUpAfterCAFlushAndRunDeferredBlocks + 236
29 UIKitCore                      0x187becd20 _afterCACommitHandler + 80
30 CoreFoundation                 0x183a4f524 __CFRUNLOOP_IS_CALLING_OUT_TO_AN_OBSERVER_CALLBACK_FUNCTION__ + 36
31 CoreFoundation                 0x183a4a1c4 __CFRunLoopDoObservers + 420
32 CoreFoundation                 0x183a4a774 __CFRunLoopRun + 1292
33 CoreFoundation                 0x183a49f40 CFRunLoopRunSpecific + 480
34 GraphicsServices               0x18dcc7534 GSEventRunModal + 108
35 UIKitCore                      0x187bc2a60 UIApplicationMain + 1940
36 App                            0x10275d180 main + 4 (main.swift:4)
37 libdyld.dylib                  0x1838c8e18 start + 4

Guess I found problem. When start-end dates for calendar is generated I just offset them, but for Japanese calendar in past there could be date like 2051 and 2100 in future (since they calculate years from new Emperor). So that's just index out of bounds problem, and it's on my side. But mb could be fixed in library itself?

Actually, I did debug further, and there Calendar returns -363 month for today date in Japanese calendar, so then it's not start-end range dates problem then.

So apparently it's not safe operate with date through dateComponents, cause they could return unexpected values in case Japanese calendar

But mb could be fixed in library itself?

yes it can, but first i need to understand Japanese Calendar.
hmm. if you have any suggestions then let me know.

What I already accomplished is that you should probably use different calendars for user and for calculation, since it's basically just abstraction on TimeInterval. So the problem starts when you try to get components, and, in my case were that I tried to calculate diff between dates, but in Japanese calendar there were 2051 year instead of 2019 or 2020, so there I've got that out of bounds exception with difference -361

ok thanks.
i will use this a information. And see what I can do from my end.
I am a little caught up so i will take some time on this.


Is it possible to set tool with dependencies ?

I am already familiar with lc.setTool( new LC.tools.Eraser() ); with core build.
But I am wondering if I can do it with literallycanvas.js ?
Thanks in Advance.

It can be done by doing like;
lc.setTool( new LC.tools.Eraser( lc ) );

Changing the tool works but it doesn't update css class names of the tools, i.e. it looks like that the previous tool is still selected


Persistent tools

I was wondering what would be the strategy to persist the changes in the studies.
For example, if a measurement tool is used on an image, I want to save it. If this particular image is accessed again, I want to see the annotations.

+1

Serialize the measurement data to JSON and save it with a reference to the imageId

Closing because Chris already answered this.
One example of saving and restoring state doing this can be found here:
https://rawgit.com/chafey/cornerstoneTools/master/examples/toolState/index.html


Update documentation and add blog

We need to curate external links of interest and post content that is
not code/issues for public consumption.
Also, fix the documentation part of https://github.com/vmware/docker-volume-vsphere/pull/583

@kerneltime - any update for this one ?

updated


Sysmon not installing from under %systemroot%

Hi, hope this is the right place for bug reports!
I'm encountering an issue when sysmon -i is run from a path under %systemroot%, sysmon isn't installing correctly:

sysmon.exe isn't copied to %systemroot%
sysmondrv.sys doesn't appear to be created anywhere
The sysmon service lists the original file path as its path.

Thanks!

Hello
this has been a known issue for some time. However I am pleased to say that this has now been resolved and the fix will be available shortly in Sysmon 10.3 and later.
Thanks for reporting. If you have any other issues the best place to report them is either via the Sysinternals forums (https://forum.sysinternals.com) or via email to<EMAIL_ADDRESS>We do monitor this site too but not as actively since this is mainly for documentation on the site itself.
MarkC (MSFT)


Create README.ua.md

Add a Ukrainian translation of README.md

Hey, not needed at this moment. Thanks for your contributions tho.


Files: encode local path on Windows

This encodes the local path in the pop up from the Files tab.

Hmm CI keeps fail on seemingly irrelevant tests. Good to go?

Is this a question for me?  Still looks good to me.  And looks like master is failing on those tests too.

Hmm CI keeps fail on seemingly irrelevant tests. Good to go?

Is this a question for me? Still looks good to me. And looks like master is failing on those tests too.

Thanks! Yeah just wanted an ack from someone before I hit the green button.