No error is thrown when two types differ by one or more properties

🔎 Search Terms
error,thrown,types differ,one or more properties
🕗 Version & Regression Information

I was able to test this on version 5.3.3

⏯ Playground Link
https://www.typescriptlang.org/play?#code/JYOwLgpgTgZghgYwgAgKoGdrIN4ChnLAAmAXMiAK4C2ARtPshFXMADZnphSgDmDADnHToA7gHsopZJ24g+AX1y5QkWIhQBhVhDggIRDFjwFiZSrXoEmLdtK69ci3AjEhOyCpihlDUZAF4cBlNkAEYAGgZrNjIAcljIgkFhcUk42MclFzcwZARtXX1fMi0dPQMvAI8vJSA
💻 Code
interface User {
  id: number
  email: string
  password: string
}

interface CleanedUser {
  id: number
  email: string
}

const user: User = {
  id: 1,
  email: '',
  password: ''
}

const cleanedUser: CleanedUser = user

🙁 Actual behavior
No error received when i assign User to CleanedUser
🙂 Expected behavior
I would like to see an error that tells me that the CleanUser and User type are not equals because "password" or any additional properties are not allowed to the CleanedUser type.
Additional information about the issue
Is there a way to configure that behavior inside the tsconfig file?

This is working as intended, see also: https://github.com/microsoft/TypeScript/wiki/FAQ#what-is-structural-typing
You would need #12936 for this.

To exclude specific properties you can do this:
interface CleanedUser {
  id: number
  email: string
  password?: never
}

@MartinJohns Re: Confused emoji - optional properties typed as never is a common pattern to prevent specific properties from existing on a type.  The property can either be omitted (because it's optional) or exist with type never, but because there are no values of type never, the effect is to prevent the object from having that property at all.  It's often used to express unions like { a: string, b?: never } | {a?: never, b: string }

Confused is the wrong emoji, but I didn't want to give the thumbs down smiley. I really don't like this hacky workaround.
Most of you wrote is correct, except the "the effect is to prevent the object from having that property at all". A property typed never does not necessarily mean it doesn't exist, it could also be a property that throws upon accessing. The type Record<string, never> was once described by Ryan as "an object that throws upon accessing any property".
This code works perfectly fine and logs true:
interface CleanedUser {
  id: number
  email: string
  password?: never
}

const f: CleanedUser = {
  id: 1,
  email: 'foo',
  get password(): never { throw new Error() }
}
console.log('password' in f)

That's fair; I'd argue that still matches intent in this case since the effect is to prevent reading a password off of a "cleaned" user, but I can see that being problematic in other scenarios.  The alternate version is password?: undefined but that breaks exactOptionalPropertyTypes (if it's used) and also doesn't fix the in issue you highlighted.
Ultimately I agree that #12936 would be the non-hacky fix, but realistically it'll probably never happen.

@MartinJohns

hacky workaround.
it could also be a property that throws upon accessing.

Note that any property could throw upon accessing, yet generally one interprets {x: string} as an object with a string-valued x property without the caveat that maybe the x property will throw when accessed instead.   An object of type {x?: never} is, in descending order of reasonableness:

an object without an x property
an object with an x property of type undefined (depending on compiler settings)
an object that throws when you access x
an object that throws when you access it in any way

I'd generally stop at the top bullet when discussing this unless unless such secondary and tertiary effects become important.  I wouldn't call this a "hack", unless I wanted to reinterpret anything that neglects "this might throw" as a hack as well.


[google_maps_flutter] Fix Android unit test.

Fix test broken by https://github.com/flutter/engine/commit/15f5696c4139a21e1fc54014ce17d01f6ad1737c#diff-599e1d64442183ead768757cca6805c3L154.
Turns out it was never needed for the test anyway.

I'll merge this as soon as all the checks pass. Will have to merge with submit-queue on red, since this PR is fixing the current breakage of the tree.

Also /cc @cyanglaz FYI (you wrote the original version of the test).


Inspectors in the Emulator are not working

downloaded and launch the nightly build (I used:  https://github.com/Microsoft/BotFramework-Emulator/releases/tag/untagged-7eff57d325872c45d04f)
the web view isn't mounting

Fixed in #880


In sidebar search bar disable ssr specifically for the cmd+K/ctrl+K text

We are currently disabling ssr for the search bar component as the content within it relies on platform information (cmd+K on mac vs ctrl+K on windows) which we're retrieving from User-Agent with ua-parser-js and that information doesn't exist server-side. To prevent sudden jumps in the interface, we may want to try extracting the text into a tiny component and disabling ssr specifically for that component to mitigate flash/jump issues.
https://github.com/fern-api/fern/blob/c76b12f0ad21b042f9feadb4256d0070caab79b3/packages/ui/app/src/sidebar/SidebarSearchBar.tsx#L32-L34

Done.


MAINT: master to main, and various maintenance tasks

This PR updates master to main

[x] updates base python to python=3.11 for all tests and tests 3.10 and 3.11
[x] removes netlify powered previews (as not required)
[x] adds github actions dependabot
[x] upgrades version pinnings for tests to run in more recent python context
[x] updates text fixtures
[ ] update default branch name on github

@agoose77 would you like to review or are you happy for me to merge this to start updating sphinx-proof?

@mmcky can we install pre-commit.ci on this repo instead of using an action? (https://pre-commit.ci)

@mmcky can we install pre-commit.ci on this repo instead of using an action? (https://pre-commit.ci)

great idea @agoose77 -- happy to try and set this up tomorrow.

@agoose77 I reverted f556407 as I wasnt sure how to satisfy the pre-commit requirement in the publish workflow to pypi.

thanks @agoose77 for your review. 👍


events mousehover, mouseactive

hover and active are both one-way bindings - they are events, so probably we can itegrate them to @events, we can add modifier "model" to declare that we use model instead of js expression.
@mousehover.model="model"
@mouseactive.model="model"

for "hover" we can use "mouseenter + mouseleave"
@mousehover.model="model"
==
@mouseenter="model=true" @mouseleave="model=false"
for "active": mousedown + mouseup + mouseleave

https://jsfiddle.net/lega911/x4ggb2ct/

In this case maybe another directive would be great (especially für mobile applications):
al-isvisible
When the visibility state of an element gets changed, it should toggle a boolean model variable.
I think it will be hard to implement, because there are no events which can be watched.


SyncPlay crashes on CentOS 8

When trying to run syncplay I get these errors:
Jun 24 00:09:39 BLDM syncplay_syncplay.desktop[16180]: WARNING: icon cache generation failed for /home/username/snap/syncplay/3/.local/share/icons/default
Jun 24 00:09:39 BLDM syncplay_syncplay.desktop[16180]: Warning: Qt4 does not support Wayland!
Jun 24 00:09:42 BLDM syncplay_syncplay.desktop[16180]: QIconvCodec::convertFromUnicode: using Latin-1 for conversion, iconv_open failed
Jun 24 00:09:42 BLDM syncplay_syncplay.desktop[16180]: QIconvCodec::convertToUnicode: using Latin-1 for conversion, iconv_open failed
Jun 24 00:09:43 BLDM syncplay_syncplay.desktop[16180]: QGtkStyle could not resolve GTK. Make sure you have installed the proper libraries.
Jun 24 00:10:18 BLDM kernel: python3[16180]: segfault at 5ea0 ip<PHONE_NUMBER>005ea0 sp 00007ffd8a223798 error 14 in python3.5[3ff000+1000]
Jun 24 00:10:18 BLDM kernel: Code: Bad RIP value.
Jun 24 00:10:18 BLDM systemd[1]: Started Process Core Dump (PID 16429/UID 0).
Jun 24 00:10:19 BLDM systemd-coredump[16430]: Process 16180 (python3) of user 1000 dumped core.#012#012Stack trace of thread 16180:#012#0  0x0000000000005ea0 n/a (n/a)

The above is the messages log when run from the GUI, below is when run from Terminal:
$ syncplay
Warning: Qt4 does not support Wayland!
QIconvCodec::convertFromUnicode: using Latin-1 for conversion, iconv_open failed
QIconvCodec::convertToUnicode: using Latin-1 for conversion, iconv_open failed
QGtkStyle could not resolve GTK. Make sure you have installed the proper libraries.
 I should've known better than to use some garbage installer like that thinking it could actually do it's job.
-- Cheers!


构建时出错 media_kit: arm64-v8a JAR verification failed.

运行环境：
environment:
  sdk: '>=2.19.4 <3.0.0'

# Dependencies specify other packages that your package needs in order to work.
# To automatically upgrade your package dependencies to the latest versions
# consider running `flutter pub upgrade --major-versions`. Alternatively,
# dependencies can be manually updated by changing the version numbers below to
# the latest version available on pub.dev. To see which dependencies have newer
# versions available, run `flutter pub outdated`.
dependencies:
  flutter:
    sdk: flutter

  # The following adds the Cupertino Icons font to your application.
  # Use with the CupertinoIcons class for iOS style icons.
  cupertino_icons: ^1.0.2
  media_kit: ^1.1.7
  media_kit_video: ^1.1.8
  media_kit_libs_video: ^1.0.1

出错信息：
FAILURE: Build failed with an exception.

* Where:
Build file 'D:\Pub\hosted\pub.flutter-io.cn\media_kit_libs_android_video-1.3.3\android\build.gradle' line: 102

* What went wrong:
A problem occurred evaluating project ':media_kit_libs_android_video'.
> media_kit: arm64-v8a JAR verification failed.

* Try:
> Run with --stacktrace option to get the stack trace.
> Run with --info or --debug option to get more log output.
> Run with --scan to get full insights.

* Get more help at https://help.gradle.org

BUILD FAILED in 1s
Exception: Gradle task assembleDebug failed with exit code 1

The CI succeeds:
https://github.com/media-kit/media-kit/actions/runs/6158991342/job/16712896080
Check your internet, flutter clean etc.


docker: fix starting containers with a local connection

Description of changes
Fixes #244159
Issue is caused by a fix in Go 1.20.6, see upstream issue https://github.com/moby/moby/issues/45935

Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[x] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[x] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
23.11 Release Notes (or backporting 23.05 Release notes)

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

[x] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 244290 run on x86_64-linux 1

18 packages built:

apptainer
apptainer-overriden-nixos
apx
charliecloud
docker (docker_20_10)
docker-gc
docker.man (docker_20_10.man)
fn-cli
nvidia-docker
pipework
python310Packages.jupyter-repo2docker
python310Packages.jupyter-repo2docker.dist
python311Packages.jupyter-repo2docker
python311Packages.jupyter-repo2docker.dist
singularity
singularity-overriden-nixos
udocker
udocker.dist

I'm taking a look but we might need to also patch docker-compose https://github.com/docker/compose/pull/10810

23.05 is also at 20.10.23 and from quick glance the automatic backport should work.


Separate task manager and task store

#3572

Coverage increased (+0.1%) to 68.915% when pulling 5f301b626500a34e0c374db1b8cb9cd808fefe0d on anish531213:aanish/taskStoreOperation into 6539b80f7bbf8def6d7dfef0000d39383a30d513 on uber:master.


Inotify implementation doesn't remove subdirectories after remove_directory

I have directory structure like this:
dir1
|
+- dir2
After running remove_directory("dir1") events in "dir1" are not catched, but events in "dir2" continue to be catched. Is it a bug or feature?

That's a bug. I do have a patch for it in my fork sorry haven't created a PR for it, I will.

https://github.com/berkus/dir_monitor/pull/14

Fixed by PR #15


Implement the MPU from Megatron

The Megatron code contains a "MPU" library. MPU stands for "model parallelism unit." The purpose of an MPU is to allow custom tensor slicing across GPUs. DeepSpeed allows you to hook up a MPU, but doesn't provide one. The goal is to convert the MPU from Megatron to GPT-NeoX. This is a modified clone of Megatron: https://github.com/EleutherAI/MegatronPipeline
You may find the (minimalistic) descriptions DeepSpeed provides helpful:
https://www.deepspeed.ai/features/#model-parallelism
https://www.deepspeed.ai/tutorials/megatron/
The full DeepSpeed docs can be found here: https://deepspeed.readthedocs.io/en/latest/index.html

Superseded by codebase refactoring.


Feature/b2018072301 add bmp61 to paynetics response messages

Added support for BMP61 paynetics subfieldsrr

I have run the specs and there are no failing ones.


Fix formatting of async blocks

Fixes #3344
Fixes #3433

The CI failures seem irrelevant to this PR.

Thanks1


Update the limitador-server/kubernetes yaml

[ ] There are things still pointing to the 3scale org on quay.io…
[ ] Need to update to v1.0.0 of limitador as well
[ ] More…?

Or should we simply delete all of them?


[Bug]: Invalid displacement location error React Native

Mapbox Implementation
Mapbox
Mapbox Version
main
Platform
Android
@rnmapbox/maps version
10.0.0-beta.65
Standalone component to reproduce
Created a Map component where I need the userLocation property enabled, nothing special there.
import MapboxGL, { MarkerView, Logger, offlineManager, Point } from '@rnmapbox/maps';
MapboxGL.setWellKnownTileServer('Mapbox');
MapboxGL.setAccessToken(
'XXX'
);

 { console.log('Coords:', JSON.stringify(feature.geometry)); setOcurrenceLocation(feature.geometry.coordinates) }}
          >

            {(ocurrenceLocation) &&
              renderAnnotations()}
      </MapboxGL.MapView>

  </View>
</SafeAreaView >

Observed behavior and steps to reproduce
Observed behavior and steps to reproduce
I was running an app using mapbox for some time, and since this weekend, after reinstalling npm the app after requesting the the location permission started to crash.
If I comment the mapbox code, it will work, can you please help?

Expected behavior
No errors
Notes / preliminary analysis
No response
Additional links and references
No response

return (
<SafeAreaView style={styles.safeAreaView}>
    <View style={styles.mapContainer}>
      <MapboxGL.MapView
        style={styles.map}
        styleURL={MapboxGL.StyleURL.Street}
        logoEnabled={true}
        localizeLabels={true}
        onPress={(feature) => { console.log('Coords:', JSON.stringify(feature.geometry)); setOcurrenceLocation(feature.geometry.coordinates) }}
      >
        <MapboxGL.UserLocation
          visible={true}
          showsUserHeadingIndicator={Platform.OS === 'ios'}
        />
        <MapboxGL.Camera
          zoomLevel={10}
          animationMode={'flyTo'}
          animationDuration={2000}
          followUserLocation={true}
        />
        {(ocurrenceLocation) &&
          renderAnnotations()}

      </MapboxGL.MapView>

  </View>
</SafeAreaView >

);
};

Resolved by exposing the LocationManager
export const { locationManager } = MapboxGL;
then,
import { locationManager } from '@rnmapbox/maps';
locationManager.start(1);

or forcing a value here
@ReactMethod
public void start(float minDisplacement) {
    isEnabled = true;
    mMinDisplacement = 1;
    startLocationManager();
}

Had the same issue.
Platform: Android
Fixed it by downgrading to version 10.0.0-beta.64. Here's the relevant link which shows the fix.
Thanks @BrunoArrojado!

I can't reproduce on the current main.
But I wasn't able to use your component because of third party libraries, internal dependencies (../../hooks/useApi), etc. Please clean up and minimise next time

This one is really a big issue, can someone confirm, if this has been fixed?

or forcing a value here
@ReactMethod
public void start(float minDisplacement) {
    isEnabled = true;
    mMinDisplacement = 1;
    startLocationManager();
}

Where we need to place these settings?


Added plugin hooks before and after the kirby user gets logged in

Added hooks before and after the kirby user gets logged in.
This was suggested in https://github.com/thathoff/kirby-oauth/issues/30#issuecomment-1432739791
An example use-case is to process the given roles in the oAuthUserData to assign kirby roles.
It would be nice if something like this could be added to the plugin. Feel free to change anything.

Thanks for your pull request. I would prefer to have the second parameter of the hook require a ResourceOwnerInterface as this is typed and could make things more flexible (so in code it would be $oauthUser).
I would also move the before hook before the whole gate logic starting here so it's possible to prevent user creation with the hook.

So, for my understanding:
Instead of the oauthUserData you want to pass the oauthUser to provide the full ResourceOwnerInterface. This would change the first parameter of the hook. The second is the kirby user, so that an additional plugin can work with the oauthUser and the kirby-user.
You suggest the before hook in front of line 148 to make it possible to prevent user creation? Or do we need to put that hook inside the If-clause to only trigger when the user does not exist (in this case, before line 149)? This hook would not be a login:before-hook in my opinion because it's before the user-creation, so this should be a third hook with only the oauthUser I think.
Something like: $this->kirby->trigger('thathoff.oauth.user-creation:before', ['oauthUser' => $oauthUser]);
Do you agree, or did I misunderstand something?

Sorry for my late reply, I’ve been on vacation.

Instead of the oauthUserData you want to pass the oauthUser to provide the full ResourceOwnerInterface. This would change the first parameter of the hook. The second is the kirby user, so that an additional plugin can work with the oauthUser and the kirby-user.

Yes you’re right.

You suggest the before hook in front of line 148 to make it possible to prevent user creation? Or do we need to put that hook inside the If-clause to only trigger when the user does not exist (in this case, before line 149)? This hook would not be a login:before-hook in my opinion because it's before the user-creation, so this should be a third hook with only the oauthUser I think.

Then i would go with:
$createResult = $this->kirby->trigger('thathoff.oauth.user-create:before', ['oauthUser' => $oauthUser]);
$kirbyUser = null;

// if the hook returns a kirby user we take this one
if ($createResult instanceof \Kirby\Cms\User) {
   $kirbyUser = $createResult
}

// if the hook returns null or true the user is created
if ($createResult === true || $createResult === null) {
   // go on with user creation
}

if (!$kirbyUser) {
    $this->error("User cannot be created.");
}

and
$this->kirby->trigger('thathoff.oauth.user-create:after', ['oauthUser' => $oauthUser, 'user' => $kirbyUser]);

@Greakz Will you have time to implement the changes suggested by @thathoff ?

Sorry for my late reply, I’ve been on vacation.

Same here, sorry.

@Greakz Will you have time to implement the changes suggested by @thathoff ?

Yes, the changes should be implemented. The only thing left to do is change the version in composer.json (I guess this will be 3.1.0?) but i think this is up to you @thathoff
Tell me if you want other changes in this PullRequest or if you are fine with what we got now @thathoff

Thank you! I’ll check everything and maybe include this feature right into the next release.


Demonstrate how succeed can return a value

This page has instructions on how succeed can return a value, but we don't demonstate that.
I don't know if we could show it succinctly without defining a sub
sub use-succeed() {
  given 42 {
    when Int {
        # say "Int";
        succeed "Found";
        say "never this!";
    }
    when 42 { say 42 }
    default { say "dunno?" }
  }
}

say use-succeed();

Or using do given, perhaps. Like my $value = do given { ... }

Or using do given, perhaps.

Yep. Just prepend a say do  in front of the existing example in the doc:
say do given 42 {
    when Int {
        say "Int";
        succeed "Found";
        say "never this!";
    }
    when 42 { say 42 }
    default { say "dunno?" }
}
# OUTPUT: «Int␤Found␤»

I've opened a PR with a small modification on your suggestion #4547


fix(EnterpriseContract): show ec results under security tab from tkn

Fixes

https://issues.redhat.com/browse/RHTAPBUGS-1100
Description

extract ec results from task run logs from tekton results
Type of change

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

Screen shots / Gifs for design review

How to test or reproduce?

Browser conformance:

[ ] Chrome
[ ] Firefox
[ ] Safari
[ ] Edge

/lgtm


Magic mode removed from 0.9

I can see in the releasenotes that Magic has been removed. 👎
This was probably done to make ractive lighter amd more easy to maintain 👍
But sadley for "us" this was one of the major features that we relied on.
Because we were able to develop POJO View Models without "thinking" of the get and set method of ractive.
I can see that there has been some talk about creating an adaptor to achive the same functionality, any work on this?
I belive it would be a bit of work to create such an adaptor, but the code from ractive should be reusable i guess.

The thread for its removal can be found in https://github.com/ractivejs/ractive/issues/2798. Taking out features with unpredictable behavior and/or hacky implementation was the primary motivation. Making Ractive lighter was a side-effect of taking things out.
There are plans to build an external adaptor for it.

I will give it a go,  and try to implement it using js  proxy object.
Have not looked to much into it yet but I guess this is a good approach.

I am now closing in on implementing "magic mode" using Proxy approach,
I have some issues when it comes to manipilating arrays. How should I signal to ractive that some array modification has occured, (push,pop,splice,shift,unshift)
All other stuff is signaled by triggering the Update(keypath), this is of course still for internal use only.
@fskreuz ?

Calling ractive.update() after the changes should do the trick for either object or array.

The lack of a way to tell ractive that a splice has occurred is one of the TODO items in #2512. You can work around it to some extent with ractive.set(keypath, array, { shuffle: true }) after you perform the splice operation on the underlying array array. That will trigger the shuffling logic, though not quite as efficiently as the ractive splice operation.

`var createProxy = function (r, data) {
var trap = new ObjectProxyTrap(r);
var ret = new Proxy(data, trap);
trap.proxy = ret;
return ret;
}
var ObjectProxyTrap = function (ractive,path) {
    if (!path) { path = [] }
    var self = this;

    this.proxy = null;
    var cache = {};

    this.get = function (target, name) {

        if (!cache[name]) {

            var tempData = Reflect.get(target, name); //target[name];
            if (!tempData) return;

            if (typeof(tempData) === "function"){
                cache[name] = function () {
                    return tempData.apply(self.proxy, arguments);
                }
            }
            else if (tempData instanceof Object) {
                var p = path.slice(0);
                p.push(name);
                var trap = new ObjectProxyTrap(ractive, p);
                cache[name] = new Proxy(tempData, trap);
                trap.proxy = cache[name];
            } else {
                return tempData;
            }
        }
        return cache[name];
    }

    this.set = function (target, fieldName, newVal) {

        //target[fieldName] = newVal;
        Reflect.set(target, fieldName, newVal);
        var keyPath = path.join(".") + "." + fieldName;
        delete cache[fieldName];
        ractive.update(keyPath, { force: true });

        return true;
    }

}`

Basic idea for trapping calls.
Use like this.
v.view = new ractive(instanceOptions);
v.view.set(createProxy(v.view, data));
Any comments?

Magic mode should be avoided for the simple fact of performance and reablilty IMO. Stick with built-in methods. As a small side note I myself use a modified version of Ractive that contains several extra methods extended to components. It brings copious amounts of utility functions into Ractive components allowing for less repetitive code. That's what you should be doing here instead of magic mode. I'm absolutely thrilled magic mode is gone.

I do think removing the MagicMode is a good move, the problem is that we have a lot of UI that is dependant on it  :(
The way we use ractive, our ViewModel is not aware of ractive at all so it will take considrable amount of time to rewrite it, magic mode took care of that :)
But yes, I agree removing MM is a sane thing to do. 👍


Document the flow for creating official images and the steps needed.

Problem
There are no clear documentation on what it takes to create an official image.
Solution
Document the steps to create and submit a new official image to the correct repositories.  @tianon can be a source for information on what needs to happen and what is expected.

What about this doc? https://github.com/docker/docker/blob/master/docs/sources/docker-hub/official_repos.md

I think what's missing is mainly some process-related information;

What counts as an official image? (ie, if I am the author of an open-source project, can I submit it as an official image?)
Is there some kind of approval proces?
Who is allowed to submit (and maintain) an official image? e.g., can I submit a "Microsoft Windows" image, even if I'm not affiliated with Microsoft?
After submitting, how much time is required for me to maintain the image? What does Docker expect from me as a maintainer?

I think @psftw is working on some updates to this, actually.

Better late than never. https://github.com/docker/docker/pull/12644
I'm also going to take a look at the docker-library/official-images documentation next to see if I can't address some FAQs about the requirements there.


categorical tags for biosamples

@emileyfadrosh has requested tags that would make it easier to find biosamples with shared methods, funding, etc. in the Data Portal. Other NMDC team members have been supportive.
I will implement this as a new slot on the Biosmaple class, whose range will be an enumeration
@emileyfadrosh and others will be responsible for

adding descriptions, meanings and see_also links for the permissible values
annotating a dump of the MongoDB bisoample_set collection with the appropriate permissible values

@dwinston said that may have a good way to make a spreadsheet out of the bisoample_set collection. But can't we just do a CSV export from Compass?

Proposed permissible values:

LTER
SIP
SFA
FICUS
NGEE
warming

cc @sujaypatil96 @cmungall

@turbomam my contribution to enabling a csv export of biosamples for annotation would be this nmdc-runtime code that demos flattening JSON hierarchy and folding in other pertinent info to a biosample row if desired. In this case, it was including all omics types associated with omics_processing_set documents that has_input that biosample.

See also https://github.com/microbiomedata/nmdc-schema/issues/467

@turbomam
We have #467 and there's a merged PR for this issue. Can we close this one if favor of the new issue?


Model the .NET BroadcastQueue

.NET has a class called BroadcastQueue which orchestrates the updating of ChatHistory from channels (assistant threads).  We can model this in reactive streams (project reactor).

Understand the .NET BroadcastQueue and how it works to sync history among AgentChannels
Model this in reactive streams.
Provide unit tests.

Done is defined as

Having the API for Agent, AgentChannel, and ChatHistory necessary to support updating chat history from multiple sources in an asynchronous fashion.
Having a sample of unit tests that exercise the BroadcastQueue functionality.

The intent of BroadcastQueue (notes from Teams chat with Chris Rickman):
Functionally, the state of each channel needs to be "in-sync" at the point an agent based on said channel is invoked.  This becomes critical when ChatCompletionAgent and OpenAIAssistantAgent are participating in the same AgentChat.
If they don't have the most up-to-date message the response won't have fidelity.
Syncing a ChatHistoryChannel is virtually instantaneous...for an assistant-agent, its based on an REST API call (to store the messages on the thread).
Syncing OpenAIAssistantChannel could therefore have non-trivial latency.
We don't want to block the chat on each turn to sync every channel.
Each ChatCompletionAgent (by default) does share the same history since they utiliize the same channel (based on the channel-key contract).
An assistant requires that all messages be saved to the thread, which is managed remotely by the API
Multiple assistants will share the same thread-id / channel (by default) [I'll come back to qualify "default" in a minute)
Ultimately, if an assistant-agent isn't taking a turn...it doesn't make sense to block on synchronization (just slow down the entire experience)
The BroadcastQueue is responsible for taking a request to broadcast the most recent messages to all channels, without blocking the caller.  Blocking only occurs when a channel is being used whose queue is not empty.
I specifically didn't want to manage a background thread looping to manage the queue...so it's all driven / triggered by adding to the queue.
I also took care to minimize as much as possible how much locking was utilized (since that can also impact performance)
In terms of the "default" qualification - it is possible for different ChatCompletionAgents to be managed in separate channels based on the presence / configuration of the HistoryReducer...this is because the reducer alters the channel specific history.
Example:  Two chat-completion agents, one with a reducer and one without will each use a different channel so that their channel history is managed as each expects.  Any chat-completion agent using a reducer with equivalent configuration will consolidate to the same channel.
For an assistant-agent, it is possible for the caller to create one that targets one endpoint and another that targets a different endpoint.  This might be an assistant that targets OpenAI and one that targets Azure...or maybe they target different azure regions or subscriptions.
In these cases, an assistant wouldn't be able to share the same thread-id.  This necessarily requires a different channel based on the assistant configuration
So, in the "vanilla" case for mixing chat-completion and assistant agents, one would expect two channels...but this isn't necessarily a given for all usage cases.


Continuous treatment variables

Probably it is in the documentation and I missed it, but can someone point me to the definition of causal effect for continuous treatment data, and how to calculate them use dowhy?
Do we bin the continuous treatment? Thanks!

You do not need to bin them. In DoWhy, the causal effect is defined wrt. the two values: treatment_value and control_value. For a continuous variable, you can set these values to get the effect of the variable with the desired change.
As for estimation, not all methods support continuous treatment. Among the in-house dowhy methods, the linear regression model does. Otherwise, you can use methods from econml, e.g., the double ml (dml) estimator.

Thanks @amit-sharma !
Just to be sure that I get it: if I for example have age, ranging from 1 to 99, then I have to choose to values among those? For example 8 and 77, as treatment and control respectively. Because in this case I am not sure what does it mean setting to 0 age and then to 1 (for a general problem).

yes, you can choose any value of age. 0 and 1 would not make sense, perhaps 8 and 77 are more interesting.
More generally, you may be interested in plotting a "dose response curve": the causal effect of increasing age from 1-5, 5-10, 10-15, and so on. https://en.wikipedia.org/wiki/Dose–response_relationship

Closing this issue. If you have any further questions, feel free to reopen it

You do not need to bin them. In DoWhy, the causal effect is defined wrt. the two values: treatment_value and control_value. For a continuous variable, you can set these values to get the effect of the variable with the desired change.
As for estimation, not all methods support continuous treatment. Among the in-house dowhy methods, the linear regression model does. Otherwise, you can use methods from econml, e.g., the double ml (dml) estimator.

Hi @amit-sharma , is it possible (or rather is there a list) of causal_estimators in fishy (and by extension, economy) that details which method is meant for binary or continuous treatment variables? Thank you!


Inline and block html not supported

Reproduction throws two exception.
# Throws:
#  - Could not process type: Markdig.Syntax.Inlines.HtmlInline
#   - Block type not supported: Markdig.Syntax.HtmlBlock
❯ "

>>

>> **Hello**,
>>
>> _world_.
>>

>>

" | md-cli

Spec

After #39 we now fallback to plain text.  For some reason we miss the final character.
AC:

Plain text to respect final character
Add support for type


[golang] location not calculated when curson on a commented

Language: golang
nvim version: NVIM v0.8.0-dev+1582-gc051ea83d
nvim-gps commit: 9552418fcbb9587025f4bd38364259b3888f582b

I couldn't identify the root cause of this, but when the cursor is on a comment the location is not being shown in the statusline. (I suppose something with the query):
https://user-images.githubusercontent.com/120483/166646250-0153642a-292d-41c0-a0ff-d65629364779.mov

Yep! I am aware of this issue, unfortunately this happens because treesitter does not treat comment nodes as child for the function node. Instead comment nodes kind of get their own tree, so when on a comment node we are unable to get info about the containing scope.
PS - I am currently working on a LSP based plugin to provide full breadcrumbs like functionality. It should be able to give context info like nvim-gps as well as let you jump around the file on functions, methods, variables, etc, etc. Using LSP will help be get rid of these inconsistencies of treesitter and another benefit is that I won't need to maintain anything for specific languages.
Will let you know when its ready to use :)


XP-241 add participant state machine

References
XP-241
Summary
Places the Participant state-machine back into FL repo. Cleans up tests and updates xain_fl/sdk legacy module.
Are there any open tasks/blockers for the ticket?
None

Reviewer checklist
Reviewer agreement:

Reviewers assign themselves at the start of the review.
Reviewers do not commit or merge the merge request.
Reviewers have to check and mark items in the checklist.

Merge request checklist

[x] Conforms to the merge request title naming XP-XXX <a description in imperative form>.
[x] Each commit conforms to the naming convention XP-XXX <a description in imperative form>.
[x] Linked the ticket in the merge request title or the references section.
[x] Added an informative merge request summary.

Code checklist

[x] Conforms to the branch naming XP-XXX-<a_small_stub>.
[ ] Passed scope checks.
[ ] Added or updated tests if needed.
[ ] Added or updated code documentation if needed.
[ ] Conforms to Google docstring style.
[ ] Conforms to XAIN structlog style.

outdated, closing


net/tcp(unbuffered): retransmit only one the earliest not acknowledged segment

Summary
As it turned out, the existing TCP unbuffered send implementation does a full rewind from the most recent sent segment back to the earliest not acknowledged one, thus many TCP segments are re-sent every time when TCP retrasmission timeout occurs.
According to RFC 6298 (5.4) only one the earliest not acknowledged segment should be retransmitted instead.
This PR implements TCP retrasmission according to RFC 6298 (5.4) ~if CONFIG_NET_TCP_SPLIT is disabled (this is by default).
If CONFIG_NET_TCP_SPLIT is enabled, TCP retrasmission works as before (full rewind). So far it is not clear how to adapt CONFIG_NET_TCP_SPLIT algorithm to conform to RFC 6298 (5.4).~ (CONFIG_NET_TCP_SPLIT is already removed by PR #4660).
Impact
TCP
Testing

btw, it has been on my todo list to remove CONFIG_NET_TCP_SPLIT. if it helps your work, please let me know. it isn't urgent and i don't want to interfere you by submitting conflicting patches.

Oh, really? I do not personally need CONFIG_NET_TCP_SPLIT algorithm. What about others? Is there any previous discussion about its deletion? I'm not sure, if there is a reason to preserve it? If I understand correctly, CONFIG_NET_TCP_SPLIT was developed for MCUs with tiny memories that do not have enough memory for a sufficient TCP retransmission queue depth.

it's just my personal todo. not community's.
while i can understand the motivation, it doesn't work well even with a traditional tcp stack.

i suspect this is something should be fixed with cwnd, which nuttx doesn't have right now.
doesn't the "buffered" version behave in a similar way? it basically moves segments on unacked_q back to write_q.

how do you think?

* i suspect this is something should be fixed with cwnd, which nuttx doesn't have right now.

* doesn't the "buffered" version behave in a similar way? it basically moves segments on unacked_q back to write_q.

how do you think?

I think it would be reasonable to implement congestion window control as an option. Also I see that Fast Retransmit algorithm is not supported in unbuffered tcp mode of NuttX that is possibly even more important.
Concerning "buffered" version I can not say at the moment as I have not yet analyzed the source code in that part.
So far I'm using "unbuffered" mode as in my case it surprisingly provides twice as higher throughput compared to "buffered" mode. Though, I expected that "buffered" mode should have better performance compared to "unbuffered" one.

btw, it has been on my todo list to remove CONFIG_NET_TCP_SPLIT. if it helps your work, please let me know. it isn't urgent and i don't want to interfere you by submitting conflicting patches.

Oh, really? I do not personally need CONFIG_NET_TCP_SPLIT algorithm. What about others? Is there any previous discussion about its deletion? I'm not sure, if there is a reason to preserve it? If I understand correctly, CONFIG_NET_TCP_SPLIT was developed for MCUs with tiny memories that do not have enough memory for a sufficient TCP retransmission queue depth.

it's just my personal todo. not community's. while i can understand the motivation, it doesn't work well even with a traditional tcp stack.

Can we poll NuttX developers about CONFIG_NET_TCP_SPLIT deletion? As I said, I personally do not need it. However, I'm afraid of if someone still needs CONFIG_NET_TCP_SPLIT?

it's a valid concern. i posted it on the ML<EMAIL_ADDRESS>
@yamt as PR #4660 is already merged into the master branch, I have adapted my patch to the removed NET_TCP_SPLIT option.

I forced-push to restart ci because "Build Documentation / build-html" previously failed.

i still think it's better to do it with cwnd-like structure. let me think a bit.

i still think it's better to do it with cwnd-like structure. let me think a bit.

By "cwnd" do you mean congestion window control algorithm or something else?

i still think it's better to do it with cwnd-like structure. let me think a bit.

By "cwnd" do you mean congestion window control algorithm or something else?

yes, congestion window.
clamping the window to one segment for retransmit is what this patch does, right?

i still think it's better to do it with cwnd-like structure. let me think a bit.

By "cwnd" do you mean congestion window control algorithm or something else?

yes, congestion window. clamping the window to one segment for retransmit is what this patch does, right?

You are saying about RFC 5681 (slow start of sending data etc.). My patch is not related to the congestion window control. My patch instead just fixes a basic requirement (RFC 6298 (5.4)) how a TCP segment should be retransmitted e.g. in case of ACK timeout. If it is detected that a segment is lost, only that particular segment should be retransmitted. However, currently NuttX TCP/IP stack (at least "unbuffered send" mode) retransmits all segments between NACK and SEQ provoking network traffic collapse.
The congestion window control is a separate advanced algorithm that I think could be implemented in NuttX TCP/IP stack as an option.

i still think it's better to do it with cwnd-like structure. let me think a bit.

By "cwnd" do you mean congestion window control algorithm or something else?

yes, congestion window. clamping the window to one segment for retransmit is what this patch does, right?

You are saying about RFC 5681 (slow start of sending data etc.). My patch is not related to the congestion window control. My patch instead just fixes a basic requirement (RFC 6298 (5.4)) how a TCP segment should be retransmitted e.g. in case of ACK timeout. If it is detected that a segment is lost, only that particular segment should be retransmitted. However, currently NuttX TCP/IP stack (at least "unbuffered send" mode) retransmits all segments between NACK and SEQ provoking network traffic collapse. The congestion window control is a separate advanced algorithm that I think could be implemented in NuttX TCP/IP stack as an option.

separate? maybe. but they can be implemented with the common machinary.
i will think a bit more, but because of holidays etc, i suspect it will take at least a few weeks.
i'm going to approve this for now.

separate? maybe. but they can be implemented with the common machinary.

Yes, the congestion window control code is of course expected to be tightly integrated into the existing NuttX code. I mean this is an extra algorithm that it would be reasonable to enable via menuconfig as an option. And this new potential code (congestion window control) could be activated by means of conditional compilation (#ifdef #endif) like e.g. CONFIG_NET_TCP_DELAYED_ACK, CONFIG_NET_TCP_WINDOW_SCALE and CONFIG_NET_TCP_FAST_RETRANSMIT_WATERMARK options, that just extend the basic NuttX TCP/IP functionality (optionally).

My patch (PR #4659) does not add a new functionality. It just fixes the existing basic retransmission part in NuttX TCP/IP stack ("unbuffered send" mode).

So, let's merge this PR first.


[CallWithChat] Switch from Beta to Public and Stable

What
Switch CallWithChat from Beta to Public and Stable
Why
https://skype.visualstudio.com/SPOOL/_workitems/edit/2770679/
How Tested
Test changes on local system on CallWithChat sample. Stable flavour

Can you please merge in https://github.com/Azure/communication-ui-library/pull/1605 and make that the new hook is also exported in stable.

I expected to see more UI test snapshots for CallWithChatComposite for stable build. Looks like we've disabled those tests in CI. Can you please also find all instances of this and add stable flavor (like the other e2e tests):

(This is from .github/workflows/ci.yaml)

I expected to see more UI test snapshots for CallWithChatComposite for stable build. Looks like we've disabled those tests in CI. Can you please also find all instances of this and add stable flavor (like the other e2e tests):

Also in update-snapshot.yml, remove this if:

Can you remove the beta flag in storybook also!

Let's merge this early today so we have a bit of a lead time rest of the week before we cut the stable release branch.
Thanks for taking care of this!


python: suppress warning on importing v1 module in init.py.

Problem
Whenever someone imports Python OL Client he gets deprecation warning on using v1 facets.
Solution
Suppress warning on import in __init__.py.
Checklist

[x] You've signed-off your work
[x] Your pull request title follows our guidelines
[ ] Your changes are accompanied by tests (if relevant)
[ ] Your change contains a small diff and is self-contained
[ ] You've updated any relevant documentation (if relevant)
[ ] Your comment includes a one-liner for the changelog about the specific purpose of the change (not required for changes to tests, docs, or CI config)
[ ] You've versioned the core OpenLineage model or facets according to SchemaVer (if relevant)
[ ] You've added a header to source files (if relevant)

SPDX-License-Identifier: Apache-2.0
Copyright 2018-2024 contributors to the OpenLineage project

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

Project coverage is 85.78%. Comparing base (ebefdc4) to head (f0c9e89).

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@            Coverage Diff             @@
##             main    #2713      +/-   ##
==========================================
+ Coverage   84.59%   85.78%   +1.19%
==========================================
  Files          59       23      -36
  Lines        3446     1520    -1926
==========================================
- Hits         2915     1304    -1611
+ Misses        531      216     -315

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


AccountID defined in the helper

I suggest changing the default flow input Id from accountId to recordID to make it a bit more generic :)
Awesome component. I was waiting for Winter 18 to use it 🥇

Good catch, residue from the earlier prototype testing =)


Add code generator

Adds simple code generator to generate code for const and var statements.

Sorry this PR was meant for my fork. I just played around a bit and the code is not really production ready.


Light mode symbol not visible when dark mode is on

Description
When the light mode is on  the dark mode symbol is visible

But when the dark mode is on the light mode symbol is not visible

Steps to Reproduce
Changing the icon symbol so that it is visible when both modes are on.
Please assign this issue to me under gssoc-ext, hacktoberfest and a suitable level label.
Expected Behavior
No response
Actual Behavior
No response
Screenshots
No response
Additional Information
No response
What browser are you seeing the problem on?

[x] Firefox
[x] Chrome
[ ] Safari
[X] Microsoft Edge

Checklist

[X] I have checked the existing issues
[X] I have read the Contributing Guidelines
[X] I want to work on this issue. (optional)

already someone is working on this


Python 3.8-dev image

Would it be possible to get an image for Python 3.8-dev :slightly_smiling_face: ?

Unfortunately, we're not well-equipped to do builds of 3.8-dev here, but the 3.8.0a1 release is definitely something doable: https://github.com/docker-library/python/pull/383 :+1:

This is great, thank you!


Is this repo actively maintained

Just a friendly question from the Package Maintenance Team. Is this repo active?

We would also like to know if this repo is actively maintained ?

Not so far.

https://www.npmjs.com/package/node-rdkafka
Or
https://kafka.js.org/
Are alternatives .
See this discussion
https://github.com/nodeshift/nodejs-reference-architecture/issues/25

I would move on and consider this module as Unmaintained

Exactly what we are thinking of doing, already implemented PoC solution using https://kafka.js.org/, also it is sponsored by Confluent Cloud Kafka SaaS provider, so it's unlikely for it to become unmaintained anytime soon.

Our team stopped using this module a few years ago so I no longer have opportunities to work on it during company hours.


Treemap is showing blank white screen with console error

Team,
Treemap is not showing after upgrade the shidoka charts package (1.3.0) with console error. Kindly take a look.

Note: Storybook is also having same issue.

:tada: This issue has been resolved in version 1.4.1 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Questions about training data preprocessing

Hi!
I noticed that "attention_mask" was ignored when preprocessing the training data, as shown in the code of the file src/tevatron/data.py.
class TrainDataset(Dataset):
    def create_one_example(self, text_encoding: List[int], is_query=False):
        item = self.tok.prepare_for_model(
            text_encoding,
            truncation='only_first',
            max_length=self.data_args.q_max_len if is_query else self.data_args.p_max_len,
            padding=False,
            return_attention_mask=False,
            return_token_type_ids=False,
        )
        return item

And I found that some other sources of work on dense retrieval didn't do this. So I want to ask what is the reason for designing the code like this.
Thanks for your answer:)

I just found that the QPCollator will add "attention_mask" to it.


Specify required Ruby version

Please remove the last commit and I will merge the PR.

Done !

Thank you for the contribution.


rake: init at 11.1.1

Add package "rake", which is a ruby-based build tool.
Obviously, no other packages depend on rake, so the addition should not break anything.
Things done:

[ ] Tested using sandboxing (nix-build --option build-use-chroot true or nix.useChroot on NixOS)
Built on platform(s)

[X] NixOS
[ ] OS X
[ ] Linux

[X] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip" (... no dependencies)
[X] Tested execution of all binary files (usually in ./result/bin/) (... no binary files)
[X] Fits CONTRIBUTING.md.

The desired commit subject format for new packages is pkgname: init at version.

Thanks for your feedback, @joachifm. I made the requested changes.
By the way, the Ruby example in the nixpkgs manual contains a trailing dot in its description.
This may confuse newcomers such as me.

I fixed the usage example. Thanks.

Err, I didn't notice this was against release 15.09 ...

@joachifm sorry if pull request was against wrong branch. I am still not quite sure which branch is best, staging or master perhaps? Will the package be available in the "15.09 channel" if it is merged into master or staging?

master is the preferred branch. staging is for non-breaking changes that cause large rebuilds, it exists mainly to let the build farm "catch up" and so minmize disruption for people running the unstable version.
A change like this wouldn't ordinarily be integrated into a release branch, they typically only see bug and security fixes once the release has been finalized. If there is a specific reason you think it should be integrated into a release branch, there's no harm in requesting it, of course.
Please re-open the PR against master.

@joachifm Thank you for the good explanation. :-) As suggested, I will re-open the PR against master.


sometimes csv output

it seems some of the services that return a simple list are amenable to also outputing a csv.  can we consider adding this?
for example:
http://localhost:8080/scigraph/dynamic/genes/NCBIGene:14183/genotypes/targets.json
we get a blob back with an array of nodes like:
nodes": [{
"id": "MGI:3766095",
"lbl": "Fgfr2<tm2.1Lni>/Fgfr2<tm2.1Lni>[involves: 129S1/Sv * 129X1/SvJ * C57BL/6]",
"meta": {
"category":
["intrinsic genotype"]}}, ...]
this seems like it could easily be flattened into a csv of:
id | lbl | meta  OR
id | lbl | category
seems like some folks might just want the csv without having to deal with parsing the json.

Is the general feature request here to just return a CSV of nodes in a subgraph?


Problem with config.json

Hi!
I am very happy about the new naming system, I wanted to try it but I had a problem with the config.json file.
I created with the notepad a file "config.json", I copied inside the example you show in the description without modifying it at all.
But when I launch aspiratv (with "aspiratv --config config.json") I get an error message: "[FATAL] [Initialize] Can't decode configuration file: invalid character '}' looking for beginning of object key string"
Do you have an idea of the problem?
Thanks!

Sure, the json file is  invalid. Could share it?

I just copied your example in an empty file.
Here is the json file : https://we.tl/t-CMm9TNxSeM
In the future, maybe you could add an example of the json file directly in the download package, to help users?

Well, the one form the documentation :-(
I'm Checking.

Hi!
Now it works :), thank you very much!
Have a nice day and thank you again to have made this software :)


Decrypt9 RedNAND Issues

Decrypt9 can have issues with several RedNAND related functions, an update will be out soon.

The temporary workaround for this problem is to use EmuNAND9 to backup redNAND, backup SD card, format SD for GW EmuNAND, and restore redNAND backup to emuNAND, then complete all instructions using EmuNAND where the guide says RedNAND.

I'm running into an issue with the workaround where it tells me that there isn't enough space for GW type EmuNAND.  I'm using a fresh 64gb SD card, so space shouldn't be a problem. Any ideas on what's wrong?

Same thing is happening to me with the work around.

I'm having the same issue with the work around. Not enough space for GW type emunand when trying to convert rednand to emunand. I'm now stuck at step 11 of this guide https://github.com/Plailect/Guide/wiki/Part-4-(Getting-the-OTP)
Any help? Really looking forward to tinkering with a9lh

dude i tried the latest testing release of decrypt9 but im still getting the same problem pls do something fast!

Just checking that this is the same problem as not seeing "redNAND Options" in the menu screen.

This should fix any RedNAND related Decrypt9 issues.

This has fixed my issue where "No EmuNAND" was displaying at the bottom. The menu item still relates to "EmuNAND Options" but proceeding allows me to use RedNAND and dump H&S.
Good work on the hotfix

D0k3 takes credit for this
On Wed, Mar 30, 2016, 11:36 AM Lachlan du Preez<EMAIL_ADDRESS>wrote:

This has fixed my issue where "No EmuNAND" was displaying at the bottom.
The menu item still relates to "EmuNAND Options" but proceeding allows me
to use RedNAND and dump H&S.
Good work on the hotfix
—
You are receiving this because you modified the open/close state.
Reply to this email directly or view it on GitHub
https://github.com/Plailect/Guide/issues/36#issuecomment-203492335

What should fix all the issues related to rednand and decrypt9?

Glad I found this issue. Just want to confirm some stuff so I don't brick or something.
I'm on Part 4, Section I, Step 11.
When I access Decrypt9 when on sysNAND, I get no redNAND Options in the main menu. Are emuNAND Options the same thing as redNAND Options?

Yes

I'm running into an issue on Part 4, Section IV, Step 5.
5.Restore RedNAND from RedNAND_original.bin
It doesn't look like the version of OTP that opened can restore for RedNAND.  Any ideas on how to fix this?

And we're back to EmuNAND until the bugs are sorted. Closing this issue.

Restore SysNAND then restore RedNAND using OTPHelper
On Wed, Mar 30, 2016, 10:07 PM bctaucsd<EMAIL_ADDRESS>wrote:

I'm running into an issue on Part 4, Section IV, Step 5.
5.Restore RedNAND from RedNAND_original.bin
It doesn't look like the version of OTP that opened can restore for
RedNAND. Any ideas on how to fix this?
—
You are receiving this because you modified the open/close state.
Reply to this email directly or view it on GitHub
https://github.com/Plailect/Guide/issues/36#issuecomment-203716068

Decrypt9WIP just had a new version released today that fixes the redNAND issues, so we should be good to go back to using redNAND for the guide.


Using the loader in a lib causes You've loaded two copies of React on the page.

When I use svg-react-loader in a library which I pack with webpack, the user using this package gets:

Warning: React can't find the root component node for data-reactid value .<IP_ADDRESS>.<IP_ADDRESS>.<IP_ADDRESS>.<IP_ADDRESS>. If you're seeing this message, it probably means that you've loaded two copies of React on the page. At this time, only a single copy of React can be loaded at a time.

If I remove the SVG components, it works fine.
I import them like this:
  Pic = require('babel!svg-react!./assets/pic.svg?name=Pic')

Using them within a project (not via a lib) works fine.

Can you describe what you mean by a "lib"?
If you mean something similar to an npm package, with its own dependencies, I can see how that could cause a problem. Is this library also depending on React?

yes.
I resolved by declaring react as an external in webpack. :)


Use .link files to deliver overlay

This depends on PYNQ supporting .link files with multiple files in a container such as .zip files. The issue is open here
https://github.com/Xilinx/PYNQ-Dev/issues/307

Pending resolution on this PR https://github.com/Xilinx/PYNQ/pull/1349
If this PR goes ahead, the way the composable overlay is zipped should change not to use root folder. E.g. zip -j
https://unix.stackexchange.com/a/299596

Depends on https://github.com/Xilinx/PYNQ/pull/1349
If this PR goes ahead, the way the composable overlay is zipped should change not to use root folder. E.g. zip -j
https://unix.stackexchange.com/a/299596


beforeinstallprompt doesnt get fired in +layout.svelte

Discussed in https://github.com/sveltejs/kit/discussions/11550

Originally posted by rheanV January  9, 2024
I have an installable PWA (for sveltekit app). I want to add a custom button for installing the app. I placed my window.addEventListener('beforeinstallprompt', (event) => {     event.preventDefault();    //logic   });  in the onMount of the +layout.svelte file. I have all other configurations correct, meets all installation criteria, and can be installed via the browser download option in the URL bar. However, my "beforeinstallprompt" does not get fired in the +layout.svelte. If I place it in app.html then it is fired but not in +layout.svelte. How should I fix this? What am I missing in my sveltekit app setup?

Same issue here - no clue if the use of this event in app.html can be a workaround? Please help

Closing this as it now works if you add it to the <svelte:window> tag. For example:
<svelte:window
  onbeforeinstallprompt={() => {
    console.log("beforeinstallprompt");
  }}
/>

This works very intermittently when adding the event listener to <svelte:window>
<svelte:window
  onbeforeinstallprompt={() => {
    console.log("beforeinstallprompt");
  }}
/>


Is there a reason for not using a proprietary documentation generator?

Title basically explains. Currently, the preject uses its own documentation generator built with Next.js, but there is a reason for not using a generator like Nextra, Docussaurus or Mintlify? Based on the project's development stage, it's way more suitable to use already battle-tested tools to build this parts that are not inherently related to the main project.
I was looking forward to contribute writing the documentations, but during the readings to spot some field to improve, I found that there are a bunch of things, specially Accessibility related like Line heights, ARIA attributes, layout shifts happening on the website.
It woundn't make more sense to use one of these previously mentioned tools to simplify the documenting process, leaving more time to spend on the main library development?

Hi @guilherssousa , I needed something that was in Next.js, at the time Nextra was having a lot of problems and didn't work properly (v1), I looked for other alternatives that would handle Next.js well, but as I wasn't finding it and I didn't want to waste more time looking or hoping for corrections so I decided to make by myself and that fit well with the main page design. Today, maybe it makes sense to change, but it's something I'll need to test and see how it will look in relation to the static and existing site in Next.js, but at the moment I don't have the time to execute this.

Can I work on this?

@guilherssousa sure! 💜

Just to make sure: Nextra is not too opinionated about styling, and since its internal styling is very is very similar to Tailwind, it makes sense to adopt it too. Any thoughts about it?

@guilherssousa currently the interprocess website and docs uses stitches.
You can go with stitches or use tailwind if you prefer to make this migration.

Here are some updates on the migration:
I used a new blank Next.js project with Nextra docs and migrating the contents was seamless. These are the things I changed:

Tailwind instead of Stitches to be able to easily style directly from MDX if necessary
New texts and design for feature section on home matching Nextra
New Homepage headline (more engaging, but needs validation)

No worries at this point but there's still work to do, here are the missing points:

[ ] Fancy code editor on Home with Typewriting effect and Intellisense
[ ] A fancier background like the previous one (or something like the defaults from Mintlify?)
[ ] Redo buttons and installing command section to clipboard

You can check progress here (documentation links won't work because of base URLs since project is being hosted on Vercel instead of GH Pages):

A scalable and type-safe Electron IPC management tool with enhanced DX - Interprocess
Overview - Interprocess

Hi @guilherssousa , sorry for the delay. The texts and visual elements must be the same and without changing their appearance. I understand that within the documentation itself some adaptations need to be made, but the visual essence of the main page must be maintained for all pages.

Also, the final version must be able to be hosted as static site on GitHub as the current version.


www/nginx: Allow custom listen parameters

Currently I can add custom listen parameters after the port.
That's totally fine but seems undocumented and therefore might even be unintended.
I would like to ensure that this functionality is being kept or otherwise better implemented in the UI.
In particular, this feature is very useful to define a single HTTP server instance for "default_server".

How do you get this into the config? The Port settings should not support this.

BTW: they may prevent the proxy from starting because some settings can only defined once (for example running IPv6 with IPv4 in the same listen directive)

This issue has been automatically timed-out (after 180 days of inactivity).
For more information about the policies for this repository,
please read https://github.com/opnsense/plugins/blob/master/CONTRIBUTING.md for further details.
If someone wants to step up and work on this issue,
just let us know, so we can reopen the issue and assign an owner to it.

This still sounds useful to me


problem_pattern_hacktoberfest

Please add the time complexity and space complexity for your code.

Please open another pull request with the required changes.


adding new lab on word2vec only in solutions folder

Adding a notebook on building word2vec model (ski-gram) as needed by the NLP offering. The objective of this notebook will be to teach students how to build word2vec models from scratch and analyze/visualize the embeddings they get from the model.
Note: The notebook has been only added to the solutions folder. Once integrate review comments, I will create a lab notebook version.

Nice lab! LGTM except for a few minor points.


Undescribable file transfer bug.

Describe the Bug
I really don't know how to explain this, but it has to do with file transfers with video editors and them holding them file, then trying to drag files to a folder, and it just says it cant copy because the file is being held by premiere/kdenlive or whatever software.
https://github.com/user-attachments/assets/33900e92-cf7e-4877-a963-4e3be8b2d68f
To Reproduce

Open premiere or a video editor
drag in a file from a vpk
drag ANOTHER file from a vpk
File cant move because its being held by premiere
Drag file to a folder instead of the editor
More file errors

Operating System
Windows 10

Will look into this, hopefully Hitfilm has the same bug because I don't own Adobe products

Ok I think I know why this is happening. When file(s) are dragged out of the application, it's expecting the OS will move them to wherever they're being dragged to. When this doesn't happen, they stay in the temp folder. At EntryTree.cpp L452, files are added to the drag based on the contents of the temp dir, files that are already in the temp dir are included in the drag because of this. I wrote it this way because I expected the temp dir to always be empty at this point. When it adds the existing files in the temp dir to the drag, this conflicts with Premiere because Premiere copied the previously dragged file to the project folder already (not moved, copied, thanks Adobe) and that file is open in Premiere. I have a bit of code to delete the contents of the temp dir after the drag is complete just in case the OS doesn't like moving stuff, but it seems like that's not working.
So I think the easiest fix here is making a different temp dir in %localappdata%/Temp (or /tmp on the better OS) for each drag operation. Files not getting deleted from the temp dir when they're dragged on top of an application like Premiere is bleh but there's nothing I can do about that, and really I blame Windows for not deleting files in Temp on startup :trollface:

Thanks for the report btw


When entering amounts "Done" button should appear (sample banking app attached for inspiration)

checked

@DenisDemyanko can you make "Done" in bold please?

checked


STContains vs. STWithin vs. STIntersects?

It would be nice if the documentation explicitly addressed why there are multiple ostensibly similar functions.  Since STIntersects' existence presumably rules out partial vs. strict subset, I can't think of any other English-based meaning difference between STWithin and STContains.

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

ID: 5be221aa-48df-e9ab-fc2d-65d4f7ec56ce
Version Independent ID: b81cfb49-c58a-97bd-5e85-224e567a633e
Content: STContains  (geography Data Type) - SQL Server
Content Source: docs/t-sql/spatial-geography/stcontains-geography-data-type.md
Product: sql
Technology: t-sql
GitHub Login: @douglaslMS
Microsoft Alias: douglasl

Thank you @eliotg - again - I'll find the answer.

Still monitoring.

Here's the answer that I got back:)

Functions starting with ST are OGC standardized function calls that can be found in other implementations of OGC spec as well in similar forms (e.g. ST_Within, ST_Contains, in PostgreSQL, Oracle, etc)
Also, I don’t see any language ambiguity when saying if A CONTAINS B, then B is WITHIN A, i.e.
a.STWithin(b) == b.STContains(a)


Re-binding does not copy updates made to original deployment

(As I stated in a previous issue, I expect kubehost to not to create a new deployment OR continuously mirror changes I make to my original deployment.)
Problem
I had a deployment/service that was kubehost bind'ed before.
I scaled it up with kubectl scale deployment/hello-server --replicas=3 from 1 replica.
I didn't expect hello-server-hostport deployment to be updated automatically (because I already figured out kubehost is an imperative tool).
What was unexpected is when I run kubectl bind hello-server again, I expected hello-server-hostport deployment to be "cloned" again and have its replcias updated to 3. This didn't happen.
$ kubectl get deployments

NAME                    DESIRED   CURRENT   UP-TO-DATE   AVAILABLE   AGE
hello-server            3         3         3            3           17m
hello-server-hostport   1         1         1            1           17m

I suppose I understood this wrong.
-hostport deployment isn't a clone of my deployment. It's just a gcr.io/google_containers/proxy-to-service.


Hotkey to return home from inside of a webview

No method currently exists that works when a webview has focus.
Current methods are

Hover border and press escape
Click border
Click home icon in top left of border

Added in upcoming 1.0.7 release.


Fix-2.0Show load npe(userinfo is null) (#27698)

(cherry picked from commit c6f43e42416b536304eeeecf863438fe50b01000)
Proposed changes
Issue Number: close #xxx

Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

run buildall

#27698


Mobile UI can be Scrolled horizontally

Describe the bug
UI can be Scrolled to the right because the search bar is too long
Profile/Location
any
Additional Info
If applicable, what pet/weapon/armor you are using and where you are in Skyblock.
Expected behavior
With an old screenshot that I found in the files it has the search done correctly and you cannot scroll across

Screenshots

Smartphone (please complete the following information):

Device: Google pixel 5
OS: Android 13
Browser: Tested with brave and stock chrome
Version: Brave - 1.51.118 Chrome 113.0.5672.162

Additional context

#1405 Dupe

Closed due to due


Cannot send because of transactionSerializationError

Sender, receiver and password are all set correctly. However I get this error from the print(res) line:
Optional(.failure(transactionSerializationError))
Am I doing something wrong?
My code looks like this:
var eks = [EthereumKeystoreV3]()
eks.append(ekv3!)
var ks = KeystoreManager.init(eks)
var sender = keyStore?.addresses?.first

var options = Web3Options()
options.gasPrice = BigUInt(120000)
options.value = BigUInt(amount.data(using: .utf8)!)
options.from = sender
options.to = EthereumAddress(target)
options.gasLimit = BigUInt(120000)

let contract = client.contract(abi, at: EthereumAddress(target))
let intermediateSend = contract?.method(options: options)

let res = try intermediateSend?.send(password: "password")

print(res as Any)

let derivedSender = intermediateSend?.transaction.sender
let txid = try res?.dematerialize()["txhash"]
print(txid as Any)

I managed to get rid of the transactionSerializationError by adding a password to the keystore manager. However now I get a different error:
Optional(.failure(unknownError))
Debugging the intermediate.send() method I noticed that the above error comes from sendRawTransaction().
This is my new Code:
public static func sendCoins()
{
    let from = EthereumAddress("some1")
    let to = EthereumAddress("some2")

    let client = getClient() //connection to ethereum based crypto currency
    let keyStore = getKeyFile(privKey: "privkey", password: "passwd") // instead of the 3 commented lines below
    //let web3 = Web3.InfuraMainnetWeb3()
    //let tempKeystore = try! EthereumKeystoreV3(privateKey: DataFromPrivateKeyWithLen32bytes, password: "passwd")
    //let keystoreManager = KeystoreManager([tempKeystore!])

    client.addKeystoreManager(keyStore)
    let contract = client.contract(Web3.Utils.erc20ABI, at: to, abiVersion: 2)

    var options = Web3Options.defaultOptions()
    options.value = Web3.Utils.parseToBigUInt("0.001", units: .eth)
    options.gasPrice = Web3.Utils.parseToBigUInt("60", units: .Gwei)
    options.gasLimit = Web3.Utils.parseToBigUInt("60", units: .Gwei)
    options.from = from
    options.to = to

    let intermediate = contract?.method("fallback", options: options)
    let result = intermediate?.send(password: "passwd")

    print("Result is: ")
    print(result as Any)
}

Do you want to send tokens or ETH?

I want to send ETH.

Thank you should literally follow my example, just use your keystore instead

Also related to #43, was fixed in #44 and #45 in case you do not use a keystore, but send an unsigned transaction to external node

we solved the problem by using your reference code. thanks for you help!


Overwrite previous benchmarks?

https://github.com/henry2004y/TestParticle.jl/blob/6236aa752a73092366aaf69e98d2651cd1fd62ea/.github/workflows/benchmark.yml#L27-L32
The current benchmark bot writes a new report for every new push. Can we do something similar to the codecov bot which overwrite the previous report @TCLiuu?

Okay, I will try to resolve this issue when I have free time.
Say something off-topic, due to limitations in energy and some trivial matters in life, I haven't been able to contribute further improvements to this project in the past year. This is very regrettable because I am very interested in what this project aims to achieve. I will take responsibility for the parts that I have completed, so please feel free to contact me if there are any issues. I will find time to resolve them. The issues and features that I have proposed, hopefully one day I will be able to solve or achieve them.

Closed via #206


icon size can not be random , be sure to press you to request it

icon size can not be random , be sure to press you to request it

?

Icon size has to be 24dp. Here's how I did it.
final float scale = mActivity.getResources().getDisplayMetrics().density; final int bottomNavPixels = (int) (24 * scale + 0.5f); Drawable dr = new BitmapDrawable(getResources(), Bitmap.createScaledBitmap(bitmap, bottomNavPixels, bottomNavPixels, true));
Now use the drawable in mBottombar.setItems(new BottomBarTab(dr, "Title"));

It works for me! Thanks!!


Maintain a .astro-registry.yaml file

As part ensuring that the SDK page in the Registry is up to date, it would be awesome to have a .astro-registry.yaml file. This is similar to the .provider.yaml file found in OSS providers. This file would make it a ton easier to parse the SDK and ensure all necessary information makes its way into the database (and ultimately, the front end of the Registry).
As of today, this file would look like:
# This file is intended to be a file which specifically calls out modules to be published to the Astronomer
# Registry. The file should not be packaged and solely lives in the repo. The modules listed should pertain
# to latest released version of the repo.

# Python package name (if it's not the name of the repo itself).
package-name: astro-sdk-python
# The name of the provider to be displayed on the Registry.
display-name: Astro SDK
# A description to be displayed on the main Provider page.
description: Astro SDK allows rapid and clean development of {Extract, Load, Transform} workflows using Python and SQL, powered by Apache Airflow.

# The next sections should be organized by module type (e.g. operators, hooks, functions, decorators, etc.).
#
# Within each section, the ``module`` value should be the path.to.the.module.specifically.
# For example, if the import path for a function is `from astro.sql.operators.append import append` then the
# value should be "astro.sql.operators.append.append".
#
# There is an option to include an override for the import path that is displayed on the Registry wrt to the
# Module page itself: ``display_path``. This would be the import path Access Instructions
# (see https://registry.astronomer.io/providers/astro-sdk/modules/append).

# These would be the Functions to be displayed on the Registry.
# (akin to https://registry.astronomer.io/modules?providers=Astro+Sdk&page=1&types=Functions)
functions:
  - module: astro.sql.operators.append.append
    display-path: astro.sql.append
  - module: astro.sql.operators.cleanup.cleanup
    display-path: astro.sql.cleanup
  - module: astro.sql.operators.drop.drop_table
    display-path: astro.sql.drop_table
  - module: astro.sql.operators.export_file.export_file
    display-path: astro.sql.export_file
  - module: astro.sql.operators.load_file.load_file
    display-path: astro.sql.load_file
  - module: astro.sql.operators.merge.merge
    display-path: astro.sql.merge
  - module: astro.sql.operators.transform.transform_file
    display-path: astro.sql.transform_file

# These are the Decorators to be displayed on the Registry.
# (akin to https://registry.astronomer.io/modules?providers=Astro+Sdk&page=1&types=Decorators)
decorators:
  - module: astro.sql.operators.dataframe.dataframe
    display-path: astro.sql.dataframe
  - module: astro.sql.operators.raw_sql.run_raw_sql
    display-path: astro.sql.run_raw_sql
  - module: astro.sql.operators.transform.transform
    display-path: astro.sql.transform

Awesome will take care of it @virajmparekh

@sunank200 to connect with @kaxil to understand more details about this ticket

@kaxil How about moving this to 1.3.0 ?

Yup


DatabaseUpgradeChecker: add upgrade path from <IP_ADDRESS> to <IP_ADDRESS>

This needs checking if it's even needed at all cc @shwstppr @DaanHoogland
Description
This PR...

Types of changes

[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] New feature (non-breaking change which adds functionality)
[ ] Bug fix (non-breaking change which fixes an issue)
[ ] Enhancement (improves an existing feature and functionality)
[ ] Cleanup (Code refactoring and cleanup, that may add test cases)

Feature/Enhancement Scale or Bug Severity
Feature/Enhancement Scale

[ ] Major
[ ] Minor

Bug Severity

[ ] BLOCKER
[ ] Critical
[ ] Major
[ ] Minor
[ ] Trivial

Screenshots (if appropriate):
How Has This Been Tested?

Let's merge this @shwstppr @DaanHoogland based on testing and only if you confirm this fixes upgrade from <IP_ADDRESS>

Did another test. LGTM
2022-09-23 11:40:25,877 INFO  [c.c.u.DatabaseUpgradeChecker] (main:null) (logid:) Grabbing lock to check for database upgrade.
2022-09-23 11:40:25,898 DEBUG [c.c.u.d.VersionDaoImpl] (main:null) (logid:) Checking to see if the database is at a version before it was the version table is created
2022-09-23 11:40:25,920 DEBUG [c.c.u.SystemVmTemplateRegistration] (main:null) (logid:) Looking for file [ ./engine/schema/dist/systemvm-templates/metadata.ini ] in the classpath.
2022-09-23 11:40:25,920 DEBUG [c.c.u.SystemVmTemplateRegistration] (main:null) (logid:) Looking for file [ /usr/share/cloudstack-management/templates/systemvm/metadata.ini ] in the classpath.
2022-09-23 11:40:25,967 INFO  [c.c.u.DatabaseUpgradeChecker] (main:null) (logid:) DB version = <IP_ADDRESS> Code Version = <IP_ADDRESS>
2022-09-23 11:40:25,968 INFO  [c.c.u.DatabaseUpgradeChecker] (main:null) (logid:) Database upgrade must be performed from <IP_ADDRESS> to <IP_ADDRESS>
2022-09-23 11:40:25,982 DEBUG [c.c.u.DatabaseUpgradeChecker] (main:null) (logid:) Running upgrade Upgrade41700to41710 to upgrade from <IP_ADDRESS>-<IP_ADDRESS> to <IP_ADDRESS>
2022-09-23 11:40:25,984 DEBUG [c.c.u.d.ScriptRunner] (main:null) (logid:) -- Licensed to the Apache Software Foundation (ASF) under one
2022-09-23 11:40:25,984 DEBUG [c.c.u.d.ScriptRunner] (main:null) (logid:) -- or more contributor license agreements.  See the NOTICE file
2022-09-23 11:40:25,984 DEBUG [c.c.u.d.ScriptRunner] (main:null) (logid:) -- distributed with this work for additional information
2022-09-23 11:40:25,984 DEBUG [c.c.u.d.ScriptRunner] (main:null) (logid:) -- regarding copyright ownership.  The ASF licenses this file
2022-09-23 11:40:25,984 DEBUG [c.c.u.d.ScriptRunner] (main:null) (logid:) -- to you under the Apache License, Version 2.0 (the
2022-09-23 11:40:25,984 DEBUG [c.c.u.d.ScriptRunner] (main:null) (logid:) -- "License"); you may not use this file except in compliance
2022-09-23 11:40:25,984 DEBUG [c.c.u.d.ScriptRunner] (main:null) (logid:) -- with the License.  You may obtain a copy of the License at
2022-09-23 11:40:25,984 DEBUG [c.c.u.d.ScriptRunner] (main:null) (logid:) --
2022-09-23 11:40:25,984 DEBUG [c.c.u.d.ScriptRunner] (main:null) (logid:) --   http://www.apache.org/licenses/LICENSE-2.0
2022-09-23 11:40:25,984 DEBUG [c.c.u.d.ScriptRunner] (main:null) (logid:) --
2022-09-23 11:40:25,984 DEBUG [c.c.u.d.ScriptRunner] (main:null) (logid:) -- Unless required by applicable law or agreed to in writing,
2022-09-23 11:40:25,984 DEBUG [c.c.u.d.ScriptRunner] (main:null) (logid:) -- software distributed under the License is distributed on an
2022-09-23 11:40:25,984 DEBUG [c.c.u.d.ScriptRunner] (main:null) (logid:) -- "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
2022-09-23 11:40:25,984 DEBUG [c.c.u.d.ScriptRunner] (main:null) (logid:) -- KIND, either express or implied.  See the License for the
2022-09-23 11:40:25,984 DEBUG [c.c.u.d.ScriptRunner] (main:null) (logid:) -- specific language governing permissions and limitations
2022-09-23 11:40:25,984 DEBUG [c.c.u.d.ScriptRunner] (main:null) (logid:) -- under the License.
2022-09-23 11:40:25,984 DEBUG [c.c.u.d.ScriptRunner] (main:null) (logid:) --;
2022-09-23 11:40:25,984 DEBUG [c.c.u.d.ScriptRunner] (main:null) (logid:) -- Schema upgrade from <IP_ADDRESS> to <IP_ADDRESS>
2022-09-23 11:40:25,984 DEBUG [c.c.u.d.ScriptRunner] (main:null) (logid:) --;
2022-09-23 11:40:25,985 DEBUG [c.c.u.d.ScriptRunner] (main:null) (logid:) UPDATE `cloud`.`configuration` SET `value` = 'false' WHERE `name` = 'network.disable.rpfilter' AND `value` != 'true'
2022-09-23 11:40:25,985 DEBUG [c.c.u.d.ScriptRunner] (main:null) (logid:) UPDATE `cloud`.`configuration` SET `value` = 'false' WHERE `name` = 'consoleproxy.disable.rpfilter' AND `value` != 'true'
2022-09-23 11:40:25,985 DEBUG [c.c.u.d.ScriptRunner] (main:null) (logid:) -- Retrieve the hypervisor_type from vm_instance
2022-09-23 11:40:25,985 DEBUG [c.c.u.d.ScriptRunner] (main:null) (logid:) DROP VIEW IF EXISTS `cloud`.`domain_router_view`
2022-09-23 11:40:26,001 DEBUG [c.c.u.d.ScriptRunner] (main:null) (logid:) CREATE VIEW `cloud`.`domain_router_view` AS     select         vm_instance.id id,         vm_instance.name name,         account.id account_id,         account.uuid account_uuid,         account.account_name account_name,         account.type account_type,         domain.id domain_id,         domain.uuid domain_uuid,         domain.name domain_name,         domain.path domain_path,         projects.id project_id,         projects.uuid project_uuid,         projects.name project_name,         vm_instance.uuid uuid,         vm_instance.created created,         vm_instance.state state,         vm_instance.removed removed,         vm_instance.pod_id pod_id,         vm_instance.instance_name instance_name,         vm_instance.hypervisor_type,         host_pod_ref.uuid pod_uuid,         data_center.id data_center_id,         data_center.uuid data_center_uuid,         data_center.name data_center_name,         data_center.networktype data_center_type,         data_center.dns1 dns1,         data_center.dns2 dns2,         data_center.ip6_dns1 ip6_dns1,         data_center.ip6_dns2 ip6_dns2,         host.id host_id,         host.uuid host_uuid,         host.name host_name,         host.cluster_id cluster_id,         vm_template.id template_id,         vm_template.uuid template_uuid,         service_offering.id service_offering_id,         service_offering.uuid service_offering_uuid,         service_offering.name service_offering_name,         nics.id nic_id,         nics.uuid nic_uuid,         nics.network_id network_id,         nics.ip4_address ip_address,         nics.ip6_address ip6_address,         nics.ip6_gateway ip6_gateway,         nics.ip6_cidr ip6_cidr,         nics.default_nic is_default_nic,         nics.gateway gateway,         nics.netmask netmask,         nics.mac_address mac_address,         nics.broadcast_uri broadcast_uri,         nics.isolation_uri isolation_uri,         vpc.id vpc_id,         vpc.uuid vpc_uuid,         vpc.name vpc_name,         networks.uuid network_uuid,         networks.name network_name,         networks.network_domain network_domain,         networks.traffic_type traffic_type,         networks.guest_type guest_type,         async_job.id job_id,         async_job.uuid job_uuid,         async_job.job_status job_status,         async_job.account_id job_account_id,         domain_router.template_version template_version,         domain_router.scripts_version scripts_version,         domain_router.is_redundant_router is_redundant_router,         domain_router.redundant_state redundant_state,         domain_router.stop_pending stop_pending,         domain_router.role role,         domain_router.software_version software_version     from         `cloud`.`domain_router`             inner join         `cloud`.`vm_instance` ON vm_instance.id = domain_router.id             inner join         `cloud`.`account` ON vm_instance.account_id = account.id             inner join         `cloud`.`domain` ON vm_instance.domain_id = domain.id             left join         `cloud`.`host_pod_ref` ON vm_instance.pod_id = host_pod_ref.id             left join         `cloud`.`projects` ON projects.project_account_id = account.id             left join         `cloud`.`data_center` ON vm_instance.data_center_id = data_center.id             left join         `cloud`.`host` ON vm_instance.host_id = host.id             left join         `cloud`.`vm_template` ON vm_instance.vm_template_id = vm_template.id             left join         `cloud`.`service_offering` ON vm_instance.service_offering_id = service_offering.id             left join         `cloud`.`nics` ON vm_instance.id = nics.instance_id and nics.removed is null             left join         `cloud`.`networks` ON nics.network_id = networks.id             left join         `cloud`.`vpc` ON domain_router.vpc_id = vpc.id and vpc.removed is null             left join         `cloud`.`async_job` ON async_job.instance_id = vm_instance.id             and async_job.instance_type = 'DomainRouter'             and async_job.job_status = 0
2022-09-23 11:40:26,004 DEBUG [c.c.u.d.ScriptRunner] (main:null) (logid:) -- PR #6080 Change column `value` size from 255 to 4096 characters, matching the API "updateConfiguration" "value" size
2022-09-23 11:40:26,004 DEBUG [c.c.u.d.ScriptRunner] (main:null) (logid:) ALTER TABLE `cloud`.`account_details` MODIFY `value` VARCHAR(4096) NOT NULL
2022-09-23 11:40:26,054 INFO  [c.c.u.DatabaseUpgradeChecker] (main:null) (logid:) Cleanup upgrade Upgrade41700to41710 to upgrade from <IP_ADDRESS>-<IP_ADDRESS> to <IP_ADDRESS>
2022-09-23 11:40:26,056 DEBUG [c.c.u.d.ScriptRunner] (main:null) (logid:) -- Licensed to the Apache Software Foundation (ASF) under one
2022-09-23 11:40:26,056 DEBUG [c.c.u.d.ScriptRunner] (main:null) (logid:) -- or more contributor license agreements.  See the NOTICE file
2022-09-23 11:40:26,056 DEBUG [c.c.u.d.ScriptRunner] (main:null) (logid:) -- distributed with this work for additional information
2022-09-23 11:40:26,056 DEBUG [c.c.u.d.ScriptRunner] (main:null) (logid:) -- regarding copyright ownership.  The ASF licenses this file
2022-09-23 11:40:26,056 DEBUG [c.c.u.d.ScriptRunner] (main:null) (logid:) -- to you under the Apache License, Version 2.0 (the
2022-09-23 11:40:26,056 DEBUG [c.c.u.d.ScriptRunner] (main:null) (logid:) -- "License"); you may not use this file except in compliance
2022-09-23 11:40:26,056 DEBUG [c.c.u.d.ScriptRunner] (main:null) (logid:) -- with the License.  You may obtain a copy of the License at
2022-09-23 11:40:26,056 DEBUG [c.c.u.d.ScriptRunner] (main:null) (logid:) --
2022-09-23 11:40:26,056 DEBUG [c.c.u.d.ScriptRunner] (main:null) (logid:) --   http://www.apache.org/licenses/LICENSE-2.0
2022-09-23 11:40:26,056 DEBUG [c.c.u.d.ScriptRunner] (main:null) (logid:) --
2022-09-23 11:40:26,056 DEBUG [c.c.u.d.ScriptRunner] (main:null) (logid:) -- Unless required by applicable law or agreed to in writing,
2022-09-23 11:40:26,057 DEBUG [c.c.u.d.ScriptRunner] (main:null) (logid:) -- software distributed under the License is distributed on an
2022-09-23 11:40:26,057 DEBUG [c.c.u.d.ScriptRunner] (main:null) (logid:) -- "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
2022-09-23 11:40:26,057 DEBUG [c.c.u.d.ScriptRunner] (main:null) (logid:) -- KIND, either express or implied.  See the License for the
2022-09-23 11:40:26,057 DEBUG [c.c.u.d.ScriptRunner] (main:null) (logid:) -- specific language governing permissions and limitations
2022-09-23 11:40:26,057 DEBUG [c.c.u.d.ScriptRunner] (main:null) (logid:) -- under the License.
2022-09-23 11:40:26,057 DEBUG [c.c.u.d.ScriptRunner] (main:null) (logid:) --;
2022-09-23 11:40:26,057 DEBUG [c.c.u.d.ScriptRunner] (main:null) (logid:) -- Schema upgrade cleanup from <IP_ADDRESS> to <IP_ADDRESS>
2022-09-23 11:40:26,057 DEBUG [c.c.u.d.ScriptRunner] (main:null) (logid:) --;
2022-09-23 11:40:26,057 DEBUG [c.c.u.DatabaseUpgradeChecker] (main:null) (logid:) Cleanup script Upgrade41700to41710 is executed successfully
2022-09-23 11:40:26,076 DEBUG [c.c.u.DatabaseUpgradeChecker] (main:null) (logid:) Upgrade completed for version <IP_ADDRESS>

Merging based on the manual testing and LGTMs


Tell People to use Github Discussions for Support

Since we just turned these on

Codecov Report

Merging #111 (c7eab09) into master (a56fb25) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #111   +/-   ##
=======================================
  Coverage   38.82%   38.82%
=======================================
  Files          41       41
  Lines        1092     1092
  Branches      148      148
=======================================
  Hits          424      424
  Misses        531      531
  Partials      137      137

Continue to review full report at Codecov.

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


robots.txt exclusion: Disallow: rules after empty Disallow: get ignored

RobotRule.blocksPathForUA(String, String) returns false for any paths with this robots.txt:
User-agent: *
Disallow:
Disallow: /wp-admin
Disallow: /wp-includes
Disallow: /wp-login.php
Disallow: /wp-content/plugins
Disallow: /wp-content/cache
Disallow: /wp-content/themes
Disallow: /trackback
Disallow: /comments

Per robots.txt specification, empty Disallow: shall be just ignored. Current RobotRule implementation returns false  when it hits empty Disallow:, ignoring the rest of rules.
Ref: internetarchive/wayback#73

We have a fix for this issue. Going forward, it'd be great to replace robots.txt parsing code with more reliable third party library (from Heritrix?)


Terminal (Dev Build) crashed on launch

I was using VS 2019 and 1903 SDK, the building and deployment were all good, while the terminal crashed on launch.
I started a debug instance and got this following message:
Exception thrown at 0x00007FFB0EDEE052 (Windows.UI.Xaml.dll) in WindowsTerminal.exe: 0xC0000005: Access violation reading location 0x0000000000000610. occurred

Since you've got a dev build running, and you're using Visual Studio to do it, it would be very helpful if you could give us a call stack instead of just an exception line. :smile:

Actually, it turned out to be that the Xaml lib was not correctly loaded. This problem should be solved by reloading Xaml from NuGet.


Initial implementation

Changes Unknown when pulling 99a611bee38c6f8ac12b2b0221038481c2739948 on yokuze:initial_implementation into ** on silvermine:master**.

Changes Unknown when pulling 99a611bee38c6f8ac12b2b0221038481c2739948 on yokuze:initial_implementation into ** on silvermine:master**.

Changes Unknown when pulling 6763ea408f01afd2fe28625861652c6639b2dc5f on yokuze:initial_implementation into ** on silvermine:master**.

Changes Unknown when pulling 8c1bcbe8c4ae4ce27427cdd6dff50cac9395a35d on yokuze:initial_implementation into ** on silvermine:master**.

Ok @jthomerson, this is ready for the re-review.


Idea for communication

Hi, How about we start a closed discord or telegram group for this work. Would be good to get more of a community around this development and enable questions and ideas to flow better. Also I feel that this will bring out more question & ideas that people may feel able to ask in a less formal forum also will allow the group to offer answers to questions rather then just 2-3 leaders. - Then the Git can be a more formal tool around the code itself and workflow. Thoughts?

I like it!
On Wed, Feb 7, 2018, 2:33 PM Bird-NZ<EMAIL_ADDRESS>wrote:

Hi, How about we start a closed discord or telegram group for this work.
Would be good to get more of a community around this development and enable
questions and ideas to flow better. Also I feel that this will bring out
more question & ideas that people may feel able to ask in a less formal
forum also will allow the group to offer answers to questions rather then
just 2-3 leaders. - Then the Git can be a more formal tool around the code
itself and workflow. Thoughts?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/AbenezerMamo/crypto-signal/issues/157, or mute the
thread
https://github.com/notifications/unsubscribe-auth/AdLWUL7T1k6mG4EA4zR68-PQ8rCVtErdks5tSfqXgaJpZM4R9RHl
.

Over the last month or so of development, myself and @jrbartola have learned a few things that require us to take stock of where we are at and what the next best thing for the project is. We are meeting this weekend to chat about it.
I've been thinking for quite some time it would be good to build a community aspect to the project and would love to foster that. We just want to be certain that we are building the right thing to form a community around.
I will keep this open and give an update early next week :)

Thanks for your sprite of openness to where the process thinking is, I do really appreciate that. To add my 10 cents of encouragement to this, I'd be saddened if this work stopped entirely but I understand and encourage that often there is a need to pivot on an idea or concept.
I feel like we at just at the start of something here that an interesting and diverse community could evolve from. Thx again, Mat.

Just to be clear we do not intend to stop development. We may just be re-adjusting the scope and intent so that we can be excellent at a particular job instead of being mediocre at several :)

Myself and @jrbartola caught up today and have made some solid decisions on what we intend to do moving forward.
First thing we are going to be doing is removing the bot and the UI behaviours from the project. Over the coming months we'll be providing that functionality in a different format but it won't be a part of this project. There are three primary reasons for this...

It feels like a bunch of very different projects slammed together.
Turning the trade bot into something genuinely useful requires more time and computational power than is reasonable for your average PC.
The current structure provides an acceptable user experience but the development experience is currently very poor, which is a side effect of problem 1 and 2.

Second thing is we will be doubling down on the default behaviour to turn it into a more useful trading assistant. We believe this to be the most widely used and useful component of the project but it hasn't seen the love it deserves and we want to fix that.
Last of all, we will be starting a community slack / discord / something in the coming week or two once we feel like we have sufficiently got the house in order. I'll update this issue and the Readme once that has happened.

Sounds great to me team, looking forward to being involved.

Hi all,
@shads2 and I have opened a Discord channel to harbor a community around this project. Feel free to share this with anybody who is interesting in crypto-signal and its development!

And with the discord opened I am closing this issue :)

@shads2 I like the idea of separating this into explicit projects. Is it too large of an ask to break this completely out as a data aggregator and then everything else can just be built on top of the database? Such as the entire analyzer is removed from the data aggregator peice?
This would make it super versatile and very useful to people even outside this project?

It wouldn't be useful to the average user. The amount of data it generates means you need to be running a reasonably sized instance on AWS, GCP or some other hosting provider and if you already have that level of technical knowledge... you probably already have the technical knowledge required to write the ingestor, it's very, very simple.
Once you move past data ingestion into the territory of the other component you begin to hit bigger problems. To make automated trade worth while you actually need vast amounts of computing because predicting the future with any degree of reliability is actually kind of resource intensive. It would cost an individual way more in computation than they would likely make from the automation.
We could easily provide something terrible that could potentially function in an up trending market and then throw your money out a window in a down trending market... but humans can already do that just fine themselves and I don't want to be responsible for providing that kind of shitty behaviour as software.
We do intend to continue working towards something useful for everyone, but simple restructures to the code are not enough to make it useful, it would just become a costly disappointment.

You'd be surprised by how many people are looking for an easy data ingestor/aggregator, but I totally see what you are saying -- and appreciate the response.
With that, to be clear - once you re-tool the project. It will doing the data ingesting and continue to add the later of dynamic trade assisting? Not 100% clear what the overall vision is now with the new direction.
Thanks!

For this current project, we aim to make it the best possible assistant we can to manual traders. We intend to keep it lightweight and highly targeted to that use case.
Myself and @jrbartola are starting work on a new project for the automated trade assistant, but I can't give too many details yet because honestly we haven't 100% nailed down how everything is going to work yet.


I updated ng2-datetime.js to have my stuff working

Because in Ng2DateTimePickerDirective.normalizeInput
Ng2DateTime.parseDate is called without a dateFormat parameter

I had to change NG2DateTime

I added an else{} when there is no dateFormat to send the date back with the default format 'YYYY-MM-DD HH:mm'
Please also update the documentation home page to YYYY-MM-DD HH:mm instead of YYYY-MM-DD HH:MM

Thank you. I will update it later.
However, if you create a PR, the change will be much faster.

I changed it local on my laptop,so i can continue.
I just wanted to share it with you guys because maybe it can help others.
Kind rg,
Stefan.


chore: release 1.10.0

:robot: I have created a release *beep* *boop*
1.10.0 (2022-11-22)
Features

add .mode() and .credentials() (73f1cc2)
add .redirect(mode) (094549b)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/keq-request/keq/releases/tag/v1.10.0 :sunflower: