Could not find 'audacity-win-3.2.0-64bit'! (error 16)

Updating 'audacity' (3.1.3 -> 3.2.0)
Downloading new version
audacity-win-3.2.0-64bit.zip (19.2 MB) [======================================================================] 100%
Checking hash of audacity-win-3.2.0-64bit.zip ... ok.
Uninstalling 'audacity' (3.1.3)
Removing shim 'Audacity.shim'.
Removing shim 'Audacity.exe'.
Removing shim 'Audacity.ps1'.
Unlinking ~\scoop\apps\audacity\current
Installing 'audacity' (3.2.0) [64bit] from extras bucket
Loading audacity-win-3.2.0-64bit.zip from cache
Extracting audacity-win-3.2.0-64bit.zip ... Could not find 'audacity-win-3.2.0-64bit'! (error 16)
所在位置 C:\Users\Winterreise\scoop\apps\scoop\current\lib\core.ps1:642 字符: 9
+         throw "Could not find '$(fname $from)'! (error $($proc.ExitCo ...
+         ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : OperationStopped: (Could not find ...it'! (error 16):String) [], RuntimeException
    + FullyQualifiedErrorId : Could not find 'audacity-win-3.2.0-64bit'! (error 16)

Happening to me a well.
audacity: 3.1.3 -> 3.2.0
Updating one outdated app:
Updating 'audacity' (3.1.3 -> 3.2.0)
Downloading new version
Loading audacity-win-3.2.0-64bit.zip from cache
Checking hash of audacity-win-3.2.0-64bit.zip ... ok.
Uninstalling 'audacity' (3.1.3)
Installing 'audacity' (3.2.0) [64bit] from extras bucket
Loading audacity-win-3.2.0-64bit.zip from cache
Extracting audacity-win-3.2.0-64bit.zip ... Could not find 'audacity-win-3.2.0-64bit'! (error 16)
At C:\Users\<redacted>\scoop\apps\scoop\current\lib\core.ps1:642 char:9
+         throw "Could not find '$(fname $from)'! (error $($proc.ExitCo ...
+         ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : OperationStopped: (Could not find ...it'! (error 16):String) [], RuntimeException
    + FullyQualifiedErrorId : Could not find 'audacity-win-3.2.0-64bit'! (error 16)

Fixed in #9296


Compiler tests should use generateSqlDelightFiles

This tests the production pathways more thoroughly but also allows testing the production error formatting/reporting.

DISAGREE
also a shitton of work. gradle tests use the tasks, i dont think the compiler tests need tot also


End point

Make the CLUSTER_ENDPOINT available to browser to be able to change it from the environment settings all at once.
Add constants to be able to select the currency and infers its dependencies directly in MainApp : all the hard coded variables are now dynamic (extracted from constants)

Thanks, but we aren't making many changes (e.g. currency selection) to the Point of Sale example.

Thanks, but we aren't making many changes (e.g. currency selection) to the Point of Sale example.

What ?!
You prefer to have hard coded values and ask people to change the currency by writing code (see how in the README.md file), instead of just changing a setting parameter in Vercel ???


Add synthetic gradient training per "Decoupled Neural Interfaces using Synthetic Gradients"

Cf. http://<IP_ADDRESS>/abs/1608.05343

yes please

Hi.
This is my experimental reproduction of "Decoupled Neural Interfaces using Synthetic Gradients"
https://github.com/rarilurelo/tensorflow-synthetic_gradient
There are two problems in my code for using Keras as a complete wrapper.

Initial gradient
Initial gradient can be set by Tensorflow(tf.gradient's grad_ys), but K.gradient has no argument for this.
Does anyone know how to set initial gradient by Theano?

control dependencies
An M which synthesis the gradients of the lower layer is trained by the true error descending from the upper layer.
This gif on DeepMind's blog is very useful to understand this flow(https://deepmind.com/blog/decoupled-neural-networks-using-synthetic-gradients/#gif-1).
The true error must be computed before the layer updated, so I need to use tf.control_dependencies.
I  think it can be implemented by modifying Model: _make_train_function() and Model's initial argument.
However tensorflow and theano have different ways to control dependencies, so it's difficult and will be ugly.

Thanks.

@rarilurelo Initial grads can be set in theano using known_grads option : theano.gradient.grad(cost, wrt, consider_constant=None, disconnected_inputs='raise', add_names=True, known_grads=None, return_disconnected='zero', null_gradients='raise')

@rarilurelo and @llSourcell Please put an example of RNN(LSTM) using synthetic gradient, which is no-where at internet. And one question:  how can we updates the weight using synthetic gradient at particular layer as LSTM layers shared weights so updating the weight of one layer can update the weights of other layers?

So was this implemented in Keras ?

@x0rb0t :(

https://github.com/mishig25/synthetic-gradients-keras


useSeoMeta doesn't work properly in an async composable

Environment
- Operating System: Windows_NT
- Node Version:     v16.16.0
- Nuxt Version:     3.6.5
- Nitro Version:    2.5.2
- Package Manager<EMAIL_ADDRESS>- Builder:          vite
- User Config:      devtools, imports
- Runtime Modules:  -
- Build Modules:    -

Reproduction
https://github.com/andreww2012/nuxt3-useSeoMeta-doesnt-work-properly-in-async-composable
Describe the bug

Let's say the script section of pages a and b is async and contains useSeoMeta call after awaiting the same async operation.
We want to avoid code duplication and move this code to a shared function (composable). Essentially, we replace this code with await thisNewComposable() expression.
After that, if we perform parallel requests to those pages, meta tags defined in useSeoMeta start randomly missing from the rendered HTML. This doesn't happen if we don't move that code in the composable.

Additional context
No response
Logs
No response

You will need to do something like this:
export const useMeta = async (name: string) => {
  const nuxtApp = useNuxtApp();
  await new Promise((resolve) => setTimeout(resolve, 1000));

  nuxtApp.runWithContext(() => useSeoMeta(() => ({
    title: `${name} layout title`,
    description: `${name} layout description`,
  })));
};

See more here: https://nuxt.com/docs/guide/concepts/auto-imports#using-vue-and-nuxt-composables

Thank you for pointing that out! I did manage to work this around using a different approach in the end.
Several factors lead me to not reading this piece of documentation:

No error messages. It worked absolutely fine, and I only started to suspect that something's not right when I started receiving emails from search engines complaining that meta tags are randomly disappearing on the production site. It took me around 6 hours in total to debug this :(
I don't use auto imports. Consequently, I didn't even read the "Auto-imports" page in the docs.
If even I did read that, it would probably take me a while to think of a solution that you proposed. useNuxtApp is not mentioned on that page, and runWithContext cannot be found in the whole documentation:

I would like to propose:

Documentation improvements in this regard (move this to a different section, more bad code examples + workarounds)?
Maybe make useSeoMeta (and possibly other built-in composables) to print the error in this case (if that is even possible).

And thank you and the whole team for your hard work on Nuxt, keep it up!

Those are excellent recommendations. Any PRs are welcome if you have specific suggestions.
cc: @harlan-zw - do you think we could do this in unhead or maybe wrap the composable in Nuxt to provide a better error message?

@harlan-zw the issue still persists after upgrading to<EMAIL_ADDRESS>by running npx nuxi upgrade --force.

provide clearer reproduction details, like not sure how you're doing this exactly

The reproduction instructions are provided in the README of the repository that I've linked in the first message. I'm not sure how it can be further improved.

@harlan-zw the issue still persists after upgrading to<EMAIL_ADDRESS>by running npx nuxi upgrade --force.

provide clearer reproduction details, like not sure how you're doing this exactly

The reproduction instructions are provided in the README of the repository that I've linked in the first message. I'm not sure how it can be further improved.

Oh nice, sorry I missed te readme :facepalm:

So the issue is that when you run anything that relies on the Vue app context after an async, the context is lost. Daniel's workaround is the correct solution to get around this for now.
An outstanding design issue with Unhead is that it tries to fallback to a shared head instance if the context is lost, which is resulting in the weird results you're seeing and it makes it a very difficult problem to diagnose.
There are already plans to change this logic but it may be a breaking change so was waiting for v2. There may be an alternative transitory solution that we can implement quicker though.
There is some work started on allowing context not to be lost after an async, but it doesn't apply to async composables. I think this would require some AST magic.

Thank you for the detailed explanation, it makes a lot of sense. I just wish it would fail with an error in this case or something similar. 😅

Are you able to provide the work around you used out of curiosity?
It's having to do with changing the logic of the app to avoid using an async composable, so I believe it would be irrelevant to this issue.

Agreed, thanks for the reproduction btw :)

Using useSeoMeta after an await should just work in Nuxt 3.7.1, let me know if you have any issues.

Well, it doesn't work, but now it throws an error when trying to navigate to the page with an async composable call - which is totally fine with me. Thank you a lot!
[nuxt] A composable that requires access to the Nuxt instance was called outside of a plugin, Nuxt hook, Nuxt middleware, or Vue setup function. This is probably not a Nuxt bug. Find out more at `https://nuxt.com/docs/guide/concepts/auto-imports#using-vue-and-nuxt-composables`.

at C:\Users\***\node_modules\.pnpm\nuxt@3.7.1_@types+node@18.17.14\node_modules\nuxt\dist\head\runtime\plugins\unhead.js:20:35
at injectHead (C:\Users\***\node_modules\.pnpm\@unhead+vue@1.5.2_vue@3.3.4\node_modules\@unhead\vue\dist\shared\vue.b1b42453.mjs:76:30)
at Module.useHead (C:\Users\***\node_modules\.pnpm\@unhead+vue@1.5.2_vue@3.3.4\node_modules\@unhead\vue\dist\shared\vue.b1b42453.mjs:85:32)
at Module.useSeoMeta (C:\Users\***\node_modules\.pnpm\@unhead+vue@1.5.2_vue@3.3.4\node_modules\@unhead\vue\dist\index.mjs:81:32)
at Module.useMeta (C:\Users\***\composables\useMeta.ts:5:25)
at async setup (C:\Users\***\pages\a-not-ok.js:17:110)

useSeoMeta still doesn't work after await, I'm on nuxt 3.10.0

You can try asyncContext. Please make a new issue with a reproduction if you're having issues beyond that.


Updating state duration

Not causing me any issues, but per your request.... Here's a log entry I encountered.  Let me know if you need any other information.
Logger: homeassistant.helpers.entity
Source: helpers/entity.py:885
First occurred: 8:32:20 AM (1 occurrences)
Last logged: 8:32:20 AM
Updating state for sensor.weatherflow_battery_tempest (<class 'custom_components.weatherflow.sensor.WeatherFlowSensor'>) took 0.731 seconds. Please create a bug report at https://github.com/briis/hass-weatherflow/issues

Thanks. However this integration is being deprecated, due to the new WeatherFlow integration introduced in core Home Assistant. Please see the README file, on how to proceed.


Body config 'profiles'

The ability to save and reload body config profiles would be invaluable for households with multiple people who use the same VR set up instead of having to write down and re-input their body config set up.
While the server/firmware is being developed this would also be incredibly useful for members of the DIY community like thebutlah who has to use a specific set up for dancing to isolate the hips but it doesn't work for day to day activities that involve bending the spine

I believe this is a duplicate of issue #38

You are incredibly correct, I missed it on a quick scan!


Replace fmt.Sprintf with hex.EncodeToString

hex.EncodeToString has better performance than fmt.Sprintf("%x", []byte), we should use it as much as possible.
I'm not an extreme fan of performance, so I think there are some exceptions:

fmt.Sprintf("%x", func(...)[N]byte())

We can't slice the function return value directly, and it's not worth adding lines.func A()[20]byte { ... }
- a := fmt.Sprintf("%x", A())
- a := hex.EncodeToString(A()[:]) // invalid
+ tmp := A()
+ a := hex.EncodeToString(tmp[:])

fmt.Sprintf("%X", []byte)

strings.ToUpper(hex.EncodeToString(bytes)) has even worse performance.

@Gusted I can't find you in the search box of reviewers, but I wish you could review it. :)


User Pills Overflow on Android Devices During a Mention

When trying to mention another user on Android devices, The user pills tend to overflow if there are a lot of potential users to mention. Subsequently, there is no scroll option and pressing on the person to mention becomes a hassle.

Thread on Zulip to discuss this issue: https://chat.zulip.org/#narrow/stream/48-mobile/topic/Issues.20with.20long.20messages

I tried this both on an emulator (1080x1920, where this is an overflow) and on my phone (1080 x 2160, no overflow), but I could not reproduce; the scroll works fine in both cases.

I'm starting to wonder if this is an error on my end (maybe I didn't scroll the right way or something)... I'll close the issue for now and re-open if I can produce more evidence for it.

I guess we need to track this issue. I am definitely sure it can happen on some device because currently we are hard coding maxHeight, ideally it should be decided at run time according to the device.
popup: {
    marginHorizontal: 16,
    marginVertical: 8,
    borderRadius: 5,
    shadowOpacity: 0.5,
    shadowRadius: 16,
    elevation: 3,
    maxHeight: 250,
  },


ReDoc install issue on windows

I am trying to install and run ReDoc on windows but it is giving me the below error. I have already installed the latest version of npm and python:
51882 warn<EMAIL_ADDRESS>requires a peer of webpack@2 || 3 but none is installed. You must install peer dependencies yourself.
51883 warn<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none is installed. You must install peer dependencies yourself.
51884 warn optional SKIPPING OPTIONAL DEPENDENCY<EMAIL_ADDRESS>(node_modules\fsevents):
51885 warn notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for<EMAIL_ADDRESS>wanted {"os":"darwin","arch":"any"} (current: {"os":"win32","arch":"x64"})
51886 verbose notsup SKIPPING OPTIONAL DEPENDENCY: Valid OS:    darwin
51886 verbose notsup SKIPPING OPTIONAL DEPENDENCY: Valid Arch:  any
51886 verbose notsup SKIPPING OPTIONAL DEPENDENCY: Actual OS:   win32
51886 verbose notsup SKIPPING OPTIONAL DEPENDENCY: Actual Arch: x64
51887 verbose stack Error<EMAIL_ADDRESS>install: detect-libc prebuild-install || node-gyp rebuild
51887 verbose stack Exit status 1
51887 verbose stack     at EventEmitter. (C:\Program Files\nodejs\node_modules\npm\node_modules\npm-lifecycle\index.js:285:16)
51887 verbose stack     at EventEmitter.emit (events.js:180:13)
51887 verbose stack     at ChildProcess. (C:\Program Files\nodejs\node_modules\npm\node_modules\npm-lifecycle\lib\spawn.js:55:14)
51887 verbose stack     at ChildProcess.emit (events.js:180:13)
51887 verbose stack     at maybeClose (internal/child_process.js:936:16)
51887 verbose stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:220:5)
51888 verbose pkgid<EMAIL_ADDRESS>51889 verbose cwd C:\Users\Areeba.Asad\Redoc
51890 verbose Windows_NT 10.0.16299
51891 verbose argv "C:\Program Files\nodejs\node.exe" "C:\Program Files\nodejs\node_modules\npm\bin\npm-cli.js" "install"
51892 verbose node v9.10.1
51893 verbose npm  v5.6.0
51894 error code ELIFECYCLE
51895 error errno 1
51896 error<EMAIL_ADDRESS>install: detect-libc prebuild-install || node-gyp rebuild
51896 error Exit status 1
51897 error Failed at the<EMAIL_ADDRESS>install script.
51897 error This is probably not a problem with npm. There is likely additional logging output above.
51898 verbose exit [ 1, true ]

Could you please verify with the latest version! thanks!

closing as stale


Permission denied?

I just got around using your editor and after attempting to inject my .json file onto the bitwig.jar, I get a Permission Denied notice and when launching Bitwig, it's still in its default state.
Here is the terminal output:
java -jar /mnt/external/Dropbox/software/bitwig/bitwig-theme-editor/bitwig-theme-editor.jar /opt/bitwig-studio/bin/bitwig.jar apply current-bitwig-theme.json
Bitwig meets themes... Let's go!
Applying theme from: current-bitwig-theme.json
Exception in thread "main" java.io.FileNotFoundException: /opt/bitwig-studio/bin/bitwig.jar (Permission denied)
	at java.base/java.io.FileOutputStream.open0(Native Method)
	at java.base/java.io.FileOutputStream.open(FileOutputStream.java:289)
	at java.base/java.io.FileOutputStream.<init>(FileOutputStream.java:230)
	at java.base/java.io.FileOutputStream.<init>(FileOutputStream.java:118)
	at dev.berikai.BitwigTheme.asm.JarNode.export(JarNode.java:51)
	at dev.berikai.BitwigTheme.Main.applyTheme(Main.java:93)
	at dev.berikai.BitwigTheme.Main.main(Main.java:57)

The problem persists even if I have the bitwig-theme-editor.jar file in my Home directory, so I am not sure whether I'm doing something wrong.

Nevermind, I forgot it needs sudo. Closing now.


Start a drawing session without setting a category first

To spice things up a little, we should include a button next to the select component on the main page, where an user can start a drawing session without specifying a category first. This should result in presenting randomly selected images to the user.
By making use of the curated endpoint provided by Pexels this task will be rather small. This endpoint will not really provide randomized images but can act as a starting point, as the results of this endpoint will change over time.
Excerpt from the doc
 We add at least one new photo per hour to our curated list so that you always get a changing selection of trending photos.

Providing real randomization is then a future task for itself (if this feature is really necessary or wanted).
Implementation Note
import { pexelsApi } from './server';

// use this method for implementing the issue
pexelsApi.photos.curated()

This functionality is kind of implemented with #18
Maybe would think about introducing a daily run functionality, where each user draws the same images for a day.


OSError: when calling maps.map()

I'm getting OSError: [Errno 30] Read-only file system:  when calling maps.map() to get a map image.
This is being run inside a container with a read-only filesystem.
It seems like there should at least be an exception raised from the GbifMap class. I don't know if this is intended to be a pure API library, but I don't expect an HTTP API wrapper to be saving files to my filesystem without me telling it to.
Versions:
Python: 3.8.12
pygbif: 0.6.0

As a workaround I monkey patched out the call to self.__write_file() in:
https://github.com/gbif/pygbif/blob/1508ca9193118ff1e1d101aef195a3c613330231/pygbif/maps/map.py#L187-L195
like so (I also removed the plotting related calls as they're extraneous for an API, and caused other issues detailed in another issue):
import pygbif as _pygbif

def new_init(self, x):
    super(_pygbif.maps.GbifMap, self).__init__()
    self.response = x
_pygbif.maps.GbifMap.__init__ = new_init


Fixtable-grid fails to render if using row selection and data is not set at render

resetSelection: Ember.observer('visibleContent.[]', function fixtableGrid$resetSelection() {
    if (!this.get('rowSelection')) { return; }

    let selectedRows = Ember.Object.create();
    this.set('selectedRows', selectedRows);
    this.get('visibleContent').forEach((row, rowIndex) => {
      selectedRows.set(rowIndex.toString(), false);
    });

This forEach fails ungracefully when data is not set at render time.  Setting the data to an empty array fixes this, though this behavior is inconsistent with the same table without row selection.

@smargovsky, looking at this code a little more closely, I'd expect this forEach to be fine because visibleContent should compute to an empty array if content hasn't been set on the fixtable-grid yet. When you say "when data is not set at render time," what specifically does that mean? Can we reproduce this in a relatively simple environment (e.g., the dummy app)?
Obviously we can just not loop over visibleContent if it doesn't exist, but I wonder if this is actually caused by calling this function at the wrong point in the component lifecycle or something.

So, attempts to reproduce this behavior in the dummy app have fabulously failed.  Closing until further notice, thanks @menewman.


[i2c,testplan] Add testpoints for new features

This PR adds new testpoints to the testplan for newly-merged I2C features
Currently split into commits with new testpoints per-PR/commit that was merged, just to make reviewing and discussion easier. This will be squashed down before merging.
Changes from:

[x] #22345
[x] #22459
[x] #22460
[x] #22551
[x] #22864
[x] #22865
[x] #22872

Closes #22895

It's difficult to know how far to go with the testplan at this point. I've included testpoints that take the interference-approach to stimulating loss-of-arbitration behaviours, but also testpoints that describe a fuller DV environment that makes use of a multi-controller aware agent on the bus. I feel like we could cross many events with e.g. timing parameter combinations and see the test space explode, so I would be interested if you have any ideas about particularly interesting crosses that may inform the testplan. Though maybe it's worth starting that discussion as a follow-up to this.

I think we should probably limit combinations to the spec'd limits for each mode, then maybe open up a small amount of freedom for some of the parameters that are chip-specific and/or board-specific. This probably will take more thought and discussion, though, haha.

CW310 tests in CI seem to be held up, so since this is a documentation-only PR and the lints have passed, I'm going to merge it.


Fix "control loop" translation to Chinese

“control loop ” in this context should be translated as "控制回路" rather than "控制环"

@chenfengjin Please sign the CLA in order for the PR to be reviewed/merged.

I signed it

/lgtm
/approve


Hololens 1st gen camera not moving, spatial tracking not working

Describe the bug
When trying to implement an app for Hololens with Vuforia model tracking, the camera seems to be stuck, it doesn't track the world.
To reproduce
Steps to reproduce the behavior:

Go to MixedRealityToolkit
Click on TargetScale and set to World (with Room or seated it doesn't work neither)
In Camera select DefaultHololens1CameraProfile
Place an object away from the camera
Simulation in the editor works fine
Build and test the app, the objects are stuck with the camera view (if spatial awareness is enabled, the world mesh is stuck too)

Expected behavior
The objects should move relative to the camera position
Your setup

Unity Version 2020.3.14f1
MRTK Version 2.6.0
Vuforia 10.4

Target platform

HoloLens

@keveleigh can you take a look at this and advise?

Ahh hmm. I had thought all our profiles were set up for both legacy XR and XR SDK, but this one might have been missed.
As a workaround, you can manually add a Tracked Pose Driver to your camera. I'll investigate the potential misconfiguration in the profile.

We appreciate your feedback and thank you for reporting this issue.
Microsoft Mixed Reality Toolkit version 2 (MRTK2) is currently in limited support. This means that Microsoft is only fixing high priority security issues. Unfortunately, this issue does not meet the necessary priority and will be closed. If you strongly feel that this issue deserves more attention, please open a new issue and explain why it is important.
Microsoft recommends that all new HoloLens 2 Unity applications use MRTK3 instead of MRTK2.
Please note that MRTK3 was released in August 2023. It features an all new architecture for developing rich mixed reality experiences and has a minimum requirement of Unity 2021.3 LTS. For more information about MRTK3, please visithttps://www.mixedrealitytoolkit.org.
Thank you for your continued support of the Mixed Reality Toolkit!


GUVNOR-2580: Guided rule editor : Insert formulas in an OR/AND constraint

See https://issues.jboss.org/browse/GUVNOR-2580

See https://github.com/droolsjbpm/drools/pull/823 too

This needs https://github.com/droolsjbpm/drools/pull/820 to replicate to Maven...

Jenkins please retest this.

jenkins retest this.

+1

Tests are fine now. Some enforcer rules are failing though which are not related to this commit.


Externalize getDisplayName since its a common concern for most higher order components?

PR to externalize getDisplayName into a sharable utility. This is a common function found in many Higher Order Components in the wild.
This external dependency is fully tested, etc. You can see the minimal source here.
Not sure if react-redux interested in an extra dependency; issuing PR for optional consideration.

Or another alternative would be to incorporate recompose utilities here as well?

I'm cool with using Recompose's wrapDisplayName() — true story, I copied the code for getDisplayName() from this repo — though I know Dan likes to keep the dependencies to a minimum.
@gaearon?

I'm OK with using recompose if it doesn't sufficiently increase UMD build size.
Mind checking?
npm i
npm run build
gzip -c dist/react-redux.min.js | wc -c

Updated PR to use recompose.

gzip -c dist/react-redux.min.js | wc -c
11283

This way you're bundling whole recompose for one method.
The build size increased 4x, it was 2867 before the change.
@acdlite Do you support importing individual files?

import recompose/wrapDisplayName from 'recompose'

updated import:
import wrapDisplayName from 'recompose/wrapDisplayName';

Output seems reasonable now:

gzip -c dist/react-redux.min.js | wc -c
2917

Hrm, still seems a bit high for such a simple util. Probably the Babel helpers... I'll see if I can get it down a bit.

^ also lol at my comment above, obviously that import is wrong

Meh, let's keep it internal for now. If we depend on a few more helpers, might be worth revisiting.


[Feature request] Mutiple action buttons on homepage

Feature request
I am sure a few people wants muti action button support in the vuepress repo. https://github.com/vuejs/vuepress/issues/2261
I am having this feature in my own theme, and I saw my users are using it.
Description

Proposed Solution
actions:
  - link: link1
    text: text1
  - link: link2
    text: text2

I am willing to send a PR if you think it's fine.

A more flexible way:
Encourage users to customize their own home page via custom layout.
This kind of minimal features on default theme is endless...

When you visit a website, you might immediately realize that it was developed by vuepress because of the homepage.

VitePress considered removing the homepage feature totally in its default theme. I think it's kind of a good idea, but we must consider some tradeoff:
Pros
Homepage of default theme is dull and makes lots of site look similar with each other. Removing default homepage might make those websites more diverse.
Cons
The default homepage is convenient indeed, allowing lots of simple sites to have a homepage that looks good.

So maybe we could:

Still provide the default homepage.
If the default homepage is not enough, encourage users to use custom homepage, and provide a detailed guide for that.
If the default theme is not enough, encourage users to use community theme for more features.

As a VuePress maintainer / contributor, what we need to consider is different from a theme author. What do you think about that 🤔

A more flexible way:
Encourage users to customize their own home page via custom layout.
This kind of minimal features on default theme is endless...

I totally agree with above comment, but not this one.
I was taking attention to all the issues between 20 Mar and 20 Oct, and I think this is a feature metioned by most people.
I do agree that something like sponser support, darkmode and so on don't need to provide with the default theme. But it's really common to have mutiple entries for a doc site. There are a lot of users using vuepress just has a simple doc generater (And that's the original goal when uliuz start this project). So I would more regard this feature has a helpful one, which can imporve the experience for those using vuepress as a simple doc generator.

A more flexible way:
Encourage users to customize their own home page via custom layout.
This kind of minimal features on default theme is endless...

I totally agree with above comment, but not this one.
I was taking attention to all the issues between 20 Mar and 20 Oct, and I think this is a feature metioned by most people.
I do agree that something like sponser support, darkmode and so on don't need to provide with the default theme. But it's really common to have mutiple entries for a doc site. There are a lot of users using vuepress just has a simple doc generater (And that's the original goal when uliuz start this project). So I would more regard this feature has a helpful one, which can imporve the experience for those using vuepress as a simple doc generator.

VuePress was created by Evan 😅

VuePress was created by Evan 😅

What about a type field for different button style?
actions:
  - link: link1
    text: text1
    type: primary
  - link: link2
    text: text2
    type: secondary

What about a type field for different button style?
actions:
  - link: link1
    text: text1
    type: primary
  - link: link2
    text: text2
    type: secondary


Add class from typelib for MFC class is removed?

see https://docs.microsoft.com/en-us/cpp/mfc/reference/add-class-from-typelib-wizard?view=msvc-160

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

ID: 57a63ad9-deda-1d5b-3baf-c99c01f1f1c6
Version Independent ID: c8b71ab6-df66-dee0-25b1-34ce0bb0cab4
Content: Automation Clients: Using Type Libraries
Content Source: docs/mfc/automation-clients-using-type-libraries.md
Product: visual-cpp
Technology: cpp-mfc
GitHub Login: @TylerMSFT
Microsoft Alias: twhitney

Thx. Somehow the other link where the removal from VS2019 was announced has disappeared from my post. I have an older wizard generated Excel wrapper file which I have to safeguard then for the rest of my life.


word

Can you display word from the url https://www.office.com/launch/word?ui=en-US&rs=US&auth=1

Can you display word from the url https://www.office.com/launch/word?ui=en-US&rs=US&auth=1

unfortunately that can't be done because it can't be iframed.

Yes microsoft does not allow it's websites to be iframed

The first line of the docs: https://projects.asylum-os.com/win11react-docs/docs/store/Add an App


melit missing definition

I think I hear people say, "melit a kim" a lot and it means, "go looking for clams". This is not in the English definition of melit which is just about opening things. The Palauan definition contains 'melit a kim'. Can people confirm and we can add, "Look for clams" to the English definition?

Confirm.
Melit: titir: telit.
On Wed, Sep 13, 2023 at 01:36 John Bent @.***> wrote:

I think I hear people say, "melit a kim" a lot and it means, "go looking
for clams". This is not in the English definition of melit which is just
about opening things. The Palauan definition contains 'melit a kim'. Can
people confirm and we can add, "Look for clams" to the English definition?
—
Reply to this email directly, view it on GitHub
https://github.com/tekinged/missing/issues/451, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AF2DJJAFMPPBHUHKSBCRZQ3X2FV7JANCNFSM6AAAAAA4WBIEWA
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

The definition is good. But when we say "melit a kim" and "melit oreuer" it
means more than just looking for clams but more about shucking them.
Also, another use of the word is more specific for poking a hole or poked
hole in something versus meling or belsibs.
On Wed, Sep 13, 2023, 4:32 AM Gnalu @.***> wrote:

Confirm.
Melit: titir: telit.
On Wed, Sep 13, 2023 at 01:36 John Bent @.***> wrote:

I think I hear people say, "melit a kim" a lot and it means, "go looking
for clams". This is not in the English definition of melit which is just
about opening things. The Palauan definition contains 'melit a kim'. Can
people confirm and we can add, "Look for clams" to the English
definition?
—
Reply to this email directly, view it on GitHub
https://github.com/tekinged/missing/issues/451, or unsubscribe
<
https://github.com/notifications/unsubscribe-auth/AF2DJJAFMPPBHUHKSBCRZQ3X2FV7JANCNFSM6AAAAAA4WBIEWA>

.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

—
Reply to this email directly, view it on GitHub
https://github.com/tekinged/missing/issues/451#issuecomment-1717370889,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AXYSPXV6SG4RHJUIMAIK5YDX2GDS5ANCNFSM6AAAAAA4WBIEWA
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

If you see someone walking out to the ocean and you ask them, "Ke mor?",
can they reply, "Ak mo melit a kim"? And, if so, does that mean, "I'm going
to go shuck clams" or does it mean, "I'm going to look for clams?"
Thanks!
John
On Wed, Sep 13, 2023 at 11:51 PM Lukes-Imeyuns @.***>
wrote:

The definition is good. But when we say "melit a kim" and "melit oreuer"
it
means more than just looking for clams but more about shucking them.
Also, another use of the word is more specific for poking a hole or poked
hole in something versus meling or belsibs.
On Wed, Sep 13, 2023, 4:32 AM Gnalu @.***> wrote:

Confirm.
Melit: titir: telit.
On Wed, Sep 13, 2023 at 01:36 John Bent @.***> wrote:

I think I hear people say, "melit a kim" a lot and it means, "go
looking
for clams". This is not in the English definition of melit which is
just
about opening things. The Palauan definition contains 'melit a kim'.
Can
people confirm and we can add, "Look for clams" to the English
definition?
—
Reply to this email directly, view it on GitHub
https://github.com/tekinged/missing/issues/451, or unsubscribe
<

https://github.com/notifications/unsubscribe-auth/AF2DJJAFMPPBHUHKSBCRZQ3X2FV7JANCNFSM6AAAAAA4WBIEWA>

.
You are receiving this because you are subscribed to this
thread.Message
ID: @.***>

—
Reply to this email directly, view it on GitHub
https://github.com/tekinged/missing/issues/451#issuecomment-1717370889,

or unsubscribe
<
https://github.com/notifications/unsubscribe-auth/AXYSPXV6SG4RHJUIMAIK5YDX2GDS5ANCNFSM6AAAAAA4WBIEWA>

.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

—
Reply to this email directly, view it on GitHub
https://github.com/tekinged/missing/issues/451#issuecomment-1717787918,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAPT2PWOTN6OKNLZ6YGLT63X2HB6ZANCNFSM6AAAAAA4WBIEWA
.
You are receiving this because you authored the thread.Message ID:
@.***>

Yes as you don’t say I’m going to look for clams. ‘Ak Mo Melit a Kim/oruer’
regardless you will find any or not.
On Wed, Sep 13, 2023 at 15:47 John Bent @.***> wrote:

If you see someone walking out to the ocean and you ask them, "Ke mor?",
can they reply, "Ak mo melit a kim"? And, if so, does that mean, "I'm
going
to go shuck clams" or does it mean, "I'm going to look for clams?"
Thanks!
John
On Wed, Sep 13, 2023 at 11:51 PM Lukes-Imeyuns @.***>
wrote:

The definition is good. But when we say "melit a kim" and "melit oreuer"
it
means more than just looking for clams but more about shucking them.
Also, another use of the word is more specific for poking a hole or
poked
hole in something versus meling or belsibs.
On Wed, Sep 13, 2023, 4:32 AM Gnalu @.***> wrote:

Confirm.
Melit: titir: telit.
On Wed, Sep 13, 2023 at 01:36 John Bent @.***> wrote:

I think I hear people say, "melit a kim" a lot and it means, "go
looking
for clams". This is not in the English definition of melit which is
just
about opening things. The Palauan definition contains 'melit a kim'.
Can
people confirm and we can add, "Look for clams" to the English
definition?
—
Reply to this email directly, view it on GitHub
https://github.com/tekinged/missing/issues/451, or unsubscribe
<

https://github.com/notifications/unsubscribe-auth/AF2DJJAFMPPBHUHKSBCRZQ3X2FV7JANCNFSM6AAAAAA4WBIEWA>

.
You are receiving this because you are subscribed to this
thread.Message
ID: @.***>

—
Reply to this email directly, view it on GitHub
<
https://github.com/tekinged/missing/issues/451#issuecomment-1717370889>,

or unsubscribe
<

https://github.com/notifications/unsubscribe-auth/AXYSPXV6SG4RHJUIMAIK5YDX2GDS5ANCNFSM6AAAAAA4WBIEWA>

.
You are receiving this because you are subscribed to this
thread.Message
ID: @.***>

—
Reply to this email directly, view it on GitHub
https://github.com/tekinged/missing/issues/451#issuecomment-1717787918,

or unsubscribe
<
https://github.com/notifications/unsubscribe-auth/AAPT2PWOTN6OKNLZ6YGLT63X2HB6ZANCNFSM6AAAAAA4WBIEWA>

.
You are receiving this because you authored the thread.Message ID:
@.***>

—
Reply to this email directly, view it on GitHub
https://github.com/tekinged/missing/issues/451#issuecomment-1718410195,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AF2DJJDLYK3IKXZP6DZNVN3X2IZYXANCNFSM6AAAAAA4WBIEWA
.
You are receiving this because you commented.Message ID:
@.***>

Yes, as Mar said.
Saying ak mo melit a kim means finding  and shucking them. The shucking
part is the key.
Now, if they need to collect young clams for a farm then they might say a
ki mo melai a kim el mo er a sers. And we know there's no shucking
involved.
J
On Wed, Sep 13, 2023, 5:07 PM Gnalu @.***> wrote:

Yes as you don’t say I’m going to look for clams. ‘Ak Mo Melit a
Kim/oruer’
regardless you will find any or not.
On Wed, Sep 13, 2023 at 15:47 John Bent @.***> wrote:

If you see someone walking out to the ocean and you ask them, "Ke mor?",
can they reply, "Ak mo melit a kim"? And, if so, does that mean, "I'm
going
to go shuck clams" or does it mean, "I'm going to look for clams?"
Thanks!
John
On Wed, Sep 13, 2023 at 11:51 PM Lukes-Imeyuns @.***>
wrote:

The definition is good. But when we say "melit a kim" and "melit
oreuer"
it
means more than just looking for clams but more about shucking them.
Also, another use of the word is more specific for poking a hole or
poked
hole in something versus meling or belsibs.
On Wed, Sep 13, 2023, 4:32 AM Gnalu @.***> wrote:

Confirm.
Melit: titir: telit.
On Wed, Sep 13, 2023 at 01:36 John Bent @.***> wrote:

I think I hear people say, "melit a kim" a lot and it means, "go
looking
for clams". This is not in the English definition of melit which
is
just
about opening things. The Palauan definition contains 'melit a
kim'.
Can
people confirm and we can add, "Look for clams" to the English
definition?
—
Reply to this email directly, view it on GitHub
https://github.com/tekinged/missing/issues/451, or unsubscribe
<

https://github.com/notifications/unsubscribe-auth/AF2DJJAFMPPBHUHKSBCRZQ3X2FV7JANCNFSM6AAAAAA4WBIEWA>

.
You are receiving this because you are subscribed to this
thread.Message
ID: @.***>

—
Reply to this email directly, view it on GitHub
<
https://github.com/tekinged/missing/issues/451#issuecomment-1717370889>,

or unsubscribe
<

https://github.com/notifications/unsubscribe-auth/AXYSPXV6SG4RHJUIMAIK5YDX2GDS5ANCNFSM6AAAAAA4WBIEWA>

.
You are receiving this because you are subscribed to this
thread.Message
ID: @.***>

—
Reply to this email directly, view it on GitHub
<
https://github.com/tekinged/missing/issues/451#issuecomment-1717787918>,

or unsubscribe
<

https://github.com/notifications/unsubscribe-auth/AAPT2PWOTN6OKNLZ6YGLT63X2HB6ZANCNFSM6AAAAAA4WBIEWA>

.
You are receiving this because you authored the thread.Message ID:
@.***>

—
Reply to this email directly, view it on GitHub
https://github.com/tekinged/missing/issues/451#issuecomment-1718410195,

or unsubscribe
<
https://github.com/notifications/unsubscribe-auth/AF2DJJDLYK3IKXZP6DZNVN3X2IZYXANCNFSM6AAAAAA4WBIEWA>

.
You are receiving this because you commented.Message ID:
@.***>

—
Reply to this email directly, view it on GitHub
https://github.com/tekinged/missing/issues/451#issuecomment-1718424323,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AXYSPXXS3VLMQUBCQED52PLX2I4CZANCNFSM6AAAAAA4WBIEWA
.
You are receiving this because you commented.Message ID:
@.***>


NaN/infinities in atmos

Description
On round 38116 on Salamander, a pressure value apparently became NaN/infinity and killed everyone.
Apparently someone reached insane pressures and temperatures in Science, which probably lead to this bug. Spectate Nevaeh Pfiefer.
Suits did not protect against the pressure.
 I tried to fix it with https://github.com/space-wizards/space-station-14/pull/22876, however the problem kept happening. There is a problem that is related but likely not the cause of this problem, and a fix was in https://github.com/space-wizards/space-station-14/pull/22907.
The linked issue https://github.com/space-wizards/space-station-14/issues/22885 was likely fixed by https://github.com/space-wizards/space-station-14/pull/22464 because the issue went away for a while (see linked reproduction steps). It's still possible that they are related.
What is likely going on is:

Something causes a GasMixture temperature to be set to a big number, possibly a divide by near-zero.
That big number or possibly NaN gets propagated to neighbors by LINDA or through pipes.
Any GasMixture that interacts with this "corrupted" mix also becomes very big or NaN.

If you find a way to reproduce this issue on a local server, please reply with the steps you did to get this bug to crop up on your local server.
A branch to revert the likely culprit is located here. I've asked other maintainers to try this revert if we don't make progress on this in the next day or two.
Thanks for your help and your patience while this gets sorted out.

Reading through and a ton of our atmos code uses single precision floating point (and associated MathF funcs rather than double precision Math funcs). Are we just degrading through floating point precision error in a bunch of places? We should try using doubles for sensitive math such as atmospheric simulation.

i guess reality stopped collapsing a few months back so im closing this issue


mount() return express.Router instance

This is very useful to have available.
export function mount (app, store, path) {
  if (!(store instanceof Container)) {
    throw new Error('You must provide an instance of JSData.Container or JSData.DataStore!')
  }
  path || (path = '/')
  const router = new Router(store).router
  app.use(path, queryParser)
  app.use(path, router)
  return router
}

Not necessary - the routes are nested within the app (express instance) passed in.


Add handling for wsarecv

Hmm, looks like the jape script assumes bash, so it's failing on windows?


reportUnknownArgumentType when argument type is defined in Callable via Protocol

Environment data
Pylance 2020.12.2
Python 3.8.5
Expected behaviour
No warnings
Actual behaviour
False-positive warning:

Code Snippet / Additional information
from dataclasses import dataclass
from typing import NamedTuple, Dict, Tuple, Union, Any, Protocol

VertData = NamedTuple("VertData", [('val', int)])
Prop = NamedTuple("Prop", [('size', int)])

class Reader(Protocol):
    def __call__(self, x: memoryview, y: Dict[str, Any]) -> Union[int, Tuple[float,...], VertData, None]:
        ...

@dataclass
class ParsedData:
    prop: Prop
    value: Union[int, Tuple[float,...], VertData, None]
    reader: Reader

data = memoryview(b'sadfsdfsdfsdf')
propMap = Prop(1)
propValues=dict(str1=ParsedData(prop=propMap, value=None, reader=lambda x,y: print(x)))

for (k,v) in propValues.items():
    vprp = v.prop
    f = v.reader
    v.value = f(data[1:0], propValues)

https://mypy-play.net/?mypy=latest&python=3.7&flags=strict&gist=202f4a912fb9b7125722676630894b6d

This will be addressed in the next release.

This issue has been fixed in version 2021.1.0, which we've just released. You can find the changelog here: https://github.com/microsoft/pylance-release/blob/main/CHANGELOG.md#202110-6-january-2021

This issue has been fixed in version 2021.1.0, which we've just released. You can find the changelog here: https://github.com/microsoft/pylance-release/blob/main/CHANGELOG.md#202110-6-january-2021


Changelog includes commits not on the release branch

For my project I'm using charmixer/auto-changelog-action as a wrapper to run github-changelog-generator. My configuration for that action produces the following command line when it runs:
github_changelog_generator --user comixed --project comixed --release-branch refs/tags/v0.6.0-0.rc8 --output CHANGELOG.md --token *** --since-tag v0.5.2-2 --due-tag v0.6.0-0.rc8

The generated ChangeLog file includes commits that are not on the release branch named. I've also changed the release branch to reference specifically to our release branch, which produced the following command line:
github_changelog_generator --user comixed --project comixed --release-branch release/0.6 --output CHANGELOG.md --token *** --since-tag v0.5.2-2 --due-tag v0.6.0-0.rc8

The problem is that, in both cases, the generated CHANGELOG.md file keeps include an issue that is not on the release branch.
I finally tried telling it to no include any unreleased changes (which includes the above mentioned issue) and it produced a changelog with nothing in it.
Is this a bug or a use error?

Revisiting this: we just pushed an update of our project and, again, the changelog created includes commits from the develop branch that are not in the release. I'm afraid of this confusing the users into thinking those features are present when they're not.
Can someone point out if this is a usage issue and, if so, how do I fix it?


[SPIKE] Check compatibility matrix for PostgreSQL related components

Is your feature request related to a problem? Please describe.
We need to update PostgreSQL related env and before this we need to make research on what is compatible with what.
Components to check (for all supported OS distributions + ARM architecture for CentOS):

pgAudit
PgBouncer
Pgpool (only k8s deployment)
repmgr

Describe the solution you'd like
Compatibility matrix that would allow us to decide to which PostgreSQL version we can upgrade (12 or 13).
Describe alternatives you've considered
n/a
Additional context
n/a

DoD checklist

[ ] Changelog updated
[ ] COMPONENTS.md updated / doesn't need to be updated
[ ] Feature has automated tests
[ ] Automated tests passed (QA pipelines)

[ ] apply
[ ] upgrade

[ ] Idempotency tested
[ ] Documentation added / updated / doesn't need to be updated
[ ] All conversations in PR resolved
[ ] Solution meets requirements and is done according to design doc
[ ] Usage compliant with license
[ ] Backport tasks created / doesn't need to be backported

Because it is a blocker for the rest of the tasks in the current sprint I decided to speed it up a little and put all findings in a comment.
Postgresql publish Feature Matrix to see what features are included in particular supported PostgreSQL version, see here

Postgresql latest release
13.3
12.7
11.12

Release date
Thursday, May 13, 2021
Thursday, May 13, 2021
Thursday, May 13, 2021

EOL
Thursday, November 13, 2025
Thursday, November 14, 2024
Thursday, November 9, 2023

pgAudit (latest)
v1.5.x (v1.5.0)
v1.4.x
v1.3.x

PgBouncer (latest)
v1.15.x
-
-

PgPool (latest)
v4.2 (v4.2.2)
-
v4.1 (v4.1.6)

repmgr
v5.2
v5.2
v5.2

(Yesterday was released Postgresql versions 13.3, 12.7, 11.12, 10.17, and 9.6.22  - fix bunch of issues and CVE's, see here)
PgPool / PgBouncer don't explicit specify compatibility with particular PostgreSQL versions, they only advise that you should use the latest stable version.
PgPool: "Supported PostgreSQL server's versions are 6.4 and higher. To use the parallel query feature, however, 7.4 and higher must be used."
However, I found some example configs in official PgPool documentation with PostgreSQL version specified (see links in above table)
As described in ARM documentation pgpool and pgbouncer are not supported by Epiphany. I figured out that PgPool actually was released for ARM but its not up to date version.
RHEL7/CentOS7:

RPM name
Release date

postgresql-pgpool-II-3.4.6-1.el7.aarch64.rpm
2016-10-15

postgresql-pgpool-II-devel-3.4.6-1.el7.aarch64.rpm
2016-10-15

postgresql-pgpool-II-extensions-3.4.6-1.el7.aarch64.rpm
2016-10-15

RHEL8/CentOS8:

RPM name
Release date

pgpool-II-10-4.1.3-1.rhel8.aarch64.rpm
8/20/2020

pgpool-II-10-4.1.4-1.rhel8.aarch64.rpm
9/17/2020

Additional links may be useful:
PgPool Bitnami image
PgBouncer Bitnami image
PostgreSQL RHEL & Ubuntu
PgAudit & PgBouncer also available via above official repository

PgBouncer latest version was released for ARM arch: rpm (thx @atsikham)


AppTP design review

Task/Issue URL: https://app.asana.com/0/0/1204637215378469/f
Tech Design URL:
CC:
Description:
This PR implements the design review notes from the linked task

Steps to test this PR:

See the linked design in Asana for review notes

Copy Testing:

[x] Use of correct apostrophes in new copy, ie ’ rather than '

Orientation Testing:

[x] Portrait
[x] Landscape

Device Testing:

[ ] iPhone SE (1st Gen)
[ ] iPhone 8
[ ] iPhone X
[x] iPhone 14 Pro
[ ] iPad

OS Testing:

[ ] iOS 14
[ ] iOS 15
[x] iOS 16

Theme Testing:

[x] Light theme
[x] Dark theme

Internal references:
Software Engineering Expectations
Technical Design Template

To see the specific tasks where the Asana app for GitHub is being used, see below:

https://app.asana.com/0/0/1204668981740167

@SlayterDev I just updated this branch with the latest develop changes in order to make a build


Review IA card sort findings with IA team

Sarah Norman to arrange a meeting for Matt Piper to feedback

Initial meeting 16 August.
@EllenDoyle, I wasn't clear who is going to arrange the follow-up meeting when we've had a chance to digest the findings.
Links to research results in #ia-service-manual chat in Slack.

I can put a meeting in diaries later this week if Sarah doesn't. I talk to Sarah all the time so will liaise with her.


dbt-utils v0.9.0 breaks semantic versioning

Describe the bug
Dbt-utils v0.9.0 is not backward compatible with dbt versions prior to 1.2.0. This is a breaking change, and thus the major version should be bumped.
Steps to reproduce

Expected results

Actual results

Screenshots and log output

System information
The contents of your packages.yml file:
Which database are you using dbt with?

[ ] postgres
[ ] redshift
[ ] bigquery
[ ] snowflake
[ ] other (specify: ____________)

The output of dbt --version:
<output goes here>

Additional context

Are you interested in contributing the fix?

Hi @mikeskov, the semver spec says the following about version zero software:

Major version zero (0.y.z) is for initial development. Anything MAY change at any time. The public API SHOULD NOT be considered stable.

We intend to ship dbt utils 1.0.0 later this year, at which point we will lock in the interfaces as required.
I assume that the release broke your run this morning; I'm sorry about that! For version zero packages, we tend to recommend splitting the difference by pinning to a single minor version at a time (i.e. receive all patches but opt into minor versions on a case by case basis).


Add tests

I know I slapped this thing together on a stream really quickly, but now that other folks are using it, I think it's time to treat it like a Real Tighten Package ™ and write some tests and stuff :)

Since we just converted this to Inertia, they'll need to be Inertia tests.
Here's a sample from the docs:
use Inertia\Testing\Assert;

class PodcastsControllerTest extends TestCase
{
    public function test_can_view_podcast()
    {
        $this->get('/podcasts/41')
            ->assertInertia(fn (Assert $page) => $page
                ->component('Podcasts/Show')
                ->has('podcast', fn (Assert $page) => $page
                    ->where('id', $podcast->id)
                    ->where('subject', 'The Laravel Podcast')
                    ->where('description', 'The Laravel Podcast brings you Laravel and PHP development news and discussion.')
                    ->has('seasons', 4)
                    ->has('seasons.4.episodes', 21)
                    ->has('host', fn (Assert $page) => $page
                        ->where('id', 1)
                        ->where('name', 'Matt Stauffer')
                    )
                    ->has('subscribers', 7, fn (Assert $page) => $page
                        ->where('id', 2)
                        ->where('name', 'Claudio Dekker')
                        ->where('platform', 'Apple Podcasts')
                        ->etc()
                        ->missing('email')
                        ->missing('password')
                    )
                )
            );
    }
}

They don't have full docs yet but the testing helpers are imported from a package with docs, so we can use the docs from the package for now:
https://github.com/claudiodekker/inertia-laravel-testing/tree/a5ac8d372e456534f5ad2e07a6875e0f27c6a73d


swipe gesture is hard to trigger

Version
Tell us which versions you are using:

react-native-router-flux v3.30.3
react-native v0.29.0

Expected behaviour
swipe gesture is easy to trigger like built-in iOS apps
Actual behaviour
Feels not responsive, must be very slow and steady to trigger it.
Or, is there any params can be tweaked?

Under the API there's a function to override the gesture handlers: getPanHandlers
https://github.com/aksonov/react-native-router-flux/blob/master/docs/API_CONFIGURATION.md#gestures
Example: https://github.com/aksonov/react-native-router-flux/issues/1237. In the bottom there's a link to a working example.


[Bug]: Delivery service template

Is there an existing issue for this?

[X] I have searched the existing issues

Description
Hi,
I'm new in Appsmith, I want to fork an app the delivery service management but when I fork it, a database information is asked but when I use my internal database, I don't have any information. Is there a documentation on how to deploy this template.

Steps To Reproduce

go to template
use delivery service management
click Use template
fork template to workspace
use internal db
when deployed I have schema not available from datab

ase

Public Sample App
No response
Environment
Production
Issue video log
No response
Version
Self-hosted

@rvmadeit This issue has been fixed, thanks for raising the issue. To test this on your instance, create a new workspace and try forking the template again, it will come with complete credentials for our Postgres mock database


Extending in ES6?

I'm using 0.8.1
Trying to figure out how to write a Bookshelf model in ES6.
if I do it like this:
export default class Account extends Bookshelf.Model {
    constructor() {
        super({
            tableName: "account",
            idAttribute: "id"
        });
    }
}

the tableName does get set and I get lots of undefined errors.
If I try like
export default class Account extends Bookshelf.Model {
    constructor() {
        super();
        this.tableName = 'account';
        this.idAttribute = 'id';
    }
}

It actually gets the table name, but it doesn't seem to be registering the id or any other column names, any query is just "select account.* from account".
Any suggestions?

Bookshelf expects tableName to be on the prototype and it's possible idAttribute is the same. There is no way to add prototype properties with the class syntax, including under the current ES7 class properties. Bookshelf models don't really play nicely with class. You have to manually add everything to the prototype after the class is defined.

So, best just not to use classes? That's disappointing.
-Clay
On Wed, May 27, 2015 at 8:36 AM, Ben Drucker<EMAIL_ADDRESS>wrote:

Bookshelf expects tableName to be on the prototype and it's possible idAttribute is the same. There is no way to add prototype properties with the class syntax, including under the current ES7 class properties. Bookshelf models don't really play nicely with class. You have to manually add everything to the prototype after the class is defined.
Reply to this email directly or view it on GitHub:
https://github.com/tgriesser/bookshelf/issues/756#issuecomment-105891138

I use ES6 with something like:
export class ProductionSheet extends bookshelf.Model
{
    get tableName() { return 'ProductionSheet'; }

    get defaults() {
        return {
            property1: 'blah',
            property1: null
        }
    }

    // START Relations
    timesheet() { return this.belongsTo('Timesheet', 'timesheet'); }
    taskType() { return this.belongsTo('TaskType', 'taskType'); }
    worksheets() { return this.hasMany('AuditWorksheet', 'productionSheet'); }
    // END Relations
}

Bump. It would be nice if there was something in the docs on using es6 class syntax.

There are still problems with ES6, especially collections. There are some static functions used that don't get 'inherited'. Models work, though, for the most part.

Strange, which static functions don't get inherited? Just glanced at the code and couldn't see anything funky. The extend() method just seems to create a new constructor and copy passed properties to its prototype or directly on the constructor (static functions). Isn't what class Child extends Parent does?

Yeah, just converted some models using the method you used above and getting weird errors.
  sql: 'insert into "outputs" ("0", "position", "tx_hash") values ($1, $2, $3)',
  returning: undefined }
{ __cid: '__cid16',
  method: 'insert',
  options: undefined,
  bindings:
   [ { amount: 498369000,
       script: [Object],
       script_type: 'pubkeyhash',
       address: 'msLoJikUfxbc2U5UhRSjc2svusBSqMdqxZ' },
     2,
     '431d6c31dcb8414432d61f9ff5eb67fd6cb2c5f91d9748718c411b86a58e3874' ],
  sql: 'insert into "outputs" ("0", "position", "tx_hash") values ($1, $2, $3)',
  returning: undefined }

when trying to input.save()

Oops, the problem was that I did:
    constructor(...args) {
      super(args);
   }

instead of
    constructor(...args) {
      super(...args);
    }

Ok all the tests pass. Will give an update if I encounter problems.

No, the (ES6) extends only does the instance properties (the prototype). None of the statics. Coffeescripts's extends does copy both the properties on the prototype and the constructor just like then supplied .extend().
I don't remember what was broken on the collections but for models, the option { require: true } fails due to the errors being static properties on the model: https://github.com/tgriesser/bookshelf/blob/master/src/model.js#L1219

...fails due to the errors it uses being static properties on the model...

@luggage66 Actually ES6 extends does do static inheritance - the inheriting class will take the static properties of the parent.
class Test {
  static test() { return "hello";}
}

class Child extends Test {}

console.log(Child.test());
// "hello"

The problem is that Bookshelf's extend method has an additional functionality that decorates the class with specific instantiations of these errors. Because ES6 offers no static constructor, I don't know that we can recreate this exact API using the new class syntax. However this is certainly something I'm keeping in mind moving forward.
The rationale behind having this sublcassed errors is for catching by type in Bluebird. eg.
User.forge({id: 1}).fetch({require: true}).then(function (user) {
  return user.account().fetch({require: true});
}).catch(User.NotFoundError, function (error) {
  console.log("User not found!");
}).catch(Account.NotFoundError, function (error) {
  console.log("Account not found!");
}).catch(function (error) { console.log("Unknown error occurred: " + error); });

I have two possible solutions for this. I prefer the second.
1. Lazily create error classes
Instead of having Model.NotFoundError, use Model.error('NotFound') to return the error instance. Since there is no static constructor, we'll have to define the error the first time this is called. So something like this:
class Model {
  // ...
  static error(errorName) {
    errorClass = `${errorName}Error`;
    if (this[errorClass] == null) {
      this[errorClass] = class extends super.error(errorName);
    }
  }
}

So that allows the above use of catch by type, like this:
User.forge({id: 1}).fetch({require: true})
.then((user) => user.account().fetch({require: true}))
.catch(User.error('NotFound'), (error) =>
  console.log("User not found!")
);

2. Give model type to errors
Provide a model type like so:
class NotFoundError extends Error {
  constructor: (message, Model) {
    this.Model = Model;
    super(message);
  }

  static forModel(Model) {
    return (error) => error instanceof this && error.model = Model;
  }
}

That class just lives at bookshelf.NotFoundError and is always fired with the model constructor as an argument. Then catch like so, taking advantage of Bluebird's catch allowing a callback.
import {NotFoundError} from 'bookshelf';

User.forge({id: 1}).fetch({require: true})
.then((user) => user.account().fetch({require: true}))
.catch(NotFoundError.forModel(User), (error) =>
  console.log("User not found!");
);

This is not a high priority change yet. There are other features that will be affected by moving to ES6 classes. However, I'd like to get everything right, so feedback is encouraged. :+1:

Here is some hackery I am testing out that just copies bookshelf 0.8.2 static properties to the inherited class: https://gist.github.com/luggage66/8920135a556fc33b06ac (it's an es6 decorator, but you can just call it as a function)

@luggage66 extends already does static inheritance. If you want to get this happening, please consider providing a PR implementing my second proposal from the post above.
AFAIK Decorators are ES7 and the standard has not yet been finalized, and this can be achieved without them anyway.
Just a note on back compatibility here. Errors can be removed from the Model classes entirely, alleviating this problem. However, they were placed on the classes so that they could be used in combination with Bluebird's Promise#catch, which also accepts a predicate as an argument. so we can do something like this:
// import new errors module
import { NotFoundError } from './errors';

// model definition
class Model {
  static NotFoundError(error) {
    // Use the predicate on our error class.
    return NotFoundError.forModel(this);
  }

  fetch() {
    // ...
    throw new NotFoundError(this);
    // ...
  }
}

Are you up for helping out with this change?

It at least copies collection, forge, fetchAll, etc.

ES6 extend does this already...

Yea, I had some coffeescript classes in the mix (don't ask) that cause things to break from 0.8.1 -> 0.8.2 and I misinterpreted the evidence.
I finished converting them all to es6 and now I can use 0.8.2 (except for the known Error problem, of course).
Yea, I'll take a look at the fixing the Error types. I think, with static getters, I can generate (and cache) error types on demand so that we can:
.catch(User.NotFoundError, (error) => ....)

without the special extended() function that creates those types now when model.extent({ instance, static}) is called. That would prevent browser use in IE < 9, if that matters to you.

Meanwhile how to solve the NotFoundError and friends problem while inheriting from Bookshelf.Model?

I've switched all my code from var Account = bookshelf.Model.extend({ ... }) to TypeScript classes (class Account extends bookshelf.Model<Account> { ... }) and all my unit tests pass as before. They heavily test NotFoundError, NoRowsUpdatedError and NoRowsDeletedError, example:
const id = req.body.id;
new Account({id})
  .fetch({require: true})
  .then(account =>
    res.status(HttpStatus.OK_200).send(account.toJSON())
  )
  .catch(Account.NotFoundError, () =>
    next(createError(HttpStatus.NotFound_404, `'${id}' not found`))
  )
  .catch(error => next(error));

it('should not get an unknown account', done => {
  const id = -1;

  request(app).get(`/Accounts/${id}`)
    .expect(HttpStatus.NotFound_404)
    .then(res => {
      expect(res.body).toEqualErrorObject({
        status: HttpStatus.NotFound_404,
        stack: `NotFoundError: '${id}' not found`,
        message: `'${id}' not found`,
        name: 'NotFoundError'
      });
      done();
    });
});

I was surprised and did more investigations and my conclusion is that everything works as expected.
@rhys-vdw

Are you sure that "Bookshelf's extend method [...] decorates the class with specific instantiations of these errors" does not work with ES6 classes? Is there a unit test somewhere to confirm?
If it does not work as you say, why does it with TypeScript (ES5 output) and not with Babel?

(My previous obsolete and deleted post was: "Meanwhile how to solve the NotFoundError and friends problem while inheriting from Bookshelf.Model?")

I've never used TypeScript, but if you use ES extend, it would copy the static error classes from Model  onto your new subclass. Bookshelf's Model.extend has an additional functionality that does extra work by the magical extended function. Errors get subclasses via Model.extended.
So presumably, using ES inheritance you get this:
class Account extends bookshelf.Model {  /* ... */ }

class User extends bookshelf.Model {  /* ... */ }

assert.equal(Account.NotFoundError, User.NotFoundError);

// The purpose of subclassing being for Bluebird's `catch` by type.
Promise.all(
  Account.where({ id: 1 }).fetch({ require: true }),
  User.where({ id: 1 }).fetch({ require: true })
).catch(Account.NotFoundError, error => /* could be either account or user */ );

The solution is to stop subclassing errors and provide some other method for catching them. We could add a static for() method and an instance of the issuing class to each error.
class NotFoundError extends Error {
  constructor(Model) {
    this.name = 'NotFoundError';
    this.Model = Model;
  }
  static is(error) {
    return error.name === this.name;
  }

  static for(Model) {
    return (error) => this.is(error) && this.Model === Model;
  }
}

// ...
const { NotFoundError } = bookshelf.Model;

Promise.all(
  Account.where({ id: 1 }).fetch({ require: true }),
  User.where({ id: 1 }).fetch({ require: true })
).catch(NotFoundError.for(Account), error => console.error('account not found!'))
.catch(NotFoundError.for(User), error => console.error('user not found!'));

.catch(Account.NotFoundError, error => /* could be either account or user */ );

Ok I see; my mistake.
Temporary solution:
import * as createError from 'create-error';

class Account extends bookshelf.Model<Account> {
  get tableName() { return 'Accounts'; }

  // Redefine errors
  static NotFoundError = createError('NotFoundError');
  static NoRowsUpdatedError = createError('NoRowsUpdatedError');
  static NoRowsDeletedError = createError('NoRowsDeletedError');
}

Sorry if it's off topic, but is there official doc for using ES6 class syntax with Model.extend now that several months have passed ?

@bogas04 We still need an error implementation and then we can add ES6 examples to the docs. I've added the "PR please" label as I am not actively working on Bookshelf presently. I will review any submissions though.

I started to work on a Knex-based ORM which aims to provide easy model integration with ES6+:
https://github.com/kripod/knexpress
My goal is to achieve feature parity with Bookshelf.js with as few lines of code as possible.

@kripod Great work! I'd love to see some of these improvements merged into bookshelf.

@henryboldi Well, Knexpress mounts every Knex method dynamically, while Bookshelf has a predefined set of functions to operate from. Bookshelf was not built to utilize ES6 classes natively, that's why I decided to create a project of my own.
Besides the points above, I would also be very glad to see my class-related ideas being implemented to Bookshelf. (At the moment, I'm working on implementing support for relations in Knexpress.)

Does es6 extends copy static getters as-is?
If so, couldn't the SomeModel.NotFoundError be handled by making NotFoundError a memoized getter that creates the subclass of NotFoundError from this.

I found a workaround per https://github.com/jtwebman/bookshelf-scopes/issues/1#issuecomment-286905196
Calling extended on your model class will cause it to be assigned the desired Error classes and other plugin behavior.

The project leadership of Bookshelf recently changed. In an effort to advance the project we close all issues older than one year.
If you think this issue needs to be re-evaluated please post a comment on why this is still important and we will re-open it.
We also started an open discussion about the future of Bookshelf.js here https://github.com/bookshelf/bookshelf/issues/1600. Feel free to drop by and give us your opinion.
Let's make Bookshelf great again

If you think this issue needs to be re-evaluated please post a comment on why this is still important and we will re-open it.

The importance of this issue should be self-evident. Bookshelf classes still require custom functions to create classes and don't work with ES6 classes and all their new features. Things like the classProperties on extends are obsolete ways of doing things and the extends don't allow you to create getters/setters.

Re-opened. Please use thumbs up emoji on the original question so have an easier time prioritising and planning the next steps.

I agree that all code should be refactored in order to drop the lodash's extend in favour of classes.
I've been using them for years with bookshelf and it plays well (yet to find an issue).
Is anyone heading this refactor?

@rapzo I don't think so.

I don't see any typescript examples online of bookshelf. How are they supposed to work?


ssl handshake failed

I keep having this kind of error at startup :
dns    | 2021/04/09 22:04:01 INFO [22768875766546432] unbound[15:0] error: ssl handshake failed crypto error:0D0D90AD:asn1 encoding routines:ASN1_TIME_adj:error getting time
dns    | 2021/04/09 22:04:01 INFO [22768875766546432] unbound[15:0] error: and additionally crypto error:0D0D90AD:asn1 encoding routines:ASN1_TIME_adj:error getting time
dns    | 2021/04/09 22:04:01 INFO [22768875766546432] unbound[15:0] error: and additionally crypto error:0D0D90AD:asn1 encoding routines:ASN1_TIME_adj:error getting time
dns    | 2021/04/09 22:04:01 INFO [22768875766546432] unbound[15:0] error: and additionally crypto error:0D0D90AD:asn1 encoding routines:ASN1_TIME_adj:error getting time
dns    | 2021/04/09 22:04:01 INFO [22768875766546432] unbound[15:0] error: and additionally crypto error:1416F086:SSL routines:tls_process_server_certificate:certificate verify failed

My docker-compose.yml file :
version: "3"
services:
  dns:
    image: qmcgaw/dns
    container_name: dns
    volumes:
      - /home/pi/config/dns/include.conf:/unbound/include.conf:ro
    environment:
      - BLOCK_MALICIOUS=off
      - PROVIDERS=cloudflare,google
      - IPV6=on
    ports:
      - 53:53/udp
    dns: <IP_ADDRESS>
    network_mode: bridge
    restart: always

My include.conf file :
server:
  local-data: "*.local A <IP_ADDRESS>"

Event without the include.conf file, any environment parameter and setting dns to localhost it doesn't work either.
What is the problem ?

Oh oh that's because of Alpine 3.13 and you're running a 32 bit OS (the time representation changed and many programs (👀 unbound/openssl) didn't change their code for it). I'll revert back to Alpine 3.12.
For the time being you can use a previous image tag (I think v1.5.1) or a soon to be newer image qmcgaw/dns:v2.0.0-beta. Documentation is a bit different, you can find it on the v2.0.0-beta branch.

Can you try that first? Does this solve it perhaps?

@qdm12 - I was having this exact problem for the last week or so and the instructions in your link fixed it for me.  Thank you!


Drag over first/last slide makes slider move to wrong direction (loop: false)

For example: when 1st slide is active and user drags slider to left slider jumps to 2nd slide.

fixed


chore(main): release 0.11.2

:robot: I have created a release beep boop
0.11.2 (2024-06-11)
🪲 Bug Fixes

revert avatar size enum change (b387a1b)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/ZebraDevs/zeta_flutter/releases/tag/v0.11.2 :sunflower:


feat(composer): Track metrics in Composer

Summary
This PR setups and instruments metrics with Composer.
Background
Composer currently doesn't track any metrics. We require metrics in production for observability and alerting.
Changes

Metrics setup for Composer crate

More changes detailed in the Metrics section
Testing
Tested these changes by launching composer against messenger rollup and bombarding messenger rollup with txs. The metrics were accurate w.r.t to the load composer received.
Metrics

geth_collector_transactions_collected: A counter of the transactions collected by the Geth Collector labelled per rollup.
geth_collector_transactions_dropped: A counter of the  transactions dropped by the Geth Collector labelled per rollup. This can be due to the Executor channel being closed or the channel has timed out.
geth_collector_transactions_forwarded: A counter of the transactions successfully sent by the Geth Collector to the Executor. This is also labelled per rollup.
geth_collector_connection_latency: A histogram of the  time taken to establish the wss connection with the geth rollup.
grpc_collector_transactions_collected: A counter of the number of transactions collected by the gRPC collector
grpc_collector_transactions_dropped: A counter of the number of transactions dropped by the gRPC collector due the Executor channel being closed or the channel being timed out.
grpc_collector_transactions_forwarded: A counter of the transactions successfully forwarded by the gRPC collector to the Executor.
transactions_received: A counter of transactions received by the executor from the collectors labelled by rollup id.
transactions_dropped_too_large: A counter of transactions dropped because they were too large to fit in a bundle
nonce_fetch_count: A counter of the number of times we have attempted to fetch the nonce
nonce_fetch_failure_count: A counter of the number of times we have failed to fetch the nonce
nonce_fetch_latency: A histogram of the latency of the nonce fetch call
current_nonce: A gauge of the current nonce
transaction_submission_latency: A histogram of the latency of submitting a transaction to the sequencer
transaction_submission_failure_count: A counter of the number of failed transaction submission to the sequencer
bundles_submission_success_count: A counter of the total number of successful bundle submissions
bundles_submission_failure_count: A counter of the total number of failed bundle submissions
bundles_outgoing_transactions_count: A histogram of the number of outgoing transactions in the outgoing bundle
bundles_outgoing_bytes: A histogram of the size(in bytes) of the outgoing bundle
bundles_not_drained: A count of the total number of bundles not drained during the shutdown process
bundles_drained: A count of the total number of bundles drained during the shutdown process
bundles_total_count: A counter of the total number of bundles created in the composer's lifetime
bundles_total_bytes: A histogram of the size of the bundles created in the composer's lifetime
bundles_total_transactions_count: A histogram of the total number of transactions in bundle's created in the composer's lifetime

closes

High level feedback: I think the metrics are too granular at this stage.


_curses.error: addwstr() returned ERR

The app launches. All seems to work. But switching to the "peers" screen fails. My bitcoind is v0.15 compiled from sources with disabled wallet (./configure --without-gui --disable-tests --disable-wallet).
Traceback (most recent call last):
  File "/Users/darwin/bitcoind-ncurses2/main.py", line 243, in <module>
    mainfn()
  File "/Users/darwin/bitcoind-ncurses2/main.py", line 232, in mainfn
    loop.run_until_complete(t)
  File "/usr/local/Cellar/python3/3.6.2/Frameworks/Python.framework/Versions/3.6/lib/python3.6/asyncio/base_events.py", line 467, in run_until_complete
    return future.result()
  File "/Users/darwin/bitcoind-ncurses2/main.py", line 49, in keypress_loop
    await handle_keypress(key)
  File "/Users/darwin/bitcoind-ncurses2/main.py", line 35, in handle_keypress
    key = await callback(key)
  File "/Users/darwin/bitcoind-ncurses2/modes.py", line 87, in handle_keypress
    await self._seek_mode(1)
  File "/Users/darwin/bitcoind-ncurses2/modes.py", line 62, in _seek_mode
    await self.set_mode(newmode)
  File "/Users/darwin/bitcoind-ncurses2/modes.py", line 50, in set_mode
    await self._call_callbacks(self._mode, newmode)
  File "/Users/darwin/bitcoind-ncurses2/modes.py", line 40, in _call_callbacks
    await cb2(newmode)
  File "/Users/darwin/bitcoind-ncurses2/view.py", line 44, in on_mode_change
    await self._draw_if_visible()
  File "/Users/darwin/bitcoind-ncurses2/view.py", line 36, in _draw_if_visible
    await self._draw()
  File "/Users/darwin/bitcoind-ncurses2/peers.py", line 85, in _draw
    self._pad.addstr(1+index-offset, 93, str(peer['synced_headers']).rjust(7)    )
_curses.error: addwstr() returned ERR

> python3 --version
Python 3.6.2
> sw_vers
ProductName:	Mac OS X
ProductVersion:	10.11.6
BuildVersion:	15G1611

Thank you for reporting this.
I think this is a simple one - in haste, I forgot to implement scrolling in the peers view.
So if you have more than ~17 peers or so it will attempt to draw outside the pad and crash.
Should be able to fix that tonight.

Yep, I had ~90 peers.
No hurry. And btw/ thanks for resurrecting development of this project.

No problem! I'm going to add an issue for handling curses errors more generally (because it doesn't make sense to bring down the house simply because something doesn't fit on the screen), but that'll be a job for later. :)

7d45bd81a76f8e238c1a1bea126ebd2cd6d97440 is a temporary fix for this issue. It doesn't implement scrolling, just stops drawing after the first 15 peers.

Confirmed. 7d45bd81a76f8e238c1a1bea126ebd2cd6d97440 fixed the crash for me.


avoid memoized flipper state in tests

Fixes recent intermittent spec failure. Avoid cached flipper state polluting tests
Review checklist

[ ] First, the most important one: is this PR small enough that you can actually review it? Feel free to just reject a branch if the changes are hard to review due to the length of the diff.
[ ] If there are any migrations, will they the previous version of the app work correctly after they've been run (e.g. the don't remove columns still known about by ActiveRecord).
[ ] If anything changed with regards to the public API, are those changes also documented in the apiary.apib file?
[ ] Are all the changes covered by tests? Think about any possible edge cases that might be left untested.

this is fixed now and should fix any intermittent spec failures caused by flipper state

Seems to be passing now, so LGTM. There's no way I can see of re-running the specs in Travis if they all pass (to test intermittence), but if they're good here, locally and they all get run again when staging gets built, that's enough.

Cool - i manually recreated the failing travis specs via bisect and the rspec seed to debug this. If you haven't you should check it out, https://relishapp.com/rspec/rspec-core/docs/command-line/bisect


Page buffer evicts files too eagerly

Originally posted by @bmschmidt in https://github.com/duckdb/duckdb-wasm/issues/381#issuecomment-968996354
I have a related question, I think. (Let me know if better placed elsewhere.)
I'm registering a remote parquet file which has one column (word0) in sorted order to facilitate partial reads using the parquet metadata.
await f.registerFileURL("words.parquet", "https://$sitename.benschmidt.org/$fname.parquet");

I then query it with
f.query(`SELECT * FROM "words.parquet" WHERE word0 = '${r}'`))

It returns the results without pulling the whole file! Hooray!
But: if I run subsequent queries for the same word, I get a large number of serial HTTP range requests each time, rather than re-using the data I just loaded. They're served from the browser cache, so it at least doesn't require a full HTTP round trip; but my impression from the blog post was that it would use a buffered or web filesystem rather than the browser to generate the chunks. Is there some way to re-use the content inside duckdb?
(FWIW: this is one-grams from google ngrams, also including count metadata for words starting with 'A', 'B', and 'C' (capital only). '$fname' above is actually called 'word_small_page', and $sitename is 'ngrams'--but it's a biggish (150MB) file that I don't want getting autoscraped from this comment.)

Fixed in 8d2ef58af9824c711bd8dd797b39559a900885a7


chore: README improvements

add angular sample
add vue sample
doc the link props

@bradmartin thanks a lot for this!


Update AzurePipelinesCredential docs

Does this need a changelog entry for https://github.com/Azure/azure-sdk-for-go/pull/23025?

No, that was in #23029


optimise interface

Thanks for making a tip top app!
I'd love to have the interface updated for better use of the screen space / real-estate.
Specifically, the 'BMO/Chat \n Model: \n Reference' text area takes up lots of room. The text being smaller, and arranged horizontally would be a good start. But removing this all together would be even better, since knowing this information is more of a settings thing? Or even integrate it into the scrolling frame?

Thanks again,

use this space for possible attributes such as tone and style etc.

v1.8.2
You can now go to BMO Settings > Appearance > Allow Header and turn off the display.
Let me know if this works for you :D

oh wow! thanks @longy2k - looking great


Add ability to exclude specific methods

DSL ideas:
class ArrayProxy
  include Charlatan.new(:array, exclude: [:to_a, :to_ary])
end

:+1: !  is this planned?

It's under consideration :)


is there documentation to write test code for the generated package?

is there reference documentation on how to go about writing test code for the generated package?

FWIW in our use of sqlc, we haven't written tests for the generated code directly, though our tests that generally exercise the related codepaths end up triggering the sqlc code during test.
In general I think I'd say, given that the code is generated, there's not a whole lot of value in writing tests for it? Any issue that such a test might catch should really be caught by tests for sqlc itself.
If there was value in having tests for the generated code, it would probably make the most sense to also generate those tests? Unless you're imagining tests that couldn't be easily generated?

FWIW in our use of sqlc, we haven't written tests for the generated code directly, though our tests that generally exercise the related codepaths end up triggering the sqlc code during test.
In general I think I'd say, given that the code is generated, there's not a whole lot of value in writing tests for it? Any issue that such a test might catch should really be caught by tests for sqlc itself.
If there was value in having tests for the generated code, it would probably make the most sense to also generate those tests? Unless you're imagining tests that couldn't be easily generated?

@aphsa
I just saw it recently.
How to handle DB errors in Golang correctly - DEV Community 👩💻👨💻

@aphsa
I just saw it recently.
How to handle DB errors in Golang correctly - DEV Community 👩💻👨💻


Add mixin to serialize nil values to defaults

Closes #720

Sorry, this just caught my eye.  If you want defaults for attributes, why would you not want to set this on the database?  Serializing attribute defaults differently than their actual default seems pretty confusing.
For what it's worth, restpack properly serializes db defaults when they're set.

In #720 Brian mentioned he'd prefer attributes to never be null, there are a few places, namely the UserSerializer, where attributes won't be shown if a user doesn't have sufficient permission to see them. This just makes them an empty string, or 0, or false instead of null.

Yeah, this is kind of all over the place (and maybe I should be commenting on #720).
Null means missing without a default value and we shouldn't try to change that.
If a user doesn't have permissions to view an attribute, it shouldn't be part of the response.
If an actual default exists, it should exist on the database column.
In the examples raised:

A project's "introduction" value is null until it's manually defined. An introduction is a string. It should never be anything else. It should never be null

Should be a default empty string value.

but what about numbers count: 0

Counters should always default to zero.
Honestly, setting defaults to fake a DTD of some sort, is going to cause more headaches in the long run.  I'm seriously confused about what's actually motivating this.

So I really have no opinion on whether null values should be returned from the API or not. According to @brian-c it was easier for him to not have them be returned, so we agreed to do that. Not returning an attributes is effectively the same as setting it to null, so those attributes are still returned in the response.
What kind of issue do think this would cause?

Not returning an attributes is effectively the same as setting it to null

Test whether it's a missing value or a missing attribute.  e.g. response.foo // => null vs. response.hasOwnProperty('foo') // => false
A simple example of how this could end up biting you:

show a model with serialized attribute: 0, but actually nil
expect model to show up in a query with the filter ?attribute=0

Other than project contents, the schema seems to have most defaults defined.
It seems like a much easier approach to just add blank/empty defaults to that table.

Yeah I'm curious what @brian-c and @camallen think. I think I mostly agree with what you're saying, but I still think we should return the attributes with some sort of null or empty value when a user isn't permitted to see their actual value to keep responses consistent.
I don't have a problem adding the defaults to contents, so I'll do that as well.

No strong opinion here.
Users' email field could be a good example:
A user is allowed to see their own email address, so it's the string<EMAIL_ADDRESS>A user is not allowed to see another user's email address, so I'd expect the other user to just not have an email field. Their email address isn't null, we just can't see it.
Let's pretend a user is allowed to say "I don't want to give you my email address." I'd expect that value to be null, (assuming we didn't set it up with some kinda has_email boolean).

Null means missing without a default value and we shouldn't try to change that.

Yep

If a user doesn't have permissions to view an attribute, it shouldn't be part of the response.

As Brian mentions the value isn't null in the DB so a representing that as an empty string is an arbitraty choice for us. I can't see any recommendations in the JSON-API spec about this so I think it's up to us to decide what we want to do. I think it makes the client simpler to just serialize empty / missing values here.

If an actual default exists, it should exist on the database column.

Agreed. Rails counters will be set to 0 so we should mimic this behavriour in any of our custom counter fields.
I think the example of filtering on a value that has been serialized with a different value is a good example of what can go wrong with this. Any value that can be filtered on should have a sensisble default in the DB. If it's a non-DB value then it won't be filterable by restpack anyway. This should take care of most of the problems.
For non-filterable values, I don't think there is any problem serializing missing values with sensible defaults based on their types.

I'll do this differently.


CO2 and Price API Connection

For CO2

In Europe (with free API) :  https://www.nowtricity.com/

Price

In Germany (no API): https://www.stromauskunft.de/


feat: Add has_one relations inference so you don't need to pass accounts that are referenced by a has_one

This is similar to PDA inference. In typescript, you can now avoid passing to .accounts() accounts that can be resolved by fetching and pulling fields off of provided public keys.
Also added a few handy methods I'd like to see. Can remove if needed.
See the tests/ repo for more details.

Nooahhhhh


restart linting if .lintr file is created or modified

Is your feature request related to a problem? Please describe.
mildly annoying that I have to restart vscode as I modify linting rules
Describe the solution you'd like
vscode-R would restart the linting process or lsp if the .lintr file is modified with a change
Describe alternatives you've considered
expose the ability to restart the lsp/lintr process manually

linting is called by languageserver. You could always save you file to trigger linting if .lintr is changed. It will always use the latest rules.

@renkun-ken appreciate the feedback! Any idea where I can configure the “re-lint on .lintr save” setting?
Also, appears that languageserver isn’t honoring the exclusions in my .lintr file. Not sure how to repro that behavior in a way that’s helpful, but wondering how I could debug that?

Any idea where I can configure the “re-lint on .lintr save” setting?
Maybe I'm not saying it clearly. There's no "re-lint on .lintr save" but "re-lint on file save with latest .lintr. If you change your .lintr, you could always save your file being edited to trigger the linting and it will use the latest .lintr without having to restart.

appears that languageserver isn’t honoring the exclusions in my .lintr file.
languageserver calls lintr::lint_text in a separate process to perform the diagnostics and languageserver does not read your .lintr file but passes the file path to lintr and only the lintr package will read it.

Looks like your .lintr is not written correctly. You may use lintr::lint_file("path/to/your/script.R") and see if the linting is producing expected results.
A correct .lintr file to exclude some linters looks like the following:
linters: with_defaults(assignment_linter = NULL, line_length_linter(120))

okay, so did some more playing around here with respect to diagnostics honoring the exclusions property in .lintr.
I was able to confirm that find_config("path/to/my/script") does find and recognize that the project .lintr file. Furthermore, with a opening of the project, it appears language-server does honor the exclusions in .lintr, which I've left below for reference.
linters: with_defaults(line_length_linter(88), object_usage_linter = NULL, commented_code_linter = NULL, seq_linter = NULL)
exclusions: list("path/to/my/script.R")

once I open the file, however, it begins linting the file, even though it's in the exclusions list that language-server formerly honored.
That all being said, it:

is likely not related to this package, but languageserver
I believe is related to jimhester/lintr#438

Not sure if you want to leave this issue open to add the "on-save" feature still, seems like it'd be a hook on the workspace onDidSaveTextDocument event or potentially the onDidSaveConfiguration event.

Thanks for your testing.
The exclusions not working is caused by languageserver trying to lint a temporary file (with user edits saved) rather than the real file in user workspace folder. The path in exclusions applies to the workspace folder but not the temp folder.
To resolve this more easily, we filed an issue https://github.com/jimhester/lintr/issues/475 but no action is taken yet. And this is indeed another issue of languageserver.

Closing as resolved.


[amazon-corretto] Automate eol retrieval

Based on the table on https://aws.amazon.com/corretto/faqs/.

Expected diff:
diff --git i/releases/amazon-corretto.json w/releases/amazon-corretto.json
index 6f40713..83f45f5 100644
--- i/releases/amazon-corretto.json
+++ w/releases/amazon-corretto.json
@@ -1,5 +1,22 @@
 {
-  "releases": {},
+  "releases": {
+    "8": {
+      "name": "8",
+      "eol": "2026-07-31"
+    },
+    "21": {
+      "name": "21",
+      "eol": "2030-10-31"
+    },
+    "17": {
+      "name": "17",
+      "eol": "2029-10-31"
+    },
+    "11": {
+      "name": "11",
+      "eol": "2027-10-31"
+    }
+  },
   "versions": {
     "<IP_ADDRESS>.1": {
       "name": "<IP_ADDRESS>.1",


DeviantArt URLs not working with mask

URL is now something like this https://www.deviantart.com/rotix102/art/Dark-Magician-Girl-857559594
The site regex in sites.ts needs to be updated

Actually I see the URL SauceNao returns does look similar but it doesn't work with the mask

@Ovyerus

I'll be closing this now as part of housekeeping, let me know if this is still a bug that you encounter.


Access screenshot feature using GPIO

I would like to access the screenshot button through a GPIO, how can I proceed.

You can control pretty much all aspects of the Cam_Web system using the command pipe. See the pipe section in the wiki.
You can try this out simply by using a terminal and using echo to send commands into the pipe. For example
echo 'im' >/var/www/html/FIFO
sends an im command and the system will take a snapshot image.
So all you have to do is use a simple python program to monitor a GPIO button and then send in whatever command you want to the pipe.
A python snippet to send commands goes like
fifo = open('/var/www/html/FIFO', "w")
fifo.write('im')
fifo.close()


Fix code block in docs

Fixes a code block that didn't properly render on the installation page.

Thank you


Fix "relabel_configs" name in an error message

Found this one while tracking down changes done in https://github.com/prometheus/docs/pull/400

Thanks for the PR. The error message is correct here, this is a about a single relabel config rather than the list of them.

Ok, sorry about this !


updateParallaxHeaderViewHeight missing

VGParallaxHeader implements updateParallaxHeaderViewHeight, which is not exposed here.

1

Hi,
The header height is not in the current release (0.0.6). I will expose the property as soon as its available in a release.

I've added the latest VGParallaxHeader code into the repo while waiting for the next release. The updateParallaxHeaderViewHeight method is now exposed.


Add support for Fedora 36

🗣 Description
This pull request adds support for Fedora 36, which was released on May 10, 2022.
Note that this PR cannot be merged until @geerlingguy creates a geerlingguy/docker-fedora36-ansible repository (or we create our own).
💭 Motivation and context

Eventually Fedora 34 and Fedora 35 will be in the rearview mirror, so it is important to go ahead and start testing our Ansible roles with Fedora 36.
We want to keep our COOL FreeIPA AMI on the latest and greatest Fedora release.

🧪 Testing
All automated testing passes.
✅ Pre-approval checklist

[x] This PR has an informative and human-readable title.
[x] Changes are limited to a single goal - eschew scope creep!
[x] All relevant type-of-change labels have been added.
[x] I have read the CONTRIBUTING document.
[x] These code changes follow cisagov code standards.
[x] All new and existing tests pass.

FYI the fedora36 docker image is coming, hopefully in a few minutes ;)


SAMD Support

I managed to get the library working with both the ItsyBitsy M0 and M4 from adafruit with a relatively small code fix. I can submit a pull request(I think) once I get a bit more familiar with GIT, but the only change that needs to be made is to replace
#if defined(__AVR__)
with
#if defined(ARDUINO_ARCH_AVR) || defined(ARDUINO_ARCH_SAMD)
If other boards use the standard SPI configuration as defined for AVRs, then moving to
#if defined(ESP32)
// esp32 specific code here
#elif
// code for everyone else here
#endif

might work better.

Hi @nakanaela, I've been busy but I will check your changes as soon as I can. It's much better if you can submit the pull request. Thanks for your contribution.