added tailwindcss to deps, including yarn.lock

Project was missing tailwindcss dependency so it wouldn't start. I also included yarn.lock as there was no lockfile present at all. Let me know if that was intentional and I can remove that and resubmit the PR.

Hi
My local set up only needed astro/tailwind in devDependencies and seems a few other people are fine also. But I am happy to add tailwindcss to dependencies if that makes it smoother for everyone to use the project.
However, I prefer not to commit lockfile in the git repo, if that is okay for you to resubmit.
Thanks a bunch!

I'll check again and see if adding tailwind into devDeps works and submit it there if so if that's your preference. It wasn't in devDeps in the repo either, so I think it needs to be somewhere, devDeps or deps, whichever makes sense.
I'll also remove the lock file and resubmit. I'll try to get that done in the next couple of days.

It is in the devDeps. See https://github.com/slamethendry/TinyRocket/blob/main/package.json, line 15.
"@astrojs/tailwind": "^5.0.0",
But I do not use yarn at all so I cannot check with yarn. And I don't know enough why it did not start for you.
Cheers.

I think that devdep is only for the Astro integration with tailwind, it doesn't include tailwind itself, which is why I didn't start for me. When I stamped out this template it wouldn't start until I added Tailwind as a dep. I'll double-check, though, before I resubmit the PR.

Just for completeness' sake, here's the error I see after running yarn install and yarn dev on the repo's main branch:
❯ yarn dev
yarn run v1.22.19
$ astro dev
10:00:06 AM [vite] Error when evaluating SSR module /Users/mitch/Dev/reference-only/astro-blog-template-personal-eval/tiny-rocket/astro.config.mjs: failed to import "@astrojs/tailwind"
|- Error [ERR_MODULE_NOT_FOUND]: Cannot find package 'tailwindcss' imported from<EMAIL_ADDRESS>    at new NodeError (node:internal/errors:405:5)
    at packageResolve (node:internal/modules/esm/resolve:887:9)
    at moduleResolve (node:internal/modules/esm/resolve:936:20)
    at defaultResolve (node:internal/modules/esm/resolve:1129:11)
    at nextResolve (node:internal/modules/esm/loader:163:28)
    at ESMLoader.resolve (node:internal/modules/esm/loader:835:30)
    at ESMLoader.getModuleJob (node:internal/modules/esm/loader:424:18)
    at ModuleWrap.<anonymous> (node:internal/modules/esm/module_job:77:40)
    at link (node:internal/modules/esm/module_job:76:36)

[astro] Unable to load your Astro config

node:internal/process/promises:288
            triggerUncaughtException(err, true /* fromPromise */);
            ^

[Failed to load PostCSS config: Failed to load PostCSS config (searchPath: /Users/mitch/Dev/reference-only/astro-blog-template-personal-eval/tiny-rocket): [Error] Loading PostCSS Plugin failed: Cannot find module 'tailwindcss'
Require stack:
- /Users/mitch/Dev/reference-only/astro-blog-template-personal-eval/tiny-rocket/postcss.config.cjs

(@/Users/mitch/Dev/reference-only/astro-blog-template-personal-eval/tiny-rocket/postcss.config.cjs)
Error: Loading PostCSS Plugin failed: Cannot find module 'tailwindcss'
Require stack:
- /Users/mitch/Dev/reference-only/astro-blog-template-personal-eval/tiny-rocket/postcss.config.cjs

(@/Users/mitch/Dev/reference-only/astro-blog-template-personal-eval/tiny-rocket/postcss.config.cjs)
    at load (file:///Users/mitch/Dev/reference-only/astro-blog-template-personal-eval/tiny-rocket/node_modules/vite/dist/node/chunks/dep-bb8a8339.js:36429:11)
    at file:///Users/mitch/Dev/reference-only/astro-blog-template-personal-eval/tiny-rocket/node_modules/vite/dist/node/chunks/dep-bb8a8339.js:36454:16
    at Array.map (<anonymous>)
    at plugins (file:///Users/mitch/Dev/reference-only/astro-blog-template-personal-eval/tiny-rocket/node_modules/vite/dist/node/chunks/dep-bb8a8339.js:36453:8)
    at processResult (file:///Users/mitch/Dev/reference-only/astro-blog-template-personal-eval/tiny-rocket/node_modules/vite/dist/node/chunks/dep-bb8a8339.js:36523:14)
    at file:///Users/mitch/Dev/reference-only/astro-blog-template-personal-eval/tiny-rocket/node_modules/vite/dist/node/chunks/dep-bb8a8339.js:36647:14]

Node.js v18.17.1
error Command failed with exit code 1.

It's possible (IIRC) that if you're managing this repo on your machine and any parent directory has Tailwind installed that it could be satisfying the dependency from that parent directory and you won't see this error on your side. I keep my repos entirely separate from others so when I stamped this repo out from the template, it comes down "clean". I keep it outside any other repo in its directory hierarchy which might be allowing this error to come through.
Note that other Astro templates that use tailwind do include the tailwind dep in their package.json, so you might have something "interesting" going on with your setup.

This is really interesting. I tested with npm instead of yarn just to make sure the problem was present on both sides and npm installs tailwind as a dependency of @astro/tailwind so the problem doesn't show up at all there. That's likely why you're not seeing this issue, given that you don't use yarn. I've never seen this kind of discrepancy between package managers before. Let me dig a touch more. Since you don't include package-lock.json in your repo, yarn can't use that as a basis to migrate to yarn and build its yarn.lock file, so it's missing that dependency on its own. Very strange.

I just modified the upstream branch and removed yarn.lock, rebased and force-pushed the branch.


FPGA: Add new jsons

Add dino-aurora and smmu jsons

We removed something from the json so that the Dino class is not created. So technically the dino in the name is not correct.


Add checkstyle maven plugin to enforce code formatting style guidelines

Resolved by commit https://github.com/uber/hudi/commit/788e4f2d2eeeeee685b9f5d2e09b56be230e34d4


@conda-forge-admin, please re-render

@conda-forge-admin, please re-render.

Hi! This is the friendly automated conda-forge-webservice.
I just wanted to let you know that I rerendered the recipe in conda-forge/freeimage-feedstock#5.

Stale so closing.


APIs that are not available to extensions should be marked with NS_EXTENSION_UNAVAILABLE

Description
We want to build an iMessage extension (available only in iOS 10+ and Xcode 8+) using React native. Cocoapods made some fixes in their 1.1.1 version that is causing React native pod integration to fail in iOS extensions. Here  is the issue logged against Cocoapods.
In summary, Cocoapods made fixes to correctly check that the pods have marked "its APIs that don't work for extensions as NS_EXTENSION_UNAVAILABLE". This change has disabled us from using the React native pod in iOS extensions.
The errors are

sharedApplication" is unavailable on iOS(App Extension) - Use view controller based solutions when appropriate

Reproduction
I dont have sample project and can work on getting one if necessary
Additional Information

React Native version:0.34
Platform: iOS
Operating System: MacOS
Image of errors

Thanks for filing the issue. This seems like something that should be fixed. Do you have a list of the particular APIs that need to be marked in this manner?

Closing this issue as we haven't heard back from the author.

I have created multiple PRs for this purpose and one of them is pending.. Some got checked in and one of them is still pending. Let me go and see if I can find it. But I have been working around this by creating my own fork of react-native and pointing to it from my project

Thanks for letting us know! I didn't see them here. Can you update your PRs to mention this issue? That way they'll automatically close this issue when they're merged. It also helps others see that a particular issue may already have a proposed fix in the pipeline.

Accepted PRs:
https://github.com/facebook/react-native/pull/13328
https://github.com/facebook/react-native/pull/13227
Pending PR:
Still need some time to find it as I think I created it from a different profile

https://github.com/facebook/react-native/pull/14263 . Turns out this was closed due to some concern about wrapping APIs this fashion. It would be awesome if you could pursue an alternative way of fixing this issue so that I can upgrade to the facebook's react-native version, instead of using my forked version
Thanks for follow  up


Adding sample primary-text-card-stock-bitcoin-feed

Q
A

New sample?
yes

What's in this Pull Request?

Adding a new sample which would display real time last trade price of US stocks, forex and crypto with the help of finnhub APIs

Hi @kunj-sangani - thx for the submission here and sorry for the delay on processing this PR. Setup looks really good and such a typical requirement for customers to have either a stock web part or an ACE for this.
Would you be available for doing a demo on this sample within upcoming community call? - This could be 10 min demo so in a call with total of 3 demos showcasing the model, API call and the automatic card update.
Right now we would have demo spots on the following calls: 17th of Nov, 15th of December or 29th of December. Please let me know what would work for you and we'll get you confirmed on the demo spot. Thx.

Hi @VesaJuvonen
Thank you for the opportunity. I would like to demo this sample on the 15th of December

Hi @kunj-sangani - we have added you on the agenda for the 15th of December call. Looking forward 👏👍🙏


Need a mechanism to serialize and deserialize records into bytes

Description:
The protobuf Any type represents data in bytes [1]. Currently, in Ballerina, we can send data types like strings since strings have mechanism to convert it to bytes. In gRPC, we represent messages as records.
Hence, we need a mechanism to serialize and deserialize these record types into bytes in order to support record as an Any data type.
[1] : https://developers.google.com/protocol-buffers/docs/proto3#any
Related Issues (optional):
https://github.com/ballerina-platform/ballerina-lang/issues/21146

Seem the original issue is fixed with the anydata type.


Plugin issue: Getting TS4023 when importing TypeParam from @pothos/core in helper functions for schema builder

We created a pagination plugin for Pothos with custom logic.
It also includes:
rootBuilderProto.fieldWithPagination = function (fieldOptions) {
  const { typeWithAggregationRef, paginationArgsGroup } = usePaginationBuilder({
    builder: this.builder,
    arg: this.arg,
    type: fieldOptions.type,
  });

  return this.field({ ...fieldOptions, type: typeWithAggregationRef, args: { ...paginationArgsGroup } } as never);
};

Object.defineProperty(rootBuilderProto, 'input', {
  get: function getInputBuilder(this: RootFieldBuilder<SchemaTypes, unknown>) {
    return new InputFieldBuilder(this.builder, 'InputObject', `UnnamedWithInputOn${this.typename}`);
  },
});

that uses helper:
import { ArgBuilder, SchemaTypes, TypeParam } from '@pothos/core';
import { upperCaseFirst } from 'upper-case-first';

type UsePaginationBuilderArgs = {
  builder: PothosSchemaTypes.SchemaBuilder<SchemaTypes>;
  arg: ArgBuilder<SchemaTypes>;
  type: TypeParam<SchemaTypes>;
};

export const usePaginationBuilder = ({ builder, arg, type }: UsePaginationBuilderArgs) => {
  if (!Array.isArray(type) || typeof type[0] !== 'object' || !('name' in type[0])) {
    // eslint-disable-next-line fleek-custom/no-default-error
    throw new Error(`Type of field with pagination must be list e.g. type: [SomeType]`);
  }

  const paginationInputTypeRef = getOrCreatePaginationInputTypeRef({ builder, name: 'PaginationInput' });

  const typeWithAggregationRef = getOrCreateTypeWithAggregationRef({
    builder,
    name: upperCaseFirst(`${type[0].name}sWithAggregation`),
    type,
  });

  const paginationArgsGroup = { filter: arg({ required: false, type: paginationInputTypeRef }) };

  return {
    typeWithAggregationRef,
    paginationArgsGroup,
  };
};

but we get this error when we want to generate TS declarations:
  src/plugins/inputGroup/usePaginationBuilder.ts(11,17): error TS4058: Return type of exported function has or is using name 'outputShapeKey' from external module "/Users/robert/Desktop/FleekHQ/fleek/node_modules/.pnpm/@pothos+core@3.41.0_graphql@16.6.0/node_modules/@pothos/core/dts/types/type-params" but cannot be named.

Typescript version: 5.3.2
tsconfig.types.ts
{
  "extends": "./tsconfig",
  "compilerOptions": {
    "removeComments": false,
    "declaration": true,
    "declarationDir": "dist-types",
    "emitDeclarationOnly": true,
    "declarationMap": true
  },
  "exclude": ["**/*.test.ts"]
}

tsconfig.ts
{
  "include": ["src", "*.d.ts", "../../env.d.ts"],
  "exclude": ["dist-*", "node_modules"],
  "extends": "../../tsconfig.json",
  "compilerOptions": {
    "rootDir": "./src",
    "strict": true
  }
}

root tsconfig.ts
{
  "extends"<EMAIL_ADDRESS>  "include": ["src", ".storybook"],
  "exclude": ["dist", "cli", "**/node_modules"]
}

PS. other CJS, ESM builds work fine
It works for Typescript versions: 4.9.3, 5.0.0-beta and stop working from 5.0.1-rc

I'll try to find some time this weekend to debug this.  If you have a reproduction you can share that may make things faster to track down and fix

I've tried to reproduce it here: https://stackblitz.com/edit/typescript-zrtilk?file=usePaginationBuilder.ts but haven't been able to see the issue

I created a repo where I was able to reproduce the issue with minimum files: https://github.com/RobertPechaCZ/pothos-ts-repro

Not sure what exactly causes this problem, but this fixes it:
...
const getOrCreateTypeWithAggregationRef = ({ builder, name, type }: GetOrCreateTypeWithAggregationRefArgs) => {
  const originalRef = builder.configStore.getOutputTypeRef(name);

  if (typeof originalRef !== 'string') {
    return originalRef as OutputType<SchemaTypes>;
  }
...

Good catch. Probably TS cannot infer outputShapeKey from function signature.

In general for this type of issue, adding an explicit cast or an explicit cast to a returned value, or a return type of a function can help.  The other thing that helps is enabling declarations in your main tsonfig file so the errors show in the editor, and exporting more functions so its easier to track down which function might be causing the issue


Automatically deafen the player when it joins a channel

Because the music player will not need to receive any audio, we can deafen it. (This just looks nicer on the user's end)

We have a voice receiving PR in progress on the main lib, so we would need the bot to not be deafened for that.

Why not add self_deaf as a kwarg in the connect function that defaults to False. Sorts out everything. (And I wanted this to be implemented too 😅)

We have a voice receiving PR in progress on the main lib, so we would need the bot to not be deafened for that.

well bot's can still hear when deafened so this PR does nothing there

Oh interesting, I didn't know that
Also I completely forgot about the plans for recording audio when I was writing this pr 😅

We have a voice receiving PR in progress on the main lib, so we would need the bot to not be deafened for that.

well bot's can still hear when deafened so this PR does nothing there

Huh wait how? Doesn't that defy the purpose?

We have a voice receiving PR in progress on the main lib, so we would need the bot to not be deafened for that.

well bot's can still hear when deafened so this PR does nothing there

Huh wait how? Doesn't that defy the purpose?

idk weird discord thing


🐞[Bug]: Rapidoc text is written even on big screen .

Is there an existing issue for this?

[X] I have searched the existing issues

Describe the bug
Rapidoc text and not the logo is written even on big screen .
Expected behavior
Logo should appear on big screen and text on small screen like other pages .
Add ScreenShots

What browsers are you seeing the problem on?
Firefox, Chrome
Record

[X] I have read the Contributing Guidelines
[X] I'm a GSSOC'24 contributor
[X] I have starred the repository

/assign


Board Details don't autosave

I just now realized that board details don't autosave. I've gotten so used to the autosave that it kind of snuck up on me. Can haz autosave on board details?
🐱  @paullewis

AFAICT we don't have an edit API for updating the top-level graph info, like title, version, and description. That means that the runtime changes these values directly on the graph descriptor, and we don't emit an edit event. The shorter term workaround is to emit the edit event, and that causes the board to save. But I think if we can add in a top level EditSpec for updating the top level graph info I can probably neaten up the runtime a bit.

Renaming so it's nearer what we need


Returning detailed results of intermediate components

Issue you'd like to raise.
I am currently using a chain with the following components:
FewshotPrompt ( with SemanticSimilarityExampleSelector) -> LLM -> Outputparser
By default, this will give me the parsed text output of my LLM.
For my purposes, I would need the output of this chain to include all intermediate steps (preferably in a dict).
For this chain that would be:

The samples selected by the Example Selector
The generated Fewshot Prompt
The raw LLM output
The parsed LLM output

From the documentation, it is not apparent to me how this could be achieved with the current state of the library.
(The documentation also does not outline details about the usage of Callbacks in the LCEL language)
Suggestion:
If this is currently implemented then add a simple example to the documentation. If this is not the case then some type of callback that allows collecting this data from intermediate steps should be added.

The Problem with this type of implementation is that the FewshotTemplate needs to be provided with either examples or an example_selector in the init. Thus providing them in this manner does not seem to be an option.

@DanielRoeder1 I came across this post when trying to do something similar - you can use a RunnablePassthrough to get the results of intermediate components. here's a simple example:
# This passthrough allows us to pass the prompt through the chain
llm_runnable = RunnableParallel(passed=RunnablePassthrough(), output=self.llm)

# each chain is just the prompt into the llm
chain = prompt | llm_runnable

results = chain.invoke({ "foo": "bar"})

prompt = results['passed']
llm_result = results['output']

This got a little unwieldy for my multi-part chains, so I ended up creating a few small chains in a class and saving off the intermediates as they were run to class variables, which worked out alright for my needs.
Hope that helps.


ScalingFailed constructed with too few parameters

Describe the bug
PR #1783 introduces a line:

       raise (ScalingFailed("No execution provider available"))

here
https://github.com/Parsl/parsl/blob/a54b6847153e85f780a84e2c437697ff314d5916/parsl/executors/high_throughput/executor.py#L572
but ScalingFailed.__init__ method requires two parameters:

def init(self, executor, reason)

On my benc-mypy branch, mypy just started complaining about that for me after my last master merge - I don't immediately see why it just started complaining now.
This will result in an exception being thrown at the right time, but the wrong type: a TypeError not a ScalingFailed.
To Reproduce
On current master a54b6847153e85f780a84e2c437697ff314d5916:
>>> from parsl.executors.errors import ScalingFailed
>>> raise (ScalingFailed("No execution provider available"))
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
TypeError: __init__() missing 1 required positional argument: 'reason'

Fixed by #1958


Add debounceDuration to CustomTextEditingController

With CustomTextEditingController, text is parsed every time it is updated. It becomes more costly as the text becomes longer. If the text is extremely long, it takes time before it is parsed and then the change becomes visible.
debounceDuration is for reducing the load. If a duration is given, parsing is started not immediately but only after the duration. If there is some user action before the duration ends, like another text input, a cursor move or a tap/long-press of a text span, the counting of the duration is reset and starts from the beginning.
However, it turned out that just debouncing text parsing was not enough. It appears something else happening (probably on the Flutter SDK side) after text parsing and rebuilding of text spans is time-consuming and slowing down text inputs. So, this feature is marked as experimental for now, and may be removed if its effect is after all not worth the maintenance cost.

I tried some packages by other developers. All of them have performance issues with very long text. If its cause lies in the framework itself, there's little we can do about it.


Updater installing same Build again

When manualy checked, the Updater says that there is a newer Version available. It then downloades the exact same Build, since the one installed is already the most recent.

fixed update file on server...


Refactor MP-CNN to Use torchtext and Implement Early Stopping

use torchtext for MP-CNN
implement early stopping if no improvements on validation set after a certain number of epochs

torchtext point addressed by #76.
Early stopping point addressed by #60


[RFCs]: Magnition Proposal

This PR proposes RFCs for the following two features:

Localized Layout Options
Template typename passing with inheritance

Hi, I suggest one RFC per PR otherwise the discussion might be hard to follow.

Regarding localized layout options:
I think the main interface for this might be the layout options view (not the sidebar) for klighd-vscode https://github.com/kieler/klighd-vscode/issues/83. This view should have the possibility to serialize the changes, which would be implemented via a service interface on the server side.
Whether the option serialization would take a separate file could be language specific and it would work as long as the option file is loaded in the synthesis.
My take would be to contribute to klighd-vscode first and see whether a simple tree view with all layout options set is enough for your use case. If it is not, the client could be extended for a different kind of interaction using the klighd-vscode LSP messages build for the new view.

Thanks for submitting this PR @mkhubaibumer! Could I ask you to split the two RFCs into two PRs? This makes it a lot easier for us to review and discuss them individually. Also, it seems like a bunch of additional files were added to the diff of this PR.

@soerendomroes @cmnrd sure. I'll split this in 2 PRs asap

@cmnrd @soerendomroes @lhstrh I've split the PR into 2.
Please review and share your feedback on the proposal

@cmnrd that's an interesting idea! But would lingua-franca be open to generating annotations in code by changing layout option for certain reactor instantiations
Its much easier to do it from diagram then write these annotations in code in my opinion

That is something we should put up for discussion in the broader team, but personally, I am open to that. Doing it in the code and also updating the code automatically certainly has some downsides, but I think the main advantage would be that we still have the diagrams representing only the code and there would be no external metadata that gets out of sync. However, before we get into the details of this, I think it would be most important to understand the feasibility on the side of the diagram backend.

Another important question is feasibility on the KIELER side. soerendomroes a-sr Does the framework only consider global rendering options, or is there support for local options too?

I agree that this is a big open question and also not a question that I am well-prepared to answer quickly.

But would lingua-franca be open to generating annotations in code by changing layout option for certain reactor instantiations

For this the big open question is not whether we can add the annotations in the code (we can do that, it is easy) but rather what the graphical UI would look like. UI design is a complex issue that is outside my expertise and I am worried that it could get pretty difficult to support this without causing a lot of confusion for non-expert users.

In our diagram framework, we distinguish two types of configuration options. Synthesis options affect how the diagram is created (e.g. if state variables are visible); these are located in the side bar. Layout options are set implicitly by the synthesis and affect only the layout/arrangement of the diagram.
For the latter, LF already supports overriding the defaults (set by the synthesis or ELK) by annotating model elements (https://github.com/lf-lang/lingua-franca/pull/1951). E.g. @layout(option="port.side", value="NORTH")
Yet, if you are interested in synthesis options here, this will require an adjustment of the LF diagram synthesis because it treats the settings in the side bare as a global configuration, e.g. if (getBooleanValue(SHOW_PORT_NAMES)). This would require an adjustment to something like if (getBooleanValue(SHOW_PORT_NAMES) || reactor.hasAnnotation("portnames")). In short: yes, it is feasible.
In terms of usability, if writing annotations is not desired, one could think of adding them via a context menu for model elements, similar to structure-based editing. However, this is not yet support in Klighd but @soerendomroes could say more to this topic.

Interesting. Thanks for the explanation. I actually completely forgot about the @layout annotation. @mkhubaibumer do these in code annotations address your use-case, or do you require GUI support? Are the layout options sufficient, or would you also need support for synthesis options?

We are planning to add structure-based editing into Klighd and will rework the interactive layout constraint framework, which was a very similar workflow to what you may be envisioning. For me, the question remains, whether layout options are enough for you or whether you want to change synthesis options

@cmnrd that's an interesting idea! But would lingua-franca be open to generating annotations in code by changing layout option for certain reactor instantiations
Its much easier to do it from diagram then write these annotations in code in my opinion

The advantage of annotations is that it gives you a way to serialize (i.e., save) layout options. If not done that way, what would be an appropriate place to save them? Do sprotty or klighd perhaps already have an established mechanism for this, @soerendomroes?

@lhstrh We are currently serializing them if possible. This might be in the next klighd/klighd-vscode release, maybe in the one shortly after that. For interactively setting layout constraint to constrain the topology of the layered layout. We are currently we are trying to serialize a constraint if the given language has a serializer, otherwise, we only work on the view model (KGraph) such that this changed will not be persisted and will be gone on reload.
The synthesis options are usually saved in the browser for a corresponding language (which is the way VS Code usually handles things).


Why are server node_modules committed to repository

Hello. Just a quick question. I saw the folder server/node_modules. What's the reason to upload node_modules folder to repo ?

Sorry about that, I added it in .gitignore after committing, did not notice that it got uploaded. I have removed it,
Thank you


Clarify that truncated tables need to be pre-split again

When a table is truncated, it is essentially re-created in a single new empty range and the old ranges that used to constitute the table are garbage collected. One effect of this is that any pre-splitting that a user has performed on the old version of the table will not carry over to the new version. The new table will need to be pre-split again. We should make this detail clear in the SPLIT AT documentation.

Thanks for reporting, @nvanbenschoten.


Setting shuffle=True for val_dataloader doesn't work when ddp enabled.

🐛 Bug
Setting shuffle=True for val_dataloader doesn't work when ddp enabled.
To Reproduce
minimum snippet:
from pytorch_lightning import LightningModule, Trainer
from torch import nn
from torch.optim import Adam
from torch.utils.data import DataLoader

class PlModule(LightningModule):
    def __init__(self):
        super().__init__()
        self.model = nn.Linear(1, 1)
        self.train_dataset = list(range(1000))
        self.val_dataset = list(range(1000))

    def configure_optimizers(self):
        return Adam(self.model.parameters(), lr=0.1)

    def training_step(self, batch, *args, **kwargs):
        return self.model(batch)

    def validation_step(self, batch, *args, **kwargs):
        print(f'{batch=}')
        print(f'{self.trainer.val_dataloaders[0].sampler.shuffle=}')
        exit(0)

    def train_dataloader(self):
        return DataLoader(self.train_dataset, shuffle=True, batch_size=5)

    def val_dataloader(self):
        return DataLoader(self.val_dataset, shuffle=True, batch_size=5)

if __name__ == '__main__':
    module = PlModule()
    trainer = Trainer(
        limit_train_batches=0.0,
        limit_val_batches=1.0,
        num_sanity_val_steps=-1,
        gpus=2,
        strategy='ddp',
        enable_model_summary=False
    )
    trainer.fit(module)

By execute the snippet above, we get the stdout:
GPU available: True, used: True
TPU available: False, using: 0 TPU cores
IPU available: False, using: 0 IPUs
initializing distributed: GLOBAL_RANK: 1, MEMBER: 2/2
initializing distributed: GLOBAL_RANK: 0, MEMBER: 1/2
----------------------------------------------------------------------------------------------------
distributed_backend=nccl
All distributed processes registered. Starting with 2 processes
----------------------------------------------------------------------------------------------------

LOCAL_RANK: 0 - CUDA_VISIBLE_DEVICES: [0,1,2,3,4,5,6,7]
LOCAL_RANK: 1 - CUDA_VISIBLE_DEVICES: [0,1,2,3,4,5,6,7]
Validation sanity check: 0it [00:00, ?it/s]/home/balabala/miniconda3/lib/python3.8/site-packages/pytorch_lightning/trainer/data_loading.py:452: UserWarning: Your `val_dataloader` has `shuffle=True`,it is strongly recommended that you turn this off for val/test/predict dataloaders.
  rank_zero_warn(
/home/balabala/miniconda3/lib/python3.8/site-packages/pytorch_lightning/trainer/data_loading.py:110: UserWarning: The dataloader, val_dataloader 0, does not have many workers which may be a bottleneck. Consider increasing the value of the `num_workers` argument` (try 96 which is the number of cpus on this machine) in the `DataLoader` init to improve performance.
  rank_zero_warn(
Validation sanity check:   0%|                          | 0/100 [00:00<?, ?it/s]batch=tensor([1, 3, 5, 7, 9], device='cuda:1')
self.trainer.val_dataloaders[0].sampler.shuffle=False
batch=tensor([0, 2, 4, 6, 8], device='cuda:0')
self.trainer.val_dataloaders[0].sampler.shuffle=False

Expected behavior
the stdout should contains the follow:
batch= # some random batch
self.trainer.val_dataloaders[0].sampler.shuffle=True

Environment

PyTorch Lightning Version 1.5.2
PyTorch Version 1.10.0
Python version 3.8.10

cc @borda @tchaton @rohitgr7 @justusschock @awaelchli @ninginthecloud @kaushikb11 @akihironitta

Out of curiosity, could you describe why you need shuffling during validation?

Out of curiosity, could you describe why you need shuffling during validation?

In training, I would like to construct random positive-negative pairs on the fly. In validation, I want to keep the same setting. Of course, I can construct random data before model fitting and fix it, but it's more convenient to do it on the fly, and I don't have to write additional code. Since I would like to choose a large batch size, the randomness the validation setting brings is acceptable.

In your model's pl.LightningModule,
class ModelModule(pl.LightningModule):
    def on_validation_start(self):
        for v in self.trainer.val_dataloaders:
            v.sampler.set_epoch(self.current_epoch)

This is the line in the Trainer where shuffling is hardcoded to be False for validation, test, and prediction dataloaders: https://github.com/PyTorchLightning/pytorch-lightning/blob/1c5a5c3dfeeefa7b8760ab5f5869f3f61c48e665/pytorch_lightning/trainer/data_loading.py#L312-L313

@rohitgr7 Mind having a look.

@ananthsub I was looking into similar issue earlier and before I made a PR the structure was changed.
The logic is now in DataConnector and the changes I made previously are no longer enough to shuffle.
The self._check_eval_shuffling function below doesn't return anything other than raising an error.
https://github.com/PyTorchLightning/pytorch-lightning/blob/9cf9ded73b66296e1b22369ea4e8327f9ce0aae8/pytorch_lightning/trainer/connectors/data_connector.py#L429-L435
https://github.com/PyTorchLightning/pytorch-lightning/blob/9cf9ded73b66296e1b22369ea4e8327f9ce0aae8/pytorch_lightning/trainer/connectors/data_connector.py#L532-L543
As mentioned in the trainer setting replace_sampler_ddp might help in a few cases.
https://github.com/PyTorchLightning/pytorch-lightning/blob/16a04b29eb811f105a11db4f7f3003489252f9f8/pytorch_lightning/trainer/trainer.py#L361-L364


npx causing issues with Yarn

Laravel Mix Version: ^6.0.18 (npm list --depth=0)
Node Version (node -v): v14.16.0
NPM Version (npm -v): 6.14.11
Yarn Version: 2.x and 3.0.0-rc.2
OS: macOS 11.2.3

Description:
The watch and build commands run npx under the hood. This causes issues when using Yarn as the package manager and forces users to install webpack and webpack-cli as dependencies manually resulting in a confusing experience.
Steps To Reproduce:

Create a project using Yarn as the package manager
Add laravel-mix as a dev dependency
Add a webpack.mix file (or compatible variant)

This only needs to contain the import at the top of the file (const mix = require('laravel-mix');)

Run mix using Yarn — yarn mix

On first run, the user is prompted to install webpack-cli.  If the user chooses to install at that time, the command then subsequently fails as it can't find webpack. In order to fix this issue, webpack must also be installed as a dev dependency.
Solution:
Rather than running these commands with npx, build and watch should call webpack directly and both webpack and webpack-cli should be listed as peer dependencies.

I have this solution working locally and will be submitting a PR shortly.

I've been digging into this further and it seems to me the larger issue is how webpack is called. Rather than compiling all the options and running them as a shell script, it might be better to execute webpack directly from Node. I'm working on it right now, but it would effectively look something like this:
// ./bin/cli.js
...

const webpack = require('webpack');
const webpackConfig = require('../setup/webpack.config.js');

...

async function commandScript(cmd, opts) {
    const config = await webpackConfig();
    webpack(config); // for build
    webpack(config).watch({}, err => {}); // for watch

...

I've thought about that myself but it's a non starter since we'll lose the automatic setup of things handled by webpack-cli and would need to replicate all options. Right now we support passing arbitrary options to webpack-cli like so: mix -- --cli-option-goes-here

Something we could do is run npx if running under npm and yarn run webpack — I think that'd work? I'd have to do some testing to check.

I see! Okay, that makes sense. I'm gonna keep poking around in the meantime. The workaround for Yarn 2+ to add webpack and webpack-cli as dev dependencies isn't the worst solution, but it would be nice to not have to.

I can give that a shot. I've got everything all set up and running at the moment, so it's worth trying and reporting back.

Something we could do is run npx if running under npm and yarn run webpack if running via yarn — I think that'd work? I'd have to do some testing to check.

I can give that a shot. I've got everything all set up and running at the moment, so it's worth trying and reporting back.


Modify example from fp32 to fp16

Models convert to FP16:

[x] llama2
[x] qwen
[x] qwen1.5
[x] mistral
[x] chatglm2
[x] chatglm3
[x] Baichuan2

@jason-dai See the performance results here: https://github.com/analytics-zoo/nano/issues/1188#issuecomment-2031323848
Can we merge this first?

@jason-dai @qiuxin2012 Merge it first. Tell us if there are any concerns.


Edit records using Eddington GUI

On the "Select record" window, when pressing twice on a record, the user should be able to edit it.
Also, add "save to file" button

I'm on it

This feature would require some work at Toga. Added an issue in beeware/toga#1022

After some conversations in the linked article TogaI  issue, it seems to me that the right thing to do is to use toga.Table instead of using labels organised in boxes...
However, not all necessary abilities are implemented in toga.Table for both Windows and Mac.
Therefore, this issue is blocked for now.


Fix hook error due to missing kubernetes-common layer

Fixes https://bugs.launchpad.net/bugs/1938943 for Flannel.

Test failure is unrelated to this change. I suggest we ignore the failure and land this so we can move on with other 1.22 testing and fixes. Please review.


Dev branch

Relies on It relies on https://github.com/pdsinterop/solid-nextcloud/pull/4.

I now have something showing on https://localhost/apps/solid/openid
But the rewrite rule in https://github.com/pdsinterop/test-suites/pull/24/files#diff-745b5ba9e18d18668d2151e5e0d9a854R5
is not doing its job yet.

This does work:
<IfModule mod_rewrite.c>
  RewriteEngine on
  RewriteRule ^\.well-known/openid-configuration /apps/solid/openid [R=301,L]
</IfModule>


Add eps and amsgrad options to Adam Optimizer

Expose more options in AdamOptions
Fix https://github.com/LaurentMazare/tch-rs/issues/145
However it will break the adamw and adam interface under src/nn/optimizer.rs. Should I create a new functions like adam_new?

Thanks for the PR, I've made further changes to preserve the current api and the newly added field can still be configured via a builder pattern. I think I'll lilkely remove the nn::adam and nn::adamw functions altogether as the intended way to setup the optimizer would be as follows, though I want to think a bit more about it before removing these.
let opt = Adam::default().eps(1e-6).amsgrad(true).build_copt(...)


Figure out why we need .mvn/extensions.xml while takari-local-repo does not

@ifedorenko do you have any idea why our integration tests do not work without .mvn/extensions.xml file (that the present pull request removes just to demo the effect)?
I did my best to do everything here as you did in takari-local-repository. But without .mvn/extensions.xml, I simply cannot see my local repo implementation being loaded. There is only [DEBUG] Using manager EnhancedLocalRepositoryManager with priority 10.0... there in log.txt, while I expect [DEBUG] Using manager SrcdepsLocalRepositoryManager...
OTOH, when I run your takari-local-repository I can see in log.txt that your repo impl is being loaded even without .mvn/extensions.xml : [DEBUG] Using manager TakariLocalRepositoryManager with priority 20.0...
Can you maybe see something important I have forgotten?

While I am still curious why we need .mvn/extensions.xml and takari-local-repository does not, this is not that hot anymore because in https://github.com/l2x6/srcdeps/pull/44 , we started exposing our test projects as quickstarts, where it is quite desirable to show the .mvn/extensions.xml to the users. Thus closing, but I'd still be thankful for any hints why did not work here.

MavenRuntimeBuilder#withExtension adds specified classes directory as Maven core extension, it does not add any dependencies (it operates on files, and does not have access to dependency information). I am guessing that srcdeps-maven-local-repository has required runtime dependencies and fails to load because they are missing. takari-local-repository does not have any required runtime dependencies, so target/classes is sufficient to make tests run.
.mvn/extensions.xml is defined in terms of artifacts, at runtime maven will use the artifact and its dependencies.
Hope this makes sense.

@ifedorenko yes, makes sense. Thanks a lot!


Update diff_drive_controller_velocity.yaml

Related with this other PR https://github.com/ros-controls/gazebo_ros2_control/pull/224

https://github.com/Mergifyio backport humble


Nextcloud backups to public shares

Hi,
I think it would be nice to be able to backup the OPNsense configuration to Nextcloud public shares.  :-)
That way there would be no need to store the credentials of a Nextcloud user on the OPNsense firewall.
You could create a public share for each OPNsense instance that you want to backup and if needed also set an individual password for it.
Nextcloud public  shares can be accessed quite simple via WebDAV.  The URL is the same one for every share on your Nextcloud, The share ID functions as username, Password is optional
https://example.com/nextcloud/public.php/webdav
https://docs.nextcloud.com/server/20/user_manual/en/files/access_webdav.html#accessing-public-shares-over-webdav
cheers
Michael

Sorry, didn't use the template. My bad.


shuffleNet pretrained model

where is the shuffleNet pretrained model , I cannot find it in google drive

refer to issue #17


Bad Gateway - https://try.gitea.io/

I stumbled across https://gitea.io/en-US/ but when I tap "Try Gitea", it responses with Bad Gateway.

go-gitea/gitea#3147 fixes this, as soon as this is merged try gitea should be working again

Fixed

Thanks! I can confirm it works now.

Hi.
Broken for me too.

Unable to connect
Firefox can’t establish a connection to the server at try.gitea.io.


Add #[allow(clippy::string_lit_as_bytes)] in w! macro to silence clippy

Motivation
This is a false positive, as changing this b"$s" will simply convert an &str with the contents "$s" to bytes, not the input.
Drawbacks
None.
Rationale and alternatives
Using the paste macro to do this instead, but depending on something for just two lines of code is, well, a bit silly.
Additional context
While this is allow by default, Embark's standard lints (which few copy-paste into their own, unrelated projects as the style is quite nice) has this as a warn, which requires this to be overridden below. This isn't ideal, as in many cases this lint works, and is cleaner.

It also appears this is an "issue"(?) with the h! macro as well.

Thanks! I played around with non-default clippy warnings and the trouble I see is that there is a great deal that would need to be handled so I'm not sure about the wack-a-mole approach.

I think I will close this here and bring it up with clippy instead, as that seems more reasonable.


Translations not loading on first request on the server

Describe the bug
Hi. I'm using Grunge Stack, running Architect (locally).
Took me a while to remember that client files are server from the _static folder in Architect, so once I did that, I got it working.
But... on first request, it doesn't appear to be loading translations on the server - so when it renders the html the first time, nothing is translated, I just see key names, then once it hydrates in the browser, the translations work. So, I get a kind of "flash of unstyled content" (but for translations).

"Hydration failed because the initial UI does not match what was rendered on the server"
I've investigated a bit but can't work out what is or is not happening on the server. Any ideas?
Your Example Website or App
https://github.com/recipher/administrato
Steps to Reproduce the Bug or Issue
...
Expected behavior
As a user, I expect to see translated content on first request.
Screenshots or Videos

Platform

OS: [e.g. macOS, Windows, Linux]
Browser: [e.g. Chrome, Safari, Firefox]
Version: [e.g. 91.1]

Additional context
No response

It seems that Architect runs from the /server directory, so it can't see files at ./public. Changing to ../public has made it work locally. I haven't deployed yet, so I'm not sure what will happen on the server - I guess I'll have to move the files somewhere.
Next issue I have is that the server translations always use the fallbackLng, not sure why yet.

Did you find any solution ?


feat: Added interpreter variable to control script runtime

Description
Include interpreter argument of provisioner.local_exec block as variable in null_resource.deploy.  Allow user to control the execution runtime of the deploy script.
Motivation and Context
/bin/bash isn't necessarily guaranteed to be the selected shell, leading to failures in bash built-in control flow.
See issue <>
Breaking Changes

How Has This Been Tested?

Fixes https://github.com/terraform-aws-modules/terraform-aws-lambda/issues/118

Thanks @zandabanda for this fix!
v1.41.0 has been just released.


Get local node tip information

Issue

#541
This PR adds a get-tip command to cardano-cli that retrieves the tip from your local node  (via its socket) and prints to stdout in the following format: blockhash@slotnumber

checklist

[x] This PR contains all the work required to resolve the linked issue.

[ ] This PR results in breaking changes to upstream dependencies.

[x] The work contained has sufficient documentation to describe what it does and how to do it.

[x] The work has sufficient tests and/or testing.

[x] I have committed clear and descriptive commits. Be considerate as somebody else will have to read these.

[x] I have added the appropriate labels to this PR.

This PR adds a get-tip command to cardano-cli that retrieves the tip from your local node (via its socket) and prints to stdout in the following format: blockhash@slotnumber

The block number is also available. We should print all three I'd say.
Any reason for the @ syntax? Where else is that used?

This PR adds a get-tip command to cardano-cli that retrieves the tip from your local node (via its socket) and prints to stdout in the following format: blockhash@slotnumber

The block number is also available. We should print all three I'd say.
Any reason for the @ syntax? Where else is that used?

@dcoutts  No specific reason, I was using showTip: https://github.com/input-output-hk/cardano-node/blob/e947da9af8ffa62abfb08b6607c5b3808be776e7/cardano-node/src/Cardano/Tracing/ToObjectOrphans.hs#L91
It's also used in the TraceChainSyncServerEvent Condense instance.
Would something like this be better:
Current tip:
  Blockhash:
  Slot:
  Block number:

bors r+

bors r-

bors r+


Chore/update dependencies

Packages updated
Major

@commitlint/cli 13.2.1 ❯ 16.0.1
@commitlint/config-conventional 13.2.0 ❯ 16.0.0
@next/eslint-plugin-next 11.1.2 ❯ 12.0.7
@typescript-eslint/eslint-plugin 4.30.0 ❯ 5.9.0
@typescript-eslint/parser 4.30.0 ❯ 5.9.0
eslint 7.32.0 ❯ 8.6.0
eslint-config-airbnb 18.2.1 ❯ 19.0.4
eslint-config-airbnb-typescript 14.0.0 ❯ 16.1.0
eslint-config-next 11.1.2 ❯ 12.0.7
eslint-plugin-react-hooks 1.7.0 ❯ 4.3.0
@next/bundle-analyzer 11.1.2 ❯ 12.0.7
next 11.1.2 ❯ 12.0.7

Minor

sass 1.42.1 ❯ 1.46.0
eslint-plugin-import 2.24.2 ❯ 2.25.4
eslint-plugin-jsx-a11y 6.4.1 ❯ 6.5.1
eslint-plugin-react 7.26.1 ❯ 7.28.0
prettier 2.4.1 ❯ 2.5.1
typescript 4.4.3 ❯ 4.5.4

Patch

@types/react 17.0.33 ❯ 17.0.38
husky 7.0.2 ❯ 7.0.4
next-sitemap 1.6.192 ❯ 1.6.237

Additional changes

Removed redundant import React from 'react'; imports as per this
Updated Eslint config to allow components as arrow functions const myComp = () => {...}
Silenced optional-chaining error in Seo.tsx
Allowed for export { default } from "..."

All changes have been integrated and released under v2.0.0.
A major release was necessary due to the upgraded packages. The newest ESLint rules recommend using function declarations (or expressions) for React components. This has been applied to all existing components and Hygen templates for component generation.
These and more changes have been tagged and released.
Thank you for helping keep this project up to date 💪 🎉 @BoyanZhelev!


docs: environment variables and Oxygen.env

Description
Docs for #304
I've renamed the file to "environment variables" since I think "secrets" can now be confusing.

cc @mcvinci for visibility.

Oh, and we may want to coordinate with the Oxygen team for shipping this work, since I'm not sure whether runtime variables have landed in the admin panel yet? cc @macpham

Oh, and we may want to coordinate with the Oxygen team for shipping this work, since I'm not sure whether runtime variables have landed in the admin panel yet? cc @macpham

@mcvinci This feature was released yesterday so I've now merged the docs. Please update shopify.dev when you have time 🙌


Update composer.json

update composer

Thanks! Would you like to tell why is composer 6.3?

Thanks


Swaps follow up

some suggestions or things that I noticed might be missing
I went through the atomic swap issues and closed a couple that had already been completed.
cc @exezbcz

#11212
#11213
#11214
#11215
#11216

some of suggestions or things that I noticed might be missing
Swap Modal
we also need to show the surcharge direction, either the user is also

requesting x amount
sending x amount

Gallery Item
missing action button

Swap Table

show surcharge direction and amount if there is enough space

Swaps in Profile Page
add button to start swap items of that user

Swap Table

show surcharge direction
show both tokens that are being swapped , with the current implementation only the receiver or creator of the swap can open the modal, there is no view swap button, so users that are not involved in the trade can't see both tokens of the swap from this page

Swap Page Review Step

surcharge is missing

commented on some of the mentioned issues, will drop other things soon


[BUG]: Horrible query performance

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
I am trying to run a simple aggregation query to count the existence of a record. The table to run the query against has only one entry. Querying against this table takes at least 40ms which is waaaaay to slow. Running the same query via psql or even the underlying pg-driver brings up query times around 1ms.
This is the code I used to compare raw pg querying vs drizzle orm:
const pg = this.database.getInternalClient()
const drizzle = this.database.client

console.time("pg benchmark")
const statement = `select count(*) as count from matcher.swipes where id = '${id}'`;
const result = await pg.query(statement)
console.timeEnd("pg benchmark") //-> 1ms

console.time("drizzle benchmark")
const existsPrepared = drizzle
  .select({count: count()})
  .from(swipes)
  .where(eq(swipes.id, sql.placeholder('id')))
  .prepare("checkIfSwipeExistsById");

const existsResult = await existsPrepared.execute({id})
console.timeEnd("drizzle benchmark") //-> 40-50ms

Running the same raw query using drizzle.execute(...) results in the same 40-50ms of execution time.
 Those times are not acceptable.
Expected behavior
I expect the query time to be somewhat close to the raw pg-driver performance.
Environment & setup

Node.js v20.17.0
AMD Ryzen 9 7950X 16-Core Processor 4.50 GHz
64GB DDR5 RAM
Windows 11 Pro

I had a look at the code and tried to follow timings. I dont know why but thel query-call of
const result = await import_tracing.tracer.startActiveSpan("drizzle.driver.execute", (span) => {
        span?.setAttributes({
          "drizzle.query.name": query.name,
          "drizzle.query.text": query.text,
          "drizzle.query.params": JSON.stringify(params)
        });
        return client.query(query, params);
      });

Is the last drizzle-code building on top of the pg module. client.query is from the pg module and adds the huge delay. So I am not sure if this is actually a drizzle problem. Calling it, like I did in the code above, manually with a query string does not result in this huge time... Interesting behavior

This is actually a problem with the pg module I am using as the driver for drizzle. Version 8.1.0 of this module is the last one that results in the same performance.

Turns out there is another fix/workaround: Using Node v16 and the newest node-postgres (8.13.0) runs fine too.

@francois-egner If it's an issue specific to the driver, it may be better to open an issue in the pg driver repo and close this one.

@L-Mario564
I already did. For whoever is interested: https://github.com/brianc/node-postgres/issues/3325
Will close this issue.


Add iOS 8, 9 test infra to devicelab

Devicelab iOS tests should also be run on iOS 8 and 9. Since physical devices have a nasty habit of being irreversibly updated to newer OS releases, and we need more simulator coverage anyway, simulators seem like the most reasonable approach.

/cc @yjbanov

See also https://github.com/flutter/flutter/issues/10718.

Hi @cbracken  is this issue still meant to be open?

/cc @godofredoc
We should also revisit https://github.com/flutter/flutter/issues/10718 and decide on something

We have now the ability to bundle different emulators, the remaining part here is to create the tests that will run on those emulators.

Thanks -- yep, this should still be open. Ideally we should be testing at least the oldest OS we claim to support.

@cbracken I think iOS 8 and 9 will no longer be supported.

I think the spirit of this is to run tests on the oldest versions of iOS, whether that's iOS 9 or 10 or whatever.  It will be easier as of https://github.com/flutter/flutter/issues/91689, simulator runtimes can be added via the .ci.yaml.

Infrastructure now supports simulator runtimes. You can write your tests and make them use an old runtime.

@godofredoc have we actually added tests that run on simulators running the oldest supported version of iOS, or just the infra to support doing so?
I'm going to tentatively re-open on the assumption that we haven't yet added the tests.

You are correct only the infrastructure part of if has landed.


how to fix stacktrace with sh.SignalException_SIGKILL

Hey @amoffat thanks for your great work with sh. I'm really close to getting a solid code parsing tail output, are there ways to catch or suppress the stack trace that comes with an attempt to kill a tail blocked with .next() ? I've been trying to catch this exception on both kill and next calls but the beautiful stack trace keeps showing.  Let me know if there's an alternative to this code. Thanks a lot!
           #elsewhere in the code
           try:
             filestatus[filename]['running'] = False #this is not enough as sh.tail is blocking at .next()
             tail = filestatus[event.src_path]['tail']
             tail.kill()
           except sh.SignalException_SIGKILL as e:
             print(str(e))

...
              #elsewhere in the code
              t = threading.Thread(target=process_tmp_ta, args=(f,)) #f == /tmp/tmp.074461843
              filestatus[f] = {}
              filestatus[f]['thread'] = t
              t.start()

def process_tmp_ta(filename=""):
      filestatus[filename]['running'] = True
      filestatus[filename]['tail'] = sh.tail("-F", filename, _iter=True)
      while filestatus[filename]['running']:
        print("running")
        try:
               line = filestatus[filename]['tail'].next()
        except sh.SignalException_SIGKILL as e:
            print("process_tmp_ta tail terminated")
            break

Exception in thread background thread for pid 3185:
Traceback (most recent call last):
  File "/Users/[REDACTED]/opt/anaconda3/lib/python3.7/threading.py", line 926, in _bootstrap_inner
    self.run()
  File "/Users/[REDACTED]/opt/anaconda3/lib/python3.7/threading.py", line 870, in run
    self._target(*self._args, **self._kwargs)
  File "/Users/[REDACTED]/src/github.com/[REDACTED]/scripts/venv/lib/python3.7/site-packages/sh.py", line 1662, in wrap
    fn(*args, **kwargs)
  File "/Users/[REDACTED]/src/github.com/[REDACTED]/venv/lib/python3.7/site-packages/sh.py", line 2606, in background_thread
    handle_exit_code(exit_code)
  File "/[REDACTED]/src/github.com[REDACTED]/scripts/venv/lib/python3.7/site-packages/sh.py", line 2304, in fn
    return self.command.handle_command_exit_code(exit_code)
  File "/Users/[REDACTED]/src/github.com/[REDACTED]/scripts/venv/lib/python3.7/site-packages/sh.py", line 877, in handle_command_exit_code
    raise exc
sh.SignalException_SIGKILL:

  RAN: /usr/bin/tail -F /tmp/tmp.074461843

  STDOUT:
[REDACTED]
  STDERR:

Hi @ggmartins, It looks like _bg_exc=False is the magic incantation you're looking for. It will force background exceptions to not happen in the background thread, but instead in the main thread, where your try/except code can catch them. Give that a try and let me know if that works.

yes, it's working perfectly now. Thanks a lot!


[4.3 beta 1] Godot produces corrupt config if language does not use '.' as decimal separator

Tested versions

v4.3.beta1.official [a4f2ea91a]

System information
Godot v4.3.beta1 - openSUSE Tumbleweed 20240523 - Wayland - Vulkan (Forward+) - dedicated AMD Radeon RX 580 Series (RADV POLARIS10) () - Intel(R) Core(TM) i7-3770K CPU @ 3.50GHz (8 Threads)
Issue description
Godot writes invalid editor_settings-4.3.tres and invalid project.godot files, when the User's language does not use a period as a decimal separator.
Floats get represented like 0,57 instead of 0.57, causing issues like Parse Error: Expected 4 arguments for constructor.
This prevents Godot from starting until editor_settings file is fixed.
Starting Godot with LANG=C ./godot fixes the problem.
Steps to reproduce

run Godot 4.3 Beta 1 with PC language set to German
change colors in Theme settings of the Editor
close Godot
start Godot
crashes immediately, Parse Error: Expected 4 arguments for constructor

Minimal reproduction project (MRP)
n.a.

Addition:
This might be related to Wayland. After starting the Editor for the first time, I immediately turned on Wayland and clicked "save & restart". The engine froze. I killed the process, restarted, and the config file was invalid.

Can you reproduce this in 4.2.2? I've never heard of this issue before, as Godot does not use language-specific decimal separators when printing numbers in the first place.

No, I've been using 4.2.2 (v4.2.2.stable.openSUSE [15073afe3] to be exact) the whole time and never had this issue.

I just tried again, and it only happens with prefer_wayland = true.
I'll attach a Screencast:
Screencast_20240601_125532.webm

Well, the Man-Page for sprintf says the decimal separator depends on LC_NUMERIC.  So setting LC_CTYPE should not change that.  But maybe it is worth giving that a try anyways:

the Unix Env Var Spec says that it will use LANG in absence of LC_ALL and other LC_* variables.  I wonder if this is true for all the LC_* variables.  So perhaps if LC_NUMERIC is unset, it uses uses the next best thing (perhaps LC_CTYPE, if set).

Other than that, I guess the only reason it happens with Wayland is that Wayland sets (or doesn't set) these Variables differently from X11.

Well, I just inspected /proc/<pid>/environ to find differences between running X11 and Wayland, and... there is absolutely no difference... if I set LANG=C, the only difference is that LANG=C instead of LANG=de_DE.UTF-8 ...
Interestingly, apart from LANG, no other LC_* variables are set at all!
Setting LC_NUMERIC=C does solve the problem!
Setting LC_CTYPE=C does not solve the problem.

It definitely happens inside snprintf
Here's an ltrace of Godot without prefer_wayland:
[pid 21555] Godot_v4.3-beta1_linux.x86_64->snprintf("0.56", 256, "%lg", 0,560000) = 4

And now with prefer_wayland...
[pid 21740] Godot_v4.3-beta1_linux.x86_64->snprintf("0,56", 256, "%lg", 0,560000) = 4

As you can see, the output with prefer_wayland takes locale into account, while without it, it does not 🤔
So... is something weird going on inside libc?!


Noise

Complete this sentence
THIS PULL REQUEST __ [IS/IS NOT] __ READY TO MERGE
Feature or improvement description
A clear and concise description of the new code.
Related issue, if one exists
Link to a related GitHub Issue.
Impacted areas of the software
List any modules or other areas which should be impacted by this pull request. This helps to determine the verification tests.
Additional supporting information
Add any other context about the problem here.
Automated test results
Add the automated test results (unit tests and regression tests) here, if they've been run.
For any failing tests, please provide justification.

Thanks for that. Let's then modify the CMakeList and remove the sources


[WIP] Feat: upload to o2 scripts

Codecov Report

Merging #714 (a2d0c7b) into release/0.15.0 (a98cea3) will decrease coverage by 0.62%.
The diff coverage is n/a.

@@                Coverage Diff                 @@
##           release/0.15.0     #714      +/-   ##
==================================================
- Coverage           57.14%   56.52%   -0.63%
==================================================
  Files                   1        1
  Lines                  70       69       -1
  Branches               15       15
==================================================
- Hits                   40       39       -1
  Misses                 30       30

Impacted Files
Coverage Δ

packages/config/src/index.ts
56.52% <0.00%> (-0.63%)
:arrow_down:

Continue to review full report at Codecov.

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

reviewed


Compiling cudpp on VS2008/2010 causes fatal error C1060: compiler is out of heap space

What steps will reproduce the problem?
1. Download CUDPP Release 2.0, Aug 8 release
2. Use CMake took to create sln files
3. build on VS2010 using the v90 platform toolset

What is the expected output? What do you see instead?
12_segmented_scan_app.compute_10.cudafe2.gpu
2>  segmented_scan_app.cu
2>  tmpxft_000007b8_00000000-6_segmented_scan_app.compute_13.cudafe1.gpu
2>  tmpxft_000007b8_00000000-16_segmented_scan_app.compute_13.cudafe2.gpu
2>  segmented_scan_app.cu
2>  tmpxft_000007b8_00000000-3_segmented_scan_app.compute_20.cudafe1.gpu
2>  tmpxft_000007b8_00000000-20_segmented_scan_app.compute_20.cudafe2.gpu
2>  segmented_scan_app.cu
2>ptxas C :
/Users/Peter/AppData/Local/Temp/tmpxft_000007b8_00000000-9_segmented_scan_app.co
mpute_10.ptx, line 183650; warning : Double is not supported. Demoting to float
2>  segmented_scan_app.cu
2>  segmented_scan_app.cu
2>  tmpxft_000007b8_00000000-8_segmented_scan_app.compute_10.cudafe1.cpp
2>  tmpxft_000007b8_00000000-32_segmented_scan_app.compute_10.ii
2>
2>C:/Users/Peter/AppData/Local/Temp/tmpxft_000007b8_00000000-5_segmented_scan_ap
p.fatbin.c(2090276): fatal error C1060: compiler is out of heap space
2>
2>  CMake Error at
CMakeFiles/cudpp_generated_segmented_scan_app.cu.obj.cmake:256 (message):
2>    Error generating file
2>
C:/Users/Peter/Documents/Labwork/Thesis/CodeSamples/cudpp_src_2.0/build/src/cudp
p/Debug/cudpp_generated_segmented_scan_app.cu.obj

What version of the product are you using? On what operating system?
Win7 x32, Visual Studio 2010 (also tested on 2008)

Please provide any additional information below.
Attempted several fixes suggested by MS, none of which worked:
increased page file size to maximum allowed
Used the /Zm option with values ranging from 100 to 2000
Removed the /Zm options

Original issue reported on code.google.com by<EMAIL_ADDRESS>on 7 Sep 2011 at 5:01

So it sounds like that is precisely on point for the aforementioned
release-note known-issue, I'm afraid. This is an NVIDIA compiler issue rather
than a CUDPP issue, with the proviso (of course) that it's CUDPP code that is
making the compiler use so much memory. Can you up your virtual memory (4 GB
sounds low for a modern system anyway) and see if that might allow the compiler
to finish?

Original comment by<EMAIL_ADDRESS>on 7 Sep 2011 at 10:11

My system has 4GB RAM, however 1GB is reserved as video RAM. I have 4GB of
virtual memory
To be exact: 3061 MB accessible physical memory and 4095MB virtual memory

Original comment by<EMAIL_ADDRESS>on 7 Sep 2011 at 5:30

http://cudpp.googlecode.com/svn/tags/2.0/doc/html/index.html

Known issue: "There is a known issue that the compile time for CUDPP is very
long and the compiled library file size is very large. On some systems with <
4GB of available memory (or virtual memory), the CUDA compiler can run out of
memory and compilation can fail. We will be working on these issues for future
releases."

How much memory do you have on your system?

Original comment by<EMAIL_ADDRESS>on 7 Sep 2011 at 5:08

Same problem on 32-bit Linux, Ubuntu 11.04 with kernel 2.6.38-11-generic
#50-Ubuntu SMP Mon Sep 12 21:18:14 UTC 2011 i686 athlon i386 GNU/Linux. The top
program says Mem 2GB total and Swap 4GB total.
cmake 2.8.3, cuda 4.0

[ 13%] Building NVCC (Device) object
src/cudpp/./cudpp_generated_segmented_scan_app.cu.o
ptxas /tmp/tmpxft_00000cbd_00000000-5_segmented_scan_app.compute_10.ptx, line
185427; warning : Double is not supported. Demoting to float
virtual memory exhausted: Cannot allocate memory
CMake Error at CMakeFiles/cudpp_generated_segmented_scan_app.cu.o.cmake:256
(message):
  Error generating file
  /home/guillaume/src/cudpp_src_2.0/build/src/cudpp/./cudpp_generated_segmented_scan_app.cu.o

Original comment by<EMAIL_ADDRESS>on 6 Oct 2011 at 5:19

unfortunately CUDPP 2.0 seems to require a 64-bit OS to compile successfully
currently.

Original comment by<EMAIL_ADDRESS>on 27 Nov 2011 at 10:40

Added labels: Priority-High, Milestone-Release2.1
Removed labels: Priority-Medium

Issue 109 has been merged into this issue.

Original comment by<EMAIL_ADDRESS>on 27 Nov 2011 at 10:41

You might need to upgrade to a 64-bit OS.  I'm not sure we have tested CUDPP
2.0 on a 32-bit OS...

Original comment by<EMAIL_ADDRESS>on 9 Sep 2011 at 2:57

I have upped the virtual memory to 8 GB (4GB on each of my drives, the maximum
allowed by Win7 x32). It does not resolve the 'out of heap space' bug

Original comment by<EMAIL_ADDRESS>on 9 Sep 2011 at 6:23

can't believe this issue still not fixed yet.

Original comment by<EMAIL_ADDRESS>on 29 Oct 2012 at 1:24

We would be delighted to hear any suggestions you had about how to structure
the project such that it eliminates this issue. If this was easily fixable, I
assure you we would place high priority on getting it fixed.

Original comment by<EMAIL_ADDRESS>on 30 Oct 2012 at 5:06


feat: add loading state to wallet balance

Resolves #499

🐝 PR preview in Swarm
Preview URL: https://bah5acgzax4z4rvfjly6qtqrkzyene4jhaskgjtel7glb65xs6tsg6hkiyzna.bzz.link
Swarm Hash: bf33c8d4a95e3d09c22ace08d27127049464cc8bf9961f76f2f4e46f1d48c65a
Commit Hash: 9c7dfd61f0181dd6c90a9a6f22cb9bd9a2125e5d
Commit Message: feat: add loading state to wallet balance


HDDS-8712. Clean up replication code

What changes were proposed in this pull request?
Clean up replication code.  See individual commits for details.
https://issues.apache.org/jira/browse/HDDS-8712
How was this patch tested?
Refactoring, covered by existing tests.
https://github.com/adoroszlai/hadoop-ozone/actions/runs/5103430870

Change LGTM, but there are some conflicts that need fixed before we can run the CI checks.

Thanks @sodonnel for the review.


Client needs to support bitcoind for getting chain info for deposits

Base on the Gateway roadmap #6178
Bitcoind didn't work because we need to upgrade the client api we're using
Better thing would be to use bdk for it and we just get rid of our stuff for interacting with chain data

@Kodylow i will continue to work on this

Can you edit the issue please and describe the problem in more detail and solutions you have in mind? The linked issue is kinda huge.

looking at fedimintd implementation, we have implementation for bitcoincorerpc, electrum, espiora, does this mean we are adding BDK implementation for IBitcoindRpc trait. or removing  bitcoincorerpc and replacing it with BDK implementation
@Kodylow

The idea is to see what we can remove from our implementation by using bdk's chain crates to get and manage it vs our custom one so we don't have as much to maintain

The idea is to see what we can remove from our implementation by using bdk's chain crates to get and manage it vs our custom one so we don't have as much to maintain

we are still implementing IBitcoindRpc traits, but using using BDK chain crate.


Abhi/connection properties

PR for
https://github.com/dbcli/mssql-cli/issues/118

I'm currently brainstorming the best ideas to write tests for these connection params that does not involve setting up an actual live server with certs for encryption, etc.
Any suggestions welcome.

I've only done manual testing, will not merge till I have unit tests for them

In reply to: 353253063 [](ancestors = 353253063)

@abhisheksinha89 , You could perhaps move the click decorators into their own module to make it modular for unit testing. Then you can use the CLI runner which is part of click.testing module to run through the options to ensure they are populated. That should verify the input aspect, then you can submit those options to the connection service contract and verify the format of the output.
For reference for click testing:
http://click.pocoo.org/5/testing/
Let me know if you thought of this already and found a issue with it.

Talked with Brian, manual testing should be good for now as we are focused more on unblocking customers. I'll add an issue to write unit tests for command line params

In reply to: 353370093 [](ancestors = 353370093)


Created a Heat and Cool Load prediction Model

Description
I have created a Heat and cool load predictor
Issue Resolved
This PR resolves #155
Changes Made
I have created a heat and cool load predictor which will help in predicting heat and cool load and hence will help user to determine which kind of building architecture it should follow so that he/she is in compliance with heat and cool load requirements of the building.

Checklist

[x] My code follows the current project structure
[x] I have thoroughly reviewed and updated the requirements.txt file to include any new packages
[x] The predict.py file includes a properly implemented model_details() function, or the notebook contains this function to print a detailed model report. The model will not be accepted without this function, as it is essential for generating the necessary model details.
[x] I have added relevant tests (if necessary).
[x] I have added comments in the code where needed.
[x] This PR is submitted under Hacktoberfest.
[x] This PR is submitted under GirlScript Summer of Code (GSSoC-Extd).

I have done all tasks please tell if there's anything else that I can do

Please review


feat: add publish for custom version

Background
In certain scenarios, some clients prefer not to update to the latest version of the software but require critical bug fixes in their current version. This necessitates bypassing the automated versioning provided by semantic-release, allowing for a manually specified version to be released.
Changes Introduced
In this PR, I've introduced a dispatcher to the workflow, enabling users to specify a custom version when triggering a release. This enhancement provides greater flexibility, particularly for clients who need targeted updates without adopting the latest release.
Key Implementations:

Custom-Version Dispatcher: Added a dispatcher that allows users to input a custom version number when initiating a release. This ensures that specific bug fixes can be released independently of the standard semantic-release process.
Release Workflow: Integrated the release process with softprops/action-gh-release@v2, ensuring a smooth and consistent release experience while accommodating the custom version specified by the user.

Discussion Point:
Tag Creation and Workflow Rerun: Currently, when a custom version is used and a package is released, the workflow is triggered again because a tag is created. This raises the question: Is it necessary to trigger the workflow with a tag, or should we consider an alternative approach to prevent redundant workflow executions? Feedback on this point would be appreciated.
Test branch:
https://github.com/splunk/splunk-add-on-for-microsoft-cloud-services/actions/runs/10353886295
References
Implementation docs: https://docs.google.com/document/d/1Qenm338CyoeZHo3M_dbX5GJD1SDmlLhz1Jfpg7VWrPg/edit
GitHub Action: softprops/action-gh-release@v2

Could you please have a look at: https://semantic-release.gitbook.io/semantic-release/recipes/release-workflow/maintenance-releases
Maybe that would fit your needs and would not require that many changes in reusable workflow?

@mkolasinski-splunk we've already considered this option before, however this won't fully fit our needs. This functionality from semantic-release has certain strict rules (e.g. naming convention for branches, commits, etc.), and we need a bit more flexibility when doing custom releases. Hence we decided to go for softprops/action-gh-release@v2

Latest updates
I took over the PR from Kamil and introduced 2 important changes:

added validate-custom-version job which validates the string provided in the custom-version input
added run-all-tests-on-develop input which allows for running full suite of workflow jobs also on develop - this functionality is needed for our new branching strategy. The input has a default value of false - thus it won't introduce any change for other TAs, unless true value is explicitly provided.

Testing done

Workflow triggered manually, invalid custom version string (test) provided in the workflow dispatcher - validation job failed with relevant error message; build, tests and publish jobs not executed: workflow url
Workflow triggered manually, valid custom version string (1.2.2) provided in the workflow dispatcher - validation job passed; build, tests, and publish jobs executed, release created properly: workflow url
Workflow triggered on PR to develop with run-all-tests-on-develop input explicitly set to true - validation job skipped, full suite of checks and tests executed: PR url, workflow url
Workflow triggered on PR to develop without providing run-all-tests-on-develop input - validation job skipped, standard behaviour, limited suite of checks and tests executed: PR url, workflow url
Workflow triggered on PR to main - validation job skipped, standard behaviour, full suite of checks and tests executed: PR url, workflow url

Latest updates v2
As per discussion with @mkolasinski-splunk  and @wtobis-splunk, I updated the PR as follows:

limited the triggers for tests on develop branch to push events only (run-all-tests-on-develop -> execute-tests-on-push-to-develop - PRs have been excluded to limit the amount of full workflow runs
added option to run tests on release branches, works the same way as the option for develop - new workflow input (execute-tests-on-push-to-release) with default value of false, allows for running tests on push events, PRs are excluded
also, enhanced validation job to check if the provided release version already exists - as per @kdoroszko-splunk suggestion

Testing done
Tests on push to develop

Workflow triggered on push to develop, without providing execute-tests-on-push-to-develop input - commit url, workflow url -> Outcome: limited workflow run :white_check_mark:
Workflow triggered on push to develop, with execute-tests-on-push-to-develop input explicitly set to true - commit url, workflow url -> Outcome: full workflow run: :white_check_mark:
Workflow triggered on opening the PR (not a push event), with execute-tests-on-push-to-develop input explicitly set to true - PR url, [workflow url] (https://github.com/splunk/splunk-add-on-for-microsoft-cloud-services/actions/runs/10561246411) -> Outcome: limited workflow run :white_check_mark:
Workflow triggered on PR merge to develop (which is a push event), with execute-tests-on-push-to-develop input explicitly set to true - PR merge commit url, workflow url -> Outcome: full workflow run: :white_check_mark:

Tests on push to release branch:

Workflow triggered on push to release/..., without providing execute-tests-on-push-to-release input - commit url, workflow url -> Outcome: limited workflow run :white_check_mark:
Workflow triggered on push to release/..., with execute-tests-on-push-to-release input explicitly set to true - commit url, workflow url -> Outcome: full workflow run :white_check_mark:

Validation of existing release version:

Workflow triggered manually, custom version string for already existing release (1.2.2) provided - workflow url -> Outcome: validation job failed :white_check_mark:

@mkolasinski-splunk linting issue fixed

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


Tests: correct expectations for WorkspaceTests

The path representation is always platform dependent and cannot be written as a literal.  Use AbsolutePath to ensure that we get the correct spelling for the path separator.

@swift-ci please smoke test

@swift-ci please smoke test


Eval cache for IFD-heavy evaluations (Question / Feature Request)

Is eval cache supported? The readme doesn't really mention something.
If not, is it in-scope?

Builds that happen during evaluation time will be cached, is that what you mean?

is that what you mean?

Actually, I was referring to these:
          ~/.cache/nix
          ~root/.cache/nix

It still can rip of +- 30s cycle time or so in some adverse scenarios based on experiences with this implementation.

In the future, we may support evaluation caching, but it isn't part of the goal just yet. Good idea, though!

Probably you could somewhat leap-frog from here.


First pass at blog post for go, wsl, nvim setup

Review, replicate, then commit

All addressed and good to go, merging.


The close button of search doesn't work.

In the search pop bar, the close button x on the right hand doesn't work.
Version:

V2EX+: 1.24.9(84)
Android: 6.0.1

It's clear button to clears query only.
I will hide it when query is empty in the next version.
Thanks.
See design pattern.

OK. It's just confusing.


[otbn/doc] Updated secure wipe specification.

Removed user-initiated secure wipe of internal state.
This resolves issue #7468 .
Signed-off-by: Vladimir Rozic<EMAIL_ADDRESS>

LGTM, thanks @vrozic.


Photoswipe doesn't load on the first page.

Hi,
Here is the website : http://m.walldress.com
When i'm on the website , the first 3 thumbs below 'Photos / + de photos' don't load on photoswipe. But if i go on any page and i come back to the home , if i click on the picture , photoswipe load good. The problem is the same if i try to go on http://m.walldress.com/photos.php?page=1 directly and i click on a picture. For loading photoswipe i have to move at least one time on the website.
Do you have a solution ?
Thank you

Do you experience any issues with the provided examples?

i tried to put the photoswipe script just before my content and not in an including file which is call at the beginning of all my php files. But it doesn't change anything.

I'm really sorry, I have to ask again, do you experience any issues with the provided examples? If not then please check your implementation against the examples provided.


Crash with Dynamic Surroundings

https://github.com/OreCruncher/DynamicSurroundings/issues/453
Reported there because it looked like it was on their end, but adding here because they asked if I reported it here.

This should've been resolved in 0.2.0-alpha-preview6 which was released on the Discord a few days ago. Can you try that one out and let me know if you still have the issue?


Add issues for not-yet-implemented CC features and link them from the doc

We were missing a couple tracking issues for not-yet-implemented CC features at the doc page, which was inconvenient.

@bot-gradle test BD

I've triggered the following builds for you. Click here to see all build failures.

BuildDistributions build

@bot-gradle merge

Sorry I don't understand what you said.
Currently, the following commands are supported:
@bot-gradle test <BuildTrigger1> <BuildTrigger2> ... <BuildTriggerN>

A trigger is a special build for this PR on TeamCity, common triggers are:

SanityCheck/CompileAll/QuickFeedbackLinux/QuickFeedback/PullRequestFeedback/ReadyForNightly/ReadyForRelease
Shortcuts: SC/CA/QFL/QF/PRF/RFN/RFR
Specific builds:

BD: BuildDistributions/BuildDocs so that you can preview the generated docs/distribution.
PT: PerformanceTest, all performance tests for Ready For Nightly stage.
APT: AllPerformanceTest, all performance tests, including slow performance tests.
AST: AllSmokeTestsPullRequestFeedback
AFT: AllFunctionalTestsPullRequestFeedback
ASB: AllSpecificBuildsPullRequestFeedback
ACC: AllConfigCacheTestsPullRequestFeedback
ACT: AllCrossVersionTestsReadyForNightly
AFTN: AllFunctionalTestsReadyForNightly
ACTR: AllCrossVersionTestsReadyForRelease
AFTR: AllFunctionalTestsReadyForRelease

@bot-gradle test and merge

queues this PR for testing and merges if all tests pass by:

Creating a merge commit from your PR branch HEAD and the target branch
Running a ReadyForNightly build against the merge commit
When it passes, fast-forward the target branch to this merge commit (i.e. merge the PR)

The merge commit is called a pre-tested commit, which means that it fully tests the integration
of your branch HEAD and latest master, instead of only testing your branch HEAD.
@bot-gradle cherrypick to <branch>

Cherrypicks the current PR to another branch.
A new PR will be created and a build will triggered automatically if there is no conflict.

@bot-gradle cancel

cancel a running pre-tested commit build or remove it from queue

@bot-gradle clean

clear the conversation history

@bot-gradle help

display this message

To run a command, simply submit a comment.  For detailed instructions see here.

@bot-gradle test and merge

Your PR is queued. See the queue page for details.

I've triggered a build for you. Click here to see all failures if there's any.


Error: can't find module main

Hi AWSLabs:
I followed the instructions using terraform to upload the payload. Everything look like it worked (assignment of site-specific Environment variables, region, etc) and included encrypted chef key.
In the console, I see all the attributes as expected, including main.handle as handler - all done by terraform.
I do have VPC configured as well & applied the appropriate policy per instructions.
However, when running the test, I get:
START RequestId: 9160bb9a-1a24-11e7-8b2c-adbf48dd1b21 Version: $LATEST
Unable to import module 'main': No module named main
Any ideas?

+1
same thing for me. played around with all kinds of module/handler names. nothing worked.
Unable to import module 'main': No module named chef

@jmstallard - I fixed this for me by making sure i was zipping properly. this instructions for this are not the most robust, so I feel your pain. when i zip the lambda function make sure to pass the "-r" flag for recursive.
For ex:
#!/bin/bash
PROFILE=my-aws-profile
NAME=my-awesome-function

zip -r $NAME.zip ./*
aws lambda create-function --cli-input-json file://$NAME.json --zip-file fileb://$NAME.zip --profile $PROFILE

Hey, Thanks for the follow-up, z-matt...
I was using the terraform & did zip up as per doc:
zip -r lambda_function_payload.zip lambda/*
Just tried this and function is now found:
cd lambda
zip -r ../lambda_function_payload.zip *
Function is now found! ... but doesn't work. times out without error after 90sec.
Oh well, a higher-class of error I guess.
-JMS.

From: z-matth<EMAIL_ADDRESS>Sent: Thursday, May 4, 2017 6:19 PM
To: awslabs/lambda-chef-node-cleanup
Cc: James Stallard; Mention
Subject: Re: [awslabs/lambda-chef-node-cleanup] Error: can't find module main (#13)
@jmstallardhttps://github.com/jmstallard - I fixed this for me by making sure i was zipping properly. this instructions for this are not the most robust, so I feel your pain. when i zip the lambda function make sure to pass the "-r" flag for recursive.
For ex:
#!/bin/bash
PROFILE=my-aws-profile
NAME=my-awesome-function
zip -r $NAME.zip ./*
aws lambda create-function --cli-input-json file://$NAME.json --zip-file fileb://$NAME.zip --profile $PROFILE
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/awslabs/lambda-chef-node-cleanup/issues/13#issuecomment-299325164, or mute the threadhttps://github.com/notifications/unsubscribe-auth/ADPiM31avphjDJKWFqlMzccV0HUgURGVks5r2k75gaJpZM4M0kX3.

@jmstallard try the ranman-patch-1 branch -- there was an error in the code (see issue #16)


Complete AnimatedTexture

Used for neon lighting in Midtown in Mafia II and Mafia II DE. Referenced by Materials located in the games MTL (Material Library). The file has a list of textures to iterate through when animating. The format also includes a fair amount of unknown values which should be investigated.
Note - Code was written a very long time ago, so the code may need to be rewritten to be more efficient and look nicer.

[x] Deserialization
[x] Serialization
[ ] Editor
[ ] Polish
[ ] Optimization

Not adding any new features into this Toolkit, obsolete


chore: update refs to default branch from master to main

Details
Updates all the points where we refer to our own default branch name to reflect recent rename
Motivation
Align name with Microsoft/GitHub policy
Context
The rename in GitHub has already occurred and I've already updated our assorted DevOps pipelines accordingly.
Pull request checklist

[x] PR title respects Conventional Commits (starts with fix:, feat:, etc, and is suitable for user-facing release notes)
[x] PR contains no breaking changes, OR description of both PR and final merge commit starts with BREAKING CHANGE:
[n/a] (if applicable) Addresses issue: #0000
[n/a] Added relevant unit tests for your changes
[x] Ran yarn precheckin
[n/a] Verified code coverage for the changes made

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


why not use Web authenticator? becuse it isn't working on Windows？

Web authenticator samples are necessary, this is a big trend, it seems that Microsoft doesn't care at all…………

See the documentation here: https://learn.microsoft.com/en-us/dotnet/architecture/maui/authentication-and-authorization we are working on some updates.
There are many choices for auth based on your setup.

请参阅此处的文档：https://learn.microsoft.com/en-us/dotnet/architecture/maui/authentication-and-authorization 我们正在进行一些更新。
根据您的设置，身份验证有很多选择。

After I got started, I worked on bug in stackflow/github all day.
When my bug was on Microsoft's backlog list, I tried swift & & kotlin and thought you led me astray, 🤣


"improve this doc" links broken because they point to non-existent branch "master"

Search repo for "master" reveals many articles' metadata is pointing at "master", presumably after moving to "main".

This is solved by Docusaurus.


emscripten support build wasm

we should add wasm build，and create a load wasm lib to use in browser.

To add some detail, if you install the latest emsdk, emscripten tries to build wasm by default and fails during linking. I found if I replaced node_modules/nbind/src/pre.js and node_modules/nbind/src/post.js with empty files then the link succeeded but I couldn't use the ndts tool. I also haven't tested if the resulting build actually runs. Error log before edited pre.js and post.js:
  LINK(target) Release/nbind.js
warning: unresolved symbol: $SOCKFS
Stack: Error
    at assertTrue (eval at globalEval (/home/edwardb/emsdk/emscripten/1.38.8/tools/js-optimizer.js:114:8), <anonymous>:59:26)
    at Object.emitDCEGraph (/home/edwardb/emsdk/emscripten/1.38.8/tools/js-optimizer.js:8165:3)
    at /home/edwardb/emsdk/emscripten/1.38.8/tools/js-optimizer.js:8389:14
    at Array.forEach (<anonymous>)
    at Object.<anonymous> (/home/edwardb/emsdk/emscripten/1.38.8/tools/js-optimizer.js:8388:21)
    at Module._compile (module.js:635:30)
    at Object.Module._extensions..js (module.js:646:10)
    at Module.load (module.js:554:32)
    at tryModuleLoad (module.js:497:12)
    at Function.Module._load (module.js:489:3)

undefined:60
    throw msg;
    ^
Assertion failed: could not find the assigment to "asmLibraryArg". perhaps --pre-js or --post-js code moved it out of the global scope? (things like that should be done after emcc runs, as they do not need to be run through the optimizer which is the special thing about --pre-js/--post-js code)
Traceback (most recent call last):
  File "/home/edwardb/emsdk/emscripten/1.38.8/emcc", line 11, in <module>
    python_selector.run(__file__)
  File "/home/edwardb/emsdk/emscripten/1.38.8/tools/python_selector.py", line 38, in run
    sys.exit(run_by_import(filename, main) if on_allowed_version() else run_by_subprocess(filename))
  File "/home/edwardb/emsdk/emscripten/1.38.8/tools/python_selector.py", line 13, in run_by_import
    return getattr(importlib.import_module(os.path.basename(filename)), main)()
  File "/home/edwardb/emsdk/emscripten/1.38.8/emcc.py", line 2019, in run
    wasm_text_target, misc_temp_files, optimizer)
  File "/home/edwardb/emsdk/emscripten/1.38.8/emcc.py", line 2559, in do_binaryen
    emit_symbol_map=emit_symbol_map)
  File "/home/edwardb/emsdk/emscripten/1.38.8/tools/shared.py", line 2481, in minify_wasm_js
    js_file = Building.metadce(js_file, wasm_file, minify_whitespace=minify_whitespace, debug_info=debug_info)
  File "/home/edwardb/emsdk/emscripten/1.38.8/tools/shared.py", line 2501, in metadce
    txt = Building.js_optimizer_no_asmjs(js_file, ['emitDCEGraph', 'noEmitAst'], return_output=True)
  File "/home/edwardb/emsdk/emscripten/1.38.8/tools/shared.py", line 2344, in js_optimizer_no_asmjs
    return run_process(NODE_JS + [js_optimizer.JS_OPTIMIZER, filename] + passes, stdout=PIPE).stdout
  File "/home/edwardb/emsdk/emscripten/1.38.8/tools/shared.py", line 162, in run_process
    return run_base(cmd, universal_newlines=universal_newlines, check=check, *args, **kw)
  File "/home/edwardb/emsdk/emscripten/1.38.8/tools/shared.py", line 157, in run_base
    result.check_returncode()
  File "/home/edwardb/emsdk/emscripten/1.38.8/tools/shared.py", line 143, in check_returncode
    raise Py2CalledProcessError(returncode=self.returncode, cmd=self.args, output=self.stdout, stderr=self.stderr)
tools.shared.Py2CalledProcessError: Command '['/home/edwardb/emsdk/node/8.9.1_64bit/bin/node', '/home/edwardb/emsdk/emscripten/1.38.8/tools/js-optimizer.js', '/tmp/tmpzAdoW8/nbind.bc.o.js.pp.js.mem.js.jso.js', 'emitDCEGraph', 'noEmitAst']' returned non-zero exit status 1
nbind.target.mk:512: recipe for target 'Release/nbind.js' failed
make: *** [Release/nbind.js] Error 1

@william-silversmith you should also be able to add "cflags": ["-s WASM=0"] to your binding.gyp file. It would be nice to have the option to generate a working wasm build too though.

I'm still seeing errors on pre/post js files relating to this. Has anyone made any progress?

Looks like it's related to this - https://github.com/Kagami/ffmpeg.js/issues/44#issuecomment-392248729

I ended up running into enough issues with nbind's default gypi configuration that I made my own copy of nbind.gypi and included that instead of including auto.gypi. This allowed me to have full control over the cflags, the pre and post js, whether FS emulation is enabled, etc. I still couldn't get WASM to work due to errors when my C++ code tried to access the filesystem. It looked like the WASM was trying to access the FS_* functions in the module and they weren't present. It's possible that the module init code needs to be changed to work with wasm. Although iirc I ran into similar issues when I tried to output asm.js with the latest emscripten. The workaround for now was to use the emscripten binaries used in nbind's CI build. I know it's probably off-topic but if it's useful for anyone, this is the Dockerfile I'm using:
FROM debian:latest

RUN apt-get update && apt-get install -y --no-install-recommends \
    ca-certificates \
    build-essential\
    curl \
    git-core \
    openjdk-8-jre-headless \
    python \
    wget \
    gnupg \
    git \
    && apt-mark hold openjdk-8-jre-headless \
    && apt-mark hold make \
    && curl -sL https://deb.nodesource.com/setup_6.x | bash - \
    && apt-get install -y nodejs

ENV TOOLS_PATH="/tools"
WORKDIR /tools

RUN git clone --depth=1 https://github.com/charto/emscripten-ci-linux-binary.git emscripten
RUN ./emscripten/emsdk activate --build=Release sdk-master-64bit
# env vars based on running: source ./emsdk_env.sh
# Adding directories to PATH:
ENV PATH="${TOOLS_PATH}/emscripten:${PATH}"
ENV PATH="${TOOLS_PATH}/emscripten/clang/fastcomp/build_master_64/bin:${PATH}"
ENV PATH="${TOOLS_PATH}/emscripten/node/4.1.1_64bit/bin:${PATH}"
ENV PATH="${TOOLS_PATH}/emscripten/emscripten/master:${PATH}"

# Setting environment variables:
ENV EM_CONFIG="/root/.emscripten"
ENV EMSCRIPTEN="${TOOLS_PATH}/emscripten/emscripten/master"

RUN emcc --version \
    && mkdir -p /tmp/emscripten_test && cd /tmp/emscripten_test \
    && printf '#include <iostream>\nint main(){std::cout<<"HELLO"<<std::endl;return 0;}' > test.cpp \
    && em++ -O2 test.cpp -o test.js && nodejs test.js \
    && em++ test.cpp -o test.js && nodejs test.js \
    && cd / \
    && rm -rf /tmp/emscripten_test

RUN npm install -g yarn
VOLUME ["/src"]
WORKDIR /src

Skipping the gyp based build instructions, I made my own CMake build based on https://groups.google.com/g/emscripten-discuss/c/LPMLVl-XcHQ/m/IBBDhR_LAAAJ, and I could successfully target WASM with that.

Skipping the gyp based build instructions, I made my own CMake build based on https://groups.google.com/g/emscripten-discuss/c/LPMLVl-XcHQ/m/IBBDhR_LAAAJ, and I could successfully target WASM with that.


Upgrading bind_parameters: allow in place and mixed floats + parameters

Summary
In the current situation we need to use bind_parameters to bind float values to a circuit (which returns a copy of the original) and _substitute_parameters to replace the existing parameters with new Parameter objects (which modifies the circuit in place).
With this PR the bind_parameter method gets an upgrade such that it can bind both numeric values and Parameter objects and can do so in-place or on a copy.
The signature is (type hints not actually included, just for explaining reasons here)
def bind_parameters(value_dict: Dict[Parameter: Union[Number, Parameter]], in_place: bool = False)

This is much needed functionality for circuits to become native objects in Aqua, where parameters are replaced a lot and it is cumbersome to always have to distinct between numeric values and Parameters.
Also a num_parameters attribute is added to the circuit for the same integration reason.
Details and comments
This allows to do things such as
>>> theta, x, y = Parameter('θ'), Parameter('x'), Parameter('y')
>>> qc = QuantumCircuit(1)
>>> qc.rx(theta, 0)
>>> qc.u3(0, theta, x, 0)
>>> qc.bind_parameters({theta: 2, x: y}, in_place=True)
>>> print(qc.draw())
        ┌───────┐┌───────────┐
q_0: |0>┤ Rx(2) ├┤ U3(0,2,y) ├
        └───────┘└───────────┘

Concerning the naming we could also use set_parameters, maybe this is the most generic. This also somewhat suggests that the behaviour is not equal to the old bind or substitute, which are still used in the parameter expression.


Are Scala 2.13 versions published anywhere?

Apologies if I am missing something obvious, but I was not able to find Scala 2.13 artifacts in bintray or maven central. Are these actually published, or is it still just Scala 2.12 for the moment? The Bintray directory I was investigating is here FWIW: https://dl.bintray.com/krasserm/maven/com/github/krasserm/.
Thanks!

At minimum, 0.13 is published for 2.12
Check the readme, the bintray group changed

At minimum, 0.13 is published for 2.12
Check the readme, the bintray group changed

Ah, thanks @Daenyth I had absolutely missed that.
For anyone else who makes my same mistake, had to change the custom bintray resolver:
-    resolvers += Resolver.bintrayRepo("krasserm", "maven"),
+    resolvers += Resolver.bintrayRepo("streamz", "maven"),

Ah, thanks @Daenyth I had absolutely missed that.
For anyone else who makes my same mistake, had to change the custom bintray resolver:
-    resolvers += Resolver.bintrayRepo("krasserm", "maven"),
+    resolvers += Resolver.bintrayRepo("streamz", "maven"),


Hardhat chainlink network error

Im trying to use the plugin on a hardhat mainnet fork. I'm using a slightly unconventional way of setting the network so I can choose whether to use mainnet fork on a suite by suite basis. This is a code snippet that is in the before() of the test suite. Shown below:
   await hre.network.provider.request({
			method: "hardhat_reset",
			params: [
				{
					forking: {
						chainId: 1,
						jsonRpcUrl: `https://eth-mainnet.alchemyapi.io/v2/${process.env.ALCHEMY}`,
						blockNumber: 14290000
					}
				}
			]
		})

But when trying to call initChainlinkPriceFeedConfig I get the error shown in the second snippet below:
const chainlinkConfig = new hre.ChainlinkPriceFeedConfig(url);
// Here we set the plugin to work with ETH/USD pair on Mainnet:
await chainlinkConfig.initChainlinkPriceFeedConfig("ETH/USD", "Mainnet");

Error: could not detect network (event="noNetwork", code=NETWORK_ERROR, version=providers/5.6.0)
      at Logger.makeError (node_modules/@ethersproject/logger/src.ts/index.ts:261:28)
      at Logger.throwError (node_modules/@ethersproject/logger/src.ts/index.ts:273:20)
      at JsonRpcProvider.<anonymous> (node_modules/@ethersproject/providers/src.ts/json-rpc-provider.ts:403:23)
      at step (node_modules/@ethersproject/providers/lib/json-rpc-provider.js:48:23)
      at Object.throw (node_modules/@ethersproject/providers/lib/json-rpc-provider.js:29:53)
      at rejected (node_modules/@ethersproject/providers/lib/json-rpc-provider.js:21:65)
      at runMicrotasks (<anonymous>)
      at processTicksAndRejections (internal/process/task_queues.js:95:5)

When running the tests I am not specifying a network as I want some of my test suites to run on different networks, so ideally I would like it to work with how im setting the network.
I'm wondering if theres an issue with how im establishing the config or if its something else. If its an issue with establishing the config how would you recommend amending it that doesn't involve setting the network when running the test suite, alternatively is it possible to amend how the init function gets the network state.
Thanks :)

@kjr217
Were you able to solve this?


CI failing for Python 3.11

In https://github.com/pypa/setuptools/actions/runs/2484717804, I'm attempting to add Python 3.11 to the build matrix, but it fails, presumably because of a new incompatibility with Python 3.11.

Since Python 3.11 isn't yet available for homebrew, I updated jaraco/multipy-tox to support Python 3.11 and then ran the tests, but they were so slow, probably because of the amd64 on arm64 emulation, so I spent some time learning how to add arm support to docker images, and now jaraco/multipy-tox supports arm64 and amd64, and the tests run much faster.

In my local run, I'm unable to replicate the failure in CI. The failure in CI is something of a different nature specific to the setup of the CI environment.
The test that fails when I test locally is the one for checkdocs. It's a warning from pep517 when it tries to invoke a deprecated method in importlib.resources.