Error while processing function CreateCompletion

Here is the error message when running CreateCompletion
Error detected while processing function CreateCompletion: Traceback (most recent call last):   File "<string>", line 1, in <module> NameError: name 'plugin' is not defined

How did you add the plugin to vim?

Using Plug

No idea what the issue is, maybe you could just reinstall it. If that doesn't work, please send me the exact Plug line, path of the installed plugin on the filesystem and the output of the ls -la * command in that path.

I just ran into this issue as well, and uninstalling + reinstalling didn't fix it. I'm using vim-plug to install in the usual way, and I see that an error flashes across the installation screen when this happens (too quick for me to read). my macOS Vim installation seems to have python3 support,
$ vim --version | grep "+python"
+cmdline_info      +libcall           +python3           +virtualedit

but I'm also seeing that the plugin seems to look for the openai installation in a way that is incompatible with pyenv, i.e., I've just done pip install openai, which installs the package in my "global" virtualenv -- not sure if this is related

Could you try installing openai in a virtualenv and running vim inside that?

@tom-doerr I faced the same problem. But it happens randomly. When I ask for an auto completion with "Ctrl+X" and then I continue asking again then it randomly appears and goes away if I give it a pause. I think it should be about handling some errors/statuses that the API returns.

Actually I have the same problem. I've just installed vim_codex, using the way specified in the documentation, so it is in my ~/.vim/bundle/vim_codex directory. Then I installed openai, and I have the same error.

It seems there is a limitation on API call:
raise self.handle_error_response( openai.error.RateLimitError: Rate limit reached for default-codex in organization org-xOr2p41SW53e8dvuSWUTdryJ on requests per min. Limit: 20. 000000 / min. Current: 30.000000 / min. Contact<EMAIL_ADDRESS>if you continue to have issues or if you’d like to request an increase. Ple ase add a payment method to your account to increase your rate limit. Visit https://platform.openai.com/account/billing to add a payment metho d.


fix: update to eye v3.4.9

fix: update to eye v3.4.9

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

npm package (@latest dist-tag)
GitHub release
v4.4.5

Your semantic-release bot :package::rocket:


Evil159/footer support rebased

Details
This PR is a rebased version of https://github.com/airbnb/MagazineLayout/pull/23. I went ahead and  incorporated all of the feedback that I would have asked you to implement  @evil159 in the last commit https://github.com/airbnb/MagazineLayout/commit/433d0bc655d62c3b300943970508074b1dc5063e
Some notable changes I made:

Simplified the footer layout logic in SectionModel. I want to avoid introducing additional flags and state. The addition of a new return-early case in the core layout function also made me nervous. The new code is less efficient, but more straightforward. I plan to refactor this function anyways so that recompute / invalidation is more explicit.
Fixed tests (the original footer layout logic had a bug, and  so the tests were buggy as well. See  https://github.com/airbnb/MagazineLayout/pull/31/commits/bf472853869e50a01690a485f582092145eb01c7#diff-187bbc570783ead7c85afd619305a795R562 - how could a footer have 0 width?)
Separated MagazineLayoutSupplementaryViewVisibilityMode into a MagazineLayoutHeaderVisibilityMode and MagazineLayoutFooterVisibilityMode. The reasoning for this is to ensure that this does not introduce a breaking API change.
Minor indentation updates
Minor naming updates
Minor file organization updates

Related Issue
https://github.com/airbnb/MagazineLayout/issues/18
Motivation and Context

How Has This Been Tested
Ran automated tests.
Types of changes

[x] Docs change / refactoring / dependency upgrade
[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist

[x] My code follows the code style of this project.
[x] My change requires a change to the documentation.
[x] I have updated the documentation accordingly.
[x] I have read the CONTRIBUTING document.
[x] I have added tests to cover my changes.

It was the least I could do after not getting to the review for 2 months 😅 Thanks for your patience and for implementing this - this is an awesome feature to have, and gets us even closer to feature parody with flow layout!


fix: properly escape $ in data files

Fix makes sense. Looks good.

It might be good to add one or more tests to verify the added modifications.

@airween You're right. I'll open an issue track that (I'm working on other stuff a.t.m.).


Tree doesn't reset when search field is emptied

When testing the Riot demo, there's a native type="search" (x) button when the search field has a value. However, clicking on it doesn't reset the tree display, it only empties the field itself. Perhaps a different event (like input) should be used?

Hi @fabien,
I don't know why (surely an overlook) but I used the keyupevent in riot and the inputevent in the other frameworks.
I'm fixing this asap, thanks for raising the issue !


LibWeb/CSS: Tweak in CSSRGB::to_color() to avoid floating point errors

Example of the difference:
50 * 2.55      --> 127.4999 --> round towards +∞ --> 127
50 * 255 / 100 --> 127.5000 --> round towards +∞ --> 128

Now, 9 failing WPT tests in /css/css-color/ pass.

Tests/LibWeb/Screenshot/css-color-functions.html fails on CI. Probably because your updated image has a scrollbar visible.

huh, i saw the failures but didn't scroll far up because of the memory leak sanitization spam.
the new ref image i put in was output by headless-browser itself. so why is it failing? i now checked CI fails because the color of the scrollbar is different.

huh, i saw the failures but didn't scroll far up because of the memory leak sanitization spam.

Yeah that spam makes it difficult to find the actual failures.

the new ref image i put in was output by headless-browser itself. so why is it failing? i now checked CI fails because the color of the scrollbar is different.

Your screenshot includes a scrollbar. When it's loaded into the browser, it'll get that, plus the real scrollbar. In the past I've manually edited the image to remove the scrollbar but there might be a smarter way of doing it now.

oh got it. because the scrollbar color has opacity < 1.

used scrollbar-width: none;

@ronak69 The test is still a reftest in serenity. I thought this might help with the FIXMEs for non-100% alpha here https://github.com/SerenityOS/serenity/pull/25171/files#diff-0111303e7ec1a9d7c5643a07175aa7ddaf04750942bf9ce00b1a21088ebaf0ddR20 but it doesn't. So maybe there's more rounding off elsewhere?


[AutoPR web/resource-manager] Update UserAssignedIdentities spec in Web

Created to sync https://github.com/Azure/azure-rest-api-specs/pull/5288

This PR has been merged into https://github.com/Azure/azure-sdk-for-js/pull/1415


Any way to debug pages not working?

Hi,
I'm using Helium for a task management web page I wrote myself. My async calls don't seem to work in Helium - perhaps something to do with cookies/auth. Everything works fine in Chrome and Firefox so I'm wondering if there's any way to find out what it's trying to send?
Jimbo

@jimbofreedman Hellium uses WebViews, which are Safari based

Thanks! Will test my page in Safari then and see if I can replicate.


Pandas 2 support

/kind feature
When will pandas 2 be supported?
Current pandas version is 1.5.3 for the last dev version with no possibility of version upgrade / downgrade. When will pandas 2 or at least a wider range of versions be supported?

@yk4r2 The latest kserve 0.11.0 supports pandas 2.


[FLINK-12204] [jdbc] make JDBCOutputFormat ClassCastException more helpful

What is the purpose of the change
This PR makes JDBCOutputFormat's ClassCastException more readable. Current exception make me confused which column is wrong. The new error message will help people find the error location.
Brief change log
Verifying this change
This change added tests and can be verified as follows:
- Already check by org.apache.flink.api.java.io.jdbc.JDBCOutputFormatTest#testExceptionOnInvalidType
Does this pull request potentially affect one of the following parts:

Dependencies (does it add or upgrade a dependency): no
The public API, i.e., is any changed class annotated with @Public(Evolving): no
The serializers: no
The runtime per-record code paths (performance sensitive): no
Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Yarn/Mesos, ZooKeeper: no
The S3 file system connector: no

Documentation

Does this pull request introduce a new feature? no
If yes, how is the feature documented? not documented

Hi @FaxianZhao, thanks for your PR.
The change looks good, however, I don't think it qualifies as a hotfix PR.
I created a Jira issue and adjusted the PR title accordingly.
Please create issues for all code changes that go beyond very simple typo fixes.
@flinkbot approve description consensus architecture quality
Will merge this change.
Thank you, Fabian

@fhueske Thanks for your help. I'm learning how to be a contributor. :)

@FaxianZhao no worries. Welcome to the Flink community! :-)


[Outlook] (Smart Alerts) Fixes accessibility and support issues

Q
A

Bug fix?
yes

New feature?
no

New sample?
no

Related issues?
N/A

What's in this Pull Request?

Updates the button in the add-in task pane for keyboard accessibility. Fixes color contrast issues.
Updates the task pane screenshot.
Adds a note on supported clients.
Minor code refactoring.

Guidance
See above.

The overview images needs the following color contrasts fixed:

Section 2, green background under "Add-ins Sample: marketing" does not pass.
Section 2, blue-green background under "Office Add-ins
Sample: sales" does not pass.
Section 1: Grey background with white text does not pass (text is not completely white.)
Section 4: Blue background with white text does not pass (text is not completely white.)

Thanks for the feedback, @davidchesnut. I've been working on addressing these, but ran into an issue with the category list/expanded dropdown field in the task pane. It appears that I'm unable to override the background color when a category is selected. I'm going to test using another form type (maybe checkboxes?) or see about creating a custom field for it. Regarding your Section 4 feedback, I confirmed that the buttons colors pass the contrast tests (foreground: #FFFFFF, background: #005D95). Let me know if I need to make further adjustments.

The changes to the category list/expanded dropdown field requires extensive changes. I'll address this in a separate PR. Internal work item: 7333950


Test Sharding

PR Checklist

[x] Addresses an existing open issue: fixes #4958
[ ] That issue was marked as status: accepting prs
[x] Steps in CONTRIBUTING.md were taken

Overview
This strategy uses file-based sharding. The entire set of test files is divided into different groups or "shards". Each shard contains a subset of the test files. The shards use a round robin approach using a simple modulus calculation. The way this works in the code is it simply filters out the tests by the shard value before proceeding to the rest of the mocha code.
A shard option has been added to the command line interface for specifying which shard to run and how many shards there are in total. This value is validated to ensure that bad values aren't inputted.
Sharding does not work when parallel mode is enabled.

Marking as draft pending discussion in #4958.


As a RC4 student, I want to know when I started and ended/completed the goals I have

so that I can be reminded of when I started to have this goal and how long I took to achieve it.

Satisfies #95


Sample does not work

Not able too run the example

The example tests are supposed to fail in order to show off the generated report. Can you elaborate on the problems you're encountering?

it´s not failing it´s not even running.
Try npm i && npm test  || yarn && yarn test

Please give me more context.
Which node version?
What operating system?
Is it a clean installation?
What is the output of the command?
On my two local machines as well as on the CI it is working.

Which node version?  -tested with 8-10 nvm
What operating system? mac
Is it a clean installation? yep
What is the output of the command?
yarn install yarn install v1.12.1 warning package.json: No license field warning jest-screenshot-example: No license field [1/4] 🔍  Resolving packages... [2/4] 🚚  Fetching packages... [3/4] 🔗  Linking dependencies... warning " ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>|| ^7.0.0-0". [4/4] 📃  Building fresh packages... [1/4] ⠐ fsevents [2/4] ⠐ native-image-diff [3/4] ⠐ node-libpng error /Users/***/Downloads/jest-screenshot-master 3/example/node_modules/node-libpng: Command failed.
then
Error: An error occurred while adding the reporter at path "/Users/***/Downloads/jest-screensho t-master 3/example/node_modules/jest-screenshot/reporter.js".Cannot find module './dist/reporter.js'     at customReporters.forEach (/Users/***/Downloads/jest-screenshot-master 3/example/node_modules/jest-cli/build/test_scheduler.js:270:15)     at Array.forEach (<anonymous>)     at TestScheduler._addCustomReporters (/Users/***/Downloads/jest-screenshot-master 3/example/node_modules/jest-cli/build/test_scheduler.js:262:21)     at TestScheduler._setupReporters (/Users/***/Downloads/jest-screenshot-master 3/example/node_modules/jest-cli/build/test_scheduler.js:243:12)     at new TestScheduler (/Users/***/Downloads/jest-screenshot-master 3/example/node_modules/jest-cli/build/test_scheduler.js:50:10)     at /Users/***/Downloads/jest-screenshot-master 3/example/node_modules/jest-cli/build/run_jest.js:149:27     at Generator.next (<anonymous>)     at step (/Users/***/Downloads/jest-screenshot-master 3/example/node_modules/jest-cli/build/run_jest.js:23:380)     at /Users/***/Downloads/jest-screenshot-master 3/example/node_modules/jest-cli/build/run_jest.js:23:540     at process._tickCallback (internal/process/next_tick.js:68:7)

You need to run yarn build and yarn webpack in the root project. Or use the Makefile.

Maybe you optimize the README and the package.json in the example project folder? while build and webpack are not existing commands by default, you might use a postinstall Hook?

Thanks for you recommendation. I will update the Readme.


Feature Request: Option to Replay Fixed Number of Interactions

I want to use vcr for debugging and I would like to replay a fixed number of interactions and record the rest.
If I am not mistaken currently all interactions are either recorded or replayed based on the record mode. There's no built-in way to replay only a subset of recorded interactions while recording new ones.
As a workaround I can edit the cassette after each session and remove the new interactions that were saved - but that is a bit time consuming. It would be more convenient if there was a config option for that.
I can see two possibilities:

New Persister Implementation
Create a subclass of FilesystemPersister that implements this functionality
Would allow for custom handling of interaction limits without modifying core code
Could be implemented by users without core changes
New Configuration Option
Add a global config option (e.g., replay_limit: int)
Would need to handle interaction with existing record_mode settings
More user-friendly but requires core changes

Claude wrote the following implementation for the second option:
class VCR:
    def __init__(self, **kwargs):
        self.replay_limit = kwargs.pop('replay_limit', None)
        # ... existing initialization code ...

    def _get_cassette(self, path, **kwargs):
        """Modified to limit loaded interactions."""
        cassette = super()._get_cassette(path, **kwargs)

        if self.replay_limit is not None and cassette.interactions:
            cassette.interactions = cassette.interactions[:self.replay_limit]

        return cassette

# Usage example with configuration:
vcr = VCR(
    replay_limit=5,
    record_mode='once'  # Will replay first 5 interactions, record new ones after
)


Add bulk-delete command for relationships in zed

We discussed turning the subject filter into a flag for both this and read before merging this PR.

@jzelinskie Added

Updated


Release 5.1.0

Prepare v5.1.0 release.
Combination of the following PRs:

https://github.com/devicekit/DeviceKit/pull/357
https://github.com/devicekit/DeviceKit/pull/356
https://github.com/devicekit/DeviceKit/pull/360
https://github.com/devicekit/DeviceKit/pull/361

Can someone approve this?


Feature Request: Strip Comments of Whitespaces

Feature Request
title.
Rationale
Users often times type "return" or "enter" in their keyboard to send their comment to the post. but in this website, it doesnt do that, and instead makes a new line. sometimes, users does not delete this newly created line and just press the "comment" button immediately. this in turn leads to an ugly space in between the comment and its interaction elements.

Can't reproduce this on my side. It seems that the form submission handler already trims posts of trailing whitespaces.

thats weird huhuu

Yep, also getting the same issue.

Oh, it's the comments that are showing this behaviour. My mistake @whinee
This seems to be an interesting issue to look into

I think I've found a fix for this. Can this be assigned to me? @bricesuazo

I think I've found a fix for this. Can this be assigned to me? @bricesuazo

Sure.

I've submitted a PR for the possible fix. Thank you! @bricesuazo


Small skeleton refactor

- Removed `HumanSkeleton` superclass to simplify hierarchy
* Rename `SimpleSkeleton` to `Skeleton`

I did better in sekelton-data branch.

i agree but skeleton-data isnt merged yet?

Why it's not usable? It doesn't seem to break anything. I just want us to have as much refactorning changes pushed in one branch and then get them to main so there no problems for others working on stuff

Closing it as it will be fully included in PR from skeleton-data soon. If there are additional changes you would want to make to it, make a new PR please.


product deleted but keep showing up in market public

Nice project :)
I've setup a stall, add a product , but when i wanted to update the picture , it didn't go well so i add another product and delete the first one .
in the lnbits extension manager, all looks great , but i can still see the deleted product : https://sadruffs4.lnbits.com/nostrmarket/market?merchant_pubkey=81cce63772699677ec45559da11ea7c2eac842f02411efa0d558ae8f325ec855&stall_id=LBoXPKu3VUNYPEYswbZqCM&product_id=YsRUqoBFZhJeLLvFT9nVHA
I did delete all nostr posts and re-publish .

Thanks!

I see two products in the marketplace. Should there be only one?
Do you have the same view as the screenshot?

I have the same view and there should be only the pineco 04 ( I deleted the pineco 1 ) .
here is a view of the current nostr market stall admin view
maybe i can send you the database dump ?

Can it be that the product didn't get deleted from at least 1 relay, and it get's pulled in?

Can it be that the product didn't get deleted from at least 1 relay, and it get's pulled in?

No. I have tested with only one relay (wss://relay.damus.io) and the product still shows up.

A bit pricey, but other than that you didn't do anything wrong. I'm trying to reproduce the issue locally.

It's unique ceramic art but you're right, we will certainly reduce the price, especially to test a real selling from this channel :)
also, i don't know how to integrate  in nostr ( just link ? )

With the new changes to the marketplace you will be able to restore from nostr your stalls and products.
Then you can update/delete them if you want.
In the video below I have mocked your pubkey and restored your stall. I was able to restore both products. Of course I could not delete the old one since I do not have the private key.
There changes are on main and there is a pre-release if you want to test:
https://github.com/lnbits/nostrmarket/assets/2951406/d8389463-c63f-4a8b-8c0d-708b41d81fb1


path result record seems to be wrong

{
        "source_asset_type": "native",
        "source_amount": "25.2424242",
        "destination_asset_type": "native",
        "destination_amount": "50.0000000",
        "path": [
          {
            "asset_type": "credit_alphanum4",
            "asset_code": "AAA",
            "asset_issuer": "GAX4CUJEOUA27MDHTLSQCFRGQPEXCC6GMO2P2TZCG7IEBZIEGPOD6HKF"
          }
        ]
      }

I think there might be a bug in the paths calculation: the below request returns 2 possible payments. One is the simple direct XLM payment, the other is pasted above. Seems as if source_asset_type should be credit_alphanum4 and source_asset_type should be AAA
https://horizon-testnet.stellar.org/paths?destination_account=GDJXQYEWDPGYK4LGCLFEV6HBIW3M22IK6NN2WQONHP3ELH6HINIKBVY7&source_account=GAN65D2FEI63T4MBMOWWOP3K7VS6SVI5T6NNKIHNCI6PN32IGF6OVKSS&destination_amount=50&destination_asset_type=native

This is not a bug as far as I can tell, @TbLtzk.
The source account for that request GAN... does not hold AAA credits, and so AAA cannot be the source asset.  In fact, that account only holds a native balance.  Why do you think the source should be AAA?  I ask because this is probably a failure of our documentation so I was hoping to understand where it is failing, so we can improve it.

Ok, you're right it can't be the source asset. But why is it returned as possible payment and why does it fail when I use this path option?
Furthermore it seems weired that I would have negative path costs (send 25.24242 and receiver gets 50)

What is the error returned when it fails?
As far as the cost, first I want to point out #239.  So, the costs are currently broken (and most likely the source of your failed transaction).  But in regards to your question about negative costs, that's a viable situation...  there's nothing stopping the exchange rate from being over 1.0.
I'm going to go ahead and close this, but feel free to add your specific failure as a comment, or open a new issue with that information.
Sorry about the pain!

The error code is
op_over_source_max
maybe I need to add a small buffer. The transaction XDR is AAAAABvuj0UiPbnxgWOtZz9q/WXpVR2fmtUg7RI89u9IMXzqAAAAZAAIbNwAAAAqAAAAAAAAAAAAAAABAAAAAAAAAAIAAAAAAAAAAA8LsDIAAAAA03hglhvNhXFmEspK+OFFts1pCvNbq0HNO/ZFn8dDUKAAAAAAAAAAAB3NZQAAAAABAAAAAUFBQQAAAAAAL8FRJHUBr7BnmuUBFiaDyXELxmO0/U8iN9BA5QQz3D8AAAAAAAAAAUgxfOoAAABAIALUg3DyNoZtmFbEzUHPA50wGcaCf9nLreqfPanjOog+xBpcCrfCQ7aBWGr6fA+t0XR49zM9RhMl7N2dEuarAg==

AH ok this MIGHT be effect of #239

Yeah, this seems like #239 in effect... I got bit by it yesterday while I was preparing for a talk I gave here in Lagos.
As far as the understanding the path:  The source_asset defines the start of the path, the destination_asset defines the end of the path, and the path attribute defines any intermediary stops in the path.  This form was chosen because it aligns with the schema for PathPaymentOp, the underlying XDR struct that drives the whole thing...  that alignment should make integration much easier.  The path defines the points on the line, not the spans.

Thanks for your help, think I got it, now!
Final question then, just to be sure: if I have one conversion, let's say EUR -> XRP, the paths array would be empty and I would only know by comparing source and destination asset, that a conversion is involved, right?

that's right


Silence gcc -Wunused-function

gcc on MacOS-ARM64  may error out with
/Users/runner/work/php-src/php-src/ext/hash/blake3/upstream_blake3/c/blake3_dispatch.c:112:5: error: unused function 'get_cpu_features' [-Werror,-Wunused-function]
full compiler log https://github.com/php/php-src/actions/runs/7762643678/job/21173438425?pr=13194

the optimal fix would be to make sure get_cpu_features() is only compiled on platforms where it is used, but that would take more effort (have not investigated how much effort that would be)

hmm noticed that get_cpu_features is not static.
that makes me wonder,
1: is get_cpu_features() supposed to be part of a public api? in which case, it needs to be compiled even on architectures where it isn't used?
2: why did gcc complain about it when it isn't static? simple tests suggest -Wunused-function does not trigger on non-static function.. except here? 🤷♂

nevermind, thought of a better way to solve it.


About memory's variational dropout

First, thanks for sharing your great work.
As following your code, a question came across about your variational dropout on memory vector. (https://github.com/stanfordnlp/mac-network/blob/master/mac_cell.py#L215, https://github.com/stanfordnlp/mac-network/blob/master/mac_cell.py#L590)
It seems the mask is generated once when building graph, maintaining its shape afterwards (64, 512), and is applied always whether the model is in training or evaluation.
Since this kind of dropout produces stochastic result while evaluation, and accept only fixed batch size. I am wondering Is it ok to apply such method.
Correct me if I'm reading the code wrong.

Hi, thank you for the interest in the repo!
Indeed, the mask is generated once and applied for all the cells. I noticed that doing so gives better performance than applying a randomly different mask after each cell, especially when there are many. Potentially the reason for that is that if you do a different mask after each cell overall there are very few continuous "gradient lines" from start to end that aren't masked by any of the steps, making training harder.
Please note that during evaluation all the dropouts in the model are always set to 1,
https://github.com/stanfordnlp/mac-network/blob/master/model.py#L122
and thus during evaluation there is no stochasticity. Only during training.
Please let me know if you have any other questions!

Thank you for your kind and quick reply!
I must have misunderstood the code :(
So the memory dropout mask is created every batch iteration and maintaining its shape during the MACCell recurrence, and feed_dict at evaluation time creates the mask with prob=1. Am I right?
Thanks again and please close this issue if my recap is correct.

No worries, what you described now is completely correct! :)
happy to help!


⚠ Processors has degraded performance

In d7fe328, Processors ($STATUS_URL) experienced degraded performance:

HTTP code: 200
Response time: 46 ms

Resolved: Processors performance has improved in 78023c4.


[BUG]: drizzle-kit push always shows columns with custom types as changed even tho the type didn't change

What version of drizzle-orm are you using?
0.33.0
What version of drizzle-kit are you using?
0.24.2
Describe the Bug
So I have the following schema file
import { sqliteTable, text } from "drizzle-orm/sqlite-core";
import { f32Blob } from "./blob.ts";
//
export const example = sqliteTable("example", {
  id: text("id").primaryKey(),
  blob: f32Blob("blob", {
    length: 10,
  }),
});

and here's the blob.ts file
import { Buffer } from "node:buffer";
import { customType } from "drizzle-orm/sqlite-core";

export const f32Blob = customType<{
  data: number[];
  config: {
    length: number;
  };
  configRequired: true;
}>({
  dataType(conf) {
    return `F32_BLOB(${conf.length})`;
  },
  fromDriver(value: Buffer) {
    const fArr = new Float32Array(new Uint8Array(value).buffer);
    return Array.from(fArr);
  },

  toDriver(value) {
    return Buffer.from(new Float32Array(value).buffer);
  },
});

the drizzle config file
import { defineConfig } from "drizzle-kit";

export default defineConfig({
  schema: "./drizzle/schema.ts",
  dialect: "sqlite",
  driver: "turso",
  dbCredentials: {
    url: "http://<IP_ADDRESS>:6969",
    authToken: "turso-token",
  },
  strict: true,
  verbose: true,
});

when i run drizzle-kit push for the first time with an empty libsql db

when i run drizzle-kit push just after the first one with 0 changes to the schema file or the blob.ts whatsoever

Expected behavior
well, the expected behaviour is it should not happen. This is just an example but in a real production app with a lot of relations, all the tables that depend on this table are being renamed and copied for no reason at all. This is bad and causes foriegn key errors sometimes which is frustrating and now i am just manually running my migrations but would be very helpful if i didn't have to.
btw Love the project and very grateful for all the work :)
Environment & setup

tried on Linux (arch btw...sorry 😅) and wsl
this example is using deno but the actual project is using node and still has the same issue

another kinda related issue
so libsql has a built in vector extension and has a way to create an index on a vector field eg
CREATE INDEX test_idx ON example (libsql_vector_idx(blob));

also there's no way (that i know of) to write this with drizzle

but when i run drizzle-kit push again it asks to drop the index and i don't think there's a way to tell drizzle kit to ignore just that index/table


chore(deps): bump html2pdf image to 1.2.1

:tada: This PR is included in version 1.0.0-next.17 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Add debugging option to write vmservice address to file after starting

Description
An attempt at addressing the workflow in https://github.com/flutter/flutter/issues/33129. Adds a new option to run, --vmservice-out-file. This takes a String which is interpreted as a path to a file where the URI of the first connected vmservice is written. The intention is that this should make automation of flutter build/run/driver easier.
Example workflow
The example below scripts flutter run and flutter drive to start and launch a driver test:
# Run the application
flutter run -d deviceId \
  --target=test_driver/example_main.dart \ # ensure we use the test driver entrypoint
  --start-paused \ # keep the vm paused until the driver starts
  --no-resident \ # disconnect but keep the application running
  --vmservice-out-file=foo  # NEW! write the vmservice uri to the file foo for reuse.

# The above command will exit once it is finished, and we can start the flutter driver:
flutter drive \
  --use-existing-app="$(cat foo)" \ # NEW! grab the vmservice uri we wrote above
  --driver=test_driver/example_main_test.dart  # provide the test script

Fixes #33129

@jonahwilliams When I run flutter with the --no-resident the vmservice url written to the file is closed after the command has completed.
This is the command that I am executing:
flutter run -t test_driver/app.dart --observatory-port=8888 --disable-service-auth-codes --flavor=development --no-resident --vmservice-out-file=foo --start-paused
While running the observatory, becomes available for a short time, but after the command has completed, it's closed. Do you know why?

When you run the first command without no-resident, then wait until the URL is printed to the file. And then start the second command with the URL from the file, in a separate terminal than it works.


Convert ED25519phSignerVerifier to the Pure version

Summary

In https://github.com/sigstore/fulcio/issues/1388#issuecomment-1915809491 we agreed to just use ED25519 (Pure) in Fulcio. That means that in Cosign (maybe elsewhere?) we need to convert a ED25519phSignerVerifier to the Pure version, but for doing so we need access to the Private key, thus the new ConvertToED25519 API.
Release Note

Added ConvertToED25519 method to ED25519phSignerVerifier to convert the ED2551ph SignerVerifier to a ED25519 one.

Documentation

See https://github.com/sigstore/cosign/pull/3479/commits/16c0256645368419359401f64744357438befd17 for how this is going to be used in Cosign.


Get-FormatData should output non-terminating errors when failing to load a control

Prerequisites

[X] Write a descriptive title.
[X] Make sure you are able to repro it on the latest released version
[X] Search the existing issues.
[X] Refer to the FAQ.
[X] Refer to Differences between Windows PowerShell 5.1 and PowerShell.

Steps to reproduce
Get-FormatData  # Works fine for now
this will demonstrate the bug, but so will any module that has a  element in a format file.
Install-Module Posh -Scope CurrentUser
Import-Module Posh
Get-FormatData # Now just blows up unhelpfully
Expected behavior
Get-FormatData writes a non-terminating error for each formatter it could not recreate.

Actual behavior
Get-FormatData: Unable to cast object of type 'Microsoft.PowerShell.Commands.Internal.Format.ControlReference' to type 'Microsoft.PowerShell.Commands.Internal.Format.ComplexControlBody'.

Error details
Exception             :
    Type       : System.InvalidCastException
    TargetSite :
        Name          : ChkCast_Helper
        DeclaringType : System.Runtime.CompilerServices.CastHelpers, System.Private.CoreLib, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=7cec85d7bea7798e
        MemberType    : Method
        Module        : System.Private.CoreLib.dll
    Message    : Unable to cast object of type 'Microsoft.PowerShell.Commands.Internal.Format.ControlReference' to type 'Microsoft.PowerShell.Commands.Internal.Format.ComplexControlBody'.
    Source     : System.Private.CoreLib
    HResult    : -2147467262
    StackTrace :
   at System.Management.Automation.CustomItemBase.Create(FormatToken token)
   at System.Management.Automation.CustomControlEntry..ctor(ComplexControlEntryDefinition entry)
   at System.Management.Automation.CustomControl..ctor(ComplexControlBody body, ViewDefinition viewDefinition)
   at Microsoft.PowerShell.Commands.GetFormatDataCommand.ProcessRecord()
   at System.Management.Automation.CommandProcessor.ProcessRecord()
CategoryInfo          : NotSpecified: (:) [Get-FormatData], InvalidCastException
FullyQualifiedErrorId : System.InvalidCastException,Microsoft.PowerShell.Commands.GetFormatDataCommand
InvocationInfo        :
    MyCommand        : Get-FormatData
    ScriptLineNumber : 1
    OffsetInLine     : 1
    HistoryId        : 42
    Line             : Get-Formatdata
    Statement        : Get-Formatdata
    PositionMessage  : At line:1 char:1
                       + Get-Formatdata
                       + ~~~~~~~~~~~~~~
    InvocationName   : Get-Formatdata
    CommandOrigin    : Internal
ScriptStackTrace      : at <ScriptBlock>, <No file>: line 1

Environment data
Name                           Value
----                           -----
PSVersion                      7.4.0
PSEdition                      Core
GitCommitId                    7.4.0
OS                             Microsoft Windows 10.0.22621
Platform                       Win32NT
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0…}
PSRemotingProtocolVersion      2.3
SerializationVersion           <IP_ADDRESS>
WSManStackVersion              3.0

Visuals
No response

I generally follow a couple of principles to keep coding simple and reliable

a functions should appear atomic, it either completely works or it fails and tells you so
a code should fail safely but cleanly
code should not try and analyse problems above it's paygrade, if it fails and it doesn't understand why, don't pretend to solve the problem when you literally don't know what the problem is

So in the case of loading a list of data, it should fail on the first item it fails to load and then report an error, not keep on going to see if others also fail to load.

@rhubarb-geek-nz, what you're describing is fundamentally at odds with PowerShell's error-handling philosophy; see Cmdlet error reporting; a concise summary that includes the important distinction between statement-terminating and script-terminating (runspace-terminating, fatal) errors can be found in this Stack Overflow answer.

Fair enough, I can see the value of that approach when you are in the middle of a pipeline and you just have to process each item as best you can, as long as your final status does say that not all succeeded.

👍 It is the automatic $? variable that tells you whether an error - of any kind - occurred in the previous statement.
In v7+ you can use || to act on this value (and in all versions/editions you can collect non-terminating errors in a custom variable with the common -ErrorVariable parameter).

Isn't the real problem here that the error is too internal and doesn't help inform the user which formatdata is at fault?


doc: arm: mec172x:  MEC172x EVB documentation points to some inexistent jumpers

Describe the bug
MEC172x EVB Documentation needs to be revisited
https://docs.zephyrproject.org/latest/boards/arm/mec172xevb_assy6906/doc/index.html
There are several some jumper options that do not match the physical board.
i.e. Documentation indicates to close JP88 5-6, but EVB board JP88 is 1x3 pin header.
If you wish to power from +5V power brick, then connect to barrel connector P11 (5.5mm OD, 2.1mm ID) and move the jumper to JP88 5-6.
Expected behavior
Updated documentation with correct jumper settings
Impact
Cannot set EVB boards for testing.

Addressed by https://github.com/zephyrproject-rtos/zephyr/pull/42652


Changing default behaviour of matplotlib

If you import your library, the axis for matplotlib are switched.

@karellat can you please submit a MWE (minimal working example) so I can trace back where the error is?
Please paste a simple piece of code, easy to reproduce and then I can try to solve the issue.

no comments in 2 weeks, closing this for now.


Group subscriptions by tenant

Is your feature request related to a problem? Please describe.
Whilst not a technical problem, it is a problem when dealing with 10s / 100s of subscriptions and not knowing which tenant they belong to.
Describe the solution you'd like
I would like to be able to group subscriptions by tenant in the left panel, so I can easily collapse or show different tenant groups, i.e. different partners, customers that I may be working with.
Describe alternatives you've considered
Not using the tool and using Azure Portal instead
Additional context
Thanks.

Duplicate of #2621


Between Level Storage

Somewhat similar to issue #19 however, possibly, easier to implement.
How about we have a "notes" page", that allows the user to keep useful pieces of code, that might be usable on all levels.  Something similar to the notepad in untrusted.

Some more thoughts on this over here on the forum: http://discourse.codecombat.com/t/notepad/3478/3

I think that rather than encouraging copy-pasta (lord knows how many interns I've broken of that habit), it would make better sense to tab-iffy the code window with Main and Library tabs. The Library tab would persist between different levels and be pre-loaded before running code in Main. The correct place to introduce this is shortly after functions are introduced. "I feel like I've written this before. Perhaps I should put this into my library since I might be using it again in the future."


add Portuguese language support

This file adds Portuguese language support for guacamole client.
JIRA already created: https://issues.apache.org/jira/browse/GUACAMOLE-1207

@anfabio: Your Pull Request title and your commit messages need to have the GUACAMOLE-1207 issue prefixed to them (see the other open pull requests for examples).
Also, please make your commit messages meaningful and descriptive of the changes. See the following page for a humorous take on good and bad messages:
https://www.codelord.net/2015/03/16/bad-commit-messages-hall-of-shame/

This was merged in #575.


Weekly Patch Release v1.5.4

What does this PR do?
Contains all bugfixes to be released next week. As bugfixes get merged to master, they will get cherry-picked into this branch by the individual author (core) or on-caller.
For staff/core: The new release guide is here.
gh pr list -s merged -S 'merged:2021-11-24T18:30:00.000Z..2021-11-30T18:30:00.000Z' --json mergedAt,milestone,url,mergeCommit,title --jq 'sort_by(.mergedAt) | reverse | .[] | select((.milestone.title ==
"1.5.x") or (.milestone.title == null)) | [.mergedAt, .url, .mergeCommit.oid, .title] | join(" ")' --limit 100

Before submitting

[x] Was this discussed/approved via a GitHub issue? (not for typos and docs)
[x] Did you read the contributor guideline, Pull Request section?
[x] Did you make sure your PR does only one thing, instead of bundling different changes together?
[x] Did you make sure to update the documentation with your changes? (if necessary)
[x] Did you write any new necessary tests? (not for typos and docs)
[x] Did you verify new and existing tests pass locally with your changes?
[x] Did you update the CHANGELOG? (not for typos, docs, test updates, or internal minor changes/refactorings)

PR review
Anyone in the community is free to review the PR once the tests have passed.
Before you start reviewing make sure you have read Review guidelines. In short, see the following bullet-list:

[ ] Is this pull request ready for review? (if not, please submit in draft mode)
[x] Check that all items from Before submitting are resolved
[x] Make sure the title is self-explanatory and the description concisely explains the PR
[x] Add labels and milestones (and optionally projects) to the PR so it can be classified

Did you have fun?
I made sure I had fun coding 🙃
Part of #1 (it's a lie, this is just here to avoid noisy GitHub bot)

Reminder: rebase onto 1.5.x after #10738


Add write support for rich text bodies

Currently, rich text will be written back to the document as its HTML form, which is not ideal.

The most "JEE" way to do this would probably be to say that the object property should be a MimeMessage, since that can represent what we need and would be a perfect hint to the driver to store it as such. However, that API is pretty annoying to use for various reasons. Maybe that could be made better with a helper utility class, but it'd be non-obvious.
Another way to handle this may be to just have a marker on the field to store a String as RT/MIME - either something on @ItemFlags or another annotation. That would be less complete, not accounting for other MIME parts, but it would fit the normal case.

Part of this is done by way of the @ItemStorage annotation, which allows you to specify storage as MIME as well as the content type. It will be better to also support MimeMessage, MimePart, and MimeMultipart, though.


The Add-On did not restore the previous operating state after the BACnet device was power-cycled.

I had to turn the GTW-21 off and on, and I found that the Add-On did not re-subscribe to CoV after the BACnet device was power-cycled.
CoV subscriptions and polling were active before the power-cycle, but not thereafter. I see in Yabe that there are no active subscriptions, even though the Add-On has subscriptions in the list.
I'd propose to add a recovery mechanism that restores the previous operating state if the connections to the BACnet device was interrupted.

There's plans to make some sort of a heartbeat functionality to poll whether a device is still there, but for now it doesn't have a priority.
A way to work around this issue is having the CoV heartbeat shorter, like 120 seconds for example. This is a similar way to how Yabe does it.

Hmm.. can I configure the heartbeat in the current Add-On? I didn't find anything in your documentation about that option...

There currently is no heartbeat, just something I want to implement later.
As for resubscribing, restarting Home Assistant does nothing to the add-on. Only rebooting the host device will also restart the add-on. Instead, you can decrease the lifetime of a CoV subscription from 28800 to 120 seconds. This should resubscribe. If it doesn't, feel free to leave some logs so I can take a look at what's happening.

The add-on should now restore CoV subscriptions after the device lost connection. This will be done through resubscribing when the lifetime of the subscription has passed.


Use different interface for setting LUT (closes #188)

Closes #188
There is an inconsistency where the previous method wanted values in [0, 255] while the current method wants values in [0, 1]. I decided to handle this within each method to otherwise maintain prior API.
I generated the docs on my Ubuntu system and everything looks good. It would  be best to have someone else on a different system verify that the example gallery does not change with this PR.

Coverage increased (+0.05%) to 78.413% when pulling 8515afa051da9532a858129ebcc23ab08a727879 on mwaskom:fix_lut_update into 69e969b3698314470ce37f608651dd7493316db9 on nipy:master.

fine with me

Thanks @mwaskom


Synch with upstream

There have been a few important changes in the upstream repo, including one for correct decimal serialisation.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.1 out of 6 committers have signed the CLA.:white_check_mark: rigadon:x: polarising-java:x: jniebuhr:x: tchiotludo:x: Gagarmel:x: fbadYou have signed the CLA already but the status is still pending? Let us recheck it.


Updates to build.gradle

Was wondering if it'd be possible to update the sdkVersions and buildToolsVersions used in the android side of the project. In my experience so far, the newer versions of gradle (3.0) require the versions to be at least 26.

Yes! This is sorely needed.

LGTM @alvelig 🐽

Here's a better idea.  Simply check for gradle properties defined in one's root build.gradle, as recommended by Android Gradle Tips & Tricks

@bsmarimon Why don't we step to 27 right away?
@christocracy so you advice against upgrading?
@rborn sorry, was very busy last week.

@alvelig see #2047.  With this PR, you won't need to rely on react-native-maps "Updating to 27 right away".  It will become a slave to your desired version whenever you want.

I think we'll close that in favor of #2047, don't you mind, @bsmarimon?

@christocracy Yes, I've already seen that and I agree totally

Closing in favour of #2047
@bsmarimon thanks for your PR 🤗


feat: expose service_endpoints

Description
Service endpoint is needed to attach a private secret manager. This update exposes it. The default is public.
Release required?

[ ] No release
[ ] Patch release (x.x.X)
[ ] Minor release (x.X.x)
[ ] Major release (X.x.x)

Release notes content

Run the pipeline
If the CI pipeline doesn't run when you create the PR, the PR requires a user with GitHub collaborators access to run the pipeline.
Run the CI pipeline when the PR is ready for review and you expect tests to pass. Add a comment to the PR with the following text:
/run pipeline

Checklist for reviewers

[ ] If relevant, a test for the change is included or updated with this PR.
[ ] If relevant, documentation for the change is included or updated with this PR.

For mergers

Use a conventional commit message to set the release level. Follow the guidelines.
Include information that users need to know about the PR in the commit message. The commit message becomes part of the GitHub release notes.
Use the Squash and merge option.

/run pipeline

/run pipeline

Upgrade test failed because the endpoint_type changes from null to public. Running this on my own it appears that nothing is destroyed, but only updated in place. So this change shouldn't cause issues for users.
following symbols:
  ~ update in-place

Terraform will perform the following actions:

  # module.secrets_manager_group_acct.ibm_sm_secret_group.secret_group will be updated in-place
  ~ resource "ibm_sm_secret_group" "secret_group" {
      + endpoint_type   = "public"
        id              = "us-south/118fdb09-7551-4232-be12-0f5cca4c188b/dd8e034a-63b4-0099-cd46-fec7738b63c3"
        name            = "test-sm-sg-module-example-group"
        # (6 unchanged attributes hidden)
    }

Plan: 0 to add, 1 to change, 0 to destroy.```

Approve for upgrade test to be skipped

/run pipeline

:tada: This PR is included in version 1.2.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Release prep: update to the latest build conventions

Reviewer checklist

[ ] Ensure relevant issues are linked (description should include text like "Fixes #")
[ ] Ensure correct labels applied
[ ] Ensure any appropriate documentation has been added or amended

Coverage remained the same at 94.007% when pulling 91fc54bc5cc522f8354d9becda01345dbdff60f5 on release_prep into b0bad285b8c33a0ecc3980afaf4d09a3be321a63 on main.


🌟 [EPIC] Gradido Final

🌟 EPIC

This EPIC just collects all the tasks not assigned to a specific release Version

Multiple Addresses
Multiple Gradido Addresses for every user.
Only at one Address per user creation is possible, therefore we need a way to check on blockchain-level for which address creation is allowed.
Maybe with HD-Wallet technique from bitcoin.
Needed for

Equalization and Environmental Fund
Public Budget
GDT
multiple E-Mails and username as sender and receiver for transactions

Voting or blockchain based authentication
Normally the user sign there transaction with there private key.
But for transactions from Equalization and Environmental Fund and Public Budget it isn't possible.
When I use the same system, everyone how gets hands on private key can spend this money. Once they have access, it isn't possible to to permit it.
We need a system which is able to track the decision of the community how is responsible and when and how long to spent money from the Equalization and Environmental Fund and Public Budget on blockchain.
We don't now which system the community will be use, so better we make a system, which can support democracy, consens, consent, council and other forms which exist.
Needed for

Equalization and Environmental Fund
Public Budget

GDT
Think about a way to securly get GDTs into blockchain.
Depends on:

Multiple Addresses

@einhornimmond Thank you for writing down those Ideas! Can you make an Issue for each of them tho? That way we can assign them to a Release, Sprint and Person at a given time <3


support on laravel 5.2

Hi .
This is very good script. but is not support laravel 5.2.
How release it in laravel 5.2?
Thanks a lot.

Ok @yepco, I will update to support laravel 5.2

Any news on this? Are there any code changes or just an update to composer.json?

Please update to support laravel 5.2,
Thank you

Hi,
I am waiting for Laravel 5.2 .....

+1

I need it very hard

Hi @essivision, currenly we are busy in other projects. We will update it next few days.
Sorry for the inconvenience.

Hi, @huytbt, I am still waiting...
Thanks


Create new widget to help with NAF eligibility and FPL

The data team can't always calculate a patient's income vs FPL with the current brackets for income. I'm self assigning this to remind myself to add a column to the exportable file with FPL calculation for both (family size) and (family size + 1).

i know we're chatting in the slack about it now but tagging @deesriv

Dumping our convo from the slack thread @lomky @mdworken @colinxfleming @lwaldsc @NerdyGirl537
MKD [10:03 AM]
@lwaldsc after discussing some potential proposals with @lomky (which I'll write up a summary of for gitlab later), I'd like to propose we add checkboxes for FPL
The way I propose it would work would be after family size is entered
(and income is determined)
Then the toggles come alive, and the CM can enter for whether they're above or below FPL (which is a proxy for NAF eligibility per NNAF)
The toggles would be autofilled if the determination can be made with the current 5k increment brackets
The advantages of this are 1) avoid infosec problems with exact incomes, 2) maintain backwards compatibility of data (by not altering the collection practice), 3) should be easy to implement
How do you think CMs would feel about this potential addition?
lwaldsc [11:43 AM]
Quick thoughts bc I have to run to a meeting: I think CMs will adapt to anything we give them and this doesn't sound like too much of a departure from what we currently do. I would want @nerdygirl537 and @alisonnjones to weigh in from our data side before we make any big changes.
Also, I'm not exactly sure what this brings us. Is this just "the data itself cant determine exactly if they're below fpl so this checkbox will tell us if they are or not" or what are the purposes of the checkbox if we're getting (kinda) determining information anyway?
All around great thoughts! I just want to be sure we're collecting for a reason and not just making more work slash more awkward conversations for the CMs/patients for things we might not really need.
MKD [12:04 PM]
You'd have to ask @alisonnjones  regarding how important the better data is. Regarding awkward conversations I don't think it will add many as it goes with the same income data, info from it is just entered in 2 spots.
MKD [12:12 PM]
It will also help CMs as FPL is a rough measure of NAF eligibility, so the threshold being visible will help
alisonnjones [12:22 PM]
Yes so a couple of things - We have been and want to continue collecting # of people in household (minors/adults) and income level. We haven't been using this info much, and it doesn't help that the way the fields are configured now are not conducive to broader application (aka the brackets don't line up with calculating FPL). In my dream world, we would have a way to input this information in DARIA in real time that would calculate for the CM so that they could tell the caller whether they think they would be NAF eligible and be exportable on the back end for us to share with our community outreach teams and with our CM leadership. Our community outreach teams are new, and work to engage with other social work/direct service orgs in DC to better understand and advocate for the intersecting/multiple needs of our clients. And ultimately, it will be helpful for the CM leadership team to have to refine best practices and troubleshoot ways to be more responsive to callers. Finally, it will be helpful for our fundraising at an aggregate level to demonstrate the varying levels of need in our own communities around affording abortion care and bringing in more $ to help fill these gaps (esp for pts who are not NAF eligible but still high need/face barriers).
I see how this would entail a larger reworking than just relabeling the income brackets, but I don't know what kind of a lift goes into making my dream world idea come true. I understand if we need to hit pause and think about bundling this with other changes down the road. But, I do think it's worth some more discussion!
for example, in my dream world we'd also have tool tips/suggested language for how to best ask patients this information in a non-exploitative/responsible way to help with the awkward bluntness of what this kind of question gets at re: power imbalances.
MKD [12:28 PM]
I agree with all of this
One idea we had was replacing annual income or even monthly/weekly income with a question like: how much did you make last week
That generally gets way better data, but Kat was very concerned about bias given that the week before calling DCAF might be very non-representative
lomky [12:33 PM]
Yeah, considering discovery of pregnancy is associated with illness (making you miss work), or that they could be taking extra shifts in preparation for the cost of the procedure
MKD [12:33 PM]
We could also ask, how much did you make in the last week, how much do you make in a typical week
The first question would anchor the first which may or may not be desirable
alisonnjones [12:37 PM]
I might crowdsource this question with some folks at other funds to see if anyone has come up with a more equitable framing/phrasing. @lwaldsc did this come up on any other NNAF calls?
alisonnjones [12:44 PM]
we can also move this to the github thread @MKD started if that's easier than clogging up the slack chat
lomky [12:45 PM]
I think that might be best just so we don't. Lose it

@mdworken @alisonnjones what's the proposed action here?

I would love an estimate from the engineering team of what kind of lift this would entail and what the implications would be for the CSV export. Ideally, I would love to change the current fields in DARIA to FPL-relevant ranges that when you select that and enter in other info like minors/adults in household the FPL automatically calculates and NAF eligibility is automatically determined in the CM dashboard/pt profile (like how the current weeks text shows up now). But, I don't know how that would mess up all our current data in those fields and how much work it would be and how we could export it in a useful way.

@alisonnjones I believe the current proposal is something like the following:

leave the ranges as they stand (this is very important for backwards-compatibility of the data) and then to address FPL we'll have a few checkboxes, something like:
above FPL, below FPL, unspecified.
The checkboxes will become active after household size becomes available, and the cutoff will be provided in a very "noticeable" way.

*For the checkboxes, it will pre-check them if FPL can be determined from the income range/household size, and will be left as an option to the CM otherwise.

I know some people were going to consult CMs regarding this, I'll ping the slack for an update.

that would be great. and the proposed solutions sounds good to me

I'm all good with it as well.

Renamed to reflect what will actually change :)

Is this something we still want to do? @alisonnjones

@alisonnjones we probably don’t want to do this because NAF has actively
asked us not to during our most recent convos with them— but open to
others’ opinions!
On Sun, Apr 7, 2019 at 3:23 PM Colin<EMAIL_ADDRESS>wrote:

Is this something we still want to do? @alisonnjones
https://github.com/alisonnjones
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/DCAFEngineering/dcaf_case_management/issues/1387#issuecomment-480621313,
or mute the thread
https://github.com/notifications/unsubscribe-auth/Ac5jSFiFNmkALdsUZfq96fFE0byJ1EEuks5vekWsgaJpZM4SSl4m
.

I think we should close this thread. We explored different options (proxy
for FPL, calculator for NAF formula, etc.), but we really don't have the
info we need from NAF to make this possible and/or useful for case
management. Glad we explored it and did our due diligence, but let's move
on.
On Sun, Apr 7, 2019 at 5:40 PM deesriv<EMAIL_ADDRESS>wrote:

@alisonnjones we probably don’t want to do this because NAF has actively
asked us not to during our most recent convos with them— but open to
others’ opinions!
On Sun, Apr 7, 2019 at 3:23 PM Colin<EMAIL_ADDRESS>wrote:

Is this something we still want to do? @alisonnjones
https://github.com/alisonnjones
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<
https://github.com/DCAFEngineering/dcaf_case_management/issues/1387#issuecomment-480621313
,
or mute the thread
<
https://github.com/notifications/unsubscribe-auth/Ac5jSFiFNmkALdsUZfq96fFE0byJ1EEuks5vekWsgaJpZM4SSl4m
.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/DCAFEngineering/dcaf_case_management/issues/1387#issuecomment-480632242,
or mute the thread
https://github.com/notifications/unsubscribe-auth/Aa6vLfUMYJfnWF6hrxDHSACdAMvmEcWQks5vemXXgaJpZM4SSl4m
.

thanks all!


I installed TwigBridge, however it can't figure out view.engine.resolver

However, everytime I run the php artisan dump-autoload command, I get a {"error":{"type":"ReflectionException","message":"Class view.engine.resolver does not exist","file":"/www/sites/www.complete.com/vendor/laravel/framework/src/Illuminate/Container/Container.php","line":303}}
I am using Laravel 4.0.9

@niterain
What was your solution to this problem?

Sorry, renalpha.
I probably should have listed the fix here.  Sorry, I don't recall how I fixed it.


-- change

-- change

    1. Configure the sampling  channel during initialization

Considering the continuous mode, I configure the sampling  channel during initialization beorfe start conversion.


Added Senseloaf Resume Parser Provider

Added Senseloaf Resume Parser Provider.
To Use, add your credentials to settings file and run
from edenai_apis.apis.senseloaf.senseloaf_api import SenseloafApi
api = SenseloafApi()
result = api.ocr__resume_parser(file='path_to_file')

Hello @Rutvik-Trivedi ,
Thank you for your Pull request,
In order to review and merge your pull request quickly, can you please pull a more recent version of our code, and than update your pull request ? It will solve some conflicts and make it easier for us to review your code.

Hi @DninoAdnane , have updated the request

Thank you @Rutvik-Trivedi for you quick update, we will have a look at it and hopefully merge it as soon as possible

@coscialp Have created a fresh pull request #69 . Let me know if any problems are faced


Add cache dir config in configuration file.

This PR started as just adding a cache_dir option to the configuration file, but in the process I had to refactor some functions.
Mainly I moved some functionality for the cache inside the cache struct and let it own a PathBuf to the cache dir.
This fixes https://github.com/dbrgn/tealdeer/issues/156 .

@hgaiser Do you want to keep working on this, or can we reassign this if someone else comes along? (Both options are equally valid)

Ah sorry, I don't think I'll have time to work on this anytime soon. Feel free to reassign to someone else 👍

Yep makes sense! Sorry for not following up on this.

Note that I also have some thoughts in #266

Replaced by #276.

Note that I also have some thoughts in https://github.com/dbrgn/tealdeer/pull/266

Aaaah, I never saw that! Sorry very much about that 😞 I'll take a look at it, to see if we independently got to the same conclusions, or whether we can merge our approaches.


[release/8.0] Update to latest versions of dependencies

Not sure whether we want to take this right now.
Microsoft Reviewers: Open in CodeFlow

stackexchange.redis tests failing with SIGABRT. Let's try rolling that one back from 33 to 27

closing while we work this out in https://github.com/dotnet/aspire/pull/3590


Only works on v0.8.x?

i try to install it on Windows 8.1 x64, but i got so many errors :(
 Microsoft Windows [Versión 6.3.9600]
(c) 2013 Microsoft Corporation. Todos los derechos reservados.

 Para habilitar l
a compilación en paralelo, agregue el modificador "/m".
C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V120\Microsoft.Cpp.Platform.t
argets(64,5): error MSB8020: The build tools for Visual Studio 2012 (Platform T
oolset = 'v110') cannot be found. To build using the v110 build tools, please i
nstall Visual Studio 2012 build tools.  Alternatively, you may upgrade to the c
urrent Visual Studio tools by selecting the Project menu or right-click the sol
ution, and then selecting "Upgrade Solution...".    Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>install script.
npm ERR! This is most likely a problem with the mdns package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     node-gyp rebuild
npm ERR! You can get their info via:
npm ERR!     npm owner ls mdns
npm ERR! There is likely additional logging output above.
npm ERR! System Linux 3.16.0-31-generic
npm ERR! command "/usr/bin/node" "/usr/bin/npm" "install" "-g" "peercast"
npm ERR! cwd /home/dovaa
npm ERR! node -v v0.10.36
npm ERR! npm -v 1.4.28
npm ERR! code ELIFECYCLE
npm ERR! not ok code 0

so only work on v0.8.x?

I had te same issue i managed to fix it with the following steps

Install nw-gyp by running: npm install -g nw-gyp
Enter in the node_modules/peercast/node_modules/mdns folder of your node-webkit project
Run nw-gyp configure --target=0.12.2 (this target is the version of the node-webkit you have installed you can get your version by adding alert(process.versions['node-webkit']) and opening your app)
And finally run nw-gyp build

And now it works fine!

I know @watson is working on a js version of bonjour that will fix this


[cssnano/pwa] Cannot read property 'push' of undefined

Expected Behavior
Running yarn dev should not trigger any error on a fresh install.
Actual Behavior
Running yarn dev triggers an error TypeError: Cannot read property 'push' of undefined

Stacktrace
TypeError: Cannot read property 'push' of undefined
    at ModuleContainer.nuxtCssano (/Users/romuald/Private/base-backoffice/node_modules/@nuxtjs/cssnano/index.js:4:29)
    at /Users/romuald/Private/base-backoffice/node_modules/nuxt/lib/core/module.js:133:29
    at Promise (<anonymous>)
    at ModuleContainer._callee2$ (/Users/romuald/Private/base-backoffice/node_modules/nuxt/lib/core/module.js:132:12)
    at tryCatch (/Users/romuald/Private/base-backoffice/node_modules/nuxt/node_modules/regenerator-runtime/runtime.js:65:40)
    at Generator.invoke [as _invoke] (/Users/romuald/Private/base-backoffice/node_modules/nuxt/node_modules/regenerator-runtime/runtime.js:303:22)
    at Generator.prototype.(anonymous function) [as next] (/Users/romuald/Private/base-backoffice/node_modules/nuxt/node_modules/regenerator-runtime/runtime.js:117:21)
    at step (/Users/romuald/Private/base-backoffice/node_modules/nuxt/dist/nuxt.js:852:30)
    at /Users/romuald/Private/base-backoffice/node_modules/nuxt/dist/nuxt.js:863:13
    at <anonymous>
    at process._tickCallback (internal/process/next_tick.js:188:7)
[nuxt] Unhandled promise rejection: TypeError: Cannot read property 'push' of undefined

Steps to Reproduce the Problem

vue init nuxt-community/pwa my-app
cd my-app
yarn install
yarn dev

Specifications

Version: Nuxt version "1.0.0-rc3" - Vue CLI: 2.8.2
Platform: macOS Sierra 10.12.5

It seems this.options.build.postcss is now undefined
https://github.com/nuxt-community/modules/blob/master/modules/cssnano/index.js#L4
options is coming back as
{ performance: { gzip: false },
  head:
   { titleTemplate: '%s - Starter Website',
     meta: [ [Object], [Object] ],
     link: [ [Object] ],
     style: [],
     script: [] },
  loading: '~components/PageLoader.vue',
  css: [ '~assets/sass/main.sass' ],
  build:
   { vendor: [ 'lodash', 'axios' ],
     extend: [Function: extend],
     analyze: false,
     extractCSS: false,
     ssr:
      { cache:
         LRUCache {
           max: 10000,
           maxAge: 900000
         } },
     publicPath: '/_nuxt/',
     filenames:
      { css: 'common.[chunkhash].css',
        manifest: 'manifest.[hash].js',
        vendor: 'vendor.bundle.[chunkhash].js',
        app: 'nuxt.bundle.[chunkhash].js' },
     plugins: [ [Object], [Object], [Object] ],
     babel: {},
     postcss: undefined,
     templates: [ [Object] ],
     watch: [],
     devMiddleware: {},
     hotMiddleware: {} },
  cache: true,
  plugins:
   [ { src: '/Volumes/LaCie/GitHub/nuxt-express-symfony/.nuxt/workbox.plugin.33bce3ec.js',
       ssr: false },
     { src: '~plugins/VueCookie', ssr: false } ],
  router:
   { middleware: [ 'session' ],
     extendRoutes: [Function: extendRoutes],
     mode: 'history',
     base: '/',
     routes: [],
     linkActiveClass: 'nuxt-link-active',
     linkExactActiveClass: 'nuxt-link-exact-active',
     scrollBehavior: null,
     fallback: false },
  modules:
   [ '@nuxtjs/component-cache',
     [ '@nuxtjs/pwa', [Object] ],
     [ '@nuxtjs/axios', [Object] ],
     [ '@nuxtjs/google-analytics', [Object] ] ],
  manifest:
   { name: 'BW Starter Website',
     short_name: 'BWStarter',
     description: 'A starter de-coupled front-end/back-end website with common functionality including an admin login',
     lang: 'en',
     background_color: '#FFFFFF',
     theme_color: '#4770fb',
     icons: [ [Object], [Object], [Object] ],
     start_url: '/',
     display: 'standalone' },
  rootDir: '/Volumes/LaCie/GitHub/nuxt-express-symfony',
  dev: false,
  mode: 'universal',
  buildDir: '/Volumes/LaCie/GitHub/nuxt-express-symfony/.nuxt',
  nuxtAppDir: '/Volumes/LaCie/GitHub/nuxt-express-symfony/node_modules/nuxt/lib/app',
  generate:
   { dir: 'dist',
     routes: [],
     concurrency: 500,
     interval: 0,
     minify:
      { collapseBooleanAttributes: true,
        collapseWhitespace: true,
        decodeEntities: true,
        minifyCSS: true,
        minifyJS: true,
        processConditionalComments: true,
        removeAttributeQuotes: false,
        removeComments: false,
        removeEmptyAttributes: true,
        removeOptionalTags: true,
        removeRedundantAttributes: true,
        removeScriptTypeAttributes: false,
        removeStyleLinkTypeAttributes: false,
        removeTagWhitespace: false,
        sortAttributes: true,
        sortClassName: true,
        trimCustomFragments: true,
        useShortDoctype: true } },
  env: {},
  layouts: {},
  serverMiddleware: [],
  ErrorPage: null,
  transition: { name: 'page', mode: 'out-in' },
  render:
   { bundleRenderer: {},
     resourceHints: true,
     ssr: true,
     http2: { push: false },
     static: {},
     gzip: { threshold: 0 },
     etag: { weak: true } },
  watchers: { webpack: {}, chokidar: {} },
  srcDir: '/Volumes/LaCie/GitHub/nuxt-express-symfony',
  appTemplatePath: '/Volumes/LaCie/GitHub/nuxt-express-symfony/.nuxt/views/app.template.html',
  store: true }

I imagine it was an empty array before. Must be latest Nuxt RC. Depending on the next release date for now a hack is:
module.exports = function nuxtCssano(options) {
  if (this.options.build.postcss === undefined) {
    this.options.build.postcss = []
  }
  this.options.build.postcss.push(cssnano(options))
}

OR much smarter option is to define it in your nuxt.config.js
build: {
    postcss: []
}

Sorry for inconveniences during rc3 upgrade. cssnano 1.0.1 now works well with rc3

The issue persists on my side. Any idea how to solve it?

@bdebever Please make sure 1.0.1 is installed by checking node_modules/cssnano/package.json

Yes it is :/

@bdebever It is working fine with a clean rc3 setup. (https://glitch.com/edit/#!/nuxt-pwa) We can't help unless having a clear idea about your project's problem. Please provide exact error about your current "issues"

@bdebever, try running npm install @nuxtjs/cssnano@latest.  This will update your package.json and package-lock.json files and move them to ^1.0.1 (as of 8/2/17).

in rc8 i still have this problem even i have put this
build: {
postcss: []
}
and also i also tried npm install @nuxtjs/cssnano@latest
but it break my whole app, any idea how to solve it?

Thanks for the report. Actually with rc6+ cssnano is enabled vy default. I'll reopen until release the patch.

Hmm seems cssnano was already disabled with workbox! @gfriend-malaysia Would you please upgrade to latest version on pwa?

@pi0 after upgrade to latest version of @nuxtjs/pwa the error have resolve, Thank you and appreciate your help 👍


Custom dots container not working

When I try to use a custom dots container using dots props it always uses the default dots container
Changing the validation when initializing the glider works for me, I'm not sure if it's the definitive solution:

I created a demo that uses a custom dots container: https://codesandbox.io/s/react-glider-demo-with-dots-qxcd2l
Let me know if that clarifies the issue.

Applying the dots container as in the demo works perfectly, thank you very much


AVI Vault link does not contain reference to 20.1.7 anymore

The instructions for obtaining Avi 20.1.7 says to navigate to vault page, however 20.1.7 is not there anymore.  Perhaps direct user to find OVA at https://marketplace.cloud.vmware.com/services/details/nsx-advanced-load-balancer-1?slug=true.

This is fixed as part of c77048d89a2a69c84ebf4d75c059efb4f2c74252 commit. Hence closing the issue.


[issue]

Describe the bug
A clear and concise description of what the bug is.
Useful debug information from command line
If applicable, add output from command line to help explain your problem.
Remember to use "```" to surround the code block.
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):

OS: [e.g. Ubuntu 18.04]
Version of SVL [e.g., 2021.03]

Additional context
在下载maps.zip时总是下载失败

Duplicate of #54


Boot Unikraft with Qemu

Use the file initrd in the QEMU initrd cli option in case of Unikraft
If the user gives us a Unikraft unikernel, we will use the file /initrd in the container rootfs for the initrd option in QEMU cli. In any other case, we can use the previous approach, where the image from the devmapper was used.
Check if initrd file exists before using it. If the file /initrd does not exist, we should simply do not use the initrd cli option in QEMU and try to boot the Unikernel.

Fixes: #6

superseded by #18


[sp] implement "add block to current pipeline"

Summary

users can now re-add an existing block back to a pipeline via the file editor

Tests

cc: @johnson-mage @tommydangerous @dy46

unbold the button text

unbold the button text

@johnson-mage Updated button styling:


Fix for PWM on Beaglebone black with a kernel > 3.8.13

Tested on hardware (Beaglebone black Rev B6)

Thanks for the contribution! Is this a debian thing or global? I've never seen such a thing and edison for example has a 3.10 kernel? I'd like to understand if this is a beaglebone thing or general?

I have only seen this on the Beaglebone black with Debian and Ubuntu.
I don't know if the Beaglebone is the only board concerned or if it's an Linux on ARM thingy, sorry I don't have an answer.

Ok I unfortunately don't have a BBB, @tingleby do you think you could take a look?

@cosscat is this something you could help with if you have a board?

I don't have BBB either, but I've found this nice description: https://github.com/szmoore/MCTX3420/wiki/Software:-PWM-Control and looks like the standard sysfs location is actually just a secondary mean to use PWMs on BBB and the one that doesn't follow the kernel documentation fully (dropping the pwmchip piece).

I believe this should rather be reworked using _replace approach, as this is specific to one board we support. @SyrianSpock, do you think you'd want to do that?

@alext-mkrs Sure, I'll do it ASAP.

Thanks and no rush :smile: I just believe this is a better way to go and looking at the code and @arfoll's comments I think it will increase its chances for merging.

So @SyrianSpock, would you be willing to modify this one as requested?


xPackage: ReturnCode only excepts positive values

I have a package that uses a non-msi EXE for installation.  It's return codes use negatives as errors
I want to add
ReturnCode                 =  @( 0, 1641, 3010, -29 )

Details of the scenario you tried and the problem that is occurring
Installing Kaseya.  Installer returns a -29 when already installed.
Verbose logs showing the problem
xPackage Cannot convert value \"-29\" to type \"System.UInt64\". Error: \"Value was either too large or too small for a UInt64.\"

Suggested solution to the issue
        # Return codes 1641 and 3010 indicate success when a restart is requested per installation
        [Parameter()]
        [ValidateNotNullOrEmpty()]
        [System.UInt32[]]     <--  CHANGE TO [System.Int32[]]
        $ReturnCode = @( 0, 1641, 3010 ),

The DSC configuration that is used to reproduce the issue (as detailed as possible)
# insert configuration here
        xPackage Kaseya {
            #-29
            Ensure                     = "Present"
            Name                       = "Kaseya"
            Path                       = "C:\kaseya_temp\Kaseya.exe"
            ProductId                  = ""
            Arguments                  = "/s"
            CreateCheckRegValue        = $true
            InstalledCheckRegKey       = "SOFTWARE\WOW6432Node\Kaseya\Agent\KSAASS01544753921945"
            InstalledCheckRegValueName = "Provider"
            InstalledCheckRegValueData = "Kaseya"
            ReturnCode                 =  @( 0, 1641, 3010, -29 )
            DependsOn                  = "[xRemoteFile]KaseyaDownload"
        }

The operating system the target node is running
OsName               : Microsoft Windows Server 2016 Datacenter
OsOperatingSystemSKU : DatacenterServerEdition
OsArchitecture       : 64-bit
WindowsBuildLabEx    : 14393.3564.amd64fre.rs1_release.200303-1942
OsLanguage           : en-US
OsMuiLanguages       : {en-US}
Version and build of PowerShell the target node is running
Name                           Value

PSVersion                      5.1.14393.3471
PSEdition                      Desktop
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0...}
BuildVersion                   10.0.14393.3471
CLRVersion                     4.0.30319.42000
WSManStackVersion              3.0
PSRemotingProtocolVersion      2.3
SerializationVersion           <IP_ADDRESS>
Version of the DSC module that was used
Script     9.1.0      xPSDesiredStateConfiguration

Hi @ChristopherGLewis - from a technical perspective, this should be fine I think. The MOF would also need to be changed etc.
This shouldn't be a breaking change.


allow assignment within JaggedArray by boolean or integer indexing

JaggedArray.__getitem__ allows for retrieving part of the array based on advanced indexing, but __setitem__ currently does not allow assignment of array contents in the same way (which is possible for numpy.ndarray). I've added this functionality to JaggedArray. It's necessary for some of the array manipulations I've needed--specifically, to convert from an integer index array to an equivalent boolean mask.

This is a hard one for me to answer—I explicitly removed this functionality in an early version of awkward-array because providing it for all array types leads to some confusing situations. You can probably still find a branch named "last with setitem" or something.
I have, however, been thinking of reintroducing it in awkward 1.0, so maybe we can quietly reintroduce it now. I don't want to be in a position where I have to explain odd behaviours due to out-of-order starts and stops or something. I think I can make the behavior sane with the "high level" view that version will be adding.
When I had a specification, it explicitly said "not supported," but I have removed that. I wonder if we can say this is an existing but not supported feature? I don't think that would fly...

I'm curious about the functionality that is not possible without this.  Can you show an example?

Here's an example of reducing over three axes in Numpy:
>>> a = numpy.ones((2, 3, 4), dtype=int)
>>> a
array([[[1, 1, 1, 1],
        [1, 1, 1, 1],
        [1, 1, 1, 1]],

       [[1, 1, 1, 1],
        [1, 1, 1, 1],
        [1, 1, 1, 1]]])
>>> a.sum(axis=0)
array([[2, 2, 2, 2],
       [2, 2, 2, 2],
       [2, 2, 2, 2]])
>>> a.sum(axis=1)
array([[3, 3, 3, 3],
       [3, 3, 3, 3]])
>>> a.sum(axis=2)
array([[4, 4, 4],
       [4, 4, 4]])

Here's a version with some zeros:
>>> b = numpy.array([[[1, 1, 1, 1], [1, 1, 1, 0], [1, 1, 0, 0]], [[1, 0, 0, 0], [0, 0, 0, 0], [0, 0, 0, 0]]])
>>> b
array([[[1, 1, 1, 1],
        [1, 1, 1, 0],
        [1, 1, 0, 0]],

       [[1, 0, 0, 0],
        [0, 0, 0, 0],
        [0, 0, 0, 0]]])
>>> b.sum(axis=0)
array([[2, 1, 1, 1],
       [1, 1, 1, 0],
       [1, 1, 0, 0]])
>>> b.sum(axis=1)
array([[3, 3, 2, 1],
       [1, 0, 0, 0]])
>>> b.sum(axis=2)
array([[4, 3, 2],
       [1, 0, 0]])

Now what if instead of zeros, we had gaps...
>>> c = awkward.fromiter([[[1, 1, 1, 1], [1, 1, 1], [1, 1]], [[1], []], []])
>>> c
<JaggedArray [[[1 1 1 1] [1 1 1] [1 1]] [[1] []] []] at 0x78e211da4400>

Note that I did emptiness three different ways: (1) I turned a [0, 0, 0, 0] array into an empty array; (2) I eliminated it entirely, so nothing instead of []; (3) I added an empty array at a higher level of nesting.
It's clear what an axis=-1 summation should be because for all the irregularity of this array, the deepest level of arrays can be replaced with scalars, no matter how many of those there are. This axis=-1 summation is what JaggedArray.sum does:
>>> c.sum()
<JaggedArray [[4 3 2] [1 0] []] at 0x78e212497588>

Compare this to
>>> b.sum(axis=-1)
array([[4, 3, 2],
       [1, 0, 0]])

The first row is the same because nonexistent elements are equivalent to zeros in summation and we haven't dealt with any of the tricky empty cases. The second row is different because while [] sums to 0, nothing sums to nothing, not 0. And then the jagged array has a third row, which is empty, corresponding to the empty array I stuck in there at the middle nesting level.
So we have axis=2 covered, but what about axis=1? Drawing it out to make the nesting clear,
[
 [
  [1, 1, 1, 1],     # first "block"
  [1, 1, 1],
  [1, 1]
 ],

 [
  [1],              # second "block"
  []
 ],

 [
                    # third "block"
 ]
]

an axis=1 sum means summing downward, such that the first row becomes [3, 3, 2, 1] (see where they line up in that first block?), just like the first row of b.sum(axis=1). Following the same procedure, the second row becomes [1], corresponding to the [1, 0, 0, 0] second row of b.sum(axis=1). But is there a third row? If so, is it []?
 As a reminder,
>>> b.sum(axis=0)
array([[2, 1, 1, 1],
       [1, 1, 1, 0],
       [1, 1, 0, 0]])

For the flat array b, the 2 in the top-left slot of b.sum(axis=0) is because two of the blocks have a 1 in the top-left slot. But for the jagged array, it's not clear how to align the rows and columns of the blocks to one another because they have different numbers of elements.
That's why I decided some time ago that we can't make sense of axis != -1 when jaggedness is involved. But looking at it now, we can make a consistent definition: slide all inner arrays to the leftmost and topmost and expand them with the reducer's identity to the smallest common size, then use Numpy's definition. With something like that, a jagged array of Muon_pt would have
Muon_pt.max(axis=0)

give you an n-element array, in which n is the maximum number of muons in the dataset, with the first slot showing the maximum first muon in each event, the second showing the maximum second muon in each event, etc. That could be useful.
In awkward 1.0, when this is done in C++, we can have a reasonable implementation of an output array that grows each time we see a larger inner array (using std::vector's push_back, probably). In awkward 0.x, I think we'd have to use things like
>>> c.pad(c.flatten().counts.max(), axis=1).fillna(0).pad(c.counts.max(), axis=0).fillna(0)
<JaggedArray [[[1 1 1 1] [1 1 1 0] [1 1 0 0]] [[1 0 0 0] [0 0 0 0] [0 0 0 0]]] at 0x7f03145497f0>

before running Numpy's sum with an axis, which is a potential memory hog...

I'm curious about the functionality that is not possible without this. Can you show an example?

It's the "convert from an integer index array to an equivalent boolean mask" thing. The reason why I actually need this conversion is because I need the complement of an integer-indexed selection. I get the integer index array from a complicated set of steps acting on argcross() pairs, but the blocking problem boils down to this conversion. For example:
>>> import awkward
>>> a = awkward.fromiter([[1], [2, 3], [4, 5, 6]])
>>> int_indices = awkward.fromiter([[], [0], [0, 2]])
>>> a[int_indices]
<JaggedArray [[] [2] [4 6]] at 0x7fc6b15e7da0>

What I want is all elements not in a[int_indices]. My solution is:
>>> bool_array = a.ones_like().astype(bool)
>>> bool_array[int_indices] = False
>>> a[bool_array]
<JaggedArray [[1] [3] [5]] at 0x7fc6b1595898>

Another possible solution:
>>> tmp = a.localindex.cross(int_indices, nested=True)
>>> a[(tmp.i0 != tmp.i1).all()]
<JaggedArray [[1] [3] [5]] at 0x0001108c8c50>

but I am wondering, is the sequence of steps acting on argcross pairs trying to choose valid decay combinations?  I have been thinking a bit about how to work with argchoose() and some sort of composite candidate structure to assist with these sorts of operations.  Would be interesting to see what you came up with for this.

(I believe Jim's comment is about #166 and not this PR, but I think I agree with everything here.)

but I am wondering, is the sequence of steps acting on argcross pairs trying to choose valid decay combinations? I have been thinking a bit about how to work with argchoose() and some sort of composite candidate structure to assist with these sorts of operations. Would be interesting to see what you came up with for this.

The pairs are of a jet and a truth particle (an LLP). There are conditions on the kinematics of the individual jet, the properties of the individual LLP, and the deltaR between them. The four-vectors of all jets and LLPs are in JaggedArrays, and other LLP properties are in other JaggedArrays. I need to access all pairs (jet+LLP) that pass selection, as well as all jets that are not in a valid pair with any LLP.

I simplified things a bit and made this work for some exotic cases like out-of-order starts/stops (at least for JaggedArrays with two dimensions).

The tests look good. I think the best thing to do is to accept it but not claim to support it. None of the documentation says you can assign to a JaggedArray, and in several places it says you can't. This can only assign to a JaggedArray in a very specific situation that has no Numpy equivalent.
The reason I'm taking it instead of encouraging Mason to use Nick's purely functional solution is because this is a way to learn what the desire paths are. Mason can tell me if this turns out to have been a good idea and it can be ported and possibly generalized to awkward 1.0.
There are some awkward classes that will never have a __setitem__, such as VirtualArray. Users who rely on assignment may be surprised when they can't assign to a lazy array, but I guess that's what the error message will say.


Route paths with leading digits break file-based route generation

Describe the bug
When using file-based routing with the Vite plugin, route paths with leading digits (like /500/index.route.tsx) result in invalid variable names.
Example build output:
♻  Generating routes...
SyntaxError: An identifier or keyword cannot immediately follow a numeric literal. (6:22)
  4 |
  5 | import { Route as rootRoute } from './routes/__root'
> 6 | import { Route as 500IndexRouteImport } from './routes/500/index.route'

Your Example Website or App
https://stackblitz.com/edit/github-19bjij?file=README.md
Steps to Reproduce the Bug or Issue

Open the example
Wait for the install and build to finish
Notice the error output in the consoleinstallation

Expected behavior
The generated variable names are prefixed with a valid leading character, resulting in valid variable names.
Screenshots or Videos
No response
Platform

OS: macOS

Additional context
No response

See also : https://github.com/TanStack/router/discussions/1013#discussioncomment-8237205


use an initContainer to inject secrets as /run/secrets/xx

What I did
For service with secret bindings, define an initContainer to get secrets from Secret Store and share them as /run/secrets/ files to mimic docker secrets management and make application code portable
When stored secret is a key:value map, create secrets as sub-folders for each entry. Otherwise (blob) dump the whole secret content into /run/secrets/<name>
sample compose file:
  backend:
    image: ndeloof/backend
    build: backend
    secrets:
      - foo_bar

secrets:
  foo_bar:
    name: "arn:aws:secretsmanager:eu-west-3:xxx:secret:foo_bar"
    external: true

application code:
        const f = "/run/secrets/foo_bar/foo"
	secret, err := ioutil.ReadFile(f)
        fmt.Fprintf(w, "my secret stored under %s is %q", f, string(secret))

Related issue
closes #207
(not mandatory) A picture of a cute animal, if possible in relation with what you did

This seems fine but should the Compose spec have an allowance for this model of hierarchical secrets?

@justincormack good point, I'll propose a clarification in the compose spec, could apply to Kubernetes secrets as well

Investigating https://github.com/docker/ecs-plugin/issues/208, I noticed creating a Secret as CloudFormation resource, passing the file content as SecretString, a plain text secret is created on Secret Manager.
As a side effect, those two approaches are incompatible : user to reference a JSON file as secret will expect this file being fully exposed in container, not split by top-level entries.
A possible workaround is to introduce x-aws-key in secrets definition, to select key in an existing AWS (JSON formatted) secret. Otherwise the secret would be considered plain text. Would it make sense @justincormack ?

@chris I updated this PR to apply the proposed approach from https://github.com/compose-spec/compose-spec/issues/93
Can be used to illustrate this proposal during community meeting (and demo ECS plugin by the way :P)


Updated index.d.ts width from null to undefined

Undefined would be better suited than null.

The ? already signifies undefined and null has special meaning here, see docs:

Full width of the progress bar, set to null to use automatic flexbox sizing


How did you get the pretrained models?

Hi,
I'm wondering how are the pre-trained models obtained? For example, when I'm loading the pre-trained model for resnet18, is this pre-trained model trained using imagenet or still cifar? Thanks!

Hi Zhaowei,
I am not the repository creator nor a contributor, but I have used the repository in the past. To my knowledge all the pre-trained models made accessible by the code in this repo were trained on all the classes of the CIFAR10 dataset. If you wanted to use this repo to train your own models with your own hardware it would train on CIFAR as well. Hope I answered your question!

Hi Zhaowei,
I am not the repository creator nor a contributor, but I have used the repository in the past. To my knowledge all the pre-trained models made accessible by the code in this repo were trained on all the classes of the CIFAR10 dataset. If you wanted to use this repo to train your own models with your own hardware it would train on CIFAR as well. Hope I answered your question!


Update the link to the single worksheet

Changes
The single worksheet has been updated.
This swaps out the link to the previous version of the single worksheet for the updated one.
Checklist

[x] Attach this pull request to the appropriate card in Trello.
[x] Update the CHANGELOG.md if needed.

 Add the new link to the single worksheet to the application


SiteTree, Sort Problem in savetreenode or updatetreenodes

Hello,
we have a bug in the functions savetreenode or updatetreenodes, when we sort the SiteTree the moved element switched to the last position of the list. And the GET Method from updatetreenodes hast Null value for NextID every time.
Not sure which version we use, because version file is empty.

@leonardpiltz Sounds like a similar issue to https://github.com/silverstripe/silverstripe-framework/issues/4137, have you tried updating to 3.1.15 of both framework and CMS?

There was a unsuccessful try to update.
I'll try your workaround and retry an update

@leonardpiltz Okay, I’ll close this then :)


Tests required to verify changes in opensearch-env

About PR #875, tests(starting multiple instances with deb/rpm packages after override the value of OPENSEARCH_PATH_CONF manually) are needed to verify this PR changes and edge cases.

@xuezhou25  @dblock the distribution tests cover this particular functionality pretty well but we don't run them now, see please [1]
[1] https://github.com/opensearch-project/opensearch-build/issues/1572


Drawable turns white when deployed on phone

The preview tab in android studio shows the drawable image but when it is deployed on device there is no kenBurnsView its white completely as if its not present

this issue was caused because image resolution


Header (experimental)

Changes

Playing around with new design for the Header pattern, based on some lovely mocks from the design team. Posted to save for later, and for feedback/discussion.

Not ready for merge. :rotating_light:
Screenshots

:skull:


AE: confirmed Proteus bug when switching characters with HDT-SMP features

phenderix — 25/02/2022
[...] I have a question regarding how to toggle HDT-SMP on and off. My mod PROTEUS seems to crash sometimes when switching to characters that have HDT SMP hairstyles or tails. [...]
DaydreamingDay — 25/02/2022
[...] I don't know how you switch to another character, do you change the "skeleton" of the PC? If it is the case, we might have a conflict, as we maintain a state of the current skeletons. There are events in the game about changing the skeleton/head/armor of the PC/NPCs, do you use them?
phenderix — 25/02/2022
[...] I use a couple functions from RaceMenu CharGen to control loading appearance, the LoadCharacter and LoadCharacterPreset ones.  It actually works sometimes but crashes other times, specifically when HDT hairs or  tails are being used. [...] The skeleton is the same but it does toggle races for NPCs and change them via script
DaydreamingDay — 25/02/2022
I'm not familiar with RaceMenu code, would you have some link to it?
phenderix — 25/02/2022
It's contained within the modders package misc file on the RaceMenu page on the Skyrim Nexus. It is a SKSE DLL so not super transparent.
github is here for it: https://github.com/expired6978/SKSE64Plugins

Phenderix is Proteus author.
Currently, I consider that there might be a need to synchronize (lock) between RaceMenu and FSMP.
A temporary dirty fix would be to expose an API allowing to stop and start physics management by FSMP; that API would be used by client mods like Proteus, not RaceMenu.

Not reproduced on SE.


Test if user details load correctly.

qesmat haye khali bejaye none , khate tire gozashte she

avataram doros kon yohahahahaaaaaa

done


Update upstream

Would this be safe to push? How do you think I should test this.

Why do we need latest from upstream?  Is it possible to apply your change to our out of date fork instead?  It seems like a lot of changes, and if we aren't getting benefit from including these changes, then I think we should play it safe and not take them (we are moving off completely soon)

derp. You're right @dfuentes https://github.com/Clever/logspout/pull/4


feature/fix-no-repository-found:

moved error message if there is no repository loaded to vscode console

Fixes error message on VS Code:

Error: warning: Not a git repository. Use --no-index to compare two paths outside a working tree usage: git diff --no-index []   Diff output format options -p, --patch generate patch -s, --no-patch suppress diff output -u generate patch -U, --unified[=] generate diffs with  lines context -W, --function-context generate diffs with  lines context --raw generate the diff in raw format --patch-with-raw synonym for '-p --raw' --patch-with-stat synonym for '-p --stat' --numstat machine friendly --stat --shortstat output only the last line of --stat -X, --dirstat[=<param1,param2>...] output the distribution of relative amount of changes for each sub-directory --cumulative synonym for --dirstat=cumulative --dirstat-by-file[=<param1,param2>...] ...


/v1/deregister-application to be added to MANAGEMENT port of subscriptions

We have few subscriptions in RO namely /v1/notify-deregistrations, /v1/notify-approvals and /v1/notify-withdrawn-approvals which shall create new http-c, tcp-c and op-c for a new application to RO is trying to subscribe.
(reference issue : https://github.com/openBackhaul/RegistryOffice/issues/344 - conversation for having subscriptions to create new ltp instances)
Problem:
As per current design, if we need to deregister these subscribed application, a direct hit of /v1/deregister-application shall only delete http-c, tcp-c and op-c and not fc-port created under Subscription forwarding-constructs like DeregistrationNotification, ApprovalNotification and WithdrawnApprovalNotification.  For deleting fc-port, we would /v1/end-subscription should be triggered first followed by /v1/deregister-application.
Proposal:
I hope, /v1/deregister-application shall be deleting all the instances of ltp and fc-port instances in config file irrespective of subscriptions. Also, if any application accidentally triggering /v1/deregister-application before /v1/end-subscription, the corresponding fc-ports will be left behind.
Also, as per above case, even if we directly trigger /v1/deregister-application, fc-ports under  DeregistrationNotification, ApprovalNotification and WithdrawnApprovalNotification shall also be deleted.
Including management port for /v1/deregister-application - ro-2-0-1-op-s-is-002 to forwarding-constructs DeregistrationNotification, ApprovalNotification and WithdrawnApprovalNotification would solve this problem
Kindly let us know your views.

Closing this issue as it would be followed up in https://github.com/openBackhaul/ApplicationPattern/issues/686 because the issue is more generalized for updating services in ApplicationPattern