Mac OS: Crash on cmd+q

OS: Mac OS X 10.14
GPMDP Version: 4.6.1
Issue Descriptions: Crash on cmd+q
Steps to Reproduce: tap cmd+q
Process:               Google Play Music Desktop Player [251]
Path:                  /Applications/Google Play Music Desktop Player.app/Contents/MacOS/Google Play Music Desktop Player
Identifier:            google-play-music-desktop-player
Version:               4.6.1 (4.6.1)
Code Type:             X86-64 (Native)
Parent Process:        ??? [1]
Responsible:           Google Play Music Desktop Player [251]
User ID:               501

Date/Time:             2018-10-01 02:20:11.482 +0300
OS Version:            Mac OS X 10.14 (18A391)
Report Version:        12
Bridge OS Version:     3.0 (14Y667)

Time Awake Since Boot: 28000 seconds
Time Since Wake:       2200 seconds

System Integrity Protection: enabled

Crashed Thread:        0  CrBrowserMain  Dispatch queue: com.apple.main-thread

Exception Type:        EXC_BAD_INSTRUCTION (SIGILL)
Exception Codes:       0x0000000000000001, 0x0000000000000000

Application Specific Information:
*** CFHash() called with NULL ***

Thread 0 Crashed:: CrBrowserMain  Dispatch queue: com.apple.main-thread
0   com.apple.CoreFoundation      	0x00007fff37985ccc CFHash + 372
1   com.apple.CoreFoundation      	0x00007fff379b1547 CFBasicHashGetCountOfKey + 198
2   com.apple.CoreFoundation      	0x00007fff379b5524 CFSetContainsValue + 73
3   com.apple.CoreFoundation      	0x00007fff379d20d2 CFRunLoopRemoveSource + 366
4   com.github.electron.framework 	0x0000000106c79514 extensions::GlobalShortcutListenerMac::StopWatchingMediaOrVolumeKeys() + 36
5   com.github.electron.framework 	0x0000000106c79f57 extensions::GlobalShortcutListenerMac::UnregisterAcceleratorImpl(ui::Accelerator const&) + 215
6   com.github.electron.framework 	0x0000000106c78b26 extensions::GlobalShortcutListener::UnregisterAccelerator(ui::Accelerator const&, extensions::GlobalShortcutListener::Observer*) + 150
7   com.github.electron.framework 	0x0000000106c78c89 extensions::GlobalShortcutListener::UnregisterAccelerators(extensions::GlobalShortcutListener::Observer*) + 297
8   com.github.electron.framework 	0x0000000106b5b992 atom::api::GlobalShortcut::UnregisterAll() + 34
9   com.github.electron.framework 	0x0000000106b5b94a atom::api::GlobalShortcut::~GlobalShortcut() + 58
10  com.github.electron.framework 	0x0000000106b5b9f9 atom::api::GlobalShortcut::~GlobalShortcut() + 9
11  com.github.electron.framework 	0x0000000106b5ba2e atom::api::GlobalShortcut::~GlobalShortcut() + 14
12  com.github.electron.framework 	0x0000000106b5ba4d non-virtual thunk to atom::api::GlobalShortcut::~GlobalShortcut() + 13
13  com.github.electron.framework 	0x0000000106bc577f mate::TrackableObjectBase::Destroy() + 15
14  com.github.electron.framework 	0x0000000106bc59ea 0x106b28000 + 645610
15  com.github.electron.framework 	0x0000000106bc59b8 0x106b28000 + 645560
16  com.github.electron.framework 	0x0000000106bc597c 0x106b28000 + 645500
17  com.github.electron.framework 	0x0000000106bc5944 base::internal::Invoker<base::internal::BindState<void (mate::TrackableObjectBase::*)(), base::WeakPtr<mate::TrackableObjectBase> >, void ()>::Run(base::internal::BindStateBase*) + 20
18  com.github.electron.framework 	0x0000000106b3d3b0 0x106b28000 + 86960
19  com.github.electron.framework 	0x0000000106bcf42d atom::AtomBrowserMainParts::PostMainMessageLoopRun() + 77
20  com.github.electron.framework 	0x0000000107039039 0x106b28000 + 5312569
21  com.github.electron.framework 	0x000000010703b57c 0x106b28000 + 5322108
22  com.github.electron.framework 	0x0000000107034d78 0x106b28000 + 5295480
23  com.github.electron.framework 	0x0000000106f7df40 0x106b28000 + 4546368
24  com.github.electron.framework 	0x0000000108b733d4 0x106b28000 + 33862612
25  com.github.electron.framework 	0x0000000106f7cd54 0x106b28000 + 4541780
26  com.github.electron.framework 	0x0000000106b2aa44 AtomMain + 68
27  google-play-music-desktop-player	0x0000000106b1ff26 main + 38
28  libdyld.dylib                 	0x00007fff64a4b085 start + 1

Can reproduce, started with Mojave. When you Quit the app, it hangs for ~30 sec before getting that SIGILL.
Workaround that will made it work as normal for me: give GPMDP "Accessibility" permissions:

I believe updating Electron in the package.json would also fix this (without needing to give Accessibility permissions), but don't have time to check.

I've looked into it some more. Updating Electron to 2.0.9 makes it crash much faster when doing cmd+q (now it crashes almost instantly instead of hanging for 20+ seconds).
I believe the cause of the issue is https://github.com/electron/electron/issues/14837. But what I said regarding "give GPMDP Accessibility permissions" is still a working workaround, but hopefully Electron gets this fixed soon.

I don't have this on the General Availability release of Mojave. Can you confirm it is still an issue on the public Mojave releases

Still have this crash on public release Mojave 10.14 (18A391)

+1 normally happens on quit, but today I had a random crash when switching to YouTube music, not sure if it's related and I haven't been able to repro.
OSX: 10.14, MacBook Pro (15-inch, 2018) I9

+1

Getting this issue too.

Hi! I'm working on the similar application, but for Yandex.Music. Here's my small native binding for this which can be used as a workaround until Electron fixes it: https://github.com/4ndv/node-mac-accessibility-features-check
It allows to determine user's consent on Accessibility.
I've never tried to build application under different OSes and it probably requires a Mac to build, but for me it works ¯_(ツ)_/¯

Ahh fantastic, so what causes the crash? The app tries to do something not
allowed so it gets killed by the macos runtime?
On Sat, 15 Dec 2018, 06:27 Andrey Viktorov<EMAIL_ADDRESS>wrote:

@deed02392 https://github.com/deed02392 actually not, it crashes only
if an app without such permissions registers a global shortcut. This
library can be used just to check permissions and register hotkeys only if
they are present.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/MarshallOfSound/Google-Play-Music-Desktop-Player-UNOFFICIAL-/issues/3369#issuecomment-447541848,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ADX01-05VMfgXpoCvdcYt9ZO9q50ZCMxks5u5JZdgaJpZM4XBNbR
.

@4ndv I commented out the globalShortcuts import (and all the calling code) in src/main/features/core/keyboardShortcuts.js and I still get the crash. My report looks different to the one in this thread, though, it doesn't mention reference to the GlobalShortcut::UnregisterAll method. I confirmed the behaviour is present or not with Accessibility permission off or on (respectively). So there must be another source to this crash.

@deed02392 can you provide crashlog or post it in here: electron/electron#16090?

Sure, added a crashlog to your issue.

This will be fixed by the incoming Electron upgrade


Maintainers wanted!

Hey guys
As you have probably noticed this git repo isn't well maintained: code is not being reviewed, requests are not merged etc.
This is all because because we have shifted our development focus away from iOS/Swift. That said we are happy to accept anyone who wish to become a contributor to the project in terms of code review and PR merging.
Please apply below this post.

Hi, I'd like to be a maintainer.  I have over a decade of dev experience and an MS in CS.  I'm expert in TDD and gain help the PRs come in with proper testing.  I'd also like to help get Travis CI setup for this project.  Hope I can help!
--Steve

Adding you to contributors Steve. The biggest challenge we have here is making sure the code works and all tests pass. Feel free to introduce any CI you think is right.

@sjturley can you email me at<EMAIL_ADDRESS>


Upgraded amplify version from 8.5.1 to 12.0.0 and amplify commands don't work anymore

How did you install the Amplify CLI?
npm
If applicable, what version of Node.js are you using?
18.13.0
Amplify CLI Version
amplify commands not returning any response
What operating system are you using?
Mac
Did you make any manual changes to the cloud resources managed by Amplify? Please describe the changes made.
No manual changes. Only ran amplify upgrade
Describe the bug
I was trying to use amplify/hooks but it was not available in the version I was using. This project is an year old. We did not find a need to upgrade the amplify version until now. We ran amplify upgrade and now none of the amplify commands return any response.
Expected behavior
I would expect that the commands would run and give me feedback on what it did.
Reproduction steps

npm install -g<EMAIL_ADDRESS>Set up a project with the steps in amplify's docs
sudo amplify upgrade

At this point in time, the latest version of amplify is 12.0.0
Project Identifier
did not give any response
Log output

# Put your logs below this line

Additional information
No response
Before submitting, please confirm:

[X] I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.
[X] I have removed any sensitive information from my code snippets and submission.

works if i use sudo


Filtered images for sevae training

Hello,
can you please share how to obtain the filtered images required for the training of the model?
In particular, I've collect some data (depth images + segmentation images) from gym simulator and I already serialized this data into some TFRecord files. The problem is that apparently the training is expecting not just the depth images and the segmentation images, but also some filtered images. How can I obtain that?
Thank you in advance

@mihirk284 can you have a look at this?

Hei @guglielmo610 ,
Filtered image was a thing we were trying out before this work, but we do not use it anymore. We kept it in code to maintain compatibility with our setup.
You can fill in this image with black pixels and ignore it, otherwise, you can just write a custom tfrecord feature descriptor here based on your .tfrecord file setup.


Bug/blank codeowners

A reference to the issue / Description of it
To try to clear the bug on #7430
This is an initial push to get the proposed changes approved/confirmation they will work to correct the issue.
The change is within the generate_codeowners section

When I tried this code locally Steve it made more changes to the CODEOWNERS file than expected. In my view the ideal scenario is that we update the script and re-run it so that the only change it would make is to the error on the /terraform/environments/genesys-call-centre-data line.
I've found a more succinct way of altering the if statement here
if [ -n "$codeowners" ] && [ "$codeowners" != "@ministryofjustice/ " ]; then
I found that on this line where $codeowners is defined, the JQ is appending @ministryofjustice/ to any values in .codeowners[] which means that rather than $codeowners being a null value it is actually given a value of "@ministryofjustice/" and so the logic was adding that to the file.
I tested it locally and it worked as expected. I can show you that and help you to try running it locally.


I2C on STM32L552x panics

Hi!
I've recently found stm32-hal for my NUCLEO-L552ZE-Q board, and it worked great with the blink example.
I have an OLED display that I wanted to use to try I2C support, but it looks like there's an error in timings calculations, where the program crashes on i2c.rs:191, on the fact that scldel is equals to 16 it seems.
Here's the relevant part of the code:
#[entry]
fn main() -> ! {
    let cp = cortex_m::Peripherals::take().unwrap();
    let mut dp = pac::Peripherals::take().unwrap();
    clock_cfg.setup(&mut dp.RCC, &mut dp.FLASH).unwrap();
    /* ... */
    // SETUP I2C
    // Configure pins for I2c.
    let mut scl = Pin::new(Port::F, 1, PinMode::Alt(4));
    scl.output_type(OutputType::OpenDrain);

    let mut sda = Pin::new(Port::F, 0, PinMode::Alt(4));
    sda.output_type(OutputType::OpenDrain);

    // Set up an I2C peripheral, running at 100Khz.
    let i2c = I2c::new(dp.I2C2, I2cDevice::Two, 400_000, &clock_cfg); // <- Panics here
    /* ... */
}

PS: I may be wrong on the ports though, but they were taken out of my board's spec sheet, as shown there:

I need to go over the I2C code, especially related to clock config - it's likely there's a bug there. I plan to change the API so you set the clock scaler instead of attempting to set a speed. I'll let you know once complete.
What happens if you set 50kHz as the speed instead?

Redid I2C init and clock code on github. Try now. Note the breaking change. Ie, to set 400K, you now do this:
let i2c = I2c::new(
    dp.I2C1,
    I2cDevice::Two,
    I2cConfig {
        I2cSpeed::Fast400K,
        ..Default::default()
    },
    &clock_cfg
);

I was able to make it work on 400kHz on my hardware. Thank you very much!


Made MatValueRequest accessible from Java (fixes #663)

Thanks for your pull request.  Please review the following guidelines.

[X] Title includes issue id.
[X] Description of the change added.
[X] Commits are squashed.
[ ] Tests added.
[ ] Documentation added/updated.
[ ] Also please review CONTRIBUTING.md.

We need to think how to address documentation for this one. I'd take it as a separate PR.


Implement Magic Wand Tensorflow Example

Implement the Magic Wand example: https://github.com/tensorflow/tensorflow/blob/master/tensorflow/lite/micro/examples/magic_wand/README.md
We may need to retrain: https://github.com/tensorflow/tensorflow/blob/master/tensorflow/lite/micro/examples/magic_wand/train/README.md

Updated links:
https://github.com/tensorflow/tflite-micro/blob/main/tensorflow/lite/micro/examples/magic_wand/README.md
https://github.com/tensorflow/tflite-micro/tree/main/tensorflow/lite/micro/examples/magic_wand/train

I bought a 6DOF board instead of a 9DOF board so it may not work for me:
https://learn.sparkfun.com/tutorials/lsm6ds3-breakout-hookup-guide/allhttps://learn.sparkfun.com/tutorials/lsm6ds3-breakout-hookup-guide/all


Release with partytown 0.10.0

Latest release for nuxt still has partytown 0.8.0, renovatebot recently merged a commit (552a64e) that bumps the partytown dependency to 0.10.0, can you do a release?
Some functionality such as {preserveBehavior} released in 0.9.x would become available too :)

Done ✅


Upload integer-simple fix

I suddenly realized I need this and I'm not alone: https://github.com/commercialhaskell/stack/issues/399. Thanks for providing support for integer-simple. Please upload that fix as soon as you can.

Done.

Amazing. Thank you!


Why components/global exactly?

Can't we define where we'll be storing those custom icon components in our project?
This sounds more sane components/icons... I looked at the source, but I found nothing that defines this path.
So could be that I'm blind, or this global directory is something that Nuxt handles?
Kind regards.

I defined it as global (Nuxt feature) so you can use it directly in the Markdown or with Dynamic components.


fixing a broken docs link in readme.md

High Level Overview of Change
fixing a broken docs link in readme.md

Thanks for the fix!

I had a PR with a fix for this over the weekend and it was blocked on a code owner. can you tell me what we missed?

See what happened here. There were two different bugs in the same doc. :-) Do we have a simple link checker for docs like this?


Make the -w flag behave as expected

The -w flag is documented as:

-w=false: write result to (source) file instead of stdout

But in the current implementation, it writes both to file and stdout. If we want it to behave as documented, it should only write to the file when the flag is set.
This is especially problematic when we try to do some automation around hcl files with hclfmt, stdout logs are pretty annoying

Good catch @julienvey Thanks :)


Implement turnLeft and turnRight methods

Allow an increment in the car's angle. Each input of "j" or "l" causes the car
to increase/decrease the the turning angle of the car into the desired
direction

On lines 93 and 98 - shouldn't it be 5 degrees? Other than that, looks good!


Kruskal’s algorithm

Implement Kruskal's algorithm in any language.

Can I work on this issue ?

Sure, go ahead.

done! Kindy label "Hacktoberfest-accepted" so that it can be count in the Hacktoberfest 2020

I would like to do the task. Do assign me for that. I will implement the Kruskal's Algorithm in C++.

I would like to do it in Java.

@atingarg1406 sure, go ahead.

@ek08 sure, go ahead.

Can I work on this?

i can solve this efficiently in C++,please assign it to me. @Thuvan96


Support Middleman request priority

Allow agents to make generation requests with a priority field, which Middleman now respects. High-priority requests will get guaranteed access to some small proportion of our rate limits with a lab
Make Vivaria's run summarization, run analysis, and runs page query generation features use high-priority Middleman requests

Testing

[x] Run summarization still works and goes through a high-priority API key in Middleman
[x] Run analysis still works (but doesn't go through a high-priority API key because it uses Gemini models and Middleman doesn't support priority for Gemini yet)
[x] Runs page query generation still works and goes through a high-priority API key in Middleman
[x] Agents can still run even if they don't explicitly opt into sending high-priority requests, using an old version of pyhooks
[x] Agents can still run even if they don't explicitly opt into sending high-priority requests, using the latest version of pyhooks
[x] Agents can explicitly opt into sending high-priority requests and they go through a high-priority API key in Middleman

What branch of middleman should I need to use for this? I'm getting the following error when trying to do the SQL generation on main:
Post failed: TypeError('Cannot serialize non-str key None')
handle_http_exception <starlette.requests.Request object at 0x10b029e50> 500: 3 Errors: Warning('coerced from regular prompt into chat prompt')
TypeError('Cannot serialize non-str key None')
TypeError('Cannot serialize non-str key None')

Ah yes, that's because you should set OPENAI_HIGH_PRIORITY_API_KEY and ANTHROPIC_HIGH_PRIORITY_API_KEY in your local Middleman. The main branch should work.

I pushed a Middleman change (to the main branch) that improves the error message here.

Maybe this should be implemented differently. Instead of people getting to request different priorities on a per-request basis, maybe there should be a command-line flag on viv run. There's already a --low-priority flag. Maybe we also add a --request-priority flag and Vivaria automatically applies that priority to all requests associated with the run?

OK I think I should couple this to runs_t."isLowPriority". Low-priority runs should both go at the end of the run queue and use the low-priority API key.
Except that runs are by default high-priority. People need to pass the --low-priority flag explicitly to override that. We might want to change that.

But I still think this PR is worth merging as-is.


Add SetupKey auto-groups property

Extend Management API to add support for setup keys auto-tagging feature that allows automatic groups assignment to peers that used the key.
This PR just adds the property to the setup key.
Works as the first feature MVP for this request https://github.com/netbirdio/netbird/issues/458#issue-1366523452

Relates to
https://github.com/netbirdio/dashboard/pull/75


#211: Make PersistentBuffer support generic types.

Generified PersistentBuffer to support Any time.

Just synced with the updates. Unfortunately, support for float32 is buggy. To bridge this, the float32 is casted to a float64 at store and casted back to float32 at runtime.


Document upgrade path

File: datacenter/ucp/2.2/guides/admin/install/upgrade.md, CC @joaofnfernandes
Need to have an upgrade path chart on this page:

If upgrading from UCP 1.1:

Upgrade from UCP 1.1 -> UCP 2.1 -> UCP 2.2

If upgrading from UCP 2.0

Upgrade from UCP 2.0 -> UCP 2.1 -> UCP 2.2

If upgrading from UCP 2.1

Upgrade from UCP 2.1 -> UCP 2.2

cc @dhiltgen
But in a pretty chart :)

We have something like that for DTR.
@dhiltgen can you take a look at ^^ at tell me if UCP follows the same policy?

@joaofnfernandes there is a similar doc here: https://success.docker.com/KBase/Upgrading_to_Docker_17.03_(or_DDC_on_Engine_1.13)
However, this doc needs to be updated for UCP 2.2 / DTR 2.3 and probably made a little bit clearer with an explicit version chart.

Prior to 2.2, we had upgrade flows going all the way back to 1.0, but the overhead was getting unwieldy, so we dropped all upgrade flows except N-1.  We should recommend customers running anything below 2.1 that they upgrade to the latest 2.1 version first, then upgrade to 2.2

Fixed in Recommended upgrade paths.


Splitting rewrite rules for backend performance boost

Some rewrite rules in the semantics have troublesome side conditions that create problems for the booster backend. An explanation can be found in issue #266, which this PR will fix. I believe the candidates for splitting are:

#initBindings
#initBasicBlocks
#executeStatement
#transferLocal
#writeLocal
#readLocal
#evalLocal
#evalRef
#evalDeref
#evalField

NOTE: Appears that there is some issue with this changed code. I haven't been able to get proof to finish with booster.

Obsolete after #304


[BUG] Need also to publish seed when manually installing

Version information

Laravel: v5.8.7
Voyager: v1.2.1
PHP: 7.1
Database: [type] [version] (e.g. MySQL 8.0)

Description

Could you please update the voyager documentation in the manual installation section ?
The user also need to publish voyager seed, otherwise he got error : VoyagerDatabaseSeeder does not exists.

That's pretty much exactly what
php artisan vendor:publish --provider=VoyagerServiceProvider
from step 1 does?

No, in my case it did nothing.
You need to use : php artisan vendor:publish --provider=seed

seed is not a valid "provider"... so that should do nothing

Corrected in https://github.com/the-control-group/voyager/commit/62df0ef6281e94994fc676436592e44c85c6c1ff


MIPS P5600(32 bit) and I6400(64 bit) cores support added.

Seperated mips and mips64 files.
Configurations support for mips 32 bit.
MSA optimizations to follow in subsequent patches.
Signed-off-by: Shivraj Patil<EMAIL_ADDRESS>

@sva-img , thank you for the patch.
Is it possible to give me remote MIPS machine access? Then, I can test the code.


[Monitoring v2] Update the Prometheus default memory limit to 3000Mi

Setup

Rancher version: 2.6.0
Browser type & version: Chrome

Describe the bug

Currently, the default memory limit for Prometheus in monitoring v2 is 1500Mi, which is too low for the Prometheus pod to run in the long term.  We need to change it to 3000Mi

Related issue: https://github.com/rancher/rancher/issues/34850

@jiaqiluo can you update the chart with this?

Can be tested in the rancher-monitoring  100.1.0+up19.0.3
Root cause
In the chart, Prometheus default memory limit to 1500Mi
What was fixed, or what changes have occurred
change the default to 3000Mi
Areas or cases that should be tested
When installing the monitoring chart, the value in the UI should be 3000Mi
What areas could experience regressions?
n/a
Are the repro steps accurate/minimal?
n/a

Rancher Setup For Reproduction

Rancher Version: v2.6.2
Reproduction Steps

Go to local cluster from cluster explorer
Go to apps & marketplace --> Monitoring
Press install then proceed to "Prometheus" in the left menu.
Witness the memory limit is lower than the needed. (2500Mi)

Screenshot of  wrong memory limit:

Rancher Setup For Validation

Rancher Version: v2.6-head

Go to local cluster from cluster explorer
Go to apps & marketplace --> Monitoring
Press install then proceed to "Prometheus" in the left menu.
Witness the memory limit is properly set to 3000Mi

Sanity Testing
I tested this from the "install monitoring" on the cluster dashboard and got the same results.


Where to create a repository-specific token

The configuration file docs mention the ability to set a repository-specific token for an application (github_token), but I can't seem to find where to create one.
I assume this is not the same as personal access tokens since I can't limit those to a single repo, nor is it a developer application, since I don't see where to associate that with a repo. I also couldn't find anything that seemed appropriate in the OAuth Authorizations API.

@andycox so it's a bit misleading in the sense that it's a token per application you're deploying. This allows you to use different tokens for different apps on different users/organizations. GitHub's API doesn't support repository specific tokens at this point.

Makes sense, I think.
I assume that creating a separate machine user is the best way to separate tokens that can access certain repos from a personal account, but machine users are (soon to be) prohibited in my org. Is there any other way to create a token not tied to my personal account that can create deployments through the API?

I don't believe so. Machine users are a common pattern due to permissioning in the GitHub API. I think your best bet would be to email<EMAIL_ADDRESS>and describe what you're looking for so they understand the use case better and hopefully roadmap it.
I'm using the deploy:token:set link syntax for my org and the deployments are created by the user instead of a machine user. This handles permissions and correctly attributes the user requesting the deployment in the GitHub API.


Remove fileFilter "array of strings" from readme

Hi @paulmillr, thanks for readdirp!
Seems like the fileFilter "array of strings" option was removed in https://github.com/paulmillr/readdirp/commit/703dee9f823f74fd990b503df52652f397759b1f

Thanks for the review and merge!


About view_components importing and Evil Martians

Hi Chris... first of all, thanks for this awesome time saver.
The thing is, I like to use my components the Evil Martians way, so instead of
/components
   /tabs_component.rb
   /tabs_component.html.erb
   /tabs_controller.js

I end up with
/components
   /tabs
     /component.rb
     /component.html.erb
     /controller.js

And so it clashes with your code that generate the controller name and the replace(/_controller.js) doesn't happen.
Would you be willing to add (or to accept a pull request to add) another replace so it matches the case where the controller is named only controller.js.
something along the lines of
  return filename
    .replace(/^\.\//, "") // Remove ./ prefix
    .replace(/_controller.[j|t]s$/, "") // Strip _controller.js extension
    .replace(/\/controller.[j|t]s$/, "") // Strip controller.js name <-- ADD THIS
    .replace(/\//g, "--") // Replace folders with -- namespaces

Ok, fair point.

However, I would consider an option to override the built-in function with your own.

That's beyond my JS fu at the moment, :-)
I was able to accomplish what I wanted with an easy change on the example provided in the docs. I'll let it here for for people with similar needs in the future.
// app/components/index.js

import { application } from "../javascript/controllers/application"

import controllers from "./**/*controller.js"
controllers.forEach((controller) => {
    let name = controller.name.replace(/--controller.js/, "")
    application.register(name, controller.module.default)
})

Thanks again for all your work.


Put GCP-only 'scratch bucket' behind a flag

Pangeo hubs have a PANGEO_SCRATCH env variable that
points to a GCS bucket, used to share data between users.
We implement that here too, but with a more generic SCRATCH_BUCKET
env var (PANGEO_SCRATCH is also set for backwards compat).
https://github.com/pangeo-data/pangeo-cloud-federation/issues/610
has some more info on the use cases for PANGEO_SCRATCH
Right now, we use Google Config Connector
(https://cloud.google.com/config-connector/docs/overview)
to set this up. We create Kubernetes CRDs, and the connector
creates appropriate cloud resources to match them. We use this
to provision a GCP Serivce account and a Storage bucket for each
hub.
Since these are GCP specific, running them on AWS fails. This
PR puts them behind a switch, so we can work on getting things to
AWS.
Eventually, it should also support AWS resources via the
AWS Service broker (https://aws.amazon.com/partners/servicebroker/)
Ref https://github.com/2i2c-org/pilot-hubs/issues/366

Nice - do we have another deliverable to track implementing Scratch Buckets for AWS/Azure? If not maybe we should make one to track adding this functionality for those providers?


Update clever.go

Per conversation with Reid, "p.config.Endpoint" is guaranteed to exist before this method runs because it's initialized in the constructor.


Fix BigCommerce login

Partially fix  #888

@cond0r now the problem is in packages/commerce/src/api/utils/index.ts where the validation against the customerSchema fails

@cond0r now the problem is in packages/commerce/src/api/utils/index.ts where the validation against the customerSchema fails

Yes, I will investigate more and provide a fix by next week. From what I remember, login & Signup had some unresolved issues from the past. Also, I saw during my quick tests that the validations from BigCommerce don't appear and show generic messages. That will be covered in my fix PR also,  Maybe this should be closed since it isn't the complete fix for it.

@cond0r changing the customerSchema to:
export const customerSchema = z.object({
  customer: z.object({
    id: z.string(),
    firstName: z.string(),
    lastName: z.string(),
    email: z.string().optional(),
    phone: z.string().optional(),
    company: z.string().optional(),
    notes: z.string().optional(),
    acceptsMarketing: z.boolean().optional(),
  })
})

seems to fix this issue

Thank you! this will be addressed in #918


feat: add str::startswith and endswith

Closes #483

Pull Request Test Coverage Report for Build<PHONE_NUMBER>8
Details

4 of 4 (100.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.01%) to 80.958%

Totals

Change from base Build<PHONE_NUMBER>3:
0.01%

Covered Lines:
5863

Relevant Lines:
7242

💛  - Coveralls


merge package from arlac77/npm-package-template

package.json

chore(package<EMAIL_ADDRESS>

Pull Request Test Coverage Report for Build 502

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 70.0%

Totals

Change from base Build 500:
0.0%

Covered Lines:
14

Relevant Lines:
20

💛  - Coveralls

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Keycodes for "a" and "ctrl" buttons

Hi,
The code as is does not allow you to enter "a" into the JSON model on the left and to select all nodes you must hold down "a" and then press "ctrl". This is due to the keycodes for "a" and "ctrl" in app.js being switched.
However, when the keycode values are swapped, pressing ctrl-a selects all the text on the LHS as well as selecting all nodes.
I have tested this in both Chrome and IE 11.
Cheers

Thanks for letting me know. Would you like to become a contributor? Clone the repo, make the change and then submit a pull request.

Fixed by pull request.


[BUG] - No default config file -

What seems to be the problem?
cp data/config-default.js data/config.js Failed due to 'File not located'
How can I recreate this problem?
Follow documentation
What did you expect to happen?
The file to be renamed and copied over to config.js
What kind of device and web browser are you using?
MacOS + Safari

Thanks for letting us know @4lPHAP4STA .  That line was likely copied from the documentation of another one of our applications.
Try this instead.
cp data/configOntario.js data/config.js

I'll update the documentation with a valid path.


Impossible to add timeline, characters etc.

The problem
Describe the bug
With the last version (25.04.2021 16:53) the plugin doesn't work. The buttons to add Timelines, Characters, Definition and Themes are empty. And when I click on the icon, nothing happen.
To Reproduce
Steps to reproduce the behavior:

Go to Dialogic plugin
Click on timelines or character or wherever you want, nothing happen.

Expected behavior
Create a new Timelines, Characters etc.
Screenshots

System (please complete the following information):

OS: Ubuntu 20.04
Godot Version: 3.3.3
Dialogic Version: 1.1 (25 april update)

Solutions
No idea...
Possible fixes
Burning the computer... maybe...

Have you tried the icons in the toolbar?

Have you tried the icons in the toolbar?

I closed Godot and restarted it and now it's work. Strange because with the last versions, I never restarted Godot after installing Dialogic

I would vote to close this. It's quite normal that restarting is necessary.


[TIR][Schedule] Support padding-by-factor in PadEinsum

This PR introduces a minor behavior change in Pad-Einsum that makes it support padding-by-factor instead of padding-by-constant-number.

Thanks @vinx13 for the huge help fixing the tensor core case!

Fixed a merge conflict


Add Docs for Map Customization.

What Does This Do
This initializes docs that explain how to enable and customize map component options.  It also adds a tiny bit on navPlace and how those properties are currently used in Canopy.

@markpbaggett Feel free to overwrite anything that came through in #9 as you resolve the conflict.


DashContainerModel.loadStateAsync() can silently early-out, discarding new state

We had a use-case in an app where we were calling dashContainerModel.loadStateAsync() shortly after it was initially constructed (potentially with different/default state).  If the DC has not yet rendered and doesn't have a ref on its element, that method will quietly return without doing anything, discarding the request without the caller having any way to know:
https://github.com/xh/hoist-react/blob/ceb0f276758adb7558f251ef0927b0518dee328f/desktop/cmp/dash/container/DashContainerModel.ts#L231
This bit us badly in our particular case, as the same DCM then published its (default / not-updated) state on a deferred basis and the app picked that up and persisted it, overwriting the custom state we thought it should be holding.
We were able to resolve the issue at the app level by not creating the DCM until we knew which custom state we were going to use, at which point we could create/init it with the right state from the start. This is an improvement all around, but the troubleshooting process was made difficult by that silent internal return.
Would prefer for the method to do one of the following:

Log something helpful - console.warn('DashboardContainer not yet rendered - cannot update state - change will be discarded!')
Throw an error (maybe a bit more harsh than we want)
Wait until it can process the state change request, then do so. This would be the best behavior, although we would want to think through how to handle potential multiple calls that could arrive, etc.

Hi @Ryanseanlee would be great to close this one out.  It's worth a look to see if we can cleanly support the goal of holding onto a pending state request if made before it was ready, then running it when ready.   But let's not go too far down the rabbit hole on it - if that doesn't look straightforward to patch in, we can add a simple log line. That would have been enough to help me realize what was going on when this issue bit me a few months back.


olm: 2.2.1 -> 2.3.0

Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools. This update was made based on information from https://repology.org/metapackage/olm/versions.
meta.description for olm is: '"Implements double cryptographic ratchet and Megolm ratchet"'.

Checks done (click to expand)

built on NixOS

0 of 0 passed binary check by having a zero exit code.

0 of 0 passed binary check by having the new version present in output.

directory tree listing: https://gist.github.com/99ed3d1a7c1baa1794b4a16d39b93917

du listing: https://gist.github.com/8df438f007de54b5378a4d273badbb58

Test this build with Cachix (click to expand)

One time setup in nixpkgs Git checkout:
cachix use r-ryantm
git remote add r-ryantm https://github.com/r-ryantm/nixpkgs.git

Test this build:
git fetch r-ryantm && git checkout 1303e7e55a90e5890794954b840cda1ea9ca1aff && nix-shell --pure -I nixpkgs=. -p olm

Success on x86_64-linux (full log)
Attempted: olm
Partial log (click to expand)
ln -s libolm.so.2.3.0 /nix/store/7g5zglilwbs69mr54cf9c76751f9cikl-olm-2.3.0/lib/libolm.so.2
ln -s libolm.so.2.3.0 /nix/store/7g5zglilwbs69mr54cf9c76751f9cikl-olm-2.3.0/lib/libolm.so
post-installation fixup
shrinking RPATHs of ELF executables and libraries in /nix/store/7g5zglilwbs69mr54cf9c76751f9cikl-olm-2.3.0
shrinking /nix/store/7g5zglilwbs69mr54cf9c76751f9cikl-olm-2.3.0/lib/libolm.so.2.3.0
strip is /nix/store/4qvrxzxa535y8304mk195x50b6p9607d-binutils-2.30/bin/strip
stripping (with command strip and flags -S) in /nix/store/7g5zglilwbs69mr54cf9c76751f9cikl-olm-2.3.0/lib
patching script interpreter paths in /nix/store/7g5zglilwbs69mr54cf9c76751f9cikl-olm-2.3.0
checking for references to /tmp/nix-build-olm-2.3.0.drv-0 in /nix/store/7g5zglilwbs69mr54cf9c76751f9cikl-olm-2.3.0...
/nix/store/7g5zglilwbs69mr54cf9c76751f9cikl-olm-2.3.0

Failure on x86_64-darwin (full log)
Attempted: olm
Partial log (click to expand)
mkdir -p build/release/src/
clang++ -Wall -Werror -std=c++11 -fPIC -g -O3 -Iinclude -Ilib -DOLMLIB_VERSION_MAJOR=2 -DOLMLIB_VERSION_MINOR=3 -DOLMLIB_VERSION_PATCH=0 -MMD  -c -o build/release/src/pickle.o src/pickle.cpp
mkdir -p build/release/src/
clang++ -Wall -Werror -std=c++11 -fPIC -g -O3 -Iinclude -Ilib -DOLMLIB_VERSION_MAJOR=2 -DOLMLIB_VERSION_MINOR=3 -DOLMLIB_VERSION_PATCH=0 -MMD  -c -o build/release/src/base64.o src/base64.cpp
mkdir -p build/release/src/
gcc -Wall -Werror -std=c99 -fPIC -g -O3 -Iinclude -Ilib -DOLMLIB_VERSION_MAJOR=2 -DOLMLIB_VERSION_MINOR=3 -DOLMLIB_VERSION_PATCH=0 -MMD  -c -o build/release/src/outbound_group_session.o src/outbound_group_session.c
/nix/store/q2wqq1k20v8kc3vckapqf5nws30brnni-bash-4.4-p23/bin/bash: gcc: command not found
make: *** [Makefile:202: build/release/src/outbound_group_session.o] Error 127
builder for '/nix/store/k1rq1wxb4jabdpgphra929ysvdssh5r4-olm-2.3.0.drv' failed with exit code 2
error: build of '/nix/store/k1rq1wxb4jabdpgphra929ysvdssh5r4-olm-2.3.0.drv' failed

Success on aarch64-linux (full log)
Attempted: olm
Partial log (click to expand)
ln -s libolm.so.2.3.0 /nix/store/sax4wr47l4lp8rp6vjj4szwyjdidn5p4-olm-2.3.0/lib/libolm.so.2
ln -s libolm.so.2.3.0 /nix/store/sax4wr47l4lp8rp6vjj4szwyjdidn5p4-olm-2.3.0/lib/libolm.so
post-installation fixup
shrinking RPATHs of ELF executables and libraries in /nix/store/sax4wr47l4lp8rp6vjj4szwyjdidn5p4-olm-2.3.0
shrinking /nix/store/sax4wr47l4lp8rp6vjj4szwyjdidn5p4-olm-2.3.0/lib/libolm.so.2.3.0
strip is /nix/store/0pjsgkxz0rp5baycq5sp2s72lrr5q9sg-binutils-2.30/bin/strip
stripping (with command strip and flags -S) in /nix/store/sax4wr47l4lp8rp6vjj4szwyjdidn5p4-olm-2.3.0/lib
patching script interpreter paths in /nix/store/sax4wr47l4lp8rp6vjj4szwyjdidn5p4-olm-2.3.0
checking for references to /build in /nix/store/sax4wr47l4lp8rp6vjj4szwyjdidn5p4-olm-2.3.0...
/nix/store/sax4wr47l4lp8rp6vjj4szwyjdidn5p4-olm-2.3.0

@GrahamcOfBorg  build olm

Success on aarch64-linux (full log)
Attempted: olm
Partial log (click to expand)
/nix/store/sax4wr47l4lp8rp6vjj4szwyjdidn5p4-olm-2.3.0

No attempt on x86_64-darwin (full log)
The following builds were skipped because they don't evaluate on x86_64-darwin: olm
Partial log (click to expand)

a) For `nixos-rebuild` you can set
  { nixpkgs.config.allowUnsupportedSystem = true; }
in configuration.nix to override this.

b) For `nix-env`, `nix-build`, `nix-shell` or any other Nix command you can add
  { allowUnsupportedSystem = true; }
to ~/.config/nixpkgs/config.nix.

Success on x86_64-linux (full log)
Attempted: olm
Partial log (click to expand)
ln -s libolm.so.2.3.0 /nix/store/7g5zglilwbs69mr54cf9c76751f9cikl-olm-2.3.0/lib/libolm.so.2
ln -s libolm.so.2.3.0 /nix/store/7g5zglilwbs69mr54cf9c76751f9cikl-olm-2.3.0/lib/libolm.so
post-installation fixup
shrinking RPATHs of ELF executables and libraries in /nix/store/7g5zglilwbs69mr54cf9c76751f9cikl-olm-2.3.0
shrinking /nix/store/7g5zglilwbs69mr54cf9c76751f9cikl-olm-2.3.0/lib/libolm.so.2.3.0
strip is /nix/store/4qvrxzxa535y8304mk195x50b6p9607d-binutils-2.30/bin/strip
stripping (with command strip and flags -S) in /nix/store/7g5zglilwbs69mr54cf9c76751f9cikl-olm-2.3.0/lib
patching script interpreter paths in /nix/store/7g5zglilwbs69mr54cf9c76751f9cikl-olm-2.3.0
checking for references to /build in /nix/store/7g5zglilwbs69mr54cf9c76751f9cikl-olm-2.3.0...
/nix/store/7g5zglilwbs69mr54cf9c76751f9cikl-olm-2.3.0

Success on x86_64-linux (full log)
Attempted: olm
Partial log (click to expand)
/nix/store/7g5zglilwbs69mr54cf9c76751f9cikl-olm-2.3.0

Success on aarch64-linux (full log)
Attempted: olm
Partial log (click to expand)
/nix/store/sax4wr47l4lp8rp6vjj4szwyjdidn5p4-olm-2.3.0

No attempt on x86_64-darwin (full log)
The following builds were skipped because they don't evaluate on x86_64-darwin: olm
Partial log (click to expand)

a) For `nixos-rebuild` you can set
  { nixpkgs.config.allowUnsupportedSystem = true; }
in configuration.nix to override this.

b) For `nix-env`, `nix-build`, `nix-shell` or any other Nix command you can add
  { allowUnsupportedSystem = true; }
to ~/.config/nixpkgs/config.nix.


Convert floats to strings in the YAML files

Similarly to issue: #290
Stacker should be smart enough to be able to parse floats in the configuration files.

Another example of issue:
      - PolicyDocument:
          Statement:
          - Action:
            - ecr:*
            Effect: Allow
            Resource: '*'
          Version: 2012-10-17
        PolicyName: name

2012-10-17 is interpreted as a python datetime. it should be interpreted as string. Quoting the 2012-10-17 works.
      - PolicyDocument:
          Statement:
          - Action:
            - ecr:*
            Effect: Allow
            Resource: '*'
          Version: '2012-10-17'
        PolicyName: name


use useIsomorphicLayoutEffect instead of useLayoutEffect to avoid the warning log

We are using nextjs and see the below warning log.
website-api-gateway:dev: Warning: useLayoutEffect does nothing on the server, because its effect cannot be encoded into the server renderer's output format. This will lead to a mismatch between the initial, non-hydrated UI and the intended UI. To avoid this, useLayoutEffect should only be used in components that render exclusively on the client. See https://reactjs.org/link/uselayouteffect-ssr for common fixes.

Duplicate of #368

Duplicate of #368


Lazy Row Rendering in Data grid

Summary
Data grid support to render only rows that are visible to keep the DOM light and improve rendering performance.
This is a hybrid way similar to virtual scroll grids but with pagination support.

What is the change?
Rendering only the rows that are visible. Removing rows from DOM as they go out of the viewport.

Why should it go in Clarity?
Clarity Data grids are used with large volume of data. With User interfaces growing complex, it is important to keep the DOM light. This is not something application specific and looks generic enough to be part of a library.

Does this change impact existing behaviors? If so how?

DOM would only have rows that are visible/about to become visible.
This might make scroll to be little sluggish in some cases.

If this change introduces a new behavior, is this behavior accessible?
Need investigation

Use case
Clarity Data grid offers expand row feature, with a page size of 50 and detail section becoming complex (Too many components per row), the expand operation on multiple rows becomes slow from rendering perspective. Having virtual rendering would help initialize components lazily thus improving performance.
https://stackblitz.com/edit/clarity-scrollbar-expandall?file=src/app/app.component.html
Examples
Not sure if people are doing pagination + virtual scroll. But virtual scroll typically include rendering only rows that are visible.
Workarounds
Currently , less ideal workound is to  make the  clr-row-detail render lazily from consumers by manually handling this.
In Angular, using a structural directive that renders a template only when another element (row) becomes visible.
This request extends the idea to have lazy rows which doesn't seem to have a workaround.

#41

#41

@bbogdanov - this seems a tiny bit different from infinite scrolling. The main difference I see here is that the ask is for the datagrid, with a large number of rows and overflow, to only render a set amount of rows in the DOM and re-use them for the row data as a user scrolls through the array if row items. I think thatvirtual scroll would re-use the existing dom nodes, like iOS does for  UITableViewController. I believe the ask here is to detect visible rows when datagrid has rows that overflow and only display data from the the visible rows. Is that correct @tarangkhandelwal ?
We had done some POC work around infinite scrolling that investigated a virtual scroll utility but it was tied to the infinate scrolling pattern. E.g - new data is fetched when the scrolling reaches a specific height. Infinite scrolling has not been developed for several reasons, primarily because of accessibility issues. We have some notes on this because it regularly comes up as a request: https://github.com/vmware/clarity/wiki/Virtual-Scrolling

@hippee-lee  Yes I think the understanding is correct. The idea was to have a mix of Pagination + Virtual rendering within a page. With clr-row-detail there could be few rows visible at  a time in the viewport. Datagrid can potentially render only the visible ones at start and as the user scrolls can start rendering the ones about to become visible ?

While this is not a complete duplicate of #41, it does retain virtually (see what I did there?) all of the technical and accessibility concerns. What we would need to do here is build a prototype of this behavior, work with accessibility to ensure it can be done in a way that is accessible, and understand what tradeoffs have to be made to make it work. I understand its technically possible, but there are a lot of side effects and design questions that arise as well.
I've seen teams implement this hybrid approach in their own applications without the help of Clarity. We're not planning to make any significant changes like this to the Datagrid in the very near term, so I'll leave this open for context.

Given the complexity of this ask and the availability of workarounds, I don't think we'll pursue this as part of Clarity Angular. Pagination is the recommendation for scaling large datagrids and anything beyond that going to require applications to handle it on their end in an accessible manner. I'm going to close this as something we won't deliver with Clarity Angular.


Option to allow deeper zoom

Hi,
cool Library!
It would be cool to have an option that would allow to zoom further in until we get an 1:1 pixel ratio (or even further)
Best,
tomthe

I support.

I ported this component to react and we used it in a real project
It's damn hard to handle this, when you zoom in too much, the image turns black
This is a really heavy operation for the browser especially for mobile devices
And it really depends on your device.
Some links
https://www.smashingmagazine.com/2016/12/gpu-animation-doing-it-right/ (Really awesome article)
https://www.chromium.org/developers/design-documents/gpu-accelerated-compositing-in-chrome

The problems are really challenging, but unfortunately I don't have much time to work on these issues right now.
sorry guys.


Quiz scaffolding

:+1: for good measure.

thanks for the feedback @normangilmore i appreciate it. going to go ahead and merge so the rest of the team is unblocked.


Changed query ranges to be only partially inclusive to avoid duplicates

Fixes #190

lg2m. I feel inclusive lower-bound, exclusive upper-bound is more usual but not totally important


[bug usability] Multiple cursors bug on phone

On phone I experience the following issue, I tap to a position in the editor and sometimes the old position remains in its position

The monaco-editor embedded in the https://github.com/x1unix/go-playground . The author said it is best to open the issue here.

We closed this issue because we don't plan to address it in the foreseeable future. If you disagree and feel that this issue is crucial: we are happy to listen and to reconsider.
If you wonder what we are up to, please see our roadmap and issue reporting guidelines.
Thanks for your understanding, and happy coding!


CX Stored_XSS @ src/main/java/org/t246osslab/easybuggy/troubles/FileDescriptorLeakServlet.java [master]

Stored_XSS issue exists @ src/main/java/org/t246osslab/easybuggy/troubles/FileDescriptorLeakServlet.java in branch master
Method doGet at line 27 of src\main\java\org\t246osslab\easybuggy\troubles\FileDescriptorLeakServlet.java gets data from the database, for the readLine element. This element’s value then flows through the code without being properly filtered or encoded and is eventually displayed to the user in method responseToClient at line 31 of src\main\java\org\t246osslab\easybuggy\core\servlets\AbstractServlet.java. This may enable a Stored Cross-Site-Scripting attack.
Severity: High
CWE:79
Vulnerability details and guidance
Internal Guidance
Checkmarx
Training
Recommended Fix
Lines: 53

Code (Line #53):
            while ((line = br.readLine()) != null) {

Issue still exists.

Issue still exists.


Can we support one pod with multiple containers that with GPU extended resource configured?

Description of problem
Can we support one pod with multiple containers that with GPU extended resource configured?
Take GPU pass-through as an example:
docker run -it --runtime=kata-runtime --rm --device /dev/vfio/1 -v /dev:/dev debian /bin/bash

It need map the whole vm /dev path to container. If in K8S environments, we have one pod with two containers, each of container requests one GPU card,  one Pod is running on one VM, so the pod  has two GPU cards, but both of the two containers share the same vm /dev path. Both of the two cards are visible to every container.
I would like to know if my question is valid and is there any solution to this case?
Looking forward to your answer and support.

@monstercy your question is valid, to fix this "bug" we need to add support for devices cgroup, unfortunately we need to map the vfio device to the final device (the device created by the driver, ie /dev/dri/renderD128). For example in the host the device is /dev/vfio/1 but in the guest we don't know what kind of device was hot plugged, hence we don't know what device path (ie /dev/dri/renderD128) we have to put in the devices cgroup.

@devimc  thank you for your insightful answer.
If the device name is fixed. Could you give me a guide on how to modify code to resolve the issue?

@monstercy more details about the complexity of this issue https://github.com/kata-containers/runtime/pull/701#issuecomment-419443916 , let me check the code to see what we can do


linter: automate generation of oxlint config

Discussed in https://github.com/oxc-project/oxc/discussions/4279

Originally posted by nicksrandall July 15, 2024
It would be nice if there was a command (or docs) to create an up-to-date .oxlintrc.json file with all of the latest recommended rules. It's currently a pain to migrate from CLI to config file and maintain feature parity.

oxlint --init? https://biomejs.dev/guides/getting-started/#configuration

In addition to a CLI command, might make sense to offer it as an IDE action/command.  (I'm pretty sure the VS Code ESLint plugin has this as a command.)


Spread operator function arguments (regression)

TypeScript Version:  3.2.1
Search Terms: spread, arguments
Code
function test(a: number, b: number, c: number, d: number) {
    console.log(a, b, c, d);
}

const nums = [0, 1, 2, 3];

test(...nums);

Expected behavior:
the snippet above should compile without error
Actual behavior:
Error TS2556: Expected 4 arguments, but got 0 or more

This is working as intended and is not a regression. We infer type number[] for nums and therefore we have to assume that the array may have as few as zero elements. It would be nice to infer a tuple type, but the reality is that arrays are mutable (the only thing that is const in the example is the array reference--the contents of the array are not). There are many similar issues already logged, e.g. #28336, #20899, #16389, #3369.

Thank you for the clarification :)


implement mongodb_auth

Problem

Authentication on MongoDB is not enabled

Solution

implement mongodb_auth but will break other apps using mongodb

PR Status

[ ] Code finished.
[ ] Tested with Package_check.
[ ] Fix or enhancement tested.
[ ] Upgrade from last version tested.
[ ] Can be reviewed and tested.

Package_check results

moving to a new branch


Output File Issue

I want output in .gif or .tiff format.
Anyone can help me to get the output in the format.
I am using Jupiter in anaconda software.

Hi! You can output data in GeoTIFF format by setting the grid output format configuration key to geotiff. Like this in the YAML file:
output_data:
  grids:
    format: geotiff


项目中用了这个库，折叠屏如何适配？

Environment

[x] Autosize Version:
[x] Target Android Version:
[x] Device Model:
[x] Device Resolution:
[x] Design Size On AndroidManifest:

Bug Description:

Log:

Screenshot

Related Code:

Others:

请问找到方法了么


import persyst module cross platform paths

Dear MNE team:
In the persyst.py module there is an issue where the script is not platform agnostic in the way that it handles paths. Persyst lay files are only able to generate in windows platforms. So when those files are saved the lay files file section contains a windows path with the location where the file was created. If you try to process these files for analysis in a different computer MacOS or Linux. when you use persyt.py line 112
if key == 'file':
    dat_fname = op.basename(val)

if this is processed in a UNIX based machine it will output the windows path and it wont be able to get the correct basename of the file to extract the DAT file.
The only two ways I can envision this can be corrected is that you can continue to use the os module. But you then have to check if the system being use to process is a UNIX or windows base system by importing the platform python module and checking the type of system. If it is a linux system then you need to do:

import ntpath

dat_fname = ntpath.basename (val)

This indeed will correct the issue; but I am not sure the behavior in a windows machine as I am using linux.
Alternatively, you can dish the OS module all together and use pathlib, this library will handle the paths correctly in a system agnostic manner; but it will mean that you need to change everything where os module is used and make sure users install that library as part of the installation. Not sure what you think.
Andres

Yes; it worked this will do the trick;

from pathlib import Path, PureWindowsPath

win_path = PureWindowsPath(op.basename (val)).as_posix()

dat_fname = Path(dat_new).name


NetStandard15 - Moved dependency System.Xml.XmlSerializer to NLog.Wcf

👍

(restaring travis)

good change!


AUR package build issue

Describe the bug
I am not able to build package from aur repositories on Arch Linux.
To Reproduce
Steps to reproduce the behavior:

Clone git clone https://aur.archlinux.org/ungoogled-chromium.git
Go to respective folder
Build makepkg -sri
See error

Expected behavior
The AUR package should build correctly from git repository.
Environment (please complete the following information):

OS/Platform and version: archlinux (5.6.6-arch1-1)
ungoogled-chromium version: 81.0.4044.129-1

Additional context
[smoorg@archlinux ungoogled-chromium]$ makepkg -sri
==> Tworzenie pakietu: ungoogled-chromium 81.0.4044.129-1 (pią, 1 maj 2020, 14:58:45)
==> Sprawdzanie zależności potrzebnych do uruchomienia...
==> Sprawdzanie zależności potrzebnych do budowy...
==> Pobieranie źródeł...
  -> Znaleziono chromium-81.0.4044.129.tar.xz
  -> Znaleziono chromium-launcher-6.tar.gz
  -> Znaleziono 81.0.4044.129-1.tar.gz
  -> Znaleziono 54bc225e3a263be9a6b7dc5a33c5d713d9c42716.tar.gz
==> Sprawdzanie plików source za pomocą sha256sums...
    chromium-81.0.4044.129.tar.xz ... Zgadza się
    chromium-launcher-6.tar.gz ... Zgadza się
    81.0.4044.129-1.tar.gz ... Zgadza się
    54bc225e3a263be9a6b7dc5a33c5d713d9c42716.tar.gz ...   Skipping patch.
1 out of 1 hunk ignored
The next patch would create the file net/url_request/trk_protocol_handler.h,
which already exists!  Skipping patch.
1 out of 1 hunk ignored
patching file net/url_request/url_request.cc
patching file net/url_request/url_request_context_builder.cc
patching file url/url_constants.cc
patching file url/url_constants.h
patching file url/url_util.cc
Traceback (most recent call last):
  File "/home/matr/aur/ungoogled-chromium/src/ungoogled-chromium-81.0.4044.129-1/utils/patches.py", line 250, in <module>
    main()
  File "/home/matr/aur/ungoogled-chromium/src/ungoogled-chromium-81.0.4044.129-1/utils/patches.py", line 246, in main
    args.callback(args, parser.error)
  File "/home/matr/aur/ungoogled-chromium/src/ungoogled-chromium-81.0.4044.129-1/utils/patches.py", line 198, in _apply_callback
    apply_patches(
  File "/home/matr/aur/ungoogled-chromium/src/ungoogled-chromium-81.0.4044.129-1/utils/patches.py", line 132, in apply_patches
    subprocess.run(cmd, check=True)
  File "/usr/lib/python3.8/subprocess.py", line 512, in run
    raise CalledProcessError(retcode, process.args,
subprocess.CalledProcessError: Command '['/usr/bin/patch', '-p1', '--ignore-whitespace', '-i', '/home/matr/aur/ungoogled-chromium/src/ungoogled-chromium-81.0.4044.129-1/patches/core/ungoogled-chromium/block-trk-and-subdomains.patch', '-d', '.', '--no-backup-if-mismatch', '--forward']' returned non-zero exit status 1.
==> BŁĄD: Wystąpił błąd w prepare().
    Przerywam...

Is the AUR packaging even under our umbrella? If not I can't see why this is here.

That one is based on the archlinux repository. But I am not sure why this error happened, as I didn't see it myself and others didn't report it too. @smoorg Maybe you forgot to delete the src folder before run makepkg or your AUR wrapper?

Closing because this issue is stale.


Paying directly with a debit card

Hi, is it possible to enable users to pay directly using a credit card, not needing to create a Paypal account?
I'm rendering them a form for subscription payments. As we can see on the screenshot bellow, they need to login to Paypal first.

This is a PayPal question, not a django-paypal thing. Probably this is relevant:
https://www.paypal.com/us/smarthelp/article/how-do-i-accept-credit-cards-with-checkout-using-the-guest-checkout-option-faq3226


[FEATURE] Finishing UI assets

Feature Information
Feature description
We provide a lot of UI assets w/ space warp, but the GUISkin is incomplete in the assets we provide
Solution proposal
Complete the assets for the Space Warp GUISkin

Reassigned you here @Rexicon226 as I closed #66 and made it a sub task of this issue.


Add axis option to l2_normalization

This PR adds axis option to chainer.functions.normalization so that it can normalize arrays along arbitrary axis.
Previously, the function only supported the case when an input array is of dimension two and normalization happens in the second axis.
The default value of axis is set to behave identical to the previous implementation when axis is not supplied by the user.

Thanks for commenting.
There was error in forward pass of test. The expected values were not calculated correctly.
I also made tests for backward pass more robust.
The new tests have never failed after executing tests for 100 times.

Thanks for the update.  LGTM!


Updated offer page reload recipe seems to contain broken code

Library Affected:
https://developers.google.com/web/tools/workbox/guides/advanced-recipes#offer_a_page_reload_for_users
Browser & Platform:
N/A
Issue or Feature Request Description:
Updated recipe for offering a page reload to users when an update is found seems to contain broken code. The working code is included here with FIXME comments. Please verify.
if ('serviceWorker' in navigator) {
    const wb = new Workbox('/sw.js');

    const showSkipWaitingPrompt = (event) => {
        // `event.wasWaitingBeforeRegister` will be false if this is
        // the first time the updated service worker is waiting.
        // When `event.wasWaitingBeforeRegister` is true, a previously
        // updated service worker is still waiting.
        // You may want to customize the UI prompt accordingly.

        // Assumes your app has some sort of prompt UI element
        // that a user can either accept or reject.
        const prompt = createUIPrompt({
            onAccept: async () => {
                // Assuming the user accepted the update, set up a listener
                // that will reload the page as soon as the previously waiting
                // service worker has taken control.
                wb.addEventListener('controlling', (event) => {
                    window.location.reload();
                });

                // Send a message to the waiting service worker instructing
                // it to skip waiting, which will trigger the `controlling`
                // event listener above.
                // Note: for this to work, you have to add a message
                // listener in your service worker. See below.
                // FIXME: there is no sw field on the originalEvent.
                // messageSW(event.originalEvent.sw, {type: 'SKIP_WAITING'});
                messageSW(event.originalEvent.currentTarget, {type: 'SKIP_WAITING'});
            },

            onReject: () => {
                prompt.dismiss();
            }
        });// FIXME: method call was not closed out.
    };// FIXME: this bracket was missing so scope of showSkipWaitingPrompt included the following lines.

    // Add an event listener to detect when the registered
    // service worker has installed but is waiting to activate.
    wb.addEventListener('waiting', showSkipWaitingPrompt);
    wb.addEventListener('externalwaiting', showSkipWaitingPrompt);

    wb.register();
}

I think it would also be handy if this recipe showed how to trigger update discovery (unless you do this somewhere else, in which case please link to that from here).
Here's my code for doing this, which I call when the user clicks a button, and from an update poller that fires once an hour:
function checkForUpdates(wb) {
    wb.update().then(function () {
        let reg = wb.p;
        if (reg.installing || reg.waiting) {
            sendMessageToUser('Update found!');
        }
        else {
            sendMessageToUser('You are already on the latest version of this app.')
        }
    });
}

Note: in order to tell if the call to wb.update() resulted in anything (so I can tell the user something) I have to look at a hidden field called p -- the associated registration object. Not a great solution (I suspect it may break at any time). Better would be a result of some kind (boolean would do) but the wb.update() promise resolves to undefined at the moment.

Please also note that I am seeing other problems with the code in this recipe. Just got the following error: TypeError: Cannot read property 'currentTarget' of undefined. The event has no `originalEvent' field:

What I need at this point is a reference to the new service worker so I can tell it to skip waiting. The simplest thing seems to be to do as follows, but this means bypassing the public API again, which is not great.
let reg = event.target.p;
let serviceWorker = (reg.installing || reg.waiting);
messageSW(serviceWorker, {type: 'SKIP_WAITING'});

I can confirm I have the issue here as well. Sometimes originalEvent doesn't exist. Also Safari does behave slightly differently than Chrome.

https://github.com/GoogleChrome/workbox/pull/2489 should be what we eventually switch it to use, but that's going to land in v6.
In the meantime, apologies that this is still an issue. Here's my attempt at provided something fool-proof:
https://github.com/google/WebFundamentals/compare/wb-skipWaiting-update-again?expand=1
(You basically save a reference to the ServiceWorkerRegistration from the initial call to wb.register(), and then use that registration.waiting as the target to postMessage() to. That avoids having to use any private symbols.)
Can you give that a try and if you confirm it behaves as you expect, I'll merge it into the docs?

@jeffposnick your suggestion worked fine for me.


Skip issue

Type
Crash/Error/Exception
Version
Last versión (25/11/2024)
Description of the bug
The Game crash (the music stops and the chart freezer) I can escape with esc
Screenshots/Video

The images aren't helpful at all.
Please send your logs.

https://github.com/user-attachments/assets/12863fcb-1771-4659-bf3f-3b6bb1917c1a
Like this?

This is even less helpful...
I asked tor logs.

Like how it happends?

Settings > General > Export Logs

Closing because of inactivity.


Wrong Compute Instance Type in Version 2.9.1 CFN Stack Parameter List

AWS ParallelCluster version [e.g. 2.9.0]: 2.9.1
Cluster Configuration:

[cluster AZ-a]
key_name = oracle
base_os = alinux2
master_instance_type = r5.24xlarge
compute_instance_type = c5n.18xlarge
placement_group = DYNAMIC
vpc_settings = AZ-a
master_root_volume_size = 3000
compute_root_volume_size = 30
initial_queue_size = 1
maintain_initial_size = true
max_queue_size = 1
fsx_settings = fs
ebs_settings = gp2
ec2_iam_role = EC2-Cluster-Generation
post_install = [redacted]
s3_read_resource = [redacted]
scheduler = slurm
disable_hyperthreading = true
enable_efa = compute
cw_log_settings = ParallelCluster
#cluster_type = spot
#spot_price = 1.50

[vpc AZ-a]
vpc_id = [redacted]
master_subnet_id = [redacted]
use_public_ips = false
vpc_security_group_id = [redacted]

[fsx fs]
shared_dir = [redacted]
storage_capacity = 14400
imported_file_chunk_size = 1024
import_path = [redacted]
deployment_type = SCRATCH_2

[ebs gp2]
shared_dir = /shared
volume_type = gp2
volume_size = 3000

[cw_log ParallelCluster]
enable = false
retention_days = 14

[aliases]
ssh = ssh {CFN_USER}@{MASTER_IP} {ARGS}

Bug description and how to reproduce:
When creating a cluster from command line (pcluster create) with the above configurations, the compute_instance_type is not being recognized by the main CloudFormation stack during the spin-up process and is set to the default, t2.micro. We have verified this by viewing the status of the CloudFormation stack of the cluster in the AWS console. The "Parameters" tab of the main stack shows the compute instance type as t2.micro rather than c5n.18xlarge - see the attached screenshot.
We have also attempted to re-write our cluster configurations to use the [queue] and [compute_resource] sections with a single queue and compute resource since we are using slurm as our scheduler. The compute instance type still defaulted to t2.micro rather than capturing the instance_type from the [compute_resource] section.
This does not seem to impact the actual instance type coming up, however, as the instance type in being created via EC2 console shows the correct type, c5n.18xlarge. Just a rather confusing bug that made it seem that even though we requested c5n.18xlarge, the stack made it seem like we were bringing up t2.micro.
Additional context:
Screenshot:

Following up on this - it also looks like the EFA parameter from the main stack (EFA) also only takes "NONE" even if enable_efa = compute in the configurations.

Hi, @stefan-maxar.
What you're observing here is a consequence of a change we made in v2.9.0 to the cluster configuration model for slurm clusters, in order to add support for heterogeneous instance types.

We have also attempted to re-write our cluster configurations to use the [queue] and [compute_resource] sections with a single queue and compute resource since we are using slurm as our scheduler. The compute instance type still defaulted to t2.micro rather than capturing the instance_type from the [compute_resource] section.

This is expected. Starting in 2.9.0, configuration files specifying slurm as the scheduler and using the 'old model' are converted internally to the same representation used for configuration files using slurm as the scheduler and using the 'new model' (queues, compute_resources, etc.).

This does not seem to impact the actual instance type coming up, however, as the instance type in being created via EC2 console shows the correct type, c5n.18xlarge. Just a rather confusing bug that made it seem that even though we requested c5n.18xlarge, the stack made it seem like we were bringing up t2.micro.

This is because the ComputeFleetHITSubstack doesn't use any of these parameters. It's generated dynamically by the CLI and then uploaded to ${ResourcesS3Bucket}/templates/compute-fleet-hit-substack.rendered.cfn.yaml, where ResourcesS3Bucket is set to the value of the CFN parameter by the same name. The data used to generate the template can be found in the same bucket at the key configs/cluster-config.json. Here's what that object contained for a cluster I created using a similar config as yours:
{
  "cluster": {
    "label": "AZ-a",
    "scaling": {
      "label": "default",
      "scaledown_idletime": 10
    },
    "default_queue": "compute",
    "queue_settings": {
      "compute": {
        "compute_type": "ondemand",
        "enable_efa": true,
        "disable_hyperthreading": true,
        "placement_group": "DYNAMIC",
        "compute_resource_settings": {
          "default": {
            "instance_type": "c5n.18xlarge",
            "min_count": 1,
            "max_count": 1,
            "initial_count": 1,
            "spot_price": 0,
            "vcpus": 36,
            "gpus": 0,
            "enable_efa": true,
            "disable_hyperthreading": true,
            "disable_hyperthreading_via_cpu_options": true
          }
        }
      }
    },
    "disable_cluster_dns": false
  }
}

You'll notice that enable_efa is true and instance_type is set to the correct value based on the config.
All that said, sorry about the confusion. Did this break some automation you had built on top of the stack's CFN paramters?

Yes, it did - we had some logic based on those parameters. Specifically, detecting if EFA was enabled upon cluster spin-up in order to properly set some environmental parameters during our post-install procedures. Is the preferred method for pulling such details now to get the cluster information from S3 as in your example? From our end, it would be ideal for these to also be in the main CFN stack parameters, or removed completely from the CFN stack parameter list to avoid the confusion.

Yes, it did - we had some logic based on those parameters. Specifically, detecting if EFA was enabled upon cluster spin-up in order to properly set some environmental parameters during our post-install procedures.

Sorry about that. We don't promise to avoid breaking changes on the CFN parameters/outputs, but we try to avoid it whenever possible because we're aware that users such as yourselves treat it as a kind of API. Unfortunately the configuration model for multiple queues, each of which potentially contains multiple instances types, doesn't map to the existing CFN parameters in the same way the single compute instance type configuration model does.

Is the preferred method for pulling such details now to get the cluster information from S3 as in your example?

Yes, for clusters using slurm as the scheduler.

From our end, it would be ideal for these to also be in the main CFN stack parameters, or removed completely from the CFN stack parameter list to avoid the confusion.

Those parameters are still required for the other supported schedulers, so we can't remove them.

I'm going to close this because I believe we've covered the root cause of your issue.
If you think there's more to cover here, please re-open and we'll do so.

@tilne Going to re-open this to provide some more feedback now that 2.10.0 is released. Since we use post-install scripts to prepare our runtime environment (create/update .bashrc files, etc.) its useful to have some of the pertinent cluster configurations (e.g., is EFA enabled?) housed somewhere that won't change ParallelCluster version to version. Our current logic uses the /etc/parallelcluster/cfnconfig file (sourced in post install) combined with describing the stack by the stack name defined the that cfnconfig file. An example of determining if EFA is enabled below.
In versions 2.8.X - grabbing if EFA was enabled was a simple one-liner:
efa_parameter=$(aws cloudformation describe-stacks --stack-name $stack_name --region $cfn_region | jq -r '.Stacks[0].Parameters[] | select(.ParameterKey == "EFA") | .ParameterValue') || exit 1

Which evolved in 2.9.X to:
stack_s3=$(aws cloudformation describe-stacks --stack-name $stack_name --region $cfn_region | jq -r '.Stacks[0].Parameters[] | select(.ParameterKey == "ResourcesS3Bucket") | .ParameterValue') || exit 1

aws s3 cp s3://${stack_s3}/configs/cluster-config.json . || exit 1

efa_parameter=$(jq -r '.cluster.queue_settings[].enable_efa' cluster-config.json)

Which now, changed again to accommodate 2.10.0:
stack_s3=$(aws cloudformation describe-stacks --stack-name $stack_name --region $cfn_region | jq -r '.Stacks[0].Parameters[] | select(.ParameterKey == "ResourcesS3Bucket") | .ParameterValue') || exit 1

resource_s3=$(aws cloudformation describe-stacks --stack-name $stack_name --region $cfn_region | jq -r '.Stacks[0].Parameters[] | select(.ParameterKey == "ArtifactS3RootDirectory") | .ParameterValue') || exit 1

aws s3 cp s3://${stack_s3}/${resource_s3}/configs/cluster-config.json . || exit 1

efa_parameter=$(jq -r '.cluster.queue_settings[].enable_efa' cluster-config.json)

So in a matter of 3 releases, an API-like one-line command with one point of failure becomes a series of API-like transactions with multiple points of failure (need for CloudFormation, S3). Given that each evolution of ParallelCluster tends to change how these parameters are defined and where they are housed, I'd like to work with you and the team to come up with a way that houses these relevant parameters in a manner that is not impacted release-to-release (unless intentionally so) and that is more readily transparent so that we downstream can leverage them in our logic. A lot of what we do is automated cluster spin-up/down, so we rely heavily on logic built around cluster configurations.
Perhaps these parameters are all put into the /etc/parallelcluster/cfnconfig file that has been around since the early days (and prior to) ParallelCluster. Or perhaps, a dynamoDB stores all the relevant cluster configuration parameters. Just throwing some ideas out there - hopefully we can find a happy middle ground that works for all users!
Thanks! Stefan


Cloudflare - Access Denied

Hi there,
First of all - huge thanks for creating this service - it's amazingly useful..
A few colleagues and I recently started receiving the following notifications when using images.weserv.nl:
Error 1006 Ray ID: 3fbb9e790382850e • 2018-03-15 02:41:05 UTC
Access denied
What happened?
The owner of this website (weserv.nl) has banned your IP address (203.174.xxx.xxx).

We work in the same building and share the same IP, so perhaps Cloudflare was being particularly cautious.
In any case, I was wondering if there is an ability to whitelist domains/hosts to lower the chance of these access denied errors - especially seeing as weserv doubles as a CDN/image cache.
Of course our last option would be to clone the project and deploy our own instance - but I thought I'd check with you guys first :)
Cheers!

Please see https://github.com/andrieslouw/imagesweserv/issues/83
If needed, we could make an exception for your IP-address, but I would like to know a rough estimation of usage, to check if our servers will be able to cope.

Thanks for the quick reply @andrieslouw!
We have an Instagram style website that loads 24-72 thumbnails per page (and there are lots of pages).
We generate thumbnails in a JIT fashion rather than in batches - and since the requests are coming from our users' browsers - I don't really have a specific IP or IP-range to provide.
I look forward to hearing from you - although I anticipate that there is probably nothing you can do here since weserv is a free public service (and you've graciously provided the source code too).
Cheers!

@bberak : What we can do is whitelist the IP-address of your office, so testing & development from your side would be unhindered and unlimited. Let me know if this would help you.
Unfortunately we're uncomfortable with removing the restriction of 700 images per 3 minutes per IP-address for all users/visitors of our public service, if your users would stay below this figure (~4 images/second) it could work.
You're always free to use the source-code, and we're always willing to assist in code and/or infrastructure related questions. I hope our BSD 3-clause license provides you with all the freedom you'd need in your product/application.

Thanks @andrieslouw, that totally makes sense.
BSD-3 should work just great - we'll look to roll out our dedicated weserv service asap. If you could whitelist our office IP in the interim - that would indeed be a huge help (<IP_ADDRESS>).
Thanks so much for the assistance, and source code :), really appreciate it.
Kind Regards.

@bberak : Whitelisted as requested, have fun!

Epic, huge thanks @andrieslouw!


.NET generation needs to use full type names for reused names cross-construct.

Names can be re-used across packages. Full type names need to be used to protect against naming conflicts.
See #786

The generated Java code uses fully qualified names for everything... Should the C# generator do the same?

The C# Generator attempts to detect whether a fully qualified name is necessary. See SymbolMap. I would start there when searching for the root cause.
Also, should this be moved to the jsii repo?

@mpiroc you're absolutely right - I've created awslabs/jsii#252 to track this. Resolving here.


Development cockpit

Moved the cockpit to a non-webpack package, working inside the threebot

This PR is too big and very hard to review, with a mix of actual changes, builds and cleanups.
IMHO, it's better to split these types of changes on multiple PRs later.

As @rkhamis stated, the base for this one can be https://github.com/threefoldtech/jumpscaleX_threebot/pull/389.

@tobiaschielens I rebased this PR on #389, can you please resolve these conflicts too?


Public repo not navigable by anonymous user

Hi,
I created a repo with public access.
For anonymous user is possible to see the main page of the repo, for example http://mydomain/johndoe/johndoerepo but non to navigate through. -> request for log in.

What the value of https://github.com/gogits/gogs/blob/master/conf/app.ini#L58 in custom/conf/app.ini?

Permalink to the version back then: https://github.com/gogits/gogs/blob/62d23e91541550d0478c4884696e918a0e818b4f/conf/app.ini#L58


Can we create nested models in one go?

If I want to create multiple models in one go, can I do so?
For example, I have a Customer that has a Contact associated with it.
export default (sequelize, DataTypes) => {
  const Customer = sequelize.define('customer', {
    id: {
      type: DataTypes.INTEGER,
      autoIncrement: true,
      allowNull: false,
      primaryKey: true
    }
  }, {
    classMethods: {
      associate() {
        const models = sequelize.models;
        Customer.hasOne(models.contact);
      }
    },
    tableName: 'customers'
  });
  return Customer;
};

I run sequelize's associations while importing the models, like so
Object.keys(db)
    .map(name => db[name])
    .filter(model => model.associate)
    .forEach(model => model.associate());

sequelize.sync();

Finally, I have the customer service defined like this
class CustomerSvc extends DBService {
  constructor() {
    super({
      Model: db.customer
    });
  }

  create(data, params) {
    return super.create(data, Object.assign({}, params, { sequelize: { include: [db.contact] } }));
  }
}

export default function() {
  return this.use('/customers', new CustomerSvc());
}

Now, the problem that I am stuck on is creating a contact along with the customer in one go.
For example,
POST /api/customers
{
  "contact": {
    "firstName": "Test",
    "lastName": "Test"
  }
}

I want this to create the contact if it doesn't exist, and fetch and use a contact if the contact ID is passed. But what feathers is doing is only running the query to create the customer without the contact.
This is what I see in the logs.
Executing (default): INSERT INTO "customers" ("id","createdAt","updatedAt") VALUES (DEFAULT,'2017-03-21 14:43:48.195 +00:00','2017-03-21 14:43:40.187 +00:00') RETURNING *;

Please advise on the best way to approach this problem.

currently that does not work with feathers-sequelize. But you can use an after hook to handle this after creating the customer. The actual "findOrCreate" logic you want to have is not there as well. Therefore you either do it yourself via 2 api calls or you write your own service which itself is directly using the sequelize model in its own create method. But tbh i would just first query, then create and with the after hook create the customer.

Okay. Well I'm going to hack around a bit on this. Will revert with some code once I manage to do something here.


[FEAT]: Enhance User Roles to Allow Workspace Creation and Management

What would you like to see?
Description:
Currently, the initial roles in the system are defined as follows:
Admin: Full access to the entire system.
Manager: Can view all workspaces and manage all properties except for settings related to LLM, Embedder, and Vector database.
Default: Can only send chats to workspaces they are explicitly added to. Cannot see or edit any workspaces or system settings.
We propose an enhancement to the Default role (or user role) to enable the following functionality:
Proposed Feature

Allow Workspace Creation:
Users with the Default role should be able to create a new workspace.

Automatic Role Upgrade to Manager for Created Workspaces:
Once a user creates a workspace, they automatically become the Manager of that workspace. This would grant them the ability to:

Add other users to the workspace.
Manage the workspace's properties (excluding system-level settings such as LLM, Embedder, or Vector database configurations).

Collaboration Facilitation:
This feature would empower users to form and manage their own teams, promoting collaborative efforts without requiring intervention from higher-level roles (e.g., Admin).

Benefits
Increased autonomy for users to organize their work.
Reduced reliance on Admins for workspace setup and team management.
Improved scalability as teams can self-organize without bottlenecks.
Implementation Considerations
Ensure that the user's management permissions are limited to the workspace they create.
Provide Admins with the ability to oversee and manage these new workspaces if needed.
Update the UI to include the option for users to create workspaces easily.
We believe this feature will significantly enhance the usability and scalability of the platform. Let us know if you need further clarification or additional details!
Thank you for considering this feature request.

https://github.com/Mintplex-Labs/anything-llm/issues/1787


Fix ELBv2 port, and target group retrieval

Fix ELBv2 port retrieval, by instead returning the listener port on the load balancer (was returning the target group port, which is irrelevant)

Also, fix missing paging over target groups by creating two new helper functions.  Previously, only the first 400 target groups were being retrieved.  Unfortunately there doesn't seem to be a more efficient way to do this than looping through all target groups, though suggestions are welcome - API docs are here: https://docs.aws.amazon.com/sdk-for-go/api/service/elbv2/#DescribeTargetGroupsInput

Is getAllTargetGroups getting called for every registration? I'm not sure how to get around the 400 limit, i've seen other aws api that have filter object, usually that allow finer control of the returned records, this api doesnt seem to offer that.

Yeah, it has to be called each time a container starts, if the ELBv2 reg is turned on.  It's a bit annoying - the Target structs don't have an associated TargetGroupArn.  So although I know what the targets are, and can filter them by instanceID/port, I can't then use the target to find the target group it's associated with.

There was a string comparison bug which I finally tracked down to comparison of two pointers instead of underlying values. I've fixed this now, seems to be working OK on the registrator:46


Use Own data - Cognitive search is AI Search

Module: 06
Lab/Demo: 06
Fixes # .
In the instructions AI Search is called Cognitive Search but the UI of the portal has the right name (AI Search)
Changes proposed in this pull request:

Change all the occurrences of Cognitive Search with AI Search

thanks for the name update!


License?

A license is required to allow people to use your code, it tells them what they can't / can do. I recommend the GPL v3 or the MIT. https://choosealicense.com/ can help.

Good call. Licensing it under MIT


func CheckSignatures

Codecov Report
Patch coverage: 100.00% and project coverage change: +0.02% :tada:

Comparison is base (b1467c0) 94.47% compared to head (45f56b1) 94.50%.
Report is 2 commits behind head on main.

:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.
Additional details and impacted files
@@            Coverage Diff             @@
##             main     #256      +/-   ##
==========================================
+ Coverage   94.47%   94.50%   +0.02%
==========================================
  Files          14       14
  Lines        6338     6366      +28
==========================================
+ Hits         5988     6016      +28
  Misses        282      282
  Partials       68       68

Files Changed
Coverage Δ

func.go
97.67% <100.00%> (+0.28%)
:arrow_up:

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


DOCS: standards page

Add a page under docs/ that lists all the standards implemented by Veraison with links to the relevant documents in their SDO's tracker.

This issue is moved to documentation repository: Please see: https://github.com/veraison/docs/issues/22


Fix accessibilityState overwriting view's disabled state on Android

Summary
While I was working on rewriting react-native-slider to Fabric I found a weird bug that prevented the slider to be set as disabled (to be exact: call the method slider.setEnabled(false). As it turned out the accessibilityState (with value: accessibilityState={{disabled: true}} prop occurred after the enabled={false} prop that I was passing to the slider, which lead to both of this props overwrite each other.
Handling of accessibilityState props inside view leads to always overwriting the enabled prop to true (even if we explicitly set it to {disabled: false}.
Workaround for this was to reorder the props, so that the accesibilityState occur before disabled, but I think it's better to not set view.setEnabled(true) if we are passing a disabled property.
Changelog
[Android] [Fixed] - Fix accessibilityState overwriting view's disabled state on Android
Test Plan
Change order of props inside native component implementation (that disabled occurs before accesibilityState). For example: Libraries/Components/Slider/Slider.js

Video showing the bug in RNTester (using Switch component)
https://user-images.githubusercontent.com/52801365/181287547-964f50e2-55dc-450f-b413-0d1c14d4bb83.mp4

@NickGerleman I've added your suggested fix, and all checks have passed. Can you take a look again?

      <Switch
        disabled={true}
      />

Will this be fixed in version 0.69? I found that the disabled property of the switch component doesn't work on Android is it related to this issue?


[Enhancement] Twitch.tv Emotions

Add twitch tv emotions
Can i make a pull request?

Omg so many help wanted.
When i got time i'll work on some.

Helping out would be much appreciated. But I'm not sure about twitch.tv emojis, maybe we should start with the new emoji standard and progress from there. :relaxed:

Ok.
i'm big fan of twitch.tv
That's why
https://twitchemotes.com/


Error in Dev:

Upgraded to SanityPress 5.4.0
Ran yarn install and yarn run dev:turbopack and received the error below.  Deleted .next and node_modules and tried again. Same error.
Build Error
Next.js (15.1.0) (Turbopack)
Failed to compile
./src/sanity/lib/fetch.ts:4:1
Ecmascript file had an error
2 | import { token } from '@/sanity/lib/token'
3 | import { dev } from '@/lib/env'

4 | import { draftMode } from 'next/headers'
| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
5 | import { defineLive, type QueryOptions } from 'next-sanity'
6 | import type { QueryParams } from 'sanity'
7 |

You're importing a component that needs "next/headers". That only works in a Server Component which is not supported in the pages/ directory. Read more: https://nextjs.org/docs/app/building-your-application/rendering/server-components
This error occurred during the build process and can only be dismissed by fixing the error.

@Brettkgamble Looks like this is more of a Next.js error, judging from the provided error message. Looks like you are young the pages/ directory rather than the app/ router.

Right....but no. I have made no changes to your code at all. To me I am
thinking it is a Sanity issue....
On Tue, Dec 17, 2024, 5:23 p.m. Mitchell Christ @.***>
wrote:

@Brettkgamble https://github.com/Brettkgamble Looks like this is more
of a Next.js error, judging from the provided error message. Looks like you
are young the pages/ directory rather than the app/ router.
—
Reply to this email directly, view it on GitHub
https://github.com/nuotsu/sanitypress/issues/41#issuecomment-2549976077,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ACZKYXKH6DNGYCRSJZHMGS32GC6BHAVCNFSM6AAAAABTXFZ4L6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNBZHE3TMMBXG4
.
You are receiving this because you were mentioned.Message ID:
@.***>

Can you please try adding 'use server' at the top of your src/sanity/lib/fetch.ts file? (This has been a new addition since updating to Next.js 15.1)
And make adjustments to your file to match the latest version of this file in SanityPress v5.4.0:

https://github.com/nuotsu/sanitypress/blob/main/src/sanity/lib/fetch.ts#L1

The suggested changes worked.  FYI....this issue was due to my way of updating my code base which somehow meant I missed a couple of files from 5.4.0.  The changes you suggested worked with another minor change in the import of Groq in queries.ts.
I appreciate your assistance and this issue can be closed.  I will make sure I get better at this, fork the repo, pull updates from main rather than unpack the zip......

I'm glad that fixed it! I will work to make better documentation on the upgrading process to avoid future mishaps like this! Thanks again for reporting this 🖤