Using SDK with Next.js and making Amplitude global

Summary
Hi, I am looking into implementing this SDK on my Next.js project as it is server side rendered.
The documentation isn't clear, so I am unsure on how to actually get started, on my app.tsx I want to init amplitude and have it available on all pages and components.
import '../styles.css';
import React from 'react';
import { ProvideAuth } from 'utils/auth';
import * as Amplitude from '@amplitude/node';

import Layout from 'components/Layout';

type Props = {
  Component: React.ElementType;
  pageProps: React.Props<unknown>;
};

let client = Amplitude.init(process.env.AMPLITUDE_API_KEY)

export default function MyApp({ Component, pageProps }: Props) {
  // The context is provided to the user so the userCtx is accessible anywhere with useContext hook.
  return (
    <ProvideAuth>
      <Layout title="OWNRS" description="">
        <Component {...pageProps} />
      </Layout>
    </ProvideAuth>
  );
}

With the above, it is not initialised, as I do not use client for anything, can I simply do Amplitude.init(process.env.AMPLITUDE_API_KEY) if not, how can I make this global?
With the client side SDK, I could init on the index.js and use amplitude.getInstance() to log an event
My question is, do I need to create a utils file that does the following
import * as Amplitude from '@amplitude/node';
const amplitude = Amplitude.init(process.env.AMPLITUDE_API_KEY);
export default amplitude;

and import it on every page, then log events?
import amplitude from 'utils/amplitude'

amplitude.logEvent({
  event_type: 'Node.js Event',
  user_id<EMAIL_ADDRESS>  location_lat: 37.77,
  location_lng: -122.39,
  ip: '<IP_ADDRESS>',
  event_properties: {
    keyString: 'valueString',
    keyInt: 11,
    keyBool: true
  }
});

How can I make this globally available within my app so that way data can be logged?

Hi @bobthebuilder1900 ! I think the pattern you have with having is exported seems solid. I was wondering what issues you were encountering with the JS SDK for server side-rendered react?
If the JS SDK also works, you could also consider using [https://github.com/amplitude/react-amplitude](our react sdk) which wraps the JS SDK and provides useful helper components. You could also consider copying its pattern for the Node SDK and inserting the initialized node client into a top component of the React tree into the context and using context providers as necessary to fetch it within your components.

The JS SDK does not work with server side rendered applications, as it relies heavily on accessing window.
Looking at the events that the node sdk sends, I am not sure I can use it as it sends the platform as Node.js and I won't be able to get devices or "Real" platforms such as Windows, Mac and Linux or browser usage.
The react amplitude sdk first paragraph says "react-amplitude is not an officially supported Amplitude SDK or library."

@bobthebuilder1900 Apologies for the delayed response.

The react amplitude sdk first paragraph says "react-amplitude is not an officially supported Amplitude SDK or library."

We don't support it officially, but I think the pattern it has (and the community built amplitude-react-hooks, or just using one of those libraries) of injecting Amplitude into React's context might worthwhile to try for building a react application with Amplitude.

The JS SDK does not work with server side rendered applications, as it relies heavily on accessing window.

Unfortunately this is true,  and something we're looking into. It would however align better to your use case as it provides a better API for the web. Things you could consider as workarounds while we work to solve this:

deferring the loading of the amplitude JS SDK to componentDidMount
adding a fallback window/document object

Has this been solved yet? I'm running into the same problem using amplitude JS SDK on a NextJS project.

@hudsonhyunlim As a workaround I conditionally import and init amplitude only on the browser side like this:
 let amplitude: any;
 export const initAmplitude = () => {
   if (process.browser) {
     amplitude = require('amplitude-js');
     amplitude.getInstance().init('your-amplitude-code');
   }
 };

Then in my _app.tsx
useEffect(() => {
    initAmplitude();
}, []);

Then also wrap all other amplitude functions like the init:
export const setAmplitudeUserId = (userId: string) => {
  if (process.browser) {
    amplitude.getInstance().setUserId(userId);
  }
};

const amplitudeEvent = (name: string, params?: {}) => {
  if (process.browser) {
    amplitude.getInstance().logEvent(name, params);
  }
};

I personally use react-amplitude for Next.js pages, and @amplitude/node for APIs.

useEffect(() => {
initAmplitude();
}, []);

It works on next js. But somehow I get the following error
ReferenceError: window is not defined
    at C:\Users\MD\Desktop\webV2\node_modules\amplitude-js\amplitude.umd.js:1197:12
    at C:\Users\MD\Desktop\webV2\node_modules\amplitude-js\amplitude.umd.js:2:83
    at Object.<anonymous> (C:\Users\MD\Desktop\webV2\node_modules\amplitude-js\amplitude.umd.js:5:2)
    at Module._compile (internal/modules/cjs/loader.js:1085:14)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:1114:10)
    at Module.load (internal/modules/cjs/loader.js:950:32)
    at Function.Module._load (internal/modules/cjs/loader.js:790:14)
    at Module.require (internal/modules/cjs/loader.js:974:19)
    at require (internal/modules/cjs/helpers.js:92:18)
    at Object.amplitude-js (C:\Users\MD\Desktop\webV2\.next\server\pages\index.js:9193:18)

After reload automatically it works. Such a weird thing. Is anyone the same as me?

@MohamedJakkariya window is not defined usually means the code is being executed on the server and not the browser. You should wrap your code in:
if (process.browser) {
    // Your code here.
}

@desmondmc Thanks for your reply. By the way, I found my issue. I just try to access the amplitude before loading it into the window. I realized. So I fixed it.

Don't calls hooks inside conditions.
I think it should be like this.
useEffect(() => {
  if (router.isReady) {
      initAmplitude();
  }
}, [router.isReady]);

See also

https://reactjs.org/docs/hooks-rules.html#only-call-hooks-at-the-top-level


Redirect isAssociated to the consensus node

Problem
Currently, the mirror node does not consume the modularized services.  This means that new view functions which are redirected via eth_call do not work.
Solution
temporarily redirect calls to isAssociated to the consensus node.   Remove this change once mirror node can consume the modularized services code.
Alternatives
No response

Release planning decided that not doing this was low impact enough that it was not worth the effort at this time


Rock, Paper, Scissors game

A simple and fun game called "Rock, Paper, Scissors". This is a two-player game where each player selects one of three options: Rock, Paper, or Scissors. The rules are simple:

Rock crushes Scissors.

Scissors cuts Paper.

Paper covers Rock.

Hi there!
I am the Mentor of this project.
Although this repo is not part of Hacktoberfest 2024, we have some great alternatives for you. Welcome to SkillShow, a repository focused on skill enhancement!
Guidelines:

Please adhere to the existing guidelines.
No additional rules, thanks!
Check it out here: SkillShow.

Note: Start by creating an issue. Once it’s assigned to you, feel free to open a pull request (PR). Directly opening a PR will lead to an invalid label.
Looking forward to your contributions!

Thank you so much <3


Allow to "mute" the output of the Kafka topic creation command

The rhoas kafka topic create allows to specify the output of the command as YAML and JSON.
I was thinking that sometimes for automated tasks and avoid to pollute the console could be useful to "mute" the output, exiting ok if the topic was creating but without printing any representation of the topic info. Maybe an --output none could be enough.

I think we might only print one sentence for topic by default. Or use some output as suggested
As workarounds for now we offer users to use std and error stream pipes.
rhoas kafka topic create --name=test -y 2> /dev/null

I think we should also document this as it is not obvious pattern we use


apulse can't open playback device when alsaequal is used

I use alsaequal (https://aur.archlinux.org/packages/alsaequal/) to have system-wide alsa equalizer.
Configuration is simple:
$ cat .asoundrc
ctl.equal {
type equal;
}
pcm.plugequal {
type equal;
slave.pcm "plug:dmix";
}
pcm.!default {
type plug;
slave.pcm plugequal;
}
It doesn't work with apulse:
$ apulse firefox
[apulse] [error] do_connect_pcm: can't open playback device "default". Error code -1 (Permission deined)
[apulse] [error] do_connect_pcm: failed to open ALSA device. Apulse does no resampling or format conversion, leaving that task to ALSA plugins. Ensure that selected device is capable
of playing a particular sample format at a particular rate. They have to be supported by either hardware directly, or by "plug" and "dmix" ALSA plugins which will perform required
conversions on CPU.
I think that sample rate of a signal sent to equalizer doesn't matter. After equalizer does its job signal  is sent further to dmix which handles conversion.

$ APULSE_PLAYBACK_DEVICE=plugequal apulse firefox

Works for me.

until I did a system upgrade

Hmm.
@worldowner, @SoniEx2, have you tried to set "security.sandbox.content.write_path_whitelist" parameter (on about:config page) to "/dev/snd/"?

I did.
Right after the system upgrade, I was getting EACCES (-13 I think), then I set that, now I'm getting EPERM (-1)...

This seems to only happen with firefox...

It has to do with e10s.
Setting both browser.tabs.remote.autostart and browser.tabs.remote.autostart.2 to false in about:config makes audio work. But the thing is, you don't wanna do that.
So, how to make apulse work with e10s?

Added all these to security.sandbox.content.write_path_whitelist:
/dev/snd/,/usr/share/alsa/alsa.conf,/usr/share/alsa/cards/,/usr/share/alsa/pcm/,/etc/asound.conf,/usr/share/alsa/alsa.conf.d/,/usr/lib/alsa-lib/libasound_module_pcm_equal.so,/home/soniex2/.alsaequal.bin,/home/soniex2/.asoundrc

And it worked. Sadly no way to filter write path whitelist and read path whitelist...

Before sandbox Firefox had rw access to all the files that your user has. So it's still better. If your're concerned about your files just run Firefox in container. I run it in LXC and works fine.

Sadly no way to filter write path whitelist and read-only path whitelist so this risks my asoundrc...

@SoniEx2, as far as I understand, that particular sandbox in Firefox allows accesses to all files for reading. And you only need add paths which need to be writable to the exception list. So, maybe "/dev/snd/,/home/soniex2/.alsaequal.bin" would be enough?

Nope. I had to add my asoundrc or else it wouldn't work.

I would like to say that I'm in (very up-to-date) arch using dmix+alsaequal+plug and apulse works out of the box with latest firefox, no need to tweak any settings. Has anything changed since you last discussed about this?

Also notice alsa is not enabled https://git.archlinux.org/svntogit/packages.git/tree/trunk/PKGBUILD?h=packages/firefox.

@memeplex please visit about:support and tell me what you see under Application Basics -> Multiprocess Windows.

Sure @SoniEx2
Multiprocess Windows 	0/1 (Disabled by add-ons)

Sandbox
---
Seccomp-BPF (System Call Filtering)	true
Seccomp Thread Synchronization	true
User Namespaces	false
Content Process Sandboxing	true
Media Plugin Sandboxing	true
Content Process Sandbox Level	2

@memeplex sandbox doesn't work if multiprocess windows is disabled.

You're right @SoniEx2. It was an autoreload addon that was disabling multiprocess windows. Now that I have paused that addon I get not sound anymore. I have set the sandbox whitelist to

/dev/snd
/usr/share/alsa
/usr/lib/alsa-lib
/etc/asound.conf (not in my system anyway)
/home/carlos/.alsaequal.bin
/home/carlos/.asoundrc

but to no avail...

needs to be /usr/share/alsa/ and same for alsa-lib.

Ahh, ok, shame on me. By trial and error I concluded that I just need to add

/dev/snd/
/home/carlos/.alsaequal.bin

to get it working. In particular, there was no need of adding ~/.asoundrc.

Today I tried on Ubuntu Xenial:
ALSA lib dlmisc.c:254:(snd1_dlobj_cache_get) Cannot open shared library /usr/lib/x86_64-linux-gnu/alsa-lib/libasound_module_pcm_equal.so
[apulse] [error] do_connect_pcm: can't open playback device "default". Error code -6 (No such device or address)
The library exists:
$ ls /usr/lib/x86_64-linux-gnu/alsa-lib/libasound_module_pcm_equal.so
/usr/lib/x86_64-linux-gnu/alsa-lib/libasound_module_pcm_equal.so
Any ideas?

I currently get exactly the same two pulseaudio log lines when trying to load module-alsa-sink for an alsaequal device on 18.04.3. The library exists, ldd shows no missing libs and arch matches, so I have no idea why it doesn't load. It works from other alsa programs, like aplay and mpd.


NginxModuleTraceAsError` directive not working as expected in ngx_http_opentelemetry_module

Describe your environment:

Platform: Ubuntu 20.04.2 LTS
Nginx Version: 1.26.0
GCC Version: 9.4.0
Kernel Version: Linux 6.5.0-1020-aws
OpenTelemetry Module Version: Latest from the repository (webserver/v1.1.0)

Steps to reproduce:

Configure Nginx with the ngx_http_opentelemetry_module.
Set the NginxModuleTraceAsError directive to either ON or OFF in the Nginx configuration.
Start Nginx and observe the error logs.

What is the expected behavior?

When NginxModuleTraceAsError is set to ON, trace logs should appear in the error logs.
When NginxModuleTraceAsError is set to OFF, trace logs should not appear in the error logs.

What is the actual behavior?

Regardless of whether NginxModuleTraceAsError is set to ON or OFF, trace logs are always written to the error logs.

Error Log:
nginx: [error] mod_opentelemetry: ngx_http_opentelemetry_init: Starting Opentelemetry Module init
nginx: [error] mod_opentelemetry: ngx_http_opentelemetry_init: Registering handlers for modules in different phases
nginx: [error] mod_opentelemetry: ngx_http_opentelemetry_init: Opentelemetry Module init completed!
2024/06/05 06:59:04 [notice] 1#1: using the "epoll" event method
2024/06/05 06:59:04 [notice] 1#1: nginx/1.26.0
2024/06/05 06:59:04 [notice] 1#1: built by gcc 9.4.0 (Ubuntu 9.4.0-1ubuntu1~20.04.2)
2024/06/05 06:59:04 [notice] 1#1: OS: Linux 6.5.0-1020-aws
2024/06/05 06:59:04 [notice] 1#1: getrlimit(RLIMIT_NOFILE): 1048576:1048576
2024/06/05 06:59:04 [notice] 1#1: start worker processes
2024/06/05 06:59:04 [notice] 1#1: start worker process 27
2024/06/05 06:59:04 [notice] 1#1: start worker process 28
2024/06/05 06:59:04 [notice] 1#1: start cache manager process 29
2024/06/05 06:59:04 [notice] 1#1: start cache loader process 30
2024/06/05 06:59:04 [error] 27#27: mod_opentelemetry: ngx_http_opentelemetry_init_worker: Initializing Nginx Worker for process with PID: 27
2024/06/05 06:59:04 [error] 28#28: mod_opentelemetry: ngx_http_opentelemetry_init_worker: Initializing Nginx Worker for process with PID: 28
2024/06/05 06:59:04 [error] 29#29: mod_opentelemetry: ngx_http_opentelemetry_init_worker: Initializing Nginx Worker for process with PID: 29
2024/06/05 06:59:04 [error] 30#30: mod_opentelemetry: ngx_http_opentelemetry_init_worker: Initializing Nginx Worker for process with PID: 30
2024/06/05 07:00:33 [notice] 30#30: http file cache: /var/cache/contentful 136.043M, bsize: 512
2024/06/05 07:00:33 [notice] 1#1: signal 17 (SIGCHLD) received from 30
2024/06/05 07:00:33 [notice] 1#1: cache loader process 30 exited with code 0
2024/06/05 07:00:33 [notice] 1#1: signal 29 (SIGIO) received

Additional context:

This issue causes unnecessary error logs and can make it difficult to distinguish actual errors from trace logs.
The configuration directive NginxModuleTraceAsError does not seem to have any effect on the logging behavior.

Root cause:
static ngx_int_t ngx_http_opentelemetry_init(ngx_conf_t *cf)
{
  ...
    ngx_writeError(cf->cycle->log, __func__, "Starting Opentelemetry Module init");

The issue is not with NginxModuleTraceAsError, but more like ngx_writeError() used instead of ngx_writeTrace().

Related:

https://github.com/open-telemetry/opentelemetry-cpp-contrib/issues/401


CI on master is currently broken

Not sure how to ping that since the change (https://github.com/BinomialLLC/basis_universal/commit/62539278e10d106f52b9a05134ef3e8267b22a02) that introduced the failure wasn't associated with a PR. Haven't investigated the failure, just wanted to raise awareness somehow.

@richgel999 Would you be able to take a look? 🙏

yup - looking at it

all fixed - thanks!


QR Code support

Should be easy to view some bits of text on the page as QR codes to make it easy to scan it with mobile phones.
I'm thinking

BIP39 Seed
BIP32 Root Key
BIP32 Extended Key (xprv and xpub)
Address
Public Key
Private Key

Perhaps a good implementation might be anything selected (with no spaces in the selection) will show a qr code for the selected text in the top right of the screen.

See https://github.com/iancoleman/bip39/commit/e00964ccf7a556895784ed05f0fdec954f5558d5 - QR code shown on hover for certain bits of data
QR code shown for:

mnemonic
seed
root key
derived extended private key
derived extended public key
addresses
public keys
private keys


Imported subsite is not working

I export a subsite from a live system:
wp mu-migration export all subsite.zip --blog_id=2 --path=/var/www/html/wordpress --plugins --themes --uploads
I then import into a new (clean, multisite) Wordpress installation:
wp mu-migration import all  subsite.zip --new_url=mynewsite.com/wordpress/subsite --blog_id=2
When finished, the site appears in the list of sites in the Network Admin, but if I try to Visit Site or show the Dashboard, I get a connection timeout error in my browser.
One curious thing is that during the import, I see the following messages:
Extracting zip package...
Importing tables...
Warning: Something went wrong while running sed
Warning: Something went wrong while running sed
Warning: Something went wrong while running sed
Warning: Something went wrong while running sed
Warning: Something went wrong while running sed
Warning: Something went wrong while running sed
Warning: Something went wrong while running sed
Warning: Something went wrong while running sed
Moving files...
etc...
Any ideas on why this is not working? Anything I can try to help track down the issue? Note that the default site continues to work, and I can still access the Network Admin pages, just not my imported subsite.
p.s. this is a new Wordpress install, so I can easily delete Wordpress and database, and set it up again - takes me less than 5 minutes!

Should have mentioned - I am using Wordpress 5.3.

@derekPrivate it looks like the server you're running MU-MIgration either does not have sed or something is wrong with it.
Can you run this on your terminal and let me know the result?
echo "wp_" | sed "s/wp_/wp_5_/g"

% echo "wp_" | sed "s/wp_/wp_5_/g"
wp_5_
--
Derek

On 3 Dec 2019, at 12:19, Nícholas André<EMAIL_ADDRESS>wrote:
echo "wp_" | sed "s/wp_/wp_5_/g"

Are you running MU-Migration in a linux server?

I’m exporting on Linux and importing into a Mac. (Catalina, 10.5)
--
Derek

On 3 Dec 2019, at 12:28, Nícholas André<EMAIL_ADDRESS>wrote:
Are you running MU-Migration in a linux server?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/10up/MU-Migration/issues/70?email_source=notifications&email_token=ABU4OWDCODY3ANR4VSY3SMDQWZGFVA5CNFSM4JTHBFO2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEFZGOXQ#issuecomment-561145694, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABU4OWFEDKWE2XWAGGGZKGTQWZGFVANCNFSM4JTHBFOQ.

This CLI tool has no official support for Mac OS, but I guess it shouldn't be too hard to come up with a fix for Mac OS, sed works a bit different on Mac OS when compared to Linux and that's probably why the sed commands this tool run is not working for you.

This is where the sed commands run in case you want to try something: https://github.com/10up/MU-Migration/blob/master/includes/commands/class-mu-migration-import.php#L663
I'll see what I can find.

@derekPrivate Can you try replacing this line https://github.com/10up/MU-Migration/blob/master/includes/commands/class-mu-migration-import.php#L685 with this: sed -i'' -e '$sed_command' $filename

Ok that solved the sed error, but now I do not see my website at all!
Previously, I saw the sed errors, but my website did appear in the list of sites in my wordpress installation (but the site did not work!)
Now, I see no errors during the import, but my website does not now appear in the list of sites
--
Derek

On 3 Dec 2019, at 12:48, Nícholas André<EMAIL_ADDRESS>wrote:
@derekPrivate https://github.com/derekPrivate Can you try replacing this line https://github.com/10up/MU-Migration/blob/master/includes/commands/class-mu-migration-import.php#L685 https://github.com/10up/MU-Migration/blob/master/includes/commands/class-mu-migration-import.php#L685 with this: sed -i'' -e '$sed_command' $filename
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/10up/MU-Migration/issues/70?email_source=notifications&email_token=ABU4OWGI4E5AAUZQDDJRIADQWZIRHA5CNFSM4JTHBFO2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEFZICLA#issuecomment-561152300, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABU4OWCY7WGJTPOLU6GZWTDQWZIRHANCNFSM4JTHBFOQ.

Hello, the same sed error. I use WSL, only the site is not being sorted, here is the error ERROR 1050 (42S01) at line 25 in file: 'mu-migration1669197215/mu-migration-1090416661oneadvocate-eu.sql': Table 'wp_addonlibrary_addons' already exists , I tried deleting the entire site and tables in turn, etc, nothing it doesn't help. but this happens when I import to a multisite blog_id=2 if I import without blog_id, then everything works


Difficulty setting up retry settings with GoogleAdsClient

Kotlin 1.4.10, jvmTarget 11
Linux, Ubuntu 18.04
We're migrating one of our reports from ruby to java (well, ok...kotlin).
In implementing this,  I ran into a server error, which in ruby we'd retry.
Then, as I tried to set up retries via the java client, I ran into some weird inconsistencies.
Originally, I had (abbreviate):
        val gClient = GoogleAdsClient
                .newBuilder()
                .setCredentials(creds)
                .setDeveloperToken(devToken)
                .setLoginCustomerId(CG_MCC_ID)
                .build()

       val totalInserts = gClient.latestVersion.createGoogleAdsServiceClient().use { gServClient ->

etc.
However, the client I get from GoogleAdsClient.latestVersion.createGoogleAdsServiceClient did not appear to have a way to modify the GoogleAdsServiceSettings
So I ended up doing
GoogleAdsServiceClient.create(getDefaultRetrySettings(creds, headerProvider))  (where I create a settings builder and set everything in the getDefaultRetrysettings function)
But in order to do the latter, I had to implement a custom HeaderProvider to set the developer token and the login customer id.
Did I miss something in one of those two versions?
I'd expect to either be able to mutate the retry settings in the former, or to be able to set developer token and login-customer-id in the latter.
Thanks!
sean

Hey thanks for reporting. This is actually a known limitation of the GoogleAdsClient surface. We currently generate a default *Settings object for every client, though as you mention there is no way to override this while still using our client factory methods.
Can I ask which error code you're receiving and trying to retry? We may be able to add that to our list of retryable error codes so that it's retried by default. Did you also want to configure the exponential backoff params?

We were also configuring the exponential backoff params.
The error code in question was just SERVER_ERROR (from memory, but you get
the idea), so it should've been retried but I don't believe it was.
It was transient, but the failure happened fast enough I really don't think
it went through retries.
We run a batch system, so we have retry settings that are probably much
longer than the defaults?
On Fri, Oct 23, 2020 at 6:01 AM Nick Birnie<EMAIL_ADDRESS>wrote:

Hey thanks for reporting. This is actually a known limitation of the
GoogleAdsClient surface. We currently generate a default *Settings object
for every client, though as you mention there is no way to override this
while still using our client factory methods.
Can I ask which error code you're receiving and trying to retry? We may be
able to add that to our list of retryable error codes so that it's retried
by default. Did you also want to configure the exponential backoff params?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/googleads/google-ads-java/issues/359#issuecomment-715239301,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAKWJV7DYR7C5S5MF6SQGNDSMFH5XANCNFSM4S3Q4DHA
.

Hmm, I don't know if we'd want to make that retryable for all API clients.
So we are planning some work here to expose the service-level settings object in the client factory, however that's not going to be ready imminently.
I think if you want to use the built in retry behavior, the solution you posted is really the best thing for the time being (as ugly as it is).
I would not recommend this though, and would just instead implement a simple retrying exponential backoff.
@devchas our resident timeouts + retry expert in case there's anything you'd like to add.

Thanks!
Incidentally, your github settings seem...weird? I can't comment or react
on this from github, but I can respond to the emails I'm getting.
On Fri, Oct 23, 2020 at 11:59 AM Nick Birnie<EMAIL_ADDRESS>wrote:

Hmm, I don't know if we'd want to make that retryable for all API clients.
So we are planning some work here to expose the service-level settings
object in the client factory, however that's not going to be ready
imminently.
I think if you want to use the built in retry behavior, the solution you
posted is really the best thing for the time being (as ugly as it is).
I would not recommend this though, and would just instead implement a
simple retrying exponential backoff.
@devchas https://github.com/devchas our resident timeouts + retry
expert in case there's anything you'd like to add.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/googleads/google-ads-java/issues/359#issuecomment-715429762,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAKWJV6ALI4A4SYRRA557YTSMGR5HANCNFSM4S3Q4DHA
.

Test

Can you share a screenshot of the reply box perhaps? Since you need to email it, please use imgur.com (or similar) thanks.

https://imgur.com/a/21vKJvJ
The reaction wasn't working at  all earlier, now I can select a reaction
but it doesn't post.
On Fri, Oct 23, 2020 at 12:46 PM Nick Birnie<EMAIL_ADDRESS>wrote:

Can you share a screenshot of the reply box perhaps? Since you need to
email it, please use imgur.com (or similar) thanks.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/googleads/google-ads-java/issues/359#issuecomment-715454276,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAKWJV7C43FFVF7J2K74USLSMGXNBANCNFSM4S3Q4DHA
.

As Nick mentioned, we have some things in the works to fix this long term. For now, agree which Nick that your best option is to implement exponential backoff.

This is now fixed in the upstream library and will be available in the next release.
Usage is: GrpcCallContext.createDefault().withRetrySettings(RetrySettings.newBuilder().build())
In the meantime you can override the version of GAX to 1.63.0 which contains these changes.
    <dependency>
      <groupId>com.google.api</groupId>
      <artifactId>gax</artifactId>
      <version>1.63.0</version>
    </dependency>

@devchas Could you add a quick set of docs to this page please?

Docs added.


merged order wrong?

I thought this package would be a very nice addition to a mechanism I have in place to specify settings/configurations...but it seems the order in which merged files end up in the final result are giving not the results I would desire.
My settings syntax is as follows:
block:
- rule1:
   setting a
   setting b
   ....
- rule2:
  setting c
  ...

The rules determine on what settings get applied. It is legal to list the same rule multiple times (that is why it is an array). If a setting is repeated, the 'last one wins' which feels most intuitive and follows what yaml does.
However in the following example:
# base.yaml
---
blockX:
- playground:
    macros:
      M_BASE: ja
      M_REPLACE: to_be_replaced
...

# settings.yaml
---
extends:
  - 'base.yaml'
blockX:
- playground:
    macros:
      M_DERIVE: ja
      M_REPLACE: replaced
...

Gives as result:
---
blockX:
- playground:
    macros:
      M_DERIVE: ja
      M_REPLACE: replaced
- playground:
    macros:
      M_BASE: ja
      M_REPLACE: to_be_replaced
...

In which it is unfortunate that the extended base comes last in the list, as a result when I process the file the macros result in:
M_DERIVE: ja
M_BASE: ja
M_REPLACE: to_be replaced         ---> should haven bee 'replaced'
Would it be difficult to put the merged list in the order from base --> derived? (maybe optional)

BTW: this seems to have a similar cause as #5

Actually...the example you show on the main page, is not working as written. The outcome I get is:
---
data:
  name: Mr. Superman
  age: 134
  favorites:
  - Raspberrys
  - Bananas
  - Apples
  power: 2000

As you can see some of the items (especially the list of fruits) are in another order compared to the main page. Here they are in 'extensions last'
Probably, often this does not matter, but in my case the order of array entries means something.

Pull request #8 adds an option to yaml_extend to traverse the tree starting at the base class

@NicoLugil, thank you very much for your issue and pull request.
I would like to provide an option/fix for this requirement and will check your pull request soon.

Hi @NicoLugil,
i want to ensure to understand your problem exactly. Did you expect the following result in your example?
---
blockX:
- playground:
    macros:
      M_BASE: ja
      M_REPLACE: to_be_replaced
- playground:
    macros:
      M_DERIVE: ja
      M_REPLACE: replaced

Correct!
This is what my pull request gives if you use the option tree_traversal: :postorder
YAML.ext_load_file 'settings.yaml' gives:
{"blockX"=>   [{"playground"=>{"macros"=>{"M_DERIVE"=>"ja", "M_REPLACE"=>"replaced"}}},    {"playground"=>{"macros"=>{"M_BASE"=>"ja", "M_REPLACE"=>"to_be_replaced"}}}]}
YAML.ext_load_file 'settings.yaml', tree_traversal: :postorder   gives
{"blockX"=>   [{"playground"=>{"macros"=>{"M_BASE"=>"ja", "M_REPLACE"=>"to_be_replaced"}}},    {"playground"=>{"macros"=>{"M_DERIVE"=>"ja", "M_REPLACE"=>"replaced"}}}]}

Thank you very much for your reply and PR.
As i figured out, the PR
https://github.com/nangelovaTeladoc/yaml_extend/pull/1
Does fix your issue and addresses the multi-file inheritance precedence order as well.
So i prefer using that solution and hope you don't feel bad when i have to reject your suggested solution.

If it works then that is fine.
However could you run the more elaborate test I provided with a0, a1, ... first to make sure it does give the correct result?

The one thing I did like about my solution is the use of rubytree.
It as a first step builds a tree.
In the next step it traverses and merges the tree in the desired order.
Rubytree has multiple built-in traversal schemes. If you want to keep that flexibility you might consider having another look at this solution.
It should also fix the multi file order issue.

I will definitely add more test cases, especially on the subject of the merging order.
And I'll reconsider your remarks.


Coordination: the second high priority feature mentioned from our mentor Dave Fisher

Coordination of WeChat, GitHub and Apache ML.

I think that this OSSBot project has two cases to consider in resolving the Apache Way with the GitHub/WeChat modern way. - @dave2wave

With the v0.1 milestone, I believe we can send a message to the Wechat group already.
the GitHub coordination is related to #11
The Apache ML part can not be started until we get the Apache email address & list.

Can we use @kaiyuanshe.org as a starter before the ASF ML acquired?

ted: 这是第三个阶段要实现的内容，等实现和邮件打通后再讨论，目前暂不讨论


Does it work with ruby 2.1, 2.2, 2.3?

Celluloid::IO works on Ruby 1.9.3, 2.0.0, JRuby 1.6+, and Rubinius 2.0.

All support for ruby 2.0 has ended. Current version of Ruby is 2.3.1, so it's probably time to update this statement?

Thanks @jan, made the change. In the future, don't be shy about proposing changes you see needed... go ahead and skip right to posting a Pull Request with your idea of how it ought to be.


PR For #24: text alignment

In this issue we . . .
In this issue we will . . .

Updated the pp-plot legend to from Bootstrap Replicates -> Bootstrap Reps
Standardized the alignment of the textbox in both the pp-plot and crossings plots

Adding @jmshapir and @rcalvo12

@jmshapir


add afl-stop

based on afl-pause, kills the fuzzers belonging to a certain sync dir with SIGKILL instead of just sending SIGSTOP.
See https://github.com/bnagy/afl-launch/issues/2

Thanks! :)


Colors on map legend are black in IE something

Problem discovered with Ed Eads in APD

fixed. for ie10+


After save and reload the markings are not the same (incompatibility with Node Controller mod?)

Which IMT are you using?  Stable, BETA, BETA with Early Access
Stable 1.3
What computer OS are you using? (ex:  Linux (version), MACOS, Windows (version))
Windows 10 Pro x64
Describe the bug
I'm using IMT 1.3 together with Node Controller V2.0 [Beta] to make my highway lanes more realistic. They work together great, but if I quit the game, and later reopen my saved city, then the "Corner smoothness" (set in Node Controller) of the junctions is not applied to markings.
To Reproduce

Set "Corner smoothness" by Node Controller on a highway junction
Create markings with IMT
Save the game, and quit Cities Skylines
Open Cities Skylines, and reload the saved city

Expected behavior
The markings look the same as before.
Screenshots
Before saving and leaving the game:

After reloading the saved city:

Additional information
The markings are restored if I select the junction by Node Controller, because then the "marking points" gets updated.
The problem can be also in the Node Controller mod, but it's hard to judge, so I started here as the problem is with the markings.
I'm using TM:PE [Stable], not the [Labs] version, but I doubt that it has anything to do with this particular problem.

Is your simulation on pause? Have you tried pressing play?

Starting the simulation doesn't help.
But interestingly, if I quit to main menu, and load the saved game again, then it gets fixed.
Seems to be a kind of "initialization order" problem: When IMT is initialized first, then the Node Controller mod's "corner smoothness" is not applied yet, so the markings are still using the original coordinates. But if I load the city again, then the Node Controller mod is the first, thus the markings are placed correctly.

Closed without resolution? :(

@gaborposz It's Node Controller problem


Add apiregistration.k8s.io/* API to the default watching list of Kubernetes

What this PR does / why we need it:
Which issue(s) this PR fixes:
Fixes part of #2436
Does this PR introduce a user-facing change?:

NONE

/hold

/golinter fmt

/hold cancel

I am not sure whether GKE Autopilot is allowing this or not. But let's merge and check against it.
/lgtm

Way to go
/approve


Puppeteer Extensions (request handlers, custom methods, ...)

Hi Everyone!
I'm currently loving puppeteer and am using it daily! However while working with it - as with any product - it seems that my codebase is getting larger and larger making it quite hard to keep a correct overview 😊
Therefore I started using an abstraction layer on top of puppeteer called puppeteer-extra but am starting to think more and more that this should be in the official puppeteer repo for obvious extensibility reasons.
The most crucial parts that required extensibility for me while working with puppeteer are:

Request handlers -> I would love to create multiple request handlers that each do their own thing (e.g. blocking resources, waiting for XHR calls in a custom way, ...)
Custom methods -> I would love to add custom methods that allow me to for create simplified methods (e.g. clickAndWait, ...)

Is this something that was answered or thought about already? Would it make sense to start integrating extension possibilities within puppeteer? I'd love to hear your thoughts around this!

Thanks for this issue and sorry for the lack of replies. I'll leave request handlers to #6735 as that's an ongoing discussion.
RE custom methods, it's not something we've really thought about to be honest. On projects we have that use Puppeteer (we write DevTools e2e tests with Pptr, for example) we have a lot of custom helpers that take the page object in:
function clickAndWait5Seconds(page: Page) {
  ...
}

Whilst that isn't quite as nice as defining custom methods, it's a nice way to build up a library of helpers and means we don't have to add the ability to define custom methods into pptr itself. It also means a developer jumping between two projects that use Pptr won't have to remember which methods are custom vs baked into the library itself.

Thanks for this issue and sorry for the lack of replies. I'll leave request handlers to #6735 as that's an ongoing discussion.
RE custom methods, it's not something we've really thought about to be honest. On projects we have that use Puppeteer (we write DevTools e2e tests with Pptr, for example) we have a lot of custom helpers that take the page object in:
function clickAndWait5Seconds(page: Page) {
  ...
}

Whilst that isn't quite as nice as defining custom methods, it's a nice way to build up a library of helpers and means we don't have to add the ability to define custom methods into pptr itself. It also means a developer jumping between two projects that use Pptr won't have to remember which methods are custom vs baked into the library itself.


Sync eng/common directory with azure-sdk-tools for PR 2513

Sync eng/common directory with azure-sdk-tools for PR https://github.com/Azure/azure-sdk-tools/pull/2513  See eng/common workflow

/check-enforcer reset

/check-enforcer reset

/check-enforcer override


coreclr\bin\FSharp.Core.dll has TargetFrameworkAttribute "Profile7"

After a build coreclr, the file Release\coreclr\bin\FSharp.Core.dll contains a TargetFrameworkAttribute mentioning Profile7.  This seems unexpected.
Repro steps
Provide the steps required to reproduce the problem

build coreclr

ildasm Release\coreclr\bin\FSharp.Core.dll

Look at the TargetFrameworkAttribute

Expected behavior
A DLL with a TargetFrameworkAttribute mentioning something like netstandard or netcore or...
Actual behavior
A DLL with a TargetFrameworkAttribute mentioning Portable7
.custom instance void [System.Runtime]System.Runtime.Versioning.TargetFrameworkAttribute::.ctor(string) = ( 01 00 2A 2E 4E 45 54 50 6F 72 74 61 62 6C 65 2C   // ..*.NETPortable,
                                                                                56 65 72 73 69 6F 6E 3D 76 34 2E 35 2C 50 72 6F   // Version=v4.5,Pro
                                                                                66 69 6C 65 3D 50 72 6F 66 69 6C 65 37 01 00 54   // file=Profile7..T
                                                                                0E 14 46 72 61 6D 65 77 6F 72 6B 44 69 73 70 6C   // ..FrameworkDispl
                                                                                61 79 4E 61 6D 65 14 2E 4E 45 54 20 50 6F 72 74   // ayName..NET Port
                                                                                61 62 6C 65 20 53 75 62 73 65 74 )                // able Subset

Related information
master branch

I think this is the culprit: https://github.com/Microsoft/visualfsharp/blob/master/src/FSharpSource.targets#L233

Notes to self about how this repo builds F# CoreCLR stuff using MSBuild (from looking in FSharp.Source.targets):

When compiling CoreCLR stuff with MSBuild, we import both Microsoft.DotNet.BuildTools\...\Build.Common.Targets and Microsoft.Portable.FSharp.Targets.  I could imagine that's risky in the long run and that we need might a standard formula for this.

  <Import  Condition="'$(TargetFramework)'=='coreclr'" Project="$(BuildToolsDir)Build.Common.Targets" />
    ...
        <FSharpTargetsPath>..\Proto\$(protoCLIDir)\bin\Microsoft.Portable.FSharp-proto.Targets</FSharpTargetsPath>
  <Import Condition="'$(ProjectLanguage)' == 'FSharp'" Project="$(FSharpTargetsPath)"/>

In this repo, When compiling CoreCLR stuff with MSBuild, we set these, I'm not sure if it's needed but it feels like typical target files would need to set these or their future equivalents.

    <NuGetPackagesPath Condition="'$(NuGetPackagesPath)' == ''">$(FSharpSourcesRoot)\..\packages</NuGetPackagesPath>
    <PackagesDir>$(NuGetPackagesPath)\</PackagesDir>

    <NuGetToolPath Condition="'$(NuGetToolPath)' == ''">$(FSharpSourcesRoot)\..\.nuget\</NuGetToolPath>
    <NuGetConfigCommandLine>-ConfigFile "$(NuGetConfigFile)"</NuGetConfigCommandLine>

    <NugetRestoreCommand>"$(NuGetToolPath)NuGet.exe"</NugetRestoreCommand>
    <NugetRestoreCommand>$(NugetRestoreCommand) install</NugetRestoreCommand>
    <NugetRestoreCommand>$(NugetRestoreCommand) -OutputDirectory "$(NuGetPackagesPath)"</NugetRestoreCommand>
    <NugetRestoreCommand>$(NugetRestoreCommand) -Config "$(NuGetToolPath)NuGet.Config"</NugetRestoreCommand>

    <DnuRestoreCommand>"$(NuGetToolPath)NuGet.exe"</DnuRestoreCommand>
    <DnuRestoreCommand>$(DnuRestoreCommand) restore</DnuRestoreCommand>
    <DnuRestoreCommand>$(DnuRestoreCommand) -OutputDirectory "$(NuGetPackagesPath)"</DnuRestoreCommand>
    <DnuRestoreCommand>$(DnuRestoreCommand) -Config "$(NuGetToolPath)NuGet.Config"</DnuRestoreCommand>

There is this funky setting (maybe Paket would like this :) )
<!-- Current version of DNX does not support all semantics used in our packages,
     so we ignore the pre-calculation in the lock file and calculate asset applicability in the build task -->
<NuGetIngoreLockFile>true</NuGetIngoreLockFile>

I tried these settings in FSHarp.Source.targets and they seem to correct the problem, at least the attribute now looks as @enricosada assures me "dotnet cli" CoreCLR binaries look.
<!-- We're building netcore using the "portable" targets file right now, so: -->
<!--   - set the TargetFrameworkProfile because we have to. -->
<!--   - set the correct TargetFrameworkMoniker by hand. -->
<!--   - set the TargetFrameworkMonikerDisplayName to empty. -->
<!--   - set ImplicitlyExpandTargetFramework to stop msbuild being helpfull and referencing the dlls for the profile -->
<TargetFrameworkProfile>portable7</TargetFrameworkProfile>
<TargetFrameworkMoniker>.NETStandard,Version=$(TargetFrameworkVersion)</TargetFrameworkMoniker>
<TargetFrameworkIdentifier>.NETStandard</TargetFrameworkIdentifier>
<TargetFrameworkMonikerDisplayName>.NET Standard Profile $(TargetFrameworkVersion)</TargetFrameworkMonikerDisplayName>
<ImplicitlyExpandTargetFramework>false</ImplicitlyExpandTargetFramework>

However I don't know what the TargetFrameworkMonikerDisplayName should be or if it really matters

the .net cli generate this assemblyinfo files (on dotnet build )
dotnet-compile.assemblyinfo.fs
[<assembly:System.Runtime.Versioning.TargetFrameworkAttribute(".NETStandard,Version=v1.5")>]

dotnet-compile.assemblyinfo.cs
[assembly:System.Runtime.Versioning.TargetFrameworkAttribute(".NETStandard,Version=v1.5")]

ok, btw added https://github.com/dotnet/netcorecli-fsc/issues/7 to track empty attributes

Yeah the profile7 was a nasty hack to get the tooling to work a year ago.  I actually don't know what the right magic is these days but I will chat with Eric and find out.

I checked the latest and this attribute now has the correct value


only files and search bar is showing on the Activity Bar

VSCode Version: 1.19.1
OS Version: win-64 bit

Steps to Reproduce:

Just installed an extension Auto rename HTML tag,
After reloading I found that the debugging, git and extension tabs have vanished
Restarted after disabling all the extensions even installed vs code again but they didn't appear.
This is strange idk what to do

Reproduces without extensions: Yes

A duplicate of https://github.com/Microsoft/vscode/issues/40531 ?

FIXED!! thx for referencing


add official support for TIC-80

hi ... @oblerion had developed this = https://github.com/oblerion/ZeroBrane-Studio-with-TIC-80
maybe is a good time to talk with him and include this as official package for tic80, that have some minor bugs and may need some  adjusts to work properly

hello,
This is code recovered from a project abandoned by this author.
It needs to be updated to version 0.80 -> 1.1 of tic80.

Interpreter is fix and optimize now

thank you so much, especially considering you didn't wrote this software and you had "rescue it" from abandonment
i already thank you in the project page

Api is update and ver 1.1 is release


fix(client): Passing undefined _count in select

Description
As _count arg in select args is conditional it can be passed as undefined and in that case query fails. The expected behavior is that the query is executed as _count is not passed. This fix aims to accomplish that.
Related Issue

Issue: #24780

Changes Made

Added functions for desugaring UserArgs in case of select args
Make sure if _count: undefined is passed it is cleared from args
Added test that covers this use case

Screenshots (if applicable)
The error log looks like this.
const links = await prisma.link.findMany({
  select: {
    user: {
      select: {
        id: true,
        _count: undefined
      }
    }
  }
})
Unknown field at "user._count selection"

Engines that is being thrown.
[
  {
    "error": "Error in query graph construction: QueryParserError(ValidationError { kind: EmptySelection, message: \"Expected a minimum of 1 field to be present, got 0\", meta: Some(Object {\"outputType\": Object {\"name\": String(\"UserCountOutputType\"), \"fields\": Array [Object {\"name\": String(\"links\"), \"typeName\": String(\"Int\"), \"isRelation\": Bool(false)}]}, \"selectionPath\": Array [String(\"findManyLink\"), String(\"user\"), String(\"_count\")]}) })",
    "user_facing_error": {
      "is_panic": false,
      "message": "Expected a minimum of 1 field to be present, got 0",
      "meta": {
        "outputType": {
          "name": "UserCountOutputType",
          "fields": [
            {
              "name": "links",
              "typeName": "Int",
              "isRelation": false
            }
          ]
        },
        "selectionPath": [
          "findManyLink",
          "user",
          "_count"
        ]
      },
      "error_code": "P2009"
    }
  }
]

Checklist

[X] I have run the code and it works as expected.
[X] I have added tests that prove my fix is effective or that my feature works.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

Hi @igort99
we really appreciate your contributions, but argsMapper looks like a wrong place to do it for me.
JSON protocol serializer looks like a better and simpler place to do it. In particular this and this conditions needs to be adjusted to include explicitly undefined fields too.
Would you be interested in adjusting your PR this way? Thank you!

Thank you for your feedback and review. As this is my first contribution to Prisma, I was uncertain about the appropriate location for the sanitization. I will update the pull request to align with your suggestions and work on enhancing the tests as well.

Hi @SevInf ,
I have updated the PR to ensure that fields explicitly passed as undefined are included in select or include queries. The _count field was previously problematic, but I have added a specific condition to handle it. This ensures that _count is correctly included when explicitly set to undefined. For all other fields, passing undefined already functions as expected. While a general condition for field === undefined could be implemented, I opted for a targeted approach to avoid potential unintended consequences.


Model - Uniquify sources

Create Source methods and specs that produce reasonable results for

[ ] #similar
[ ] #identical

May need to subclass specific methods for Verbatim vs. BibTeX.
Should follow similar pattern to #288, but potentially much more complicated given the many more attributes.

Is this to return a scope of similar/identical, or as methods returning Booleans for comparing two specific sources?

Scope ideally, but that might be tricky
On Mon, Apr 9, 2018, 8:19 AM James Tucker<EMAIL_ADDRESS>wrote:

Is this to return a scope of similar/identical, or as methods returning
Booleans for comparing two specific sources?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/SpeciesFileGroup/taxonworks/issues/373#issuecomment-379748688,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AABYSMjpGbJhCEWKuNA4ssvj-yaIdhb5ks5tm1_GgaJpZM4TG_Ky
.

Pertinent fast finding with postgres

https://stackoverflow.com/questions/28156795/how-to-find-duplicate-records-in-postgresql
https://gist.github.com/rob-murray/b3528ffcd71040a9fdf1

You can just pass in model.attributes.keys - HOUSEKEEPING_ATTRIBUTES - MODEL_ATTRIBUTES to the latter.

Closing and cross-referencing https://github.com/SpeciesFileGroup/taxonworks/issues/970.


Change language

Hi nice work !
i have a little question for you : how i can change the language please ?
thanks a lot for reply

Language is managed through your plugin config. Thanks!


Windows 10 installation problem

Describe your environment

GPU: [cuda]
VRAM: [12GB]
CPU arch: [x86]
OS: [Windows 10]
Python: [Anaconda]
Branch: [main]
Commit: [commit 03f5ebb5526005929ab91a98da724830414608ef (HEAD -> main, origin/main, origin/HEAD)
Author: spezialspezial<EMAIL_ADDRESS>Date:   Wed Oct 26 15:18:07 2022 +0200]

Describe the bug
Tried to install thanks to conda and pyenv on Windows 10, same error every time:
(invokeai) C:\Users\w00t\Desktop\ai_art\InvokeAI>python scripts\preload_models.py
NOTE: Redirects are currently not supported in Windows or MacOs.
Traceback (most recent call last):
  File "C:\Users\w00t\anaconda3\envs\invokeai\lib\site-packages\transformers\utils\import_utils.py", line 1002, in _get_module
    return importlib.import_module("." + module_name, self.__name__)
  File "C:\Users\w00t\anaconda3\envs\invokeai\lib\importlib\__init__.py", line 126, in import_module
    return _bootstrap._gcd_import(name[level:], package, level)
  File "<frozen importlib._bootstrap>", line 1050, in _gcd_import
  File "<frozen importlib._bootstrap>", line 1027, in _find_and_load
  File "<frozen importlib._bootstrap>", line 1006, in _find_and_load_unlocked
  File "<frozen importlib._bootstrap>", line 688, in _load_unlocked
  File "<frozen importlib._bootstrap_external>", line 883, in exec_module
  File "<frozen importlib._bootstrap>", line 241, in _call_with_frames_removed
  File "C:\Users\w00t\anaconda3\envs\invokeai\lib\site-packages\transformers\models\clip\modeling_clip.py", line 27, in <module>
    from ...modeling_utils import PreTrainedModel
  File "C:\Users\w00t\anaconda3\envs\invokeai\lib\site-packages\transformers\modeling_utils.py", line 79, in <module>
    from accelerate import dispatch_model, infer_auto_device_map, init_empty_weights
  File "C:\Users\w00t\anaconda3\envs\invokeai\lib\site-packages\accelerate\__init__.py", line 7, in <module>
    from .accelerator import Accelerator
  File "C:\Users\w00t\anaconda3\envs\invokeai\lib\site-packages\accelerate\accelerator.py", line 27, in <module>
    from .checkpointing import load_accelerator_state, load_custom_state, save_accelerator_state, save_custom_state
  File "C:\Users\w00t\anaconda3\envs\invokeai\lib\site-packages\accelerate\checkpointing.py", line 24, in <module>
    from .utils import (
  File "C:\Users\w00t\anaconda3\envs\invokeai\lib\site-packages\accelerate\utils\__init__.py", line 96, in <module>
    from .launch import PrepareForLaunch, _filter_args, get_launch_prefix
  File "C:\Users\w00t\anaconda3\envs\invokeai\lib\site-packages\accelerate\utils\launch.py", line 25, in <module>
    import torch.distributed.run as distrib_run
  File "C:\Users\w00t\anaconda3\envs\invokeai\lib\site-packages\torch\distributed\run.py", line 386, in <module>
    from torch.distributed.launcher.api import LaunchConfig, elastic_launch
  File "C:\Users\w00t\anaconda3\envs\invokeai\lib\site-packages\torch\distributed\launcher\__init__.py", line 10, in <module>
    from torch.distributed.launcher.api import (  # noqa: F401
  File "C:\Users\w00t\anaconda3\envs\invokeai\lib\site-packages\torch\distributed\launcher\api.py", line 15, in <module>
    from torch.distributed.elastic.agent.server.api import WorkerSpec
  File "C:\Users\w00t\anaconda3\envs\invokeai\lib\site-packages\torch\distributed\elastic\agent\server\__init__.py", line 40, in <module>
    from .local_elastic_agent import TORCHELASTIC_ENABLE_FILE_TIMER, TORCHELASTIC_TIMER_FILE
  File "C:\Users\w00t\anaconda3\envs\invokeai\lib\site-packages\torch\distributed\elastic\agent\server\local_elastic_agent.py", line 19, in <module>
    import torch.distributed.elastic.timer as timer
  File "C:\Users\w00t\anaconda3\envs\invokeai\lib\site-packages\torch\distributed\elastic\timer\__init__.py", line 44, in <module>
    from .file_based_local_timer import FileTimerClient, FileTimerServer, FileTimerRequest  # noqa: F401
  File "C:\Users\w00t\anaconda3\envs\invokeai\lib\site-packages\torch\distributed\elastic\timer\file_based_local_timer.py", line 63, in <module>
    class FileTimerClient(TimerClient):
  File "C:\Users\w00t\anaconda3\envs\invokeai\lib\site-packages\torch\distributed\elastic\timer\file_based_local_timer.py", line 81, in FileTimerClient
    def __init__(self, file_path: str, signal=signal.SIGKILL) -> None:
AttributeError: module 'signal' has no attribute 'SIGKILL'. Did you mean: 'SIGILL'?

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "C:\Users\w00t\Desktop\ai_art\InvokeAI\scripts\preload_models.py", line 6, in <module>
    from transformers import CLIPTokenizer, CLIPTextModel
  File "<frozen importlib._bootstrap>", line 1075, in _handle_fromlist
  File "C:\Users\w00t\anaconda3\envs\invokeai\lib\site-packages\transformers\utils\import_utils.py", line 993, in __getattr__
    value = getattr(module, name)
  File "C:\Users\w00t\anaconda3\envs\invokeai\lib\site-packages\transformers\utils\import_utils.py", line 992, in __getattr__
    module = self._get_module(self._class_to_module[name])
  File "C:\Users\w00t\anaconda3\envs\invokeai\lib\site-packages\transformers\utils\import_utils.py", line 1004, in _get_module
    raise RuntimeError(
RuntimeError: Failed to import transformers.models.clip.modeling_clip because of the following error (look up to see its traceback):
module 'signal' has no attribute 'SIGKILL'

To Reproduce
Steps to reproduce the behavior:

Follow https://github.com/invoke-ai/InvokeAI/blob/main/docs/installation/INSTALL_WINDOWS.md
Run python scripts\preload_models.py on step 7

Expected behavior
I don't know but not an error.

Replacing SIGKILL with SIGTERM might work.

It worked, changed \invokeai\lib\site-packages\torch\distributed\elastic\timer\file_based_local_timer.py
def __init__(self, file_path: str, signal=signal.SIGKILL)
to
def __init__(self, file_path: str, signal=signal.SIGTERM)
Thanks !

Confirmed, hacky workaround works.
What's the root cause here?
I assume sometime in the last few weeks a newer version of pytorch has been added which includes this SIGKILL bug.
I'm outta my depth here a little but maybe:
https://github.com/invoke-ai/InvokeAI/commit/65b14683a8df15fae7b9c5ea3e189cfeaa9fe2d7
Which has allowed
https://github.com/pytorch/pytorch/issues/85427
To squeeze its way in.

These updated modules also caused my install to fail to detect CUDA entirely.
Forcing my environment.yml back to the following (And rebuilding the cuda environment) resolved both issues for me:
dependencies:
  - python>=3.9
  - pip>=22.2
  - cudatoolkit=11.3
  - pytorch=1.11.0
  - torchvision=0.12.0
  - numpy=1.19.2

I can confirm I have the same issue on Win 10 with Cuda. Fresh install with pew or with Conda both fail with the module 'signal' has no attribute 'SIGKILL'

Seems like a Pytorch developer accidentally added a Linux-only command into a script.
SIGTERM (terminate) is basically what a program receives when you send CTRL+C to cancel something in a CLI.
Linux has some more like SIGTERM, but those do not work on Windows.
I guess for now users will have to rollback and/or wait for a fix. Or, of course, patch it themselves (you can just find-and-replace signal.SIGKILL with signal.SIGTERM

Same issue on Windows 11,
Changing to SIGTERM resolved it

It worked, changed \invokeai\lib\site-packages\torch\distributed\elastic\timer\file_based_local_timer.py
def __init__(self, file_path: str, signal=signal.SIGKILL) to def __init__(self, file_path: str, signal=signal.SIGTERM)
Thanks !

I was having the same issue from another project, and your solution worked like a charm, it saved my days .

We sorted this issue last week. I don't recall the specific PR or version, but at least in the upcoming v2.2 this is sorted.


[Bug Report] Crash on Pycobertura Generated CSV

Category:  major / the application does not fulfill the task it is designed for
Steps to reproduce:

cargo tarpaulin --engine llvm --out xml
pycobertura show -f csv cobertura.xml > cobertura.csv
cargo r -- cobertura.csv

Detailed description:  Tarpaulin is a Rust binary to determine the code coverage of a project.  At option, it can also generate you some reports to be processed by further software.  Pycobertura is such software; I use to format the report for comments on PRs.  It can also convert the Tarpaulin XML report into other formats, like CSV, for instance.  I assumed your application would handle them, as well, because you stated this behaviour in your README.  Instead, the application crashes on an assertion and makes the terminal unusable, as well; normally, one could expect to enter further instructions in the same terminal instance but the crash also seems to affect the terminal process as a whole.  Hence, this is really a major bug you need to take care about.

Could you maybe send me such a csv file so I can debug it?
And yes, terminal displaying is still broken in a lot of points (flickering in certain situations, screens often not clearing, even though they should and could and similar things). So it is no surprise that such a crash happens. It would probably be nicer to add thiserror to tabelle-core and make the gui show a error message? At least as a first fix, so that no crashes happen.
I actually uploaded this repository to have it on another computer, but at the same time I actually think it could be something very useful, so that is why I made sure to add a README and polish the repository.

Here is the cobertura report for Aeruginous v2.0.0:
Filename;Stmts;Miss;Cover;Missing
src/application.rs;29;29;0.00%;87-137
src/cffreference.rs;68;0;100.00%;
src/macros.rs;4;0;100.00%;
src/running.rs;4;0;100.00%;
src/version.rs;26;0;100.00%;
src/pattern/buffer.rs;21;0;100.00%;
src/pattern/io_processor.rs;19;19;0.00%;72-160
src/pattern/reader.rs;31;20;35.48%;57-58, 75-79, 90-109, 123-139
src/pattern/writer.rs;77;30;61.04%;133-152, 187-197, 231-259
src/changelog/comment_changes.rs;163;163;0.00%;106-399
src/changelog/fragment.rs;11;0;100.00%;
src/graphing/agd.rs;156;0;100.00%;
src/graphing/graph.rs;146;0;100.00%;
src/traits/append_as_line.rs;9;0;100.00%;
src/traits/colour_message.rs;8;0;100.00%;
src/traits/convert_buffer.rs;21;0;100.00%;
src/traits/prefer.rs;3;0;100.00%;
src/traits/to_ron.rs;4;0;100.00%;
src/traits/to_stderr.rs;4;0;100.00%;
TOTAL;804;261;67.54%;

Okay, I know why it fails. tabelle parses csv files very simply by just splitting each line into rows and then splitting everything by a ,. So it does not read this file correctly. I will see, that I fix that today.


No support for latest IntelliJ - IU-223.7571.182

Hi,
Thank you for the great plugin. I'm using it every day.
However, it looks like the current Intellij is not supported anymore.
Can you fix it, please?
Plugin 'Mintlify Doc Writer' (version '1.1.6') is not compatible with the current version of the IDE, because it requires build 222.* or older but the current build is IU-223.7571.182

This issue also plagued me. Will this problem ever be resolved?

bump

bump

Me too

Not compatible with the version of your running IDE (IntelliJ IDEA 2022.3.1)

Hello, I hope this can help you to use it on latest intellij
https://github.com/mintlify/writer/issues/98

go to https://github.com/shizeying/writer/releases


stardust@1.1.1:45 TypeError: e.usePlugins is not a function

Hi, I was trying to test the scatter plot chart in Nebula and loaded them like below:
HTML:

JS:
{
name: 'scatterplot',
load: () => Promise.resolve(window["sn-scatter-plot"])
},
nuked.render({
element: document.querySelector(".object"),
id: "mPFcgw",
});
I am basically pulling an object from my QS App.
I end up with this error every time -
TypeError: e.usePlugins is not a function
at hj (sn-scatter-plot:11)
at component (sn-scatter-plot:11)
at stardust@1.1.1:45
at u (runtime.js:45)
at Generator._invoke (runtime.js:274)
at Generator.forEach.t. [as next] (runtime.js:97)
at r (stardust@1.1.1:7)
at l (stardust@1.1.1:7)
at stardust@1.1.1:7
at new Promise ()
Looks like something is wrong with the package.

Hi @dipankarqlik! The sn-scatter-plot requires version 1.2.0 or later of @nebula.js/stardust. We should probably communicate that better… Thanks for submitting the issue. Let me know if you still have problems with a later nebula version.


Add Schwarzschild Black Hole with thin accretion disc as alternative to the Sun

To figure out what it is assignee can watch that video!

 It's that simple.
Alternatively, if you want it only during some event, for example, you should put the texture to the textures folder, create global variable to access it in code, initialize it on startup phase, and then add custom logic to that function.
Alternatively, if you want it to be dynamic, you should create 3d-texture and use some logic to switch layers every time interval dt. There's no support for 3d textures yet, you'll have to add it.
 It's the hardest option, you'll have to write a lot of glsl code to make it beautiful, but the results will surely be amazing.


Updated reportback image flow.

Problem
Needed to rework the reportback image flow to deal with various cases of the user not fully submitting the modal form and closing out of the modal.
Changes

Only creates the crop preview image if the user hits the "done" button in the modal.
If the modal closes without the user clicking "done", we clone and reset the file field so that the user can reupload the image
Creates an edit photo button if the user hits done that allows the user to open the modal again and reset their crop.
Made some updates to the crop preview logic that was causing the preview to break if the modal was submitted more than once.

@DoSomething/front-end

Looks good to me! :boat:

Yar, looks good :dancer:


Error missing module after fresh install

After fresh install when trying to run onedrived-pref (with any options) I get the following error:
Traceback (most recent call last):
File "/home/marcel/.local/bin/onedrived-pref", line 11, in
load_entry_point('onedrived==2.0.0', 'console_scripts', 'onedrived-pref')()
File "/usr/local/lib/python3.5/dist-packages/pkg_resources/init.py", line 561, in load_entry_point
return get_distribution(dist).load_entry_point(group, name)
File "/usr/local/lib/python3.5/dist-packages/pkg_resources/init.py", line 2631, in load_entry_point
return ep.load()
File "/usr/local/lib/python3.5/dist-packages/pkg_resources/init.py", line 2291, in load
return self.resolve()
File "/usr/local/lib/python3.5/dist-packages/pkg_resources/init.py", line 2297, in resolve
module = import(self.module_name, fromlist=['name'], level=0)
File "/home/marcel/.local/lib/python3.5/site-packages/onedrived/od_pref.py", line 11, in
from . import mkdir, od_auth
File "/home/marcel/.local/lib/python3.5/site-packages/onedrived/od_auth.py", line 15, in
from .od_models import account_profile
ImportError: No module named 'onedrived.od_models'
Running Ubuntu 16.04.

same problem here

I think the commit dce21b439c2588a35de6242d03a5a2796d8716d3 solved the issue, which seemed to be indicated by #18.


Running amplify api add-graphql-datasource yields strange error

Before opening, please confirm:

[X] I have installed the latest version of the Amplify CLI (see above), and confirmed that the issue still persists.
[X] I have searched for duplicate or closed issues.
[X] I have read the guide for submitting bug reports.
[X] I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.

How did you install the Amplify CLI?
npm
If applicable, what version of Node.js are you using?
12.22.1
Amplify CLI Version
7.6.2
What operating system are you using?
mac
Amplify Categories
api
Amplify Commands
Not applicable
Describe the bug
Following this instruction set https://docs.amplify.aws/cli-legacy/graphql-transformer/relational/, I follow the instructions to exactness. At the point of running amplify api add-graphql-datasource, I get a strange error. The documentation seems to be legacy(if you look to where the documentation exists), but I failed to find any updated version.
Expected behavior
The amplify command line interface should allow you to run amplify api add-graphql-datasource without error. If that command is deprecated it should state as such.
Reproduction steps

Follow the steps in https://docs.amplify.aws/cli-legacy/graphql-transformer/relational/

GraphQL schema(s)

# Put schemas below this line

Log output

🛑 Cannot destructure property 'serviceWalkthroughFilename' of 'serviceMetadata' as it is undefined.
TypeError: Cannot destructure property 'serviceWalkthroughFilename' of 'serviceMetadata' as it is undefined.
    at Object.addDatasource (/usr/local/lib/node_modules/@aws-amplify/cli/node_modules/@aws-amplify/amplify-category-api/src/provider-utils/awscloudformation/index.ts:300:11)
    at processTicksAndRejections (internal/process/task_queues.js:97:5)
    at Object.run (/usr/local/lib/node_modules/@aws-amplify/cli/node_modules/@aws-amplify/amplify-category-api/src/commands/api/add-graphql-datasource.ts:37:21)
    at Object.executeAmplifyCommand (/usr/local/lib/node_modules/@aws-amplify/cli/node_modules/@aws-amplify/amplify-category-api/src/index.ts:222:5)
    at executePluginModuleCommand (/usr/local/lib/node_modules/@aws-amplify/cli/src/execution-manager.ts:204:3)
    at executeCommand (/usr/local/lib/node_modules/@aws-amplify/cli/src/execution-manager.ts:30:5)
    at Object.run (/usr/local/lib/node_modules/@aws-amplify/cli/src/index.ts:205:5)

Additional information
No response

Hi @NoahGaeta, could you provide the contents of your config file ./amplify/cli.json? Want to verify which version of the transformer is enabled

@marcvberg After investigating more, I found that graphql-transformer-v2 does not support RDS. I went back to older version of the command line interface and I am able run the command fine(other than postgres not working). I can give you the json if you find my report still relevant, if not I will close the issue.

We would expect that you are still able to add a graphql datasource on the latest version so long as the transformerVersion feature flag is set to 1, there are plans to make this available in V2 in the future but you are correct the functionality is currently not supported. If this is broken for V1 on the latest version that's still a concern as we don't want to break existing functionality

It was a test project to see what the system feels like, I can no longer recover it but I did not modify the cli.json file. So whatever behavior exists for generating that file on the latest cli version should've been mirrored in my environment. Is there any documentation that discusses transformerVersion? I totally missed that.

transformerVersion determines whether to use the graphQL V1 vs V2 transformer, so if you create a new project but want to use the V1 transformer you'll need to switch it to 1 instead of 2 to use V1. We like to abstract the feature flag details away when possible, it's something that's automatic in the amplify migrate api workflow

@marcvberg I am not really wondering about that specific flag, I am actually wondering about where other flags/parameters are documented so I know where to look.

It looks like the docs aren't fully up to date with every feature flag released, but generally speaking this is where you would find feature flag information: https://docs.amplify.aws/cli/reference/feature-flags/

Got it, I appreciate the help.

I'm getting the exact same crash even with version 1.
I initialized a new project with these flags:
AMPLIFYCLI_GRAPHQLTRANSFORMER__TRANSFORMERVERSION=1
AMPLIFYCLI_GRAPHQLTRANSFORMER__useExperimentalPipelinedTransformer=false
(by default Amplify generates a cli.json with useExperimentalPipelinedTransformer=true, which overwrites the transformer version, so you need that flag as well)
I then added an api and tried add-graphql-datasource.

cli.json
{
  "features": {
    "graphqltransformer": {
      "addmissingownerfields": true,
      "improvepluralization": false,
      "validatetypenamereservedwords": true,
      "enableiterativegsiupdates": true,
      "secondarykeyasgsi": true,
      "skipoverridemutationinputtypes": true,
      "transformerversion": 1,
      "suppressschemamigrationprompt": true
    },
    "frontend-ios": {
      "enablexcodeintegration": true
    },
    "auth": {
      "enablecaseinsensitivity": true,
      "useinclusiveterminology": true,
      "breakcirculardependency": true,
      "forcealiasattributes": false,
      "useenabledmfas": true
    },
    "codegen": {
      "useappsyncmodelgenplugin": true,
      "usedocsgeneratorplugin": true,
      "usetypesgeneratorplugin": true,
      "cleangeneratedmodelsdirectory": true,
      "retaincasestyle": true,
      "addtimestampfields": true,
      "handlelistnullabilitytransparently": true,
      "emitauthprovider": true,
      "generateindexrules": true,
      "enabledartnullsafety": true
    },
    "appsync": {
      "generategraphqlpermissions": true
    },
    "latestregionsupport": {
      "pinpoint": 1,
      "translate": 1,
      "transcribe": 1,
      "rekognition": 1,
      "textract": 1,
      "comprehend": 1
    },
    "project": {
      "overrides": true
    }
  }
}

Crash log
? Please select from one of the below mentioned datasources GraphQL
� There was an error adding the datasource
� Cannot destructure property 'serviceWalkthroughFilename' of 'serviceMetadata' as it is undefined.
TypeError: Cannot destructure property 'serviceWalkthroughFilename' of 'serviceMetadata' as it is undefined.
    at Object.addDatasource (/home/marco/.nvm/versions/node/v17.2.0/lib/node_modules/@aws-amplify/cli/node_modules/@aws-amplify/amplify-category-api/src/provider-utils/awscloudformation/index.ts:300:11)
    at processTicksAndRejections (node:internal/process/task_queues:96:5)
    at Object.run (/home/marco/.nvm/versions/node/v17.2.0/lib/node_modules/@aws-amplify/cli/node_modules/@aws-amplify/amplify-category-api/src/commands/api/add-graphql-datasource.ts:37:21)
    at Object.executeAmplifyCommand (/home/marco/.nvm/versions/node/v17.2.0/lib/node_modules/@aws-amplify/cli/node_modules/@aws-amplify/amplify-category-api/src/index.ts:222:5)
    at executePluginModuleCommand (/home/marco/.nvm/versions/node/v17.2.0/lib/node_modules/@aws-amplify/cli/src/execution-manager.ts:204:3)
    at executeCommand (/home/marco/.nvm/versions/node/v17.2.0/lib/node_modules/@aws-amplify/cli/src/execution-manager.ts:30:5)
    at Object.run (/home/marco/.nvm/versions/node/v17.2.0/lib/node_modules/@aws-amplify/cli/src/index.ts:205:5)

Reopening for @marco-viewpoint

I'm seeing the same error as @marco-viewpoint and my cli.json is identical in terms of flag values.

Hi, is it possible to use the add-graphql-datasource command if you install an old version of the cli? If so, do you know which version allows this? If not, is there any other way to add a datasource (I'm trying to connect Amazon Aurora) to the graphql api?

@Dennis-Dekker I was told that the breaking change was introduced in 7.5.0 so in theory if you reverted your CLI to an earlier version than that, you should be able to do it.  I had an earlier version that I was using it with, so I can confirm it does work.

@ryanchuleff Thanks for your answer, I just noticed that the issue is resolved in the new version of the CLI. After the update, the add-graphql-datasource command works again.

@Dennis-Dekker thanks for the heads up, I'll grab the latest update.

9288


[FEAT]: API endpoints to create/delete threads within workspace

What would you like to see?

Create API endpoints with the ability to create and delete threads via API
Create API endpoints to chat with workspace threads

I support this, it would be very useful, because now it seems that it is impossible to access, for example, a unique chat instance using the user ID through the API.

This is really a very useful functionality, I hope you add it as soon as possible, I'll be looking forward to it.

Wow, that would be really cool! I'm looking forward to it!

excellent, this is something we need to use in our project. @shatfield4 anything you need help with?

Really need this for my project as well!

I just created a Slack app that connects to AnythingLLM via API.  It would be very cool to be able to pass the slack unique user ID over and keep threads separate between different Slack users.


ImportFileAction doesn't use URI

re  #34218
Most file actions work on URI and to make them work with uris from other schemes little work is needed, however it seems that the import action and the drag&drop model work with paths:
https://github.com/Microsoft/vscode/blob/joh/ftp/src/vs/workbench/parts/files/browser/fileActions.ts#L852

@jrieken I hope I did the right thing in https://github.com/Microsoft/vscode/commit/47cfc8bf7aa3778e358c15d0cfa483eb0e637522#diff-9404b1da682862c61dce10b84ff76e5cR850


Fix WUnderground spamming logs

Description:
See #12517 for a detailed explanation. This is option 1 - never invalidate valid data.
Related issue (if applicable): fixes #12517
Example entry for configuration.yaml (if applicable):
sensor:
  - platform: wunderground
    api_key: !secret wunderground_api_key
    monitored_conditions:
      - weather
      - weather_1d_metric
      - weather_1n_metric

Checklist:

[x] The code change is tested and works locally.

If the code does not interact with devices:

[x] Local tests with tox run successfully. Your PR cannot be merged unless tests pass
[ ] Tests have been added to verify that the new code works.

Should I add tests? If so, how can I best trigger an update to all entities?

Hi,
Apologies if this isn't the right place to report this, but I'm seeing these errors in my logs again. Running 0.65.2. Please let me know if there is somewhere else this should go.

Hmmm, it seems like this only fixed part of the issue. Apparently WUnderground is sometimes sending out invalid JSON to us 🤕. I'm seeing the same thing now on my installation, but unfortunately it is quite hard to reproduce and appears only quite seldomly.
I have now put a log into my installation that will hopefully allow me to further debug the issue. If you have additional please use the #12517 issue, I'll reopen it. Thanks :)


Add AMIP debug plots

Purpose

closes #328

[x] I have read and checked the items on the review checklist.

bors r+


uses-sdk:minSdkVersion 15?

uses-sdk:minSdkVersion 15 cannot be smaller than version 16 declared in library [link.fls:swipestack:0.3.0] E:\kaishuapp_android\kaishustory\app\build\intermediates\exploded-aar\link.fls\swipestack\0.3.0\AndroidManifest.xml

If you want to use this library then you need to change the minSdkVersion in your build.gradle to 16.

@mandarl thanks ,, It is really helps me a lot.


Remove the flags?

It doesn't seem to be a good idea to allow contributors to include the national flags in the README file. This affect the readability and might encourage others to do so

Hmm isn't it helpful to know a project is in Chinese only??

Oops nvm, I thought they were added to show developers' nationalities.

Cool ok :smile:


docs(diagrams): :adhesive_bandage: add path as input for create_id_path

Description
These changes are to add the missing input path to the create_id_path() function. This also aligns with how this part of the flow has been made for create_resource_structure()
Closes #
Reviewer Focus

This PR needs a quick review.

Nice use of the scope!


React UI: batch of fixes

Motivation and context

This changes fix non-opening jobs with cuboids in new UI and change primary annotation UI from old to new one.
How has this been tested?

Manualy
Checklist

- [ ] I have raised an issue to propose this change (required)

[x] My issue has received approval from the maintainers
[x] I've read the CONTRIBUTION guide
- [ ] I have added description of my changes into CHANGELOG file
- [ ] I have updated the documentation accordingly
- [ ] I have added tests to cover my changes
- [ ] I have linked related issues (read github docs)

License

[x] I submit my code changes under the same MIT License that covers the project.
Feel free to contact the maintainers if that's a concern.
[x] I have updated the license header for each file (see an example below)

# Copyright (C) 2020 Intel Corporation
#
# SPDX-License-Identifier: MIT

@ActiveChooN  Please update CHANGELOG.md


Update MaxDOP.sql

Issue #, if available:
Description of changes:
MAXDOP shouldnt always be 1, should be decided based on the application workload.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

We are no longer using that script in the Quick Start, we are need to cleanup the script folder. We are currently using the DSC scripts and using the Auto Feature of DSC that will set the MAXDop to the optimal setting for the instance. Here is the section that does that. Appreciate the PR, we will archive these scripts as they are no longer active.


Reports->Main Milestone-2

This PR covers all documentation implementations including mainly Milestone-2 report.
Initially, it is a draft pull-request at the moment.
Later on, it will be converted to actual pr.
Due Date: 06 December 2023
Presentation Date: 04 December 2023
Software Release Date: 03 December 2023

@dbaslan hi,
since there are some line fixings,
could you please pull the latest version into HackMD file?
thanks in advance.

pre-commit.ci autofix


Solving db_xref problems on modifications

I have updated one annotation using the db_xref to check that it loads.,
/product="Rho family GTPase Rho3"
/systematic_id="SPAC23C4.08"
/controlled_curation="term=modification, far
db_xref=PB_REF:0000001; date=19700101"
this is the first annotation in
http://curation.pombase.org/dumps/latest_build/logs/db_xref_problems.txt
should disappear.
After this, we probably need to open a corresponding jira ticket to ensure that the PB_references.txt file  is read ?
Original comment by: ValWood

nothing to do for this except what's in the jira ticket


[IntelliJ Plugin] Add bug fixes and improvements

Purpose
This PR includes few plugin fixes and improvements related to the 0.990.1 release.

Codecov Report

:exclamation: No coverage uploaded for pull request base (release-0.990.0@53c8fed). Click here to learn what that means.
The diff coverage is n/a.

@@                Coverage Diff                 @@
##             release-0.990.0   #12875   +/-   ##
==================================================
  Coverage                   ?   60.02%
  Complexity                 ?      659
==================================================
  Files                      ?     2068
  Lines                      ?   101767
  Branches                   ?    12956
==================================================
  Hits                       ?    61087
  Misses                     ?    35488
  Partials                   ?     5192

Continue to review full report at Codecov.

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


QT Wallet. Minimum secondary currency amount need to be set depend on coins.

Currently we have such features for fees only, need extend it to trading amounts.

Testing:
Please check that min amounts for mainnet are:
BTC:  0.001
BCH: 0.001
LTC: 0.01
ZCash: 0.01
Dash: 0.01
Doge: 100
For floonet limits are 10 times smaller.

Verified the fix , hence closing this ticket.
BTC: 0.001
BCH: 0.001
LTC: 0.01
ZCash: 0.01
Dash: 0.01
Doge: 100


ISO 8601 format cells not supported

I have a xlsx spreadsheet where the DataSet returned by AsDataSet() contains bad dates (1899-1-1) rather than the values shown by Excel.
The XML of the relvant cells are like this:
    <c r="A2" s="1" t="d">
        <v>2017-03-16</v>
    </c>

Looking at the ECMA spec, t="d" means that it's a date in ISO 8601 format.
Is this expected to work already?  If not, is there any reason to believe the fix is more than:
                        else if (aT == "b") //// boolean
                        {
                            o = _xmlReader.Value == "1";
                        }
+                        else if (aT == "d") //// ISO 8601 date
+                        {
+                            DateTime dt;
+                            if (o != null && DateTime.TryParseExact(o.ToString(), "yyyy-MM-dd", null, DateTimeStyles.None, out dt))
+                                o = dt;
+                        }
                        else if (aS != null) //// if something else

Thanks

Fixed


Ability to draw arrows on board

I also interested in this feature as well, i would like to contribute on this project.

This is a feature I am very interested in. I am going to start working on it, but I am less than proficient in the land of javascript. I may just have to put up a bounty.

Any progress on this or will I need to do it myself?

Any progress on this or will I need to do it myself?

I would like to see also this feature in a next release.
Any plan to add it in a near future?

For anyone wanting an updated version with arrows, look at: https://github.com/pythoncrazy/chessboardjs/tree/main


Design choices document

As per #430 it seems a lot of the changes people request on the "fundamental API" are discussions we have had in the past.
Our collective memory for these things is not good enough. We should start documenting these explicitly.

Possible format to use: https://adr.github.io


feat: preview auto shows plan details

What type of PR is this?

/kind feature
What this PR does / why we need it:
This PR supports automatically showing the plan details when executing kusion preview.
Which issue(s) this PR fixes:

Fixes #787
Special notes for your reviewer:
Does this PR introduce a user-facing change?

Additional documentation e.g., design docs, usage docs, etc.:

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 1 (100.0%)  changed or added relevant line in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.1%) to 76.978%

Totals

Change from base Build<PHONE_NUMBER>:
0.1%

Covered Lines:
8767

Relevant Lines:
11389

💛  - Coveralls


Keep VPA namespace env variable in sync

How to categorize this PR?

/area auto-scaling
/kind bug
/priority critical
What this PR does / why we need it:
Keep VPA namespace env variable in sync in all cases. If they are out of sync between the admission controller and the updater, the updater might become inactive and stop actively scaling targets that have update mode Auto or Recreate.
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
Release note:

Keep VPA namespace env variable in sync in all cases. If they are out of sync between the admission controller and the updater, the updater might become inactive and stop actively scaling targets that have update mode `Auto` or `Recreate`.

please, open cherry-pick PRs to release 1.15 and 1.16.

ping @amshuman-kr

please, open cherry-pick PRs to release 1.15 and 1.16.

ping @amshuman-kr

please, open cherry-pick PRs to release 1.15 and 1.16.

Done.
https://github.com/gardener/gardener/pull/3480
https://github.com/gardener/gardener/pull/3481

please, open cherry-pick PRs to release 1.15 and 1.16.

Done.
https://github.com/gardener/gardener/pull/3480
https://github.com/gardener/gardener/pull/3481


Separate CSS classes for next, prev and complete buttons

At the moment, the CSS class of all navigation buttons is equal. Would be really good if the next, prev and complete buttons could have different classes (e.g. "next" and "complete" in green, "prev" in grey).

default css object has new attributes: navigation: { complete: "", prev: "", next: "" }. Use it to change the style of navigation buttons separately.
PS: To use this feature now, you should build the library from the source.
Thank you,
Andrew

Cool, thanks!
Von einem mobilen Gerät gesendet - bitte entschuldigen Sie eventuelle Tippfehler.

Am 24.08.2016 um 22:00 schrieb Andrew<EMAIL_ADDRESS>default css object has new attributes: navigation: { complete: "", prev: "", next: "" }. Use it to change the style of navigation buttons separately.
PS: To use this feature now, you should build the library from the source.
Thank you,
Andrew
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.


Hamburger button icon missing

Describe the bug
The hamburger 'icon' is not showing
To Reproduce
Steps to reproduce the behavior:
Used NuGet package manager to add MahApps
Simply run WPF app (see repo below)
Expected behavior
The three white lines hamburger 'icon' should always show
Screenshots

Environment(please complete the following information):

MahApps.Metro version v1.6.5
OS: Win10 Pro 17134
Visual Studio Pro 2017 15.8.1
.NET Framework 4.6.1

Repo
https://github.com/savaged/SixNations
This should simply need NuGet restore and F5

@savaged Hi, you forgot some necessary steps to use MahApps.Metro. I created a PR on your repo. By the way, thx for the repo :-D Hope my PR helps you a little bit.