Development halt?

Hi, this is important and much needed project in the geoscience and mining space. I'm disappointed to see that it appears development has been halted? Is there a plan to continue development by Seequent or others? If so, perhaps it is worth shifting focus to adoption of the GEOH5 standard which appears to be well resourced by Mira https://geoh5py.readthedocs.io/en/stable/content/geoh5_format/index.html

Hi, this is important and much needed project in the geoscience and mining space. I'm disappointed to see that it appears development has been halted? Is there a plan to continue development by Seequent or others? If so, perhaps it is worth shifting focus to adoption of the GEOH5 standard which appears to be well resourced by Mira https://geoh5py.readthedocs.io/en/stable/content/geoh5_format/index.html

There is work happening on the next version.  In fact, there is a meeting next month to finalise what is in V2.  Details on that meeting can be found at https://www.eventbrite.ca/e/open-mining-format-v20-finalization-workshop-tickets-441189518727.

Thanks for flagging this @ngodber . We are actively working on creating the i/o between geoh5 and omf v0.9.0 so users can export in either format.
https://github.com/MiraGeoscience/omf/pull/7
We will PR back here when we are done, or hold until v2 is offical then update. Should be straight forward.
Looking forward for v2 release.

That is great news. For clarity it will be 'i' as well as the 'o'?
On Thu, 20 Oct 2022 at 15:40, domfournier @.***> wrote:

Thanks for flagging this @ngodber https://github.com/ngodber . We are
actively working on creating the i/o between geoh5 and omf v0.9.0 so users
can export in either format.
MiraGeoscience#7 https://github.com/MiraGeoscience/omf/pull/7
We will PR back here when we are done, or hold until v2 is offical then
update. Should be straight forward.
Looking forward for v2 release.
—
Reply to this email directly, view it on GitHub
https://github.com/gmggroup/omf/issues/121#issuecomment-1284966612, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AC2JLXSHH4QVH3SKRQMTVHDWEDLLVANCNFSM6AAAAAARJVXGKI
.
You are receiving this because you were mentioned.Message ID:
@.***>

Correct, the omf -> geoh5 is done, now working on the geoh5 -> omf. At least for the 5 objects that were supported in 0.9.0 (points, surface, curves, grid2D and block models)

Awesome - that's great to hear. That code is going to get a lot of leg work around here.

hi

Hi @ngodber
There is a steering committee meeting to discuss feedback/endorse OMF V2.0 this coming Wednesday (NZST/AEST).
Expect an announcement soon after.

Great news! Would I be correct in thinking the spec doc will go into the aforementioned github repo?

That is the logical place to put it. Documentation is one of the agenda items.

Hi @mikestewartseeq - Is there any update that can be provided on the likely release date of V2.0?  Maybe I missed the announcement?


Update google-cloud-bigquery to 1.130.0

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

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "com.google.cloud", artifactId = "google-cloud-bigquery" } ]

labels: library-update, semver-minor

Superseded by #68.


Disable video compression, add debugging to check videos in Github Ac…

…tions

Test result in public dashboard; https://dashboard.cypress.io/projects/8vuidn/runs/e0a3cf9c-9653-4b03-97cc-04178dd6adb8/test-results/044b4dba-9ee4-43ec-8db0-6fcf12c95df5
:heavy_check_mark:


fix(@angular/pwa): use relative paths in webmanifest

Use relative paths instead of absolute paths in manifest.webmanifest, so PWA (including the service worker) can work with apps with base-href different from just /. It's especially important since Angular CLI v9 as the new --localize option uses base-href values different from just /.
Fixes #16922
Fixes #15092

Also merged to 9.0.x patch branch.


Disable Geolocation by commenting it out in the config.js

also, add this comment
The geolocation button has been hidden from the user interface by commenting out the widgetpath for geolocation below. You can enable geolocation by uncommenting the widgetpath for geolocation. The geolocation button, however, will only work on browsers supporting geolocation over HTTP connections.  If a browser requires a HTTPS connection to support geolocation and the button is enabled, the button will not work, but the application will work correctly otherwise.

committed.
FYI @jessnoo @lindsayking
Need to test this before packaging

This has been tested.


Contributing to the library while using a different version of Node.js or NPM could make unexpected changes to the published packages

Expected Behavior
If another contributor makes changes to the repository, the files generated by Rollup for distribution should reflect only those changes, and nothing to do with the contributor's environment.
Current Behavior
If I am using a different version of Node.js or NPM and make a small change to any of the files in the src directory, and run npm dev, the generated files could differ beyond the change I've made.
Possible Solution

Include brief contributing instructions
Instruct contributors to use Node Version Manager and to use a specified version of Node.JS (Ideally the latest LTS version for longevity)
Include the specified version of Node.JS in .nvmrc so that contributors can run nvm use in the project directory to automatically install and select that version of Node.JS
Include the specified version of Node.JS in the engines property of package.json
Instruct contributors to install the specified version of NPM e.g. npm install<EMAIL_ADDRESS>-g
Include the specified version of npm in the engines property of package.json

Notes

This could make other contributors more confident that they won't destroy your library ;)
This would open the door to configuring a GitHub Action that automatically tags, releases and publishes new versions of the library on NPM after PRs are merged e.g. via Release Please
This could also open the door to automated tests

If you're keen, let me know and I can open a PR.

Hey once more @gridsystem, I'd like to apologize once more for keeping you waiting for so long. I really appreciate your determination to help and I'm more invested in bringing this library forward a bit more again, especially the npm package part.
The Contributing part of this repository isn't fleshed out yet, but I'm happy and thankful for any contributions and pull requests. I'm also more than happy to honor contributors in some way by listing them somewhere on the repository.
When I'm done with my testing in regards to the newly bundled library, which should now also work when imported via npm, I'm happy to invest time into this issue here as well. But I'm also open to accept pull requests that solve this issue and provide some instructions for potential contributors.
I'm currently on Node.js version v20.11.1 and npm version 8.19.2, but since those do not seem to be LTS versions, I'm happy to make the switch to Node.js v22.11.0 (LTS) and whatever npm version is associated with it. :)
While I wasn't working on this library directly, I implemented a new ascii shader which might qualify as a new rendering mode apart from the existing  brightness mode in the future. Essentially, it's a mode that attempts to find the most fitting ascii character from the given character set to produce the best possible representation of an input image. In the video below is a video of me sucking at Rocket League a few years ago, which is accurately asciified in real-time at 60 frames per second. I really like the results, could also see this working as a overlay for video games in general. 😄
https://github.com/user-attachments/assets/e686dd29-92cb-4826-9510-0bdfbfcddef8
Cheers!

Hey again @gridsystem! I have started working on this in a separate branch, which is also linked in this issue: https://github.com/humanbydefinition/p5.asciify/tree/11-contributing-to-the-library-while-using-a-different-version-of-nodejs-or-npm-could-make-unexpected-changes-to-the-published-packages
I have been testing around a bit and really like the functionalities that come with the suggestions you provided, thanks a bunch!
Except updating the README and the Wiki potentially, I have already pushed solutions for all the other suggestions you have made. The workflow implemented is currently bare-bones and does some redundant checks I think, but overall it should be able to check whether the source is bundled successfully and is not empty.
I'd love to have your feedback on this!
Regarding the README, i'd like to keep it short there and link to the Wiki, where I'm happy to provide more elaborate instructions on how to contribute. Hope I find motivation for that soon. :)
I'm definitely motivated to add more functionality to the library itself and improve the code structure overall. 🤞

Hey again, I decided to merge this to main already, since the most important things are done from my point of view.
As mentioned in the pull request, the Wiki entry regarding the Contributing Guidelines is still work-in-progress, as well as a more sophisticated workflow including proper tests.
I'll re-open this issue until then, also to receive potential feedback. :) I'm unsure if people are able to comment on a closed issue.


[only test] refactor mem_reuse in MutableBlock

Proposed changes
Issue Number: close #xxx

Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

run buildall

(From new machine)TeamCity pipeline, clickbench performance test result:
the sum of best hot time: 52.18 seconds
stream load tsv:          503 seconds loaded<PHONE_NUMBER>9 Bytes, about 141 MB/s
stream load json:         19 seconds loaded<PHONE_NUMBER> Bytes, about 118 MB/s
stream load orc:          65 seconds loaded<PHONE_NUMBER> Bytes, about 16 MB/s
stream load parquet:          32 seconds loaded 861443392 Bytes, about 25 MB/s
insert into select:          30.1 seconds inserted 10000000 Rows, about 332K ops/s
storage size:<PHONE_NUMBER>7 Bytes
https://doris-community-test-1308700295.cos.ap-hongkong.myqcloud.com/tmp/20230713112151_clickbench_pr_177656.html

run p0

run buildall

run buildall

run buildall

run p0

run buildall

(From new machine)TeamCity pipeline, clickbench performance test result:
the sum of best hot time: 51.51 seconds
stream load tsv:          537 seconds loaded<PHONE_NUMBER>9 Bytes, about 132 MB/s
stream load json:         19 seconds loaded<PHONE_NUMBER> Bytes, about 118 MB/s
stream load orc:          65 seconds loaded<PHONE_NUMBER> Bytes, about 16 MB/s
stream load parquet:          31 seconds loaded 861443392 Bytes, about 26 MB/s
insert into select:          29.0 seconds inserted 10000000 Rows, about 344K ops/s
storage size:<PHONE_NUMBER>3 Bytes


Update jsoniter-scala-core to 2.24.4

About this PR
📦 Updates com.github.plokhotnyuk.jsoniter-scala:jsoniter-scala-core from 2.17.9 to 2.24.4
📜 GitHub Release Notes - Version Diff
Usage
✅ Please merge!
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

⚙ Adjust future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "com.github.plokhotnyuk.jsoniter-scala", artifactId = "jsoniter-scala-core" } ]

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequests = { frequency = "30 days" },
  dependency = { groupId = "com.github.plokhotnyuk.jsoniter-scala", artifactId = "jsoniter-scala-core" }
}]

labels: library-update, early-semver-minor, semver-spec-minor, version-scheme:early-semver, commit-count:1

Superseded by #262.


Geminate "End of Turn" section reference

Last two questions in Geminate section (8.6) reference section 4.5 but should instead reference 5.5

thanks for posting :)

Updated with hyperlink


Should we allow to execute tasks in the extension host

VSCode Version: 1.12

In VS Code 1.12. there will be API to contribute tasks to the Run Task drop down. This will for example support cases were an extension wants to contribute task generated from special built tools which we don't want to hard code (make, cmake, npm, ant, ...)
I am pretty sure that users will ask soon to support something like Task.execute() to execute a task created in the extension in a terminal.
@Tyriar what is your take on this. You might want to look at the task API in vscode.proposed.d.ts. A task could offer some listening on output as well which would scope the output to the creator of the task.

So you want extensions to be able to contribute tasks through registerTaskProvider? What do we get from that that we wouldn't by introducing a global/user tasks.json file?
Does introducing task-related APIs break the plans of moving Tasks to an extension?

The problem is that people want to auto detect tasks like we do for gulp, grunt. And this needs the ability to run some code. You might want to look at the gulp extension which provides and example to auto detect gulp tasks.
Having the API will not break any plans to move the tasks to an extension. I will make things simpler since I don't need to send objects between the extension host and the renderer.

@chrisdias this might be interesting for you in terms of configuring the shell to use for docker. The task API has support to do so. So if we enable tasks to be executed you get this for free :-)

This could be really useful!  /cc @rkeithhill

Moving due to shifted priorities.

This is basically done already with the CustomExecution API.


[Identity] Rename auth_only to tenant_access

Description

Rename auth_only to a better name tenant_access, indicating bare tenant-level access.
Deprecate --allow-no-subscriptions, because:

Even with --allow-no-subscriptions, az login fails when ARM request is blocked.
Depending on whether the tenant has subscriptions, the id property in az account list/show is ambiguous: it can mean either tenant ID or subscription ID.

Testing Guide
> az login -h

    --allow-no-subscriptions [Deprecated] : Support access tenants without subscriptions.
                                            It's uncommon but useful to run tenant level commands,
                                            such as `az ad`.
        Option '--allow-no-subscriptions' has been deprecated and will be removed in version
        '3.0.0'. Use '--tenant-access' instead.

    --tenant-access                       : Only log in to the home tenant or the tenant specified
                                            by --tenant. CLI will not perform ARM operations to list
                                            tenants and subscriptions. Then you may run tenant-level
                                            commands, such as `az ad`, `az account get-access-
                                            token`.

Identity


Why seal PathComponentKind ?

The latest version breaks my usecase where i use parsed iso lang keys:
#[derive(Clone, Debug, Serialize, Deserialize, JsonSchema, Validate)]
#[serde(rename_all = "snake_case")]
pub struct I18nStruct {
    #[garde(dive)]
    pub i18n: HashMap<Lang, I18nName>,
}

why seal it ? people may need to have custom string-representable keys.

Can't remember why I did it. Maybe I was being overly defensive or something. Seems fine to unseal it


pasefMGF loss of precursor intensity?

Hi ProteoWizard!
When I make an MGF using the pasefMGF defaults using the MSConvert WindowsGUI I don't seem to get a precursor intensity. Is this just a case of the PEPMASS precursor mass and intensity not being separated?

Is this something I can fix on my end?
Thanks!

Answered on mailing list.


Wrongly Wriiten formula of CSA and TSA of hollow sphere

I would like to correct the formula.It should not be Internal surface area or external surface area,
In that column corresponding formula for CSA and TSA shoul be written

@sairish2001 Please assign it to me.I would like to work on it

Go ahead
Deadline 30 March,2021 (11:59 PM IST)


Broken link in New contributor course - community slide

Describe the issue
I was learning on kubernetes.dev and found link where page is not found. it is a Slack server listing page.
New Contributor course - community slide
Page not found
Screen recording 2023-10-05 18.28.13.webm

Thanks.  Ack, the Slack link is mangled.  As soon as I find the source for that slide, I'll fix it.

/triage accepted
/kind bug


Exit status should never be zero on failure

When the unibeautify CLI encounters an exception that causes a stack trace, it currently exits with exit code zero (which conventionally all Unix tools use to indicate a successful exit). We should have some countermeasure so that exit code is never zero on failure. Otherwise users will easily lose valuable source code when an editor plugin or script thinks that source code formatting was successful and trusts the output from unibeautify.

💯 % agree. I consider this a bug. Good catch, @lassik .

Thanks 😄  I was able to confirm that these now exit nonzero:
$ unibeautify
$ unibeautify -x
$ unibeautify --config-json '{' -l C

Is it the switch to yargs (60b86eef) that addressed this?
I wonder what would be a foolproof way to catch all situations including the likes of  #32? Unfortunately, this would be a critically important thing to get right, since editor plugins and especially batch jobs (like CI builds that run automatically on a server so a human doesn't get the chance to verify that the output is correct) will rely on correct code to stdout when the exit code is zero.
It would actually be a reasonable policy to write the program so it always exits nonzero by default, except in the specific few instances where we call exit(0). But I don't know much about Node/JS so I don't know how to go about this.

In any case, we could add safeguards to editor plugins to check that if stdout from CLI is zero bytes long, and the stdin that went to the CLI contained characters other than space/tab/newline/return, then that's an error. At least those Node stack traces seem to go into stderr so stdout stays blank.

Another good thing would be to ensure that errors always use exit code 2 or bigger. Exit codes 0/1 are sometimes useful for indicating true/false (see e.g. issue #19 and "The Cantrip Pattern" in The Art of Unix Programming).
Sorry for being so picky about this, but I know from experience that good use of exit codes makes scripting massively easier. I think now is the best time to establish strict and clean conventions while we can still do so without breaking backwards compatibility 😄

Yep, this is very WIP.  I'll close this, and when new things are implemented they will use the proper status codes.

Sorry for being so picky about this, but I know from experience that good use of exit codes makes scripting massively easier.

No apologizes necessary. I 💯% agree and the exit codes should be appropriate to allow for scripting and automation 👍 .


Running on gpu

Hi,
Thank you for the awesome work! It is very helpful!
Is it possible to run the code on GPU? I am running it on Ubuntu 18.04 and when I try to run, it does not run on gpu devices and runs on cpu. Is there any way to enforce the condition to run the example.py on gpu? I also tried to run export CUDA_VISIBLE_DEVICES=0, but it still seems to be running on cpu.
Many thanks!

To my knowledge, it runs on CPU only no matter what.

Hi @Cuda-Chen, do you think trying to run the dlib library on gpu can help?

@gd1925
It is possible to let dlib and OpenCV function run on GPU. However, the bus to GPU will be the bottleneck. Unless you have a particular reason to run on GPU (e.g., given a 4K resolution image and find the face), running on GPU will not be an idea.


Add Support for deleting tokens from the database via API

Is your feature request related to a problem?

Not really, I just would like to be able to clean up the database via the API.
Describe the solution you'd like

A possible API call for deleting a specified token.

I implemented the delete protokoll for the token endpoint
curl -X DELETE \
     -H "Authorization: SharedSecret <APIAdminPassword>" \
     -H "Content-Type: application/json" \
     http://localhost:5000/api/token/<token_name>

-> {"success": true}

although - I might still change the response


why use Ugly hack?

Thanks for great job!!
Ugly hack because I didn't use tensorflow's exact padding function
self.pad_5a = torch.nn.ConstantPad3d((0, 0, 0, 0, 0, 1), 0)
https://www.tensorflow.org/versions/r0.12/api_docs/python/nn/convolution
pad_along_height = ((out_height - 1) * strides[1] +
filter_height - in_height)
pad_along_width = ((out_width - 1) * strides[2] +
filter_width - in_width)
pad_top = pad_along_height / 2
pad_left = pad_along_width / 2
Why use ugly hack?
I think
pad_along_front = ((8-1)*2 + 2 - 16) = 0
pad_back = 0/2 = 0

First, I saw you did a very similar conversion in one of your repos almost at the same time as me ! :)
You are right, removing this padding does not create any problems.
At some version of my code, I obtained an error if I did not pad, and I forgot to remove this padding after I resolved it !
I just pushed the removal of this line to the master branch.
Thank you for your help !


Merge exid-types.json with gedcom-registries

exid-types.json predates gedcom-registries, and has some overlap with it (in particular, it duplicates the semantic purpose of https://github.com/FamilySearch/GEDCOM-registries/tree/main/uri/exid-types). We should merge these two to avoid duplicate information, probably keeping the registries because it is more versatile.

exid-types has: label, type, description, contact, change-controller, and reference.
These can be mapped to https://gedcom.io/terms/format fields as follows:

label -> label
type -> uri
description -> specification
contact -> contact
change-controller ("FamilySearch" for AFN/RIN/RFN) ->??? no current field
reference -> ??? no current field

Filed https://github.com/FamilySearch/GEDCOM.io/issues/220 in GEDCOM.io regarding change-controller and reference.

Adding one entry:

reference -> documentation

(see https://gedcom.io/terms/format)

https://github.com/FamilySearch/GEDCOM-registries/pull/102 added the data from exid-types.json to gedcom-registries.  exid-types.json can now be deleted.

The removal of the exid-types.json has left a number broken references in the documentation which need to be corrected.
https://github.com/FamilySearch/GEDCOM/blob/5c2eb6046972c21abd877a8b8ed5d2447ed5b260/extracted-files/tags/EXID-TYPE#L22C1-L36C18
https://gedcom.io/_pages/exid-type/


Run benchmarks as part of Zebra CI

Motivation

We currently do not run our benchmarks as part of CI; the zebra-chain::block benchmarks are currently broken by default because there is a misconfig of what test resources are available under which feature flags.
Solution

We may want to run benchmarks as part of CI in a manner similar to our coverage jobs (informational but not blocking) to track these over time and make sure they don't break silently.
Alternatives

Don't run benchmarks regularly as part of CI. They may continue to break silently.
Related Work

https://github.com/ZcashFoundation/zebra/pull/2288

+1! If we don't do that then we can end up with benchmarks gettings worse for whatever reason and having no immediate idea what the cause is (been there)

+1! If we don't do that then we can end up with benchmarks gettings worse for whatever reason and having no immediate idea what the cause is (been there)

That's a slightly different change - this ticket is about making sure benchmarks compile and run successfully.
@conradoplg can you open a different ticket for showing benchmark results in CI using a bot?

That's a slightly different change - this ticket is about making sure benchmarks compile and run successfully.
@conradoplg can you open a different ticket for showing benchmark results in CI using a bot?

Sure, done in https://github.com/ZcashFoundation/zebra/issues/2348


compile arch86 for iOS failed

Operating system or device - Godot version:
MacOS Sierra
Issue description:

When compiling with
scons p=iphone arch=x86 target=debug
the following errors were produced
please advise
thanks
thirdparty/etc2comp/Etc.h:38:8: error: no type named 'shared_ptr' in namespace 'std'
std::shared_ptr paucEncodingBits;
~~~~~^
thirdparty/etc2comp/Etc.h:38:18: error: expected member name or ';' after declaration specifiers
std::shared_ptr paucEncodingBits;
~~~~~~~~~~~~~~~^
thirdparty/etc2comp/Etc.cpp:99:25: error: no member named 'paucEncodingBits' in 'Etc::RawImage'
a_pMipmapImages[mip].paucEncodingBits = std::shared_ptr(image.GetEncodingBits(), [](unsigned char *p) { delete[] p; });
~~~~~~~~~~~~~~~~~~~~ ^
thirdparty/etc2comp/Etc.cpp:99:49: error: no member named 'shared_ptr' in namespace 'std'
a_pMipmapImages[mip].paucEncodingBits = std::shared_ptr(image.GetEncodingBits(), [](unsigned char *p) { delete[] p; });
~~~~~^
thirdparty/etc2comp/Etc.cpp:99:69: error: expected '(' for function-style cast or type construction
a_pMipmapImages[mip].paucEncodingBits = std::shared_ptr(image.GetEncodingBits(), [](unsigned char *p) { delete[] p; });
~~~~~~~~ ^
5 errors generated.
Steps to reproduce:
just compile with args mentioned
Link to minimal example project:

Hey @bartalluyn ,
Is this for Godot 2.1? I'll see if I can reproduce the same here

Must be master, etc2comp is not present in 2.1.

@vnen well that could explain it. It currently only compiles for 64bit and doesn't even run at the moment, still hoping we get there soon because I want to start on ARKit support.
At this time I'm not even sure if we can keep 32bit support, we're starting to use APIs that are only available in the later versions of the OS which only run on the 64 bit devices. Though I did recently learned this put iPhone 5C's at risk (last of the 32bit iPhones).
iPhone 5, and iPhone 5S are both 64bit phones as are anything after that.
Pretty sure Apple will start dropping support for the 5 soon anyway with iOS 11 coming out end of the year and probably an iPhone 8 next year and iPhone 4's don't even run the latest iOS.

Hi,
I took the 2.1 branch, and that indeed did the trick.  Everything went well, but when I copied over the executable and changed the executable name in the pList it told me I didn't have permissions.  Any idea here?

CC @tagcup, I guess the C+11 definition doesn't work in some cases/with some compilers.

Wait, I think etc2comp is only needed in tools builds. It should be disabled for iOS.

@akien-mga Yeah, seems that way, although just like @vnen said, this is similar to Android situation and etc2comp should be disabled for iOS


ycsb “ You have to open all column families. Column families not opened: usertable”

./bin/ycsb run rocksdb -s -P workloads/workloada -p rocksdb.dir=/tmp/ycsb-rocksdb-data -p rocksdb.optionsfile=workloads/ycsb-rocksdb-options.ini
When I perform the ycsb experiment, I add the ycsb-rocksdb-options.ini configuration file, and the above error is reported

same.
any idea? sad

well，i figure it out
you can solve this with read the given basic option file https://github.com/brianfrankcooper/YCSB/blob/master/rocksdb/src/test/resources/testcase.ini
just add  [CFOptions "usertable"] after [CFOptions "default"] and then you can run successfully

I had already solved the problem before.
See the README at this link.
I had to add that and one other thing.


Install error - 'stackName' failed to satisfy constraint

Install error - 'stackName' failed to satisfy constraint
EROR[02-28|18:16:05] Error: 2 validation errors detected: Value '' at 'stackName' failed to satisfy constraint: Member must satisfy regular expression pattern: [a-zA-Z][-a-zA-Z0-9]*|arn:[-a-zA-Z0-9:/._+]*; Value '' at 'stackName' failed to satisfy constraint: Member must have length greater than or equal to 1
INFO[02-28|18:16:05] Event: cluster_state: deleted
INFO[02-28|18:16:22] Event: cluster_state: deleting
INFO[02-28|18:19:58] Event: log: Using saved key pair (flynn)
INFO[02-28|18:19:58] Event: log: Allocating domain
INFO[02-28|18:19:58] Event: log: Fetching image manifest
INFO[02-28|18:19:59] Event: log: Generating start script
INFO[02-28|18:19:59] Event: log: Creating stack
INFO[02-28|18:20:14] Event: cluster_state: error

Were you deploying to the us-east-1 region? If so, this may have been related to today's AWS outage.

Indeed, I think it's AWS problem


fix: use status.managedProcessing to get the pipelineRun for Release

Fixes

https://issues.redhat.com/browse/KFLUXBUGS-1683
Description

Release service updated the status of Releases as part of https://issues.redhat.com/browse/RELEASE-1109 status.managedProcessing should be used instead of status.processing to get the data for PipelineRun
Type of change

[ ] Feature
[X] Bugfix
[ ] Code style update (formatting, renaming)
[ ] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[ ] Documentation content changes
[ ] Other (please describe):

Screen shots / Gifs for design review

How to test or reproduce?

Browser conformance:

[ ] Chrome
[ ] Firefox
[ ] Safari
[ ] Edge

/retest

/lgtm

/retest

/retest


Feature request : UPS monitoring with apcupsd

Hi,
First of all, do not hesitate to close this demand if it's out of scope, I would totally understand.
A few days ago, I was playing with Netdata, and I noticed that it magically shows statitistics for my UPS, which is managed by the apcupsd daemon on my host. There are graphs for current consumption (in W), minutes left, battery percentage, etc.
It would be very cool to have this kind of stats in Beszel ;)
Here is the Netadata documentation for reference : https://learn.netdata.cloud/docs/collecting-metrics/ups/apc-ups

I agree this would be a nice feature. I'll look into it. Would be nice if there was an open protocol though, rather than an APC specific thing.
We're also planning to add custom charts where you can supply data via command or file content, so it should be possible in the future even if direct support isn't added.


Casting a vector to a different vector type does not work when type depends on generic

struct SomeStruct<Real : __BuiltinFloatingPointType> {
    vector<Real, 3> color;
    __init() {
        vector<float, 3> _color = vector<float, 3>(0);
        color = _color; // error 30019: expected an expression of type 'vector<Real,3>', got 'vector<float,3>'
        color = vector<Real, 3>(_color); // also does not work
    }
}

It is not possible to cast the whole vector of type float or double to Real which must be float or double. Same for int types.
Workaround:
color = vector<Real, 3>(Real(_color.x), Real(_color.y), Real(_color.z));

Adding to Q4 milestone by default, as there is currently a workaround.


Transformer examples uses incorrect function definition

/kind bug
Example use List   def postprocess(self, inputs: List) -> List:
https://github.com/kserve/kserve/blob/efda8c6f062e41368cb2eba3986e8cf9a7ba7dfc/docs/samples/v1beta1/transformer/torchserve_image_transformer/image_transformer/image_transformer.py#L87
While base uses Dict   def postprocess(self, response: Union[Dict, ModelInferResponse]) -> Dict:
https://github.com/kserve/kserve/blob/efda8c6f062e41368cb2eba3986e8cf9a7ba7dfc/python/kserve/kserve/model.py#L166

@smhgit Thanks for catching this! Are you interested to contribute the fix?

@yuzisun sure, will take a look how to make contribution here.

Fixed in #2266


Create a document to explain web platform async timing entry-points

As discussed at Melbourne F2F, there are a lot of ways in the platform to schedule stuff, and lots of APIs that do it.
We would like to create a document that collates all of these timing entry-points, describes where the timings should happen in relation to other implementation details (layout, painting), and applies fixes for known issues (as noted by @dbaron) with HTML5 task queue description.

https://lists.w3.org/Archives/Public/public-houdini/2015Oct/0017.html was the discussion we had in Paris at the Houdini meeting in august, which covers mostly improvements to the rendering part.
This is related to, but somewhat distinct, from the idea of having all of these different task queues (setTimeout, microtask, nanotask, setImmediate, setIdleCallback, etc.) and perhaps the need for a better developer-facing way to prioritize tasks.

I'm a little unclear on the scope here. Maybe the minutes would make it clearer?

describes where the timings should happen in relation to other implementation details (layout, painting), and applies fixes for known issues (as noted by @dbaron) with HTML5 task queue description.

This sounds like it would be best done not as a separate document but as a pull request to modify https://html.spec.whatwg.org/#processing-model-8.

We would like to create a document that collates all of these timing entry-points

This might be a worthwhile guidance document explaining when and how specs should use HTML's algorithms to perform their work.

perhaps the need for a better developer-facing way to prioritize tasks.

There are actually some discussions on this happening right now between myself and the Angular team. We hope to send a proposal as an issue on whatwg/html shortly (next few days probably). Stay tuned!

This sounds like it would be best done not as a separate document but as a pull request to modify https://html.spec.whatwg.org/#processing-model-8.

Yeah, I agree this probably doesn't belong in a TAG document, although the plan in the Houdini group was to write a separate rendering pipeline document, and presumably then make a pull request to change a few of the list items in the HTML spec's event loop description to refer to an entirely separate (and probably substantially larger) spec.

although the plan in the Houdini group was to write a separate rendering pipeline document, and presumably then make a pull request to change a few of the list items in the HTML spec's event loop description to refer to an entirely separate (and probably substantially larger) spec.

That makes a lot of sense to me; I agree that HTML's "update the rendering" (step 7) would largely best be handled by the CSSWG.

Dupe of issue #72


Selector::areDependenciesFromComposer does not match all composer dependencies

Expected behavior
All classes defined/autoloaded from packages defined in composer->require section should be matched by the selector.
Actual behavior
It does work mostly, but not for all cases. For example packages from like tracy/tracy or nette/* are not loaded and currently I have to add classesThat(Selector::haveClassName('Nette\*')) to work aroud it.

Hello. This happens because tracy (and I guess the rest of nette packages) do not define a base namespace https://github.com/nette/tracy/blob/master/composer.json#L34
The current composer parser is checking the declared autoload namespaces to search the parsed code against them. This is something that should be considered and coded in the parsed, or maybe delegate the composer parsing to some already extinting library.
I will close this issue as is an known missing feature but will keep in mind and try to include it in the composer parsing.


Improve documentation

I sat down the last two days to read the new documentation and thought I could contribute while learning. The new website and docs really are a great improvement over the old one.
I tried to focus on improving clarity, fixing typos and correcting grammar mistakes while trying to avoid rewriting the author's original meaning and intent. Although I read the entire documentation, I may have missed a few things. I also tried to maintain the contribution style according to previous commit messages.
I'd be happy to make any changes / squashes if necessary. Hopefully this can be of use!

wow, thanks!


Example doesn't provide info on the WRITE to Cosmos DB

Example notebook doesn't provide info on the WRITE to Cosmos DB (only READ).

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

ID: 7197a1f8-bc64-1ac0-bf54-4a76381acc87
Version Independent ID: 3c5a8e1d-bb1e-0bcc-571a-7cee8edad2ba
Content: Azure Cosmos DB - Azure Databricks
Content Source: databricks/data/data-sources/azure/cosmosdb-connector.md
Service: azure-databricks
GitHub Login: @mssaperla
Microsoft Alias: saperla

@michalmar
Thanks for your feedback! We will investigate and update as appropriate.

@michalmar
Thanks for your feedback! I've assigned this issue to the author who will investigate and update as appropriate.

Thanks for your dedication to our documentation. Unfortunately, we have been unable to review your issue and apologize for the delayed response. The requested updates have not yet been made. The timeline for resolution varies based on resourcing. We've created an internal work item (DOC-7183) to incorporate your suggestions. We are closing this issue for now, but feel free to comment here as necessary.
#please-close

#please-close


Suggestion: Add IGDB endpoints

Twitch switched their game lookup from Giant Bomb to IGDB (which they bought a while ago).
See https://twitter.com/TwitchSupport/status/1310625492274470912
With that switch, IGDB's API now uses Twitch' OAuth2 Tokens (https://medium.com/igdb/igdb-api-v4-is-coming-6ba97874edbc).
I think, it would be nice, if IGDB (which is now technically part of Twitch) could be integrated into this package.
Generating and handling Bearer Tokens for the same authentication system twice, seems a like a big overhead.
Additionally, by integrating the IGDB API, more information regarding the games, returned by Twitch's API, can be obtained without handling another authentication system.

For me IGDB is a completely decoupled product that has a completely different namespace. The only thing they share is the oauth server.
Also a quote from d-fischer / SatisfiedPear from Twitch API Discord:

Same stance as on my own package: IGDB should be a separate package, it could maybe depend on the auth portion of the Twitch code but it has nothing else in common, really

Still, Twitch's game library is now powered by IGDB.
To be able to request additional data from the same data source using another package and another token handling seems a bit weird.
It doesn't have to be directly in this package, but a possibility to request metadata is required.

The only thing they share is the oauth server.
Nope, if you look at https://medium.com/igdb/we-are-joining-twitch-54cfdf44c496 they moved them to the same infrastructure. It's all Twitch. (see "By joining Twitch, we will be able to tap into their experience, resources," or "clean up some features and migrate infrastructure in order to make room for new and improved tools.")

Twitch changes the API and moves it to the same infrastructure, to make it more accessible for Twitch-related developers.
So there is no reason to not allow PHP developers, who want to build something Twitch-related, to use one system for all Twitch APIs instead of a dozen (one for every namespace).
At least, the app access token should be made available to outside packages, to be able to use the same token and not requiring to request another one.


Chore/handle multiple txs

Checklist

[ ] JIRA - <link>
[ ] Proper tests implemented
[ ] Screenshots added.

Proposed solution
Explain how does this PR solves the problem stated in JIRA ticket.
You can also enumerate different alternatives considered while approaching this task.
Testing
Describe here, how the new implementation can be tested.
Provide link or briefly describe User Acceptance Criteria/Tests that need to be met
Screenshots

@vetalcore @mchappell - this PR is over 2 weeks old.

What Jira ticket does it relate to?
How can we get this merged or cancelled?

@vetalcore @mchappell - this PR is over 2 weeks old.

What Jira ticket does it relate to?
How can we get this merged or cancelled?

JON P

This relates to being able to visualise multiple transactions that may appear in lace. This might be superseded by the work already being done in tx representation, will sync on this tomorrow and either resolve + merge, or cancel

closing this one due to the lack of activity


Nextification

I'm switching nteract.io over to Next.js so that I'm more likely to contribute to it while also being able to use our other components.
This is a work in progress as I adapt this. I'm going to hand jam in the built CSS (it's SCSS right now) and then remove that commit later.
Current progress, I've only done the header and footer so far:

Alllllmost there...

@rgbkrk you should test out styled-components some time ;) It's really enjoyable

Everybody keeps talking about them. ;) I'll be happy to switch over after we migrate the original base. Want to take over this PR and finish it off?

@rgbkrk Not sure whether I'll have time :) I'm actually working on some styled-components contributions myself, besides my other OSS projects ^^

Fair enough, I'll keep on going here.

Ok, what was missing here was the jQuery code that's run on start. I'd like to see about doing this without jQuery given that we're using React.
$(document).ready(function () {

  function checkHeaderLocation() {
    var top_of_object = $('.page--body').offset().top - 72;
    var top_of_window = $(window).scrollTop();

    return top_of_object < top_of_window;
  }

  function fadeHeaderIn() {
    $(".header--main").addClass("logo-dark");
  }

  function fadeHeaderOut() {
    $(".header--main").removeClass("logo-dark");
  }

  function isContentVisible(element) {
    var bottom_of_object = element.offset().top + element.outerHeight() - 400;
    var bottom_of_window = $(window).scrollTop() + $(window).height();

    return bottom_of_window > bottom_of_object;
  }

  $(window).scroll(function () {

    if (checkHeaderLocation()) {
      fadeHeaderIn();
    } else {
      fadeHeaderOut();
    }

    $('.hidden').each(function (i) {
      if (isContentVisible($(this))) {
        $(this).addClass("animate-content");
      }
    });

  });

  // Init
  setTimeout(function() {
    if (checkHeaderLocation()) {
      fadeHeaderIn();
    } else {
      fadeHeaderOut();
    }

    $('.hidden').each(function (i) {
      if (isContentVisible($(this))) {
        $(this).addClass("animate-content");
      }
    });
  }, 750);

  // Hero
  var scene = $('.hero--scene');
  scene.parallax({
    invertX: false,
    limitY: 0
  });

});

This now is roughly like the current site. To make the transition to next.js work out well though, I'll have to create a build for the gh-pages branch.

If you are looking to move toward styled-components, I can help with that effort.

Folks working in nteract/commuter and nteract/nteract are aiming to go with Aphrodite, that's not holding this PR up though.

:+1: on Aphrodite. I tried it on a project recently and it was fantastic.

Yeah, Aphrodite isn't a bad library. It does have some limitations in that you can't use Aphrodite to write any global CSS; it doesn't support the entire CSS spec, lacking specifically sibling and descendant selectors; and it can be tedious to convert existing CSS (as opposed to starting from scratch) since Aphrodite's CSS is written as a JS object. Within those boundaries, it is a solid CSS-in-JS solution.

Ended up bringing the real next.js setup into our nteract.io app here: https://github.com/nteract/nteract.io/pull/1
Going ahead and closing this for now.


💦 DevTools monitor gone with webpack 2

This is probably a rubber duckie session, but bear with me

After switching to<EMAIL_ADDRESS>I found that the DevTools (dock) has gone AWOL. I cannot figure how this has happened. I'm on the end of the workday and stuck in a rut here.
"webpack": "2.2.0",
"redux-devtools": "^3.3.2",
"redux-devtools-dock-monitor": "^1.1.1",
"redux-devtools-log-monitor": "^1.2.0",

// inside <Provider><Oidcprovider> in Root.jsx (routes)
{process.env.NODE_ENV !== 'production' ? require('./DevTools').default : null}

// configurestore.dev.js
const store = compose(
  applyMiddleware(thunkMiddleware, oidcMiddleware),
  DevTools.instrument()
)(createStore)(rootReducer, initialState);

// DevTools.jsx
import React from 'react';
import { createDevTools } from 'redux-devtools';
import LogMonitor from 'redux-devtools-log-monitor';
import DockMonitor from 'redux-devtools-dock-monitor';

export default createDevTools(
  <DockMonitor
    defaultIsVisible={false}
    toggleVisibilityKey='ctrl-d'
    changePositionKey='ctrl-q'>
    <LogMonitor />
  </DockMonitor>
);

What could possibly have happened?

As I see, it's not visible by default, you should press ctrl+d to show it. Try changing defaultIsVisible to false. Also make sure to render the component imported from './DevTools'.

@zalmoxisus sorry, I must have given you the impression that I haven't used this before. It's always worked before, and I can't figure out what has happened with it. And as you see from the code supplied, I do render it.

After doing some digging, it seems to me that, for now, the culprit of this issue is Webpack 2. I've manually retraced steps in the commits for now, checking out every commit until I got it to work. Will update when I know more

I see that I never hit DevTools.prototype.render , but I hit function createDevTools(children) {, investigating further

Yeah, found the culprit. Me. In the haze of using webpack@2* I forgot the basics of module importing it seems. Working with this in DevTools.jsx makes it work like a charm.
As stated in the issue, this was a rubber duckie session :duck: :duck:  :weary:
import React from 'react';

let devtools = null;

if(process.env.NODE_ENV !== 'production'){

  const reduxDevTools = require('redux-devtools');
  const LogMonitor = require('redux-devtools-log-monitor').default;
  const DockMonitor = require('redux-devtools-dock-monitor').default;

  devtools =  reduxDevTools.createDevTools(
    <DockMonitor
      defaultIsVisible={false}
      toggleVisibilityKey='ctrl-d'
      changePositionKey='ctrl-q'>
      <LogMonitor />
    </DockMonitor>
  );

}

export default devtools;


adding pagination in homepage feed

Is your feature request related to a problem? Please describe.
This feature is not related to any problem
Describe
I Guess the API endpoint in the backend for fetching mumbles api/mumbles has pagination implemented, If so I think we can start implementing pagination on the frontend.
Additional context
I would like to implement this, so I ask @MidouWebDev  or @codyseibert to assign it to me.

sounds good, I think we do pagination on a couple of other pages, so maybe follow the same approach unless you can think of a better solution.

@mani-barathi
I added it to the project board :wink:

@MidouWebDev do update the project board. I'm closing this issue.

I guess it is automated
@mani-barathi


feat: add rust prism highlight code block

For some reason my PR look dirty. 🤔 It should be only feat: add rust prism highlight code block but it somehow contain the details from previously merged. Maybe I should create new branch before PR next time.

I will cherry-pick your commit when I get back to my computer

Cherrypicked: https://github.com/sobelio/llm-chain/commit/f02bb98d95715825ed5899bd4644c027b19ec579
Thanks for that :)


Detect EOF in regular expressions

It would be nice if the \W anchor was supported in #[regex] strings such that certain regular expressions could succeed if EOF is encountered early. For example:
#[derive(Logos)]
enum Token {
    #[end]
    End,
    #[error]
    Error,
    #[regex = r"/\*([^*]|\*+[^*/]|[^\W])*(\*+/|\W)"]
    BlockComment,
}

The regex shown above would be able to match both /* hello */ and also /* hello, where the second one is immediately followed by an #[end]. This would allow for the lexer to process the token successfully even if the input terminates early before the */ could be received, and we could check whether the comment is properly terminated by calling lexer.slice().ends_with("*/") at a later stage.
See TokenKind::BlockComment { terminated: bool } in rustc_lexer for an example of this common lexing pattern.

Might still add this to regex itself, but you will be able to handle this with callbacks next release, reference: #103.

Closing this a too old, feel free to re-open if needed.


fix(codemod): comment tmpdir for package managers

Description

When using Yarn 4, the default is to use a local version to your repository. Codemod runs package managers from a tmp directory, which causes Yarn to think there's no local version and uses global version instead. This is fixed when removing the line to run from tmp dir, but needs to be tested if it works with other package managers/projects.
https://github.com/vercel/turborepo/pull/8076
Testing Instructions

Closing this one because I asked for it in conversation during 8076. I'm fairly confident we're on the right track now and we can toss this.
Really appreciate your help on the way to sorting this out. Thank you!


I'm a beginner and don't know how to use it

Your plug-in is very good. I am a beginner and don’t know how to use it. Can you provide some cases so that I can quickly understand it? Thank you very much.

Hi @hl0709 , this project is old and not maintained.

Thank you very much for your reply. I really need a fabricjs editor plug-in that can be expanded independently. For me, a beginner, this plugin of yours is suitable for me. I am a college student who has just graduated. I just love programming, but I still don’t know how to use your fabricjs plug-in. If you have time, can you give me a brief introduction to how to use it? I've compiled it!


Tiling algorithm

Web map tiling algorithms efficiently represent high resolution data by displaying a subset of the data at a particular resolution. The subtleties in the algorithm concern issues such as throttling, caching and managing tiles.

[ ] Improve cache performance
[ ] Throttle or debounce the render() cycle or send actions to the store
[ ] Only display tiles related to the current zoom level

The above aspects are tangentially related to the DataTileRenderer itself and should not depend on whether PNG file(s) or JSON tiles are being displayed

De-coupling the DataTileRenderer from orchestration of tiles might be a better design

#35, #42 and #43 close this issue


InfluxDB query won't return container name

When I am trying to get the names of those containers that have been updated by ouroboros from InfluxDB the query will stay empty:
> SELECT "container" FROM "Ouroboros" WHERE type = 'container_update'
>

However, when I will SELECT everything, it will show me the container names:
> SELECT * FROM "Ouroboros" WHERE type = 'container_update'
name: Ouroboros
time                           configuration container          count data_export docker_sockets docker_tls_verify hostname ignore influx_database influx_password influx_port inf lux_url influx_username interval log_level monitored_containers self_update socket              type             updated_count
----                           ------------- ---------          ----- ----------- -------------- ----------------- -------- ------ --------------- --------------- ----------- --- ------- --------------- -------- --------- -------------------- ----------- ------              ----             -------------
2019-03-23T20:30:38.110991872Z               proj_image_1       1                                                                                var/run/docker.sock container_update
>

Also, I guess this is why in Grafana cannot create a table with the times and containers to be shown, "containers" can only be selected after the WHERE statement, not by the SELECT.
Am I missing something from InfluxDB or a bug?

You cannot select a TAG. The container name is a tag not a field. Example of query that works is:
SELECT count("count") FROM "Ouroboros" GROUP BY "container"


mx-bluesky unit tests taking ~3x longer since signal-typing changes

Since updating mx-bluesky to be compatible with #594, the unit tests are taking significantly longer to complete.
On my desktop machine the difference is ~97s to complete compared to ~27s before
It seems that most of this slowdown is due to waiting in call_in_bluesky_event_loop() waiting for wait_for_connection(coros=device.connect(mock=True)) to complete.
Can this be made faster?

Can you post a typical test please?

See https://github.com/DiamondLightSource/mx-bluesky/blob/3845a51a2f083c578b92476702950f4125813b4b/tests/unit_tests/beamlines/i04/test_thawing.py#L118 for a typical test
In our tests, devices are created through fixtures which look like
smargon = i03.smargon(fake_with_ophyd_sim=True)
which in turn calls
call_in_bluesky_event_loop(...) and the ophyd-async wait_for_connection(..)

I'm happy this is fixed by https://github.com/bluesky/ophyd-async/pull/641


Uncaught TypeError on making an image out of iframe which contains a canvas.

Hi,
I am trying to create a canvas out of iframe which contains canvas which contains images and objects (3d obj models) which are being downloaded from s3.
Most of the times it is able to render everything properly but sometimes it is not able to load all the objs and throws this error:
Uncaught TypeError: Failed to execute 'shaderSource' on 'WebGLRenderingContext': parameter 1 is not of type 'WebGLShader'.
Is there any way to handle this error so that it does not keep on looping in the console?
If I could catch it or fix it, it would be a huge help.
here is how I am generating the image:
I generate the image with this code.
html2canvas(document.getElementById('result-iframe').contentDocument.childNodes[0].childNodes[1], {
				  onrendered: function(canvas) {
					canvas.style.width='112px';
					canvas.style.height='112px';
					document.getElementById('project-thumb').appendChild(canvas);
					document.getElementById('pushProjectButton').removeAttribute('disabled');
				  },
					letterRendering:false,
					taintTest:false
				});

```I tried using promise and catching the error but no luck:

try{
				html2canvas(document.getElementById('result-iframe').contentDocument.childNodes[0].childNodes[1]
				).then(function(canvas,err){
					try{
						canvas.style.width='112px';
						canvas.style.height='112px';
						document.getElementById('project-thumb').appendChild(canvas);
						document.getElementById('pushProjectButton').removeAttribute('disabled');
					}
					catch(e){console.log('caught nested error');}
				});
				}
				catch(e){console.log('error caught!');}

b/w document.getElementById('result-iframe').contentDocument.childNodes[0].childNodes[1] is the canvas inside the iframe.
thanks...

Which version of html2canvas are you testing with? Could you replicate the error on jsfiddle as it is quite difficult to try and figure out what the problem is from what you shared?

I am using 0.5.0-beta4.
I am trying to take a picture of scene (which is in canvas) in aframe (https://aframe.io) if you go to this link you can find a canvas inside an Iframe.
I won't be able to reproduce it but from above link, I think you can make out the issue.
Let me know I can do anything else to make it more clear
also is there any way to catch it so then for now I can atleast stop it looping all over the console.
-Thanks


What equipment does the author use for training？Time consuming

Same issue as https://github.com/ethnhe/PVN3D/issues/10

好的，谢谢回答


Expose stringFT

This PR:

exposes gdImageStringFT to render text on images via SwiftGD
fixes a couple of typos that I've spotted in the codebase

Thank you for this great library!

Hello! Thank you for the wonderful contribution – this looks like a really valuable feature to have 👍
I wonder if we could perhaps look at the API a little more closely? I realize you've just exposed the internal GD function, but I think we could Swiftify it a little and make the exposed API a little nicer for developers 😀
Let's take a look at the components we have right now:

func stringFT – could this perhaps be addText(), renderText(), or similar?
from: looks fine to me.
boundingRect: – what is this?
fontList – could this perhaps be an array of strings rather than a semi-colon-delimited strings? We can join it with semi-colons inside the function, but I wouldn't want to expose that outside the API.
color: Great!
pointSize: Are there plans to support other kind of sizing, or can this just be size?
angle: We haven't used angles before in SwiftGD, but I can see this kind of thing being useful. Do you think perhaps adopting a SwiftUI-like Angle type would be good? That way we can let folks specify as radians or degrees. Also, is this measured from the positive X axis?
string: Depending on the final function name, this might end up being the first parameter. e.g., add(text: "Whatever"), or renderText("Whatever"). I think the second option seems to fit in with the rest of the existing SwiftGD API, I think, but I'd love to hear your suggestions here.
- Returns: I'm not sure that an array of points is the most ergonomical approach here. Could we perhaps send back a tuple of points, or perhaps a Rectangle? It would be a lot safer.

Thank you for the suggestions/feedback!

boundingRect: – what is this?

Old documentation leftover. Nicely spotted! Removed, thank you!

fontList – could this perhaps be an array of strings rather than a semi-colon-delimited strings? We can join it with semi-colons inside the function, but I wouldn't want to expose that outside the API.

Done 👍🏻

pointSize: Are there plans to support other kind of sizing, or can this just be size?

Renamed to size 👍🏻

angle: We haven't used angles before in SwiftGD, but I can see this kind of thing being useful. Do you think perhaps adopting a SwiftUI-like Angle type would be good? That way we can let folks specify as radians or degrees.

That was my thought, too. I didn't add an Angle type because I was not sure you'd be ok with adding a new type just for this API.
Angle type added! 👍🏻
Geometry.swift file is getting a little crowded:
if it's ok by you, I'd be happy to create a Geometry subfolder and split all geometry types to a new file for each (this can be another PR).

Also, is this measured from the positive X axis?

Yes, I've updated the documentation with: The angle to rotate the rendered text from the basepoint perspective. Positive angles rotate counter-clockwise..
I welcome suggestions on how to improve this.

string: Depending on the final function name, this might end up being the first parameter. e.g., add(text: "Whatever"), or renderText("Whatever"). I think the second option seems to fit in with the rest of the existing SwiftGD API, I think, but I'd love to hear your suggestions here.

Agreed!

parameter moved to be the first
renamed the function to renderText

Much more Swifty :)

- Returns: I'm not sure that an array of points is the most ergonomical approach here. Could we perhaps send back a tuple of points, or perhaps a Rectangle? It would be a lot safer.

Updated to return a tuple 👍🏻
We need to return each point separately, as they represent the four "corners" of the rendered text at any angle.
For example, if we render text at 45 degrees, we might get something like this (imagine the text within the rectangle/square):
     c
    /\
  /   \
d/     \ b
  \    /
   \ /
    a

Where the returned tuple would be the (a, b, c, d) points.

This is a huge improvement – thank you! I agree with the Geometry.swift split 👍
At this point only two things have me doubtful:

Rotating counter-clockwise rather than clockwise. The rotation direction might be normal for GD, but it's the opposite of Apple's frameworks e.g. SwiftUI. Given that our developers are more likely to come from Apple than from PHP/GD, I think we should flip the direction.
Tuple order in the return. Again, this is the way GD does it, but it reads odd to me. I guess everyone is different, though! If I asked you to draw a square, would you start at the bottom left? I think I'd start at the top left, then go TR, BR, BL. Or if I were drawing just dots like we have here, I think I'd go TL, TR, BL, BR. This only affects people who use access the tuple using .0, .1, etc, but I think it's still worth looking at before we plant a new release tag.

Anyway, both of those are minor and can be figured out later, so I'm going to merge this now – great work! 🙌

Oh! Sorry, there was one more thing: working with fonts is always something I worry about when rendering text using GD 😅

What happens if fontList is empty?
Is there a sensible default parameter can provide here to avoid people wondering "what font can I use?"?
What happens if the user specifies an nonexistent font?

PR #30 splits the Geometry files
PR #31 addresses the concerns in https://github.com/twostraws/SwiftGD/pull/29#issuecomment-899032723

What happens if fontList is empty?

No text is drawn and the returned renderText bounding box is all zeroes.

Is there a sensible default parameter can provide here to avoid people wondering "what font can I use?"?

This is one of the reasons why I added the example in the documentation.
I'm not aware of a font that would work across platforms:
even if there was one, I'm not sure that we could guarantee that it will work for future releases (note: I might be very wrong on this 😅).

What happens if the user specifies an nonexistent font?

GD will use the first match in the list it can find:
if all fonts specified are "misses" (a.k.a. GD cannot find any of them), it's the same as if the fontList was empty and no text will be drawn.
I'm happy to expand the fontList documentation mentioning this if it's ok with you.
Currently, it says:
fontList: A list of font filenames to look for. The first match will be used.

Thank you and please let me know 😊


Android white screen after exiting using physical back button

Describe the bug
After opening an app, I click the back button on my Android phone to exit, and when I click the app icon on my phone again to enter, the screen turns completely white and I can’t see anything.
I'm using android 9 api 28, this problem occurs when using 11.1.0-beta2 and 11.2.999-cibuild0048108-alpha, 11.1.0-beta1 has no problem
To Reproduce

Open an app.
Click the Android physical back button to exit the app.
Click on the app icon to open it again.

Expected behavior
It will display normally when you open the app again.
Avalonia version
11.1.0-beta2
OS
Android
Additional context
No response

@yumikou you can use src/Samples/MobileSandbox to see if you find the code that does produce this behavior.

@yumikou you can use src/Samples/MobileSandbox to see if you find the code that does produce this behavior.

Thank you for your reply. I tested the SafeAreaDemo.Android in the example and still have the same problem and I don't see any exception logs. I am not familiar with the source code of avalonia yet, It is a bit difficult for me to locate the problem code, so I am reading slowly now, but may not be able to find it.

I was hoping you see an obvious error message or smth. So yeah I don't expect you to scan all source code. Thanks for your time anyways 👍

@afunc233 thanks for your help ❤


Include the registration client in all images to support BYOS instance

using the update infrastructure

@jgleissner this has no effect on config.sh generation correct? For BYOS we do not want to enable the regionsrv client service by default.

The guestregister service gets enabled by data/base/cloudreg/sle?/config.yaml. Since we're getting rid of data/base/cloudreq, those configs would need to be replicated in data/csp/*/ondemand/sle?.

Now that we have to make modifications I am wondering about the separation by convention. But that is for another time. So here is my next attempt.


feat: default Vega-Lite-based renderer (#342)

Goals

Create a default renderer based on Vega-Lite

Used Altair to get automatic VL schema validation
The renderer returns an alt.VConcatChart | alt.HConcatChart | alt.FacetChart | alt.Chart, ready to be displayed, exported, customized, etc.

Define the schema of the Draco specification language using Pydantic

Using raw dicts one has to fight a lot with the type checkers
Having typed access to the schema makes its traversal and processing more readable

closes #342

Vega-Lite vs. Draco spec
Below I list my takeaways in a nutshell from implementing all the example charts from the docs (https://dig.cmu.edu/draco2/facts/examples.html)  in Vega-Lite using Altair.

VL mostly covers all our rendering needs, in most cases the mapping from our schema to the VL schema is straightforward ✓
VL has no explicit support for toggling between cartesian and polar coordinate systems

However, we can use an arc mark & the encodings theta, radius to overcome this ✓

As far as I can tell, VL does not allow for nested faceting / repeating / concatenation. This is problematic since Draco can produce multi-view recommendations and each view might or might not be faceted 🚫

Questions regarding Draco's spec

What do we consider as a strictly valid spec? Defining this would be important so that the renderer method can validate the input before trying to convert it into VL. For example, the following spec (Pie Chart Example) does not define a field for its encoding on the y channel:

{'field': [{'name': 'temperature', 'type': 'number'},
           {'name': 'condition', 'type': 'string'}],
 'number_rows': 100,
 'view': [{'coordinates': 'polar',
           'mark': [{'encoding': [{'aggregate': 'count',
                                   'channel': 'y',
                                   'stack': 'zero'},
                                  {'channel': 'color', 'field': 'condition'}],
                     'type': 'bar'}],
           'scale': [{'channel': 'y', 'type': 'linear', 'zero': 'true'},
                     {'channel': 'color', 'type': 'categorical'}]}]}

While it is easy to infer that the temperature field should be used here, is the renderer expected to handle this inferring?

What do you think, would it make sense to define a Draco spec strictly? We could use Pydantic for this & the implementation would mean relatively little effort. It has an awesome DX when it comes to defining schemas (see https://pydantic-docs.helpmanual.io/usage/schema/) and we already depend on the package.

@JunranY, @Zehua-Zeng, @domoritz

do you know a workaround to concatenate faceted views in VL?
what do you think about introducing a Pydantic-based schema validation?
in general, what kind of development roadmap would you prefer for this feature? Should we...

merge an MVP as soon as possible that is capable of rendering simpler recs (basically any non-multi-view rec in a cartesian polar system) and work on further refinements iteratively, or
create a more elaborate issue from this handling all specs & create a rendering base-class to support multiple renderer implementations?

Hey @domoritz! While the code I pushed is indeed not really LGTM (as it is partial work full of quick & dirty experimenting), I believe the LGTM.com report is not right:

kw_only is a totally valid parameter name since Python 3.10. Is it possible that the Python version based on which LGTM.com checks our code is not in sync with the version we actually use? I did not update it in 06144c472ad2daf036263f64f0ec158a30711416, as I have no access to the job's config as far as I know.

Update
Writing tests for the renderer are still in progress. All charts defined with a cartesian coordinate system are supported by the renderer. It produces a syntactically valid VL spec for each of the example charts. It is possible that the VL output still needs to be fined-tuned semantically.
A review round on the implemented approach would be much appreciated to find out in what other ways should the renderer be further-developed.

Still Open

Handling decision between vconcat and hconcat (vconcat is used by default at the moment)
Handling charts in polar coordinate-system

@domoritz could you please take a look at this PR?

The failing workflows might be related to actions/setup-python#162.

@domoritz, I added the discussed changes in bd7ca3b


Could you support shadow border?

I just saw the related issue: https://github.com/folke/noice.nvim/issues/266
Unfortunately, shadow border can't support text (since it doesn't really have any border to put the text on).
Closing the issue.

Well, I think maybe I don't get what you meant by:

[...] shadow border can't support text (since it doesn't really have any border to put the text on).

Then why which-key can do this:

Border text is different. It's when you have text on the border, for example:

^ "[Rename]" on this screenshot.

@MunifTanjim Thanks for your kindness, you just made better explanation than the author :) Then where should I put the style to achieve the same effect as the image I post?

noice.nvim is probably setting the border.text internally. So it's getting merged with your config and ends up being: { border = { style = "shadow", text = { --[[ something set by noice ]] } } }, which is not supported.
I don't know about the noice.nvim internals, so you'll need to discuss it on that project.

@MunifTanjim I did, but he hasn't replied. No worries, I think he's busy with something more important. Again thanks for your detailed reply :)

Well, you created issues on both repo with absolutely no description. That was a bad way of submitting issues.
Issues should be created with proper description - details about what you tried, what you're expecting and what's happening. Provide as much information as you can. Otherwise plugin maintainers can't just guess the problem you're facing.
I hope it helps when you face any problems in future.

You're right. I have no excuse then.


How to implement dictionary learning using keras

Hii, experts. I am looking for the implementation of dictionary learning using Keras. Are there any API for the same.Please suggest.

https://github.com/tensorflow/tensorflow/issues/34114#issuecomment-588574494


ARROW-7028: [R] Date roundtrip results in different R storage mode

Although it's to some extent tolerated that Date vectors are backed by integer vectors, it's much more common that they are backed by numeric:
.Internal(inspect(Sys.Date()))
#> @7fb95b8178c0 14 REALSXP g0c1 [OBJ,ATT] (len=1, tl=0) 18425
#> ATTRIB:
#>   @7fb9586b1808 02 LISTSXP g0c0 [REF(1)]
#>     TAG: @7fb957004fd0 01 SYMSXP g0c0 [MARK,REF(25905),LCK,gp=0x6000] "class" (has value)
#>     @7fb95b817888 16 STRSXP g0c1 [REF(1)] (len=1, tl=0)
#>       @7fb9571c1530 09 CHARSXP g0c1 [MARK,REF(191),gp=0x61] [ASCII] [cached] "Date"
.Internal(inspect(as.Date("1982-05-15")))
#> @7fb95c10eb58 14 REALSXP g0c1 [OBJ,ATT] (len=1, tl=0) 4517
#> ATTRIB:
#>   @7fb9587cbc48 02 LISTSXP g0c0 [REF(1)]
#>     TAG: @7fb957004fd0 01 SYMSXP g0c0 [MARK,REF(25948),LCK,gp=0x6000] "class" (has value)
#>     @7fb95c10eb20 16 STRSXP g0c1 [REF(1)] (len=1, tl=0)
#>       @7fb9571c1530 09 CHARSXP g0c1 [MARK,REF(192),gp=0x61] [ASCII] [cached] "Date"

Created on 2020-06-12 by the reprex package (v0.3.0)
So I've changed Converter_Date32 to convert to a numeric vector:
library(dplyr, warn.conflicts = FALSE)

tmp = tempdir()
dat = tibble(tag = as.Date("2018-01-01"))
dat2 = tibble(tag2 = as.Date("2019-01-01"))

arrow::write_parquet(dat, file.path(tmp, "dat.parquet"))
dat = arrow::read_parquet(file.path(tmp, "dat.parquet"))

typeof(dat$tag)
#> [1] "double"
typeof(dat2$tag2)
#> [1] "double"

bind_cols(dat, dat2) %>%
  mutate(comparison = if_else(TRUE, tag, tag2))
#> # A tibble: 1 x 3
#>   tag        tag2       comparison
#>   <date>     <date>     <date>
#> 1 2018-01-01 2019-01-01 2018-01-01

Created on 2020-06-12 by the reprex package (v0.3.0)
Note: dplyr::if_else is due a rewrite, probably in funs:: that will be more vctrs-correct and perhaps would deal with the issue:
library(dplyr, warn.conflicts = FALSE)

today_dbl <- Sys.Date()
today_int <- structure(as.integer(today_dbl), class = "Date")

dplyr::if_else(TRUE, today_dbl, today_int)
#> Error: `false` must be a `Date` object, not a `Date` object.

Created on 2020-06-12 by the reprex package (v0.3.0)
This might be a usecase for vctrs::vec_cast_common(). ping @lionel- @DavisVaughan:
library(dplyr, warn.conflicts = FALSE)

today_dbl <- Sys.Date()
today_int <- structure(as.integer(today_dbl), class = "Date")
.Internal(inspect(
  vctrs::vec_cast_common(today_dbl, today_int)
))
#> @7ffe825f1688 19 VECSXP g0c2 [] (len=2, tl=0)
#>   @7ffe823aeaa0 14 REALSXP g0c1 [OBJ,REF(12),ATT] (len=1, tl=0) 18425
#>   ATTRIB:
#>     @7ffe823b5408 02 LISTSXP g0c0 [REF(1)]
#>       TAG: @7ffe80804fd0 01 SYMSXP g1c0 [MARK,REF(33031),LCK,gp=0x6000] "class" (has value)
#>       @7ffe823aea68 16 STRSXP g0c1 [REF(65535)] (len=1, tl=0)
#>  @7ffe809c1530 09 CHARSXP g1c1 [MARK,REF(395),gp=0x61] [ASCII] [cached] "Date"
#>   @7ffe8265eb30 14 REALSXP g0c1 [OBJ,REF(1),ATT] (len=1, tl=0) 18425
#>   ATTRIB:
#>     @7ffe82664938 02 LISTSXP g0c0 [REF(1)]
#>       TAG: @7ffe80804fd0 01 SYMSXP g1c0 [MARK,REF(33031),LCK,gp=0x6000] "class" (has value)
#>       @7ffe82d15d60 16 STRSXP g1c1 [MARK,REF(65535)] (len=1, tl=0)
#>  @7ffe809c1530 09 CHARSXP g1c1 [MARK,REF(395),gp=0x61] [ASCII] [cached] "Date"

Created on 2020-06-12 by the reprex package (v0.3.0)

@romainfrancois funs::if_else() is one of the few functions that is already implemented in funs and it does handle this correctly. vec_cast() and vec_ptype2() always push towards numeric Dates, no matter what the input is. I would imagine the same should happen here.
I would say the round trip options are:
Date<int> -> arrow -> Date<dbl>
Date<dbl> -> arrow -> Date<dbl>

Thanks, I had not checked funs::if_else().
Yeah, a Date32 arrow gets converted to a Date<dbl> no matter what, that means data copy as arrow backs it with a int vector internally but Date<int> is a weird thing in R.

Thanks y'all for looking into this. Given where we are right now, this PR is probably an improvement on the status quo. If we had benchmarks that the conversion to Date had a big penalty, that would be different, but we don't. But I have to ask: if funs::if_else() handles this situation correctly (which I read to mean doesn't error when mixing integer vs. numeric Dates, but maybe I misunderstand what "correctly" means), why make the change here?
Longer discussion: Since the R and Arrow data types aren't exactly the same, there's tension between different objectives of the arrow package here:

Efficiency and fidelity of moving data from/to Arrow memory, zero-copy where possible (which IIUC would point to using integer)
Usability in R and fidelity of R data round trip (which would point to using numeric)

We have a few related issues open currently:

https://jira.apache.org/jira/browse/ARROW-9083 (int64)
https://jira.apache.org/jira/browse/ARROW-7798 (related, discussion of R <--> Arrow conversion code)
https://jira.apache.org/jira/browse/ARROW-7657 (handling Arrow dictionary arrays that don't have string type values)
https://jira.apache.org/jira/browse/ARROW-6235 (BinaryArray conversion, which doesn't have an exact R analog)
https://jira.apache.org/jira/browse/ARROW-3628 (Decimal128 conversion)
https://jira.apache.org/jira/browse/ARROW-3446 (documenting how integer types are converted)

I wonder whether for things like this, there should be option(s) for choosing how to do the conversion, based on your use case and needs.

@github-actions autotune everything

It turns out we don't ever, AFAICT, move data from Arrow to R with zero copy (https://issues.apache.org/jira/browse/ARROW-9140), so I don't have any objections to making this change.


chore(main): two more checkprops functions to address code smells

Issue #, if available:
Description of changes:
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

AWS CodeBuild CI Report

CodeBuild project: githubautobuild-for-cdk-v2
Commit ID: 6cc2da801303c863935a345d7d063c0e53381b8a
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository


Decoupling the query language from the query engine?

Hi,
I watched your HYTRADBOI 2022 talk and this looks super cool!
I'm wondering how closely linked the query language is to the query engine itself?
To me it seems like the real magic is your query engine and I would love to see that exposed through other query languages. In particular I'm a contributor to PRQL and would love to be able to run PRQL queries on your query engine. PRQL currently only supports SQL as a backend and plans to go beyond that are quite some way off atm but it's interesting to think about.
Where would you see the limitations of providing a SQL frontend (and hence also PRQL) to trustfall?

Hi,
Thanks for watching the talk and for looking into Trustfall!
My stance on other frontends for the Trustfall engine is "YES PLEASE" 😁 My ultimate goal for Trustfall is to make it the LLVM of data: LLVM intermediates between programming languages and hardware, and Trustfall should intermediate between data use and data providers regardless of format, access pattern, storage mechanism, etc.
In light of the above, the language and engine today are somewhat tied together, but not particularly strongly so. I've been following the work on PRQL and I'd be interested in exploring what a PRQL/SQL frontend might look like. I suspect I won't have time to write code for it myself (I'm instead working on something that produces a literal 1000x speedup), but I'd be happy to support you or someone else taking point on it.
The key points I think would be worth keeping an eye on are:

Right now, the IR uses the GraphQL type system to represent types internally. This is something an early prototype of PRQL/SQL frontend should probably do too via a little translation layer from SQL types, and if successful we can in the future switch the IR to a more agnostic type system.
Trustfall only allows joins on pre-specified relations, whereas SQL (and presumably PRQL?) allow joining anything to anywhere else, and could in principle be used to write nonsensical joins like joining today's temperature to the scores of last night's basketball game. Users using Trustfall via PRQL/SQL may not be used to the system preventing them from doing an operation that has a well-defined result as relational algebra but is semantically nonsensical. I'd say this is more of a feature than a bug ... but some SQL users might disagree 😅
PRQL/SQL have some features that Trustfall today considers explicitly out of scope, like a general ORDER BY ability. Trustfall preserves the order of data entries produced by the underlying data provider, and Trustfall's joins are function-like in that they could be made to take an ordering parameter (resolved by the data provider). This functionality has been sufficient thus far, and giving up the general ORDER BY means we were able to implement other more important functionality instead (happy to go into more details, if they are ever useful). So supporting ORDER BY in PRQL/SQL executed via Trustfall may require an additional post-processing step, and I wouldn't recommend building it at first.

If hopping on a quick video call and walking through Trustfall queries or source code or anything else would be helpful as you decide how to move forward, I'd be happy to do that!

Just following up — would you be interested in collaborating on a PRQL frontend for Trustfall? I've been too swamped with other work to properly look into it, but if you're open to working together on it, I'd be happy to join in!


gocode: c7fddb39 -> 00e7f5ac

Motivation for this change
Also, switch to the now-maintained fork of gocode available at github.com/mdempsky/gocode because github.com/nsf/gocode is now unmaintained.
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[x] Fits CONTRIBUTING.md.

Success on x86_64-linux (full log)
Attempted: gocode
Partial log (click to expand)
installing
post-installation fixup
shrinking RPATHs of ELF executables and libraries in /nix/store/igj9ihz2fg5a7ghrfxfgs88ggdkscxg2-gocode-20180727-00e7f5a-bin
shrinking /nix/store/igj9ihz2fg5a7ghrfxfgs88ggdkscxg2-gocode-20180727-00e7f5a-bin/bin/gocode
strip is /nix/store/h0lbngpv6ln56hjj59i6l77vxq25flbz-binutils-2.30/bin/strip
stripping (with command strip and flags -S) in /nix/store/igj9ihz2fg5a7ghrfxfgs88ggdkscxg2-gocode-20180727-00e7f5a-bin/bin
patching script interpreter paths in /nix/store/igj9ihz2fg5a7ghrfxfgs88ggdkscxg2-gocode-20180727-00e7f5a-bin
checking for references to /build in /nix/store/igj9ihz2fg5a7ghrfxfgs88ggdkscxg2-gocode-20180727-00e7f5a-bin...
strip is /nix/store/h0lbngpv6ln56hjj59i6l77vxq25flbz-binutils-2.30/bin/strip
/nix/store/igj9ihz2fg5a7ghrfxfgs88ggdkscxg2-gocode-20180727-00e7f5a-bin

Success on aarch64-linux (full log)
Attempted: gocode
Partial log (click to expand)
installing
post-installation fixup
shrinking RPATHs of ELF executables and libraries in /nix/store/is0ksaz99zm9d1nc4kwjiw7jpjqb87r8-gocode-20180727-00e7f5a-bin
shrinking /nix/store/is0ksaz99zm9d1nc4kwjiw7jpjqb87r8-gocode-20180727-00e7f5a-bin/bin/gocode
strip is /nix/store/y4ymnvgxygpq05h03kyzbj572zmh6zla-binutils-2.30/bin/strip
stripping (with command strip and flags -S) in /nix/store/is0ksaz99zm9d1nc4kwjiw7jpjqb87r8-gocode-20180727-00e7f5a-bin/bin
patching script interpreter paths in /nix/store/is0ksaz99zm9d1nc4kwjiw7jpjqb87r8-gocode-20180727-00e7f5a-bin
checking for references to /build in /nix/store/is0ksaz99zm9d1nc4kwjiw7jpjqb87r8-gocode-20180727-00e7f5a-bin...
strip is /nix/store/y4ymnvgxygpq05h03kyzbj572zmh6zla-binutils-2.30/bin/strip
/nix/store/is0ksaz99zm9d1nc4kwjiw7jpjqb87r8-gocode-20180727-00e7f5a-bin


vkCmdCopyImage and vkCmdBlitImage both return incorrect results on MacOS/iOS

Hi,
As far as I can tell, the functions vkCmdCopyImage and vkCmdBlitImage both seem to return bad/incorrect texture data when trying to copy the backbuffer (get a screenshot) on MacOS and iOS.
On MacOS an empty texture with the correct dimensions is returned (0, 0, 0, 0) while on iOS this only happens if trying to get a screenshot on the very first frame, afterwards it appears to be fine. Using either of these methods on Windows works fine.
Stepping through Molten didn't seem to return anything immediately obvious.
I've uploaded a modified version of the cube demo C file to demonstrate the problem:
https://www.dropbox.com/s/blthbleqfulhds3/cube.c?dl=1

The call to get the screenshot happens after vkQueuePresentKHR (line 1325).
The code I'm using for actually grabbing the screen image is based on the Sascha Willems screenshot example and starts at line 690.
I've also added some defines for changing between copy methods (starting at line 59) to hopefully make testing/reproducing easier. =)

I've been using breakpoints and looking at the data that comes back in the memory window in XCode as my results.
Thanks,

@floorman
Is there a reason why you capture the screenshot immediately after the call to vkQueuePresentKHR() instead of immediately before?
The content will have already been written to the swapchain texture by then. The call to vkQueuePresentKHR() does not affect the content of the underlying swapchain texture...it simply tells the OS to use the image in the presentation compositor.
On macOS and iOS, swapchain resources (MTLTextures from MTLDrawables)  are a very scarce resource...and so MoltenVK very deliberately releases them as soon as vkQueuePresentKHR() is processed...so that they can be recycled by the Metal rendering engine.
This is why you are seeing an empty first image...and why subsequent images seem to be one frame behind. It is because by the time you capture the screen image...MoltenVK has released the underlying MTLTexture...and a different MTLTexture is then retrieved for use in the screenshot copy.
I have tested moving your demo_process_screenshot() call to just before vkQueuePresentKHR...and it seems to fix it...at least as far as the memory inspection indicates.
Can you test it further, and let me know if moving the screenshot call as I describe resolves the issue, please?

Hi Bill,
Moving the screenshot call as described solves the problem for me as well.
Thanks. =)


fix: enable infra label to console-plugin deployment

What type of PR is this?

Uncomment only one  /kind line, and delete the rest.
For example, > /kind bug would simply become: /kind bug

/kind bug

What does this PR do / why we need it:
Have you updated the necessary documentation?

[ ] Documentation update is required by this PR.
[ ] Documentation has been updated.

Which issue(s) this PR fixes:
Fixes #?
Test acceptance criteria:

[ ] Unit Test
[ ] E2E Test

How to test changes / Special notes to the reviewer:
Enable runOnInfra: true in GitOpsService CR
And verify that the console-plugin pods has the correct nodeSelector label added to it.

/cherry-pick v1.12


TypeError: WHERE() takes at least 4 arguments (3 given)

I'm trying to build the QueryXML with this as a segment:
<field>AssignedResourceID<expression op="IsNull"></expression></field>
By using the command:
query.WHERE('AssignedResourceID',query.IsNull)
However, I receive the error message in the title.
This should be possible, I think, as the XML would be a valid query.  Is there any way around this?

True is the third argument
On Fri, 12 Jul 2019, 11:47 James Leach<EMAIL_ADDRESS>wrote:

I'm trying to build the QueryXML with this as a segment:
AssignedResourceID
By using the command:
query.WHERE('AssignedResourceID',query.IsNull)
However, I receive the error message in the title.
This should be possible, I think, as the XML would be a valid query. Is
there any way around this?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/MattParr/python-atws/issues/66?email_source=notifications&email_token=ABIM7456J6S4TE4A5VB4AWLP67BBJA5CNFSM4IBZ4QS2YY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4G6YHHUA,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABIM7432Z3WB3KTXJCHOPXLP67BBJANCNFSM4IBZ4QSQ
.

When I do that:
query.WHERE('AssignedResourceID',query.IsNull,True)
I don't receive an error, and the XML ends up looking like this:
>>> print query.pretty_print()
<?xml version="1.0" ?>
<queryxml>
        <entity>Ticket</entity>
        <query>
                <field>
                        QueueID
                        <expression op="Equals">29971060</expression>
                </field>
                <field>
                        Status
                        <expression op="NotEqual">5</expression>
                </field>
                <field>
                        AssignedResourceID
                        <expression op="IsNull">True</expression>
                </field>
        </query>
</queryxml>

But when I run the query it just sits there forever...
If I build the XML myself (using XML I've used in another project), converting the XML from a string using xml.etree.ElementTree's fromstring function:
>>> querystring = '<queryxml><entity>Ticket</entity><query><field>QueueID<expression op="Equals">29971060</expression></field><field>Status<expression op="NotEqual">5</expression></field><field>AssignedResourceID<expression op="IsNull"></expression></field></query></queryxml>'
>>> queryxml = fromstring(querystring)
>>> query = atws.Query()
>>> query._queryxml = queryxml
>>> print query.pretty_print()
<?xml version="1.0" ?>
<queryxml>
        <entity>Ticket</entity>
        <query>
                <condition>
                        <field>
                                QueueID
                                <expression op="Equals">29971060</expression>
                        </field>
                </condition>
                <condition>
                        <field>
                                Status
                                <expression op="NotEqual">5</expression>
                        </field>
                </condition>
                <condition>
                        <field>
                                AssignedResourceID
                                <expression op="IsNull"/>
                        </field>
                </condition>
        </query>
</queryxml>

This query runs very quickly and returns the expected results.
One obvious difference is the  elements.   If I leave them out when I build the XML from a string then things just hang when I query the tickets.

I think an empty string will work on the third argument then.
We will have to correct the handling of the query operators that do not
allow a value.  In previous versions of the API I do not think this
mattered.
On Sat, 13 Jul 2019, 08:37 James Leach<EMAIL_ADDRESS>wrote:

When I do that:
query.WHERE('AssignedResourceID',query.IsNull,True)
I don't receive an error, and the XML ends up looking like this:

print query.pretty_print()

Ticket

                        QueueID
                        29971060

                        Status
                        5

                        AssignedResourceID
                        True

But when I run the query it just sits there forever...
If I build the XML myself (using XML I've used in another project),
converting the XML from a string using xml.etree.ElementTree's fromstring
function:

querystring = 'TicketQueueID29971060Status5AssignedResourceID'
queryxml = fromstring(querystring)
query = atws.Query()
query._queryxml = queryxml
print query.pretty_print()

Ticket

                                QueueID
                                29971060

                                Status
                                5

                                AssignedResourceID

This query runs very quickly and returns the expected results.
One obvious difference is the elements. If I leave them out when I build
the XML from a string then things just hang when I query the tickets.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/MattParr/python-atws/issues/66?email_source=notifications&email_token=ABIM7466P5CPMEPVVRLHU6TP7DTO7A5CNFSM4IBZ4QS2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODZ22BCQ#issuecomment-511025290,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABIM74Z4GEJR2YVZHJ2YVHLP7DTO7ANCNFSM4IBZ4QSQ
.

Using an empty string on the third argument does yield XML that looks like it would work.  It's similar to the XML that I built from the string - without the 'condition' elements:
>>> query.WHERE('AssignedResourceID',query.IsNull,'')
>>> print(query.pretty_print())
<?xml version="1.0" ?>
<queryxml>
        <entity>Ticket</entity>
        <query>
                <field>
                        QueueID
                        <expression op="Equals">29971060</expression>
                </field>
                <field>
                        Status
                        <expression op="NotEqual">5</expression>
                </field>
                <field>
                        AssignedResourceID
                        <expression op="IsNull"/>
                </field>
        </query>
</queryxml>

However, the same issue occurs during the actual query.  It just sits there not returning any data.   Perhaps the 'condition' elements are important, now?

Actually, using query.AND, like I probably should be anyway, along with an empty string for the third argument results in this XML:
query = atws.Query('Ticket')
query.WHERE('QueueID',query.Equals,29971060)
query.AND('Status',query.NotEqual,5)
query.AND('AssignedResourceID',query.IsNull,'')
print query.pretty_print()
<?xml version="1.0" ?>
<queryxml>
        <entity>Ticket</entity>
        <query>
                <field>
                        QueueID
                        <expression op="Equals">29971060</expression>
                </field>
                <condition operator="AND">
                        <field>
                                Status
                                <expression op="NotEqual">5</expression>
                        </field>
                </condition>
                <condition operator="AND">
                        <field>
                                AssignedResourceID
                                <expression op="IsNull"/>
                        </field>
                </condition>
        </query>
</queryxml>

And allows the query to run successfully.
I believe the only potential issue is the handling of the query operators that do not allow a value.   The queries hanging were likely due to me not providing well formatted XML.

Maybe if you print the entire code for the query and condition...ensuring
passwords and usernames are not present or obscured I might see what the
problem is.
On Tue, 16 Jul 2019, 02:41 James Leach<EMAIL_ADDRESS>wrote:

Using an empty string on the third argument does yield XML that looks like
it would work. It's similar to the XML that I built from the string -
without the 'condition' elements:

query.WHERE('AssignedResourceID',query.IsNull,'')
print(query.pretty_print())

Ticket

                        QueueID
                        29971060

                        Status
                        5

                        AssignedResourceID

However, the same issue occurs during the actual query. It just sits there
not returning any data. Perhaps the 'condition' elements are important, now?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/MattParr/python-atws/issues/66?email_source=notifications&email_token=ABIM745ARFJI35PZABW6EPTP7SEBZA5CNFSM4IBZ4QS2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODZ55EYQ#issuecomment-511431266,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABIM747PTKO3WR4Z7MKPEMTP7SEBZANCNFSM4IBZ4QSQ
.

Okay.  Great that you got it sorted.
On Tue, 16 Jul 2019, 03:06 James Leach<EMAIL_ADDRESS>wrote:

Actually, using query.AND, like I probably should be anyway, along with an
empty string for the third argument results in this XML:
query = atws.Query('Ticket')
query.WHERE('QueueID',query.Equals,29971060)
query.AND('Status',query.NotEqual,5)
query.AND('AssignedResourceID',query.IsNull,'')
print query.pretty_print()

Ticket

                        QueueID
                        29971060

                                Status
                                5

                                AssignedResourceID

And allows the query to run successfully.
I believe the only potential issue is the handling of the query operators
that do not allow a value. The queries hanging were likely due to me not
providing well formatted XML.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/MattParr/python-atws/issues/66?email_source=notifications&email_token=ABIM7434NA65MTXCQXPEOJ3P7SG57A5CNFSM4IBZ4QS2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODZ57RBA#issuecomment-511441028,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABIM742IHAK7UUSSHEHT6HTP7SG57ANCNFSM4IBZ4QSQ
.


Firebase Remotely hosted Code error from Chrome Developer Store

Describe the bug
Hi! I am using firebase in my extension, apparently it downloads remotely hosted code and chrome store rejected my package.
See below:

Violation reference ID: Blue Argon
Technical Requirements - Additional Requirements for Manifest V3:
Violation: Including remotely hosted code in a Manifest V3 item.
Violating Content:
Code snippet: content-scripts/jobDesc.js: https://www.google.com/recaptcha/enterprise.js?render=
How to rectify: Ensure that all logic related to the extensions operation is included in the extension package. For more information please refer to the documentation on removing remotely hosted code & migration checklist on Manifest V3 version.
Relevant section of the program policy:
Extensions using Manifest V3 must meet additional requirements related to the extension's code. Specifically, the full functionality of an extension must be easily discernible from its submitted code. (learn more)

When I was using webpack, I had to manually remove those remotely downloaded code using replace plugin this code below:
new ReplaceInFileWebpackPlugin([
				{
					dir: 'dist', // replace with your output dir
					test: [/background.js(\.map)?$/, /popup.js(\.map)?$/], // replace this with something that matches your output
					rules: [
						{
							search: 'https://apis.google.com/js/api.js',
							replace: '',
						},
						{
							search: 'https://www.google.com/recaptcha/enterprise.js',
							replace: '',
						},
					],
				},
			]),

How can we do the same thing in WXT perhaos using vite?
To Reproduce
If you include firebase in any project it will be flagged.
Expected behavior
A clear and concise description of what you expected to happen.
Additional context
See Chrome's guide on fixing this: https://developer.chrome.com/docs/extensions/develop/migrate/remote-hosted-code

How did you end up fixing this @ddeisadze?


Ability to rename Audio inputs

It would be nice to be able to add names to audio inputs.

merged this into develop


Prepare for Phase I

Get everything ready for phase 1, including:

Merge client & server branches to respective main branch (Faculty side remaining)
README.md file creation with proper documentation
final testing (Both portals)
Deploy test via a hosting service

Phase 1 tentative date: Friday, 7th July
(Student Portal)
Possible Rollout by next week end
Preparation needed before rollout:

test all functionality, remove unnecessary stuff
load all the spit student data thru csv provided for initialization
small deploy test with some hosting service