Add a way to add a website quickly to a blacklist

Perhaps from a hotkey or from the menu bar option.
Currently I can ignore tab but that is not very useful since on some sites Nightlight is broken. I would like to blacklist those sites quickly.
Thank you.

Also for some reason, option + N, O are not working at all for me. :(

Do you find yourself adding to the blacklist often, or is it more of a one-time pain point?

Actually you are right, it's not that common to add a website to blacklist, it's easier to just turn off nightlight for that website temporarily and have a blacklist only for most common sites. :)


How practitioners perceive the relevance of software engineering research

http://dl.acm.org/ft_gateway.cfm?id=2786809&ftid=1615641&dwn=1&CFID=725641379&CFTOKEN=87982003

This paper has been performed as a survey at Microsoft. And they do not provide any data set


More consistent error reporting on new GRPC API

From #383
When a RPC to subscribe() fails, all we get back is a gRPC status code e.g. StatusCode.INVALID_ARGUMENT(3) with details set to "NotFound".
SubscribeResponse does not yet have an Error field which means that only the gRPC error tells us whether something bad happened.
In order to have VISS-compatible error information, I think we would need to have a serialized-as-string Error message behind the 'details' attribute of the gRPC error (see https://github.com/grpc/grpc/tree/master/examples/python/errors).
We need to return "descriptive" error messages as mich as possible, and preferably having VISS/HTTP-style status codes where it makes sense.
It seems it makes sense to give SubscribeResponse an Error field for consistency, but we may also want to check how to make better use gRPC error mechanism
Adding @argerus @romainletendart  to the discussion

Here are some extra inconsistencies I noticed which could be addressed as part of fixing this issue:

Set() databroker implementation does not fill in 'error' proto field, only 'errors'.
Get() databroker implementation wrongly escapes paths within error/errors messages.
Get() and Set() error message formats are inconsistent for the same kind of error (404).

Where it makes sense we should use VISS error codes and reasons https://www.w3.org/TR/viss2-transport/#status-codes when we intend to express the same semantic

Here's another inconsistency:
When getting the current value for an unknown Data Entry (No.Such.Path), the databroker's response contains a global error with code 404.
However, when setting the current value for an unknown Data Entry (No.Such.Path), the databroker's response contains a Data Entry specific error with code 404 but no global error.
In general, it is quite unclear what kinds of error codes to expect in the response message under what circumstances because the proto file only covers syntax but (almost) no semantics.

We are about to archive this repo soon. If you consider this issue as important please file a new issue at one of the new Kuksa repos at https://github.com/eclipse-kuksa


Skill issue

ср, 4 янв. 2023 г., 11:36 Nikolay Tsay @.***>:

Closed #17 https://github.com/nikolay-tsay/AccounteeApi/issues/17 as
completed.
—
Reply to this email directly, view it on GitHub
https://github.com/nikolay-tsay/AccounteeApi/issues/17#event-8149887904,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AYWIF7J5BKECIJ7AFIZUGH3WQVHBVANCNFSM6AAAAAATQQG4NA
.
You are receiving this because you authored the thread.Message ID:
@.***>


Does "Independant" mean decoupled from facebook's libraries and tech

After the recent licensing issues with Facebook's BSD + Patents license the company I work for is very hesitant to use any of their libraries. However we still wish to make use of the GraphQL standard as it seems to be the way of the future. So my question is, does "independent" mean that this repository has no dependencies on Facebook libraries?

It means "agnostic" but yes, it does not depend any Facebook library.


how to remove the dead zone?

tell me how to remove the dead zone, resulting in a preview image before cropping?

dead zones I noted in the screenshot "this".

Change the view mode?
Checkout the 'VM3' button at the right side menu.
http://fengyuanchen.github.io/cropperjs/

If you had read this part of the documentation, you will not get this problem.
Just a CSS problem:
/* Limit image width to avoid overflow the container */
img {
  max-width: 100%;
}

Thank you, it worked


Syncer(DM): alerting enhancement for DM sync process exists with error

Is your feature request related to a problem?
We have retry for downstream bad connection.Some time  we would got some altering but the task had already resumed.
[2022/08/10 08:07:18.088 +08:00] [INFO] [subtask.go:292] ["unit process returned"] [subtask=ames-syncer-207] [unit=Sync] [stage=Paused] [status="{\"totalEvents\":71594423,\"totalTps\":486,\"recentTps\":241,\"syncerBinlog\":\"(log-bin|000001.019314, 409540520)\",\"binlogType\":\"local\"}"]
[2022/08/10 08:07:18.088 +08:00] [ERROR] [subtask.go:311] ["unit process error"] [subtask=ames-syncer-207] [unit=Sync] ["error information"="{\"ErrCode\":44008,\"ErrClass\":\"schema-tracker\",\"ErrScope\":\"downstream\",\"ErrLevel\":\"high\",\"Message\":\"startLocation: [position: (, 0), gtid-set: ], endLocation: [position: (log-bin|000001.019314, 409542651), gtid-set: ]: cannot parse downstream table schema of `xxx`.`xxxx` to initialize upstream schema `xxxx`.`xxxx` in schema tracker\",\"RawCause\":\"driver: bad connection\"}"]
[2022/08/10 08:07:18.279 +08:00] [INFO] [relay.go:683] ["flush meta finished"] [component="relay log"] [meta="master-uuid = 0-163.000001, relay-binlog = (log-bin.019314, 409682882), relay-binlog-gtid = "]
[2022/08/10 08:07:18.586 +08:00] [INFO] [worker.go:476] ["auto_resume sub task"] [component="worker controller"] [task=ames-syncer-207]
[2022/08/10 08:07:18.586 +08:00] [INFO] [subtask.go:525] ["resume with unit"] [subtask=ames-syncer-207] [unit=Sync]
[2022/08/10 08:07:18.586 +08:00] [INFO] [task_checker.go:401] ["dispatch auto resume task"] [component="task checker"] [task=ames-syncer-207]

Describe the feature you'd like
Because of the retries, it seems that there is no need for such frequent alerts,
Describe alternatives you've considered
No response
Teachability, Documentation, Adoption, Migration Strategy
No response

alert: DM_sync_process_exists_with_error
expr: changes(dm_syncer_exit_with_error_count[1m]) > 0
labels:
env: ENV_LABELS_ENV
level: critical
expr: changes(dm_syncer_exit_with_error_count[1m]) > 0
annotations:
description: 'cluster: ENV_LABELS_ENV, instance: {{ $labels.instance }}, task: {{ $labels.task }}, values: {{ $value }}'
value: '{{ $value }}'
summary: DM sync process exists with error


Please update the changelog

Please update the changelog for v2.0.1: it is stuck at 1.1.0.RC1

+1

@xtianus, I found it!
https://spring.io/blog/2015/04/27/spring-social-facebook-2-0-1-released
https://jira.spring.io/secure/ReleaseNote.jspa?projectId=10607&version=14996


WebAuthn gives error: "Failed to execute 'atob' on 'Window': The string to be decoded is not correctly encoded."

Hello! I have the error when logging in with Webauthn or when adding a WebAuthn device.
Casdoor Version: v1.281.0
Browser Google Chrome Version: 111.0.5563.146
How to reproduce:

Go to login page
Select WebAuthn
Enter username
Click Sign in button
Getting error in browser console:
Uncaught (in promise) DOMException: Failed to execute 'atob' on 'Window': The string to be decoded is not correctly encoded.  at rO (https://casdoor.vitim.io/static/js/main.a301da6f.js:2:3740754)  at https://casdoor.vitim.io/static/js/main.a301da6f.js:2:3909520
Step 4 and 5 can be repeated many times

Or another scenario:

Go to user profile
Click Add webauthn device button
Getting error notification: "Failed to connect to server: InvalidCharacterError: Failed to execute 'atob' on 'Window': The string to be decoded is not correctly encoded.."

Recording how to reproduce it:
out_webauthn.webm

@wsolara hi, can you check starting from which release version this problem happens?

hsluoyz, ok, I'll try

@wsolara hi, can you check starting from which release version this problem happens?

hsluoyz Hello, I checked, in versions 1.260.0, 1.261.0 there is no such error, starting from version 1.262.0 there is an error

@wsolara are you sure that this PR: https://github.com/casdoor/casdoor/pull/1623 has caused this issue? I don't think that one line change has anything to do with WebAuthn..

ping @wsolara

@wsolara are you sure that this PR: #1623 has caused this issue? I don't think that one line change has anything to do with WebAuthn..

hsluoyz I can see from the commits that the webauthn library was changed here - https://github.com/casdoor/casdoor/compare/v1.261.0...v1.262.0

@wsolara yes, good catch. We updated the webauthn library at that time and perhaps this action introduced this bug.
The original commit is: https://github.com/duo-labs/webauthn/commit/a22482edaa3b
It is changed to: https://github.com/go-webauthn/webauthn/releases/tag/v0.8.2
Actually go-webauthn/webauthn is forked from duo-labs/webauthn. So can you check starting from which commit of go-webauthn/webauthn repo this issue happens? You can use binary-search. This will help us locate the problem.

@wsolara yes, good catch. We updated the webauthn library at that time and perhaps this action introduced this bug.
The original commit is: duo-labs/webauthn@a22482edaa3b
It is changed to: https://github.com/go-webauthn/webauthn/releases/tag/v0.8.2
Actually go-webauthn/webauthn is forked from duo-labs/webauthn. So can you check starting from which commit of go-webauthn/webauthn repo this issue happens? You can use binary-search. This will help us locate the problem.

ok

@wsolara yes, good catch. We updated the webauthn library at that time and perhaps this action introduced this bug.
The original commit is: duo-labs/webauthn@a22482edaa3b
It is changed to: https://github.com/go-webauthn/webauthn/releases/tag/v0.8.2
Actually go-webauthn/webauthn is forked from duo-labs/webauthn. So can you check starting from which commit of go-webauthn/webauthn repo this issue happens? You can use binary-search. This will help us locate the problem.

Ok, I will try

I have tried using different versions of webauthn, and it seems that versions from this commit onwards can trigger this bug. To address this bug， you can specify the version of webauthn as v0.5.0 or an earlier in the go.mod file of casdoor. I will continue to investigate what has caused this problem.


Ensure all the dependency injection methods are accurately represented

There are now three, if my understanding serves me correctly:

accepting the services as parameters in your constructor
accepting the services as fields of your primary Plugin class (it is automatically initialised)
initialising another class with pluginInterface.Create to populate its static fields

Creation and injection of your own services and classes:
var poop1 = di.Create<PoopyClass>(myServiceA, myServiceB);
var poop2 = di.Inject(poopInstance, myServiceA, myServiceB);


Distraction-free mode should show task list on "jump-to" action

When a user invokes jump-to, he/she actually does want to keep the task list visible, but distraction-free mode hides it. Can this be adjusted?

This one is covered now.

Works great, thank you!

I just noticed that calling any dialog that has a numbered list (such as "Load template", "Load search", etc) and then hitting : to jump to an item breaks distraction-free mode.

Hm, right. That actually makes sense… try with ab8984da!

Works now, thank you!


Alias for getPrevalentTaxa

The getPrevalentTaxa can be useful function also for other assays and omics. I suggest to add an alias: getPrevalentFeatures

Good idea. Should we also consider aliases for other *taxa functions?

getTopTaxa
getUniqueTaxa
countDominantTaxa
getPrevalentTaxa
getRareTaxa
subsetByPrevalentTaxa
perSampleDominantTaxa
addPerSampleDominantTaxa

Yes.


Summary blocks

Add summary blocks for public methods to explain what they do for the consumer.

This is dependent on #19 .


numColumns Not working V1.6.1

I downloaded version 1.6.1 and numColumns didn't work, i downgraded version 1.6.0 and it worked properly

I had this problem too. It was fixed when I reverted to version 1.6.0.
"react-native": "0.71.7",

I've seen this issue with this setup as well:
"react-native": "0.72.5",
 "react-native-big-list": "^1.5.4",

I've tried several later versions of this library but none seem to work with version 72 of RN

I've seen this issue with this setup as well (using a sections list):
"react-native": "0.72.5",
"react-native-big-list": "^1.5.4",

I've tried several later versions of this library but none seem to work with version 72 of RN

Was anyone able to get this working?


OneClick add parameter for data set name

When sending data to CartoDB OneClick, it would be great if we could specify a file name for the imported data. When we are sending over data from a generated GeoJSON endpoint (WFS), the default naming isn't that great of a user experience.

Is this Issue solved? Can it be closed?

Nope, we never resolved it on our end.. Just hoping for a CartoDB feature request :pray: .... I think it would definitely enhance the CartoDB user's experience with user's importing data from OneClick. Without allowing metadata (titles) to come along with the dataset it can potentially convolute a CartoDB user's dataset's dashboard when importing many files.

Seems like a duplicate of #4607

There has been no activity on this issue for more several months. We are closing it. If you think this still needs to be addressed please open a new issue.


beamdurationseconds

The light doesn't turn on with beamdurationseconds over 32500.

Thanks for the info! I didn't test the upper bounds, but that's right at 9 hours.  Seems like a pretty smart maximum since the most of the lights are battery powered.  I'll add some information to the readme.  Anything else you think we should do?

Added it to the readme and put a check in place.  Now if you set the value too high, it will use the max allowed value (32767).  Thanks for bringing the issue to my attention!

Thank you! Is it possible to disable this timeout altogether?

Unfortunately that limit is coming from Ring, not from anything on my end.  If 9 hours isn't quite enough, you could probably add a second automation that would run in the middle of the night.  So at sunset, turn on the light for 9 hours.  Then at 1am turn it on for 9 hours again (which would basically just reset the duration timer).  Then at sun rise turn it off.

Thanks a lot! Your solution worked perfectly.


Typos y errores de traducción - typos and translation errors

Some small typos and translation errors
Algunos errors de tipeo y traducción pequeños

[x] I have read freeCodeCamp's contribution guidelines.
[x] My pull request has a descriptive title (not a vague title like Update index.md)
[x] My pull request targets the master branch of freeCodeCamp.
[x] None of my changes are plagiarized from another source without proper attribution.
[x] My article does not contain shortened URLs or affiliate links.

If your pull request closes a GitHub issue, replace the XXXXX below with the issue number.
Closes #XXXXX

@GonzaloGM Thanks for making these corrections! 👍 🌋


swift 3?

Please checkout the swift_3.0  branch for  Swift 3.0 support. Please check and  let me know if you need help from me.


[3.0.0-beta.1] adaptive themes not working when destructuring theme object

Description
I create new project then add this library. I turn adaptiveThemes on.
I create stylesheet like this:
const styles = StyleSheet.create(({colors}, {screen: {width}}) => ({
  container: {
    paddingHorizontal: 16,
    rowGap: 5,
  },
  fill: {
    flex: 1,
  },
  row: {
    flexDirection: 'row',
    columnGap: 5,
  },
  box: {
    width: (width - 32 - 7 * 5) / 8,
    height: (width - 32 - 7 * 5) / 8,
    backgroundColor: colors.accent,
  },
}));

when switch os theme. UI not update. But when I use:
StyleSheet.create((theme

instead :
StyleSheet.create(({colors}

It's working.
Steps to Reproduce
You can clone repo then follow this video:
https://github.com/user-attachments/assets/d39aff2a-09d3-4d95-b621-011becf17918
Snack or Repository Link (Optional)
https://github.com/ngocle2497/Unistyles-issue-adaptiveThemes
Unistyles Version
3.0.0-beta.1
React Native Version
0.76.5
Platforms
iOS
Expo
None

Hey 👋🏼 this is currently not supported in babel plugin. You need to use theme or rt directly to detect dependencies. It can be improved so I will keep it as a reference.


query for timelaps

hi mate, sorry for the noob question, but i noticed that the laptimes are incomplete, how can transform thats values in the times for each completed laps? I read in the pdf that the ibt files are updated every 60 seconds, so I think that's why the laps are incomplete.
https://prnt.sc/cs9hf2puTCds
https://forums.iracing.com/discussion/62/iracing-sdk/p1
https://us.v-cdn.net/6034148/uploads/8DD84H30FIC8/telemetry-11-23-15.pdf

You are correct that the YAML is only updated every X seconds.
It's been a while since I worked with the telemetry, but you should be able to calculate the lap times. It would probably be best to ask on the official iRacing forum on how best to do this with the "disk" telemetry. Using live telemetry (which this library doesn't support), it would be possible to calculate it using the values in the lower section around "CarIdxEstTime" etc

Just noticed your username, I happen to be visiting Japan until Saturday. Been a wonderful time in this country 🇯🇵

Ahh yes, Japan is a wonderful place for sure, I lived there for most of my life and enjoyed it a lot


[move-lang] Change address value syntax.

Change address value syntax from 0x to @<num>
0x hex values are now numbers
Makes room for named addresses

Motivation

@ allows for @ syntax for named addresses without shadowing issues from locals or constants

Test Plan

TODO

Change address value syntax from 0x to @

From the code changes in the PR, it looks like 0x -> @0x--expected?

Change address value syntax from 0x to @

From the code changes in the PR, it looks like 0x -> @0x--expected

Bad rendering of the grammar comment in github. Should be @<num>. Numbers (u8, u64, u128, or no suffix) can now be hex or decimal, so  <num> can be things like 255 or 0xFF. Addresses are then @<num> with no suffix on the number.

Doe

Change address value syntax from 0x to @

From the code changes in the PR, it looks like 0x -> @0x--expected

Bad rendering of the grammar comment in github. Should be @<num>. Numbers (u8, u64, u128, or no suffix) can now be hex or decimal, so <num> can be things like 255 or 0xFF. Addresses are then @<num> with no suffix on the number.

Does that mean this
 public fun DIEM_ROOT_ADDRESS(): address {
        @0xA550C18
 }

could also be written as
public fun DIEM_ROOT_ADDRESS(): address {
        @A550C18
}

could also be written as
public fun DIEM_ROOT_ADDRESS(): address {
        @A550C18
}

No, I don't think so. Without the 0x prefix, the "number" is expected to be a decimal value, and A550C18 is not a valid decimal number. But, you could use @173345816 as the equivalent decimal representation of 0xA550C18.

/land

/cancel
we have a sev3 fix and need to cut the line

/land


chore: bump to Aspect CLI 5.8.19

Also green up Windows CI

Replaced by https://github.com/aspect-build/rules_esbuild/pull/176


Add-GSDrivePermission does not support fileOrganizer role for Team Drives

Describe the bug
Team Drives support a "Content Manager" role, which is called "fileOrganizer" in the API. However, PSGsuite currently does not support this role.
To Reproduce

Add-GSDrivePermission -User<EMAIL_ADDRESS>-FileId TeamDriveID -role fileOrganizer -Type User -EmailAddress<EMAIL_ADDRESS>
Expected behavior
The role should be added to the Team Drive.
Environment (please complete the following information):

OS:  Ubuntu
PowerShell Version:  Core 6.2.0
PSGSuite Version:  2.26.2

Additional context
In Add-GSDrivePermission.ps1, updating line 88 to include fileOrganizer in the ValidateSet, and updating line 168 to:
$body.$key = ($PSBoundParameters[$key]).ToLower().Replace("fileorganizer","fileOrganizer")
should do the trick (it works in my local environment). It seems the underlying API unfortunately requires the uppercase O.

Thank you so much for the detailed analysis and quick fix! Google is definitely sensitive when it comes to casing, camelCase all the things. I'll add it in asap!

hey @aitcriver - you should be good to go now on the latest version. Try it out and let me know!


Add url configuration handler

Adding an url configuration handler similar to request configuration handler which is useful to handling custom url modification.
Changes are also made to have the cache keys reflect the url modification.

          1 Warning

:warning:
Any source code changes should have an entry in CHANGELOG.md or have #trivial in their title.

  Generated by :no_entry_sign: Danger


Macro cfg! cause function "from_gentry" won't get compiled when Features set to "manifest" but not "gantry"

https://github.com/wascc/wascc-host/blob/8f7ddea6d583f52f94300f78b4fa0c566d0403fc/src/lib.rs#L340
Suggest to use #[cfg(feature="gantry")] instead of if cfg!(feature = "gantry") to skip this line at the compile time.
The Rust document on macro cfg! is not clear. Related bug is here https://github.com/rust-lang/rust/issues/38928
At compile time, the code is expended to something like this:
            if false && actor.len() == 56 && actor.starts_with('M') {
                // This is an actor's public subject
                self.add_actor(Actor::from_gantry(&actor)?)?;
            } else {
                self.add_actor(Actor::from_file(actor)?)?;
            }

Of course, the Actor::from_gentry() won't have a chance to run, but it cannot pass compile either.

thank you for your fixing


Small install process note

There is a "sanity check" at the top of ledisdb/dev.sh:
if [[ "$LEDISTOP" == "${LEDISTOP/\/src\/github.com\/siddontang\/ledisdb/}" ]]; then
    echo "WARNING: LEDISTOP($LEDISTOP) does not contain src/github.com/siddontang/ledisdb"
    exit 1
fi

The issue is with that exit command.
Installation guide in the README suggested to source this file, so this exit leads to surprisingly closed shell session. You, probably, should use return instead.
Well, may be MacOS doesn't close window till you manually close it, but Ubuntu does.
It's a rather cosmetic issue, but may be a first frustrating impression for newcomers.
I tried to replace exit with return on my local copy (Ubuntu 14.04.3 LTS, GNU bash, version 4.3.11(1)-release), it works as expected - exits script without closing bash session. Cannot check on MacOS or Windows though.

Hi @nikolay-turpitko , in my mac, running return will return "return: can only `return' from a function or sourced script".  :-)

Well, don't know how to fix it then. May be just add something like read -n1 -rsp $'Press any key to exit...\n' before exit to let user read the message before window disappears?

@nikolay-turpitko
how about false? can you help me test in linux?

Well, I placed confirmation before exit like
# LEDISTOP sanity check
if [[ "$LEDISTOP" == "${LEDISTOP/\/src\/github.com\/siddontang\/ledisdb/}" ]]; then
    echo "WARNING: LEDISTOP($LEDISTOP) does not contain src/github.com/siddontang/ledisdb"
    read -n1 -rsp $'Press any key to exit...\n'
    exit 1
fi

When project placed in the wrong dir it give me a chance to read message before exit and close terminal window. In the right place it works as usual. Sorry, if I misunderstand your question.

@nikolay-turpitko
what I mean is using false instead of exit 1 like :
if []; then
   echo
   false
fi

This can work in my mac osx, how about in your linux system?

Yes, this works perfect in Ubuntu!

Hi @nikolay-turpitko
Can you send me a PR for this? :-)


Explicitly specify window title

This should tell macOS to display the correct title.
Fixes #8

This did not fix the issue.

This now works with electron-builder, merging.


fix shell integration issues after clearing

This PR fixes #145148 fixes #151217

oh I think what happens is the top line is just retained of the prompt and not cleared

which explains why xterm.js doesn't parse anything even though the prompt appears to show up after the clear


Gradle command in Exec got an output different from plain command execution in Linux

Expected Behavior

I'm running command line commands through a custom Gradle Plugin I've created within Gitlab CI inside a jdk17 Linux pod. When the plugin executes a helm upgrade command I get an error, but when I execute the same command from the Gitlab CI scripts, it works perfectly. I'd expect commands running within Gradle to work the same way as if they would get executed directly on the Linux machine.
Current Behavior

I create a custom Gradle plugin that executes the helm upgrade command with the code of (inside of a class that extends DefaultTask:
@TaskAction
public void command() {
    // code for building the commands array
    getProject().exec(t -> t.commandLine(commandsArray);
}

The command line that is generated is /home/jboss/helm update -i my-release -f /builds/my/project/chart/values-prod.yaml/builds/my/project/chart/output/my-project-chart.tgz —set image.tag=“0.1.2”.
When I execute it directly it works, but when Gradle executes it - it doesn't. It's important to note that it also works perfectly when Gradle executes it on Windows.
The error I get when I execute this within the Gradle plugin task is: Error: UPGRADE FAILED: YAML parse error on my-project/helm-common/deployments.yml: error converting YAML to JSON: yaml: line 31: did not find expected key. I would accept that I have some lint issues here, but it's working perfectly from anywhere but the Gradle execution engine. I would like to get some help understanding the differences that can occur between executing a command from Gradle vs. directly, and understanding how to fix this (I thought of running the command with the keyword bash at the beginning but it didn't help).
Context

Steps to Reproduce

Your Environment

I execute the command within this JDK-17.0.2 image.

As a workaround, I've managed to get this work by executing getProject().exec(t -> t.commandLine("bash", "-c", "'helm upgrade ...'").

Thank you for your interest in Gradle!
Your issue appears to be a question about how to use Gradle. Your question might be answered in Gradle documentation or on our community Slack or forums. Find links to these resources on help.gradle.org.
If you think you have come across a Gradle bug, please file a new issue describing the problem and how to reproduce it.
If you think Gradle is missing a feature, please file a new issue describing your use case for the feature.

A process started from a shell started manually and a process started by Gradle might have different environment, this might be the source of your problem.


Ability to extend existing declared schemas without redefining

Going through converting from zod to valibot - and I love all the new primitives! I used to take existing zod schema's, and add onto them, like...
const schema = z.object({
  name: z.string();
});

const refinedSchema = schema.refine({...});

This does not seem possible with Valibot as you can't extend schemas once they are created, unless I am missing something?
You would need to do:
const schema = v.object({
  name: v.string();
});

const refinedSchema = v.object({
  ...schema.entries
}, v.custom(...));

This also affects working with Drizzle as you are to re-define the schema type instead of being able to "add on" to it, which could cause you trouble down the line if you are trying to keep one source of truth (being Drizzle).
For example:
zod-drizzle:
const insertUserSchema = createInsertSchema(users, {
  id: (schema) => schema.id.positive(),
  role: z.string(),
});

valibot-drizzle:
const insertUserSchema = createInsertSchema(users, {
  id: (schema) => v.number([v.minValue(0)]),
  role: v.string(),
});

Notice how with "id", you have to refine it as v.number() as opposed to just using schema.id.number()
Hopefully this makes sense?

I am not sure if I fully get it, but I think this proposal makes Valibot more composable, since the pipe function can be nested: https://github.com/fabian-hiller/valibot/discussions/463

I am not sure if I fully get it, but I think this proposal makes Valibot more composable, since the pipe function can be nested: #463

Ah yes! If you are able to do something like this:
const schema = v.pipe(
  v.object({
    name: z.string();
  });
);

const refinedSchema = v.pipe(schema, v.custom(...));

Then that'd be great - if I am understanding the proposal correctly.

Yes, this will be possible 🙌

I plan to publish a first version of the pipe function in about two or three weeks.


The logic for sharedSubexprs within lambdas can be a memory hog

Bug description
The logic for evaluating shared subexpressions once in Expr.cpp uses a map keyed on the addresses of the distinct input fields, which contains a SelectivityVector with the rows already processed, and a Vector containing the results for the already processed rows.
https://github.com/facebookincubator/velox/blob/d3f0dc9ca68e1c7a39ae38a4864ca79375840a8a/velox/expression/Expr.cpp#L872,L873
Normally this map should be small given usually only having one entry given that in order for an expression to be reused all of its input expressions need to be identical as well.
With lambdas this is not necessarily the case.  Although the expressions may be identical, the addresses of the inputs may not be.  For example, reduce wraps the input in a dictionary before each invocation of the lambda, meaning the input to each lambda is a unique Vector with a unique address. This means we can't take advantage of shared subexpressions, but worse, it can cause the sharedSubexprResults_ maps in the expression to explode, with one entry per lambda invocation.
https://github.com/facebookincubator/velox/blob/d3f0dc9ca68e1c7a39ae38a4864ca79375840a8a/velox/functions/prestosql/Reduce.cpp#L139,L143
I saw just such a case where Reduce was being called on arrays with millions of values in some rows.
This was compounded by the selectivityVectorPool_ in the ExecCtx.  Elsewhere in the lambda we were constructing LocalSelectivityVectors on the order of the size of the elements in the arrays, which would get returned to the pool and reused as the SelectivityVectors in the values of sharedSubexprResults_ on subsequent calls.
So we ended up trying to create 1,000,000 SelectivityVectors, each large enough to hold 1,000,000 bits, which easily surpassed 10's of GBs of memory.
I mention the selectivityVectorPool_ only because it's an interesting complicating factor, and was critical to this particular example (and made it much harder to debug).  However, I think the root cause is the way sharedSubexprResults_ is used within lambdas.  It's easy to envision a case where the issue occurs even with the selectivityVectorPool_ disabled.
Given that lambdas may be called many more times than other expressions, I could see a lot of value in using sharedSubexprResults_, particularly for expressions involving captured values which may be the same for every invocation.  (Although the wrapCature logic is also likely to trigger the same issue).
https://github.com/facebookincubator/velox/blob/aaaa0791008267d8be0a5c141db6da261aba8892/velox/expression/LambdaExpr.cpp#L113,L116
Should we limit the size of sharedSubexprResults_ to 1 (it gets cleared at the end of every ExprSet eval invocation)?  If we're going to get value from it, it's probably going to have the same inputs on every invocation, and this prevents the sort of unbounded growth I witnessed.
System information
.
Relevant logs
No response

I dug into the history of the change that adds a map to manage the inputs to shared subexpressions. Looks like it was added around the time when dictionary inputs were allowed to be used as inputs to the shared sub-expressions and we witnessed instances where different levels of unwrapped inputs ended up being fed into the shared sub-expressions. With all the fixes that went in, this should now be highly unlikely so we can probably limit the size to 1 (or replace it with a mechanism that resets the cached results if a different set of inputs are used).
Like you mentioned earlier, this state should have been reset on every invocation of ExprSet, which means that some state of an expression tree should be reset between subsequent batches. For a lambda like reduce, every index from the input arrays is like a new set of input for the lambda expression tree. Maybe we should reset its state between these invocations and take a look at other lambdas that are similar. This would ensure that any state (apart from shared subexpression or any others that might be added in the future) that should be reset between input batches would consistently be reset for cases like this. If this is generic enough then we can also build this reseting functionality into the lamda function's API.
What do you think?

@bikramSingh91
Thanks for digging into the history!
This is what I was trying to get at in the second to last paragraph.  Although the input arguments may be the different on each invocation, the captures will likely be the same, so not having to recompute expressions on top of those could yield a lot of benefit depending on the cost of the expressions and the number of times the lambda is invoked.

If this dire situation happens only for batches with very large number of elements in vectors and some lambda expressions running through them, then we can have a threshold after which we don't apply the sharedSubexprs optimization or clean it on every iteration over the elements or keep a restricted 'depth' (not 1 or infinite, but N)?

@bikramSingh91 Thanks for digging into the history!
This is what I was trying to get at in the second to last paragraph. Although the input arguments may be the different on each invocation, the captures will likely be the same, so not having to recompute expressions on top of those could yield a lot of benefit depending on the cost of the expressions and the number of times the lambda is invoked.

Thats a good point, the captures are same so there might be branches inside the lambda that only rely on these, so their result can be reused. I think restricting the size to 1 (or replacing it with a mechanism that resets the cached results if a different set of inputs are used) should work well. It might still be worth checking if there is state in Expr that should be reset between subsequent iterations and make sure we do reset it.

Thanks for the responses, it sounds like we agree on restricting the size. I'll make the limit configurable so we can tweak it as needed.

I saw just such a case where Reduce was being called on arrays with millions of values in some rows.

@kevinwilfong Curious if this is happening when an array have millions of elements. Is this the case? Any chance you could share a snippet of reduce expression for that scenario. Wondering if 'reduce' call here could have been re-written into something simpler.

@mbasmanova here's the reduce expression in the case I saw
        REDUCE(
          ARRAY_AGG(
            ARRAY[
              start, start + duration
            ]
            ORDER BY
              start ASC
          ),
          ARRAY[0, 0],
          (s, x) -> ARRAY[
            s[1] + (
              IF(
                x[1] < s[2],
                IF(
                  x[2] - s[2] > 0,
                  x[2] - s[2],
                  0
                ),
                x[2] - x[1]
              )
            ),
            IF(
              s[2] > x[2],
              s[2],
              x[2]
            )
          ],
          s -> s[1]
        )


background script no longer run when alarm/gcm event fires and app isn't running

Hi,
Could someone please have a look at https://github.com/MobileChromeApps/mobile-chrome-apps/issues/297 ?
This is still happening to me: I register for GCM, kill the app, send a GCM message from the server and the D/XWalkCordovaWebViewClient﹕ onPageFinished(file:///android_asset/www/plugins/org.chromium.bootstrap/chromeapp.html) gets launched without processing my code (showing a black background screen when I bring the app into the foreground).
My cca version is 0.5.1. The org.chromium.bootstrap plugin is 1.1.3 (Jan 28, 2015) according to README.md. Btw, in the "Release Notes" section there is no mention of #297 being fixed.
Users currently need to kill the app every time a GCM message was received while the app was not running :/

We've been working on improving the background functionality (see #322).  That work includes addressing the behaviour of background events when the app is not running.
The effort was delayed for a while, but we're back in active development.  The goal is to complete the work in the next few weeks.

Sounds great! Keep up the good work :)

This problem has been fixed, and is available in the latest cca release candidate (just out today).


[CUDA] mma.sync pipeline failed compilation with some tuning configs

What happened?
I tried to tune the matmul ops with mma.sync pipeline and used the same tile/workgroup size constraints from wmma pipeline. But a lot of them failed with the error error: Cannot determine operandId this vector::TransferReadOp is used as in the vector::TransferContractOp
Steps to reproduce your issue
Input IR:
{
  %arg0 = util.unfoldable_constant dense<1.0> : tensor<32x320xf16>
  %arg1 = util.unfoldable_constant dense<0.4> : tensor<320x1280xf16>
  %cst = arith.constant 0.000000e+00 : f16
  %0 = tensor.empty() : tensor<32x1280xf16>
  %1 = linalg.fill ins(%cst : f16) outs(%0 : tensor<32x1280xf16>) -> tensor<32x1280xf16>
  %2 = linalg.matmul {compilation_info = #iree_codegen.compilation_info<lowering_config = <tile_sizes = [[16, 32, 64]]>, translation_info = <LLVMGPUMatmulTensorCoreMmaSync pipeline_depth = 6>, workgroup_size = [256, 1, 1]>} ins(%arg0, %arg1 : tensor<32x320xf16>, tensor<320x1280xf16>)
    outs(%1: tensor<32x1280xf16>) -> tensor<32x1280xf16>
  return %2: tensor<32x1280xf16>
}

Compilation command:
iree-compile --iree-vm-bytecode-module-output-format=flatbuffer-binary --iree-hal-target-backends=cuda --iree-hal-cuda-llvm-target-arch=sm_80 --iree-hal-cuda-disable-loop-nounroll-wa ~/tmp/matmul_32x1280x320.mlir -o matmul.vmfb
What component(s) does this issue relate to?
No response
Version information
Nvidia A100
Additional context
No response

@manishucsd Have you been able to take a look at this?

@manishucsd Have you been able to take a look at this?

No, I haven't yet looked into this.
Just eyeballing this, I have a suspicion the matmul shape here is similar to the one I am working here #13075

I tried to tune mma.sync with the updated IREE library and I think the error was gone by then. So feel free to close the issue.


[FE] show blog post from db

use the blog post API endpoint (https://github.com/Hack-Weekly/tangerine-moose-blog/issues/48) to get actual blog post data based on the URL and display it

This has been resolved via postUtils and app/blog/post/page.js


Support for NeoVim Async api

This plugin is amazing, good job!
Any plans for adapting it to NeoVim's async api?
Thanks

I develop on NetBSD. I see there is a pkgsrc/wip package for Neovim,
but I haven't yet tried it to see if it works (the package looks
fairly active though so I guess should work).
So... I haven't even tried to run Neovim yet, I have no idea about the
async api, but I do have Neovim on my radar and was planning to see
how Simplenote.vim functioned under it at some point.
No plans right now, but happy to leave this issue open for when I get
around to it.


⚠ ClamAV has degraded performance

In 3f7fd93, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 121 ms

Resolved: ClamAV performance has improved in 745b66c after 6 minutes.


Release engine drone builds use an arbitrary recipe version

For example, in the (test) release build (note, this was a sub-build of ) https://chrome-swarming.appspot.com/task?id=69b02efb05491510&o=true&w=true, the input args say:
              "kitchen-checkout": {
                "cipd": {
                  "server": "chrome-infra-packages.appspot.com",
                  "specs": [
                    {
                      "package": "flutter/recipe_bundles/flutter.googlesource.com/recipes",
                      "version": "refs/heads/flutter-0.0-candidate.1234"
                    }
                  ]
                }
              }

Note that flutter-0.0-candidate.1234 is not a real release branch, but was just an experimental test branch pushed to the engine as part of https://github.com/flutter/flutter/issues/146078, and unrelated to the release branch that was (intended) to be built.
The parent build was https://ci.chromium.org/ui/p/dart-internal/builders/flutter/Mac Production Engine Drone/12070/infra
Which used the recipe https://flutter.googlesource.com/recipes/+/refs/heads/master/recipes/engine_v2/engine_v2.py#107
Which called the module: https://flutter.googlesource.com/recipes/+/refs/heads/main/recipe_modules/shard_util/api.py#398
      req = self.m.buildbucket.schedule_request(
          swarming_parent_run_id=self.m.swarming.task_id,
          bucket=bucket,
          builder=builder_name,
          properties=properties,
          dimensions=task_dimensions or None,
          # Having main build and subbuilds with the same priority can lead
          # to a deadlock situation when there are limited resources. For example
          # if we have only 7 mac bots and we get more than 7 new build requests the
          # within minutes of each other then the 7 bots will be used by main tasks
          # and they will all timeout waiting for resources to run subbuilds.
          # Increasing priority won't fix the problem but will make the deadlock
          # situation less unlikely.
          # https://github.com/flutter/flutter/issues/59169.
          #
          # Set priority to be same of main build temporily to help triage
          # https://github.com/flutter/flutter/issues/124155
          priority=30,
          exe_cipd_version=self.m.properties.get(
              'exe_cipd_version', 'refs/heads/%s' % branch
          )
      )

Of which the branch argument is derived from https://flutter.googlesource.com/recipes/+/refs/heads/flutter-3.18-candidate.18/recipe_modules/repo_util/api.py#575
  def release_candidate_branch(self, checkout_path):
    """Returns the first branch that starts with "flutter-"."""
    commit_branches = self.current_commit_branches(checkout_path)
    for branch in commit_branches:
      if branch.startswith('flutter-'):
        return branch

This is selecting the first release candidate branch that was output by git branch -a --contains $COMMIT, not necessarily the one that is supposed to be built.

@cbracken can you fix this?

This is fixed as of https://flutter.googlesource.com/recipes/+/ca8cc15c33beb389bd9ae23b4aff2008c01e360b


Is Tranco dead?

The lists are currently unavailable to download via the website and, having just installed the Python package, I am getting errors which seem to imply it can't connect to or read from the online lists.
The website link for the up to date list gives a Cloudflare 502 error.
The permalink to https://tranco-list.eu/top-1m.csv.zip DOES work but I'm concerned it may not actually be up to date since it's not timestamped.

I'm able to pull older dates latest_list = Tranco(cache=True).list(date='2019-02-25')
but doing latest_list = Tranco(cache=True).list() currently fails for me as there is no response

I'm able to pull older dates latest_list = Tranco(cache=True).list(date='2019-02-25')
but doing latest_list = Tranco(cache=True).list() currently fails for me as there is no response

Thanks for the notification. The file should be available again.
As noted on the home page of the website, the Last-Modified header provides an exact timestamp for when the file was updated (when following the redirects).

Thanks for the notification. The file should be available again.
As noted on the home page of the website, the Last-Modified header provides an exact timestamp for when the file was updated (when following the redirects).

Awesome, thanks so much for the quick response!

Awesome, thanks so much for the quick response!


badge-links

@sideeffffect What is this change? How is it different than what's already in there?

@sideeffffect What is this change? How is it different than what's already in there?

Oh, I see now. The difference is that the badge is actually a link to the repo, right?


Add rewind()

First off, we require calling finish() before reading results. This is a deliberate API change.
Currently, we "incrementally keep track of results". This means feeding the input in multiple chunks has a performance penalty.
I've patched our Stream implementation, so users of that API won't even notice this change!
Everyone else will have to drop in a p.finish() line before they read p.results.
Then, I added rewind(index), which requires the keepHistory option. It resets the parser state to the state after seeing that token. So if you feed it 10 tokens, rewind(10) has no effect. [rewind(11) is an error; you can't rewind forwards!]
Note that this is not a reset method. If you want to reset a parser, throw it away and initialise a new one. Assuming you're using Grammar directly this is basically free. If you're using an Earley parser, you shouldn't care about allocating one single object. :-)

@Hardmath123 thoughts? As an API change this might have to wait for v3... :/

Hmm… I don't want to break things by requiring .finish(). Why is that a prerequisite for having .rewind()? Can't we just run .finish() at the end of .rewind() to fix results? Also, what are the possible uses for .rewind() besides syntax-highlighting tricks?
(Sorry that ended up being a log of questions! :P)

Why is that a prerequisite for having .rewind()?

I suppose it's actually not, but I want to do that also, and I thought I might as well do it first :P I'll drop that commit from this PR, and instead add it to my stack of API changes...
I can't think of other uses off the top of my head. But in general being to re-parse only some of the input seems useful. We could perhaps instead have a CachingParser, which re-uses the beginning of the previous parse where possible; and let rewind() remain only as part of the private API. But I'd rather provide rewind(), and let people implement their own logic on top of that if they so choose.

Updated. :)

Sounds good to me. Thanks, Tim!

nearleyc
  ✓ should build test parser (check integrity) (122ms)
  ✓ should build for CoffeeScript (260ms)
  ✓ calculator example
  ✓ csscolor example (47ms)
  ✓ exponential whitespace bug
  ✓ nullable whitespace bug
  ✓ percent bug
  ✓ tokens
  ✓ leo bug
  ✓ json example compiles
  ✓ json test1
  ✓ json test2
  ✓ tosh example (174ms)
  ✓ classic crontab
  ✓ parentheses
Parser
  ✓ can rewind
  ✓ won't rewind without `keepHistory` option

I feel we might want to think about what the headings should be. The line between "nearleyc" and "Parser" seems kind of arbitrary.

At some point, probably. I figured a different section was justified since these are testing the API, not the compiler or parsing algorithm. :-)


Replica errors if I touch the field in any way

Steps:

Create deployment
Type in the number 2 in the Replicas field
Fill out name and Image
Create

Results:  Error.  It's being converted to a character field?

Verified fixed


[#1749] Disable presentation mode

#1749
Due to accessibility issues, we are disabling Presentation mode temporarily instead of investing time in the fix when we are not yet decided on how to improve this feature. For more information, please see #1866

Presentation mode is now hidden, but the related code has not been deleted.

Coverage decreased (-0.04%) to 65.742% when pulling<PHONE_NUMBER>fed0f686c602ba63974caf50fe65ac on corinagum/1749 into 7ef388a5ac7f24437ebb595ad7758cdce55984b0 on master.


docs: auto-generation warning message; more robust env table generation

Make the docs-generator more robust around the environment table. This fixes running it. However I
have not committed (all) of the results of running it because that would overwrite some changes made
to the generated files in a80015d7. We need to alter the generation script to account for those changes.
Make the generation script add a comment to the top of generated files warning that changes to those
files might get overwritten next time the generator is run.

pushed


ISS348: Deprecated Meta::Action Ephemera entries

Mistake label had this close 348.  Should have been closes #360


Create extension releases via GitHub Actions

Is that creating a release on each commit to master?

I think so, but also manual trigger would be possible

The release name will simply be the sha-1 of the commit, right?

I think so, I am not very familiar with GH actions yet so not sure how to trigger on "version release" yet.


Extend all Arg types to include the same fields and omit unneeded fields with type never

Problem
It would be great to extend all Argument types to include the same fields. Currently when we try to access the utility type Args<Type, Operation>[FieldName] FieldName can only be common to each operation arguments. For example for create operation we have only 'data' and 'select', however indexing 'include' is not possible. If each function argument includes the same fields (where we do not want a field we can impose fiels type equals to never) indexing 'include' would be possible.
How to reproduce

Create Prisma schema that include two related tables and one that's not related to anything.

model make {
  id        Int     @id @default(autoincrement())
  name      String  @unique
  model     model[]
}

model model {
  id        Int     @id @default(autoincrement())
  name      String  @unique
  makeName  String
  make      make    @relation(fields: [makeName], references: [name])
}

model fuel_type {
  id        Int     @id @default(autoincrement())
  name      String  @unique
  isDeleted Boolean @default(false)
}

Try to use utility type Args<Type, Operation>
const a: Prisma.Args<PrismaService[M], 'create'>['include'] = {.....}
(M extends ModelName)

#Expected behavior
Being able to index the type Prisma.Args by field "include" although it is not usable for model fuel_type.
Prisma.Args<PrismaService[M], 'create'>['include']
###Actual behavior (optional)
In reality it is not possible
Suggested solution
fuel_type arguments shall include the field with type "never"
{
......
include: never
......
}

I think I would also be wise to allign all operations argument to match each other out of consistency reasons (not only for the create function as I mentioned above).
for ex.
Similarly you can use the same idea and apply it to all other functions, namely:
findFirst, findFirstOrThrow, findUnique, findUniqueOrThrow, findMany, create, createMany, update, updateMany, upsert, delete, deleteMany, aggregate, count, groupBy, $queryRaw, $executeRaw, $queryRawUnsafe, $executeRawUnsafe, findRaw, aggregateRaw, $runCommandRaw
Alternatives
You can make a type wrapper for the arguments like follows:
type AddIncludeArg<T> = T extends { include?: any } ? T : T & { include?: never }
Here we are working in the context of the creare function.
I am not sure if such a solution can scale well with other functions

+1

Thank you for the solution. I already thought about it, but I don't like such "pathes" to the problem. I have found a way to my issues, by moving one abstraction layer higher than prisma, so I do not need to deal with such issues. I am currently using ZenStack with is build on top of prisma. Personally I think the TS types should be more abstract and at the end diverge only for the data of each model. However this is just my idea, which is not at all validated, because I am not an expert in prisma and this might not be feasible due to something I don't know and I haven't taken into account.


Linked list zip

Feature Tasks

[x] Write a function called zip lists
[x] Arguments: 2 linked lists
[x] Return: New Linked List, zipped as noted below
[x] Zip the two linked lists together into one so that the nodes alternate between the two lists and return a reference to the the zipped list.
[x] Try and keep additional space down to O(1)


feat(ci): Jenkins & overview started

@spinnaker/google-reviewers FYI

offline comments
On Mon, May 8, 2017 at 11:31 AM, Lars Wander<EMAIL_ADDRESS>wrote:

@spinnaker/google-reviewers
https://github.com/orgs/spinnaker/teams/google-reviewers FYI
You can view, comment on, or merge this pull request online at:
https://github.com/spinnaker/spinnaker.github.io/pull/87
Commit Summary

feat(ci): Jenkins & overview complete

File Changes

M setup/ci/index.md
https://github.com/spinnaker/spinnaker.github.io/pull/87/files#diff-0
(20)
M setup/ci/jenkins.md
https://github.com/spinnaker/spinnaker.github.io/pull/87/files#diff-1
(29)

Patch Links:

https://github.com/spinnaker/spinnaker.github.io/pull/87.patch
https://github.com/spinnaker/spinnaker.github.io/pull/87.diff

—
You are receiving this because you are on a team that was mentioned.
Reply to this email directly, view it on GitHub
https://github.com/spinnaker/spinnaker.github.io/pull/87, or mute the
thread
https://github.com/notifications/unsubscribe-auth/AEKkGJAKtf6pX5qR6Qlj35i97us_ag3Iks5r3zVUgaJpZM4NUHVt
.


chore(deps): upgrade dependencies

Upgrades project dependencies. See details in workflow run.

Automatically created by projen via the "upgrade-1.x" workflow

⚪ Backport skipped
The pull request was not backported as there were no branches to backport to. If this is a mistake, please apply the desired version labels or run the backport tool manually.
Manual backport
To create the backport manually run:
backport --pr 750

Questions ?
Please refer to the Backport tool documentation


Typofix/solid motor

Pull request checklist
Please check if your PR fulfills the following requirements:

[ ] Tests for the changes have been added (for bug fixes / features)
[ ] Docs have been reviewed and added / updated if needed (for bug fixes / features)
[ ] Build (python setup.py install) was run locally and any changes were pushed
[ ] Lint (black rocketpy) has passed locally and any fixes were made for failures
[ ] All tests (pytest --runslow) have passed locally

Pull request type

Please check the type of change your PR introduces:

[ ] Bugfix
[ ] Feature
[ ] Code style update (formatting, renaming)
[ ] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[ ] Documentation content changes
[ ] Other (please describe):

What is the current behavior?

RocketPy's code did not have any unit tests setup.
What is the new behavior?

Does this introduce a breaking change?

[ ] Yes
[ ] No

Other information

Fixed some typos in the SolidMotor class

Hey @ompro07 , thanks for pulling those tpos corrections, nice job.
Before merging the PR, I would like to ask you to add your name as an author in the 3rd line. Would you please?

I add my name as requested, thanks


Math and lab clarification.

I have done the setup and am at the Jacobi part, which is taught in graduate numerical methods (which is a significant math class, which is not a prerequisite for this course).  The math required for this homework was not covered in the lectures in enough detail for someone who has not had that level of math.
The homework says to use Jacobi and Gauss-Seidel not norms and point-wise updates using neighbors.
If it was covered in the labs which distance students do not have access to then it should not be part of the homework.

The Jacobi method was described in lecture as u_{k+1} = u_k + omega * D^{-1} R(u_k) where D is the matrix diagonal and R(u_k) is the residual function you have been given in the homework. We drew pictures of this during the lab that introduced the homework, and discussed a number of questions. If you don't attend lab (distance section or otherwise), I would expect that you work through it on your own and ask questions, either in this forum or by directly discussing with other students. Respectfully, the best time to ask questions about how to start is in the first few days so that I can incorporate visual discussion into lecture. I realize I may not have communicated this clearly and will do my best to answer questions in this forum.
As for prerequisites, this class is about scientific computing, each aspect of which uses math (often different flavors of math). There will be concepts you haven't seen; I'll provide introductions and pointers to further references. You won't need to dive in deep with the math (I don't ask you to derive equations, prove theorems, etc.), but you will need to have an open mind, be willing to read supplementary resources, and strive to ask questions.
As for this particular homework, you've been given a function Residual that evaluates b - A u where A is the matrix representation of the stencil operation
[0  -1   0;
-1   4  -1;
 0  -1   0]

It shows the relation between stencils and matrices; Jacobi is a small modification to the above, and Gauss-Seidel can be thought of as a triangular solve or as sweeping through the grid like in Residual, but where the updates are in-place (so that subsequent points use the "new" values of u).

Please show where in the course description it says that distance students would be disadvantaged.

That is not the intent, but you absolutely need to take the initiative to read and ask questions because you aren't in the room talking with classmates during the lab. Suggestions to improve format for distance section labs would be greatly appreciated.


Need to reinitialize PIP workset in pip_utils

fixes #295, connected to #295, connected to #272, connected to #293

@mriehl
https://travis-ci.org/pybuilder/pybuilder/jobs/95222834#L735
https://travis-ci.org/pybuilder/pybuilder/jobs/95222834#L1430
There, FTFY. :smile:


Submission dropzone issues

References

Fixes #957
Fixes #849

Description

The dropzone on the submission form will no longer be rendered when the submission form does not include an upload section.
When a file is dropped on the submission forms dropzone, the page will not automatically scroll to the top of the age anymore. The dropzone and its progress bar is now always visible at the top of the page, similar to the collection dropdown.

Instructions for Reviewers

Collections without an upload section in their form definition, should no longer show the dropzone on their submission page
Dropping a file anywhere on the submission page should no longer cause the page to scroll up, but should always show the progress bar at the top of the page, independently from the user's current scroll position.

Checklist

[x] My PR is small in size (e.g. less than 1,000 lines of code, not including comments & specs/tests), or I have provided reasons as to why that's not possible.
[x] My PR passes TSLint validation using yarn run lint
[x] My PR doesn't introduce circular dependencies
[x] My PR includes TypeDoc comments for all new (or modified) public methods and classes. It also includes TypeDoc for large or complex private methods.
[x] My PR passes all specs/tests and includes new/updated specs or tests based on the Code Testing Guide.

@atarix83 Thanks for the feedback. You're absolutely right, I'm sorry I missed that. I cherry-picked your changes into this branch and pushed them.

Merging, as this is at +2 & @atarix83's improvement commit was included. Thanks again @LotteHofstede (and @atarix83) !

Unfortunately, after merging this I've just now realized it's had major side effects. It's now impossible to click on any field in the submission form, which means it's impossible to submit a new item.  I've created a revert PR #1083 which I'll merge shortly just to get the demo site working again.

@tdonohue That's indeed unfortunate, my apologies for not noticing this very obvious issue.
It should be fixed now that the page-wide dropzone is only rendered once the user actually drags a file onto the window.
I created a new PR https://github.com/DSpace/dspace-angular/pull/1087


Always go through the adapter to decide how to propose visits

This fixes a bug introduced in: https://github.com/hotwired/turbo/pull/410
#410 made a change that made the decision to visit internal vs external urls outside of the adapter. This works fine in the browser context, but breaks the expectations for the turbo-ios and turbo-android native adapters.
Native apps using the native turbo libraries already must provide logic for properly routing internal/external urls to the WebView or an external app/browser. This change brings back the capability for programmatic Turbo.visit(url) proposals to flow through the adapter, even for external urls. This gives the native adapters the opportunity to pass external url visit proposals to the native apps.
Before this change Turbo.visit("https://google.com") would result in the native app's Turbo WebView navigating directly to google.com, bypassing the Turbo visit flow, which should never happen.

@seanpdoyle that's a great point — I would like the main native adapter methods to be tested. Really, we just need to swap the adapter for a native stub and verify that the correct methods are being called. We can let the native libraries continue to be responsible for testing their custom behaviors.
I'm actually aware of another bug I need to look into soon where Frame Navigation doesn't appear to propose new visits through the adapter. Proper testing would help isolate issues like this and of course prevent regressions in the future.
I'll look into this soon 👍

@seanpdoyle I've added unit tests for the native adapter interface, which would have caught this particular issue: https://github.com/hotwired/turbo/pull/1054/commits/2414740c0990b36b2646e636e79b84e10f17f430


Add the world map to the landing page

Type of Changes

Type

✓
:sparkles: New feature

✓
:link: Update dependencies

Description
This pull pull request:
1- Adds new dependencies: react-datamaps and d3.
2- Adds  aWorldMap component to path-to/landing-page/components. That component displays the world map colored based on the number of users in each country. (The countries and number of users are hard coded for now)
3- Displays the component on the landing page.
How it looks so far

Testing Guidelines

From your terminal, pull down this branch with git pull origin Feature/add-the-world-map-to-the-landing-page and check that branch out with git checkout Feature/add-the-world-map-to-the-landing-page
Then yarn to install the newly added dependencies locally and yarn start to launch the app.
Go to http://localhost:3000/ to see the map on the landing page.

Please let me know if anything needs to change. Thanks.

This is great, Hajar! I made some minor changes, but this is perfect.
@all-contributors please add @hajarNasr for code!


Fix GPU CI

Use ops.numpy.multiply in most operations within MixUp to address torch GPU CI issues
Disable run_training_check in MixUp when using GPU to address tensorflow GPU CI issues

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 60.59%. Comparing base (90d36dc) to head (18a2ce3).

:exclamation:  There is a different number of reports uploaded between BASE (90d36dc) and HEAD (18a2ce3). Click for more details.
HEAD has 6 uploads less than BASE

Flag
BASE (90d36dc)
HEAD (18a2ce3)

keras
4
1

keras-torch
1
0

keras-tensorflow
1
0

keras-jax
1
0

Additional details and impacted files
@@             Coverage Diff             @@
##           master   #20637       +/-   ##
===========================================
- Coverage   82.55%   60.59%   -21.96%
===========================================
  Files         518      518
  Lines       48682    48682
  Branches     7592     7592
===========================================
- Hits        40188    29498    -10690
- Misses       6669    17404    +10735
+ Partials     1825     1780       -45

Flag
Coverage Δ

keras
60.59% <100.00%> (-21.81%)
:arrow_down:

keras-jax
?

keras-numpy
60.59% <100.00%> (ø)

keras-tensorflow
?

keras-torch
?

Flags with carried forward coverage won't be shown. Click here to find out more.

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


New Vue warning in version 0.24.13

Describe the bug
Since version 0.24.13 i get this console message in both Firefox and Chromium when i run my Vue3 app:
[Vue warn]: Avoid app logic that relies on enumerating keys on a component instance. The keys will be empty in production mode to avoid performance overhead.
I can not find any wrongdoing in my code. Can it be a change in the bootstrap-vue-next code?
Reproduction
https://github.com/ErikVerheul/onebacklog
Used Package Manager
pnpm
Validations

[X] Have tested with the latest version. This is still alpha version and sometime things change rapidly.
[X] Follow our Code of Conduct
[X] Read the Contributing Guide.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Check that this is a concrete bug. For Q&A, please open a GitHub Discussion instead.
[X] The provided reproduction is a minimal reproducible of the bug.

which file gives that error? You might be passing a ref of a ref or something like that, or watching route object (just based on 1min of googling).
Please provide a reproduction that doesn't require an installation of other software and configurations.

Sorry for the inconvenience. I should have put this as question. For what i could see in the browser debugger the problem has a relation with the use of JSON.stringify. But not in my code. I try to recreate the bug with stackblitz but without success until now.

only json.stringify are in table (when sorting/filterin) and tooltip/popovet directive. Maybe the way you are using them?

I pinpointed the cause of the warning to a change in git: fix directives on element update during interaction (#2170) at September 5 by Jukka. My debugger points at line 22  el.$__binding = JSON.stringify(binding)  in the file BPopover.ts and to line 23, with the same line content, in BTooltip.ts.
I am still trying to recreate the bug but without success until now.

@ErikVerheul could you try with the pull request if that fixes your warnings?
change the version in package.json to https://pkg.pr.new/bootstrap-vue-next/bootstrap-vue-next@2208 and run pnpm/npm/yarn i

YES! Problem solved, the warning is gone. I had to install pnpm and to run 'pnpm i'. However i got a totally unrelated error:
Uncaught TypeError: this.emitter is undefined     update 						quill.js:4401     quill @vueup_vue-quill.js:7147     ScrollBlot2 quill.js:7190     Scroll2 quill.js:4227     create quill.js:184
I look forward to your next release with your fix. Meanwhile i undo the changes pnpm introduced and use npm. I expect the new error to disappear.
By the way, i thank you for your effort to create this great peace of software.

I'll release a new one later today


Inventory not Generated

Hello i using this mod on server
and it only saying on all chests
(Inventory not Generated) how to fix?
(MC: 1.20.1)
(Lootr: <IP_ADDRESS>)

If it's showing this in a HUD mod like Jade, that simply means that that mod doesn't have integration with Lootr. If you are still able to open chests and get loot, there is no issue.

If it's showing this in a HUD mod like Jade, that simply means that that mod doesn't have integration with Lootr. If you are still able to open chests and get loot, there is no issue.

oh okey but i had zero problem with jade on version 1.19.2 and worked fine with lootr

There is a Jade integrations mod that you may have also had installed as well.

yea i got it to work it was jade thank you :)


Feature request: RSS feed crawler

When items contain enclosures linking to available documents.

Hi @jenkin . Can you please describe this crawler a bit? Should it fetch all linked documents? And if the document an html page should it fetch it too?

RSS specifications require the mime type as attribute of enclosure tag: "It has three required attributes: url says where the enclosure is located, length says how big it is in bytes, and type says what its type is, a standard MIME type." So the crawler should fetch only enclosures with a supported (by Ambar) mime type (ie. application/pdf). Other types, such as mp3 in podcast feeds, will be ignored.

@jenkin got it! Can you please also describe use case for the RSS crawler? What kind of data you want to crawl with it? Newsletters or what?

Check our support options


As a family or a work team I want to be green

We need to implement a teams feature where users in the same group or team don't show up.

As user I can select and join a Safe Team.
Other people in my team will be registered as 'green' when they are close during an app session.
User can join safe teams, but defaults to no team when app is opened.
Use case A: Family goes grocery shopping and Mom and Dad have their phones with them and the app on. This allows them to show up as green while they are in the store, but still get notifications when others not on the "Safe Team' are around.
Use Case B: Two manufacturers always work next to each other and are not able to social distance. They may join a Safe Team so their app doesn't notify of each other, but will still notify when other users are close.


Enable milliseconds in syslog-ng for all pot log timestamps

Hello, this PR increases log timestamp accuracy by adding 3 fractional digits for seconds (a.k.a. milliseconds) for all pots that have syslog-ng configs.
Example timestamp without this change:
2024-10-27T06:11:12+00:00

Example timestamp with this setting:
2024-10-31T14:16:48.762+00:00

thanks @thrashwerk
some of these I don't want to rebuild images for, so the version number doesn't need an increment.

haproxy
influxdb

the CHANGELOG format was changed for a more condensed style some time back, with x.y.Z changes grouped under a single X.Y item. Some haven't adapted yet.
Please remove the tmp.sh file


Webpack 4 not generating the webpackBootstrap function when more than 2 reducers

Bug report

https://stackoverflow.com/questions/51804768/webpack-4-not-generating-the-webpackbootstrap-function-when-more-than-2-reducers
What is the current behavior?
Webpack 4 not generating the webpackBootstrap function when more than 2 reducers
If the current behavior is a bug, please provide the steps to reproduce.
See GitHub project and Stackoverflow question for expanded details.
download the code from:
https://github.com/stuartsimpson/webpackbug
install nodeModules
changing the following lines of code in the coreReducers.js file will change when webpackBootstrap is generated.  When the webpackBootrap is generated the application will have the appropriate entry point.
//Not generating webpackBootstrap
var reducerList = {
    footerState: feedbackReducer,
    menuState: menuReducer,
    newReducer: newReducer
};

//Generating webpackBootstrap
var reducerList = {
    menuState: menuReducer,
    newReducer: newReducer
};

Please let me know if you need addtional clarfication over what is provided in Stackoverflow and the associated GitHub repository
Other relevant information:
webpack version:  4.14.0
Node.js version: 10.5
Operating System: Windows
Additional tools: React, Redux

I updated to the latest version of webpack (4.16.5) and now no mater what no webpackBoostrap function is created.

@sokra Thanks.  That worked.  However based on what i had read in the documentation I thought my configuration was correct.  Is there any documentation about what causes the webpackBootstrap function to be generated vs pushing functions/objects onto the webpackJsonp stack?


Add DeviceFrames support

Bug/issue #, if applicable: 102182966
Summary
Adds support for DeviceFrames for images and videos.

Dependencies

https://github.com/apple/swift-docc/pull/462

Testing
simpler.json.zip - this file is built with the docc branch above
Steps:

To test this you will need an archive that has @Image or @Video tags with deviceFrames.
You will also need to add deviceFrame definitions to your theme-settings.json file, as by default docc-render does not ship with frames. - see https://forums.swift.org/t/support-for-device-frames/62151 for more info

Checklist
Make sure you check off the following items. If they cannot be completed, provide a reason.

[x] Added tests
[x] Ran npm test, and it succeeded
[x] Updated documentation if necessary

One thing I feel that needs discussion is the different way a DeviceFrame is rendered for an Image vs Videos.
For the Image, I wrap it around a DeviceFrame component, right inside the ContentNode.
For the Video, I instead added a special conditional component inside the VideoAsset instead. This is because replayable videos cannot be wrapped in a frame, because then the replay button overlaps the frame, along with other resizing complications.
I am open to other suggestions, but this is what I could think of after much trial and error.

@swift-ci test

@swift-ci test

Also I saw that when you declare an image path but it doesn't exist in the doccarchive image folder, this error in console comes up.

I'll fill a different radar for it, no a blocker for this PR.

@swift-ci test

@swift-ci test

@swift-ci test

@swift-ci test


macOS Catalina: Scripting Addition fails to load

I am on macOS Catalina 10.15 (19A583) using yabai-v1.1.2. I turned off SIP in recovery mode and restarted before re-installing the scripting addition.
I am trying to use the scripting addition to switch spaces.

1.1.2 was a long time ago, and I don't think Catalina was a thing back then. Use version 2.0.1 or build from the master branch instead.

I ran brew install yabai again before making the issue and it seemed like it updated but maybe I should try updating to git master

You need yabai ≥2.0.1 on Catalina, and current master to avoid the window title bug. Just brew upgrade yabai, followed by sudo yabai --install-sa and brew services restart yabai.

That worked! Thank you!


Offline App

Does this app works offline ? I mean, Is service workers activated ?

The service worker is not enabled by default, it can be enabled by uncommenting the code here: https://github.com/driftyco/ionic-conference-app/blob/master/src/index.html#L15-L21


[DOCFIX] Add Running-Alluxio-On-Docker.md of Chinese version

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/13340/
Test PASSed.


Use explicit Interface types vs object in ISender and IPublisher.

Update ISender Send method to take explicit IRequest instead of object
Update IPublisher Publish method to take explicit INotification instead of object
Giving us compile time checks vs runtime.
Tests
Associated tests cases that are no longer required have been removed.
All other tests continue to pass.
I am not sure if this is a breaking change.  Technically the interface changes and thus some peoples code may not compile if they were using explicit object.  Which would mean this is a breaking change.  But they would have gotten a runtime error, where this will give a compile time error.

the object api was added explicitly in this PR https://github.com/jbogard/MediatR/pull/415/files why are you wanting to remove it?

See discussion on #385 too. There are two changes here too:

Adding generic constraints
Going from object to IRequest/INotification.

The object scenario supports cases where the types aren't known until runtime. Changing to IRequest won't result in a compile-time error, but a runtime exception:
object requestObject = DeserializeRequest(incomingJson);
IRequest request = (IRequest) requestObject; // Runtime exception if it doesn't match
await mediator.Send(request);

The exception will be the same whether MediatR does the casting or the consumer does it. I'd rather keep object to make this API very explicit about the intent, that you don't know the type at compile-time, only at runtime.

Ah I am reading #385 now and didn't think of this use case.  I vaguely remember reading something about this before.  I was updating my architecture and was wondering why this wasn't explicit. Did a quick search and couldn't find a reason ( guess I didn't look hard enough)

Ha no worries, I couldn't remember either and had to use blame to find out why. It was a good thought but would break existing folks for this scenario.

Yep,  I'm just used to things that are not strongly typed being a smell.  And implemented a delegate for ISender in my tests to wrap everything in a scope and wondered... why is the one strong typed and the other not.  :)
Itch scratched now I know.  Thanks.


nginx reverse proxy on non-root location

I'm working on a multi-container application that hosts a few different static files (grafana, couple custom SPAs, etc) via an nginx reverse-proxy and I'm trying to add a location for wifi-connect. Based on other services like grafana, node-red, etc, I should need to change configuration in wifi-connect for this to work but can't find anything relevant. I've tried a few different things here, including hosting wifi-connect from the root with no success.
What am I doing wrong here? Sample docker compose and nginx config below with just grafana and wifi-connect for simplicity.
version: '2.1'

volumes:
  data:

services:

  nginx:
    build : nginx
    ports:
        - '80:80'
        - '443:443'

  wifi-connect:
    build: wifi-connect
    expose:
      - '80'
    labels:
      io.balena.features.dbus: '1'
    cap_add:
      - NET_ADMIN
    environment:
      - 'DBUS_SYSTEM_BUS_ADDRESS=unix:path=/host/run/dbus/system_bus_socket'
      - 'PORTAL_LISTENING_PORT=80'

  grafana:
    build: grafana
    expose:
      - '80'
    volumes:
      - 'data:/data'
    environment:
        - 'GF_PATHS_DATA=/data/grafana'
        - 'GF_SERVER_HTTP_PORT=80'
        - 'GF_SESSION_PROVIDER=memory'

events {}

http {
  server {
    listen 80;
    root /usr/share/nginx/www;
    index index.html index.htm;

    location /data/ {
      proxy_pass http://grafana:80/;
    }

    location /wifi/ {
      proxy_pass http://wifi-connect:80/;
    }
  }
}

What is the error? During build? Connecting via NGINX? Connecting with your browser? Is there an error message?

I have it "working" on the host network, using port 81 so that MOST of the time users can just navigate to the IP and access the endpoints served up by nginx.
That means I can connect to the endpoint, navigate to http://<IP_ADDRESS>:81/ in the browser and get to WiFi Connect. Everything is excruciatingly slow though; making connection and loading the web portal both took minutes. Now I think if I do what you said and use a 301 within in nginx I can accomplish most of what I want. Yes, I'd like to get everything going through nginx but this isn't so bad of a workaround.
I'll post an update after I try it out.
Thanks @maggie0002 !

I couldn't actually get this working the way I wanted but I'm going to close this issue. My main driver here was to be able to access wifi-connect over LAN but I've gone away from that approach now.


Harvester not scraping links?

Hello,
I am a bit new to Javascript and this sort of stuff so apologies if I missed something. I am using Chrome Version 77.0.3865.90 (Official Build) (64-bit). I have disabled all extensions to rule out anything strange from those.
I am trying to scrape this search query page while waiting for a linguist pull request to go through. I followed the instructions to copy paste the javascript file into my console and I get undefined.
I run harvest(); as per the README, it displays Promise {<pending>} in console and starts searching pages. In the network tab, it goes through about 80 pages over about 6 minutes before sending me the notice to use copy(that);
I run that, try to paste whats in my clipboard, and it's blank.
Console shows this (immediately after I paste the script):
undefined
harvest();
Promise {<pending>}
copy(that);
undefined

I have also tried with harvest("mrc","mirc"); (on a new search page) to no avail. The network page URLs all seem to be valid.
Please let me know if I missed anything. Thanks :)

You aren't missing anything. It appears GitHub changed their markup again, meaning the script itself needs to be updated.
Leave it to me. 👍

Fixed.
I've also included the results of the extension:mrc mirc harvest below, to save you having to rerun and wait for the script all over again:

(List not shown in e-mail notification because I'm a considerate prick)


Postgres connection issues with newer drivers

I'm currently trying to evaluate App Optics in combination with node and postgres. I have a version of the server app running on node 10.2.1 inside a docker container, but when I try to start the server I get an error:
2018-09-20T11:03:00.957Z appoptics:warn ao.bind  - no context Error: CLS NOT ACTIVE
  at Object.exports.bind (./node_modules/appoptics-apm/dist/index.js:659:17)
  at Client.connect (./node_modules/appoptics-apm/dist/probes/pg.js:78:49)
  at Pool.connect (/./node_modules/pg-pool/index.js:207:12)
  at config.promise (./node_modules/pg-promise/lib/connect.js:22:11)
  at new Promise (<anonymous>)
  at Object.promise (./node_modules/pg-promise/lib/promise.js:23:20)
  at poolConnect (./node_modules/pg-promise/lib/connect.js:11:19)
  at Object.pool (./node_modules/pg-promise/lib/connect.js:127:24)
  at Database.query (./node_modules/pg-promise/lib/database.js:304:36)
  at Database.query (./node_modules/massive/lib/database.js:377:29)
  at Database.reload (./node_modules/massive/lib/database.js:202:10)
  at module.exports (./node_modules/massive/index.js:32:59)
  at module.exports (./packages/.../server/config/database.js:6:10)
  at listen (./packages/.../server/server.js:21:28)
  at Object.<anonymous> (./packages/.../server/server.js:17:1)
  at Module._compile (internal/modules/cjs/loader.js:702:30)

After this, I get information about the http requests on my dashboard, but the database connection isn't working. Any request that hits the database gets a similar warning.
The chain of dependencies means that we're using the 7.x series of pg drivers, so is there a roadmap for when you might be upgrading to use those, or am I barking up the wrong tree with that?

It's on our list to fix but I don't have a specific time-frame for you. There are currently 4 packages that require non-trivial fixes due to significant changes in their implementation.
https://node-postgres.com/guides/upgrading

If I can get a dev environment up and running I can take a look at the work required to update it if that would be useful? I tried running tests on the mac and mysql blew up, but I've added a skip option to it. Little steps, eh?

Also facing this issue (log message appoptics:warn ao.bind  - no context Error: CLS NOT ACTIVE).
I'm using any-db, any-db-postgres and any-db-transaction with appoptics-apm 5.6.1

@paps - are you also running pg 7.x drivers? if not, please provide the stack trace with the lost context. i've recently fixed quite a few of those (going to be in the 5.9.0 release) but I haven't seen them with pg for our currently supported versions.

@chooban - be happy to collaborate with you on this. our c-library doesn't compile/execute on a mac so you'll need a linux docker container to get things working. i can spend some time with you on getting a dev environment set up (given the caveat that i run linux, not mac) if you are interested in pursuing this.
i will be taking a look at it pretty soon.

@paps - no, i think you're ok running<EMAIL_ADDRESS>That version passes our tests, but with any system like postgres there are many situations we don't test. Can you provide the stack trace associated with those errors? And, if you know the query that is being used it would be great to get that as well.
useful info:

os
node version
npm ls --json
stack trace from error
query if you know what is being executed.

thank you so much for your help!

@bmacnaughton Apologies for the delay. I saw the notification then it got swamped by others. Happy to take a look at this with you. Do you have a dockerfile for getting up and running with it?

no worries. i get swamped with notifications too.
appoptics-apm v5.9.3 is just published. it has a number of changes primarily in v7 support. If you can give that a try I'd appreciate it. the biggest change in v7 is the way in which the pool works. v6 is somewhat challenging as it tries to maintain compatibility with previous versions and also implement the v7 changes.
We do have a docker-compose file and collection of docker files that can be used to develop and provide the testing database. it's not hard but there are a fair number of moving pieces. i'd be happy to work with you on that if 5.9.3 doesn't fix your issues and you can't use pg@7.
the CONTRIBUTING.md file has some hints about testing but it's not perfect. I develop using Linux so the making things work on the mac is not so well defined. Also, reading env.sh is helpful for two things:

it sets up APPOPTICS_SERVICE_KEY in a way that requires AO_TOKEN_STG be defined (I use our staging server for testing when I do test against a live backend) though the unit and probe tests do not require using a live collector.

i generally give it the "bash" argument and it sets up things for my command line environment. that's what you'd use inside the "main" container.

Also note that in the docker-compose file setting up the main container is commented out (I don't use it) and that it's an old version of node specified in test/docker/main.yml - the line to install node should change from v4 to whatever version you want to run.

One additional question - are you using callbacks, promises, or events to handle the asynchronous calls?

We released new postgres probes in v5.9.3. Could you give those a try and let us know whether it addresses your issues? They specifically addressed the pg v7 promises and pooled connections. our v6 instrumentation does not support promises but continues to support events and callbacks.

@chooban - the latest commit includes a a docker setup for the mac. It's test/docker/mac-os-test-env and can be used for developing and/or testing.

I believe this is addressed with the latest versions. And the koa-router problem has been addressed with your help - thank you.


Don't check soft deleted accounts on account create validation

Currently, in case an account (Stripe or Open Collective) is soft deleted, it's not shown in the finance tab and the maintainer is then promoted to setup an account (good). However, in the modal to connect a Stripe or OC account, they get an error message that an account is already connected to the organization, i.e our validation logic here does not filter out soft deleted accounts.

Won't fix for now 😄
Soft-deleting an account is not possible from the API right now (the change was done manually in DB). Since we have some unique constraints on account (good), the only way we could handle this would actually be to hard-delete the entry.


Paths starting with "../" point to the wrong directory.

Given this structure:
package.json
dist/
    lib.es.js
test/
    index.js
    rollup.config.js

Where index.js imports lib.es.js using with import lib from 'lib', running rollup -c test/rollup.config.js from the package root produces some weird results:

With alias({ lib: './dist/lib.es.js' }), it resolves to <pkg>/test/dist/lib.es.js (testing 1..2..3)
With alias({ lib: './../dist/lib.es.js' }), it resolves to <pkg>/dist/lib.es.js (ok, we got it)
With alias({ lib: '../dist/lib.es.js' }), it resolves to <pkg's parent>/dist/lib.es.js (wut?!)

When you start the path with ../, the "current directory" is no longer test but the package directory, causing the path to overshoot and resolve to the wrong path.

Hey folks. This is a saved-form message, but rest assured we mean every word. The Rollup team is attempting to clean up the Issues backlog in the hopes that the active and still-needed, still-relevant issues bubble up to the surface. With that, we're closing issues that have been open for an eon or two, and have gone stale like pirate hard-tack without activity.
We really appreciate the folks have taken the time to open and comment on this issue. Please don't confuse this closure with us not caring or dismissing your issue, feature request, discussion, or report. The issue will still be here, just in a closed state. If the issue pertains to a bug, please re-test for the bug on the latest version of Rollup and if present, please tag @shellscape and request a re-open, and we'll be happy to oblige.


feat: support lsp buffer formatting when formatting the whole file

solves: https://github.com/stevearc/conform.nvim/issues/271
Turned out to be such a simple change... opts.range should just be nil when the whole buffer is selected.
cc @wookayin

This LGTM. Ideally we would add magic support for range formatting for the LSPs that don't do it natively like we do for normal formatters, but that would be a lot of work (which is why I haven't done it yet). This is a reasonable workaround for this use case.

Thanks! I see, that indeed sounds great.


Issue templates

Description
Added more changes to the issue templates and created an additional template for documentation changes
Type of change

Documentation update

Love this and the red panda :)

@edwinthinks and @cielf, can you please elaborate on what "Acceptance Criteria" means? I'm not following.

We used to have a section "Criteria for Completion"  where we would list the the things that have to be done for the issue to be considered complete.   That's what I mean by Acceptance Critera.     See [https://github.com/rubyforgood/human-essentials/issues/2475] for an example.

Okay. I thought that's what you meant but I was confused because I have a "Criteria for Completion" section in the Feature Request template. I just added one to the Bug Report template as well.
I don't think the Documentation one needs it.


Missing "ent" in annotation

Hi Li,
when I want to preprocess some data new for the model, I have encountered an error which warns me about missing the "ent" field. I think there may be a omit in wikisql/annotate.py, and here is my solution:
def annotate(sentence, lower=True):
    global client
    if client is None:
        client = CoreNLPClient(default_annotators=['ssplit', 'tokenize', 'pos'])
    words, gloss, after, ents = [], [], [], []
    for s in client.annotate(sentence):
        for t in s:
            words.append(t.word)
            gloss.append(t.originalText)
            after.append(t.after)
            ents.append(t.pos)
    if lower:
        words = [w.lower() for w in words]
    return {
        'gloss': gloss,
        'words': words,
        'after': after,
        'ent': ents
    }

Hope it could help others, thanks :-D

Hi @SivilTaram ,
Thanks for the code!
import spacy
import codecs
import json
from spacy.tokens import Doc

nlp = spacy.load('en_core_web_lg')

def anno_main(anno_path):
    with codecs.open(anno_path.replace('annotated', 'annotated_ent'), "w", "utf-8") as f_out:
        with codecs.open(anno_path, "r", "utf-8") as f_in:
            for line in f_in:
                js = json.loads(line)
                w_list = js['question']['gloss']
                ws_list = [it.isspace() for it in js['question']['after']]
                doc = Doc(nlp.vocab, words=w_list, spaces=ws_list)
                for name, proc in nlp.pipeline:
                    doc = proc(doc)
                js['question']['ent'] = [tk.tag_ for tk in doc]
                assert(len(js['question']['ent']) == len(js['question']['words']))
                f_out.write(json.dumps(js))
                f_out.write('\n')

for split in ('train','dev','test'):
    anno_main("data_path/WikiSQL/annotated/{}.jsonl".format(split))


Create a contributing section on the website

Remove the contributing file
Move content to the website
Add anymore useful things necessary to the contributing section.

- # Contributing

- This isn't a job! Have fun!

## Code Philosophy

- Similar to how DD supports cross platform runtimes, we also are very flexible in the codebase. Where it makes sense to use Classes they can be used but mostly we prefer using no-class based approach.

Some things that could be useful for contributing:

Prerequisites
Description of the tooling used (this could just be a list with links to websites etc)

TypeScript
ESLint
Yarn monorepo
Turborepo
etc

Getting started

Clone, setup commands, etc
Maybe provide a development project? Something that is a common pattern to test with?
Linking project to monorepo (if applicable)
Common development commands (build, linting, etc)

I do have concerns with too much detail and becoming a book, I tend to be detailed anyway. I'm not sure how in depth it's recommended to go. I read things like Quasar and Laravel which are super bare bones. So I don't know. I see there's questions about this stuff but how much do we want to assume people know before contributing?


[Feature][WIP] Introduce alarm e2e test

What changes were proposed in this pull request
Issue Number: close #3854

Add basic alarm e2e test cases.

Brief change log

Verifying this change

This change is a trivial rework / code cleanup without any test coverage.
(or)
This change is already covered by existing tests, such as (please describe tests).
(or)
This change added tests and can be verified as follows:

Does this pull request potentially affect one of the following parts

Dependencies (does it add or upgrade a dependency): (no)

@SbloodyS Is there anything that needs to be improved in the current content? I'd love to improve it.🫡


can't create new index

As title, the index does not exist. But when I create it, nebula says it exists.

No problem
When creating an index, if there is no index field, it can only be created when the tag/edge is without any index.

No problem
When creating an index, if there is no index field, it can only be created when the tag/edge is without any index.


Start writing installation instructions

I think this is good enough. The deadline to submit this is Friday. If we want to make any changes before then, we can just push them up.


Dispenser doge activity check when opening in empty address

Looks good in testing, errors thrown for address with XDP and DOGE balances.
[2023-12-23 03:04:16][WARNING] Error composing dispenser transaction via API: ['cannot open on another address if it has any balance history']
[2023-12-23 03:04:16][WARNING] Traceback (most recent call last):
  File "/dogeparty-lib/dogepartylib/lib/api.py", line 587, in create_method
    return compose_transaction(self.db, name=tx, params=transaction_args, **common_args)
  File "/dogeparty-lib/dogepartylib/lib/api.py", line 434, in compose_transaction
    tx_info = compose_method(db, **params)
  File "/dogeparty-lib/dogepartylib/lib/messages/dispenser.py", line 161, in compose
    if problems: raise exceptions.ComposeError(problems)
dogepartylib.lib.exceptions.ComposeError: ['cannot open on another address if it has any balance history']

[2023-12-23 03:04:51][WARNING] Error composing dispenser transaction via API: ['cannot open on another address if it has any confirmed dogecoin txs']
[2023-12-23 03:04:51][WARNING] Traceback (most recent call last):
  File "/dogeparty-lib/dogepartylib/lib/api.py", line 587, in create_method
    return compose_transaction(self.db, name=tx, params=transaction_args, **common_args)
  File "/dogeparty-lib/dogepartylib/lib/api.py", line 434, in compose_transaction
    tx_info = compose_method(db, **params)
  File "/dogeparty-lib/dogepartylib/lib/messages/dispenser.py", line 161, in compose
    if problems: raise exceptions.ComposeError(problems)
dogepartylib.lib.exceptions.ComposeError: ['cannot open on another address if it has any confirmed dogecoin txs']