Add events that are happening in 🇳🇱

https://github.com/awkward/awesome-events
This list contains awesome (tech related) events happening (and are mostly recurring) in The Netherlands like: conferences, meetups and parties 🎉
By submitting this pull request I confirm I've read and complied with the below requirements.
Failure to properly do so will just result in the pull request being closed and everyone's time wasted. Please read it twice. Most people miss many things.

I have read and understood the contribution guidelines and the instructions for creating a list.
This pull request has a descriptive title. For example, Add Name of List, not Update readme.md or Add awesome list.
The entry in the Awesome list should include a short description about the list project/theme (not the list itself), and should be added at the bottom of the appropriate category.
The list I added

has been around for at least 30 days,
is the result of hard work and is the best I could possibly produce,
is a non-generated Markdown file in a GitHub repo,
is not a duplicate,
includes a succinct description of the project/theme at the top (example),
includes a project logo/illustration (whenever possible) at the top right of the readme (example). (The logo should link to the project website or any relevant website. The logo should be high-DPI, so set it to maximum half the width of the original image.),
only has awesome items with descriptions (Awesome lists are curations of the best, not of everything),
contains the awesome badge on the right side of the list heading,
has a Table of Contents section named Contents as the first section,
has an appropriate license (Meaning something like CC0, NOT a code licence like MIT, BSD, Apache, etc) (If you use a license badge, it should be SVG, not PNG),
has contribution guidelines,
doesn't include a Travis badge,
has been checked for inconsistent formatting, spelling, and grammar:

Each link description starts with an uppercase character and ends with a period.
Drop all the A / An prefixes in the descriptions.
Consistent naming. For example, Node.js, not NodeJS or node.js.

I would suggest adding in The Netherlands to the heading.

Should be:

Events in the Netherlands

The repo title is too vague. Should be either awesome-events-netherlands or awesome-netherlands-events.

I would also include a link to http://lanyrd.com/places/netherlands/ to track all conferences.
And maybe also https://www.meetup.com/find/?allMeetups=false&keywords=tech&radius=100&userFreeform=netherlands&gcResults=Netherlands%3ANL%3Anull%3Anull%3Anull%3Anull%3Anull%3A52.132633%3A5.2912659999999505&change=yes&sort=member_count

Thanks for the feedback 👍  Made some changes ^


Improve the text at the top of the home page.Feature/home page text

Received the latest home page text from the product team.

 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.:x: shellandco sign nowYou have signed the CLA already but the status is still pending? Let us recheck it.


[C-version] Support sockeye-compiler.

A configuration option with the name of the file must be added.
This file should contain the results of the benchmarks in a format compatible with the sockeye-compiler.

Closed by https://github.com/365andreas/X-Mem/commit/9d4e2ba11af982f6a7fb5bf556a8d1011c0e1d0f.


Better user experience for keyboard interrupts

When running web server (or other daemon-like process) via poetry run, like aiohttp.web.run_app stopping it with Ctrl+C leads to redundant traceback, like:
$ poetry run python -m api
======== Running on http://<IP_ADDRESS>:8205 ========
(Press CTRL+C to quit)
======== Running on http://<IP_ADDRESS>:8205 ========
(Press CTRL+C to quit)
^CTraceback (most recent call last):
  File "/Users/playpauseandstop/.pyenv/versions/3.6.4/bin/poetry", line 11, in <module>
    sys.exit(console.run())
  File "/Users/playpauseandstop/.pyenv/versions/3.6.4/lib/python3.6/site-packages/poetry/console/application.py", line 59, in run
    return super().run(i, o)
  File "/Users/playpauseandstop/.pyenv/versions/3.6.4/lib/python3.6/site-packages/cleo/application.py", line 94, in run
    status_code = self.do_run(input_, output_)
  File "/Users/playpauseandstop/.pyenv/versions/3.6.4/lib/python3.6/site-packages/poetry/console/application.py", line 70, in do_run
    status_code = command.run(i, o)
  File "/Users/playpauseandstop/.pyenv/versions/3.6.4/lib/python3.6/site-packages/poetry/console/commands/command.py", line 25, in run
    return super(BaseCommand, self).run(i, o)
  File "/Users/playpauseandstop/.pyenv/versions/3.6.4/lib/python3.6/site-packages/cleo/commands/base_command.py", line 146, in run
    status_code = self.execute(input_, output_)
  File "/Users/playpauseandstop/.pyenv/versions/3.6.4/lib/python3.6/site-packages/cleo/commands/command.py", line 108, in execute
    return self.handle()
  File "/Users/playpauseandstop/.pyenv/versions/3.6.4/lib/python3.6/site-packages/poetry/console/commands/run.py", line 17, in handle
    return venv.exec(*args)
  File "/Users/playpauseandstop/.pyenv/versions/3.6.4/lib/python3.6/site-packages/poetry/utils/venv.py", line 167, in exec
    completed = subprocess.run([bin] + list(args), **kwargs)
  File "/Users/playpauseandstop/.pyenv/versions/3.6.4/lib/python3.6/subprocess.py", line 405, in run
    stdout, stderr = process.communicate(input, timeout=timeout)
  File "/Users/playpauseandstop/.pyenv/versions/3.6.4/lib/python3.6/subprocess.py", line 835, in communicate
    self.wait()
  File "/Users/playpauseandstop/.pyenv/versions/3.6.4/lib/python3.6/subprocess.py", line 1457, in wait
    (pid, sts) = self._try_wait(0)
  File "/Users/playpauseandstop/.pyenv/versions/3.6.4/lib/python3.6/subprocess.py", line 1404, in _try_wait
    (pid, sts) = os.waitpid(self.pid, wait_flags)
KeyboardInterrupt

From my POV, the keyboard interrupt traceback should be omitted as it is a kind of expected error for poetry run ... calls.

Source of api/__main__.py is listed below,

```py
import asyncio
import uvloop
from aiohttp import web
from api.app import create_app
if name == 'main':
asyncio.set_event_loop_policy(uvloop.EventLoopPolicy())
app = create_app()
if app['settings']['DEBUG']:
    import aiohttp_autoreload
    aiohttp_autoreload.start()

web.run_app(app, host='<IP_ADDRESS>', port=8205)

</details>

This is now implemented in the latest versions :-)

Instead of using subprocess.run and communicating back and forth, it may make more sense for poetry to just execve, unless on Windows, see my project vrun which can be used with virtualenvs to setup the environment correctly/set $PATH:
https://github.com/bertjwregeer/vrun/blob/master/src/vrun/oscompat.py
This way you don't have a python process that runs unnecessarily, and there is less chance of dealing with terminal issues (think ncurses and other such things).


Fixing serde to use Bech32 encoding for ContractId and SchemaId types

Closed in favor of #168 (this one was done from a wrong branch)


Add example error to docs about sp_refreshsqlmodule

This morning we had an issue with a scalar function that was causing SqlExceptions to come back from ADO.NET when queried.  Running EXEC sys.sp_refreshsqlmodule 'dbo.MyFunctionName'; fixed the problem.  The exact error that prompted us to need to run this command would be useful to be in the article.  I'm not sure it belongs right in the header, but I do think it should be in here somewhere.
Example stack trace (we were using Dapper with ADO.NET/.NET Core 3.1 if it's relevant but I don't think it is):
System.Data.SqlClient.SqlException: The definition for user-defined data type 'decimal' has changed.
   at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, bool breakConnection, Action<T> wrapCloseInAction)
   at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, bool breakConnection, Action<T> wrapCloseInAction)
   at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj, bool callerHasConnectionLock, bool asyncClose)
   at System.Data.SqlClient.TdsParser.TryRun(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj, out bool dataReady)
   at System.Data.SqlClient.SqlDataReader.TryHasMoreRows(out bool moreRows)
   at System.Data.SqlClient.SqlDataReader.TryReadInternal(bool setTimeout, out bool more)
   at System.Data.SqlClient.SqlDataReader+<>c__DisplayClass190_0.<ReadAsync>b__1(Task t)
   at System.Data.SqlClient.SqlDataReader.InvokeRetryable<T>(Func<T, TResult> moreFunc, TaskCompletionSource<TResult> source, IDisposable objectToDispose)
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at System.Runtime.CompilerServices.ConfiguredTaskAwaitable<TResult>+ConfiguredTaskAwaiter.GetResult()
   at Dapper.SqlMapper+<ExecuteScalarImplAsync>d__69<T>.MoveNext() in /_/Dapper/SqlMapper.Async.cs:line 1247
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter<TResult>.GetResult()
   at DotNetHelpers.Db.DatabaseReader+<>c__DisplayClass4_0<T>+<<GetScalar>b__0>d.MoveNext()
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter<TResult>.GetResult()

@nycdotnet : Thanks for your contribution! The author(s) have been notified to review your proposed change.

Hi @markingmyname - is this ok to merge?  any concerns adding this example error that would cause someone to need to run sys.sp_refreshsqlmodule?

@markingmyname : Thanks for your contribution! The author(s) have been notified to review your proposed change.

#sign-off

@ktoliver : Thanks for your contribution! The author(s) have been notified to review your proposed change.

Thank you.


Add legacy/conversion support for older versions of 2525 and APP-6

We've had a recent user community request for enhancing JMSML to support 2525B Change 2.  So I've created this issue to help track/discuss that enhancement.  It is certainly something we have talked about, something to be done sometime after the initial release is complete.

Low Priority... they should look to update their systems.

Disagree. This is a high priority for interoperability with older systems. Many systems will send messages with 2525B Change 2 Symbol ID codes and users would expect to be able to see that data.

Gentlemen:
Questions from a DISA perspective:
Is there still disagreement with Mr. Bayles' comment that this is a low priority, given the results of the change proposals to which he refers in a separate posting?
Is Mr. Bayles priority level designation is from an Esri perspective?
Is Mr. Conklin's disagreement from a COCOM and/ or Program perspective?
Regards,
Bill McGrane
Chair, Symbology Standards Management Committee
DISA EE212
Messaging Standards Section
Ft. Meade, MD
301-225-7383
-----Original Message-----
From: Ben Conklin<EMAIL_ADDRESS>Sent: Monday, April 13, 2015 2:39 PM
To: Esri/joint-military-symbology-xml
Subject: Re: [joint-military-symbology-xml] Add legacy/conversion support for older versions of 2525 and APP-6 (#131)
Disagree. This is a high priority for interoperability with older systems. Many systems will send messages with 2525B Change 2 Symbol ID codes and users would expect to be able to see that data.
—
Reply to this email directly or view it on GitHub https://github.com/Esri/joint-military-symbology-xml/issues/131#issuecomment-92455568 . https://github.com/notifications/beacon/AI5TbfrFjnHcn2wWCIcAtl6-GE_fvMcwks5n_ATGgaJpZM4Cvj9U.gif

@wmcgrane,
This was a discussion of relative vs. absolute priority (the scope of ESRI work backlog vs. necessity from a COCOM/program perspective. We still intend on providing backwards compatibility to MIL-STD-2525B Ch. 2, and have change the priority from low to high. We plan on beginning work on that relatively soon.

Per discussion w/ @abouffard, I've added the list of things to accomplish in the original issue.

Creating a separate issue for APP-6(B) support to separate that out.
(also removing the high priority label from this one - since it doesn't seem like it was a high priority)

Verified.


Update documentation to use Material for MkDocs

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

@Brian969 Do not use this branch, move to mkdocs-0.2, the CI tooling deleted all files and placed static documents in its place


Restructure internal/time.h for better combination with internal/e_os.h

For its fallback implementation of ossl_sleep(), internal/e_os.h includes
internal/time.h.  This is all good, as long as internal/e_os.h is included
first.  However, internal/time.h also includes internal/e_os.h for its time
structure conversion functions, and we find ourselves with an inclusion loop
that happens before OSSL_TIME is defined, and we get a warning or an error
for the fallback implementation of ossl_sleep().
To remedy this, internal/time.h is restructured to include internal/e_os.h
late, and move all the functions for converting between OSSL_TIME and other
time structures after that inclusion, as internal/e_os.h helps making those
other structures available.

VMS builds currently fail, this fixes the current problem

Actually, this isn't quite right.  Some of the apps/ source use ossl_sleep(), which means that if the fallback is used, they will refer to ossl_time_add(), ossl_ms2time(), ossl_time_compare() and ossl_time_now().  Most of the are static inline, which is fine.  However, ossl_time_now() is not, so requires resolution when linking.  But, libcrypto in shared library form doesn't export it, so you end up with a reference to undefined symbol, like this (VMS example):
%ILINK-W-NUDFSYMS, 1 undefined symbol:
%ILINK-I-UDFSYM, 	ossl_time_now
%ILINK-W-USEUNDEF, undefined symbol ossl_time_now referenced
	section: $CODE$
	offset: %X0000000000012A50  slot: 2
	module: cmp
	file: USR_DISK:[RICLE.TEST.openssl-3_1_0-dev._VMS-IA64.apps]OPENSSL-BIN-CMP.OBJ;1
%ILINK-W-USEUNDEF, undefined symbol ossl_time_now referenced
	section: $CODE$
	offset: %X0000000000012AD0  slot: 2
	module: cmp
	file: USR_DISK:[RICLE.TEST.openssl-3_1_0-dev._VMS-IA64.apps]OPENSSL-BIN-CMP.OBJ;1
%ILINK-W-USEUNDEF, undefined symbol ossl_time_now referenced
	section: $CODE$
	offset: %X000000000000D7A0  slot: 2
	module: s_server
	file: USR_DISK:[RICLE.TEST.openssl-3_1_0-dev._VMS-IA64.apps]OPENSSL-BIN-S_SERVER.OBJ;1
%ILINK-W-USEUNDEF, undefined symbol ossl_time_now referenced
	section: $CODE$
	offset: %X000000000000D820  slot: 2
	module: s_server
	file: USR_DISK:[RICLE.TEST.openssl-3_1_0-dev._VMS-IA64.apps]OPENSSL-BIN-S_SERVER.OBJ;1
%ILINK-W-USEUNDEF, undefined symbol ossl_time_now referenced
	section: $CODE$
	offset: %X000000000000FBC0  slot: 2
	module: s_server
	file: USR_DISK:[RICLE.TEST.openssl-3_1_0-dev._VMS-IA64.apps]OPENSSL-BIN-S_SERVER.OBJ;1
%ILINK-W-USEUNDEF, undefined symbol ossl_time_now referenced
	section: $CODE$
	offset: %X000000000000FC40  slot: 2
	module: s_server
	file: USR_DISK:[RICLE.TEST.openssl-3_1_0-dev._VMS-IA64.apps]OPENSSL-BIN-S_SERVER.OBJ;1

Is there a reason why ossl_time_now() isn't a static inline function like the other ones?

ossl_time_now() is messy with respect to the pre-processor and I've designs on adding additional clocks to it eventually (which could make it quite a bit larger).

ossl_time_now() is messy with respect to the pre-processor and I've designs on adding additional clocks to it eventually (which could make it quite a bit larger).

I suspected that.  I can really only think of one option at this point: rename ossl_sleep() to OSSL_sleep() and make it a public symbol, declared in <openssl/crypto.h>.  It's really the only way to ensure our app (and consequently, any app) can use it in a sane way (*).

(*) Oh, there are not so sane options as well.  I'd say that's the wrong way to go, though.

I'm not actually against making this an inline function.

I'm not actually against making this an inline function.

If you meant ossl_time_now(), I am.  As you said, there are preprocessor complexities, and that's a risk of more complicated entanglements in e_os.h, where we already have a bit of conflagration with the time.h / e_os.h inclusion delicacies.  I don't think that's a sane path to take.

Closing this, as it wasn't a good solution


q-FedSGD update

Dear author, thanks for sharing your wonderful codes.
In the ICLR paper Algorithm 1, the server updates w by (sum of deltas) / (sum of hs). As I understand from the paper, the h_k^t's are the upper bounds of the gradient on each device. So why is the summation not taken over the (delta_k^t / h_k^t)? What is the rationale in aggregating all the upper bounds and use the sum as a denominator?

The numerator can be considered as the mini-batch gradient of the objective, and the denominator is the estimated Lipshictz constant of the gradient on the numerator, which is 1 / the estimated step size.

please let me know if this does not answer your question

Thanks for your reply. I think I get what you mean, I'm just wondering if
there would be a better bound on the step size than the sum of (potentially
loose) bounds :D. Please let me know if you have any further thoughts on
this :)
On Thu, Jul 2, 2020 at 4:28 AM Tian Li<EMAIL_ADDRESS>wrote:

please let me know if this does not answer your question
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/litian96/fair_flearn/issues/5#issuecomment-652630158,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAJXZTSYQPLZMKL6CICAKBDRZOL6RANCNFSM4OLZT5HA
.

that's a good point. We use the heuristic of estimating the step size as the inverse of the estimated Lipschitz constant. How to estimate the Lipschitz constant itself is an open problem (we use the heuristic based on Lemma 3). The estimate might not be very accurate, but we empirically demonstrate that we achieve similar (or better) performance than distributed SGD with a best-tuned fixed step size on all the datasets (see Figure 4 in https://openreview.net/pdf?id=ByexElSYDr).


EmailAddress Scaffold

A user has_many email_addresses.
Attributes

user_id, :integer
value, :string
description, :string
is_public, :boolean, default: true
position, :integer

Indexes

value (unique)
user_id

Validations

@required_fields ~w(value is_public user_id)
The associated user has to be valid.
value has to be a valid email address. But don't go overboard with this. A 99% validation is fine for now.

Misc

Within a user all email_addresses are always ordered by the position.
value is auto downcased during create and update.

Routing
They are nested under the users resource:
/users/:slug/email_addresses
Form

value, :string
description, :string # Pulldown select with 'Work', 'Home' and a free field where people can enter they own text.
is_public, :boolean, default: true

Will every email address need to be verified? Do we want to add a verified attribute to the table?

Will every email address need to be verified? Do we want to add a verified attribute to the table?

I think so, to minimize false email addresses and security reason.

Will every email address need to be verified? Do we want to add a verified attribute to the table?
I think so, to minimize false email addresses and security reason.

Yes, we do have to verify every new email address by sending one email to it and having the user clicking on the verification link. We already do it in v1.1. Otherwise I could add your email address to my account and you couldn't use it any more.


DOM-based XXS vulnerability in the MarkDown Editor Activity

You can easily style the elements of the UI using CSS in the Markdown editor.
Here's how to replicate:
Open the Markdown Activity.
And paste the following code into the box.
Move your mouse pointer and enjoy:)
Here's the code:

Hello World, This is a paragraph and <button style="background: black!important;" onclick="alert('Stop clicking me!')">This is a button </button>

If you click on that black (colour changing when you hover) button, you'll notice that it even accepts JavaScript code and the code works perfectly.
I can see two possible fixes:
The dumb fix:
Use JavaScript to remove all occurences of the

Very nice.
BTW not sure using iframe is a good idea. It's not a good practice.

It seems to be fixed by now. So I'm closing the issue.

Source code for MarkDown Editor activity is located here https://github.com/llaske/sugarizer/tree/dev/activities/Markdown.activity

Fixed in https://github.com/llaske/sugarizer/commit/039b2b14bdcbfd9591c87b68b2e108a3fe880422

Marking this as closed.


Proxy: preservation_client - add method to call "validate_moab" endpoint

see https://github.com/sul-dlss/preservation-client/issues/46

closed by


No implicit any error on call in JS but not in TS

Bug Report

🔎 Search Terms

js, overload
🕗 Version & Regression Information

This is the behavior in every version I tried, and I reviewed the FAQ entries but non apply.
⏯ Playground Link

JS version playground link with relevant code
TS version playground link with relevant code
💻 Code

JS version:
/**
 * @template T
 * @template U
 * @typedef {T & { [K in Exclude<keyof U, keyof T>]?: never }} ButNot
 */

/**
 * @template T
 *
 * @overload
 * @param {ButNot<T, Function>} [context]
 * @returns {void}
 *
 * @overload
 * @param {(index: number) => any} mapFn
 * @param {T} [context]
 * @returns {void}
 */
function foo() {}

//   v- ❌ ERROR: Parameter 'k' implicitly has an 'any' type. (7006)
foo((k) => [k]);

// No errors ✅
foo((k) => [k], undefined);

TS version:
type ButNot<T, U> = T & { [K in Exclude<keyof U, keyof T>]?: never };

function foo<T>(context?: ButNot<T, Function>): void;
function foo<T>(mapFn: (index: number) => any, context?: T): void;
function foo() {}

// No errors ✅
foo((k) => [k]);

ButNot is as @RyanCavanaugh suggested in https://github.com/microsoft/TypeScript/issues/4196#issuecomment-413096492.
🙁 Actual behavior
Parameter 'k' implicitly has an 'any' type. error in JS version but not TS one.
🙂 Expected behavior
No errors.
PS: This feels like a bug to me but I'm not sure if there's another way to achieve the expected outcome.

Do you see same behavior if you declare all types and overloads in TS, and only try use it in JS (instead of JS docs declaration)?
To exclude difference between JSDoc and TS declarations.
May be related to #39509

Experimenting with 3 overload signatures shows that only the first fails to get the type parameter. I'm not sure what's going on but at least I'm pretty sure it's not parsing.
Here's the variant I ended up with:
/**
 * @template T
 * @overload
 * @param {(index: number) => any} mapFn
 * @param {T} [context]
 * @returns {void}
 *
 * @overload
 * @param {Partial<T>} [bipartite]
 * @returns {void}
 *
 * @overload
 * @param {ButNot<T, Function>} [admissible]
 * @returns {void}
 */
function foo(admitation) {}

Confusingly, type baselines for this test case are correct. But the call still has the error from the OP:
// @checkJs: true
// @allowJs: true
// @strict: true
// @noEmit: true
// @filename: /overloadTag4.js
/**
 * @template T
 * @template U
 * @typedef {T & { [K in Exclude<keyof U, keyof T>]?: never }} ButNot
 */

/**
 * @template T
 * @overload
 * @param {ButNot<T, Function>} [admissible]
 * @returns {void}
 * @overload
 * @param {(index: number) => any} mapFn
 * @param {T} [context]
 * @returns {void}
 *
 * @param {any} admitation
 */
function foo(admitation) { !!admitation }
foo(x => [x])

I tested signature help some more, and it behaves the same in JS and TS--the first signature is instantiated and the others are not. Confusing but probably intentional.
Quick info is not good at specifying which signature was selected in a call, but it turns out both TS and JS select the same signature: the mapFn one. Both fail to make any inferences since context is not provided. The difference is that in JS a type parameter without inferences is constrained to any; in TS it's constrainted to unknown:
    function getDefaultTypeArgumentType(isInJavaScriptFile: boolean): Type {
        return isInJavaScriptFile ? anyType : unknownType;
    }

The inferred any causes a noImplicitAny error.
"strict": true and "checkJs": true is a combination that may lead to problems because checkJs needs to support very loose JS code, but also JS-in-TS code. In this case, JS-in-TS has its usability hurt by a loose-JS design decision.

Thank you @sandersn for getting to the bottom of this issue.
How would you explain the outcome of the test in https://github.com/microsoft/TypeScript/issues/55062#issuecomment-1640531237 (TS infers correct type for callback parameter but not JS)?

In TS, T=unknown, so there's no implicit any error on k: unknown.
In JS, T=any, so there IS an implicit any error on k: any, since it was not explicitly declared.
In both cases, the same overload is chosen and there are no inference sources for T, so you're getting the default type parameter type for JS (any) vs TS (unknown).

Well this is confusing because I observed TS inferring k: number not unknown😅

Poking at it again, I see that T=any causes the first overload with ButNot to be chosen. You can force this to happen in Typescript with foo<any>(k => [k]). That way k's contextual type is any instead of number since mapFn isn't there to give index's type.

I see, so if I understood correctly:

In JS the inference defaults to any so foo((k) => [k]) is equivalent to foo<any>((k) => [k]) (matching the ButNot overload)
In TS it defaults to unknown so foo((k) => [k]) is equivalent to foo<unknown>((k) => [k]) (matching the mapFn overload).

Which seams to holdup:
//        v- ❌ (parameter) k: any
foo<any>((k) => [k]);

//            v- ✅ (parameter) k: number
foo<unknown>((k) => [k]);

Playground link
Thank you for taking the time to explain it to me 😄


User.password cannot be null

Hi guys,
First of all, I would like to thank you for such an awesome project. It helps me a lot.
Today I faced with a strange logic, so I would like to ask for some help with that.
I extend org.springframework.social.security.SocialUser class to get representation of an authorized user. I use it with form-based auth and with social auth too. The problem is in password field. When I authorize user through Facebook, for example, I do not have it's password to populate the field. So, I pass null to the constructor of SocialUser and get java.lang.IllegalArgumentException: Cannot pass null or empty values to constructor. The exception comes from User:
...
if (((username == null) || "".equals(username)) || (password == null)) {
        throw new IllegalArgumentException("Cannot pass null or empty values to constructor");
}
...

As a workaround, I pass an empty string as password, and it works pretty well, but such approach don't seems to be good. :smile:
Maybe it worth to make password nullable?
Thanks.

I understand your issue, but as you pointed out, the enforcement of a non-null password comes from User, which is a class from Spring Security and any relaxation of that rule should come in Spring Security changes. The best that Spring Social can do is to pass in an empty string on your behalf, but that would just be shifting the workaround from your code to Spring Social's code. I suggest you open an issue with the Spring Security project, referencing this issue and Spring Social's SocialUser type.
Since this can't be addressed properly in the context of Spring Social, I am closing this issue.


Move long running QA tests into a separate 'performance' set of tests

This will not usually be executed during development (only by CI, or when something breaks)
At the moment they take 31seconds to run locally (which is about 28 seconds too much)

and 47 seconds in Travis

There needs to be a set of QA tests that are super fast to run, and an dev environment for writing more Browser automation tests (with the idea that these are the tests that are worked during normal development)

done, there are now 26 tests in the main QA test project that run in 2.6 seconds

and there are 16 tests in the 'performance' QA test project that runs in 27 seconds


Update README.md to fit consistent style

See https://github.com/GoogleCloudPlatform/gcloud-meta/issues/3 for the format

@ajkannan can you check if our README.md consistent with the proposed style?


[Bug] The description for field source_type is too long

Is there an existing issue for this?

[X] I have searched the existing issues

Describe the issue
The docs part of the source_type columns is too long in bigquery
Relevant error log or model output
12:18:50  38 of 133 START sql table model dbt_t_app_store.stg_apple_store__crashes_platform_version  [RUN]
12:18:51  Unhandled error while executing target/run/apple_store_source/models/stg_apple_store__app_store_territory.sql
400 PATCH https://bigquery.googleapis.com/bigquery/v2/projects/dlake/datasets/dbt_t_app_store/tables/stg_apple_store__app_store_territory?prettyPrint=false: The description for field source_type is too long. The maximum length is 1024 characters.

Expected behavior
running without issue or shorter description for that field
dbt Project configurations
app_reporting:
+schema: app_reporting
apple_store:
+schema: apple_store
apple_store_source:
+schema: app_store
google_play:
+schema: google_play
google_play_source:
+schema: google_play
Package versions

package: fivetran/app_reporting
version: [">=0.3.0", "<0.4.0"]

What database are you using dbt with?
bigquery
dbt Version
Core:

installed: 1.4.5
Plugins:
bigquery: 1.4.1

Additional Context
No response
Are you willing to open a PR to help address this issue?

[X] Yes.
[X] Yes, but I will need assistance and will schedule time during our office hours for guidance
[ ] No.

Yes we are persisting these docs to the warehouse. Maybe you can see the same if you try as I do.

Will there be any action for the ones those persisting the docs in the warehouse or should I just go with override of the documents ? @fivetran-joemarkiewicz

Hi @calkan-cue apologies for the delay, we are bringing this issue into our current sprint and will share more as we investigate and work towards a fix.

Hey @calkan-cue! Thanks for opening this up. Our latest release of this package (v0.3.2) addresses this. As such we'll be closing this issue, but let us know if there's anything else!


Bump version to 0.1.0

Coverage decreased (-1.5%) to 21.856% when pulling 1d2cbe8860a306d6333ff419a90e203250bc1615 on main into 9e7ef804e64f24cd5e85f48595abc1370b768c87 on release.


lowercase infinitive not working in german

I have absolutely no idea how the .dic format works, all I can say is that practically any infinitve german word is marked as misspelt when using this in retext-spell.
For example, "markieren" is a normal word and has several entries in the dictionary, but somehow just "markieren" doesn't work, while "Markieren", "markierend", "markierens" or even "-markieren" work. What is the issue here?
"würde" is another case, even though that isn't an infinitive. "würde" is a verb, meaning "would", "Würde" (which works), meaning "dignity", is a substantive. It seems like every infinitive verb you could also write in uppercase (so basically any german verb) is not allowed when written in lowercase.

Hmm, might be nspell related, as it’s not 100% compatible with hunspell.
It might be worth checking with hunspell, if the dictionary works there. I would appreciated it a lot if you could check that?
Looking at the .aff file here, it might be duplicated. Those lines are typically at the top, not half way into a document

C++ compiling and all that makefile spam is such a joke, but I guess that's how things are done there...
What I did after installing hunspell:
wget -O de.dic https://raw.githubusercontent.com/wooorm/dictionaries/main/dictionaries/de/index.dic
wget -O de.aff https://raw.githubusercontent.com/wooorm/dictionaries/main/dictionaries/de/index.aff

and then testing it:
hunspell -d de
Hunspell 1.7.0
markieren
*

markierend
+ markieren

Markieren
*

markierens
& markierens 8 0: Markierens, markierend, markieren, -markierens, markiere, maskieren, marinieren, massieren

As you can see, "markieren" is correct here. "markierens" is not, but it would be in retext-spell. But only the uppercase "Markierens" is correct.
It really seems like nspell has some issues with case.

Testing with nspell here:
https://runkit.com/nnmrts/nspell-de-test
yields this:
{
	"markieren": [
		false,
		[
			"Markieren"
			"markierend",
			"markierens",
			"-markieren",
			"markiere",
			"markierten",
			"maskieren"
		]
	],
	"markierend": [
		true,
		[]
	],
	"Markieren": [
		true,
		[]
	],
	"markierens": [
		true,
		[]
	]
}


v3.0.0-beta

Rewrite in TypeScript
Support discord.js v13
Use @discordjs/voice
Manage voice connections
New stream system
Task queue system

Codecov Report

:exclamation: No coverage uploaded for pull request base (beta@b3cb6bd). Click here to learn what that means.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             beta     #121   +/-   ##
=======================================
  Coverage        ?   21.40%
=======================================
  Files           ?       24
  Lines           ?      953
  Branches        ?      319
=======================================
  Hits            ?      204
  Misses          ?      748
  Partials        ?        1

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 b3cb6bd...e0dccf5. Read the comment docs.


Containerize all the things

The goals of this ticket are as follows:

Deprecate Travis. Rip out all the infrastructure that depends on Travis. When the ticket is complete, .travis.yml, if it is still utilized at all, should be a skeleton of its former self, merely calling shell scripts to build and test. This will pave the way for migrating from Travis to another CI that provides much faster, more stable builds.
Improve Determinism. Remove the maximum number of hidden dependencies, points of failure, and points of indeterminism. Developers should be able to check out the code base and run all the tests without having to install or configure external dependencies. Moreover, such tests should succeed all the time if they succeed once, and fail all the time if they fail once, up to the determinism limitations of the tests themselves.
Provide Flexibility. Allow running just the tests for a given backend (plus core tests). This can be utilized by developers working on a specific backend, but also by testing infrastructure that's capable of running the same build in parallel over a matrix of configuration options (i.e. Travis' matrix, but without Travis).

Currently, the best route to obtaining these goals seems to involve containerization. Specifically, if for every connector, we have a mechanism to build a container that has all dependencies and can run all tests for the connector, then we can completely isolate different connectors, parallelize on arbitrary (non-Travis) building & testing infrastructure, and maximize determinism.
To achieve these goals, the following steps are needed (and may be revised as necessary):

[x] Create Dockerfiles to encode the recipes necessary for building dependencies together with test infrastructure.
[ ] Create shell scripts or sbt tasks to run tests for a specified connector.
[x] Simplifying Travis to utilize the new machinery.
[ ] Downloading or at least detecting the presence of Docker / rkt to enable bootstrapping.
[ ] ???

@nicflores , @jdegoes -> Fyi , for now the goal is not necessarily to rip out Travis. Agreed that we should minimize any dependencies, so we can plug/play any CI with minimal fuss. We are trying to fix things without necessarily switching the CI, via working with Travis support on possible options and upgrades. More can be gleaned here. However, we do want to Dockerize and this would be a great way for you to add value immediately.

Fyi -> https://docs.travis-ci.com/user/docker/

Here are some thoughts I'd like to get out there regarding this task.
Several ideas come to mind.
First: In order to have developers run isolated tests against containerized connectors they will need to have docker installed locally on their development machines. Depending on the OS the developer is running they would need to go through an installation process outlined here.
This defeats the idea that all the developer should have to do run commands like sbt testMy<ConnectorName> and not have to worry about mucking with their dev box.
Second: There's another tool called Docker Compose that allows one to define an entire dockerized environment in yml. Here's a good example. Again, though, this would require developers to have Docker Compose installed on their dev box.
Third: I happened to come upon an example in the Travis-CI docs of how to use Docker Compose. I'll be experimenting with this on one of my own repos. This functionality could bring down build times and also possibly avoid having  developers install docker on their machines if we are willing to interface with travis-ci via the command line tool. For example, we could trigger integration tests on branches containing a docker-compose.yml file using something similar to this example.
If you ya'll have any feedback on this I'd appreciate it. In the mean time I'll keep moving forward with the tasks above beginning with creating dockerfiles for the various databases. I'll be starting with the various versions of MongoDB.

I gave @drostron a quick demo of docker compose yesterday and demonstrating that using a command like docker-compose up mongo26 mongo30 bring ups those specific databases in containers locally. A plain docker-compose up would being up every service defined in the docker-compose.yml file. Dave and I agreed that if developers had docker installed this would help ease db setup for integration tests.
The demo pulled docker images from docker hub so the next step is to make docker compose configure each database as we needed. This my next task.

Ultimately it'd be nice to have an SBT task to pull down Docker / Docker Compose.

@jdegoes, @drostron and I have been bouncing ideas off each other on that topic. I found this sbt plugin which might help once a developer has docker and docker-compose installed. As for getting docker on developer dev machines @drostron found this linux script which may help. I'm still on the hunt for something similar for mac and windows.
On another note I managed to figure out how to get around this docker couchbase issue I was having:
{"storageMode":"memory_optimized","indexerThreads":0,"memorySnapshotInterval":200,"stableSnapshotInterval":5000,"maxRollbackPoints":5,"logLevel":"info"}

running this this command:
curl -v -s -X POST $CBWOP:8091/pools/default -d memoryQuota=512

before running the setupServices curl command does the trick. Found out the other folks on chouchbase issue tracking were having the same problem: https://issues.couchbase.com/browse/MB-16233.
I'll be moving on to dockerizing Marklogic next.

I've got Marklogic dockerized. The pre-configuration commands within the installMarklogic script, i.e. login to marklogic website and download of Marklogic.rpm, have been migrated to a Marklogic-Dockerfile. The post configuration now lives in a script under a docker directory of the root quasar repo along wth dditional post configuration scripts for mongo, couchbase, and postgresql. In addition I created a setupdbs.sh script that wraps all the post configuration scripts into a single place.
Using what I have above I ran the following tests:
> it/test-only **.ReadFilesSpec -- -showtimes -ex simple read  --
> it/test-only **.ReadFilesSpec -- -showtimes

against dockerized databases on my local machine. All tests passed but I did have to populate my own testing.conf file, ideally I'd like have setupdbs.sh do that for me.
There's one more fix I'd like to, which is to minimize the number of RUN commands in the Marklogic Dockerfile in order to reduce the number of layers created when building the Marklogic image.
At this point half of the first goal is complete. The next step will be to look into which tests specifically test individual connectors.

Reviewed my current progress with @drostron this morning. We looked at my current .travis.yml refactoring and how database containers are being created and configured. We found a couple of small issues I'll be fixing today and once I have a build in my branch that times out we can re-run a build of my branch on the quasar-analytics repo.

PR submitted for local scripts and travis containerization refactor. I'll be moving on to writing some sbt tasks for integration testing.

At this time PR #2037 contains scripts which may help developers manage their integration testing environment.
Here is a rundown of what is possible:

From within the docker directory.
a. One can run, for example,

docker-compose up -d marklogic_xml mongodb_read_only couchbase

which will spin up the passed in containers. Similarly
docker-compose stop marklogic_xml mongodb_read_only couchbase

will stop the containers. Finally
docker-compose rm marklogic_xml mongodb_read_only couchbase

will delete these containers.
The current list of containers available to spin up are:
mongodb_2_6
mongodb_3_0
mongodb_read_only
mongodb_3_2
mongodb_3_4

2. Once containers are up and running some may need some extra configured. The `setupConnectors` is able to configure all running containers or specific containers. In addition one can skip the use of `docker-compose` mentioned above and use the `-u` flag along with a list of quoted space separated connectors to bring up connectors and configure them all in one command. Below is the usage output for `setupConnectors`.

[14] → ./scripts/setupConnectors -h
Usage: ./scripts/setupConnectors [-h] [-a] [-c CONNECTOR-NAME]
Create and configure dockerized mongo, couchbase, marklogic, and postgresql
connectors for integration tests with Quasar.
-h                   help (also trigged with no parameters): display this help and exit
-a                   configure all currently running dockerized connectors
-c CONNECTOR-NAME    configure running dockerized connector named CONNECTOR-NAME
-u "con1 con2..."    use docker-compose up to create and configure a quoted list of connectors

3. After containers are up and configured `assembleTestingConf` can be used to build an 'it/testing.conf` file. Below is the usage output of this for `assembleTestingConf`.

[15] → ./scripts/assembleTestingConf -h
Usage: ./scripts/assembleTestingConf [-h] [-a] [-c CONNECTOR-NAME]
Assembles Quasar integration configuration file, it/testing.conf, from currently running
containerized connectors or for the specific CONNECTOR-NAME passed in. Works for local
development and within travis-ci.
-h                   help (also trigged with no parameters): display this help and exit
-a                   cleans existing testing.conf and adds connector URIs to testing.conf for all currently running dockerized connectors
-i CONNECTOR-NAME    add connector URI to existing testing.conf file
-c CONNECTOR-NAME    cleans exisitng testing.conf and adds a connector URI for CONNECTOR-NAME currently running
-t                   create testing.conf with all currently running dockerized connectors plus spark local connector

Looking good! This should all make it into documentation of the README, probably, in a new section on build/test.

Can I close this issue?
This PR #2037  contained much of the containerization work including Dockerfiles, a docker-compose.yml file, scripts to create and configure containers as well as a script to generate testing.conf file based running containers. In addition it included an updated .travis.yml file which leverages docker-compose and the scripts mentioned above.
The PR, #2053, contained updated Quasar README with information on how to use the new scripts.
@alissapajer and @drostron have both used the scripts and I believe they working as they should.

@nicflores  - Let's discuss scope some more before closing this out.

sounds good, @zeeiyerWork.

After discussion with @nicflores and based on the above comments - closing this one out. since containerization is done vis-a-vis developers. There are questions around cases, where:

Dockerization can play a part in making installation experience smoother (i.e. installer asks if user wants a Mongo/ML/CB etc. instance and sets those up). Chat with others next week wrt this.
we could work on integration tests, to separate data loading out of the tests - i.e.

A set of tests share the same instance and loaded data.
Performance tests rely on a prior-established Mongo instance, teed up with large data sets.

But those will be recoded as separate issues.
Thanks


support notebook on volume

Out of curiosity what were you thinking of the story for this?  Axolotl is mainly a CLI tool and I see limited utility of a notebook - but I could be missing something!
cc: @charlesfrye


Use of partitioned_by failing

Prior I was running our models in dbt with these versions:
installed version: 0.21.0
   latest version: 1.0.0
Plugins:
  - athena: 0.21.0

And the use of partitions was fine, but now I am changing the host and I can't install the dbt-athena-adapter in version 0.21.0 (this was installed long ago and this version don't exist anymore) so I installed this package.
But running even a simple model with partition fail.
{{ config(
    format='parquet',
    partitioned_by=['status']
) }}

select
    'a' as user_id,
    'pi' as user_name,
    'active' as status
union all
select
    'b' as user_id,
    'sh' as user_name,
    'active' as status
union all
select
    'c' as user_id,
    'sh' as user_name,
    'disabled' as status

The result query have double quotes in the partition array like this:
create table
    "service"."test"

    with (
        partitioned_by=ARRAY["status"],
        format='parquet'
    )
  as

And the execution fail with SYNTAX_ERROR: line 3:27: Column 'status' cannot be resolved. But the same query with single quotes in partition clause executes normally.
Am I doing something wrong? Because this is a simple use. The target is a Athena version 2 datalake.

👋🏻 Hello
Can you give us the name of the library you installed and the version please ?
For your information, to this install this package and not the package created originally by Tomme you need to install dbt-athena-community instead of dbt-athena which is the Tomme version. And the dbt-athena-community package is only compatible with dbt 1.x.

I just tried to run this:
{{ config(
    format='parquet',
    partitioned_by=['status']
) }}

select
    'a' as user_id,
    'pi' as user_name,
    'active' as status
union all
select
    'b' as user_id,
    'sh' as user_name,
    'active' as status
union all
select
    'c' as user_id,
    'sh' as user_name,
    'disabled' as status

with the latest version from main and it worked, I also installed dbt-athena-community==1.4.1 and run the model, and also that worked.
@KleyLimaa Could you run this pip list | grep dbt and post the output?

@nicor88 Thanks for taking time to analyze. The output is:
dbt-athena-community     1.4.1
dbt-core                 1.4.5
dbt-extractor            0.4.1

@KleyLimaa I tried also in a "containarized" version running debian...working fine.
Could you try to install the latest version from main and copy the error that you get?

@nicor88 I made:
git clone git@github.com:dbt-athena/dbt-athena.git
cd dbt-athena/
virtualenv venv
source venv/bin/activate.fish
python setup.py sdist
cd dist/
tar -xvzf dbt-athena-community-1.4.1.tar.gz
cd dbt-athena-community-1.4.1/
python setup.py install
# cd to the dbt project directory
dbt run --model test

The error is SYNTAX_ERROR: line 3:27: Column 'user_status' cannot be resolved.
Using DBT_DEBUG=true show me the query:
create table
    "service"."test__dbt_tmp"

    with (
        partitioned_by=ARRAY["user_status"],
        format='parquet'
    )
  as

Why is there not the select part of the query ?

The issue seems to be partitioned_by=ARRAY["user_status"] user_status is not quoted as it should...

Looking deeper https://github.com/dbt-athena/dbt-athena/blame/28410b96bc2e2ad94a9765841fe646b63e756196/dbt/include/athena/macros/materializations/models/table/create_table_as.sql#L55
{{ partition_property }}=ARRAY{{ partitioned_by | tojson | replace('\"', '\'') }} seems that this is not replacing as it should...could be that the escape char \ is not added.
we could add another round of replace replace('"', "'")

The issue seems to be partitioned_by=ARRAY["user_status"] user_status is not quoted as it should...

Yes, running the same query with single quotes make its fine.

@nicor88 I managed to build the Tomme plugin in version 0.21.0 that I was using prior and the test just works.
I take a look on the code and the part that handles the partition clause looks the same https://github.com/Tomme/dbt-athena/blame/cb081c68acfaf27f7ff8f2e53e0f20767f1490c5/dbt/include/athena/macros/adapters.sql#L25

@KleyLimaa any update on this issue? feel free to reach me out on slack dbt in order for me to gather mode details and help you out.

Since there is no activity, I am going to close it. Feel free to reopen if needed.


Initial support for Terraform v0.12.x

Thanks for @Magicloud for tackling the repo-wide upgrade! The MR has been testing well, but it's likely imperfect. I'd rather release and fix and release updates, than hold this back.

[X] Update the changelog
[X] Make sure that the linting passes on CI.

I will make the changelog.
For lint issue, where did you get it? https://gitlab.fpcomplete.com/fpco-mirrors/terraform-aws-foundation/-/jobs/12750 is the 0.12 branch built with new default-build-image. Lint seems passed.

One thing I am not sure is the hardcoded version of terraform in Makefile. Why 0.12.2 when latest release is 0.12.4? I think this also affects default-build-image. If we want to stick to a non-latest version, I'd suggest to have a KV DB to store those kind of "company preference". So every where, it is the right version.

The review system is bit of weird, so I post some comments without a link to source.
In examples/load-asg/main.tf, around line 105, you removed the TODO generated by TF. That is fine. But seems like you also removed two other comments, started with "Ensure", and "ELBs". Just to confirm it is on purpose.

And there are multiple syntax error, for example, examples/kube-stack-public/kube.tf, line 24.
It is a lint for one element list. But the closing bracket is gone.

Is the code review physically not working? It would be helpful if you could put the comments at the relevant code in the future. Thank you for the review, and you are correct, removing the TODO should not have removed the next line.

Sorry, get it working now. Posted my comments.
And for syntax error, I think I made mistake. I said multiple, but reviewing today gets only one.

@qrilka / @Magicloud ok, I have updated the branch again. Please review one last time, give approval if that is ready, and we can merge.


The push notification did not send to multiple devices!

I am using "Sending a Downstream Message to Multiple Devices".
I get the device tokens from database and pushed it to array.
$deviceTokens = array();
foreach ($following as $follow) {
if (!is_null($follow->user->account->device_token)) {
array_push($deviceTokens, $follow->user->account->device_token);
}
}
Below are the entire source code.
$business_id = $this->deal->business->id;
$following = Follow::where('business_id', $business_id)->get();
$deviceTokens = array();
foreach ($following as $follow) {
if (!is_null($follow->user->account->device_token)) {
array_push($deviceTokens, $follow->user->account->device_token);
}
}
$notification = [
'deal_id' => $this->deal->id,
'photo' => url('storage/uploads/deals/' . $this->deal->photo),
'sound' => 'default',
];
$optionBuilder = new OptionsBuilder();
$optionBuilder->setTimeToLive(60 * 20);
    $notificationBuilder = new PayloadNotificationBuilder('Featured Deal posted');
    $notificationBuilder->setBody($this->deal->description)
        ->setSound('default');

    $dataBuilder = new PayloadDataBuilder();
    $dataBuilder->addData($notification);

    $option = $optionBuilder->build();
    $notification = $notificationBuilder->build();
    $data = $dataBuilder->build();

    foreach ($deviceTokens as $token) {
        $downstreamResponse = FCM::sendTo($token, $option, $notification, $data);
    }

But the push notification did not send multiple devices.
What's wrong? Please help me.
Thank you in advince!

I think I have the same problem.

Just change
foreach ($deviceTokens as $token) {
  $downstreamResponse = FCM::sendTo($token, $option, $notification, $data);
}

to
$downstreamResponse = FCM::sendTo($deviceTokens, $option, $notification, $data);

@Abnormally thanks


dashboard 如果后台运行

nohup ./../bin/codis-config -c config.ini -L config.log dashboard >> config-dashboard.log 2>&1 &
一个sh文件写入上面的代码，执行完，程序立马结束了。
请问，dashboard如何成为后台进程

@yangzhe1991
下面是 启动 dashboard 日志里面输出的内容
2016/06/28 01:40:22 dashboard.go:144: [WARN] ********** Attention **********
2016/06/28 01:40:22 dashboard.go:145: [WARN] You should use kill {pid} rather than kill -9 {pid} to stop me,
2016/06/28 01:40:22 dashboard.go:146: [WARN] or the node resisted on zk will not be cleaned when I'm quiting and you must remove it manually
2016/06/28 01:40:22 dashboard.go:147: [WARN] *******************************
Properties below are for dashboard and proxies
zookeeper or etcd
coordinator=zookeeper
Use comma "," for multiple instances. If you use etcd, you should also use this property.
zk=<IP_ADDRESS>:2181
product=test
This addr is used for codis's proxies and commands, which should be host:port, host can not be <IP_ADDRESS> or omited.
The address/port which is listened by dashborad service whose host can be omited depends on the "--addr" in its start command arguments.
dashboard_addr=<IP_ADDRESS>:18087
password=
Properties below are only for proxies
Proxy will ping-pong backend redis periodly to keep-alive
backend_ping_period=5
If there is no request from client for a long time, the connection will be droped. Set 0 to disable.
session_max_timeout=1800
Buffer size for each client connection.
session_max_bufsize=131072
Number of buffered requests for each client connection.
Make sure this is higher than the max number of requests for each pipeline request, or your client may be blocked.
session_max_pipeline=1024
If proxy don't send a heartbeat in timeout millisecond which is usually because proxy has high load or even no response, zk will mark this proxy offline.
A higher timeout will recude the possibility of "session expired" but clients will not know the proxy has no response in time if the proxy is down indeed.
So we highly recommend you not to change this default timeout and use Jodis(https://github.com/CodisLabs/jodis)
which watches the available proxies and will skip the offline proxy or add new online proxy automatically.
If you are not using Java in client, you can DIY a zk watcher accourding to Jodis source code.
zk_session_timeout=30000
must be different for each proxy
proxy_id=proxy_1
这是配置文件

dashboard 是不是依赖文件，比如html文件，css等。我把bin目录的文件独立哪出来用来 。
@yangzhe1991

是的。依赖。把资源文件和 binary 放在一个路径下。
具体的。代码里面写了：），但是文档没写。
2016年6月28日星期二，githublaohu<EMAIL_ADDRESS>写道：

dashboard 是不是依赖文件，比如html文件，css等。我把bin目录的文件独立哪出来用来 。
@yangzhe1991 https://github.com/yangzhe1991
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/CodisLabs/codis/issues/867#issuecomment-228822679,
or mute the thread
https://github.com/notifications/unsubscribe/AAsHpfcFChZQS-ptINlCWUbzrJSicUjeks5qQA45gaJpZM4I-86C
.

已经把   assets 目录复制到，自定义codis目录下，与 codis-config  同级。还时启动失败

@spinlock
还有把cmd 目录也复制到 bin目录同级了。
启动还是报错。。要命啊

nohup 没有输出吗？
2016年6月28日星期二，githublaohu<EMAIL_ADDRESS>写道：

@spinlock https://github.com/spinlock
还有把cmd 目录也复制到 bin目录同级了。
启动还是报错。。要命啊
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/CodisLabs/codis/issues/867#issuecomment-228825216,
or mute the thread
https://github.com/notifications/unsubscribe/AAsHpcHbNLYPEyhh8hJ1vvgB5FkvPtoUks5qQBAbgaJpZM4I-86C
.

nohup 没有任何输出

先不用 nohup，能直接启动吗？

已经处理完毕。。多谢 @spinlock
不需要./ 就行了。


Fix client fetch_token throwing NoMethodError when raise_errors is set to false

The problem occurs when the identifier service is unreachable and we are passing the :raise_errors option set to false.
The fetch_token method throws NoMethodError while trying to perform the following code:
response.parsed.merge(access_token_opts)
This happens because the response.parsed is nil.

Related to opened issue: #459

Pull Request Test Coverage Report for Build 848

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 ?%

Totals

Change from base Build 847:
0.0%

Covered Lines:

Relevant Lines:
0

💛  - Coveralls

Pull Request Test Coverage Report for Build 848

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 ?%

Totals

Change from base Build 847:
0.0%

Covered Lines:

Relevant Lines:
0

💛  - Coveralls

Pull Request Test Coverage Report for Build 848

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 ?%

Totals

Change from base Build 847:
0.0%

Covered Lines:

Relevant Lines:
0

💛  - Coveralls

Hello @pboling, I was really short on time to contribute to this PR. But here you go.
My suggestion to this is to return nil when there is now way we can build the access token, which is the saying the same that !response_contains_token.
Cheers mate!

Thanks @joaolrpaulo !!

Hello @pboling, is there a possibility to add this to a new patch release in order for we to use it ?

@joaolrpaulo it would have to be backported to the 1-4-stable branch, as a second PR.

I will do it in the next few days :pray:


Evaluate custom dispatch events to reduce the need to run the action every hour

Evaluate custom dispatch events to reduce the need to run the action every hour - https://github.com/rancherlabs/updatecli-automation/pull/2#discussion_r1032425883.

Closing as currently not-planned. We can reopen and do this in the future if it makes sense by that time.


Feature: List item input click stop

now developers can have a @click event on  that will not get triggered by selection change
this PR also fixes some incorrect BEM classes on p-list-item and p-list-item-input

@stackoverfloweth this is so you could have the whole list item have a click action? That feels like a "link inside a link" which isn't a great UX or devx.
I'm thinking a click.stop also means that any global click handlers (for closing an overflow menu for example) won't be triggered.

@pleek91 I don't disagree, thoughts on just emitting a separate event for clicking on content vs clicking on checkbox? (see last commit)

Not sure what side effects having a custom event with the same name as a native event.
Also thinking, couldn't this be an implementation detail by adding a click handler to the slots content itself?

@pleek91 good call, I like that even better. I'll leave only the BEM fixes here if you wanna make that change


Added info on plugin install location

Changes
Added message to tell user plugins are in PATH and need to be moved to ~/.config/kn/plugins

:broom: Update or clean up current behavior

/ok-to-test

@navidshaikh a quick approval on this. I will remove once I am done with issues #8 #9


NFT card component

Title and Issue number
NFT card component #2096
Close #2096
Checklist:

[X] I have mentioned the issue number in my Pull Request.
[X] I have commented my code, particularly in hard-to-understand areas
[] I have created a helpful and easy to understand README.md

@MohitGupta121

@MohitGupta121 Can you please merge it?

You haven't merged it yet🥲


Default JSON collection Path

In the XRM Toolbox version of DRB, I can't figure out where the default path to JSON collection is located.
It loads a collection every time I open the plugin (I want to know which path). But if i save collection, the default path is always download folder.
Would be great to be able to select a default load / save path.

the JSON collection is stored inside localStorage (inside the browser, the XTB version uses a browser runtime to execute DRB), if the app is loading a collection every time you open mean that has been saved with "Save State" option (by right click on the collection name).
The JSON collection inside the localStorage is actually saved with a key structured as DRB_{environmenturl} so you can have a saved collection for each environment, so based on the environment you load it will show the right collection (if present).
When the collection is saved a path is not specified, it saves to the default path of the browser. If you are interested the code is this function https://github.com/GuidoPreite/DRB/blob/main/js/drb.collection.js#L139
This behavior (the load folder and the default save folder) is a standard of the browser (for security reasons they can't know that you have a D drive for example).
Can you explain why you need this behavior? it has to do with source control? Maybe I can think of an alternative way for what you need.

As this issue is opened from a week without a reply I will close it. If you have additional questions please open a new one.
Thanks


README.md references Atom forum but it's a broken link

Prerequisites

[x] Put an X between the brackets on this line if you have done all of the following:

Reproduced the problem in Safe Mode: https://flight-manual.atom.io/hacking-atom/sections/debugging/#using-safe-mode
Followed all applicable steps in the debugging guide: https://flight-manual.atom.io/hacking-atom/sections/debugging/
Checked the FAQs on the message board for common solutions: https://discuss.atom.io/c/faq
Checked that your issue isn't already filed: https://github.com/issues?utf8=✓&q=is%3Aissue+user%3Aatom
Checked that there is not already an Atom package that provides the described functionality: https://atom.io/packages

Description
There are multiple references to an Atom forum that no longer seems to exist (404 file not found)

spotted 2 references in README.md
spotted 1 reference in the bug report pre-requisite ("Checked the FAQs on the message board")

Problematic link that no longer works: https://github.com/atom/atom/discussions/

Noticed a few links to the broken forum on https://atom.io/ as well

This is an issue in the actual editor as well.
Help > Community Discussions leads to the same broken link.

Hi , if I can get the correct link I can fix this issue


Use gcc -dumpmachine to automatically derive Rust_CARGO_TARGET

gcc -dumpmachine allows you to get the target triple of the selected compiler, so it should be possible to do a reasonable job of deriving an appropriate cargo target triple from this.
Some info here: https://wiki.osdev.org/Target_Triplet

Should only apply when CMAKE_CXX_COMPILER_ID STREQUAL "GNU"

gcc target triples and clang target triples don't always match 1:1 as far as I know, so I don't think this is worth the effort.


Custom name for query type breaks client generation

If you call your query type "Queries" instead of "Query" the client is generated incorrectly.
Steps to reproduce:

Follow instructions here

Skip curl command,

Manually create schema.graphql with the following content

schema {
  query: Queries
}

type Queries {
  me: User!
  user(id: Int!): User
}

type User {
  id: Int!
  firstName: String!
  lastName: String!
  role: Role!
}

type Role {
  id: Int!
  name: String!
}

Build solution to generate client.
The client will now be missing methods on the query type.

Fixed in v2.0.0-preview.3

That was fast :)


feat: remove enrichment fields from tenant usage report

Description

Remove enrichment fields from tenant usage report

Testing required outside of automated testing?

[x] Not Applicable

Screenshots (if appropriate):

[x] Not Applicable

Rollback / Rollforward Procedure

[x] Roll Forward
[ ] Roll Back

Reviewer Checklist

[ ] Description of Change
[ ] Description of outside testing if applicable.
[ ] Description of Roll Forward / Backward Procedure
[ ] Documentation updated for Change

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Can I flash(update) the device using this lib?

Hi,
I am want update the device with new firmware. Is this library able to supporting flashing(update)?

@v2kb2l I guess it depends of whatever device you want to flash. What are you want to flash?

I would like to update bin/out file to CC1350 Launch pad using USB serial.

@v2kb2l It should be possible if it uses a serial connection for flashing but probably you have to implement the flashing protocol above UsbSerial.


Bluejeans: Add update script and <IP_ADDRESS> -> <IP_ADDRESS>

Motivation for this change
Add update script and <IP_ADDRESS> -> <IP_ADDRESS>
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
21.11 Release Notes

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Should we backport this?

I assume yes, it shows annoying popup on every app start 🤷🏻 Other than that it doesn't prevent people from using the app


HTTP Error codes custom information

When server responds with status 400, it additionally adds custom information why the request was malformed, is there any way I can extract this information?

additionally adds custom information

they are status message, headers or response body then you can
note that status 400 is still resolved, not rejected.

see readme and testcases for examples.

https://github.com/bitinn/node-fetch#usage
https://github.com/bitinn/node-fetch/blob/master/test/test.js


New maintainer wanted

Hello
I don't have time to maintain or release this project. If anyone wants to help or take over please respond below!

Hi!
I'm trying to upgrade the django-pagination version in the Read the Docs project and I found that we are using this fork in a very specific commit (probably because there wasn't a realese when this was done).
Now, I want to upgrade our dependency to the latest release of django-pagination and I found that some work has done in this repo but also in https://github.com/pydanny/dj-pagination. In fact, the repo linked here has a 2.3.2 version released (latest releases seems to be just compatibility things: http://dj-pagination.readthedocs.io/en/latest/changes.html#version-2-3-2)
What would be the correct one to use?
cc @pydanny


Fixed doc for gaussian_kde (kde.factor description)

Reference issue
gh-14217
What does this implement/fix?
This fixes the doc description of the factor attribute in stats.gaussian_kde.
Additional information
Here is the code in stats.gaussian_kde, where factor is assigned and used. Its square multiplies the data covariance matrix, to get the covariance of the Gaussian distributions used to construct the Gaussian mixture giving the kde.
    def _compute_covariance(self):
        """Computes the covariance matrix for each Gaussian kernel using
        covariance_factor().
        """
        self.factor = self.covariance_factor()
        # Cache covariance and inverse covariance of the data
        if not hasattr(self, '_data_inv_cov'):
            self._data_covariance = atleast_2d(cov(self.dataset, rowvar=1,
                                               bias=False,
                                               aweights=self.weights))
            self._data_inv_cov = linalg.inv(self._data_covariance)

        self.covariance = self._data_covariance * self.factor**2
        self.inv_cov = self._data_inv_cov / self.factor**2
        L = linalg.cholesky(self.covariance*2*pi)
        self.log_det = 2*np.log(np.diag(L)).sum()

The documentation currently reports that it is factor to multiply the covariance, not factor**2.

Hi @berberto @rgommers, thanks for posting and merging this fix. I came across this post when looking for method to set Gaussian bandwidth to a constant so that it doesn't scale with the data distirbution. It seems that the way to to it is to set bw_method=gaussian_bandwidth_value/np.sqrt(np.cov(data)), is this correct?
However, in the case where the data is 1-d array, np.cov(x) is not equal to np.var(x), as np.var(x) = np.cov(x, bias=True) where the latter's default setting is bias=False. I wonder if, in my case where x is a 1-d array, it is true that gaussian_bandwidth_value = bw_method / np.std(data)?
Many thanks!


What authority is creating accounts for the TAN web-Interface?

Your Question

Documentation File: solution_architecture.md
Line / Paragraph:

The teleTAN is then issued to the officer (4-5)

Question: Is there some documentation of who creates TAN web-interface accounts - or who counts as employee of a health authority?

This could be a potential weak point if the TANs can be generated by a malicious users. If they gains access to the TAN web-interface server they could sent false "exposure notices" to users.
Would it be possible to only allow TANs to be created when they are linked to a positive Lab result?

Hi Marco,
by definition TANs are only created once a registration token is presented to the user (see your last ticket).
TeleTANs are generated while the users are on the phone with either the health authority (they call the users upon a positive test) or when they call the hotline to request a teleTAN. And in those cases only if the users have specifically confirmed that they need a teleTAN.
There will be dedicated documentation artefacts for the Verification Server, as well regarding the Technical Security Concept and Data Privacy Concept (as mentioned in the README.md).
Best,
Thomas

Thanks for your question, @marcopashkov ! I hope that @tklingbeil 's preliminary answer and the upcoming, additional documentation answer your question. Feel free to reopen this issue, if that's not the case.


Refactor code

Description

Refactor main.rb with required changes
Create an options.file which will contain all the ui options
Create Options class in the options.rb file

Team

@utsargo
@JacintaNgwu

Hi @franclobo ,
Thanks for your review. In the project requirement, there is nothing required regarding app.rb file. Every instruction is explicitly for main.rb file. I've got your point but I think the changes you required should go under optional suggestions.


Company client

In this PR I added the company client, to get the company users, with the getCompanyUsers function we call the /user endpoint and we get the users array.

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


Application for polkadot-wallet-aggregator

Project Abstract
A Polkadot wallet aggregator connector for dapps running on Polkadot (Substrate / Polkadot / Kusama) to allow DApp developers to easily integrate all known wallet browser extensions
Answering this grant proposal : "wallet-aggregator-library RFP #1465" 1st phase (research)
Grant level

[x] Level 1:  Up to $10,000, 2 approvals
[ ] Level 2:  Up to $30,000, 3 approvals
[ ] Level 3:  Unlimited, 5 approvals (for >$100k: Web3 Foundation Council approval)

Application Checklist

[x] The application template has been copied and aptly renamed (project_name.md).
[x] I have read the application guidelines.
[x] Payment details have been provided (bank details via email or BTC, Ethereum (USDC/DAI) or Polkadot/Kusama (USDT) address in the application).
[x] The software delivered for this grant will be released under an open-source license specified in the application.
[x] The initial PR contains only one commit (squash and force-push if needed).
[x] The grant will only be announced once the first milestone has been accepted (see the announcement guidelines).
[x] I prefer the discussion of this application to take place in a private Element/Matrix channel. My username is: @tobiask:iabsis.com

 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.

Fyi: I just closed the RFP: https://github.com/w3f/Grants-Program/commit/d43ef9bb31c5f39392b5461065b58311de6d6b28

I'm closing the application. Let me know if I should reopen it.


Use detector zenith to check for cached value for IceCube-centered atmosphere

In the previous version of the IceCube-centered atmosphere, the upgoing zenith angle >90 degree has been subtracted from 180 to obtain the equivalent zenith at the surface. This value (>90 degrees) has been used to store the previous value. If one requests after a calculation for 0deg, a calculation for 180deg, and then asks again for 0 degree, it will stick to 180 degrees since the last surface zenith is 0 deg in both cases. By storing the last detector zenith instead of the surface zenith, the check for the previous value will correctly detect the change and recalculate the spline.

Maybe yes?


GA raise hand

What
StabilizingrRaise hand feature for GA
Why
For September stable release
How Tested
Process & policy checklist

[ ] I have updated the project documentation to reflect my changes if necessary.
[ ] I have read the CONTRIBUTING documentation.

Is this a breaking change?

[ ] This change causes current functionality to break.

Note there are bugs in the snapshot changes like this one:

The new snapshot adds raise hand button in the control bar and in the more button.
This is fixed in a separate PR #3561


Update awake.md

The Value to change is customTrayTimes not tray_times anymore

@mattwojo
Can you review the proposed changes?
When the changes are ready for publication, add a #sign-off comment to signal that the PR is ready for the review team to merge.
#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

@dend to verify, if he signs off i'm good

#sign-off

Thanks for this update and contribution @florianmulatz! Merged.


🤖 Fix security scans missing from master build

Signed-off-by: Itxaka<EMAIL_ADDRESS>What this PR does / why we need it:
Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #

Directly to merge as it affects master builds cc @jimmykarily


Increase SSL Renewal Notification Frequency

We should increase the frequency at which the check runs - currently we only notify the teams of certificate expiry 30 days before. This card is to update that to include a 15 day warning and a 1 day warning (to match how Gandi distributes reminders.
This would be a good opportunity to create another couple of template on GovUk Notify to cover these additional notifications.
Acceptance Criteria

[ ] Are warnings send out 15 and 1 day(s) before expiry as well as the original 30 days?
[ ] Do we have 3 total templates on Notify to explain the renewal process/thresholds?

Abandoned. The currect automated process works well with the single notification. Revisit if we have issues with renewals.


Benchmark File Unavailable

Hi, @yawen-d , Thanks for your great job!
I am interested in this Benchmark but I can't access the transnas-bench_v10141024.pth in https://www.noahlab.com.hk/opensource/vega/page/doc.html?path=datasets/transnasbench101
This link is invalid: https://box.saas.huaweicloud.com/p/b31f2ecde9d19e5261cd76d55fc0804f
Looking forward to your reply, thanks again

Same problem here. Could you please provide a valid link for downloading the file? Thanks!

Hi both! I updated the README.md to include a Google Drive Folder for the file release. Hope this helps!

Thanks! @yawen-d


Headless Export Does Not Import Files

Godot version
4.0.rc3
System information
Linux (Ubuntu Xenial)
Issue description
When running godot --headless --export with a good export target, such as godot --headless --export "Linux/X11" build/linux/godot-template-4.x86_64, there are import errors, and the build silently fails. Here's some output from my repro project:
libfontconfig.so.1: cannot open shared object file: No such file or directory
Godot Engine v4.0.rc3.official.7e79aead9 - https://godotengine.org
TextServer: Added interface "Dummy"
TextServer: Added interface "ICU / HarfBuzz / Graphite (Built-in)"
Using "default" pen tablet driver...
JoypadLinux: udev enabled and loaded successfully.

TextServer: Primary interface set to: "ICU / HarfBuzz / Graphite (Built-in)".
CORE API HASH: 170646664
EDITOR API HASH:<PHONE_NUMBER>
Loaded builtin certs
ERROR: Unable to open file: res://.godot/imported/icon.png-487276ed1e3a0c39cad0279d744ee560.ctex.
   at: _load_data (scene/resources/texture.cpp:846)
ERROR: Failed loading resource: res://.godot/imported/icon.png-487276ed1e3a0c39cad0279d744ee560.ctex. Make sure resources have been imported by opening the project in the editor at least once.
   at: _load (core/io/resource_loader.cpp:221)
ERROR: Failed loading resource: res://icon.png. Make sure resources have been imported by opening the project in the editor at least once.
   at: _load (core/io/resource_loader.cpp:221)
ERROR: res://actors/Player.tscn:3 - Parse Error: [ext_resource] referenced nonexistent resource at: res://icon.png
   at: load (scene/resources/resource_format_text.cpp:490)
ERROR: Failed loading resource: res://actors/Player.tscn. Make sure resources have been imported by opening the project in the editor at least once.
   at: _load (core/io/resource_loader.cpp:221)
ERROR: res://scenes/main.tscn:4 - Parse Error: [ext_resource] referenced nonexistent resource at: res://actors/Player.tscn
   at: load (scene/resources/resource_format_text.cpp:490)
ERROR: Failed loading resource: res://scenes/main.tscn. Make sure resources have been imported by opening the project in the editor at least once.
   at: _load (core/io/resource_loader.cpp:221)
ERROR: Failed loading scene: res://scenes/main.tscn
   at: start (main/main.cpp:2954)
XR: Clearing primary interface
XR: Removed interfaceNative mobile
XR: Removed interfaceOpenXR
ERROR: Condition "_first != nullptr" is true.
   at: ~List (./core/templates/self_list.h:106)
ERROR: 1 RID allocations of type 'N18RendererCanvasCull6CanvasE' were leaked at exit.
ERROR: 1 RID allocations of type 'N16RendererViewport8ViewportE' were leaked at exit.
ERROR: 1 RID allocations of type 'PN13RendererDummy14TextureStorage12DummyTextureE' were leaked at exit.
ERROR: 1 RID allocations of type 'N17RendererSceneCull8ScenarioE' were leaked at exit.
WARNING: ObjectDB instances leaked at exit (run with --verbose for details).
     at: cleanup (core/object/object.cpp:1982)
Leaked instance: GDScript:-9222584786529287748 - Resource path: res://autoloads/Store.gd
Leaked instance: Node:820235674321378 - Node name: Store
Leaked instance: Node:832330302226924 - Node name: GameConstants
Leaked instance: GDScript:-9222549052401384979 - Resource path: res://lib/util/GDUtil.gd
Leaked instance: GDScript:-9222559497761848850 - Resource path: res://constants/ClientConstants.gd
Leaked instance: Node:829031767343599 - Node name: GDUtil
Leaked instance: Node:830681034785265 - Node name: ClientConstants
Leaked instance: SceneReplicationInterface:-9222589184575798788
Leaked instance: StreamPeerBuffer:-9222589734331612675
Leaked instance: SceneMultiplayer:-9222590284087426562
Leaked instance: World3D:-9222590833843240449 - Resource path:
Leaked instance: Object:780653255721477
Leaked instance: ViewportTexture:-9222591933354868212 - Resource path:
Leaked instance: World2D:-9222592483110682099 - Resource path:
Leaked instance: Window:779003988279826 - Node name: root
Leaked instance: SceneTree:778454232465939
Leaked instance: GDScript:-9222556199226965405 - Resource path: res://constants/GameConstants.gd
Leaked instance: GDScriptNativeClass:-9222938279517617563
Leaked instance: OfflineMultiplayerPeer:-9222587535308356403
Leaked instance: SceneCacheInterface:-9222588085064170287
Leaked instance: SceneRPCInterface:-9222588634819984174
Hint: Leaked instances typically happen when nodes are removed from the scene tree (with `remove_child()`) but not freed (with `free()` or `queue_free()`).
ERROR: Resources still in use at exit (run with --verbose for details).
   at: clear (core/io/resource.cpp:489)
Resource still in use: res://autoloads/Store.gd (GDScript)
Resource still in use: res://constants/ClientConstants.gd (GDScript)
Resource still in use: res://constants/GameConstants.gd (GDScript)
Resource still in use: res://lib/util/GDUtil.gd (GDScript)
Orphan StringName: tree_changed
...

There are hundreds of Orphan... lines, but nothing after. No build is exported.
Steps to reproduce

Download project
godot --headless --export

Minimal reproduction project
https://github.com/Bloodyaugust/godot-template/archive/refs/heads/godot-4.zip

Steps I have tried to fix this:

creating .godot/imported folder before executing (shouldn't be necessary in rc3, but I wasn't seeing it create the .godot directory either)
running timeout 60 godot --headless ahead of attempting to export

Another interesting tidbit: after using the .godot directory from a different windows machine (still using rc3, successfully builds), the export doesn't spout errors but instead hangs forever.

--export is not valid in 4.0, it's either --export-release or --export-debug.
It works fine for me with 4.0 RC 3 using:
Godot_v4.0-rc3_linux.x86_64 --headless --export-debug "Linux/X11" build/linux/godot-template-4.x86_64

after creating build/linux manually as the target folder needs to exist, Godot doesn't create the whole path if missing.
I'll add a hint when using --export to help users migrating from Godot 3.x, but it's not a bug.

You need to use the workaround described in https://github.com/godotengine/godot-proposals/issues/1362.

You need to use the workaround described in godotengine/godot-proposals#1362.

The workaround doesn't seem to work. My CICD process runs these commands in order:
godot --headless --editor --quit
godot --headless --export-release linux64 ../export/linux64/project.x86_64

After godot --headless --editor --quit, the .godot/imported directory is still empty. Is it quitting too soon? The --export-release command returns exit code 0 but creates no packs or executables.
Doing this instead (exporting twice) gets further:
godot --headless --export-release linux64 ../export/linux64/project.x86_64
godot --headless --export-release linux64 ../export/linux64/project.x86_64

I also cannot seem to get .godot/imported to populate with any of the workarounds mentioned on 4.2.1-stable. I've resorted to unignoring .godot but if would love to know if someone's got this to work in any other ways!


Feature request: verbose input parameter

What about having verbose input parameter such that verbose=1 would print the progress using the ErrorLogger() callback but also showing what happens before (kNN index construction, affinity calculation, etc.) and giving the times taken by the each stage?

Yes, this is a good idea. I've had this on my mind for a while now. It will be included in the release.


standardise on UPPERCASE for type0..type2 as per docs

The specified TYPE should standardise to be uppercase as explained in the earlier text. It is incorrect to assume that all MSSQL instances or individual databases have Case-insensitive collation!
P.S. you will have to merge my earlier PR9568

@markingmyname

Can you review this PR?
IMPORTANT: When this content is ready to merge, you must add #sign-off in a comment or the approval may get overlooked.

#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

Thanks for your contribution.
I'm confused, though. On the one hand, you remove the N'' prefix from a number of places, and on the other you leave the prefix there and only change the casing. You also spread your changes across two PRs on the same lines in the same file, making this incredibly difficult to parse.
I'll have to speak to a member of the product group, which means these two PRs will have to be merged manually, and only reviewed next year when everyone is back.

After careful review, I figured out what your intention was. There are three articles affected by your suggestions, so we'll publish an internal PR that includes your suggested changes.
Thanks again for your contribution.

 Will progress on your internally worked up correction (3 articles) notify me via this PR9569 so I can see satisfactory conclusion ?Tks


Tm12

PR Description 📜
I addressed the issue regarding the start and restart buttons, which initially seemed to be malfunctioning. However, upon closer inspection, it became apparent that they were functioning as intended. The only concern was the lack of visual feedback to indicate when the game was starting and ending. Consequently, I updated the functionality of both buttons to provide clear visual cues, ensuring users understand precisely when the game begins and concludes.
Fixes # <3198>

Mark the task you have completed ✅

[x] I follow CONTRIBUTING GUIDELINE & CODE OF CONDUCT of this project.
[x] I have performed a self-review of my own code or work.
[x] I have commented my code, particularly in hard-to-understand areas.
[x] My changes generates no new warnings.
[x] I have followed proper naming convention showed in CONTRIBUTING GUIDELINE
[ ] I have added screenshot for website preview in assets/images
[ ] I have added entries for my game in main README.md
[ ] I have added README.md in my folder
[ ] I have added working video of the game in README.md (optional)
[ ] I have specified the respective issue number for which I have requested the new game.

Add your screenshots(Optional) 📸

Thank you soo much for contributing to our repository 💗

Hey @Tasnuva12,
Please make sure to link the relevant issue using the appropriate syntax, such as "#issueNumber" 👀.
Follow the proper guideline and make a new PR again 😀.
Happy Hacking 💗

Thank you  @Tasnuva12 , for your valuable time and contribution in our GameZone 💗.
It’s our GameZone, so Let’s build this GameZone altogether !!🤝
Hoping to see you soon with another PR again 😇
Wishing you all the best for your journey into Open Source🚀


fix alchs staying filtered when you alch an item

This fixes #12. Tagging @RedSparr0w as the person who introduced this bug in case my fix breaks something else I'm not aware of.
After #11, the inventory would remain filtered after alching an item until another click was provided. This was convenient visually if you were spam-alching, but it was annoying for the reasons specified in #12 - namely, alching an item then using Fkeys to get back to the inventory left things filtered.
This was because after switching to .contains, the second half of the alch action (selecting an item) was also captured as "still alching". Reverting this part of the logic for determining when you're alching resolves the issue.
The first screenshot captures what isAlching captured before #11 and will capture again once this PR is merged.
The second shows the part of the process that should not be captured that #11 added into the equation.

Tested with explorer's ring and normal high alchemy to make sure nothing broke, worked for me. Found a couple new bugs I'll file issues for (related to explorer's ring, weird edge cases that should rarely if ever affect anyone). But tested on base RuneLite and those were not introduced by this PR.
(edit: import changes were automatically done by my vscode config, couldn't figure out how to disable it but figured it wasn't a problem. if it is, can tweak that upon request)

@robrichardson13 - is this repository still maintained? tried to reach out on discord, will start asking runelite folks if we can get maintainership transfered if needed.


Missing link to JSON field on Fields Overview page

Documentation Issue
The fields overview documentation page has a list of field types, but the JSON field is not listed.
Is there a way for me to edit the documentation? If not, could you please add a link?

Yes, if you want to change the docs fork this repo and make changes to the mdx files in /docs and open a pull request.

Thank you, @DanRibbens. Pull request here: https://github.com/payloadcms/payload/pull/4989

Thanks! Closed by #4989


Works on XiaoXin 14 Pro 2024 (Chinese Ideapad 5 Pro 14AHP9)

All features work. Thank you for your development.

Ideapad 5 Pro 14AHP9 sold by lenovo, everything works too.


{storage-preview} Refine test with upgraded api version

This checklist is used to make sure that common guidelines for a pull request are followed.

For new extensions:

[ ] My extension description/summary conforms to the Extension Summary Guidelines.

About Extension Publish
There is a pipeline to automatically build, upload and publish extension wheels.
Once your PR is merged into master branch, a new PR will be created to update src/index.json automatically.
The precondition is to put your code inside this repo and upgrade the version in the PR but do not modify src/index.json.

storage-preview

/azp run

/azp run


Developer Portal > Deploy > SAP Cloud Platform

Rewrite of documentation with new screenshots and additional information
Update to Deployment > SAP Cloud Platform to encourage users to use the Developer Portal

Needs review by DES before merging to development


Fix var scoping on proxy function (fixes #50)

cc/ @bajtos

Interesting. I don't fully understand what is happening here, but as long as the fix solves then problem, then it LGTM.
Can you add a unit-test to verify the fix and prevent regressions in the future?

It's a pure js edge case sort of thing, not something specific to fsevents. In the previous for loop code, the value of key was getting bound as start inside that inner function for either method. It has to do with the fact that for statements do not create a closure, while a forEach callback does.
Using bind on the function to pass the correct value of key as an arg could have been an option except in this case where there was no appropriate value to be bound as this in the same place. Anyway, there are other ways this could have been refactored to fix the issue, but I tend to favor the functional approach of the ES5 array methods.

It's a pure js edge case sort of thing, not something specific to fsevents. In the previous for loop code, the value of key was getting bound as start inside that inner function for either method. It has to do with the fact that for statements do not create a closure, while a forEach callback does.

Of course! How could I missed that (facepalm).
Thank you for writing up the explanation.

Regarding a unit test for this, something is failing in the current test script (I'm not sure what), which I think would need to be fixed before I could effectively add assertions around where .stop() is called.
(sorry for the double-notification, accidentally posted this in the wrong thread before)

ping @bajtos @bnoordhuis
Now that you have control, can we get this fix pushed out?

LGTM.  My only nit is the commit log, I like it to explain what the author changed and why.  That said, I'm happy to hand it off to @bajtos and have him be the supreme judge. :-)

I am ok with the current commit message, as it has a link to the issue where more details can be found. I know tt's not perfect when doing code archaeology offline, but then my experience is that I almost never need to dig through the history in small projects with little activity (like this one).

FWIW, I need to sort out npmjs ownership before I can publish a new version with this fix.
@pipobscure could you please run npm owner add bajtos fsevents? Otherwise I'll have to wait for my colleagues in Bay Area to run that command as strongloop user.

Released as v0.3.5.


rubocops/text: forbid "go get" only in install method

[ ] Have you followed the guidelines in our Contributing document?
[ ] Have you checked to ensure there aren't other open Pull Requests for the same change?
[ ] Have you added an explanation of what your changes do and why you'd like us to include them?
[ ] Have you written new tests for your changes? Here's an example.
[ ] Have you successfully run brew style with your changes locally?
[ ] Have you successfully run brew typecheck with your changes locally?
[ ] Have you successfully run brew tests with your changes locally?

Idea from here: https://github.com/Homebrew/homebrew-core/pull/89377#discussion_r748841562
This is not tested though.

Review period will end on 2021-11-16 at 00:00:00 UTC.

Review period skipped due to critical label.


Properly auto-detect PUBLIC_IP when omitting from docker-compose.yml

Have you read the Important information text above

[X] Yes i did

Current behavior
When omitting PUBLIC_IP from docker-compose.yml, it is not auto-detected and instead the PublicIp value in /game/Pal/Saved/Config/LinuxServer/PalWorldSettings.ini set to <IP_ADDRESS>.
For users, it is a bit hard to follow what the actual behavior of the container will be since the docs for PUBLIC_IP contradicts itself by stating auto-detect if not specified while also stating that the default value is <IP_ADDRESS>. No auto-detection is taking place.
Desired behavior
Proper auto-detection of PUBLIC_IP
Two steps to this below.
Remove default value for PUBLIC_IP
Remove <IP_ADDRESS> as the default value from Dockerfile:
https://github.com/jammsen/docker-palworld-dedicated-server/blob/ee23b8807b280d2787af71ab18cfb7a0cc51b577/Dockerfile#L16
Reasons for this:

<IP_ADDRESS> is slightly misleading as a default PUBLIC_IP since the <IP_ADDRESS>/8 IP ranges are specially reserved for private networks. It's not a sensible default. In general, there really is no sensible default for PUBLIC_IP, which is why I'm opting for it to be removed as a default entirely.
Omitting PUBLIC_IP will line up with the Setup for community server. instructions:

You can manually specify the global IP address of the network on which the server running. If not specified, it will be detected automatically. If it does not work well, try manual configuration.

Instead of defining a default, the value can be dynamically populated when the container starts (see below).

Allow PUBLIC_IP to be detected and set dynamically
Add ability to set PUBLIC_IP environment variable to auto and make this the default value/behavior as currently noted in the README. This will automatically detect the network's public IP and set it in the game config. This is particularly useful for networks that do not have static IPs, as it removes the manual effort of reflecting changes to the public IP in docker-compose.yml. Even for networks with static IPs, it removes a manual step in the initial setup process.
General flow can go like this:

Container is started and servermanager.sh script is run.
startServer() is called and checks if PUBLIC_IP is either not set or set to the string auto.

If either of these expressions are true, execute command curl ifconfig.me to retrieve public IP address and replace PublicIp config value with this IP in /game/Pal/Saved/Config/LinuxServer/PalWorldSettings.ini.
If something other than auto is defined for PUBLIC_IP, use that for the PublicIp config value.

Links to screenshots
No response
To Reproduce
Steps to reproduce the behavior:

Fresh clone or install of the repo, or remove cached images for the docker-compose project and set PublicIp to "" in game/Pal/Saved/Config/LinuxServer/PalWorldSettings.ini.
Remove PUBLIC_IP env variable from docker-compose.yml
docker-compose up -d wait for server to start (monitor with  docker-compose logs -f)
Run command cat /game/Pal/Saved/Config/LinuxServer/PalWorldSettings.ini (or wherever your config file is located), PublicIp will have been overridden to <IP_ADDRESS>.

Software setup

OS: Slackware 15.0 x86_64 (post 15.0 -current)

i.e. Unraid 6.12.6

Docker: Docker version 20.10.24, build 297e128

Hardware setup

vCPU: 12
RAM: 104 GiB
Disk: 1 TB

Additional context
I'm happy to write a PR for this but I wanted to get your input beforehand.

Hey @Jarvl
What you need to set is:
    environment:
      ...
      - PUBLIC_IP=
      - PUBLIC_PORT=8211
      ...

This works flawless, when i just tested this. Of course the default set of the Dockerfile will be used when you dont set something else in Docker-Compose, thats suppose to happen.

@Jarvl Did this help?

Please keep in mind that the community server search is limited to 200. It querys only the 200 search entrys, so you may need to load the next 200 entrys (bottom right Button). This is a known bug in Palworld.

This issue should be solved