Copy attachments as temporary files before sending

This was necessary in my case as the files were local to the app. May not be necessary in other cases, in which case a boolean switch should be added.

I guess you are solving the problem that the mail program will not have permission to the original file if it's an app asset?
I have solved that in my use case, by using react-native-fs to copy asset files once to RNFS.ExternalDirectoryPath. I would rather not copy several files each time the user attaches.
However, I agree that it would be good to handle this case in a built-in way, and copying to a temp file seems fine. Some questions:

What if the file is already in a location that is accessible to the mail program? It would be better not to copy it. You mentioned a switch, but can't the code detect if it's in an accessible location?
I didn't see where the temp file is cleaned up. Maybe that's not possible since you don't know when the mail app is done with it.
When you create the temp file, does that overwrite any existing file with the same path? Bad if not, I guess.

Thanks for those points. I had a look and found some documentation which looks like this issue could be avoided by using the FileProvider: https://developer.android.com/training/secure-file-sharing/share-file

Cool, it would be great if you could get that working. It would allow me to delete some code from my app. My favorite coding is deleting code!


Add selectable example contracts

Closes https://github.com/FuelLabs/sway-playground/issues/57
Testing requires running the server locally.
Also added integration tests to make sure all examples compile. I had to combine the frontend and backend workflows in order to run the correct docker image for the integration test.

Nice, I'm just wondering if we should have the UI widget be a drop down menu similar to what we are using to select the different networks?

Nice, I'm just wondering if we should have the UI widget be a drop down menu similar to what we are using to select the different networks?

Like a dropdown that says "examples" rather than an icon?

Yeah, or potentially a side bar?

I think a sidebar would look too crowded, but maybe there's a way to do I'm not thinking of. If you can share a mockup of what you have in mind it would be helpful!

This is currently blocked by https://github.com/FuelLabs/fuelup/issues/598

@sdankel agree with Josh here, it's unclear that button is actually a drop down, which is why it would be better to just have two drop downs here. Having the network selector is fine, but the network selector could be eventually moved to a higher level menu in the sway-playground app (it's usually top right corner or in settings) for example.
I'm going to approve and merge for now, we can make this adjustment in a future PR.


Could not find a server matching the region en

const akinator = require('discord.js-akinator');
await akinator(message, {
	language: 'en',
	childMode: false,
	gameType: 'character',
	useButtons: true,
	translationCaching: {
		enabled: false
	}
});

results in the error
Error: Could not find a server matching the region en
    at Akinator.start (/opt/stratobotelite/node_modules/aki-api/dist/src/Akinator.js:49:19)
    at processTicksAndRejections (node:internal/process/task_queues:95:5)
    at async module.exports (/opt/stratobotelite/node_modules/discord.js-akinator/src/index.js:118:9)
    at async module.exports.run (/opt/stratobotelite/src/bot/commands/Games/Singleplayer/akinator.js:28:3)
    at async module.exports.runCommand (/opt/stratobotelite/src/bot/monitors/commandHandler.js:75:23)
    at async module.exports._run (/opt/stratobotelite/src/frameworks/klasa/lib/structures/Monitor.js:99:4)

https://github.com/jgoralcz/aki-api/issues/155

Hello @BannerBomb, thanks for the issue report. I am aware of the state of the Akinator API as of present, and I will be sure to publish a new version of this package assuming the developer of the depending package provides a fix. 👍

Thank you! Looking into it now.

@BannerBomb Fixed in v4.1.4, which has now been made available for installation! Please update the package on your system.


Typos in the wiki

Hey, Find EOS recently and very excited about this project!
Just find some tiny issues in the wiki pages.
https://github.com/EOSIO/eos/wiki/Database Schema#3-transaction:
"Account nmae of block producer" should be "Account name ..."
https://github.com/EOSIO/eos/wiki/Database:
Nested Document is a data type, so I think it should keep the same, but now, there is one Nested_Document, one Nested document and one Nested document
The images on https://github.com/EOSIO/eos/wiki/Database API are broken on my side,

A lot of these tutorials has been rewritten. I did fix one of these problems that still existed.


Add Node groups document

I found it useful to have such document because nodes in the config.yml file are sorted by name and the file is too big to scroll it and discover similar nodes.
Any suggestions are welcomed and appreciated.

I understand the motivation here, but I'm nervous about this thing getting out of sync/out of date pretty quickly. What do you think about putting a "category" or something similar in config.yml and then generating this document instead?

@andrykonchin do you have time to implement the changes here? Otherwise I'll close this and we can come back to it later.

Let's come back to this later.


how show month in chinese ？

I  want show month in chinese ! please tell func to change it

Under the hood react-native-modal-datetime-picker uses react-native original DatePickerAndroid, TimePickerAndroid and DatePickerIOS.
Before reporting a bug, try swapping react-native-datetime-picker with react-native original date/time pickers and, if the issue persists, check if it has already been reported as a react-native issue.

Language related issues: #31 #83


Microsoft Azure

How do I integrate this package with my Azure environment? Is there an easy way to use the custom endpoint for my model?
I am using LLPhant in a Laravel project and so far everything is going very well, but due to data isolation reasons, I need to work with the model hosted in our Azure Cloud.

Hey @olimarferraz !
it should be easy because you can pass any client you want. see the mistral class for one example.
$clientFactory = new Factory();

$config->client = $clientFactory
                ->withApiKey($apiKey)
                ->withBaseUri(self::BASE_URL)
                ->make();

Does it help you?

Hi,
I think this doesn't work with the embedded models.
Any suggestions on how to deal with it ?
Thanks


Fetch thrown exceptions for methods and show them in the tooltip.

Hello
This improvement fetches the thrown (@throws) exceptions listed in the docblock and displays them in the tooltip, along with a description of when they are thrown (if it is present in the docblock).
This also improves the formatting of the tooltip a bit, ensuring it is always left-aligned rather than centered, bolding the method/property name, etc.

Hello,
Nice thank you :+1:
Regards,
Peekmo


Release vscode-quarkus 1.11.0

Given the number of projects (eclipse/lsp4mp, vscode-microprofile, redhat-developer/quarkus-ls) involved in the release of vscode-quarkus, let's create a bug to capture and discuss the progress.

vscode-microprofile changelog preparations : https://github.com/redhat-developer/vscode-microprofile/pull/101 ( https://github.com/eclipse/lsp4mp/pull/275 )

We should move this release to the 25th, given the severity of the breakage caused by https://github.com/redhat-developer/vscode-quarkus/issues/526 .

vscode-quarkus changelog preparations : https://github.com/redhat-developer/vscode-quarkus/pull/529 ( https://github.com/redhat-developer/quarkus-ls/pull/673 )

These have just been published on the marketplaces.


Add logs to detect non parametrized queries (NPQs) in cosmosDB

Is your feature request related to a problem? Please describe.
Currently, we have no easy way of tracking if any applications are using non parametrized queries (NPQs) in cosmosDB.
Describe the solution you'd like
For the query APIs, we would like to have a warning message in the logs stating the non parametrized queries .  The logging should be sampled.
And metrics to count the occurrence of these queries.
This would allow us to search logs and find out all users who are non parametrized queries
Describe alternatives you've considered
An alternative is to make Cosmos Clients class non final so we can override.
Additional context
Add any other context or screenshots about the feature request here.
Information Checklist
Kindly make sure that you have added all the following information above and checkoff the required fields otherwise we will treat the issuer as an incomplete report

[ ] Description Added
[ ] Expected solution specified

Thanks for creating this issue @JJ-WM, I have added this to our Todo list. We will prioritize it accordingly.


WIP: DateTimeInput POC

Integrates the initial DateTime component with react datepicker component

Please also add me as a Reviewer once this is done/ready to review.


Use Dropdown from pf-react 3

PF 3 Dropdown is replaced by PF 4 equivalent.
Component's API has changed, so our code is adapted accordingly.

Pull Request Test Coverage Report for Build 2316

33 of 35 (94.29%)  changed or added relevant lines in 3 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.04%) to 82.862%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

src/components/Form/Dropdown.js
19
20
95.0%

src/components/Table/EditableDraggableTable.js
6
7
85.71%

Totals

Change from base Build 2315:
0.04%

Covered Lines:
4220

Relevant Lines:
4877

💛  - Coveralls

The later issue with the Consoles tab is fixed separately by https://github.com/openshift/console/pull/2727 .
This PR is now just "nice-to-have" as we can still use the older PF3 Dropdowns.

@priley86 , any idea how to fix the reference to pf-react/consoles in openshift/consoles via web-ui-components ? If we can fix that on this level, we will avoid patching pf-react/consoles as the consoles are PF3 and the working Dropdown is PF4.

hey @mareklibra - It looks like you are on the right track here w.r.t to conversion to PF4 Dropdown. My best guess is that you'll have fewer style conflicts and compatibility issues if targeting PF4 where possible. It is certainly possibly to style PF3 Dropdown to look more like PF4 Dropdown, but we noticed a lot of problems w/ consistently styling surrounding items (i.e. PF3 Buttons will no longer match PF4 Dropdown Button height, menu container is styled differently in PF4, etc.)
The upstream was unable to adopt PF4 React Dropdown components 1 due to JS API conflict, so they decided to adopt the CSS classes as an initial step 2. So this meant replacing things like .dropdown-menu with '.pf-c-dropdown__menu, .form-control with .pf-c-form-control, .dropdown-toggle with .pf-c-dropdown__toggle , etc... I like the long term plan though is to consume Dropdown directly from PF-React. Since you are heavily integrated there, I would probably try to match these classes and styles best you can...
In regards to @patternfly/react-console, it does not seem a good option to try to mix PF3 components/markup w/ PF4 classes. In theory it should work, but I always had trouble with this and often found that one style change would lead to several others. For that reason, I would consider targeting PF4 Dropdown components inside @patternfly/react-console, potentially as additional JS components inside that package. I thought of maybe passing some prop such as pf4=true to AccessConsoles component for example, which could render alternative JSX, but the problem here of mixing APIs will be Webpack resolution and tree-shaking. I believe the long term goal is to remove all PF3 React dependencies, and this will add additional unnecessary weight... so that being said, I would split that code towards a PF4 edition/exposed module.


Do not use stopPropagation

There are risks in using stopPropagation. The current Touchable uses it a lot. Let us analyse why we used it in the first place and then try to implement the desired behaviour in a better way.
Background
With ev.stopPropagation() we prevented gesture recognition to happen on multiple items at the same time. The topmost Touchable captured all the events and stopped all.
However, this led to a problem when we wanted to recognize gestures concurrently on multiple nested items:

items with tap handlers on top, pannable view on bottom
view with tap handler on bottom, movable items on top

The problem caused us to implement propagate property into Touchable mode. With propagate: true the events were allowed to propagate from items to view, where they were finally stopped. The example Tiles made use of this and provided a dense grid of items that could be rotated by tapping, but still keeping the view transformable.
Proposition
Enforce stronger separation between transform and tap events. Do not emit gesturestart etc if only tap is enabled. Topmost transformation recognizer wins. Topmost tap recognizer share with all other tap recognizers. Tap does not cancel transformations. Transformations do not cancel tap. Taps do not cancel each other.
So, let the events bubble but mark as transformation-handled those events that take part in transformation recognition. A transformation handled event is respected in recognition of tap but does not contribute in item's transformation or emission of gesture events.
Naming contradiction: tap is a gesture and therefore gesturestart etc are a misleadingly named. Before tapspace v1 gesturestart etc were named transformstart etc. There was wisdom in the naming. We probably should revert back to those event names. In addition, Wheelable takes care of mouse wheel gestures. The word gesture is way too generic.

The previous proposition makes Touchable even more complex than it already is. The separation between transforms and taps in a nested structure would require careful and separate handling of both types of events, duplicating the tap threshold, distance, and T estimation logic. We want to keep things simple, KISS the sky, leading to the following advanced proposition.
Advanced proposition

Touchable ignores event if ev.defaultPrevented. Therefore only the topmost Touchable can recognize transforms and tap events.
Implement hit testing

There is a big problem in the advanced proposition: N-finger tap does not have single position. For example four-finger tap on four separate tiles bubble to a mutual parent. Their mean point might even lay on an untouched item in the middle.

Browsers solve the issue by throwing the ball to the programmer by providing the preventDefault method. We however cannot let programmer to prevent individual events because Touchable emits accumulated events, events that are result of multiple raw UIEvents.
However, we can provide similar via the mode as we previously tried to do with the propagate flag. But what keyword would replace propagate?

propagate clearly presents the purpose but is misleading because we are not using stopPropagation
preventDefault transparently tells what is happening under the hood. Downside is that almost every mode should define it for tapspace to work properly. Also, it does not express the interaction between nested Touchables, unless the parent Touchables are considered as "default".
final indicates that the Touchable is the last one to handle the events. Alias to preventDefault so it is needed in almost every mode.

We choose preventDefault being the way to go because it is closest to the convention.


[Question] How does it compare to the plugin obsidian-note-aliases?

This is the link: https://github.com/pulsovi/obsidian-note-aliases
It is already accepted btw.

Both plugins behave same when command is started on the existing link. They both create an alias in link target note.
While purpose of obsidian-note-aliases is actually only to create an alias of existing link, the purpose of my obsidian-link-with-alias plugin is to cover whole link creation process (including adding link brackets, adding separator between link name and link text and adding alias).
My plugin is optimized for the cases when user needs to create a lot of links. There are these extra features:

It keeps the origin text. Note: standard obsidian link autocompletion can change the origin link text, which is not wanted in my case. I want to keep text as it is, just to add links.
Minimize necessary effort. It means, just select the text which has to be converted to the link, run the command, select the target and press enter. Or in some cases you have to type in the part of the target note name, before you press Enter to finish link and alias creation.
The created aliases are sorted from longest to shortest, which is necessary to have other other Obsidian features working well.

You can see most of the use cases on README page.

Thanks a lot, this sounds awesome!


App is throwing the error while running electron 14.0.0 and better-sqlite3

Description:
I'm using electron 14.0.0 and latest version of better-sqlite3 package.
However, when I try to run my app I get the following error:
Compiling Renderer Code[13984:0903/144946.475:ERROR:crashpad_client_win.cc(808)] not connected
And my app exits.
Steps to reproduce:

use npx create-electron-app --template="webpack to create/initialize a fresh new electron app with ElectronForge.
Now execute npm install better-sqlite3.
Require better-sqlite3 in your main.js file: (let db = require("better-sqlite3");)
Now execute npm start and observe.
The app will throw the error such as:
Compiling Renderer Code[13984:0903/144946.475:ERROR:crashpad_client_win.cc(808)] not connected

(This error doesn't come if we use Electron 13.3.0)
@JoshuaWise

I can reproduce this with a vanilla project as well (without all the bells and whistles of create-react-app). This error seems to come up frequently with other native modules as well https://github.com/search?o=desc&q=_ZN2v816FunctionTemplate3NewEPNS_7IsolateEPFvRKNS_20FunctionCallbackInfoINS_5ValueEEEENS_5LocalIS4_EENSA_INS_9SignatureEEEiNS_19ConstructorBehaviorENS_14SideEffectTypeE&s=&type=Issues
I am kind of confused, because I can't seem to make npm rebuild or electron-rebuild actually make it rebuild from scratch. And since there is no prebuild for Electron 14 I have no idea what it's actually installing?
So I'm not sure on which end this needs to be fixed.

I might be entirely lost, but maybe this is related to the fact that both Electron 13 and 14 use ABI 89. That means it pulls the prebuild for ABI 89 but it was compiled for Electron 13. The prebuilds need be a matrix of Electron Version × ABI. There needs to be a prebuild for 13 + 89 AND for 14 + 89. Does that make sense?

Ya, you are right.
I too agree with you.
It may be possible that it may need to be compiled/built for electron V14 in order to make it work but I don't know that how to acomplish it.

I might be entirely lost, but maybe this is related to the fact that both Electron 13 and 14 use ABI 89. That means it pulls the prebuild for ABI 89 but it was compiled for Electron 13. The prebuilds need to be for a given Electron version, not ABI version. There needs to be a prebuild for 13 AND for 14, not a single 89. Does that make sense? Maybe this was the first Electron major release without ABI bump, at least since better-sqlite3 has prebuilds (see https://github.com/electron/node-abi/blob/master/abi_registry.json).
Edit:
Currently:
better-sqlite3-v7.4.3-electron-v89-linux-x64.tar.gz

Future?
better-sqlite3-v7.4.3-electron-v13-linux-x64.tar.gz
better-sqlite3-v7.4.3-electron-v14-linux-x64.tar.gz

But I don't really know a lot about this. Maybe the ABI version is the only thing relevant for compatibility? If so, then why doesn't it work?

This could potentially be fixed by upgrading prebuild-install https://github.com/JoshuaWise/better-sqlite3/blob/master/package.json#L14
Because of https://github.com/electron/node-abi/pull/104 but it's not in yet https://github.com/prebuild/prebuild-install/blob/c96c526d360b2e8ce0ece5b9e3c06b13082ea74e/package.json#L29
Manually doing npm i<EMAIL_ADDRESS>doesn't fix it, so yeah.

Cool, so how can I incorporate the fix at my side so that I can run electron 14 with better-sqlite3?

This could potentially be fixed by upgrading prebuild-install https://github.com/JoshuaWise/better-sqlite3/blob/master/package.json#L14
Because of electron/node-abi#104 but it's not in yet https://github.com/prebuild/prebuild-install/blob/c96c526d360b2e8ce0ece5b9e3c06b13082ea74e/package.json#L29
Manually doing npm i<EMAIL_ADDRESS>doesn't fix it, so yeah. Maybe that needs to happen in the better-sqlite3 CI first to create new prebuilds.

Is there anything that can be done in the meantime? I tried going back to<EMAIL_ADDRESS>but that doesn't seem to be working now either.

I have the same problem. When using electron v14 this happens when upgrading better-sqlite3 beyond v7.4.0.
It seems that adding prebuilt binaries may have caused this: https://github.com/JoshuaWise/better-sqlite3/releases/tag/v7.4.1
Could it be that a node mismatch is created with electron?

Still no update on this.
Sadly I can't use electron 14 due to this issue
On 9/9/21, Alexander Gabriel @.***> wrote:

I have the same problem. When using electron v14 this happens when upgrading
better-sqlite3 beyond v7.4.0.
It seems that adding prebuilt binaries may have caused this:
https://github.com/JoshuaWise/better-sqlite3/releases/tag/v7.4.1
Could it be that a node mismatch is created with electron?
--
You are receiving this because you modified the open/close state.
Reply to this email directly or view it on GitHub:
https://github.com/JoshuaWise/better-sqlite3/issues/694#issuecomment-916060018

@akash07k have you tried using v7.4.0? That is the last version that works for me

No, not tried, but going to try now.

@akash07k have you tried using v7.4.0? That is the last version that works for me.
If the reason is a node mismatch then probably versions beyond 7.4.0 will not work in lower versions of electron either.

Yes bro, I tried with 7.4.0.
It works fine.
@JoshuaWise
Any update on this?

@akash07k have you tried using v7.4.0? That is the last version that works for me.
If the reason is a node mismatch then probably versions beyond 7.4.0 will not work in lower versions of electron either.

I am not sure if the issue is with better-sqlite3 or with the build tools used with electron.

yeah
On 9/10/21, Alexander Gabriel @.***> wrote:

I am not sure if the issue is with better-sqlite3 or with the build tools
used with electron.
--
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub:
https://github.com/JoshuaWise/better-sqlite3/issues/694#issuecomment-916997741

//First Uninstall  better-sqlite3
npm uninstall better-sqlite3
//use version 7.4.0
npm install<EMAIL_ADDRESS>
npm uninstall electron
//use version 13
npm install<EMAIL_ADDRESS>
//install electron-rebuild
npm i -D electron-rebuild
// Delete both "node-modules" folder, as well as the "packages-lock.json"
//reinstall using
npm i
//rebuild packages
./node_modules/.bin/electron-rebuild    //run for mac
.\node_modules\.bin\electron-rebuild.cmd  //run for windows

/////that solved my problem

///Use electron-packager to build your app
npm install -g electron-packager --save-dev
npx electron-packager <appDirectory> appName --overwrite --asar --electron-version=13.4.0 --platform=win32 --arch=x64 --prune=true --out=release-builds --icon=./build/icon.ico"

No, this is not the way for the users who want to use electron 14 with their apps.
Although as of now I'm using better-sqlite3 7.4.0 for the time being

//First Uninstall  better-sqlite3
npm uninstall better-sqlite3
//use version 7.4.0
npm install<EMAIL_ADDRESS>
npm uninstall electron
//use version 13
npm install<EMAIL_ADDRESS>
//install electron-rebuild
npm i -D electron-rebuild
// Delete both "node-modules" folder, as well as the "packages-lock.json"
//reinstall using
npm i
//rebuild packages
./node_modules/.bin/electron-rebuild    //run for mac
.\node_modules\.bin\electron-rebuild.cmd  //run for windows

/////that solved my problem

///Use electron-packager to build your app
npm install -g electron-packager --save-dev
npx electron-packager <appDirectory> appName --overwrite --asar --electron-version=13.4.0 --platform=win32 --arch=x64 --prune=true --out=release-builds --icon=./build/icon.ico"

Yes definitely, but until the issue is resolved, this is the solution I'm using.
Did yours work with electron 14, because mine does not

Yes, better-sqlite3 7.4.0 works well with electron 14.

Yes definitely, but until the issue is resolved, this is the solution I'm using.
Did yours work with electron 14, because mine does not

Yes, better-sqlite3 7.4.0 works well with electron 14.

Yes definitely, but until the issue is resolved, this is the solution I'm using.
Did yours work with electron 14, because mine does not

KK.. I will try it out

I've been trying to integrate better-sqlite3 with Electron, I've found this solution:
https://ishwar-rimal.medium.com/integrating-sqlite3-in-electron-project-build-with-electron-forge-6d4d634b8648
But, it seems it to work on Windows, but I'm using Linux.
I also found this issue posted on electron-rebuild:
electron-rebuild properly rebuilds better-sqlite3 on Windows, but skips the rebuild on Linux
https://github.com/electron/electron-rebuild/issues/591

@JoshuaWise I poked at this a bit just now.
prebuild-install can be forced to rebuild by setting the environment variable npm_config_build_from_source=true, but using the currently-released version (6.0.1), I still got
(node:2357177) UnhandledPromiseRejectionWarning: Error: The module '/tmp/.mount_PhotoS9hayLP/resources/app.asar.unpacked/node_modules/better-sqlite3/build/Release/better_sqlite3.node'
was compiled against a different Node.js version using
NODE_MODULE_VERSION 89. This version of Node.js requires
NODE_MODULE_VERSION 98. Please try re-compiling or re-installing
the module (for instance, using `npm rebuild` or `npm install`).

I cloned better-sqlite3 into a local directory, ran npx ncu -u which pulled in "prebuild-install": "^6.1.4", changed my package.json to point to that new directory, and everything looks good.
TL;DR: please upgrade your prebuild-install dependency. #702 should take care of it.

I adapted renkei's workaround slightly to directly call npm rebuild providing the target versions. I don't really understand how it uses the electron version properly  ¯_(ツ)_/¯
#!/bin/bash

# Adapted from:
# https://github.com/electron/electron-rebuild/issues/591

# Electron's version.
# example of electron -v --> v15.1.1
export npm_config_target=$(npx electron -v)

# The architecture of Electron, see https://electronjs.org/docs/tutorial/support#supported-platforms
# for supported architectures.
export npm_config_arch=x64
export npm_config_target_arch=x64

# Download headers for Electron.
export npm_config_disturl=https://electronjs.org/headers

# Tell node-pre-gyp that we are building for Electron.
export npm_config_runtime=electron

# Tell node-pre-gyp to build module from source code.
export npm_config_build_from_source=true

HOME=~/.electron-gyp npm rebuild better-sqlite3

@Prinzhorn No need for a rebuild. We simply have to wait till app-builder-bin is fixed. (https://github.com/electron-userland/electron-builder/issues/6352#issuecomment-968363064)

Version 7.4.5 works for me. Thanks!

Thanks @barbalex. Closing this, but would appreciate more confirmations that it is working for people in 7.4.5

I recently migrated to Electron 16 and it went smooth. So I can confirm that it works with the latest Electron + better-sqlite3. Can't speak for older combinations.

I just got this again in two projects after having updated to v7.4.6 and electron 16.0.6. Reverting to v7.4.5 solved the issue

I just want to add something , it works at build time but in the release didn't work .I'm using electron 15

I've encountered this issue with Electron 26 & better-sqlite3 v8.5.x. Going to see which downgrade works again :(

I've encountered this issue with Electron 26 & better-sqlite3 v8.5.x. Going to see which downgrade works again :(

I just got the same issue with Electron 26.1.0. Had to downgrade to 25.4.0 and it worked again.


Move bootstrap and font-awesome dependency to main file

This allows the patternfly-sass/engine.rb to be loaded without loading any external dependencies. In production scenarios that don't want to load the sass compiler, and just want to load the Engine, this makes that possible.

Thanks @skateman !

@NickLaMuro nice work, I'm waiting for the CI to go green and the next release will ship this!


have a translator for modalities

for display and tables it can be nice to have longer names than the one used in the plan


The starts_in sensor is incorrect when loadshedding is the following day

The starts in sensor only looks at times so it gives an incorrect value in the low stages of loadshedding when an areas next slot is the following day. The delta calculation needs to be between the two datetimes and not just the times.

Is this the starts_in in the sensor attributes or the Card's yaml?

I think it's both. It may not actually be if the next slot is not the following day but if it is more than 24 hours away. I'll try and replicate this next time my loadshedding schedule is in that state and share more accurate details

The issue is with .seconds which should be .total_seconds() | int.
Made some tweaks.  Let me know if this works.

Code
type: 'markdown'
content: >
  {% set stage_sensor = "sensor.load_shedding_stage_eskom" %}
  {% set area_sensor = "sensor.load_shedding_area_eskde_14_milnertoncityofcapetownwesterncape" %}
  {% set start_time = state_attr(stage_sensor, "start_time") %}
  {% set end_time = state_attr(stage_sensor, "end_time") %}
  {% set area_schedule = state_attr(area_sensor, "forecast") %}

  {% if area_schedule %}
    {% set start_time = area_schedule[0].start_time %}
    {% set end_time = area_schedule[0].end_time %}

    {% if is_state(area_sensor, "off") %}
      {% set starts_in = timedelta(minutes=state_attr(area_sensor, "starts_in")).total_seconds() | int // 60 %}
      {% set mins = starts_in % 60 %}
      {% set hrs = starts_in // 60 % 24 %}
      {% set days = starts_in // 1440 %}
      {% set alert = "Load Shedding starts in {d}d {h}h {m}m ({next})".format(d=days, m=mins, h=hrs, next=as_timestamp(start_time) | timestamp_custom("%H:%M", True)) %}

      {% if is_state_attr(stage_sensor, "stage", 0) %}
        <ha-alert alert-type="success">{{ states(stage_sensor) }}</ha-alert>
      {% elif starts_in > 1440  %}
        <ha-alert alert-type="success">{{ alert }}</ha-alert>
      {% elif not is_state_attr(stage_sensor, "stage", 0) and 60 < starts_in <= 1440 %}
        <ha-alert alert-type="warning">{{ alert }}</ha-alert>
      {% else %}
        <ha-alert alert-type="error">{{ alert }}</ha-alert>
      {% endif %}
    {% else %}
      {% set ends_in = timedelta(minutes=state_attr(area_sensor, "ends_in")).total_seconds() | int // 60 %}
        {% set mins = ends_in % 60 %}
        {% set hrs = ends_in // 60 % 24 %}
        {% set days = ends_in // 1440 %}
        {% set alert = "Load Shedding ends in {d}d {h}h {m}m ({next})".format(d=days, m=mins, h=hrs, next=as_timestamp(end_time) | timestamp_custom("%H:%M", True)) %}

        <ha-alert alert-type="error">{{ alert }}</ha-alert>
    {% endif %}
  {% endif %}

I'd also recommend you check out the latest dev release for a new card.

Fixed card4.yaml in v1.1.0-dev.2


Fixed #34040 -- Removed autofocus from admin search box.

@moshe742 Thanks :+1: Welcome aboard :boat:


ISPN-5521 Upgrade to Hibernate ORM 5.0.9.Final

https://issues.jboss.org/browse/ISPN-5521

Integrated, thanks :)


Does not deploy Lambda function when Netlify redirects are defined

Describe the bug
First I'm not 100% sure if this is a bug with Netlify (the Netlify CLI itself) or if it's related to this plugin. So hopefully someone with more insights can help here: when there is already a _redirects file defined in the static/ directory this plugin indeed does create correctly the following entry at the end of the file
## Created with gatsby-plugin-netlify
/foo/*  /  301
# @netlify/plugin-gatsby redirects start
/api/* /.netlify/functions/gatsby 200
# @netlify/plugin-gatsby redirects end

but the Lambda function itself is not deployed. From the Netlify CLI I'm getting
(Netlify Build completed in 3m 26.6s)
Deploy path:        /Users/me/Workspace/some-site/public
Configuration path: /Users/me/Workspace/some-site/netlify.toml
Deploying to draft URL...
✔ Finished hashing 4242 files
✔ CDN requesting 42 files
✔ Finished uploading 42 assets
✔ Deploy is live!

When I completely remove the static/_redirects file the Netlify CLI output is
(Netlify Build completed in 3m 31.2s)
Deploy path:        /Users/me/Workspace/some-site/public
Functions path:     /Users/me/Workspace/some-site/netlify/functions
Configuration path: /Users/me/Workspace/some-site/netlify.toml
Deploying to draft URL...
✔ Deploying functions from cache (use --skip-functions-cache to override)
✔ Finished hashing 4242 files and 1 functions
✔ CDN requesting 42 files and 0 functions
✔ Finished uploading 42 assets
✔ Deploy is live!

On the third line there is the indicator that the function is found and deployed. I'm using additionally gatsby-plugin-netlify in combination with @netlify/plugin-gatsby.
Steps to reproduce

create a new Gatsby project
create a Lambda function in src/api/
create a static/_redirects file with one or more redirects. For example /foo/*     /      301
build the project with npx netlify deploy --build

The same happens when a _redirects file is not present but created programatically in gatsby-node.js with
exports.createPages = async ({ actions }) => {
  const { createRedirect } = actions;

  createRedirect({
    fromPath: '/foo/*',
    toPath: '/',
    statusCode: 301,
  });
};

Expected behavior
A Netlify Lambda function should be deployed
Configuration

Environment
$ npx envinfo --system --binaries --browsers --npmPackages @netlify/plugin-gatsby

  System:
    OS: macOS 12.1
    CPU: (8) arm64 Apple M1
    Memory: 2.16 GB / 16.00 GB
    Shell: 5.8 - /bin/zsh
  Binaries:
    Node: 16.13.2 - /var/folders/85/8rb_y49j5911bg5qzd7tkddw0000gp/T/fnm_multishells/78765_1642439901724/bin/node
    npm: 8.1.2 - /var/folders/85/8rb_y49j5911bg5qzd7tkddw0000gp/T/fnm_multishells/78765_1642439901724/bin/npm
  Browsers:
    Chrome: 97.0.4692.71
    Edge: 97.0.1072.62
    Firefox Developer Edition: 92.0
    Safari: 15.2
  npmPackages:
    @netlify/plugin-gatsby: 1.0.3 => 1.0.3

plus I'm using "gatsby-plugin-netlify": "3.14.0" and Gatsby v3 (3.14.5)
Screenshots

Can you submit a pull request?
No.

Hi. Can you try with @netlify/plugin-gatsby@next?

There is no @netlify/plugin-gatsby@next. And the latest @beta was published 4 months ago.

Can you try again with the latest version?

Do you mean 2.0.2 of @netlify/plugin-gatsby? This gives me
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR!
npm ERR! While resolving<EMAIL_ADDRESS>npm ERR! Found<EMAIL_ADDRESS>npm ERR! node_modules/common-tags
npm ERR!   dev<EMAIL_ADDRESS>from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm ERR! node_modules/@netlify/plugin-gatsby
npm ERR!   dev<EMAIL_ADDRESS>from the root project

When I do npm install --legacy-peer-deps the installation seems to work. But then I get following message during build time:
❯ Loading plugins
   -<EMAIL_ADDRESS>from netlify.toml and package.json

❯ Incompatible plugins
   -<EMAIL_ADDRESS>version 1.0.3 is the most recent version compatible with<EMAIL_ADDRESS>
And v1.0.3 is already the version that I have.

Looks good now. However I've updated to Gatsby 4 in the meantime.


about dynamic wake model

Hello,everybody.
I have some questions about DWM theory.
Question 1: after using the DWM model of fast. Farm, I want to deduce the Wake-Deficit model. According to the user guide, I know that the momentum equation used is eq. (1), but I get eq. (2) by deriving the thin shear layer (TL) approximation. I find that the Wake-Deficit model ignores the influence of the second term on the right. Why?
Question 2: we know the eddy visibility formulation expressions the influence of the ambient vapor (first term on the right-hand side) and wake shear layer (second term) on the vapor stresses in the wake, formula 3. According to the mixed length theory, I know that the eddy visibility is equal to the second term, but what theory is the first term on the right hand side based on? I have read all the articles on DWM development and quoted the three articles of Ainslie [1-3], but there are no resources on the Internet. Does anyone know how this is derived? Or have anyone share these three articles?
[1] Ainslie, J. F., 1986, “Wake Modelling and the Prediction of Turbulence Properties,” Proceedings of the Eighth British Wind energy Association Conference, Cambridge, Mar. 19–21, pp. 115–120.
[2] Ainslie, J. F., 1988, “Calculating the Flow Field in the Wake of Wind Turbines,” J. Wind. Eng. Ind. Aerodyn., 27, pp. 213–224.
[3] Ainslie, J. F., 1985, “Development of an Eddy Viscosity Model for Wind Turbine Wakes,” Proceedings of the BWEA Conference, pp. 61–66.
Best regards,
Yuan.

Dear @HEUMK,
It looks like you asked the same question on our forum.  I've now responded there: https://wind.nrel.gov/forum/wind/viewtopic.php?f=39&t=2847&p=18461.
Best regards,


Backend Code linting

Running flake8 on the soruce tree shown several code style issues
  flake8 pyeudiw --count --select=E9,F63,F7,F82 --show-source --statistics
  flake8 pyeudiw --count --exit-zero --statistics  --max-line-length 160

for example: https://github.com/italia/eudi-wallet-it-python/actions/runs/7473221007/job/20336981885?pr=218#step:8:12
please cleanup and resolve all thos issue in a way that flake8 would return 0 issues

resolved via PR https://github.com/italia/eudi-wallet-it-python/pull/224


added some attributes to iframes to make them more accessible[patch]

Jira ticket

Summary
this is in response to: https://github.com/braintree/braintree-web/issues/434
the aria-hidden attribute is correct if the frameService is only ever used to create iframes without interactive content. i can remove it if that isn't the case.
Checklist

[x] Added a changelog entry

i am getting one failed test. it is also failing in my master branch, so i don't think it's related to my changes
FAILED TESTS:
  Modal
    open
      ✖ scrolls to top if platform is iOS and using WKWebView
        PhantomJS 2.1.1 (Mac OS X 0.0.0)
      expected scrollTo to have been called with arguments 0, 0
      AssertionError@/var/folders/3v/node_modules/assertion-error/index.js:74 <- /var/folders/3v/kz0c_r7d4jjg0bbm46k8j0j8gfbw1j/T/0b63f902bc0288259c133bd19b6d34f4.browserify.js:6507:24
      assert@/var/folders/3v/node_modules/chai/lib/chai/assertion.js:141 <- /var/folders/3v/kz0c_r7d4jjg0bbm46k8j0j8gfbw1j/T/0b63f902bc0288259c133bd19b6d34f4.browserify.js:7502:31
      /var/folders/3v/node_modules/sinon-chai/lib/sinon-chai.js:105 <- /var/folders/3v/kz0c_r7d4jjg0bbm46k8j0j8gfbw1j/T/0b63f902bc0288259c133bd19b6d34f4.browserify.js:42964:24
      methodWrapper@/var/folders/3v/node_modules/chai/lib/chai/utils/addMethod.js:57 <- /var/folders/3v/kz0c_r7d4jjg0bbm46k8j0j8gfbw1j/T/0b63f902bc0288259c133bd19b6d34f4.browserify.js:15087:30
      /var/folders/3v/kz0c_r7d4jjg0bbm46k8j0j8gfbw1j/T/unit/frame-service/external/strategies/modal.js:166 <- /var/folders/3v/kz0c_r7d4jjg0bbm46k8j0j8gfbw1j/T/0b63f902bc0288259c133bd19b6d34f4.browserify.js:52240:47```

I couldn't reproduce the build failure, everything passed on our build system. So I'm gonna merge this.


Make 500 Error Page Prettier

Right now our 500 page is just a white page with a very simple text.
This should be brought in line with the style of OpenFarm and not really break the flow of the app.

Did this corn character before I got to know that we had Obi as our main mascot

@justinmarkfarrugia could you explain your reasoning for thinking it clashes with Obi design wise? Educational for everyone involved :)

Sure :) Let's look at the two next to each other

Now at first glance you could definitely say that they were sketched/designed at two different points in time, but let's assume they weren't or that we don't have that eye to differentiate the two. In every product, designers always make sure there is a visual voice or a design language to follow to make sure that there is some level of consistency across the entire experience of actually using the product.
With Obi and Cropster, there's a complete contrast with how they look/could look and feel/could feel in the overall product. Speaking from a visual perspective, Obi has multiple shadows, large outer stroke and looks dynamic whereas Cropster looks plastered into a picture frame. The only dynamism that Cropster has is possibly the light shadows and the subtle gradients but that's it. Sure, in illustration you're given that freedom to sometimes go a bit crazy and explore, but this felt like a complete departure from the original mascot and the preset visual tone.
Now, consistency is not just incorporated in there for the sake of having replication or predictability it's the first thought that comes to designer's mind because they don't want to  have a mixed visual bag. It's ideal for people to keep coming across the same or similar assets/elements because then they'd feel at home.
Illustrations that follow a particular design language and are incorporated routinely across the entirety of the product gives people not only a strong sense of place, but also some clarity. By doing just that, people wouldn't be second-guessing whether assets came from the same source (OpenFarm) or not.
Anyone whose interested in reading further should definitely check this out

This is a really great write-up. Thanks @justinmarkfarrugia.

Was this 500 error implemented?

@farmanp I don't think it was


Define complex cross table constraints

Example:
model Category {
  id                    ID
  value                 String      @unique
  types                 Type[]
}

// @unique(category.value, value) <-- something like this is needed
model Type {
  id                    ID
  value                 String
  category              Category
}

Type should be unique by type.value, but across a category. In other words, there may be several types with the same value if they belong to different categories.

Since this couldn't be enforced at the database level, we're assigning the client team.


Issue : RaspberryPi 3 - Run the command "-ieee80211n --ht_capab '[HT40+] '" cause of the ER

hi,
create_ap was run normal in raspberry pi 3 ,then i run the command "sudo create_ap --ieee80211n --ht_capab '[HT40+]' wlan0 eth0 rpi_ap 12345678" , create_ap can't setup AP , the following is hostapd trace. is issue ? how can i modify it? thx.
pi@raspberrypi:~/Downloads/create_ap $ sudo create_ap -n wlan0 rpi_ap 12345678 --hostapd-debug 1
WARN: brmfmac driver doesn't work properly with virtual interfaces and
it can cause kernel panic. For this reason we disallow virtual
interfaces for your adapter.
For more info: https://github.com/oblique/create_ap/issues/203
WARN: Your adapter does not fully support AP virtual interface, enabling --no-virt
Config dir: /tmp/create_ap.wlan0.conf.D3AIF7JF
PID: 4629
No Internet sharing
hostapd command-line interface: hostapd_cli -p /tmp/create_ap.wlan0.conf.D3AIF7JF/hostapd_ctrl
random: Trying to read entropy from /dev/random
Configuration file: /tmp/create_ap.wlan0.conf.D3AIF7JF/hostapd.conf
ctrl_interface_group=0
rfkill: initial event: idx=0 type=1 op=0 soft=0 hard=0
rfkill: initial event: idx=1 type=2 op=0 soft=1 hard=0
nl80211: TDLS supported
nl80211: Supported cipher 00-0f-ac:1
nl80211: Supported cipher 00-0f-ac:5
nl80211: Supported cipher 00-0f-ac:2
nl80211: Supported cipher 00-0f-ac:4
nl80211: Using driver-based off-channel TX
nl80211: Supported vendor command: vendor_id=0x1018 subcmd=1
nl80211: Use separate P2P group interface (driver advertised support)
nl80211: use P2P_DEVICE support
nl80211: interface wlan0 in phy phy0
nl80211: Set mode ifindex 3 iftype 3 (AP)
nl80211: Setup AP(wlan0) - device_ap_sme=0 use_monitor=1
nl80211: Create interface iftype 6 (MONITOR)
Failed to create interface mon.wlan0: -95 (Operation not supported)
nl80211: Driver does not support monitor interface type - try to run without it
nl80211: Enable Probe Request reporting nl_preq=0x1aa2fa0
nl80211: Register frame type=0x40 (WLAN_FC_STYPE_PROBE_REQ) nl_handle=0x1aa2fa0 match=
nl80211: Register frame command failed (type=64): ret=-22 (Invalid argument)
nl80211: Register frame match - hexdump(len=0): [NULL]
nl80211: Failed to enable Probe Request frame reporting in AP mode
nl80211: QCA vendor test command returned -95 (Operation not supported)
nl80211: Add own interface ifindex 3
nl80211: if_indices[16]: 3
phy: phy0
BSS count 1, BSSID mask 00:00:00:00:00:00 (0 bits)
nl80211: Regulatory information - country=CN (DFS-FCC)
nl80211: 2402-2482 @ 40 MHz 20 mBm
nl80211: 5170-5250 @ 80 MHz 23 mBm
nl80211: 5250-5330 @ 80 MHz 23 mBm (DFS)
nl80211: 5735-5835 @ 80 MHz 30 mBm
nl80211: 57240-59400 @ 2160 MHz 28 mBm
nl80211: 59400-63720 @ 2160 MHz 44 mBm
nl80211: 63720-65880 @ 2160 MHz 28 mBm
nl80211: Added 802.11b mode based on 802.11g information
Completing interface initialization
Mode: IEEE 802.11g  Channel: 1  Frequency: 2412 MHz
DFS 0 channels required radar detection
nl80211: Set freq 2412 (ht_enabled=0, vht_enabled=0, bandwidth=20 MHz, cf1=2412 MHz, cf2=0 MHz)

freq=2412
vht_enabled=0
ht_enabled=0
RATE[0] rate=10 flags=0x1
RATE[1] rate=20 flags=0x1
RATE[2] rate=55 flags=0x1
RATE[3] rate=110 flags=0x1
RATE[4] rate=60 flags=0x0
RATE[5] rate=90 flags=0x0
RATE[6] rate=120 flags=0x0
RATE[7] rate=180 flags=0x0
RATE[8] rate=240 flags=0x0
RATE[9] rate=360 flags=0x0
RATE[10] rate=480 flags=0x0
RATE[11] rate=540 flags=0x0
hostapd_setup_bss(hapd=0x1aa09e0 (wlan0), first=1)
wlan0: Flushing old station entries
nl80211: flush -> DEL_STATION wlan0 (all)
nl80211: Station flush failed: ret=-14 (Bad address)
wlan0: Could not connect to kernel driver
wlan0: Deauthenticate all stations
nl80211: sta_remove -> DEL_STATION wlan0 ff:ff:ff:ff:ff:ff --> 0 (Success)
wpa_driver_nl80211_set_key: ifindex=3 (wlan0) alg=0 addr=(nil) key_idx=0 set_tx=0 seq_len=0 key_len=0
nl80211: set_key failed; err=-22 Invalid argument)
Failed to clear default encryption keys (ifname=wlan0 keyidx=0)
wpa_driver_nl80211_set_key: ifindex=3 (wlan0) alg=0 addr=(nil) key_idx=1 set_tx=0 seq_len=0 key_len=0
nl80211: set_key failed; err=-22 Invalid argument)
Failed to clear default encryption keys (ifname=wlan0 keyidx=1)
wpa_driver_nl80211_set_key: ifindex=3 (wlan0) alg=0 addr=(nil) key_idx=2 set_tx=0 seq_len=0 key_len=0
nl80211: set_key failed; err=-22 Invalid argument)
Failed to clear default encryption keys (ifname=wlan0 keyidx=2)
wpa_driver_nl80211_set_key: ifindex=3 (wlan0) alg=0 addr=(nil) key_idx=3 set_tx=0 seq_len=0 key_len=0
nl80211: set_key failed; err=-22 Invalid argument)
Failed to clear default encryption keys (ifname=wlan0 keyidx=3)
Using interface wlan0 with hwaddr b8:27:eb:2c:00:12 and ssid "rpi_ap"
Deriving WPA PSK based on passphrase
SSID - hexdump_ascii(len=6):
72 70 69 5f 61 70                                 rpi_ap
PSK (ASCII passphrase) - hexdump_ascii(len=8): [REMOVED]
PSK (from passphrase) - hexdump(len=32): [REMOVED]
random: Got 20/20 bytes from /dev/random
GMK - hexdump(len=32): [REMOVED]
Key Counter - hexdump(len=32): [REMOVED]
WPA: Delay group state machine start until Beacon frames have been configured
nl80211: Set beacon (beacon_set=0)
nl80211: Beacon head - hexdump(len=57): 80 00 00 00 ff ff ff ff ff ff b8 27 eb 2c 00 12 b8 27 eb 2c 00 12 00 00 00 00 00 00 00 00 00 00 64 00 11 04 00 06 72 70 69 5f 61 70 01 08 82 84 8b 96 0c 12 18 24 03 01 01
nl80211: Beacon tail - hexdump(len=65): 2a 01 04 32 04 30 48 60 6c 30 14 01 00 00 0f ac 02 01 00 00 0f ac 04 01 00 00 0f ac 02 00 00 dd 1a 00 50 f2 01 01 00 00 50 f2 02 02 00 00 50 f2 04 00 50 f2 02 01 00 00 50 f2 02 7f 04 00 00 00 02
nl80211: ifindex=3
nl80211: beacon_int=100
nl80211: dtim_period=2
nl80211: ssid - hexdump_ascii(len=6):
72 70 69 5f 61 70                                 rpi_ap
beacon_int=100
nl80211: hidden SSID not in use
nl80211: privacy=1
nl80211: auth_algs=0x3
nl80211: wpa_version=0x3
nl80211: key_mgmt_suites=0x2
nl80211: pairwise_ciphers=0x18
nl80211: group_cipher=0x8
nl80211: beacon_ies - hexdump(len=6): 7f 04 00 00 00 02
nl80211: proberesp_ies - hexdump(len=6): 7f 04 00 00 00 02
nl80211: assocresp_ies - hexdump(len=6): 7f 04 00 00 00 02
WPA: Start group state machine to set initial keys
WPA: group state machine entering state GTK_INIT (VLAN-ID 0)
GTK - hexdump(len=32): [REMOVED]
WPA: group state machine entering state SETKEYSDONE (VLAN-ID 0)
wpa_driver_nl80211_set_key: ifindex=3 (wlan0) alg=2 addr=0xc7868 key_idx=1 set_tx=1 seq_len=0 key_len=32
nl80211: KEY_DATA - hexdump(len=32): [REMOVED]
broadcast key
nl80211: set_key default failed; err=-67 Link has been severed)
WPA: group state machine entering state FATAL_FAILURE
wlan0: Flushing old station entries
nl80211: flush -> DEL_STATION wlan0 (all)
nl80211: Station flush failed: ret=-22 (Invalid argument)
wlan0: Could not connect to kernel driver
wlan0: Deauthenticate all stations
nl80211: sta_remove -> DEL_STATION wlan0 ff:ff:ff:ff:ff:ff --> -22 (Invalid argument)
wpa_driver_nl80211_set_key: ifindex=3 (wlan0) alg=0 addr=(nil) key_idx=0 set_tx=0 seq_len=0 key_len=0
wpa_driver_nl80211_set_key: ifindex=3 (wlan0) alg=0 addr=(nil) key_idx=1 set_tx=0 seq_len=0 key_len=0
wpa_driver_nl80211_set_key: ifindex=3 (wlan0) alg=0 addr=(nil) key_idx=2 set_tx=0 seq_len=0 key_len=0
wpa_driver_nl80211_set_key: ifindex=3 (wlan0) alg=0 addr=(nil) key_idx=3 set_tx=0 seq_len=0 key_len=0
hostapd_free_hapd_data(wlan0)
Interface initialization failed
wlan0: interface state UNINITIALIZED->DISABLED
wlan0: AP-DISABLED
wlan0: Unable to setup interface.
hostapd_interface_deinit_free(0x1a9fcd8)
hostapd_interface_deinit_free: num_bss=1 conf->num_bss=1
hostapd_interface_deinit(0x1a9fcd8)
wlan0: interface state DISABLED->DISABLED
hostapd_bss_deinit: deinit bss wlan0
wlan0: Deauthenticate all stations
nl80211: sta_remove -> DEL_STATION wlan0 ff:ff:ff:ff:ff:ff --> -22 (Invalid argument)
wlan0: AP-DISABLED
hostapd_cleanup(hapd=0x1aa09e0 (wlan0))
hostapd_free_hapd_data: Interface wlan0 wasn't started
hostapd_interface_deinit_free: driver=0xd8b84 drv_priv=0x1aa2e20 -> hapd_deinit
nl80211: deinit ifname=wlan0 disabled_11b_rates=0
nl80211: Remove monitor interface: refcount=0
nl80211: Remove beacon (ifindex=3)
netlink: Operstate: ifindex=3 linkmode=0 (kernel-control), operstate=6 (IF_OPER_UP)
nl80211: Set mode ifindex 3 iftype 2 (STATION)
nl80211: Teardown AP(wlan0) - device_ap_sme=1 use_monitor=1
hostapd_interface_free(0x1a9fcd8)
hostapd_interface_free: free hapd 0x1aa09e0
hostapd_cleanup_iface(0x1a9fcd8)
hostapd_cleanup_iface_partial(0x1a9fcd8)
hostapd_cleanup_iface: free iface=0x1a9fcd8

Error: Failed to run hostapd, maybe a program is interfering.
Doing cleanup.. done

colse it ,thx


Feature request: Disable update check

Feature request:

Configuration to disable update checker. We have our own out-of-band automagical update checker.

There is no update checker in Panilla.

What is the reason to reach out to api.spigotmc.org ?

Panilla does not reach out to api.spigotmc.org
Have you downloaded your version from spigotmc.org or compiled it yourself?

Here is the file referenced in that paste.
https://github.com/Ruinscraft/Panilla/blob/master/bukkit/src/main/java/com/ruinscraft/panilla/bukkit/PanillaPlugin.java

Downloaded fro SpigotMC.

I am not sure what software you use to detect outgoing HTTP connections but Panilla certainly isn't making a connection to api.spigotmc.org. Perhaps this is some type of false positive?
Here's the decompiled PanillaPlugin file from the downloaded binary on SpigotMC
https://paste.ubuntu.com/p/9HZKyX2y62/
I encourage you to decompile it yourself. I am very much against auto updaters and making unnecessary HTTP connections.

Agreed. So I don't understand why JavaPluginLoader is making that call, if Panilla doesn't request it. In any event, we block it. But just trying to understand, and eliminate the tracking report, if possible.

The report is from NetworkInterceptor.

Have you tested with and without Panilla? Any difference?

Will do. I see that many other plugins are making similar calls. Perhaps I should address it with Luck. :(

Also, is this a recent phenomenon? When did you start using NetworkInterceptor and when did this start flagging Panilla?

Just started, so new to me.

Perhaps try a test server with only NetworkInterceptor and Panilla. You can verify for yourself it isn't Panilla making the HTTP request. I do think this is strange.

Agreed. I started using NetworkInterceptor after our network report of these outbound calls.

This has been on the Panilla resource page ever since I posted it, haha

Thanks for the fast response. We'll also try to have a look at JavaPluginLoader. The issue may lie there.

Explanation from my dev: For premium plugins, Spigot injects a very simple "anti-piracy" feature (the loadConfig0 method) that generates a nonce number for each purchase of a premium resource. Then the method calls the Spigot API to make sure the user who bought the plugin (or rather the nonce generated) has access to it.
But since I block the calls, and still use the plugins (which I have purchased), the security protection is zero.
Further explanation from my dev: The way it's set up is that if the call fails, it'll let you play anyway.
This is because of the premium resource guidelines, which state that the plugin must work without an internet connection.

Ah yes, I forgot about that anti-piracy feature. Thanks for the explanation.


Handle missing field in error response

Summary
When adding a field submission response had a error that did not map to any field, it considered as if no errors occurred and closed. Now we are showing a general error specifying the field and the error.
Ticket Link
https://mattermost.atlassian.net/browse/MM-34640
Related Pull Requests
Mobile: https://github.com/mattermost/mattermost-mobile/pull/5461
Release Note
NONE

/update-branch

Error trying to update the PR.
Please do it manually.

@DHaussermann I reviewed the logic of this, and here is a rundown:

If there are valid errors in the form, the "invalid errors" are ignored
If there are no valid errors in the form (neither field or general) but there is an "invalid error", the invalid error will show at the top of the form with the following message:

Received an error for an unknown field. Field name: `{field}`. Error:\n{error}

I will update the test app so you can test this.

@DHaussermann master of the test app has the needed command.

Thanks @larkox with /test valid open_markdown_form_modal_missing_error I now see the error as expected.
One last thing...

If there are no valid errors in the form (neither field or general) but there is an "invalid error", the invalid error will show at the top of the form with the following message:

This likely was the case before this PR but can this also be validated with the test-app?

The /test valid open_markdown_form_modal (or something like that) has errors everywhere, including a missing error.

Thanks @larkox the explanation with bullets above makes sense to me now 👍


Export ONNX 4 bit

feature
Hi ,
Firstly, I would like to express my gratitude for your released model. I attempted to export the 4-bit Llava model to ONNX, but encountered an error indicating that ONNX does not support it.
es.py", line 248, in forward
out = bnb.matmul_4bit(x, self.weight.t(), bias=bias, quant_state=self.weight.quant_state)
File "/home/zghaderi/miniconda/envs/test/lib/python3.10/site-packages/bitsandbytes/autograd/_functions.py", line 579, in matmul_4bit
return MatMul4Bit.apply(A, B, out, bias, quant_state)
File "/home/zghaderi/miniconda/envs/test/lib/python3.10/site-packages/torch/autograd/function.py", line 506, in apply
return super().apply(*args, **kwargs)  # type: ignore[misc]
RuntimeError: _Map_base::at
Do you have any suggestions or plans to incorporate ONNX model export?

Hello, have you successfully converted to onnx

searching for  solutions

searching for solutions


Component coloration not working

Vue - Official extension or vue-tsc version
Vue - Official extension version 2.1.6
VSCode version
1.93.1
Vue version
3.4.21
TypeScript version
~5.4.0
System Info
System:
    OS: Linux 5.15 Ubuntu 22.04.4 LTS 22.04.4 LTS (Jammy Jellyfish)
    CPU: (8) x64 Intel Xeon Processor (Skylake, IBRS, no TSX)
    Memory: 10.03 GB / 15.24 GB
    Container: Yes
    Shell: 5.1.16 - /bin/bash
  Binaries:
    Node: 20.10.0 - ~/.nvm/versions/node/v20.10.0/bin/node
    npm: 10.2.3 - ~/.nvm/versions/node/v20.10.0/bin/npm

package.json dependencies
"dependencies": {
    "@primevue/themes": "^4.0.0",
    "axios": "^1.7.7",
    "dotenv": "^16.4.5",
    "luxon": "^3.5.0",
    "pinia": "^2.1.7",
    "primevue": "^4.0.7",
    "vue": "^3.4.21",
    "vue-i18n": "^9.13.1",
    "vue-material-design-icons": "^5.3.0",
    "vue-router": "^4.3.0"
  },
  "devDependencies": {
    "@primeuix/styled": "^0.0.5",
    "@rushstack/eslint-patch": "^1.8.0",
    "@tsconfig/node20": "^20.1.4",
    "@types/jsdom": "^21.1.6",
    "@types/luxon": "^3",
    "@types/node": "^20.12.5",
    "@vitejs/plugin-vue": "^5.0.4",
    "@vue/eslint-config-prettier": "^9.0.0",
    "@vue/eslint-config-typescript": "^13.0.0",
    "@vue/test-utils": "^2.4.5",
    "@vue/tsconfig": "^0.5.1",
    "cypress": "^13.7.2",
    "eslint": "^8.57.0",
    "eslint-plugin-cypress": "^2.15.1",
    "eslint-plugin-vue": "^9.23.0",
    "jsdom": "^24.0.0",
    "npm-run-all2": "^6.1.2",
    "prettier": "^3.2.5",
    "sass": "^1.77.0",
    "start-server-and-test": "^2.0.3",
    "typescript": "~5.4.0",
    "unplugin-vue-components": "^0.27.0",
    "vite": "^5.2.8",
    "vitest": "^1.4.0",
    "vue-tsc": "^2.0.11"
  },
  "packageManager"<EMAIL_ADDRESS>}

Steps to reproduce
Installing the newest extension version (2.1.6) breaks the coloration of the components and they are shown like normal html tags in the template.
Rolling back to version 1.8.27 fixes the issue.
I am connecting to a remote sandboxed server via the remote-ssh extension.
No related errors in the vscode developer tools nor on the output channel for the extension.
What is expected?
I am expecting the newest version to work  as expected, recognizing the components and adding a different color from the other html tags.  (when hovering, components are indeed recognized and their definition is shown, but the coloration is not applied)
What is actually happening?
Updating to the newest version or any version 2+ breaks the coloration of vue components (but still recognizes them)
Link to minimal reproduction
No response
Any additional comments?
I have tried deleting cache on both the remote server and locally
tried different typescript versions
tried uninstalling all extensions and installing only the Vue official extension. (nothing changed)
tried rebooting my server
What is interesting, is that opening the same vuejs project on another remote server the same way, did not have the same issue.
I am not sure what could even be causing this issue.

What theme are you using? By calling the editor.action.inspectTMScopes command on the component name, it can be seen that the semantic token type is correctly emitted, but some themes do not handle it.

@KazariEX  here's an example output from the editor.action.inspectTMScopes command:

I've tried many themes, none making any difference. I am using the default Dark+ theme

It seems semantic token is not working, @KazariEX do you know if vscode can turn server capabilities off in someway ( I did not found)? But the server it self should have no issue since you had it work in another server.
Can you also confirm the configuration for both server are the same, e.g. set editor.semanticHighlighting.enabled to false will disable semantic highlighting. Not sure if vscode has other settings may effect it.

editor.semanticHighlighting.enabled is set to configuredByTheme on both sides.
What is interesting, is that it just broke when using a local repository. The only change I might have done is to change the version of the vue extension back and forth to earlier and newer versions.
uninstalling and installing again doesn't help. settings have not been changed since. I am thinking it might be something cache related, but I have tried deleting it:
C:\Users<USER>\AppData\Roaming\Code\CachedData
is there any other related cache that is to be deleted?

Try setting it to true?

yes, tried that :/ but, same.

uninstalling and installing again doesn't help. settings have not been changed since. I am thinking it might be something cache related, but I have tried deleting it:
C:\Users\AppData\Roaming\Code\CachedData

The cache should on server not your window local, and I dont really feel it's a cache thing. Based on what you have done, it's really became some kind of mysterious since you mentioned it works in another server and the types are correctly inferred . Two last thing probably worth to try:

remove node_modules and re-install
Try a new project create with vite create	see if it has the same issue.

removing and re-installing node_modules did not help, but I found that it is related to either the packages I am using (the dependencies) or to yarn.
creating a new project did have the colors correctly, then replacing the package.json with the old one that I am currently using caused the issue.
Seems there is a problem with yarn v4+ ? (installing with npm was OK)
I will investigate further and will comment again.

removing both node_modules and lockfile, and re-installing seems to have solved the issue.(removing either one separately didn't have effect).
Works with all npm, yarn 1.22 and yarn v4.
Closing as solved. thanks @RayGuo-ergou @KazariEX


[REEF-792] Find actual memory on the machine in ContainerManager,java

This patch:

Calls the OperatingSystemMXBean to get the actual memory size on the machine
Uses the default memory size if the call fails

JIRA:
REEF-792

@zerg-zerg I'm not convinced this does the right thing - the JIRA item wants to find the memory on the Evaluator node, not on the current node in which the driver runs.

@afchung This is for the local runtime and hence correct.
@zerg-zerg I did a pass as well.

@markusweimer I see, I missed that, sorry!

Other than the points Markus mentioned, this looks fine to me. Thanks!

Hi, all. It looks good to me, too.
By the way, is it possible to move the following code into org.apache.reef.util.MemoryUtils? We can reuse this logic in other places.
try {
+          long memorySizeInBytes = ((com.sun.management.OperatingSystemMXBean) ManagementFactory
+                    .getOperatingSystemMXBean()).getTotalPhysicalMemorySize();
+
+          memorySizeInMB = Ints.checkedCast(memorySizeInBytes / BYTES_IN_MEGABYTE);
+        } catch (Exception e) {
+          memorySizeInMB = this.defaultMemorySize;
+        }

On more thing, please replace ',java' into '.java'  in the commit log.

I updated this request

@zerg-zerg Thanks. I left one more minor comment. Otherwise, I am +1 on merging, but can't do it myself due to computer issuers.
@afchung Can you merge after this last change?

@markusweimer Done

OK, I'll test and merge this.


Join Community

Slack channel:
https://join.slack.com/t/flowercorp-slack/shared_invite/zt-19oj8ecqb-V02ycMV0BH1~Tn6tfeTz6A

join us!
@gozeloglu @icemint0828 @Roderland @Reid00

What is the task of this community and what are the requirements for member?

What is the task of this community and what are the requirements for member?

You can share your ideas or problems in the community with other rosedb developers and users.
RoseDB is also an open project that anyone can contribute to.


typo: suport -> support

@nschonni : Thanks for your contribution! The author, @maggiesMSFT, has been notified to review your proposed change.

Merging typo fix.

@ktoliver : Thanks for your contribution! The author, @maggiesMSFT, has been notified to review your proposed change.


Switching to tsx for running commands and scripts

Better ESM support outta box.
Easy to use.
Press F to pay respect to SWC and @swc-node/register.
You did it great.

coverage: 100.0%. remained the same
when pulling 4c663b5ec3681597fce538df3d792a272ecf3ff5 on use-tsx
into f0491ee839dcf9ca68a6a768ed7ffa630caa826f on master.


Changes for creation of lists in Neo4j

I couldn't create lists from properties in BioCypher's current state. So, I changed some elements to create lists from properties. I added double star mark to join elements of lists then replace this mark with array delimiter in _write.py. With that, I was able to create lists in my properties during admin-import. However, this can be done in _create.py by simply joining lists with selected array delimiter. Another thing I changed is headers. To make headers compatible to list format, I added string[] to header creation so that neo4j can detect the format as a list. Lastly, when I create admin-import-call.sh file after selecting the delimiter as a \t, it writes "    " instead of "\t" which causes error while importing. I manually fixed that issue as well.

In addition, I think sensitive marks such as delimiter and array delimiter marks can also be replaced in _create.py

2e2490922c5924bc122034dee02ece11f774db13 fixed that for me, should be fine now


clip-path isn't prefixed

What as awesome library – thank you! It seems as though clip-path isn't properly prefixed with -webkit- in Chrome, though.
-Ben Leibert

This seems to still be an issue in Safari 10.

Yeah, this is a known issue for properties that come from SVG. In a nutshell, -prefix-free sees that the unprefixed property is also available and thinks it doesn't have to do anything about it. It doesn't know that they don't both accept the same syntax…


Roll Packages from<PHONE_NUMBER>bf to 27c98537ccac (3 revisions)

https://github.com/flutter/packages/compare/0321757447bf...27c98537ccac
2024-09-28<EMAIL_ADDRESS>[pigeon] fix int bug (flutter/packages#7725)
2024-09-28<EMAIL_ADDRESS>[pigeon] update deprecated command in README of the example (flutter/packages#7709)
2024-09-27<EMAIL_ADDRESS>[google_maps_flutter] Fix incorrect comment: Change "marker" to "polyline" (flutter/packages#7664)
If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/flutter-packages-flutter-autoroll
Please CC<EMAIL_ADDRESS>on the revert to ensure that a human
is aware of the problem.
To file a bug in Flutter: https://github.com/flutter/flutter/issues/new/choose
To report a problem with the AutoRoller itself, please file a bug:
https://issues.skia.org/issues/new?component=1389291&template=1850622
Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md

Commit queue failed; closing this roll.


Add paragraph explaining that table properties can change their seman…

…tics
Also replaced the word 'attribute' when it was referring to a table
'property', to make the word 'property' consistently used for that
thing everywhere.
Fixed a couple occurrences of 'action' that should have been the
standard table property name 'actions'.

The most significant change here is the new 2nd to last paragraph in the diff starting with "Additional properties are permitted".  Everything else is as described in the commit comments above.  I can back out all of the other changes if this is too off-topic.

Mihai,
I agree. The best way would be to periodically standardize more "popular"
properties. Additionally it might make sense to agree on the naming for
vendor-specific properties, so that people can clearly see them in the code.
Thanks,
Vladimir
On Tue, May 9, 2017 at 10:30 AM, Mihai Budiu<EMAIL_ADDRESS>wrote:

@mbudiu-vmw commented on this pull request.
In p4-16/spec/P4-16-draft-spec.mdk
https://github.com/p4lang/p4-spec/pull/189#discussion_r115550853:

-A table declaration indicates the interfaces expected from a table: keys and actions. However, the best way to implement a table is actually dependent on the nature of the entries that will populate the table at runtime (for example, tables could be dense or sparse, could be implemented as hash-tables, associative memories, tries, etc.) An implementation attribute could also be used to pass additional information to the compiler back-end. The value of this attribute could be an instance of an extern block chosen from a suitable library of components. For example, the core functionality of the P4~14~ table action_profile constructs could be implemented on architectures that support this feature using a construct such as the following:
+Additional properties are permitted to change the semantics of a table lookup. For example, an architecture could define a property default_action_undefined that, when given the value true, causes the behavior of the data plane to be undefined for any packet that found no match when searching the table.
We have to be careful with the semantics of table lookup, if it can be
arbitrary, then the compiler cannot really reason about the behavior of
programs. The compiler assumes the semantics in the diagram.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/p4lang/p4-spec/pull/189#pullrequestreview-37098497,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AMPb8y4xfkStrLQDYCixGy_cAu9SL35_ks5r4KKcgaJpZM4NUuUB
.

@vgurevich I don't see how to standardize vendor-specific properties and be open to extensions (as is the intention of this feature). What we can do is restrict which parts of the semantics of table lookup they are allowed to affect.

I think that the semantics of the lookup should never change; the lookup is given a key and returns an action and a hit bit.
What can change is how this lookup is done, or how the actual table is implemented.

I don't see how to implement @jafingerhut's default_action_undefined with those types. What action would be returned -- e.g., for a table with nothing in its action list?

It is not clear the compiler should accept a table with no actions.
The compiler assumes that one of the actions will run, and nothing else.
The dataflow analysis for tables makes a join of the dataflow produced by all actions.
If that's not true all bets are off.

You're right: the grammar does not allow the empty list of actions.
Still, what action should be produced if the table misses and there is no default action? If the default_action_undefined, would the onus be on the target to interpret a "0" hit bit and an arbitrary action as undefined (or target-specific) behavior? I suppose that could work, although it's kind of kludgy since the types are being abused ;-)

Whatever it is, the compiler will assume it is one in the list. Otherwise the meaning of the program is undefined. Which is perhaps what the user wants.

So maybe the right thing to say is that targets may support other properties that control how the results of table lookups (action and hit) are interpreted. For example, default_action_undefined...

@jnfoster ,
The way to standardize is to adopt certain conventions on how to name these additional properties, e.g. by suggesting that vendors always name their properties as VENDOR_XXX_ or something. This can be published later in a separate "best practices" doc.  Separately, we can maintain a list of commonly recognized properties, such as "counters", "meters", etc.

This kind of convention is fine, but it doesn't resolve the issue that @mbudiu-vmw raised: if the compiler relies on all tables to have a certain set of behaviors to do its job, then a vendor cannot  modify that behavior or the compiler will be broken. Hence, we must restrict what vendor extensions can do. (Exception: if the behavior with these extensions becomes completely undefined -- i.e., not just an undefined value, but C-style undefined behavior then we could have our cake an eat it too.)
I think the solution proposed above resolves it -- i.e., vendor-specific properties can change whether/how an action and hit/miss metadata are interpreted on the packet state. Mihai would have to confirm that this is a strong enough guarantee for the compiler.

Here is an example of a table with a slightly different behavior that started the whole conversation. A directly indexed table, which has 2^n entries and indexed by an n-bit-wide key. In many implementations, entries in such tables do not have a "valid" bit and therefore there can be no miss and thus no default action per se. From the control plane standpoint, there are two approaches that the driver designer can take:

Provide the same add/delete APIs as for regular table, but every time a delete happens, the action portion of the actual entry is overwritten by the default action. That's why there is no default/default -- the default action has to always be chosen.
Provide set() APIs instead, meaning that all the entries are always present in the table and the control plane can only change them, but there is no "delete"

Neither of these approaches are inconsistent with the semantics we adopted: no default action means a miss in a table does not change the packet state (because false implies anything).


Can someone give me an example of nuxt3 ts referencing cesium's demo?

It's not correct to use it like me.

After running, that's it.

Hi there,
CesiumJS is a big project, so we use GitHub for feature requests and bug tracking exclusively. In the future, please take any questions to the Cesium Forum where there are members of the community and developers from the team who can help.
Thanks!


Fix wrongly placed strings

The translated string was committed into the English strings and vice versa, this swaps them back.

Thanks! I didn't notice that.


Bug in Android when unregisterVideoFrameObserver

@littleGnAl @LichKing-2234 @uzawa-gmo
Do I fix it?

it has been fixed


BadgeFramework - sending badge_id and group_number

In badge_protocol.py (the old protocol-implementation) l.114 and 115 the badge_id and group_number is only set, when != 0. So if one of them is 0, the serialized message doesn't contain the "0" anymore, it is just ignored. So my implementation of the old-protocol assumes that both id and group number is transmitted at the same time. And I think the old firmware also assumes it, because it checks for the length of the received message, and this shouldn't match anymore.

We should force the protocol to accept both badge and project id. They can be 0's though


Vote For Name Here

phatefetch? valleyfetch?
tinyfetch? ironfetch? rustfetch? minifetch??

I was hoping something short and easy to type. That's why I suggested things like vfetch (short for valleyfetch), rsfetch (short for rustfetch), and etc.
Because no one wants to type a long every time, and they really shouldn't have to alias it due to a long name.

I kinda want to wrap this up (for some reason it bothers me to see issues open), so for now I'm going to change the name to rsfetch. If anyone doesn't like the name just let me know. :)


AnnounceSignatures resend in gossiper.

This PR adds state of AnnouceSignatures to the gossiper, making it retry sending it to the remote peer if it fails initially. This state is also persisted on restarts, making it retry sending the message if need be.
This should help the case where a peer has gone offline before receiving the announcement signatures, not making us able to craft the final channel proof, even though the peer comes back online.

I ended up rewriting this quite a bit, reverting the changes done to the WaitingProofStore, and instead storing the result of sending the announcement message in a separate database within the gossiper. This lead to a much smaller diff, and simpler logic, since the two set of states (Sent and Completed) now is handled separately. This should also get rid of the mentioned race.
In addition I added the suggested changes to the peer and server (see the fixup! commits), making the the queueing of messages not blocking, and added to the godoc an explanation of how to use the method to broadcast messages.

Another day, another revamp! Notable changes this time is that the resending logic is significantly simplified:

At startup we check all local proofs in the message store, and send them if we don't have the full proof. If we do, we just delete the local proof from the message store.
When sending the local proof, we add it to the message store first, but we don't delete it after a successful send. This because we cannot really know if the remote was able to store it. We will delete it at first gossiper startup after we have the full proof stored.
If we see the remote sending us his remote proof while we already have assembled the full proof, we send the full proof to the remote.
To make (3) possible, an additional check is added when attempting to add a ChannelAnnouncement to the router: if AddEdge fails with ErrIgnored/ErrOutdated we check if the edge we have in the graph already contains the channel proof, if not we add it at this point.


Translation json structure

Hello,
I am facing an issue regarding editing the exported translation json file via the tabular translator tool (https://www.sqlbi.com/tools/ssas-tabular-translator/). When a translation json file exported from tabular editor the section referenceCulture is missing (this section is generated when the translation json file exported from visual studio) and the tabular translator tool cannot process the file.
Thank you

Fixed in 2.8.4. Thanks for reporting!


Package cannot automatically be dropped, but is currently

The Package implementation must be changed. It's good that alpm_pkg_load is the only function that return a alpm_pkg_t which must owned but it can't be free automatically via Drop. In fact the common usage is to load a local tarball and then to install it. In the case of a successful install it must not be freed, otherwise it must be freed.
What I would do:

implement alpm_pkg_load in Transaction in a function which load a tarball and add the returned package to install, this way the package can freed manually in case of failure.
rename PackageRef as Package for name consistency.
maybe implement Package as Db with a struct keeping a reference to a alpm_pkg_t

I need to look at this again, but my first thoughts:
Maybe a successful install could take ownership of the package, and then not run the drop (using mem::forget or similar).

I've implemented an approach based on mem::forget. Need to check it works as expected.


Change to Minio's test container

It has more features, supports proper authentication, etc.

@vagaerg all comments addressed


Debugging variables not working with sourcemaps + uglify

I have the following gulp task for bundling javascript:
gulp.task('js', function () {
    return gulp.src(paths.js)
        .pipe(sourcemaps.init())
        .pipe(uglify())
        .pipe(concat('bundle.min.js'))
        .pipe(sourcemaps.write('./'))
        .pipe(gulp.dest('dist'));
});

When I run this in the Chrome dev tools, sourcemaps are found and breakpoints work, but variables can't be debugged.
Take this example chunk of angular code:
iarApp.config(['$animateProvider', function ($animateProvider) {
    $animateProvider.classNameFilter(/angular-animate/);
}]);

If I add a breakpoint to see the value of $animateProvider, I get the following:

But if I turn off variable mangling in Uglify:
.pipe(uglify({ mangle: false }))

Then it works:

So it seems that the gulp-sourcemaps plugin can't follow up variables after Uglify mangles the names.
Can anyone else get the same issue and/or know a solution?

+1 I also encounter the same problem. @fernandoneira, when you add a break point does it anchor exactly where you put it or does it stop in minify code ?

@phil-lgr I don't have problems anchoring in the source, that may be something else going with your source.
The variable mangling is, as I found out, a limitation of the current source map spec. It just doesn't support symbol mapping as I mentioned here: http://stackoverflow.com/questions/33913641/debugging-variables-not-working-with-gulp-sourcemaps-uglify/34872450#34872450

@fernandoneira I have just tried your workaround { mangle: false } and works fine. Thanks man!

Can this be be closed or does this need to be dug unto more? Will need to copy the workflow above into integration.js

This is a sourcemap problem, not a gulp-sourcemaps issue.


callsigns inside <> get cut-off

consider logs like:
200712 1304  11 -21 -1.1  14.097076  OZ7IT JO65 37           0     1    0
200712 1312   2 -28 -1.5  14.097110  PA0ANH JO22 27         -1  1922    0
200712 1322   1 -28 -1.1  14.097110  <PA0ANH> JO22LH 27     -1  5495   -2
200712 1326   3 -27  0.6  14.097006  HB9FID JN47 37          0   306    0
200712 1326   8 -23 -1.0  14.097162  DG7RJ JN58 37           0   155    0

but the fixed-position calls expected here:
https://github.com/swharden/FSKview/blob/824d92e85640ecb7c816851bc7b264703a39c6d6/src/FSKview/WsprSpot.cs#L142

Here's a full log file provided by Ko, NL9222
ALL_WSPR (4).TXT

resolved, will be in FSKview 1.0.8 uploaded in a few minutes...


WIP: Phase two - framework and base implementations

Framework and base implementations for phase two of SparseML:

imports, check installs and versions, and require installs decorators for frameworks
framework info implementations for getting availability of functionality within frameworks
sparsification info in prep for getting availability of sparsification algorithms within frameworks
generic ability to call into core functionality with an item and detect proper framework to run

TODO:

unit/integration tests
generic callable script for framework_info and sparsification_info


libxc: 6.2.2 -> 7.0.0

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://repology.org/project/libxc/versions.
meta.description for libxc is: Library of exchange-correlation functionals for density-functional theory
meta.homepage for libxc is: https://www.tddft.org/programs/Libxc/
Updates performed

Version update

To inspect upstream changes
Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 7.0.0 with grep in /nix/store/8jd3zfnkngq9f2sxbsvqqjzl6wn2zjk5-libxc-7.0.0
found 7.0.0 in filename of file in /nix/store/8jd3zfnkngq9f2sxbsvqqjzl6wn2zjk5-libxc-7.0.0

Rebuild report (if merged into master) (click to expand)

15 total rebuild path(s)

15 package rebuild(s)

First fifty rebuilds by attrpath

cp2k
libxc
octopus
openmolcas
python311Packages.gpaw
python311Packages.pyscf
python311Packages.simple-dftd3
python311Packages.sirius
python312Packages.gpaw
python312Packages.pyscf
python312Packages.simple-dftd3
python312Packages.sirius
quantum-espresso
sirius

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/8jd3zfnkngq9f2sxbsvqqjzl6wn2zjk5-libxc-7.0.0 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A libxc https://github.com/r-ryantm/nixpkgs/archive/97f57ea4fe7d89a877ab994f7089def29acb3b61.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/97f57ea4fe7d89a877ab994f7089def29acb3b61#libxc

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/8jd3zfnkngq9f2sxbsvqqjzl6wn2zjk5-libxc-7.0.0
ls -la /nix/store/8jd3zfnkngq9f2sxbsvqqjzl6wn2zjk5-libxc-7.0.0/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
nixpkgs-review result
Generated using nixpkgs-review.
Command: nixpkgs-review

x86_64-linux

:x: 22 packages failed to build:

cp2k
octopus
openmolcas
python311Packages.gpaw
python311Packages.gpaw.dist
python311Packages.pyscf
python311Packages.pyscf.dist
python311Packages.simple-dftd3
python311Packages.simple-dftd3.dist
python311Packages.sirius
python311Packages.sirius.dev
python312Packages.gpaw
python312Packages.gpaw.dist
python312Packages.pyscf
python312Packages.pyscf.dist
python312Packages.simple-dftd3
python312Packages.simple-dftd3.dist
python312Packages.sirius
python312Packages.sirius.dev
quantum-espresso
sirius
sirius.dev

:white_check_mark: 2 packages built:

libxc
libxc.dev

Maintainer pings
cc @markuskowa for testing.

[!TIP]
As a maintainer, if your package is located under pkgs/by-name/*, you can comment @NixOS/nixpkgs-merge-bot merge to automatically merge this update using the nixpkgs-merge-bot.

Add a :+1: reaction to pull requests you find important.

Converting to draft, Libxc-7 breaks all packages.
Please do not close this PR.

See also https://github.com/NixOS/nixpkgs/pull/348409  for tracking.


[T4A5][T13-B2] Gabriel Gheorghian

Ready for review.

Referenced #1245 for guidance

@GabrielGhe Overall nice work.
Some comments added. Please close the PR after reading comments


odb: support for PROPERTY LEF58_FORBIDDENSPACING

@maliberty Jenkins was failing, but nothing was wrong with the code. I think this PR is ready for review.

Failing "Check That ODB Files Are Generated "

Failing "Check That ODB Files Are Generated "

Fixed. I didn't notice the missing "schema" field for the new rule.


use aws-admin_credentials.csv

change from aws-admin_accessKeys.csv to aws-admin_credentials.csv.

OK


How to change color of spinner and progress bar?

+1: Solved my problem

@chieffancypants shouldn't there be the API support to change CSS? Over-riding CSS is not a good practice.

Over-riding CSS is not a good practice

According to whom?  That's the entire point of CSS -- it's why projects like bootstrap are so popular, they give you sane defaults, and from there, you override the styles to fit the org's brand.  Exact same concept here.
Moreover, APIs should have nothing to do with styles.  You're mixing concerns that were separated on purpose.


leaderboard error and manager have been define before

Create the ScenarioManager
    self.manager = ScenarioManager(args.timeout, args.debug > 1)

Traceback (most recent call last):
File "D:\transfuser\transfuser\leaderboard\leaderboard\leaderboard_evaluator.py", line 122, in del
self._cleanup()
File "D:\transfuser\transfuser\leaderboard\leaderboard\leaderboard_evaluator.py", line 134, in _cleanup
if self.manager and self.manager.get_running_status()
AttributeError: 'LeaderboardEvaluator' object has no attribute 'manager'

what exactly did you do, such that this error appears?


Create at least 3 weapons for shootemup

Beam, AoE, Projectile?
Laser, missiles, auto-cannon?

basic laser, penetrating laser, long range laser are ready
basic missile launcher is ready
still need a few more missiles and a shotgun


hide ice adapter info window, bump adapter to v2.4.1

But what if ice adpter does not terminate how do i close it (Taskmanager ??)

Also ho do i turn it on?

The ice adapter now has a tray icon, that signals it is still running and when clicked opens the info window able to kill it and show the debug window. (which can also send notifications to your system)

ok cool

Is java fx available?

Probably not he uses jdk 11

Yeah @Geosearchef we need to either apply the workarround we did in the client or u go modular


Cannot use multiple Windows in WinUI 3 1.0.0 Preview

Describe the bug
When I try to create a new Window other than the MainWindow, it throws an Exception from KernelBase.
When I try to create a new AppWindow, I cannot find a way to set a content.
The AppWindow shows fine, but without content.
In UWP we used ElementCompositionPreview.SetAppWindowContent(appWindow, new Page()); but this does not exist in WinUI 3.
In WinUI 3 Experimental we first created the new Window(), then got the AppWindow from the Windows Handle and Window ID.
Steps to reproduce the bug

Create a new WinUI 3 1.0.0 Preview Desktop app
Create methods from screenshots
Not able to use multiple windows with my app

Expected behavior
Desktop app should be able to use multiple windows. Also the Window.Activate() worked fine in WinUI 3 1.0.0 Experimental for multiple Windows on same thread.
Screenshots

Version Info
WinUI 3 1.0.0 Preview Desktop, Windows 10 19044, Visual Studio 2019 16.11.2
NuGet package version:

Windows app type: Win32 x86
| Windows version
| Insider Build (19044)
| Device form factor | Saw the problem?
| Desktop
Additional context
Need this as fast as possible.
Our current UWP app have grown so large that RH-Bind goes out of memory even in x64 compiler, and currently unable to build. Also our current UWP app is using gRPC.Core wich have production bugs that are solved when using WinUI and Net 5.
This is a large LOB app.

Unfortunately the support for multiple Windows was not finished in time to be included in 1.0. The Experimental build had the block for this and other incomplete features disabled, and those blocks are re-enabled for Preview and Stable releases.

Ohh, thank you for the answear.
It still looks like Winui 3 <IP_ADDRESS> Experimental is more stable than our current UWP build, so I think we will have to go to production with this. But please disable the block in next WinUI 3 Preview. It works perfectly fine for our needs in the Experimental build, with only 1 workaround for activating the window (it displays back the mainwindow when heavily loaded with ui objects).

how to create Window on Window in winui3 with wpf  preview 1.0?

Any workarounds for this?

Multiple Windows on the same thread is now supported in Windows App SDK 1.0.1. Check out the release notes for more info.

@codendone I'm still seeing this happening on my Windows 10 PC. Exact same code works on my Windows 11 PC. Both 1.0.1 and 1.1.0-preview1 has this behavior.

The release notes didn't mention anything about it being a Win11-only thing.

@dotMorten I think you logged microsoft/WindowsAppSDK#2363 for what you were hitting?

Yeah it was due to another bug in the app Sdk packaging system that led to that behavior. It’s a deployment issue if mixed versions that was causing it: ignore my comment above


Update metadata in database for submission '653f646de6cd82000152e763'

By user request, I needed to update metadata for 2 studies with sumstats: GCST90296499 and GCST90296498
In the submission template, through the DepoCuration App, I edited the following columns:
analysis_software: PLINK.
readme
I also edited the reported traits to:
Educational attainment (years of education)(excluding related participants)
In the yaml file on staging, I edited:
reported_trait
author_notes [same as readme in template]
analysis_software [same as template]
Please amend this information in the database as well
Submission template:
Chen_TT_-_user_submission-L2-_ST3 - update (4th study).xlsx

@eks-ebi to add to next user support epic

@earlEBI will re-upload the metadata template to re-initiate

@earlEBI will re-upload the metadata template again to re-initiate

@earlEBI we confirmed analysis_software exists in mongo but not Oracle.

Done. Looks good. Ticket can be closed.


rewrite: allow custom id generation

A common scenario is to go through a page of content and apply sre-to-tree to every equation. In this case, there can easily be identical equations, leading to identical ids. While this doesn't cause any real issues, it's invalid.
Since we cannot guess this here, authors might want to to customize the ids.

I'm not sure how I feel about it. Authors can of course fix this themselves by randomly modifying duplicate equations (e.g., adding IDs - duh). They could also post-process to make IDs unique. So I don't know how far I'd go. Just a counter or full custom functions? It's a rabbit hole with limited gain, I think.

With #20 this will no longer be necessary.


AN-4799/Backfill Migration

Adds a new set of parameterized bronze views on the external tables for the backfill. The silver  models will pull in the backfill data when LOAD_BACKFILL and a network version is passed with the dbt run command.
Transactions Final, Events  and curated models updated to load incrementally based on modified_timestamp to parse the new data.
Load 1 network version at a time to the silver models. Once everything is in, the gold views can be updated to remove the UNION to the chainwalkers data and the silver_cw directory can be deleted, with each of those models being dropped from the prod db.

Last TODO - update incremental filter on remaining curated models to migrate to modified timestamp

Migrated incremental logic in curated models (tag:scheduled_non_core). Onchain metadata models did not get the col additions and need to be FR'd to add the modified_timestamp col or the incremental logic will fail. Takes <3mins for thse 8.
dbt run -s models/silver/nft/metadata/onchain --full-refresh


[Notifications] - fix notification item aligment

amount of new notifications should be placed above the bell

Done!


Update docs to reflect required Python version

I just started using reactionmenu in one of my Discord bots today, and I had trouble running it in Python 3.6. I updated to Python 3.9 and it worked fine. I did some digging and it turns out the issue is with the create_task method. You use the name parameter that wasn't added until 3.8. So it should work fine with Python 3.8+, but anything earlier will run into that error. Just thought you should know so you can update the docs--not expecting a fix for earlier versions.

In v1.0.9, the name parameter was removed from all create_task, but who knows when I might use it again in the future or any other Python 3.8+ features. It's always a good idea to show what version of Python is needed in order for the package to work properly. I will update the docs. Thank you! 👍

I could have sworn I saw name used in one line of 1.0.9, but you're right I don't see it now. Thanks for adding the version note anyway!


Can not receive interface{} type of value in request body

Describe the bug
A clear and concise description of what the bug is.
I wish to receive any type of request body. But go-zero seems not support interface{} type of value.
To Reproduce
Steps to reproduce the behavior, if applicable:

The code is
type (
        CreateDemoReq {
                Data interface{} `json:"data"`
        }
        CreateDemoResp struct{}
)

service Demo {
        @handler CreateDemo
        post /api/v1/demos (CreateDemoReq) returns (CreateDemoResp)
}

The error is
# curl localhost:8888/api/v1/demos -H 'Content-Type: application/json' -d '{"data": "some"}'
error: type mismatch for field data

Expected behavior
A clear and concise description of what you expected to happen.
Request success
Screenshots
If applicable, add screenshots to help explain your problem.
Environments (please complete the following information):

OS: centos7
go-zero version 1.3.4
goctl version 1.3.5

More description
Add any other context about the problem here.

It's by design, we prefer concrete types. Closing.

it work for me!
using json Unmarshal to  read interface{} type data
func SaveSaveDataHandler(svcCtx *svc.ServiceContext) http.HandlerFunc {
	return func(w http.ResponseWriter, r *http.Request) {
		// read bytes data from body
		bytes, err := io.ReadAll(r.Body)
		if err != nil {
			httpx.ErrorCtx(r.Context(), w, err)
			return
		}
		//  parse bytes json data to struct
		var req types.CreateDataDto
		err = json.Unmarshal(bytes, &req)
		if err != nil {
			httpx.ErrorCtx(r.Context(), w, err)
			return
		}
		// pass params to my save data logic
		l := productVersion.NewSaveDataLogic(r.Context(), svcCtx)
		resp, err := l.SaveData(&req)
		if err != nil {
			httpx.ErrorCtx(r.Context(), w, err)
		} else {
			httpx.OkJsonCtx(r.Context(), w, resp)
		}
	}
}


Fix typo in wasm-bindgen-test usage docs

The bindgn force is strong with you :smile:

Oops, thanks!


[CT-2176] [Feature] Report bytes processed for tests

Is this your first time submitting a feature request?

[X] I have read the expectations for open source contributors
[X] I have searched the existing issues, and I could not find an existing issue for this feature
[X] I am requesting a straightforward extension of existing dbt-bigquery functionality, rather than a Big Idea better suited to a discussion

Describe the feature
As @elyobo commented in this closed issue https://github.com/dbt-labs/dbt-bigquery/issues/14#issuecomment-1295698710, it would be very nice to see the bytes processed by running tests in BigQuery.
Tests can consume a lot of bytes, especially when running tests like unique and not_null without where, where they scan the whole table.
Since BQ billing is based on these bytes, you can get surprised by an expensive bill because you have no idea of the costs of your tests when developing. So, it would be fantastic to see the cost of each test in the logs as we see for the models.
Describe alternatives you've considered
Currently, the information of bytes_processed for models is taken from total_bytes_processed from the query_job object.
https://github.com/dbt-labs/dbt-bigquery/blob/main/dbt/adapters/bigquery/connections.py#L491
I am assuming the query_job information is queried from INFORMATION_SCHEMA.JOBS. I checked it and jobs that run tests also return a value for total_bytes_processed.
I don't understand why in run_results.json tests don't return the bytes processed, as I didn't find any restriction in this code
https://github.com/dbt-labs/dbt-bigquery/blob/main/dbt/adapters/bigquery/connections.py
Maybe I am looking at the wrong code.
Anyway, the information is available and we already do this for models, so I think we can do this for tests.
Who will this benefit?
People working with dbt in BigQuery as they can monitor better the costs caused by dbt tests.
Are you interested in contributing this feature?
Yes, I am interested. I am not sure where the information for test results is written.
Anything else?
No response

Good news! Starting in v1.5 (currently available as a beta prerelease), this information will also be available for tests and source freshness checks, thanks to this contribution:

https://github.com/dbt-labs/dbt-core/pull/6645

You can try it out!
pip install dbt-bigquery~=1.5.0b1