Define and implement wind resource data schema and format

The format of the wind resource data should be to represent the probability mass/density of a wind resource joint PDF, $p(\psi, V)$ where $\psi$ and $V$ give the prevailing wind direction in degrees (0°, 360° as north) and the wind speed in m/s, respectively.

My thinking on this is progressing towards actually using FLORIS's wind rose representation by default and using a WindQuery class to translate that to queries when necessary, but more generally using it also to hold onto a set of wind states to query with a solver.

Should be complete as of<PHONE_NUMBER>d17280f762c583732a891ec2fc8456


use idc-index for IDCClient directly

To address second task left on #15, I removed IDCClient.py as it will be imported from idc-index python package. Added a cursor to indicate while initializing IDCClient.

Interesting error!

I think I know exactly where the error (not a fatal one) is happening. The download works just fine but throws this error, because I wanted to stream the output of s5cmd download. But it may not be useful at all, so I'll comment it out.

I have a bit better fix for it, hold on

https://github.com/ImagingDataCommons/idc-index/pull/5


Skeleton should have npm postinstall script to run jspm install -y

I know we've had this come up before...but the question I still have is, do we want to hide jspm away like that?

I don't like this change. It may be good for newcomers that they type one less shell command when they first setup the project, but npm and jspm have two different roles in the skeleton. One is for devDependencies and one is for client dependencies.
What I recommend is adding recipes and docs (?) for the skeletons (ex: https://github.com/kriasoft/react-starter-kit/tree/master/docs/recipes). Then make a recipe explaining how to add jspm install as postinstall script.

I personally vote against this. It's a convenience, sure, but I think it's an abstraction and I don't think it's worth it. It may not be a bad idea to add an optional postinstall script (perhaps with the code commented out with an "uncomment to use" note), but I definitely don't want this as a default.
The only use I can see for this is for Visual Studio users who use an integrated task runner to call npm install. I think this would actually be a hindrance for the rest of us. That said, it may have a place in the Typescript skeleton navigation project.

The reason I brought this up originally is because I've been seeing this done frequently in many projects I've come across. It seems that people use the npm command as a task runner (npm test, npm start`). It kind of struck a cord with me in that light, as it seemed quite nice to be able to run a single command and get all dependencies installed, even if those dependencies are handled by separate package managers.
As @jedd-ahyoung said, it's also really nice for Visual Studio users, which is a not-insignificant section of the userbase.

It's a good reason. Perhaps we can distill the argument a bit here - what's the target audience? Aurelia has preferred convention over configuration for code standards; do we want to do the same for setup purposes?
People new to JS, npm, and the CLI may find it a boon to simply run one command. It also makes the documentation simpler, and it lowers the barrier to entry somewhat. Additionally, it helps with VS tooling.
More advanced users may be able to find this easily and reason about what's going on; the postinstall scripts would have to be noticeable, though. I am honestly a little concerned about abstracting away JSPM, as many users will have to jspm install new dependencies when needed.
Do we want to abstract the tooling? I think that the aurelia-cli project was an attempt to do this, and it didn't end well. However, it wasn't a bad idea; I simply think that didn't end well because the target audience (CLI users) didn't need that abstraction - they already had the necessary tools to do what was needed. That said, I understand that the installation step is a little different - not everyone will be dropping down to the CLI.
I don't have an answer as of yet. I just wanted to write this up to foster more discussion. Questions lead to questions which lead to answers. Right?

As an aside - note that I recognize that I may not fall into the target demographic for these changes, which I accept and understand. The questions above are sincere questions - I hope it came across as an opener for discussion, not a cynical downvote against the idea.

When have you been in the target demographic for anything, @jedd-ahyoung?

Last time was when I was in the target demographic for your mom, @AshleyGrant.

BTW, Jedd and I had dinner tonight, so that's why I can be snarky with him. He brings up some good points. I'm of the mind that this change will be necessary for the asp.net versions of the skeleton for better automation of visual studio.

Closing for now since this is heavily debated.


MPAS-Analysis v0.6

MPAS-Analysis has just been updated to v0.6.  It would be good to update a-prime accordingly, as there are many enhancements:
https://github.com/MPAS-Dev/MPAS-Analysis/releases/tag/v0.6
I'm happy to help wherever I can, e.g. with testing and with changes to the configuration.
Note: MPAS-Analysis now only works properly on 1 node, not on 1 node per task.  So various batch scripts will need to be changed accordingly.

addressed by #24


Unable to build ember after updating to 0.4.1 or higher

I updated ember-cli-htmlbars-inline-precompile when updating to ember-cli 2.13.2 and found I could no longer build ember. I pinpointed it to the 0.4.1 version of this package. Any suggestions on how to diagnose this issue?
Build failed.
The Broccoli Plugin: [BroccoliMergeTrees] failed with:
Error: Build Canceled: Broccoli Builder ran into an error with Babel plugin. 💥
    at new BroccoliBuildError (/Users/bryan/src/betterup-app/frontend/node_modules/broccoli-builder/lib/broccoli-build-error.js:40:9)
    at /Users/bryan/src/betterup-app/frontend/node_modules/broccoli-builder/lib/builder.js:168:19
    at tryCatch (/Users/bryan/src/betterup-app/frontend/node_modules/rsvp/dist/rsvp.js:539:12)
    at invokeCallback (/Users/bryan/src/betterup-app/frontend/node_modules/rsvp/dist/rsvp.js:554:13)
    at publish (/Users/bryan/src/betterup-app/frontend/node_modules/rsvp/dist/rsvp.js:522:7)
    at publishRejection (/Users/bryan/src/betterup-app/frontend/node_modules/rsvp/dist/rsvp.js:457:3)
    at flush (/Users/bryan/src/betterup-app/frontend/node_modules/rsvp/dist/rsvp.js:2414:5)
    at _combinedTickCallback (internal/process/next_tick.js:73:7)
    at process._tickCallback (internal/process/next_tick.js:104:9)

The broccoli plugin was instantiated at:
    at BroccoliMergeTrees.Plugin (/Users/bryan/src/betterup-app/frontend/node_modules/broccoli-plugin/index.js:7:31)
    at new BroccoliMergeTrees (/Users/bryan/src/betterup-app/frontend/node_modules/broccoli-merge-trees/index.js:42:10)
    at Class.postprocessTree (/Users/bryan/src/betterup-app/frontend/node_modules/ember-browserify/lib/index.js:79:14)
    at projectOrAddon.addons.reduce (/Users/bryan/src/betterup-app/frontend/node_modules/ember-cli/lib/utilities/addon-process-tree.js:6:25)
    at Array.reduce (native)
    at addonProcessTree (/Users/bryan/src/betterup-app/frontend/node_modules/ember-cli/lib/utilities/addon-process-tree.js:4:32)
    at EmberApp.addonPostprocessTree (/Users/bryan/src/betterup-app/frontend/node_modules/ember-cli/lib/broccoli/ember-app.js:586:12)
    at EmberApp.appAndDependencies (/Users/bryan/src/betterup-app/frontend/node_modules/ember-cli/lib/broccoli/ember-app.js:1114:33)
    at EmberApp.javascript (/Users/bryan/src/betterup-app/frontend/node_modules/ember-cli/lib/broccoli/ember-app.js:1225:30)
    at EmberApp.toArray (/Users/bryan/src/betterup-app/frontend/node_modules/ember-cli/lib/broccoli/ember-app.js:1662:12)

Updated some dependencies/deprecations and I don't hit this anymore (There was a fair amount of activity since I tried this activity, so it's unclear which actually eliminated the issue). Actually hitting #71 instead, will follow the suggestions there.


Mainboard firmware architecture description

This PR adds a markdown doc which describes the AMDS mainboard firmware design. This will be helpful to future users who want to understand the system performance.
Read the main doc I added here.

Suggestion of updating Sync signals to " 'Sync_xxx' shall be a square wave". A square wave/pulse is a requirement for proper timing, right?
The use of "normally" suggest I could feed this a triangle wave and the system would maintain the described timing latency.
For TX signals 'DATAx' the UART is described, how is the ADC data packed into the 8bit transmission? is ADC data 8bit, 32bit? Byte order in UART transmission might be helpful also.

@ngadiyar93 Good idea for adding a doc about the AMDC side of the AMDS interface.
I think this doesn't belong in this repo, but instead, in the AMDC repos -- probably AMDC-Firmware since there is a full driver in the FPGA to interface to the AMDS.
Can you create an issue in AMDC-Firmware which explains the need for this? Thanks.

@GnomeTek See updated doc. I added comments on data packing/ordering in UART stream.

This ended up getting merged into the docs.amd.dev website, see: https://docs.amdc.dev/accessories/amds/firmware/


cURL contains too many values in "Accept" parameter and yields multiple "Content-type" parameters

Hi!
I have encountered strange cURL that returns after I make a call from documentation.
cURL contains too many "application/json" values in "Accept" and there are 2 "Content-Type" parameters as well.
I am almost sure that it has to do something with the quantity of examples in both path parameters and body.
Can you take a look, please?

@pavlovmike @molochiyivan

thanks, can you provide a minimal example to reproduce it.
I tested
https://mrin9.github.io/RapiDoc/examples/examples-multiple.html#post-/multiple-example-in-request-body
and
https://mrin9.github.io/RapiDoc/examples/examples-multiple.html#get-/multiple-examples-in-query-param
was not able to reproduce it.

Hi!
I guess you could take a look here

can you provide a minimal spec that highlights this issue. you can update the example that I shared above if needed

can you provide a minimal spec that highlights this issue. you can update the example that I shared above if needed
Here we go. Please note that content type duplicates as number of items in 'responses' section increases

openapi: 3.0.3
tags:
  - name: users
    description: basic description
info:
  title: Sample API
  description: Retrieves user by country and city
  version: 0.0.1
  contact:
    name: me
servers:
  - url: http://api.example.com/v1
components:
  examples:
    example1:
      value: "ua"
      summary: "example $ref ua"
    example2:
      value: "pl"
      summary: "example $ref pl"
    example3:
      value: "ch"
      summary: "example $ref ch"
paths:
  /users/{country}/{city}:
    get:
      operationId: "get_users"
      tags:
        - users
      summary: Returns a list of users.
      description: Optional extended description in CommonMark or HTML.
      parameters:
      - name: 'country'
        required: true
        in: 'path'
        schema:
          type: 'string'
        examples:
          example1:
            $ref: '#/components/examples/example1'
          example2:
            $ref: '#/components/examples/example2'
      - name: 'city'
        required: true
        in: 'path'
        schema:
          type: 'string'
        examples:
          example1:
           value: "lviv"
           summary: "example inline lviv"
          example2:
           value: "kyiv"
           summary: "example inline kyiv"
      responses:
        '200':    # status code
          description: A JSON array of user names
          content:
            application/json:
              schema:
                type: array
                items:
                  type: string
        '404':    # status code
          description: not found
          content:
            application/json:
              schema:
                type: array
                items:
                  type: string


How to make a custom splash screen with animated android views in Flutter?

How to make a custom splash screen with animated android views in Flutter?
In the Flutter Splash Screen documentation they have mentioned one, but I couldn't understand how to implement that.
The documentation link is here.
https://flutter.dev/docs/development/ui/splash-screen/android-splash-screen#creating-a-custom-splashscreen

Hi @noobcoder17
Please see https://flutter.dev/community for resources and asking questions like this,
you may also get some help if you post it on Stack Overflow.
(like this one)
Closing, as this isn't an issue with Flutter itself,
if you disagree please write in the comments and I will reopen it
Thank you

Hi @noobcoder17
Please see https://flutter.dev/community for resources and asking questions like this,
you may also get some help if you post it on Stack Overflow.
(like this one)
Closing, as this isn't an issue with Flutter itself,
if you disagree please write in the comments and I will reopen it
Thank you

Thanks for your help. Actually all the tutorials are showing that a stateful/less widget where the animation is going on and after that animation the home screen is shown. For this they are showing the splash screen for 2 to 3 seconds which is not technically correct. Splash screen should be shown until the first frame of app appears. But they are showing the splash screen for 3 seconds without any reason by the help of a Timer function. So I just wanted to know that how to add a real custom splash screen mentioned in the Flutter documentation.
https://flutter.dev/docs/development/ui/splash-screen/android-splash-screen#creating-a-custom-splashscreen
The example in the documentation in above link is not clear to me. So can anyone help to implement that in a real app example?

Hi @noobcoder17
please follow up the linked issue for
the splash screen disappearing too early
https://github.com/flutter/flutter/issues/20827
https://github.com/flutter/flutter/issues/39494
thank you


PROD 541: Chompmas streaks mystery boxes

Implements whitelisted Chompmas streaks mystery boxes.
Requires the mechanism update to function.

I set CHOMPMAS_MIN_STREAK=1 in preview, but I'm not getting a mystery box

Oh I need to add myself to allowlist. I'll try that.

We also need the mechanism-engine update.

We also need the mechanism-engine update.

We also need to run migrations for this to work. For now I just want to be able to test in staging so I want to merge. Can you:

Use the existing event type for claim all instead of chompas?
Double check that this code will not impact prod if merged (ie hidden behind FF feature flag)

We also need the mechanism-engine update.

We also need to run migrations for this to work. For now I just want to be able to test in staging so I want to merge. Can you:
1. Use the existing event type for claim all instead of chompas?

Done

2. Double check that this code will not impact prod if merged (ie hidden behind FF feature flag)

I added an extra flag. Everything looks good with it switched off.


Percona Everest cannot be installed on ARM architecture due to percona/everest-catalog Docker image being amd64 only

When attempting to install Percona Everest on ARM architecture, the installation fails because the percona/everest-catalog Docker image is built for amd64 only. ARM-based systems like Ampere CPUs on Ubuntu 24.04 are becoming more common, and supporting ARM architecture would be greatly beneficial for users on these platforms.
Steps to reproduce:

Run installation on an ARM-based server (Ampere CPU, Ubuntu 24.04).
Observe failure due to the percona/everest-catalog Docker image being incompatible with ARM.

Expected behavior:

Percona Everest should be installable on ARM architecture by providing multi-architecture Docker images, including support for arm64.
everest catalog

System details:

Ubuntu 24.04 on ARM architecture (Ampere CPU).

hey @maamoon95
Thanks for the feedback! We want to eventually support ARM architecture, for Everest this wouldn't be a very heavy lift but we are dependent on our operators and database distribution supporting ARM and unfortunately only one of them currently is. There is an ongoing effort to add ARM support for MySQL and PMM which should be delivered in next 2 quarters and it make sense to release Everest for ARM at the same time when most components have this support.


Update docker/docker

Updates the docker/docker version used in the examples to the following issue:
github.com/docker/docker/pkg/term imports
	github.com/Sirupsen/logrus<EMAIL_ADDRESS>parsing go.mod:
	module declares its path as: github.com/sirupsen/logrus
	        but was required as: github.com/Sirupsen/logrus

Related: https://github.com/pulumi/ci-mgmt/issues/513

Good catch. Let me update the description for all open PRs related to this.


Add Dataset Downloading, Info, and Checksums

We want to go for the largest datasets we can for this. They are listed in a Google doc. Not all of them will be downloadable via public links, so we want to provide checksums in this repo so that folks know they're working with the same data once they acquire it. Would also be nice to give the dataset info in the repo.

Sounds good, haven't heard back from Spotify yet. Mozilla common voice checksum:
https://commonvoice.mozilla.org/en/datasets
sha256 checksum: 0f8fdfc4fe715738be94ee49c4fb63d5f1608d2e6a43a2bed80f6cb871171c36

Some stats on Common Voice English version 6.1.
1,224,864 validated clips, of which 1,224,858 have UTF-8 captions. 596,665 unique sentences
52 Python characters on average, and 52.9 bytes on average.
Quantiles of byte lengths:
10% - 23
20% - 32
30% - 39
40% - 45
50% - 52
60% - 60
70% - 67
80% - 74
90% - 83
95% - 90
98% - 97
Max byte length of 210.


Switch Pro Controller

So I use the Switch Pro Controller on emulator in Windows. Has been working fine, but the first time I clicked a button on the controller after opening Splitty in Chrome, it automatically connected to the splitter, and a blue light appeared around the home button. The controller now works in splitty, but no other programs on my computer detect any input.. Not the emulator, and not even windows' input-test-thing in bluetooth settings. I've tried removing the bluetooth device, quitting Splitty, and adding the device again, but it now always goes automatically into the state with the blue light.. Splitty can detect it but no other programs as far as I know..

Fixed by restarting computer.. duh
Don't know why I didn't try that before posting. But oh well, now you know.

Happy to see that your problem was fixed. Sorry for not having replied earlier.


Adjusted People, Added Publications

Fixed some typos among the people. Please note: I was not able to preview the site locally yet.
Changed "References" on the people page to "Publications" as it displays not (just) references in the peoples description. Added Publications Elisa had while at ITU

Also fixed Dan's name in file and presentation


Possible paths when small or tiny.

Be able to go through every possible little cracks (bboxes on blocks or something) when you are tiny or small, and perhaps even go under certain blocks when tiny (1/8  -  1/256)  etc.
EDIT: Changed ''(1/512  -  1/4096)'' to ''(1/8  -  1/256)'' .
And ''little cracks when''  to  ''little cracks (bboxes on blocks or something) when''

The game is mostly responsible for that part - i did a couple of hacks like the nether portal and the bed, but overriding most blocks bboxes so that they are more precise - too much unthankful work.
Some mods are precise with their bboxes - for example Chisel&Bits, the main inspiration for this mod in the first place.
Also, what kind of cracks do you want from 163 pixels blocks exaclty? :D

I'm not such of a math fan 😅  .  And yes i tried going under a bed, which is great!! . Could you mention other mods than Chisel&bits (Which i am using with your mod) ?

Oh i just thought of one!! - Fences and gates, you still can't go through them when you're tiny or small

Minecraft bboxes do not follow models exactly, as I've said.
I could do the same override as with the nether portal block, just for the fences and the fun, huh

Changing more vanilla hitboxes is yet another non-goal(the portal hack is already gone and maybe I should remove the bed one too), however I am (still) planning on making a small mod that will allow you to customize vanilla hitboxes with JSON, just like vanilla did with block models.

Changing more vanilla hitboxes is yet another non-goal(the portal hack is already gone and maybe I should remove the bed one too), however I am (still) planning on making a small mod that will allow you to customize vanilla hitboxes with JSON, just like vanilla did with block models.


refactor(*): update the Host and Contact field in the config

What this PR does / why we need it:
Update the definitions of the Host and Contact fields in the configuration to sync with the swagger specification
Which issue(s) this PR is related to (optional, link to 3rd issue(s)):
Fixes #
Reference to #

Special notes for your reviewer:
/cc @xpofei

Release note:

NONE

/lgtm

/lgtm

/approve

/approve


Add fail task

fix Issue #314 by adding IsFailed to ProgressTask

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

@GabrielNarcisi There are some build problems with your PR which need to be fixed before we can review it.


chore: Add GitHub issues templates

To better categorize our GitHub issues, we will add the following templates:

Bug Report
Feature Request
General Inquiries

We will disable the option to create a blank issue so all issues must use one of the three templates mentioned above. Tested each template by pushing changes to separate branch in forked repo and verifying the generated form.

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

I'm worried we are adding too much friction for people to open issues. See if you can simplify the process by eliminating questions or checkboxes that don't add much value.
We can add stricter controls as needed, but given this is still a small repository in terms of user base, my preference is for a more lightweight process. I believe the issues this repository have received so far are evidence of this approach, as they are largely high quality posts.

nit: We have a question about the build system they are using. Maybe we should have one more question asking more details about their application they are using RUM with. Details related to if its a SPA/MPA might help us see if issue is specific to certain type of applications.

This piece of information can at times definitely be helpful when debugging. Added question in the bug report template.


TSAN and memory order consume semantics

Tell TSAN that we know that we're doing with CONSUME semantics so that it doesn't flag false positive issues
Radar-Id: rdar://problem/105634683

@swift-ci please test

@swift-ci please test Linux platform

@swift-ci please test

@swift-ci please test macOS platform


Bower install does not work

Bower doesn't install all files, only bower.json, package.json, README.md and license.

@dlewand691
{
"headroom.js": "https://npmcdn.com/headroom.js/bower.zip"
}
Add this to your bower dependencies

Still does not work. Bower says package not found. Cannot get it to work with any way I've tried.

Yes, still has errors
bower bower#*               not-cached https://npmcdn.com/headroom.js/bower.zip#* bower bower#*                  resolve https://npmcdn.com/headroom.js/bower.zip#* bower headroom.js#*             cached https://unpkg.com/headroom.js/bower.zip bower headroom.js#*           validate https://unpkg.com/headroom.js/bower.zip#* bower bower#*                 download https://npmcdn.com/headroom.js/bower.zip bower bower#*                  extract bower.zip bower bower#*             invalid-meta The "main" field cannot contain minified files bower bower#*             invalid-meta The "main" field cannot contain minified files bower bower#*             invalid-meta The "main" field cannot contain minified files bower bower#*             invalid-meta The "main" field has to contain only 1 file per filetype; found multiple .js files: ["dist/headroom.js","dist/headroom.min.js","dist/jQuery.headroom.js","dist/jQuery.headroom.min.js","dist/angular.headroom.js","dist/angular.headroom.min.js"] bower headroom.js#*           resolved https://npmcdn.com/headroom.js/bower.zip bower headroom.js#*            install headroom.js

The dist folder is not pushed to the repository and the src folder is ignored so when you install via bower you only get the files that are not in ignored list in bower.json
You should choose a way to expose your dist files or src files to your end user.

please fisx this issue. it should only take a few minutes to do so that people can stay on specific versions

Thanks for your Message.
From 24.12.2016 - 08.01.2017 our Office is closed cause of Holidays. Maybe we will answer in this time but it could take some time. Please note that we also doesn't provide support for our Templates or Extensions in this Time Period.
Thank you.

C:\Program Files (x86)\Microsoft Visual Studio 14.0\Web\External>bower install "
headroom.js": "https://npmcdn.com/headroom.js/bower.zip"
bower not-cached    https://npmcdn.com/headroom.js/bower.zip#*
bower resolve       https://npmcdn.com/headroom.js/bower.zip#*
bower download      https://npmcdn.com/headroom.js/bower.zip
bower extract       bower#* bower.zip
bower invalid-meta  for:C:\Users\XXX\AppData\Local\Temp\XXX\bowe
r\c3a4419258c98e9dc1dd5c36a7ec9fad-15308-PxA2ts\bower.json
bower invalid-meta  The "main" field cannot contain minified files
bower invalid-meta  The "main" field cannot contain minified files
bower invalid-meta  The "main" field cannot contain minified files
bower invalid-meta  The "main" field has to contain only 1 file per filetype; fo
und multiple .js files: ["dist/headroom.js","dist/headroom.min.js","dist/jQuery.
headroom.js","dist/jQuery.headroom.min.js","dist/angular.headroom.js","dist/angu
lar.headroom.min.js"]
bower resolved      https://npmcdn.com/headroom.js/bower.zip#e-tag:W/"21e9-15
bower ENOTFOUND     Package headroom.js: not found

TBH i'm considering dropping bower support. I don't use it, I constantly break it, and perhaps most importantly - npm has won

Can't download 0.9.3 from unpkg.com.

<EMAIL_ADDRESS>

today it seems bower install does  not work again. anyone same issue?

Same issue here!

Same issue :-(

I'm going to drop bower support since it has been deprecated / put into maintenance mode. You should be able to continue using it, by following the advice here.


Publish in crates.io?

Are you considering to put it on crates.io to be able to install using cargo install?

Hello. I'm not sure if games are the sort of thing that belong on crates.io. I always thought crates.io & cargo were meant for Rust development dependencies & tools.
There would be other issues such as the fact that this project requires SDL2 to be installed in order to build or run and installing that is outside of the scope of cargo. I do want to find a way to properly create cross-platform binaries though. I've tried using trust but have had issue with dependencies & building on Windows.


Issue #71: Refactored DataReader and DataWriter

@chenlica @JavierJia .. Refactored DataWriter to accept Analyzer object and DataReader to accept Query object. Please review the code.

I left two comments about the analyzer used in a reader and a writer. After you take care of them, you can do a merge.
Please also send an email to the class to ask people to do a merge from the master into their branch to minimize future conflicts.


[tcgc] initial version to support generic type decorators in sdk types

resolve: https://github.com/Azure/typespec-azure/issues/829
current design:

use whitelist configured in tspconfig.yaml to do decorators filtering, support equal/regex comparison
all the decorator arguments will use jsValue from typespec and the only extra logic is literal and enum member type will be converted to their value

All changed packages have been documented.

:white_check_mark: @azure-tools/typespec-client-generator-core

Show changes
@azure-tools/typespec-client-generator-core - feature ✏

export decorators in white list to all sdk types

You can try these changes at https://cadlplayground.z22.web.core.windows.net/typespec-azure/prs/966/
Check the website changes at https://tspwebsitepr.z22.web.core.windows.net/typespec-azure/prs/966/

@iscai-msft @live1206 @m-nash could you review again?

Would like to learn more about the whitelist configuration in tspconfig.yaml, should every service team provide the whitelist when writing tspconfig.yaml? Will the list be very long and have many duplicate decorators across different service's tspconfig.yaml? Is there a default whitelist that covers common decorators, and service team can add additional special decorators if it does not exist.

Would like to learn more about the whitelist configuration in tspconfig.yaml, should every service team provide the whitelist when writing tspconfig.yaml? Will the list be very long and have many duplicate decorators across different service's tspconfig.yaml? Is there a default whitelist that covers common decorators, and service team can add additional special decorators if it does not exist.

tcgc left it to language's emitter. when you call createSdkContext, you could add default to decorators-white-list config.

Would like to learn more about the whitelist configuration in tspconfig.yaml, should every service team provide the whitelist when writing tspconfig.yaml? Will the list be very long and have many duplicate decorators across different service's tspconfig.yaml? Is there a default whitelist that covers common decorators, and service team can add additional special decorators if it does not exist.

tcgc left it to language's emitter. when you call createSdkContext, you could add default to decorators-white-list config.

Emm. Shall TCGC have a default whitelist shared by each language as well?

Would like to learn more about the whitelist configuration in tspconfig.yaml, should every service team provide the whitelist when writing tspconfig.yaml? Will the list be very long and have many duplicate decorators across different service's tspconfig.yaml? Is there a default whitelist that covers common decorators, and service team can add additional special decorators if it does not exist.

tcgc left it to language's emitter. when you call createSdkContext, you could add default to decorators-white-list config.

Emm. Shall TCGC have a default whitelist shared by each language as well?

we do not have a clear whitelist for now, so leave it for empty.


Add pixi support (document how to install pixi in the shell)

Either add some magic commands, or at least document how to install pixi from the shell on all platforms.
Then document how to use pixi to install vim and other essential programs that are not part of the shell itself.

One one machine I installed pixi using rust by cargo b -r. Then I copied pixi.exe to ~/bin, and added ~/bin to $PATH.
I think we can simply append such paths in .shellrc (#95), just like on Linux, no need to modify global PATH.

Ideally, you type pixi, which shell would recognize and ask to download it. It's just one binary, so it will download it and put it somewhere (to be figured out), so that it just works.
One pixi is installed (single binary), one can use pixi to install everything else (eventually including things like conda, rust etc.).


[ConstraintSolver] NFC: refactor candidate solver to use constraint system arena

While shrinking we have to allocate containers for the reduced domains
for some of the candidates, it's currently done using permanent arena
of the ASTContext allocator. This patch changes candidate solver to
use arena associated with the parent constraint system, which significantly
limits lifetime of domain containers.

@swift-ci please test

Build failed
Jenkins build - Swift Test Linux Platform
Git Commit - 2a10240c7cc6907a56e3915d17b53fcfcc2de125
Test requested by - @xedin

Build failed
Jenkins build - Swift Test OS X Platform
Git Commit - 2a10240c7cc6907a56e3915d17b53fcfcc2de125
Test requested by - @xedin

@swift-ci please smoke test

@swift-ci please smoke test

@swift-ci please smoke test

@swift-ci please smoke test

/cc @jrose-apple mostly changes in the ASTContext

@swift-ci please smoke test

@swift-ci please clean smoke test

@swift-ci please clean smoke test

@swift-ci please smoke test

@swift-ci please smoke test

@rudkx all of the intermediate arrays used for decls are going to be allocated temporarily while main constraint system is alive but the final versions are going to be still permanent because we might need to keep OSR longer for diagnostics.


fix(reactivity): fix #709 issue, effect should observe for of iteration in Map

Solution's description
In this unit test case:
it('should observe for of iteration', () => {
  let dummy
  const map = reactive(new Map())
  effect(() => {
    dummy = 0
    // eslint-disable-next-line no-unused-vars
    for (let [key, num] of map) {
      key
      dummy += num
    }
  })

  expect(dummy).toBe(0)
  map.set('key1', 3)
  expect(dummy).toBe(3)
  map.set('key2', 2)
  expect(dummy).toBe(5)
  map.set('key1', 4)
  expect(dummy).toBe(6)
  map.delete('key1')
  expect(dummy).toBe(2)
  map.clear()
  expect(dummy).toBe(0)
})

the runner of effect actually binds itself to the map 's Symbol.iterator, the relationship of them is:

target
key
effect (dep)

map
Symbol(iterator)
for...of function

Before PR , when we use .set(K, V), the trigger goes like this:
// schedule runs for SET | ADD | DELETE
if (key !== void 0) {
  addRunners(effects, computedRunners, depsMap.get(key))
}
// also run for iteration key on ADD | DELETE
if (type === TriggerOpTypes.ADD || type === TriggerOpTypes.DELETE) {
  const iterationKey = isArray(target) ? 'length' : ITERATE_KEY
  addRunners(effects, computedRunners, depsMap.get(iterationKey))
}

Since it didn't have any effect as dependencies, depsMap.get(key) would get undefined, and it won't trigger the for...of function, but it should !
In conclusion, any iterable type object should seek for those deps of their Symbol(iterator) first when trigger !! If there's no reactive effect, would get undefined, addRunner will not add them, so we won't lost any effcient.
And if there are some dependencies of a key, just go and add them.
Result:
// schedule runs for SET | ADD | DELETE
const iterationKey = isArray(target) ? 'length' : ITERATE_KEY
const iterationEffect = depsMap.get(iterationKey)
addRunners(effects, computedRunners, iterationEffect)

if (key !== void 0 && depsMap.get(key) !== iterationEffect) {
  addRunners(effects, computedRunners, depsMap.get(key))
}

I'm still in my third year of college, this PR may not be correct too, if there are any mistake that I made, would you please give me some advice ?
Thanks for your awesome work of Vue 3.0 !

As the issue #709 said, befor PR Iterating a Map only tracks addition/removal. Modifications of map contents don't run effect, resulting in unexpected, stale values.
But for the belowing:

When enumerating entries or values on a Map, next should call track on the key before returning the results, as it's effectively a read on the entry value.

Catching and tracking the key seems to be unprocurable in createIterableMethod  ...

For Optimization
I also found @jods4 give an suggestion of optimization for full traverse in issue #673
I think we found a way for that in my PR solution, because every time we wanna traverse all the array ( Map , Set as well ), whatever we use traditional for loop, .forEach method, we would definitely use the ITERATE_KEY, and track it.
so I gave a condition judge in the if brach:
if (
  key !== void 0 &&
  depsMap.get(key) &&
  depsMap.get(key) !== iterationEffect
) {
  addRunners(effects, computedRunners, depsMap.get(key))
}

If the reactive effect runner of a key is actually the same as ITERATE_KEY, so we don't need to add it to trigger runners at all !!
in my new two test case, I used VSCode Debugger for Jest, it showed that we collect this effect runner for many times... it is unnecessary as far as I'm concerned.

I can make it look as bad as I want since track allocates in O(n) and my proposal in O(1) (for ideal pattern that fit a full iteration, random access is still bad).

I am thinking about if this goal has already achieved, but I do not have any experience of Vue's benchmark 🤣

From here... https://github.com/vuejs/vue-next/blob/master/packages/reactivity/src/effect.ts#L197
Although in addRunners we have a if brach to judge whether effectsToAdd is void 0, but for a huge array or collection, trying not go into another function is better for performance,
I'm thinking about xxx && addRunners(...) is cheaper than that.

Thanks for your effort, but I don't think the fix is on the right track... see e1c9153
We should only add a case for Map.set. There are cases where the iterate effect should not be triggered - e.g. when the target can be an Array or a WeakMap.
Also, addRunners dedupes the effects using Sets so there's no need for the if check. This is also not related to #673.

Ah... seems like I was over thinking about this case ... 🤣 my first commit was just right ...


Improve og description

These are changes intended to fix issue #158

Question:
Is there any reason for extracting the description from the content instead of having some kind of configuration for it?
For example: For authors, the description is defined in the bio prop of the author.
I think that we can give users more control over what they want the description to be if it's defined explicitly. For example, using gray_matter provides a way to define metadata inside the md file.
What do you think?

Also, I think we need to exclude the links from the description extraction. Taking your "bio" as an example, in the current implementation the description ends up containing the "Github" word (from your github link) but I don't think that makes sense in the description.

The main reason why we extract the description from markdown is I hope to keep zine as simple as possible. The less property the better for the user. Maybe we can add an optional property to allow customizing the description?
[[article]]
summary = "article summary"

Also good to know the gray_matter crate, I had considered using the front matter to replace the issue's zine.toml, maybe it should add to the plan.

Roger that.

Also, I think we need to exclude the links from the description extraction. Taking your "bio" as an example, in the current implementation the description ends up containing the "Github" word (from your github link) but I don't think that makes sense in the description.

We can't exclude all links from the description, for example, Rust Search Extension in my bio is key info. I think the GitHub link in my bio is just a corner case, so we needn't put much attention to it.


Update logback-classic, logback-core to 1.5.11

About this PR
📦 Updates

ch.qos.logback:logback-classic
ch.qos.logback:logback-core

from 1.5.10 to 1.5.11
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 = "ch.qos.logback" } ]

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequests = { frequency = "30 days" },
  dependency = { groupId = "ch.qos.logback" }
}]

labels: test-library-update, early-semver-patch, semver-spec-patch, commit-count:1

Superseded by #149.


[bug]: max-commit-fee-rate-anchors ignored at force close, much higher fee used.

Background
Regarding the outstanding issue that will be fixed by https://github.com/lightningnetwork/lnd/pull/8096 still waiting to be merged, I finally received a FC by WOS, I was the opener.
Only it was published at 589sat/vB while my max-commit-fee-rate-anchors was set to 25.
Your environment

version of lnd0.17.3
which operating system (uname -a on *Nix) debian
version of btcd, bitcoind, or other backend bitcoind
any other relevant environment details

Steps to reproduce
Have channel with WOS, meet above bug, set sane limit for FC fee rate, see it completely ignored when tx is published at almost 24x the set value, overpaying 2x.
Expected behaviour
FC is published at desired max fee.
Actual behaviour
FC makes you pay 100$ in fees.

Closing as "possibly mistaken". Ziggie checked the code for me and their opinion is that this couldn't possibly happen unless I did have that value set to a higher fee rate.
While I had it set high before as a matter of fact, I am fairly sure I decreased it after an ugly expensive FC I got a week ago.
WOS went offline for me after that.
But as I cannot, past any doubt, confirm that I in fact had it lowered in time for WOS to take it up, I am going to terminate the issue for now.

Ziggie suggested I reopen the issue :stuck_out_tongue:
In case someone can check the code with another pair of eyes.
So to sum it up, I had max-commit-fee-rate-anchors set to 1000 once. I got a couple of very ugly FCs, so I lowered it.
I have no means to prove that I had lowered it in time for an update to be sent to WOS, so my standing is less than rock solid.

The give some background: LND will initiate a feeupdate msg in a timeperiod between 10min and 1h (randomly choosen) after the change of the lnd setting happened. Then for anchor channels we limit the feerate either to the max-commit-fee-rate-anchors when smaller than  minrelayfee, the minrelayfee if its bigger than the cap, or the maxAmount we have on the channel when this amount is still smaller than the minrelay fee.
Here poured into code:
https://github.com/lightningnetwork/lnd/blob/master/lnwallet/channel.go#L8477-L8526

So a user set the max fee rate to 1000 sat/byte, there was a fee rate spike, causing the commit fee rate to go up to 500 sat/byte, then a force closer happened?
Was the value lowered before the fee rate? The value only really needs to be set to a value high enough to widely propagate across the network. In times like this 100, should give a lot of breathing room.
We have some changes planned where the user won't really need to set this value, and we'll dynamically set it based on our own mempool, and the feefilter value of our peers.

You can search for this in your logs to see when the last fee update happened: updating commit fee

Made this issue re that feefilter comment above: https://github.com/lightningnetwork/lnd/issues/8302

Was the value lowered before the fee rate?

This I believe was the case, but I am not able to prove it.
The most recent entry of updating commit fee for WOS chanpoint is updating commit fee to 145019 sat/kw which is lower than 589sat/vB...


Remove check for browserstack in travis config.

This change is

Review status: 0 of 1 files reviewed at latest revision, all discussions resolved, some commit checks failed.

Comments from Reviewable

Closing since it's outdated.


Jax refactor

Hi Rob,
Here is a pull request to use Jax instead of numba for compilation.
On 40k points, we have

6.53 ms per loop with Jax
38.9 ms with Numba
8.18 s with base numpy

So that I think it is worth the upgrade to Jax.
(I meant to submit this to Katelyn first - ignore for now)
Cheers,
Ben

Accidentally sent this to Rob not Katelyn - ignore for now.


Cannot read properties of undefined (reading 'value') in handleFormSubmit with no value set to submit button

Hi, I found that the following error occurs when handleFormSubmit is executed on form submit.
Uncaught (in promise) TypeError: Cannot read properties of undefined (reading 'value')
    at handleSubmit (handleFormSubmit.js:20:61)

When this error occurred, I tried to process the registration by setting registration as the second argument to handleFormSubmit. I did not have a type field on the form, and I did not set a value on the submit button.
Is this correct usage?
Under this situation, This error seems to occur when evaluating target.type.value in the following line of source code.
https://github.com/alexanderson1993/remix-auth-webauthn/blob/main/src/handleFormSubmit.tsx#L45
Thanks for developing such a great package. This save me a lot of time to implement passkey login to my Remix Stack!

Thanks for submitting this issue. It should be fixed in 0.0.9.


traverse error?

OrientDB Version: 3.0-develop
Java Version: 1.8
OS: CentOS
One of my data has two out edge as below:

But if I traverse starting from it, I get below graph:

As my understanding, it should look like below:
#157:645786<-invest-#186:57556-invest->#141:350412

Hi @weickdev
I just tried it with latest snapshot and it seems to work fine, could you please a sample SQL script to reproduce the problem?
Thanks
Luigi

Do you mean you need the sql I run? It is as below:
traverse * from #xxxx:xxxx maxdepth 1, but all the datas are 100+GB. By the way, I package the zip on develop brach, is this matter?

What I need is a small dataset to reproduce the problem, if you could isolate a small portion (or create a new one that has this problem) it would be awesome
Thanks
Luigi

I try to create a new small dataset, but the small dataset works well. I can't make sure which part of datas cause this issue.

I try this on V2.2.28, it has same issue!

Hi @luigidellaquila Is there any feedback about this issue? Or anything I can do?

Hi @weickdev
It's really hard for me to understand where the problem is, with my datasets this does not happen and you say it doesn't happen with your sample dataset either, so it seems the problem is in the original dataset...
Could you please post the result of the following query:
SELECT FROM [#157:645786, #186:57556, #141:350412]

maybe we will find something there
Thanks
Luigi

Hi @luigidellaquila
The select result seems ok:
+----+---------+-------+----+--------+--------+---------+---------+---------+---------+---------+---------+---------+---------+--------------+------------------+-------------------------------------+
|#   |@RID     |@CLASS |city|province|industry|capital  |entity_ty|name     |business_|enterpris|utime    |ctime    |operation|_key          |in_invest         |out_invest                           |
+----+---------+-------+----+--------+--------+---------+---------+---------+---------+---------+---------+---------+---------+--------------+------------------+-------------------------------------+
|0   |#157:6...|Company|北京  |北京      |商务服务业   |100000...|Company  |xxxxxx...|存续（在营、...|其他有限责任公司 |2017-0...|2017-0...|1999-0...|793BD62EDC6...|[#219:289714,#2...|[#245:171381,#216:225630,#237:1714...|
|1   |#186:5...|Person |    |        |        |         |Person   |xxxxxx      |         |         |2017-0...|2017-0...|         |042151FAC7D...|                  |[#219:289714,#229:289804]            |
|2   |#141:3...|Company|广西桂林|广西      |有色金属矿采选业|100000...|Company  |xxxxxx...|存续（在营、...|有限责任公司...|2017-0...|2017-0...|2015-0...|41C7B74F4C7...|[#245:289784,#2...|                                     |
+----+---------+-------+----+--------+--------+---------+---------+---------+---------+---------+---------+---------+---------+--------------+------------------+-------------------------------------+

`xxxxxx``` is the name of the Company/Person.

Hi @weickdev
From this result I cannot see if the edge (#186:57556) is contained in the out_/in_invest fields of both vertices. Could you please check it?
Thanks
Luigi

I can't check it, it throws timeout error as below:
orientdb {db=dev}> select bothE('invest') from #157:645786

Error: com.orientechnologies.common.io.OIOException: Read timed out

Error: java.net.SocketTimeoutException: Read timed out

@luigidellaquila
I try the web studio again, it works well. As you guess, there is some mistake:

yes, I'd say your graph is "broken".
You can easily repair it with
UPDATE #141:350412 ADD out_<TheEdgeClassName> = #186:57557
just make sure to spell out_TheEdgeClassName in the right case.
This could have happened for many reasons, a good candidate is a bug we fixed in latest stable release
Thanks
Luigi

@luigidellaquila I close the transaction when I insert edges, does this may cause this issue?

I doubt, connection close just does a commit if you are running in a transaction, otherwise it just closes.
BTW, are you running in a tx? How are you inserting data?
Thanks
Luigi

@luigidellaquila
No, I am running without tx, I insert data by 'OrientGraphNoTx', and set the OIntentMassiveInsert.

Uhm... ok, as I wrote before, we fixed a bug about this in 2.2.29, I'd say that can be the reason for this problem.
In general, I suggest you to use transactional connections when manipulating graphs, they have better performance and are more consistent
Thanks
Luigi

@luigidellaquila
Because I have massive edges to insert, but the insert speed is too slow. I find some blogs said without tx and setting the  OIntentMassiveInsert will be faster. So I remve the tx. Do you have some advice about inserting massive edges?
BTW, will you fix this issue in 3.x?

Hi @weickdev
The best advice I can give you for a massive insert is to work in embedded mode (ie. plocal). The massive insert intent does not give much advantage with graph import, as the big part of the elaboration is vertex lookup and save.
The issue should be already fixed.
Thanks
Luigi

Hi @luigidellaquila
Right now, I am using plocal storage, connecting the database by DB address remote:localhost/mydb. So the client and the db server are on the same server. As you said, should I change the DB address to plocal:xxxxx?

If it's a one-shot batch import, then yes, using plocal:xxx will give you a big advantage.
Just consider that you cannot run both a plocal process and a server at the same time, so you have to stop the server, run the import and then restart it
Thanks
Luigi

@luigidellaquila Thanks for you advice, I will try it!


[BUG] Not prompted for credentials in Windows Terminal session

When using userpass authentication in a Windows terminal noticed that the prompt for username/password is not provided. This is not the case in PowerShell7 or PowerShell 5.1

Related to CLM


Remove default geopoint hint

Steps to Reproduce
…add geopoint question to form but dont add any hint
…preview form in Enketo
…

Expected behavior
no hint
Actual behavior
see default hint "GPS coordinates can only be collected when outside."
Additional details
Always displaying a default hint is not really appropriate, and indeed this particular hint is not even correct (it is quite possible to get a GPS fix inside a house or building)
I cant find anything in the actual code to remove this using a PR. I suspect the hint is getting copied out of one of the template spreadsheets (base.xls or all.xls) and used to initialize geopoint hint in any new form definition otherwise lacking a corresponding user-defined hint.
In general, I dont believe the pyxfom tool should be adding any new semantic content into a form (even if well intentioned...). If the form writer wants a suitable hint in their form then it is their responsibility to explicitly define one. And if they dont want a hint then it should be possible not to have one [sic].

This is no longer an issue in Pyxform.
It was addressed in this PR #67


connection refused when docker daemon is secured

I have secured my docker daemon like suggested by docker: https://docs.docker.com/articles/https/ The nginx-proxy stopped working and outputs:
dockergen.1 | 2015/03/04 13:48:01 error listing containers: dial unix /tmp/docker.sock: connection refused
dockergen.1 | 2015/03/04 13:48:01 Unable to ping docker daemaon: dial unix /tmp/docker.sock: connection refused

How can I run nginx-proxy with a secured daemon?

You'll need to start your Docker daemon with both a TLS socket and a Unix socket.
How are you starting your Docker daemon?

I run docker via systemd. In /etc/default/docker I have configured docker like this:
DOCKER_OPTS='--tlsverify --tlscacert=/etc/docker/ca.pem --tlscert=/etc/docker/server-cert.pem --tlskey=/etc/docker/server-key.pem -H=<IP_ADDRESS>:2376'

After that nginx proxy stopped working. @md5 any ideas?

When you switched to TLS, you removed the unix domain socket that nginx-proxy uses to connect to docker.  nginx-proxy does not currently support TLS although you should be able to get it to work by mounting in your docker key/cert and starting docker-gen w/ the -tls* flags.  If you don't do that, you'll have to add back the -H unix:///var/run/docker.sock to your DOCKER_OPTS

:100:

@jwilder any plans on supporting tls? So I need to create separate containers, one for nginx and one for docker gen?

@ArtworkAD No immediate plan but I added #114.

@ArtworkAD What's wrong with doing as @jwilder suggested an having Docker listen on both TLS and a Unix socket?

FWIW, that's how Docker Machine configures the Docker daemons it provisions.

How can I configure this?

Am 04.03.2015 um 22:27 schrieb Mike Dillon<EMAIL_ADDRESS>@ArtworkAD What's wrong with doing as @jwilder suggested an having Docker listen on both TLS and a Unix socket?
—
Reply to this email directly or view it on GitHub.

DOCKER_OPTS='--tlsverify --tlscacert=/etc/docker/ca.pem --tlscert=/etc/docker/server-cert.pem --tlskey=/etc/docker/server-key.pem -H=tcp://<IP_ADDRESS>:2376 -H unix:///var/run/docker.sock'

@md5 this works, thank you.

Any hints on where to configure this in CoreOS?

@vallard take a look here: https://coreos.com/docs/launching-containers/building/customizing-docker/

@md5, thanks!  Funny, I was over there as well trying that out.  I still didn't have success but what I did do was this:
sudo cp /usr/lib/systemd/system/docker.service /etc/systemd/system/
sudo vim /etc/systemd/system/docker.service

Changed the relevant line to be:
ExecStart=/usr/lib/coreos/dockerd --daemon --host=fd:// -H=tcp://<IP_ADDRESS>:2376 -H unix:///var/run/docker.sock $DOCKER_OPTS $DOCKER_OPT_BIP $DOCKER_OPT_MTU $DOCKER_OPT_IPMASQ

Then:
systemctl enable docker.service
sudo systemctl daemon-reload
sudo systemctl restart docker

I still got the same error, but maybe this will help someone get on the right track or have them correct me via Cunningham's Law


CCI: DevConfig task -- Custom buttons to override underlying packaged versions

Includes custom buttons that a dev can simply add to their page layouts to work around the issue with buttons from the underlying managed packages have npsp__ hardcoded in the URL. All the new buttons start with [NPSP] so they stand out.
Critical Changes
Changes
Issues Closed
New Metadata
Deleted Metadata

Curious as to why these are being added to the config folder, shouldn't they live in dev_config/src_qa vs the config folder?

@jjbennett we renamed dev_config/src to config/dev with the idea that it can hold additional sets of unpackaged config metadata that aren't necessarily meant for a dev org (there's already QA config, some config that can be optionally installed with another task, etc...). Did we miss something else that the config folder was already used for though? We saw it in .gitignore but weren't sure what that was from.

I'm thinking it's from sublime or mavensmate maybe?

@jjbennett oh shoot, yeah it's mavensmate. That's not very nice of it to claim that name instead of, say, a mavensmate folder. Okay, I guess we'll have to rename it back to something else.

@jjbennett Jason says that Mavensmate is no longer maintained. Do you think it's okay if we leave the move from dev_config to config in place?

I am no longer using MavensMate but I believe @RadSFDeveloper does, will this cause issues if we continue to use MM or do we just need to add specific ignores or?

Hmm, I would guess it might cause issues if someone is still using Mavensmate. @RadSFDeveloper could you do me a favor and make a backup copy of your config directory, then update Cumulus to latest master and see what it does to your config directory?

The MavensMate plugin is not even supported by the developer at this point. Seems to me that we probably need to just drop support for it entirely.
That noted though, config is a pretty generic folder that could be used by some other ide down the road. I would prefer to go back to dev_config or something that will never stand a chance of conflicting with a valid local folder.

@force2b I'm not too worried about that, but I want to avoid putting "dev" in the name because there are use cases for unpackaged metadata besides just configuring orgs for developers. Maybe we should move these sets of metadata into the unpackaged folder (just not in pre or post which are looked for specially by the installer).

Hmm how about unpackaged/config?

unpackaged/config works for me.

@jjbennett Ok. I moved the new buttons into the deploy_qa_config task folder.

@force2b - this is saying the branch is out of date with master, can you check into it?

@jjbennett probably because https://github.com/SalesforceFoundation/Cumulus/commit/4f8908aae8588bccf148393480b6d6995b5f0dd4 was merged but the build hasn't gotten to the point of automerging back to feature branches yet.


Cannot load the sidebar on fresh install

Hello,
I'm new to docusaurus so maybe this is obvious but on a fresh install I'm getting this error while trying to load
Error: Bad sidebars file.
These sidebar document ids do not exist:
- swapi/schema,

Available document ids=
- swapi
- swapi/directives/deprecated
- swapi/directives/include
- swapi/directives/skip
- swapi/directives/specified-by
- swapi/enums/account-billing-types
...

Any pointers?

Fixed it by manually creating the file. Not sure if that's expected?

Fixed it by manually creating the file. Not sure if that's expected?

@djpate - There a small hack you can add to your sidebars.js to make it more resilient:
const apiSidebar = path.resolve(__dirname, `../api/sidebar-schema.js`); // adjust path here

let api = [];
try {
  api = require(apiSidebar);
} catch (err) {
  console.warn(`Warning: Missing sidebar file "${apiSidebar}"`);
}

Fixed it by manually creating the file. Not sure if that's expected?

Sidebar should be generated automatically. But sometimes you have to run the command twice.


Implement gfxprint

This commit implements the entirety of gfxprint. Special thanks to zeldaret for their version of gfxprint. All functions are 100% matching. Needs -char unsigned flag during compilation. Also, gfxprint.c has an include for vaprintf which is defined in libultra/aprintf.h which is not yet added.

Looks great, thank you :)


SimonBaey

I want to join

Welcome to OpenAOD, I will be sending a invite very soon. If you have any query or want to start contributing to our organization please feel free to message me on our Discord server (https://discord.gg/RGPPrwSZ). Cheers


Complete italian translation

Hello my fellow Rustaceans.
I have made the effort to translate the entire Rust website to italian.
The translation of the Rust website is complete except for

[ ] 50% of the FAQ page (will be submitted later in another pull request)
[ ] The alphabetical ordering of countries in Rust's user group

This is my first contribution ever to an open source project so please be kind

Thanks for the pull request, and welcome! The Rust team is excited to review your changes, and you should hear from @aturon (or someone else) soon.
If any changes to this PR are deemed necessary, please add them as extra commits. This ensures that the reviewer can see what has changed since they last reviewed the code. Due to the way GitHub handles out-of-date commits, this should also make it reasonably obvious what issues have or haven't been addressed. Large or tricky changes may require several passes of review and changes.
Please see the contribution instructions for more information.

This is my first contribution ever to an open source project so please be kind

Looks great to me so far! However, due to some other changes, you'll need to rebase this before we can merge. I can absolutely help you with that if you need any.

Thanks @steveklabnik I should now have managed to get the branch to merge cleanly.

Great! Do you want me to merge this as-is, or do you have more work to do? You mentioned that you wanted to do at least one part in another PR...

Thanks for your help @steveklabnik, as I stated beforehand I would like to terminate the translation of the FAQ page before finally being merged, I will update this pull request with the final details probably around 20 CEST of the 12 of Jan because tomorrow I am attending two exams so I will probably be busy.
In the meanwhile I will ensure that the automatic merge can be performed without conflicts with the base branch and directly state its status of completeness in another comment.
After declaring the PR as ready you can be free to merge it as soon as you want.
After that I might try to still get involved into getting the Italian translation synced with the upstream en-US one.
Let's keep in touch for later, and thanks for your help!

I am attending two exams so I will probably be busy.

That's super okay, thank you so much for the work so far, and good luck on your exams! Just let me know when this is ready to ship 😄

Ok, sorry for the delay, now the translation is complete, including the FAQ page

Merged! Thanks 😄


Dome U Pro - Switch / Sensor for Face Detection

Hello,
would it be possible to provide a switch and sensor for face detection supported by the Dome U Pro? (also via MQTT)
Thank you

My cam doesn't support face detection and I can't develop it at the moment.

My cam doesn't support face detection and I can't develop it at the moment.

If you want I can volunteer for tests :-)
I'm at your service!
Thanks anyway

I need to know if the app sends a message to the cam when you toggle the switches on/off.
Use ipc_sniff
https://github.com/roleoroleo/yi-hack-Allwinner-v2/issues/168#issuecomment-862667876
Run it manually and check if you can see a numeric code when you toggle the switch.

I need to know if the app sends a message to the cam when you toggle the switches on/off.
Use ipc_sniff
#168 (comment)
Run it manually and check if you can see a numeric code when you toggle the switch.

Sorry, how do you use ipc_sniff? Where should I run it from?

You can copy it to your sd card /tmp/sd using ftp after decompressing it.
Then login with ssh and run it manually /tmp/sd/ipc_sniff

Hi @roleoroleo
I copied the ipc_sniff file to the microSD (via USB), creating the tmp / sd folder, but when I try to start ipc_sniff via the mac terminal, it can't find the file.
Where am I wrong?

@SmartM-ui

@SmartM-ui

@SmartM-ui
The "tmp" folder is only available if the cam is running.
If you copy it via usb, you can place ipc_sniff into the root of your sd-card.
Than with ssh you can find the file here: /tmp/sd/ipc_sniff

Hi,
I put the file directly into the microSD root, but when I launch it with / tmp / sd / ipc_sniff, it reports "Segmentation fault".
For info, I have formatted the microSD directly from the cam, the macbook does not read it and the partition with Windows detects that there is an error in the microSD, but I can still use it and write. I have tried several microSDs and they all have the same behavior.
PS can you recommend a free FTP software for MacOS?

it reports "Segmentation fault".

Then try the following:

killall ipc_multiplexer
/tmp/sd/yi-hack/bin/ipc_multiplexer &

Than toggle the app settings how roleoroleo has described.
When you are done you should restart the camera.

formatted the microSD directly from the cam

Maybe because the cam is formating at sector 2. My linux machine has no problems with it.

FTP software for MacOS?

I don't have a mac but I like filezilla and it is also available for mac. (filezilla-project.org)

it reports "Segmentation fault".

Then try the following:
1. `killall ipc_multiplexer`

2. `/tmp/sd/yi-hack/bin/ipc_multiplexer &`

Than toggle the app settings how roleoroleo has described.
When you are done you should restart the camera.

formatted the microSD directly from the cam

Maybe because the cam is formating at sector 2. My linux machine has no problems with it.

FTP software for MacOS?

I don't have a mac but I like filezilla and it is also available for mac. (filezilla-project.org)

Perfect,
it worked! After I try to check the settings and bring them back to Roleoroleo

Hi @roleoroleo
this is the data that is detected when I press the Home and Not_Home button from the YIhome app

Not_Home:
IPC message. Len: 20. Status: No error information!
Parsing message.
01 00 00 00 04 00 00 00 8e 00 01 00 04 00 00 00 00 dd 6d 00
Home:
IPC message. Len: 20. Status: No error information!
Parsing message.
01 00 00 00 04 00 00 00 8e 00 01 00 04 00 00 00 00 dd 6d 00
I hope it can be used for the switch and synchronization with Home Assistant

Hi @roleoroleo
this is the data that is detected when I press the face detection from the YIhome app:
Face detect ON
IPC message. Len: 20. Status: No error information!
Parsing message.
01 00 00 00 08 00 00 00 3d 10 01 00 04 00 00 00 01 00 00 00
Face detect OFF
IPC message. Len: 20. Status: No error information!
Parsing message.
01 00 00 00 08 00 00 00 3d 10 01 00 04 00 00 00 00 00 00 00

Ok, now try to send these messages.
1 - Save the binary code (20 bytes) into a file (use hxd if you are a windows user).
2 - Use the command ipc_cmd -x file.bin
3 - Refresh the app and check if the switch is changed.

Hi,
this code turns face detection on and off from the YIhome app
Face detect ON
01 00 00 00 08 00 00 00 3d 10 01 00 04 00 00 00 01 00 00 00
Face detect OFF
01 00 00 00 08 00 00 00 3d 10 01 00 04 00 00 00 00 00 00 00

https://github.com/roleoroleo/yi-hack-Allwinner-v2/commit/ccea78899b1e781771222a0975f9cf3fcfcb6593

Hi @roleoroleo
the Face Detection sensor, after the firmware update to version 0.1.9, manages to perfectly enable the sensor on the official YIHome app.
You are GREAT!
Would it be possible to implement the motion tracking switch as you did for the other sensors via MQTT?

Would it be possible to implement the motion tracking switch as you did for the other sensors via MQTT?

I didn't implement the advertise part. It was a contribution from EnricoFerro.
Do you want to try to make a pr?

Would it be possible to implement the motion tracking switch as you did for the other sensors via MQTT?

I didn't implement the advertise part. It was a contribution from EnricoFerro.
Do you want to try to make a pr?

If you show me how to do it, gladly!
We can also ask @EnricoFerro for support?


Fix create DNS script for cname records

Cname records in the relenv deploy script failed to create and had to be done manually

Script fixed, will test when new version of SAPIG is released


UI-X crashs after trying to change the color

UI-X crashs after trying to change the color (in the config-ui-x plugin setting)
Fails to load any menu

installed (default image) on Docker on Synology DS716+II
Secure Mode
restart of container doesn't help
had to delete the Homebridge folder (sub folder from docker in file browser) and reinstall Homebridge

Hi @t6a,
Does this happen every time?


[SPARK-40929] Add Apache Spark 3.3.1 Dockerfiles

What changes were proposed in this pull request?
Add Apache Spark 3.3.1 Dockerfiles.

Add 3.3.1 GPG key
Add .github/workflows/build_3.3.1.yaml
./add-dockerfiles.sh 3.3.1

Why are the changes needed?
Apache Spark 3.3.1 released.
https://lists.apache.org/thread/7x5s8fpg16jvlm4cng5kvfk3njhwd0zh
Does this PR introduce any user-facing change?
Yes in future, new image will publised in future
How was this patch tested?
Add workflow and CI passed

BTW, the 3.3.1 dockerfiles won't be included in the intilial version of official image first to reduce the first version review complex.
But will be quick to update once initial version approved.

cc @wangyum @HyukjinKwon @zhengruifeng

Merge to master.

@HyukjinKwon @wangyum Thanks!


Fixed failing patching tests

The yield function in the lunatic module was recently renamed to yield_,
but the patching tests still expected yield in the patched modules.

The last commits touched many parts of the code base and I must have missed this. Thanks @imor for the fix!


Fix (Issue #56,#57,#58) : refactoring relation of UWP.

Move UWP project to new project's Kinugasa.Uwp.sln
Create new directory for UWP projects.

Relate to #56 #57 #58


feat: add content assistance

Description
This is a preliminar version for the following functionality:

Add SmartPaste functionality to editor
Add Snippets to VSCode for Content Assistance

Related issue(s)
Implements #132 #133

tests are failing because of issues with dependencies installation, related to package-lock v1 vs. v2 issues
problem with fsevents that are needed for chokidar that is needed by mocha. Maybe we can just remove mocha as we anyway do not have tests?
npm info it worked if it ends with ok
npm verb cli [
npm verb cli   '/opt/hostedtoolcache/node/14.20.1/x64/bin/node',
npm verb cli   '/opt/hostedtoolcache/node/14.20.1/x64/bin/npm',
npm verb cli   'install',
npm verb cli   '--loglevel',
npm verb cli   'verbose'
npm verb cli ]
npm info using<EMAIL_ADDRESS>npm info using<EMAIL_ADDRESS>npm verb npm-session 0fe29d83cbeee9d4
npm info lifecycle<EMAIL_ADDRESS><EMAIL_ADDRESS>npm timing stage:loadCurrentTree Completed in 12ms
npm timing stage:loadIdealTree:cloneCurrentTree Completed in 1ms
npm WARN read-shrinkwrap This version of npm is compatible with lockfileVersion@1, but package-lock.json was generated for lockfileVersion@2. I'll try to do my best with it!
npm timing stage:loadIdealTree:loadShrinkwrap Completed in [5](https://github.com/asyncapi/vs-asyncapi-preview/actions/runs/3273141816/jobs/5384988824#step:7:6)03ms
npm http fetch GET 200 https://registry.npmjs.org/fsevents 108ms
npm http fetch GET 200 https://registry.npmjs.org/fsevents/-/fsevents-2.3.2.tgz 38ms
npm timing stage:rollbackFailedOptional Completed in 1ms
npm timing stage:runTopLevelLifecycles Completed in 10[6](https://github.com/asyncapi/vs-asyncapi-preview/actions/runs/3273141816/jobs/5384988824#step:7:7)0ms
npm verb stack Error: Unsupported platform for<EMAIL_ADDRESS>wanted {"name":"fsevents","version":"2.3.2","engines":{"node":"^8.16.0 || ^10.6.0 || >=11.0.0"},"os":["darwin"],"dependencies":{},"optionalDependencies":{},"peerDependenciesMeta":{},"devDependencies":{"node-gyp":"^6.1.0"},"bundleDependencies":false,"peerDependencies":{},"deprecated":false,"_resolved":"https://registry.npmjs.org/fsevents/-/fsevents-2.3.2.tgz","_integrity":"sha512-xiqMQR4xAeHTuB9uWm+fFRcIOgKBMiOBP+eXiyT[7](https://github.com/asyncapi/vs-asyncapi-preview/actions/runs/3273141816/jobs/5384988824#step:7:8)jsgVCq1bkVygt00oASowB7EdtpOHaaPgKt[8](https://github.com/asyncapi/vs-asyncapi-preview/actions/runs/3273141816/jobs/5384988824#step:7:9)12P[9](https://github.com/asyncapi/vs-asyncapi-preview/actions/runs/3273141816/jobs/5384988824#step:7:10)ab+DDKA==","_shasum":"8a526f78b8fdf4623b709e0b975c52c24c02fd1a","_shrinkwrap":null,"_id":"fsevents@2.3.2","_from":"fsevents@~2.3.2","_requested":{"type":"range","registry":true,"raw":"fsevents@~2.3.2","name":"fsevents","escapedName":"fsevents","rawSpec":"~2.3.2","saveSpec":null,"fetchSpec":"~2.3.2"},"_spec":"fsevents@~2.3.2","_where":"/home/runner/work/vs-asyncapi-preview/vs-asyncapi-preview/node_modules/chokidar"} (current: {"os":"linux","cpu":"x64"})
npm verb stack     at checkPlatform (/opt/hostedtoolcache/node/14.20.1/x64/lib/node_modules/npm/node_modules/npm-install-checks/index.js:46:14)
npm verb stack     at thenWarnEngineIssues (/opt/hostedtoolcache/node/14.20.1/x64/lib/node_modules/npm/lib/install/validate-args.js:63:5)
npm verb stack     at /opt/hostedtoolcache/node/14.20.1/x64/lib/node_modules/npm/node_modules/iferr/iferr.js:3:64
npm verb stack     at checkEngine (/opt/hostedtoolcache/node/14.20.1/x64/lib/node_modules/npm/node_modules/npm-install-checks/index.js:25:[10](https://github.com/asyncapi/vs-asyncapi-preview/actions/runs/3273141816/jobs/5384988824#step:7:11))
npm verb stack     at module.exports.isInstallable (/opt/hostedtoolcache/node/14.20.1/x64/lib/node_modules/npm/lib/install/validate-args.js:60:3)
npm verb stack     at resolveWithNewModule (/opt/hostedtoolcache/node/14.20.1/x64/lib/node_modules/npm/lib/install/deps.js:677:10)
npm verb stack     at /opt/hostedtoolcache/node/14.20.1/x64/lib/node_modules/npm/lib/install/deps.js:600:7
npm verb stack     at /opt/hostedtoolcache/node/14.20.1/x64/lib/node_modules/npm/node_modules/iferr/iferr.js:3:64
npm verb stack     at /opt/hostedtoolcache/node/14.20.1/x64/lib/node_modules/npm/node_modules/call-limit/call-limit.js:28:43
npm verb stack     at processTicksAndRejections (internal/process/task_queues.js:77:[11](https://github.com/asyncapi/vs-asyncapi-preview/actions/runs/3273141816/jobs/5384988824#step:7:12))
npm verb pkgid<EMAIL_ADDRESS>npm verb cwd /home/runner/work/vs-asyncapi-preview/vs-asyncapi-preview
npm verb Linux 5.15.0-1020-azure
npm verb argv "/opt/hostedtoolcache/node/[14](https://github.com/asyncapi/vs-asyncapi-preview/actions/runs/3273141816/jobs/5384988824#step:7:15).20.1/x64/bin/node" "/opt/hostedtoolcache/node/14.20.1/x64/bin/npm" "install" "--loglevel" "verbose"
npm verb node v14.20.1
npm verb npm  v6.14.[17](https://github.com/asyncapi/vs-asyncapi-preview/actions/runs/3273141816/jobs/5384988824#step:7:18)
npm ERR! code EBADPLATFORM
npm ERR! notsup Unsupported platform for<EMAIL_ADDRESS>wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})
npm ERR! notsup Valid OS:    darwin
npm ERR! notsup Valid Arch:  any
npm ERR! notsup Actual OS:   linux
npm ERR! notsup Actual Arch: x64
npm verb exit [ 1, true ]
npm timing npm Completed in 2826ms

npm ERR! A complete log of this run can be found in:
npm ERR!     /home/runner/.npm/_logs/2022-10-[18](https://github.com/asyncapi/vs-asyncapi-preview/actions/runs/3273141816/jobs/5384988824#step:7:19)T11_50_[23](https://github.com/asyncapi/vs-asyncapi-preview/actions/runs/3273141816/jobs/5384988824#step:7:24)_562Z-debug.log

for some reason just adding genson-js which is in charge of creating a jsonschema from a json example, messed with the fsevents dependency :/

/rtm


[OpenGL ES] Improve detection for non-zero base vertex support

DrawIndexed with a non-zero vertex offset can work just fine on my mobile device (Xiaomi Redmi 4X), even though GL_OES_draw_elements_base_vertex is not listed as a supported extension.
According to the docs, glDrawElementsBaseVertex is part of core GLES 3.2. As far as I understand, there is no need to check for any extensions if the device implements ES 3.2.
Proposed change:
-DrawElementsBaseVertex = GLVersion(3, 2)
+DrawElementsBaseVertex = GLVersion(3, 2) || GLESVersion(3, 2)
    || IsExtensionSupported("GL_ARB_draw_elements_base_vertex")
    || IsExtensionSupported("GL_OES_draw_elements_base_vertex");

Good catch. I have pushed a commit with this change.


Feature request

Not sure if already possible, but could not find it in the documentation.
I am trying to find a way to start the flow in a given step.
The idea is to automatically populate the fields with stored data on each step and advance until a given step.
The user will see only the given step without having to go through the previous ones.
Thanks

I found a way to do it by saving the data for each step on the $currentRequest and then saving the form and moving to the following step


Error when import PandasTools

Describe the bug
When I import PandasTools, I get the error message:
Failed to find the pandas get_adjustment() function to patch
Failed to patch pandas - PandasTools will have limited functionality

Then when I reproduce the gist https://gist.github.com/greglandrum/3b9da87a20e9b0d4827bbf1e64f68056 the molecule column isn't rendered:

Configuration (please complete the following information):

RDKit version: 2023.09.4 and 2023.09.5
OS: MacOS Ventura 14.3 and Ubuntu 22.04 under WSL2
Python version (if relevant): 3.12
Are you using conda? mamba
If you are using conda, which channel did you install the rdkit from? conda-forge
If you are not using conda: how did you install the RDKit? N/A

Additional context
The pandas version installed as part of the rdkit env is 2.2.0.

@DavidACosgrove Ouch, it looks like something has changed in the pandas module. I'll look into fixing it - thanks for reporting the problem.

Hi @ptosco,
I was having the same issue, so I took a look, found the problem, and submitted a PR that fixes it: #7165

@AAriam Thank you, just approved!
@DavidACosgrove could you please check that applying
https://patch-diff.githubusercontent.com/raw/rdkit/rdkit/pull/7165.diff
to your RDKit installation also fixes the problem at your end?
Thanks!

@ptosco @AAriam Yes, that's working for me.  Many thanks for the speedy resolution.

@AAriam Thank you, just approved! @DavidACosgrove could you please check that applying https://patch-diff.githubusercontent.com/raw/rdkit/rdkit/pull/7165.diff to your RDKit installation also fixes the problem at your end? Thanks!

Could you kindly explain how to go about this? I got a similar message as David. Thank you.

I tried the following code after applying the patch:
installed with conda
Pandas 2.2.1
rdkit 2023.09.5
import pandas as pd
from rdkit import Chem
from rdkit.Chem import PandasTools

smiles = ['c1ccccc1', 'c1ccccc1O', 'c1cc(O)ccc1O']
df = pd.DataFrame({'ID':['Benzene', 'Phenol', 'Hydroquinone'], 'SMILES':smiles})
df['Mol Image'] = [Chem.MolFromSmiles(s) for s in df['SMILES']]
PandasTools.SaveXlsxFromFrame(df, 'test.xlsx', molCol='Mol Image')

and got
AttributeError: module 'pandas.io.formats.format' has no attribute 'get_adjustment'
I believe there is still one part needing correction PandasPatcher.py:
def patchPandas():
...
  -> if getattr(pandas_formats.format, get_adjustment_name) != patched_get_adjustment:
  ->   setattr(pandas_formats.format, get_adjustment_name, patched_get_adjustment)
  #should be like this perhaps?
  if getattr(pandas_formats.printing, get_adjustment_name) != patched_get_adjustment:
    setattr(pandas_formats.printing, get_adjustment_name, patched_get_adjustment)
...

@martinj80 The fix will be available starting from 2023.09.6.
To get the current RDKit conda package to work you need to apply this patch to your current installation.
You can do that as follows:
$ curl -L https://patch-diff.githubusercontent.com/raw/rdkit/rdkit/pull/7165.diff -o /tmp/7165.diff
$ cd $CONDA_PREFIX/lib/python3.*/site-packages
$ [ -e rdkit/Chem/PandasPatcher.py ] && patch -p1 < /tmp/7165.diff

@ptosco
Thank you for the response.
I applied the patch file already, but for some reason it did not help 100% (before the error message was different though). Only after I modified the lines I pointed out in my post it worked without errors.

I also cannot get this to work

That's what I did in the end, and it works, pandas=2.1. Just wanted to add some weight to @martinj80's suggestion that applying the patch as outlined by @ptosco in https://github.com/rdkit/rdkit/issues/7159#issuecomment-1971637963 is not enough.

The problem is you have a new version Pandas that RDKit does not know how to patch(work with). Downgrade the pandas to a version that RDKit is familiar with or upgrade RDKit if greglandrum does something to RDKit. For example, my RDKit is '2023.09.5' and it does not work with version 2.2.2 of Pandas. So I downgrade Pandas to 2.0.0. (I use the trial-and-error method to know which version works)
pip install pandas==2.0.0

Hi all,
I face the error:
PandasTools.WriteSDF(pp, args.output_file, molColName='ID', properties=list(pp.columns))
  File "/scratch/micromamba/envs/biotools_py39/lib/python3.9/site-packages/rdkit/Chem/PandasTools.py", line 440, in WriteSDF
    mol = Chem.Mol(row[1][molColName])
RuntimeError: Bad pickle format: unexpected End-of-File while reading

I updated pandas == 2.0.0 but it still errored.
Please help me to solve it.
My code here:
pp = pd.read_csv(args.input_file)
PandasTools.AddMoleculeColumnToFrame(pp,'smiles')
pp["Mol_H"] = pp["ROMol"].apply(Chem.AddHs)
pp["Mol_H"].map(AllChem.EmbedMolecule)
pprint(pp)
PandasTools.WriteSDF(pp, args.output_file, molColName='ID', properties=list(pp.columns))

Change to PandasTools.WriteSDF(df, args.output_file, idName='AQID', properties=list(df.columns)) to fix this error.


BLAS for TropicalNumbers

We have an extensible BLAS library in Julia community.
https://github.com/YingboMa/MaBLAS.jl
It is useful in Tropical tensor networks:
https://arxiv.org/abs/2008.06888
Tropical BLAS will speed up solving combinatorial optimization problems with Tensor networks.

Implemented Here: https://github.com/TensorBFS/TropicalGEMM.jl


error running scripts/docs.sh

$ ./scripts/docs.sh
returns:
Generate documentation for packages
lerna info version 2.11.0
fs.js:948
binding.stat(pathModule._makeLong(path));
^
Error: ENOENT: no such file or directory, stat '/home/pwright/repos/aerogear/aerogear-js-sdk/packages/metrics-cordova/src'

@finp Valid procedure to start doing anything in this repository is to:
npm i
npm run bootstrap
npm run build

Then we can execute:
./scripts/docs.sh

Regards


Save the generated deployment manager template to GCS.

When forseti is initially deployed, it generates a deploy-forseti-timestamp.yaml deployment template in the installer's cloud shell (i.e. installer is the person).
If this deployment template is not saved outside the installer's cloud shell, no one else can use it to redeploy forseti, whether to update it to a new version or make tweaks.  So, it would be nice to save this deployment template to forseti's GCS bucket so that anyone can retrieve this and update to newer version.

Issue Review: Let's do this in Q4.


Create deploy-all scripts

To simplify deployment we need scripts for deploying all sites to production with latest version at the same time.

Looks good


Update args_asr.py

Codecov Report

Merging #138 into master will decrease coverage by 0.01%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master     #138      +/-   ##
==========================================
- Coverage   39.15%   39.13%   -0.02%
==========================================
  Files          84       84
  Lines       10060    10060
  Branches     2110     2110
==========================================
- Hits         3939     3937       -2
- Misses       5921     5922       +1
- Partials      200      201       +1

Impacted Files
Coverage Δ

neural_sp/bin/args_asr.py
0.00% <ø> (ø)

neural_sp/models/modules/cif.py
87.34% <0.00%> (-1.27%)
:arrow_down:

neural_sp/models/modules/mocha.py
83.59% <0.00%> (-0.53%)
:arrow_down:

...eural_sp/models/seq2seq/decoders/rnn_transducer.py
75.23% <0.00%> (+0.31%)
:arrow_up:

Continue to review full report at Codecov.

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


Remove vagrant from requires until it's in epel8

As for now 'tmt-all' cannot be installed on rhel-8 or centos-8 without
enabling the vagrant copr repository. Let's remove the requires until
vagrant is directly available in epel.

@lukaszachy, removed vagrant.py and base.py from the package.

I do not intend to build it in EPEL. It would be "unmaintanable". At least without significant effort (and time I do not have).
Can you change it to Recommends instead? So it actually gets pulled if available.

Also, could you actually create the conditional in RPM spec, instead of in Makefile? IMO it makes more sense to me.
%bcond_with vagrant

[ . . . ]

%if %{with vagrant}
Recommends: vagrant
%endif

[ . . . ]

%if %{without vagrant}
rm tmt/steps/provision/{base,vagrant}.py
%endif

So that way it can be triggered with different conditions even without changing the spec file? See --with for mock (I do not think koji supports it so far.)


Add ENV NVIDIA_DRIVER_CAPABILITIES=all to permit Video SDK transcoding, 3D rendering, and X11 OpenGL Display

https://github.com/NVIDIA/nvidia-container-runtime/issues/112
I'm interested in capabilities beyond the default Nvidia base images of just compute and utility. I'm particularly interested in using the video encoding and decoding functionality and OpenGL in an X11 application.

Hmm works locally on my WSL2 machine but not on replicate.com itself. Will need to continue investigating.

https://replicate.com/p/jokv5fbbljv3mu64k4eyyyqjli
Nope, got it working after all. Pretty pleased :) . I would like to bring this up for re-consideration.

Could there be some consideration of this? It is not possible to set this at runtime and get the same results as the Nvidia parts of the runtime will mount more files into the container if it sees these environment variables set. That is not something possible when the container is already running.

Hi @nelsonjchen sorry your PR went unnoticed. This seems like a sensible change to me, but do you have a sense of whether this change might break anything?
Wold you be willing to update this PR with docs about the purpose of this env var in https://github.com/replicate/cog/blob/main/docs/environment.md ?

Hi @nelsonjchen sorry your PR went unnoticed. This seems like a sensible change to me, but do you have a sense of whether this change might break anything?

My sense is that it does not, but I am also not a typical/normal/daily GPU user. However, I do defer to this comment by an Nvidia employee in the thread I linked on Nvidia's repo about this which was made about 3 years ago with a general approval for this kind of change:
https://github.com/NVIDIA/nvidia-container-runtime/issues/112#issuecomment-712312284

Wold you be willing to update this PR with docs about the purpose of this env var in https://github.com/replicate/cog/blob/main/docs/environment.md ?

I don't know. It's not really configurable which is unprecedented. The environment variables there are usually customizable. I suppose I could add a section of "interesting" environmental variables that can't be configured but might be of interest.

@zeke Documented. Not sure if that's what you're looking for.

Hey @nelsonjchen sorry there hasn't been much attention on this.
I think it'd be much less risky to ship this as an option than a new default. 👍🏼

Hey @nelsonjchen sorry there hasn't been much attention on this.
I think it'd be much less risky to ship this as an option than a new default. 👍🏼

OK, I'll see what I can do to propose it as an option.

I think I'm fine with this even without it being an option. Can you rebase on main please?

Rebased on main.


Redesign

looks more nerdy now -- I really like it

Wow, that is different! Not too sure if I like it. But we might go that way. Would you mind changing the background color slightly to increase readability?


[FEATURE] Usage with pyxl

Is your feature request related to a problem? Please describe.
Not really! But I do think a JSX-like syntax would be nice.
Describe the solution you'd like
Basically, integrate with pyxl4: https://github.com/pyxl4/pyxl4
Example code
Provide an example of how you imagine the feature working:
# coding: pyxl
from fasthtml_pyxl import *

page =
    <title>Some page</title>

            Some text,
            a link,

print(to_xml(page))

Similar implementations
None I can think of! (Except for the pyxl4 itself, and older versions of course)
Problem solved
N/A
Additional context
N/A
Confirmation
Please confirm the following:

[x] I have checked the existing issues and pull requests to ensure this feature hasn't been requested before.
[x] I have read the project's documentation to ensure this feature doesn't already exist.

That project is long dead, and I don't like all that extra typing myself - but you could make this an external project if you wanted; no need to put it in fasthtml itself afaict.


[Feature] support  pod crash debug

when a pod of doris crashes and does not restart successfully, we should exec the pod for manual debugging.
when a pod crashes, we can add an annotation selectdb.com.doris/runmode=debug, the next start of the pod should run in debug mode.  The pod will re-enter running status in the next restart. when you have finished debugging the service, you can delete the pod or cancel the annotation, the pod will run in normal mode at the next start.

https://github.com/selectdb/doris-operator/pull/42


Add Linux Desktop on your browser as option?

I'm very intrigued in the Jupyter Desktop Server referenced in the welcome page to the Jupyterhub service. I'm currently running a VPN+VNC combo to connect to a remote teaching server for a lab course. Something like this could make life a lot easier for my students. How do I make this happen?

I suppose that first you would need to install a vpn on xfce if xfce doesn't ship with it.  @yuvipanda is this correct?

@michaelmack it's actually already installed! Check out utoronto.2i2c.cloud/hub/user-redirect/desktop. You can also access it from under 'New' button in the default Jupyter Notebook view.
We can install pretty much any desktop application you want. I'll be very excited if you can use this in your class - will help us improve the service for everyone! Let us know what you would need, and we can talk about how to access them?
Currently everyone's memory limits are set for interactive python use, so maybe not big enough for desktop use fully yet. Can easily increase limits though.
@ntaback  jupyter-desktop-server already runs a VNC client, so nothing more would be needed really.

@michaelmack heya! Just wanted to see if you had any time to look at it. Would love some feedback, so it can be made usable for your students :)

@michaelmack heya! Just wanted to see if you had any time to look at it. Would love some feedback, so it can be made usable for your students :)


feat(VSelect): add VSelect

option element can't be styled via CSS.
ref: https://stackoverflow.com/questions/7208786/how-to-style-the-option-of-an-html-select-element


chore: bdd-spring-1575378746 to 0.0.1

chore: Promote bdd-spring-1575378746 to version 0.0.1

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approvers:
If they are not already assigned, you can assign the PR to them by writing /assign  in a comment when ready.
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment


Revert "Remove code that nobody understands the need for"

Reverts vespa-engine/vespa#15737
Seems to have broken a bunch of system tests.

Thanks


Add Google.Protobuf.Any.Codec module

This new module provides pack/1 and unpack/2 functions to manipulate google.protobuf.Any structs. This follows the equivalent Python API.
This PR depends on https://github.com/tony612/protobuf-elixir/pull/54

@tony612 any chance this and tony612/protobuf-elixir#54 can be reviewed and merged?

I don't understand why you want to add this. You can write a module by yourself in your code.

Language implementations of the google. messages need to support the google.protobuf.Any message. This message is useless if you don't provide the canonical Pack() and Unpack() equivalent. It's what the google.protobuf.Any type is used for. If your library provides the structure, it needs to provide the code to manipulate it don't you think?

I think this documentation is why @matehat made this PR: https://developers.google.com/protocol-buffers/docs/proto3#any
This says that libraries should provide this.
If you (@tony612) have your own use case for this software, and don't want to/can't devote time to supporting the use case that others have, I think there might be interest in helping to build/maintain new features.

@isaacsanders @tony612 yep, I'd be up for it. Our company uses protobuf extensively through Elixir, Python and Dart, and we'd definitely be able to sponsor work into this particular library when needs arise.

@matehat @isaacsanders As @demilletech has a use for Protobuf in Elixir, we have made a fork we plan to maintain. Feel free to reopen this PR there.


Remove border-radius on the first tbody row

Remove border-radius on the first tbody row, it is likely not something that is desirable.
The border radius is not visible when the table is placed on a white background, but when using a darker background it will be visible and ugly.

We'll be working to redo the table styles in 2.0-wip to resolve this. Since this can't be merged cleanly, and we're not fixing noncritical bugs in master, I'll close this. Please reopen if you wish to revisit this yourself in 2.0-wip before us.


NTR: spindle pole body anchor complex

Can you please add the following two terms?
thanks a lot
Livia
Term 1:
Name: spindle pole body anchor complex
Ontology: cellular_component
Def: A protein complex capable of interacting with the spindle pole body and the nuclear envelope, in order to embed the spindle pole body in the nuclear envelope at fusion sites of the inner and outer nuclear membrane.
References:
GOC:lnp
PMID:28356353
Relationships:
is_a GO:NEW nuclear membrane protein complex (Term2)
part_of GO:0005816 spindle pole body
part_of GO:0016021 integral component of membrane
part_of GO:0005635 nuclear envelope
capable_of_part_of GO:0071789 spindle pole body localization to nuclear envelope
capable_of_part_of GO:0071988 protein localization to spindle pole body
DB xref:
IntAct:EBI-16412392
Term 2:
Name: nuclear membrane protein complex
Ontology: cellular_component
Def: Any protein complex that is part of the nuclear membrane.
References:
GOC:lnp
PMID:28356353
Relationships:
is_a GO:0098796 membrane protein complex
part_of GO:0031224 intrinsic component of membrane
part_of GO:0005635 nuclear envelope

[ ]

Val; I am working on this now;

OK done the list... time for dinner

I put first chunk in ; will have to wait for 9 and 10

I changed the numbers mid way so double check... 5 got inserted later

[ ] create a new term    <<<<<<<<<< defintion, references!!!!!!
nuclear membrane microtubule tethering complex
as a parent to the mitotic and meiotic versions

if not done already remove "capable_of_part_of GO:0071988"
From GO:0034992 ?

The new def for pt 4 has a typo:

A nuclear membrane protein complex which connects the nuclear outer and inner membranes together, and links thereby links the nuclear lumen to cytoplasmic microtubules.

should be
"A nuclear membrane protein complex which connects the nuclear outer and inner membranes together, and links thereby links the nuclear lumen to cytoplasmic microtubules."

Hi @bmeldal ; fixed typo as it went in yesterday.

5  is just a grouping term for the functionally similar
meiotic nuclear membrane microtubule tethering complex
and
mitotic nuclear membrane microtubule tethering complex
so the definition would just be the genus which is
A nuclear membrane protein complex which connects the nuclear outer and inner membranes together, and links thereby links the nuclear lumen to cytoplasmic microtubules.
I made a mistake in the
meiotic nuclear membrane microtubule tethering complex
definition, it needs  "during meiosis" adding
the parent will be "nuclear membrane protein complex GO:0106083"

@ValWood do you have a PMID for #5

you can use any of the ids on the children?

Actually use this nice review  describes a few of the complexes, the first figure is from this
PMID: 19225124

@ValWood
I  made the new term nuclear membrane microtubule tethering complex and made it a parent of the meiotic version, but I cannot find 'mitotic nuclear membrane microtubule tethering complex; I found the 'meiotic nuclear membrane microtubule tethering complex'

@ValWood
is this the term you mean
nuclear membrane mitotic spindle pole body tethering complex ? should this be renamed ?

Hi HArold, I think this was 99% don, is anything outstanding?

Fixed term label from
-name: nuclear membrane mitotic spindle pole body tethering complex
to
-name: mitotic nuclear membrane microtubule tethering complex
Added the more specific parent for mitotic nuclear membrane microtubule tethering complex
from : GO:0106083 ! nuclear membrane protein complex
to: GO:0106094 ! nuclear membrane microtubule tethering complex
I think that finishes the work needed for this ticket.
Thanks, Pascale