[BUG] disk module + logo causes straggling characters that disappear on window resize

General description of bug:

What happened: With {"modules":["disk"]} set as the config.jsonc (to be clear it happens with more than one module, just that module has to enabled), invoking the command will generate \s before the first driver letter. The few other straggling characters, will show if any module's present + logo. It was resized back to the same size with ALT+ENTER 2x in Alacritty, starting window size doesn't seem to matter.
What should happen: Should look the same as the resized window has been resized.
Fastfetch version used: fastfetch 2.12.0 (x86_64)
Did it work in an older version: Somewhat, but there was a similar bug.
Where did you get the binary: Scoop (GitHub release)
Does this issue still occurs in the latest dev build? yes

Often helpful information:
Screenshot:

invocation
❯ fastfetch
l\\\\                           ..,         Disk (C:\): 421.07 GiB / 3.72 TiB (11%) - NTFS
                    ....,,:;+ccllll    Disk (D:\): 1.54 TiB / 1.82 TiB (85%) - NTFS
      ...,,+:;  cllllllllllllllllll
,cclllllllllll  lllllllllllllllllll
llllllllllllll  lllllllllllllllllll
llllllllllllll  lllllllllllllllllll
llllllllllllll  lllllllllllllllllll
llllllllllllll  lllllllllllllllllll
llllllllllllll  lllllllllllllllllll

llllllllllllll  lllllllllllllllllll
llllllllllllll  lllllllllllllllllll
llllllllllllll  lllllllllllllllllll
llllllllllllll  lllllllllllllllllll
llllllllllllll  lllllllllllllllllll
`'ccllllllllll  lllllllllllllllllll
       `' \*::  :ccllllllllllllllll
                       ````''*::cll
h                                ``                             ``

window resize
❯ fastfetch
                                ..,    Disk (C:\): 421.07 GiB / 3.72 TiB (11%) - NTFS
                    ....,,:;+ccllll    Disk (D:\): 1.54 TiB / 1.82 TiB (85%) - NTFS
      ...,,+:;  cllllllllllllllllll
,cclllllllllll  lllllllllllllllllll
llllllllllllll  lllllllllllllllllll
llllllllllllll  lllllllllllllllllll
llllllllllllll  lllllllllllllllllll
llllllllllllll  lllllllllllllllllll
llllllllllllll  lllllllllllllllllll

llllllllllllll  lllllllllllllllllll
llllllllllllll  lllllllllllllllllll
llllllllllllll  lllllllllllllllllll
llllllllllllll  lllllllllllllllllll
llllllllllllll  lllllllllllllllllll
`'ccllllllllll  lllllllllllllllllll
       `' \*::  :ccllllllllllllllll
                       ````''*::cll
                                 ``

logo null (no resize needed)
❯ fastfetch
Disk (C:\): 421.07 GiB / 3.72 TiB (11%) - NTFS
Disk (D:\): 1.54 TiB / 1.82 TiB (85%) - NTFS

The content of the configuration file you use (if any):

invocation & resize
{
  "$schema": "https://github.com/fastfetch-cli/fastfetch/raw/dev/doc/json_schema.json",
  "modules": [
    "disk"
  ]
}

logo null
{
  "$schema": "https://github.com/fastfetch-cli/fastfetch/raw/dev/doc/json_schema.json",
  "logo": null,
  "modules": [
    "disk"
  ]
}

Output of fastfetch --list-features:
threads
vulkan
zlib
opencl
Proprietary GPU driver API

Shell: PowerShell 7.5.0-preview.2
Term: alacritty 0.14.0-dev (3a7f21b0)
OpenConsole/conhost: 1.20.2405.06001
Windows: 10.0.19044.4412

Can you reproduce it with Windows Terminal?

Nope doesn't happen on wt.

Doesn't happen on Wezterm either. I think you should report it to alacritty

I think it was caused by the hyperlink escape code. I don't know if alacritty supports it. If not, the escape should be silently ignored

Yes fastfetch --pipe works, there's just no color.

fastfetch --disk-key 'Disk ({1})' should also work

Tested in Linux. alacritty worked fine. Therefore it should be a Windows specific issue.

fastfetch --disk-key 'Disk ({1})' should also work

Yea it does, is there a way to set that in config.jsonc?

I downloaded and tried alacritty. It worked for me in both Win11 and Win10 (VM)

Have no idea what's wrong in your machine.

 Then try launching Alacritty and see if you can repro 🤔.

Uhh, I restarted my PC, and the issue disappeared, I have no clue what the cause was o_O.


Viewers: Indicate the selected column in the column selector

This issue has been mirrored in Jira: https://reddata.atlassian.net/browse/GROK-15236

DG 1.19.0


TreeView Drag And Drop no work

hi~
vs2015 asp.net mvc
when i use link to cdn.jsdelivr.net in view  page

Drag And Drop work fine
but
when i download js and css to view

the Drag And Drop no work
and when i try

to web first layer view page , <script src="@Url.Content("~/Scripts/gijgo/combined/gijgo.js")" type="text/javascript">
is work fine , but   jquery.ui.datepicker.js   will be no work
have any idea?
thank you~~~

I would recommend you to upgrade to version 1.9.6.
Could you tell me if you have any javascript errors when you use local js files. Can you check if the file is loaded correctly.
If you want to use jqueryui datepicker, then the jqueryui.js needs to be included after the gijgo.js. If gijgo.js is included after jqueryui.js, then gijgo datepicker override jqueryui datepicker and etc.

hi~
2.
when i use local js file , no error show in console , but when i  drag and drop item , the console show
Error: no such method 'isOver' for droppable widget instance
when i use<EMAIL_ADDRESS>, no error
and  jquery.ui.datepicker.js will be no  work

i try , if local  gijgo.js after  jqueryui.js , drag and drop is work , but jquery.ui.datepicker.js will be no work
if   jqueryui.js  after  local gijgo.js , drag and drop no  work

I see. jqueryui doesn't work well with gijgo. I would recommend you to use just one of these libraries. just jqueryui or just gijgo. Sorry for the inconvenience.

Thank you for Help and gijgo :)


New requirement - at least one minus letter validation

Thanks

Just to clarify here @usackoka - are you suggesting that requiring a lowercase letter should be a validation option?

Yes, for example:
<PasswordChecklist
rules={['length', 'specialChar', 'number', 'capital', 'match', 'minus']}
messages={{
minus: 'At least one lower case letter.',

Duplicate of #6


Error when trying to pull plugin [Traefik]

Hi,
when I update the version number from v1.6.47 to v1.6.48/49 it gives me this error in the traefik log
ERR Plugins are disabled because an error has occurred. error="unable to set up plugins environment: unable to download plugin github.com/darkweak/souin: failed to call service: Get \"https://plugins.traefik.io/public/download/github.com/darkweak/souin/v1.6.49\": GET https://plugins.traefik.io/public/download/github.com/darkweak/souin/v1.6.49 giving up after 4 attempt(s)"
it works fine with versions older than 1.6.47. Sorry, I'm not exactly sure how the automation works, is this something that you control?
Thank you in advance!

Same here!

That's an error on their side, it works when I'm mounting the plugin from the source code to the path /plugins-local/src/github.com/darkweak/souin in træfik directly using localPlugins configuration key. Even if I try with a simple curl, it doesn't download the resource, but it exists because if I send a curl request on https://plugins.traefik.io/public/download/github.com/darkweak/souin/v1.6.50, it throws a 404 not found.

Thank you, so I guess local install is the option for now.

Are there any updates on the situation? As I am still experiencing the same issue.

@AlphaCraft9658 that's an issue related to Træfik, not this repository.

@AlphaCraft9658 that's an issue related to Træfik, not this repository.

Yeah, but I thought maybe someone knows something and I could just ask here instead of searching, but okay. I'm sorry if that's a problem.


Warning, Failed - Network Key Not Set

I added Network key to option.xml but still
Warning, Failed - Network Key Not Set

I added Network key to option.xml but still

What? :confused:
You have to add network key using the UI

I am sorry this my first project,please can you explain this point.😢

@Ghada-Ch Once installed and running, go to localhost:8091 --> settings tab --> zwave settings --> network key

That's why I am asking bcz  localhost:8091 doesn't work !


Re-design ScopeFlags

Personally I find the design of ScopeFlags confusing. It's also a bit bloated - we can pack more information into less bits.
For example, presently we use separate bits for Constructor and GetAccessor, but the two are mutually exclusive - a function can't be both a constructor and a getter. So we can compress this info.
New design
I propose redesigning it as an 8-bit bitfield with the following parts:

Bits 0-2: "Full" function type i.e. function or method (not arrow)
Bits 3-4: "Special" block i.e. ClassStaticBlock / TsModuleBlock
Bit 5: Strict mode
Bit 6: Arrow function
Bit 7: Statement block

Why?
Encode more info
This allows us to distinguish between many different states which we can't presently without searching up the scopes stack. e.g.:

At program top level (ScopeFlags::Top).
In a nested statement block at program top level (ScopeFlags::Block).
At top level within a function (ScopeFlags::Function).
In a nested statement block within a function (ScopeFlags::Function | ScopeFlags::Block).
In an arrow function within a class constructor (ScopeFlags::Constructor | ScopeFlags::Arrow).

Reduce type size
Reducing ScopeFlags from 2 bytes to 1 byte is not such a big wow in itself.
But getting it down to 8 bits would also allow packing it into ScopeId. ScopeId can be a u32, but 24 bits should suffice for the actual ID (16 million scopes is probably enough for any JS file). So the top 8 bits could contain the scope flags. Then we can have scope type info embedded inline, reducing memory accesses.
Implementation
Implementation something like this:
const FUNCTION_TYPE_MASK:  u8 = 0b00000111;
const BLOCK_TYPE_MASK:     u8 = 0b00011000;
const BLOCK_TYPE_SHIFT:    u8 = 3;
const STRICT_MODE:         u8 = 0b00100000;
const ARROW:               u8 = 0b01000000;
const BLOCK:               u8 = 0b10000000;

#[derive(Clone, Copy, Debug, PartialEq)]
pub struct ScopeFlags(u8);

#[derive(Clone, Copy, Debug, PartialEq)]
#[repr(u8)]
pub enum FunctionType {
  None = 0,
  Function = 1,
  ObjectMethod = 2,
  ClassMethod = 3,
  GetAccessor = 4,
  SetAccessor = 5,
  Constructor = 6,
  // 7 is unused
}

#[derive(Clone, Copy, Debug, PartialEq)]
#[repr(u8)]
pub enum SpecialBlockType {
  None = 0,
  ClassStaticBlock = 1 << BLOCK_TYPE_SHIFT,
  TsModuleBlock = 2 << BLOCK_TYPE_SHIFT,
  // 3 is unused
}

#[allow(non_upper_case_globals)]
impl ScopeFlags {
  pub const Top: Self = Self(FunctionType::None as u8);
  pub const Function: Self = Self(FunctionType::Function as u8);
  pub const Constructor: Self = Self(FunctionType::Constructor as u8);
  pub const GetAccessor: Self = Self(FunctionType::GetAccessor as u8);
  pub const SetAccessor: Self = Self(FunctionType::SetAccessor as u8);

  pub const ClassStaticBlock: Self = Self(SpecialBlockType::ClassStaticBlock as u8);
  pub const TsModuleBlock: Self = Self(SpecialBlockType::TsModuleBlock as u8);

  pub const StrictMode: Self = Self(STRICT_MODE);
  pub const Arrow: Self = Self(ARROW);
  pub const Block: Self = Self(BLOCK);
}

impl ScopeFlags {
  pub const fn at_top(self) -> bool {
    self.function_type() == FunctionType::None
  }

  pub const fn function_type(self) -> FunctionType {
    unsafe { std::mem::transmute(self.0 & FUNCTION_TYPE_MASK) }
  }

  pub const fn in_full_function(&self) -> bool {
    self.function_type() != FunctionType::None
  }

  pub const fn special_block_type(self) -> SpecialBlockType {
    unsafe { std::mem::transmute(self.0 & BLOCK_TYPE_MASK) }
  }

  pub const fn in_special_block(self) -> bool {
    self.special_block_type() != SpecialBlockType::None
  }

  pub const fn is_strict_mode(self) -> bool {
    (self.0 & STRICT_MODE) != 0
  }

  pub const fn in_arrow(self) -> bool {
    (self.0 & ARROW) != 0
  }

  pub const fn in_block(self) -> bool {
    (self.0 & BLOCK) != 0
  }

  pub const fn with_function_type(self, fn_type: FunctionType) -> Self {
    Self((self.0 & !FUNCTION_TYPE_MASK) | fn_type as u8)
  }

  pub const fn with_special_block_type(self, block_type: SpecialBlockType) -> Self {
    Self((self.0 & !BLOCK_TYPE_MASK) | block_type as u8)
  }

  pub const fn with_strict_mode(self, is_strict: bool) -> Self {
    Self((self.0 & !STRICT_MODE) | (is_strict as u8 * STRICT_MODE))
  }

  pub const fn with_arrow(self, is_arrow: bool) -> Self {
    Self((self.0 & !ARROW) | (is_arrow as u8 * ARROW))
  }

  pub const fn with_block(self, is_block: bool) -> Self {
    Self((self.0 & !BLOCK) | (is_block as u8 * BLOCK))
  }
}

Any thoughts?

Just to say this isn't just about reducing the size of ScopeFlags. It's about increasing the amount of information that can be got from ScopeFlags.
e.g.:
function foo(value) {
  return (cond) => {
    if (cond) {
      return value;
    }
  };
}

At present the sequence of changes in current ScopeFlags as move from top level to return value; is:
Top -> Function -> Arrow -> Block.
This change would make it:
Top -> Function -> Function | Arrow -> Function | Arrow | Block.
So when you're visiting return value; you can get a lot more information about surrounding context from the current ScopeFlags:

Am I in a function? Yes.
What kind of function is it? A "normal" function, not a method or constructor.
Am I in an arrow function within that function? Yes.
Am I in a nested block within that arrow function? Yes.

Whereas the only answers ScopeFlags can give you at present are:

Am I in a function? I can't tell you.
What kind of function is it? I can't tell you.
Am I in an arrow function? I can't tell you.
Am I in a nested block? Yes.

To answer the "don't knows", currently you have to search up the scope stack, which is more expensive.
This extra info would reduce the code required in #3258, for example.

It's about increasing the amount of information that can be got from ScopeFlags

It's going to be a lot more difficult to test the semantics if we change its meaning right now,  let me think about this 😅

Doesn't have to be right now. I could implement it as TraverseScopeFlags and we test this out in the transformer, then integrate it back into semantic etc later on.
Or maybe just push it onto back burner entirely.


[WIP] Working on "organization" APIs implementations and/or refactoring

Good start, @lalalah. Let me know if you need help getting a test groove going. :zap:

Hey @pengwynn I have added the plan struct. However the following API for editing cannot be implemented because Go does not support Patch and doesn't seem likely that it will in near future.

https://developer.github.com/v3/orgs/#edit-an-organization

Here's a discussion in the Go Lang group talking about possibilities of implementing Patch.

https://groups.google.com/forum/#!topic/golang-nuts/GjngdEKsUXA

I can see how this can be done in POST with some changes on the server side tho. Please let me know what you think. I will go ahead and work on something else before I hear back.

I think the mailing list topic was for the ParseForm method. NewRequest definitely accepts PATCH since we're using it in other places. Does that help?

Cool. My bad. Turns out Request is defined in every layer of the wrappers and I got caught up tracking them down! :stuck_out_tongue_closed_eyes:
The patch method as well as its test cases; testing both method and body of the patch http call.
NOTE: I think this is a typo:
On the development page https://developer.github.com/v3/orgs/#response-3, I think the description field in the response should have be updated to:

"description": "GitHub, the company."

However the page currently says the following, which I think is wrong:

"description": "A great organization",

I have designed my test with my understanding. If the developer page is not a typo, please let me know and I'll revert it.

I think the description field in the response should have be updated

The sample responses in the docs are there to show the fields, not so much the values. I'd grab the fixtures you need for your tests via curl from the API. :grinning:

Yep I've been doing that! This is the first time I run into a situation where I don't have the permission to view the fields! Would you help me out?
How does this look otherwise?

For your convenience, the json fixture that I need for organzation(after update) but couldn't curl is here: https://github.com/octokit/go-octokit/blob/5e68239c4c25c486843cd3c4ae2b161b729ffdee/fixtures/organization_updated.json

updated per discussion in https://github.com/octokit/go-octokit/pull/98#discussion_r27810077

@feiranchen This is looking good, I like the recent changes. Anything else to implement here before we merge?

@pengwynn Thanks for your feed back!
It's all good except the test fixture for this specific task was not curl-ed, but rather from the developer's documentation site. This is because I don't have the permission to curl some of these fields.
For your convenience, the json fixture that I need for organzation but couldn't curl is here: https://github.com/octokit/go-octokit/blob/5e68239c4c25c486843cd3c4ae2b161b729ffdee/fixtures/organization_updated.json

@feiranchen No problem. I just updated the fixture.

@feiranchen I think we'll have to update the test after changing the fixture. If you need me to take another look, just add the needs-review label back on there.

Synced with test cases. No high level update.

:cake:


Add STS assume role and web identity credential providers

Issue #

awslabs/aws-sdk-kotlin#325
awslabs/aws-sdk-kotlin#19
Description of changes

Provide SDK types for aws-crt-kotlin credential providers: sts assume role and sts web identity

Scope

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

I didn't setup the cross-repo branches for this so the aws-crt-kotlin change will need to be merged before CI will pass.


React Native Expo Build Failing due to cocoapods version

Summary
Recently, expo eas started to spontaneously install cocoapods 1.15.0 which was causing expo iOS builds to fail.
The thing is that even forcing the installation (in several ways) of a previous working cocoapods version (in our case, 1.14.3), the expo build overwrites it and still uses 1.15.0 to run pod install.
Already Modified eas.json with
...
 "ios": {
        "image": "latest",
        "resourceClass": "default",
        "cocoapods": "1.14.3"
   },
   ...

but this takes no effect at all. eas build with  --clear-cache also no effect
Using app configuration:
[READ_APP_CONFIG] Using app configuration:
[READ_APP_CONFIG] {
  "name": "Closet Kitchen Sink",
  "slug": "closet-kitchen-sink",
  "version": "0.1.2",
  "sdkVersion": "49.0.0",
  "platforms": [
    "ios",
    "android",
    "web"
  ],
  "orientation": "portrait",
  "icon": "./assets/icon.png",
  "splash": {
    "image": "./assets/splash.png",
    "resizeMode": "contain",
    "backgroundColor": "#ffffff"
  },
  "updates": {
    "fallbackToCacheTimeout": 0,
    "url": "https://u.expo.dev/e45e67a4-43eb-4b49-9510-314c393e4783"
  },
  "assetBundlePatterns": [
    "**/*"
  ],
  "ios": {
    "supportsTablet": true,
    "bundleIdentifier": "com.xxxxxx.closetkitchensink",
    "infoPlist": {
      "UIBackgroundModes": [
        "fetch",
        "remote-notification"
      ]
    },
    "googleServicesFile": "./GoogleService-Info-qa.plist"
  },
  "android": {
    "allowBackup": false,
    "softwareKeyboardLayoutMode": "pan",
    "adaptiveIcon": {
      "foregroundImage": "./assets/adaptive-icon.png",
      "backgroundColor": "#FFFFFF"
    },
    "package": "com.xxxxxxx.closetkitchensink",
    "googleServicesFile": "./google-services-qa.json"
  },
  "web": {
    "favicon": "./assets/favicon.png",
    "bundler": "metro"
  },
  "plugins": [
    [
      "expo-build-properties",
      {
        "ios": {
          "flipper": false,
          "deploymentTarget": "14.0",
          "useFrameworks": "static"
        }
      }
    ],
    [
      "@react-native-firebase/app"
    ],
    [
      "./plugins/withAndroidRiveAssets"
    ]
  ],
  "extra": {
    "eas": {
      "projectId": "333333333333"
    }
  },
  "owner": "xxx-xxx",
  "runtimeVersion": {
    "policy": "sdkVersion"
  }
}

Some logs:
Cocoapods version in your eas.json does not match the version currently installed in your system
[SETUP_WORKINGDIR] Preparing workingdir /var/folders/gh/0cww6vn93nv_jjsw3xkm0b4m0000gn/T/eas-build-local-nodejs/dcc0aa2c-750e-4b87-b960-a3fa38047581
[START_BUILD] Starting build
 "job": {
   "type": "managed",
   "platform": "ios",
   "projectArchive": {
     "type": "PATH",
     "path": "/var/folders/gh/0cww6vn93nv_jjsw3xkm0b4m0000gn/T/eas-cli-nodejs/713f90[82](https://github.com/xxxxxxxxxxxx/actions/runs/7991059456/job/21821579243#step:13:83)-5b0f-4af4-9d9c-90a019cc0deb.tar.gz"
   },
   "projectRootDirectory": "apps/kitchen-sink-app",
   "builderEnvironment": {
     "image": "latest",
     "cocoapods": "1.14.3"
   },
   "cache": {
     "disabled": false,
     "paths": [],
     "clear": true
   },
   "updates": {},
   "scheme": "ClosetKitchenSink",
   "version": {
     "buildNumber": "[96](https://xxxxxxxxx/Closet-Kitchen-Sink/actions/runs/7991059456/job/21821579243#step:13:97)"
   },
   "experimental": {},
   "mode": "build",
   "triggeredBy": "EAS_CLI"
 }

...

[INSTALL_PODS] Installing glog (0.3.5)
[INSTALL_PODS] Installing hermes-engine (0.72.10)
[INSTALL_PODS] [!] Error installing hermes-engine
[INSTALL_PODS] ――― MARKDOWN TEMPLATE ―――――――――――――――――――――――――――――――――――――――――――――――――――――――――――
[INSTALL_PODS] ### Command
[INSTALL_PODS] ```
[INSTALL_PODS] /usr/local/lib/ruby/gems/3.0.0/bin/pod install
[INSTALL_PODS] ```
[INSTALL_PODS] ### Report
[INSTALL_PODS] * What did you do?
[INSTALL_PODS] * What did you expect to happen?
[INSTALL_PODS] * What happened instead?
[INSTALL_PODS] ### Stack
[INSTALL_PODS] ```
[INSTALL_PODS]    CocoaPods : 1.15.0
[INSTALL_PODS]         Ruby : ruby 3.0.6p216 (2023-03-30 revision 23a532679b) [x86_64-darwin21]
[INSTALL_PODS]     RubyGems : 3.5.5
[INSTALL_PODS]         Host : macOS 12.7.3 (21H1015)
[INSTALL_PODS]        Xcode : 14.2 (14C18)
[INSTALL_PODS]          Git : git version 2.43.0
[INSTALL_PODS] Ruby lib dir<EMAIL_ADDRESS>
Managed or bare?
Managed
Environment
expo-env-info 1.2.0 environment info:
    System:
      OS: macOS 12.7.3
      Shell: 3.2.57 - /bin/bash
    Binaries:
      Node: 18.19.0 - /var/folders/gh/0cww6vn93nv_jjsw3xkm0b4m0000gn/T/yarn--1708531962090-0.9098061866296252/node
      Yarn: 1.22.19 - /var/folders/gh/0cww6vn93nv_jjsw3xkm0b4m0000gn/T/yarn--1708531962090-0.9098061866296252/yarn
      npm: 10.2.3 - ~/hostedtoolcache/node/18.19.0/x64/bin/npm
    Managers:
      CocoaPods: 1.14.3 - /Users/runner/hostedtoolcache/Ruby/2.7.6/x64/bin/pod
    SDKs:
      iOS SDK:
        Platforms: DriverKit 22.2, iOS 16.2, macOS 13.1, tvOS 16.1, watchOS 9.1
      Android SDK:
        API Levels: 31, 32, 33, 33, 33, [34](https://github.com/Utility-NYC/Closet-Kitchen-Sink/actions/runs/7991911947/job/21824514886#step:15:35), 34, 34
        Build Tools: 31.0.0, 32.0.0, 33.0.0, 33.0.1, 33.0.2, 33.0.3, 34.0.0
        Android NDK: 25.2.9519653
    IDEs:
      Xcode: 14.2/14C18 - /usr/bin/xcodebuild
    npmPackages:
      @expo/metro-config: ~0.10.7 => 0.10.7
      babel-preset-expo: ~9.5.1 => 9.5.2
      expo: ~[49](https://xxxxxxxxxx/Closet-Kitchen-Sink/actions/runs/7991911947/job/21824514886#step:15:50).0.18 => 49.0.22
      metro: 0.78.0 => 0.78.0
      react: 18.2.0 => 18.2.0
      react-dom: 18.2.0 => 18.2.0
      react-native: 0.72.10 => 0.72.10
      react-native-web: ~0.19.6 => 0.19.9
    Expo Workflow: managed

Error output
No response
Reproducible demo or steps to reproduce from a blank project
eas build --profile=store --plarform=ios

Hi there, I see that your logs come from the --local build. There are some limitations regarding local builds: https://docs.expo.dev/build-reference/local-builds/#limitations. One of them is that Customizing versions of software is not supported, fields node, yarn, fastlane, cocoapods, ndk, image in eas.json are ignored.
So basically if you run a build not on EAS servers (--local) you are responsible for making sure that the correct tool version is installed on the device. You can also see a warning about version mismatch in your logs:
Cocoapods version in your eas.json does not match the version currently installed in your system
[SETUP_WORKINGDIR] Preparing workingdir /var/folders/gh/0cww6vn93nv_jjsw3xkm0b4m0000gn/T/eas-build-local-nodejs/dcc0aa2c-750e-4b87-b960-a3fa38047581
...


Keep current snipe when can't find further chars

Currently I'm using evil-snipe a la Clever-F, and it works as intended. The only thing I noticed is that if I land on the last occurrence and hit 'f' again while on it, I'll get a message saying "Can't find char" and I'll lose the current snipe and I'll have to reinput the snipe again, in the reverse direction. Is there anyway to change this behavior? If you need clarification, I can give examples.

Sorry that I've only gotten to this now. This should be fixed as of 3ae382d, so I'll consider this resolved. Feel free to reopen this if that isn't the case.


Add Go 1.13 to Travis

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Hi @gliptak,
Thank you for your contribution. As you can see the Travis tests are failing with this change, and I believe it's because of this issue. Changing the logic to get get all on v1.13 should fix it. Also, there are some places where the latest Go version is referenced and should be increased.

Hi @gliptak,
It seems like there are lots of errors unrelated to your PR that are nonetheless causing Travis to fail sporadically. My suspicion is #156 had some unintended consequences that lead to this behavior, since it affected BeginSegment. We'll have to do some investigation here and determine if the PR or the tests themselves are broken and make the appropriate fix. Otherwise your changes look good.

@willarmiros thank you for the pointers. I will wait for the BeginSegment updates.
As for SQL, .1.12 picks up go: finding github.com/DATA-DOG/go-sqlmock v1.2.0 while 1.13 picks up go: finding github.com/DATA-DOG/go-sqlmock v1.2.0


fix(rollback) Use ingest proposal to submit status updates

Fixes an issue where ingesting status updates on key aspects getting soft deleted during rollbacks failed with the following exception:
Caused by: java.lang.UnsupportedOperationException: Failed to find Typeref schema associated with Config-based Entity
        at com.linkedin.metadata.models.ConfigEntitySpec.getAspectTyperefSchema(ConfigEntitySpec.java:78)
        at com.linkedin.metadata.entity.EntityService.toAspectUnion(EntityService.java:808)
        at com.linkedin.metadata.entity.EntityService.buildSnapshot(EntityService.java:757)
        at com.linkedin.metadata.entity.EntityService.produceMetadataAuditEvent(EntityService.java:555)
        at com.linkedin.metadata.entity.EntityService.sendEventForUpdateAspectResult(EntityService.java:387)
        at com.linkedin.metadata.entity.EntityService.ingestAspect(EntityService.java:353)

The reason being that non snapshot based aspects don’t have the typerefschema. To fix this, instead of using ingestAspect the code has been modified to use ingestProposal  which is also aligned with the intended use of these internal methods.
Checklist

[x] The PR conforms to DataHub's Contributing Guideline (particularly Commit Message Format)
[ ] Links to related issues (if applicable)
[ ] Tests for the changes have been added/updated (if applicable)
[ ] Docs related to the changes have been added/updated (if applicable). If a new feature has been added a Usage Guide has been added for the same.

build failed on :metadata-integration:java:datahub-protobuf:test ran locally and it passed.


Incorporate injection of custom Executor to the eventual Loader

This is enabled for ChunkSampleStream and ProgressiveMediaSource

Hey @tonihei, one area that I might have missed here is being able to listen on the Loader's onLoaderReleased callback for ProgressiveMediaSource. There isn't a way for us to know when to shutdown. Do you have any suggestions or if this should be added as a parameter?

There isn't a way for us to know when to shutdown without it. Ideally, we should be able to pass in our own downloadExecutorReleaser if possible.

Thanks for highlighting this again! This is actually also what we discussed before and it just came up during the internal review again too. I will add another parameter for onDownloadExecutorReleased or similar during the import.


Replace Repetitive Structures

For example, ["AXIS","Easting","EAST"] appears 1360 times in WKT data and should be replaced with a variable.

done


TFDeepSurv package on medical images ?

@liupei101 Thank you so much for the package.
Could you please tell is it possible to use TFDeepSurv package on medical images ?
Where can the convolution layers be introduced?
Thank you!

Thx for your feedback.
TFDeepSurv cannot directly be utilized for medical iamges. It is developed for a feature representation. If you want to use this package on your own images, maybe you can try to

add some conv modules in the model to extract the feature of image;
firstly obtain representations of images and then input it to TFDeepSurv.

Any survival prediction related models can be built upon TFDeepSurv. All you need is to deal with the input data (tables, images or 3D objects).


Accept gzipped FASTA for input

This is a large step towards #124, although initially only sourmash/branchwater and fastANI work.
Additional code will be required for ANIm, dnadiff and ANIb - and perhaps switching to a different test case there for speed.
Right now this is using the 4 bacteria (now gzipped), where sourmash/fastANI need just a couple of seconds to run.
Type of change

[ ] Bug fix (non-breaking change that fixes an issue)
[x] New feature (non-breaking change that adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality not to work as expected)
[ ] This change requires a documentation update
[ ] This is a documentation update

Action Checklist

[x] Work on a single issue/concept (if there are multiple separate issues to address, please use a separate pull request for each)
[x] Fork the pyani-plus repository under your own account (please allow write access for repository maintainers)
[x] Set up an appropriate development environment (please see CONTRIBUTING.md for this repository)
[x] Create a new branch with a short, descriptive name
[x] Work on this branch

[x] style guidelines have been followed (please see CONTRIBUTING.md for this repository)
[x] new code is commented, especially in hard-to-understand areas
[x] corresponding changes to documentation have been made
[x] tests for the change have been added that demonstrate the fix or feature works

[x] Test locally with pytest-plus -v non-passing code will not be merged
[x] Rebase against origin/master
[x] Check changes with linting/formatting tools before submission (please see CONTRIBUTING.md for this repository)
[x] Commit branch
[x] Submit pull request, describing the content and intent of the pull request
[ ] Request a code review
[x] Continue the discussion at Pull requests section in the pyan-plus repository

Currently this normalised the bacterial example back to all using .fna but in hindsight it makes sense to keep the assorted filenames in order to have tests with .fasta.gz etc too.


Formatting

Description
Once #52 and #28 are merged, the code should be formatted and all linting errors fixed.

I will do this after #67 is merged.


Context receivers in Kotlin

Hey, man.
As promised, here is the article on context receivers in Kotlin.
Let me know your thoughts 😃

Hey, man. I fixed the issues 😄

We can talk offline about the TF thing and we can merge


JOSS Review Feedback by Nick

Here is my feedback to improve the PyForestScan software for https://github.com/openjournals/joss-reviews/issues/7314.
General checks

[ ] Contribution and authorship: Has the submitting author (@iosefa) made major contributions to the software? Does the full list of paper authors seem appropriate and complete?
The main author is the only contributor in the source code of this package based on the commits history. However, the co-authors might have helped the development in early stages before using git to track changes. As it stands, without a few lines of explanation of their roles, I assume the other co-authors had mentoring, reviewing and funding acquisition roles. In JOSS, these roles do not qualify as authorship (link) and should not be included in this submission. Please clarify the co-authors role or do not include them.

[ ] Substantial scholarly effort: Does this submission meet the scope eligibility described in the JOSS guidelines
While this package does simplify several tasks (reading, cleaning, classifying, filtering, digital terrain and canopy height model creations and more) by acting as a wrapper around PDAL—which can be challenging to master due to its syntax and pipeline structure—it does not introduce any substantial new functionality except the computation of the metrics. For example, in the benchmarking section of the documentation, claims such as, “PyForestScan is designed for high performance and memory efficiency, ensuring it can handle large-scale point cloud datasets effectively,” could equally apply to PDAL itself, as PyForestScan primarily repackages PDAL’s capabilities rather than adding novel performance enhancements.
In my opinion, this package is indeed valuable for those looking to streamline tasks that might otherwise require working with PDAL’s more complex syntax with the added bonus of including few key tree metrics. However, since it functions as a wrapper rather than a significant software innovation, I believe it does not meet the minimum requirements for publication as original software in JOSS.

Functionality

[ ] Installation:
Installation works well, however, as you provide a Jupyter Notebook as a demo, you could include in the quickstart guide a section on how to install jupyter notebook (conda install jupyter) and run the demo with your test data.

[ ] Functionality:
In the demo notebook, there is an error importing plot_3d simply due to this functionality being removed due to dependencies problem (commit 249ca40). You just forgot to remove it from the demo notebook.
[OPTIONAL] However, I think it is worthwhile to have a 3D visualization capability, so if you can fix the dependencies problem you had, it would be cool to re-integrate this function and provide an extra cell in the demo notebook where you showcase plot_3d function and output. Just a suggestion, not required.

[ ] Performance:
The benchmark provided in the documentation appears to compare PDAL with leafR rather than showcasing any substantial improvements introduced by this package itself.  This because the bulk of the processing time is spent in reading the point clouds rather than computing the metrics, I believe. As a consequence, there doesn’t seem to be a specific contribution from the authors that significantly speeds up the PAI computation beyond what PDAL (repackaged into PyForestScan) already offers.

Documentation

[ ] Example usage: As you have prepared a demo notebook, please mention the demo notebook from the documentation.

Software paper

[ ] References:
Citation of PDAL is missing and of uttermost importance given this package almost entirely relies on PDAL.

For more detailed paper feedback, refer to this issue I opened.

@npucino
Thank you again for these very detailed comments. They have helped to improve the repository, the library, and the paper.
I will continue my response to your comments (as I did in #13):

The main author is the only contributor in the source code of this package based on the commits history. However, the co-authors might have helped the development in early stages before using git to track changes. As it stands, without a few lines of explanation of their roles, I assume the other co-authors had mentoring, reviewing and funding acquisition roles. In JOSS, these roles do not qualify as authorship (link) and should not be included in this submission. Please clarify the co-authors role or do not include them.

We added a Contributions section to the manuscript. iosefa did contribute a significant majority of the source code, but this was mostly done together with benleamon -- either through pair programming or discussion. benleamon presented the first version of the software to FOSS4G Asia and, while he has not contributed as much code, he has had an important impact on the develop of this library. For this reason, I think that it is important that he remains an author. Ryan Perroy provided guidance on the direction of the project during its later stages, and helped in the writing of the manuscript. However, seeing that this may not qualify, we have agreed to remove him as an author and instead include him in the acknowledgements in recognition of his contributions and support.

While this package does simplify several tasks (reading, cleaning, classifying, filtering, digital terrain and canopy height model creations and more) by acting as a wrapper around PDAL—which can be challenging to master due to its syntax and pipeline structure—it does not introduce any substantial new functionality except the computation of the metrics. For example, in the benchmarking section of the documentation, claims such as, “PyForestScan is designed for high performance and memory efficiency, ensuring it can handle large-scale point cloud datasets effectively,” could equally apply to PDAL itself, as PyForestScan primarily repackages PDAL’s capabilities rather than adding novel performance enhancements.
In my opinion, this package is indeed valuable for those looking to streamline tasks that might otherwise require working with PDAL’s more complex syntax with the added bonus of including few key tree metrics. However, since it functions as a wrapper rather than a significant software innovation, I believe it does not meet the minimum requirements for publication as original software in JOSS.

Thank you for raising this concern. We have re-organized the manuscript so that the emphasis is really on the tools that the library provides to calculate key forest structural metrics, rather than any performance gains that are now apparent due to the use of PDAL for IO operations. Metrics like PAI, PAD, FHD, and canopy height, are critical and fundamental measures of forest structure and are very important in many studies in ecology (not only forest ecology, but also the ecology of birds and other biological communities) and land cover dynamics. To our knowledge, their are no other Python libraries that calculate all of these metrics. As is now explained in the manuscript, having these in the Python ecosystem is important because Python use in ecological analysis is only increasing, and there are several other datasets and platforms that utilize Python, such as Google Earth Engine and the GEDI dataset which also include measures of PAI, PAD, FHD, and canopy height. That being said, we also feel that it is important that our library makes use of existing libraries like PDAL, and data formats like EPT, to enhance performance. PDAL and Entwine are incredibly powerful and important tools, and we acknowledge that our work would not be as great if it were not for many of the functions they provide. We hope that our changes to both the manuscript and the documentation of the library itself provide the credit they deserve to allow other scientists and software engineers like ourselves to build from their work to create new and more specialized tools for science and research. That said, there are also performance gains in our library. Though this is not the focus, the calculations of PAI in PyForestScan are roughly 20 times faster than the calculations of LAI (which is functionally equivalent) in existing libraries to calculate this metric in the R programming language. This has a pretty big impact when calculating PAI at very large landscape scales.
We hope that our revisions have helped to clarify the importance of this library and its contributions to science. We are planning to continue building the software to incorporate additional forest metrics -- like canopy cover, and other features such as tree segmentation.

Hi @iosefa,
thx for taking the time to adress these comments.
I am very happy to see your effort in making clear the importance of your work and I am convinced that now, the usefulness and role of this package in the Pythonic Forestry community.
I still do not understand how SfM can 3D model a whole forest to justify the use of pyforestscan, but, I agree with you that this package will work with point clouds no matter how they are generated so if there are scientists out there crazy enough to model a forest using SfM and really getting vertically distributed tie-points (and not only the top-of-the-canopy), then this package can be used!
Overall, I am happy to accept this submission as it is now and I want to congratulate you all with the initial development and the revision of it.
Congrats!
with regards,
Nick


Build mafia using GHC 8.0

The tests for this depend on x being upgraded to ghc 8.0
/cc @tmcgilchrist @thumphries @erikd-ambiata

Once 8.0.1 build is good 🌽

lgtm 🍧


Update role requirements to latest versions

What this PR does / why we need it:
Update role requirements to latest versions
(Resubmit of https://github.com/davestephens/ansible-nas/pull/251 post IC fixes.)
Which issue (if any) this PR fixes:
Fixes # n/a
Any other useful info:

:+1:


Reevaluate LBCommTable initialization

Original issue: https://charm.cs.illinois.edu/redmine/issues/1838

This is what LBCommTable currently looks like:
class LBCommTable {
    LBCommTable() {
        NewTable(initial_sz);
    }
    void NewTable(int _sz) {
        set = new LBCommData[_sz];
        state = new TableState[_sz];
        cur_sz = _sz;
        in_use = 0;
        for(int i=0; i < _sz; i++)
            state[i] = nil;
    }
    enum { initial_sz = 10000 };

I haven't dived in to how this is used but just noticed that these are probably taking up more memory than is needed.
Is this allocated once per PE, once per Node, or what? Why is it initialized to 10,000? Each of the elements in those arrays are something like 64+ Bytes in size. The arrays should likely be replaced by vectors that reserve some more conservative amount of space, rather than C-style arrays.

Original date: 2018-03-28 20:32:14

LBCommData is 88 Bytes, and TableState is 4 Bytes.
This commit cuts TableState from 4 Bytes to 1 Byte: ~~https://charm.cs.illinois.edu/gerrit/#/c/3913/~~ https://github.com/UIUC-PPL/charm/commit/80109f47baac9441fef7ef83af68001bd5192620
This commit reduces initial_sz from 10,000 to 500 which is I think reasonable? ~~https://charm.cs.illinois.edu/gerrit/#/c/3915/~~ https://github.com/UIUC-PPL/charm/commit/7ed2f13955539630691fa4853817bc5fa3816859
In all, these take the initial size of LBCommTable from 920,024 Bytes to 44,506 Bytes.
There is one LBCommTable per PE.


[Bug]:

enex2notion version
latest
What OS are you using?
Windows
OS Version / Linux distribution
Windows 10
Bug description
The end of notion notes is always garbled。

Log excerpt
No response

Could you please share any of the notes that is causing this?

Here is the notion link of my problem notes：https://www.notion.so/Docker-6528d3a0c7f141f790de3337b1f22bf1
And the enex file：https://1drv.ms/u/s!Ar1_SsPXoXZ_sy5cZqe1SAVIBGMb?e=5sbb3N
There is no any display problem in Enernote.

I looked at your enex file. It seems like Yinxiang is appending hidden block to some notes which repeats note's content but in markdown format. I'll add fix to skip those blocks during parsing.

Fixed. Please check out the new version and tell how it works for you.

I looked at your enex file. It seems like Yinxiang is appending hidden block to some notes which repeats note's content but in markdown format. I'll add fix to skip those blocks during parsing.

Hi, I found a exception in the new code, lots of notes meet "AttributeError: 'NavigableString' object has no attribute 'attrs'" in the new function _filter_yinxiang_markdown()
I think it still caused by Yinxiang's format problem, and here's my test enex file: https://1drv.ms/u/s!AhqI0UmA43o2g8hZKNWYNALG7kTFbg?e=thad6w
sorry the content is in Chinese.

@Ma-hy Fixed, thank you for reporting it. Check out the new version.

Amazing thanks! It works great!


Use correct path for submission >_<

@bjorncs please review and merge.

You should consider having the signature verifying filter assigning a principal to the request. This will simplify the controller api code and enrich the access log with information on the remote identity.


Confirm Email - Add image

Add image to brighten the page up - Janine suggested the checklist graphic from Craig.
Perhaps in orange

This is irrelevant now isn't it? We're not collecting subscribers to anything!

Closing due to inactivity


Find a way to not duplicate hyperscript typings in every package

See: https://github.com/prezly/slate/commit/ab18120b9113971b6bd36a0537809217bfc8f0ea#diff-7717d77c7fc8a9c5df0cf8c6096f5e4ad73a25dfab82ae0988c6a26a3d65ba32R11-R13
Apply this patch:
diff --git a/packages/slate-commons/src/jsx.ts b/packages/slate-commons/src/jsx.ts
index 1d88835..55d52c0 100644
--- a/packages/slate-commons/src/jsx.ts
+++ b/packages/slate-commons/src/jsx.ts
@@ -8,54 +8,6 @@ import { INLINE_ELEMENT, INLINE_VOID_ELEMENT, VOID_ELEMENT } from './test-utils'

 declare global {
     namespace JSX {
-        // This is copied from "packages/slate-hyperscript/src/index.ts"
-        // TODO: find a way to not have to copy it and still have type hinting
-        // when using hyperscript.
-        // See: https://github.com/prezly/slate/issues/6
-        interface IntrinsicElements {
-            anchor:
-                | {
-                      offset?: never;
-                      path?: never;
-                  }
-                | {
-                      offset: number;
-                      path: number[];
-                  };
-            cursor: {
-                children?: never;
-            };
-            editor: {
-                children?: ReactNode;
-            };
-            element: {
-                [key: string]: any;
-                children?: ReactNode;
-                type: string;
-            };
-            focus:
-                | {
-                      offset?: never;
-                      path?: never;
-                  }
-                | {
-                      offset: number;
-                      path: number[];
-                  };
-            fragment: {
-                children?: ReactNode;
-            };
-            selection: {
-                children?: ReactNode;
-            };
-            // using 'h-text' instead of 'text' to avoid collision with React typings, see:
-            // https://github.com/DefinitelyTyped/DefinitelyTyped/blob/0182cd9094aa081558a3c4bfc970bbdfb71d891d/types/react/index.d.ts#L3136
-            'h-text': {
-                [key: string]: any; // allow marks
-                children?: ReactNode;
-            };
-        }
-
         interface IntrinsicElements {
             'h-inline-element': {
                 children?: ReactNode;

And you're going to get these errors in *.test.tsx files:

Property 'editor' does not exist on type 'JSX.IntrinsicElements'.
Property 'h-text' does not exist on type 'JSX.IntrinsicElements'.
etc.

The goal is to fix it without having to duplicate the common IntrinsicElements definitions.

Now this affects @prezly/slate-lists package as well.

Closing this for now. I don't see slight duplication as a big problem here.


add nattawatt.com krub!!

On pc :

On mobile:

@RealNattawattHongthong I missed this PR, I'm sorry for the delay. Welcome to the webring krub!


Date only added to newest release

We use this to generate updated changelogs for every release.
When the file is generated, it only puts the release date on the newest tag. So with each new release, it "removes" the date from the previous release in the changelog.

That does not seem to happen for me. Care to supply some more details about how to reproduce it?

@jdforsythe if it is for an open source project, it would be really helpful if you could point us to the changelog with the problem :-)

Closing due to inactivity.


Add Harry Wolff

Please fix conflict

Competitive Programming And Interview Preparation
[take U forward] (https://www.youtube.com/channel/UCJskGeByzRRSvmOyZOz61ig/videos)


Cheat unloading when Slider int is to big

I dont know if its because i changed some things in the slider, but when i create a slider that goes from 0 to 1000 and i change the value to 0 in the slider the cheat unloads itself, i also cant unload it with the Detach function when the max value is 1000.
EDIT: i just realised that the whole cheat bugs out, every other slider doesnt work anymore, and the slider with the max value only works when on max

Weird thing, ill test that out later on. Possibly will rebuild menu schema so its easier to use anyway.

Closing, after alot of testing couldn't make it crash.
Open new issue if it will appear again.


#397: Added playgrounds to doc site

A few other minor updates other than the title

Removed the Rickroll page - It's a bit unprofessional, I'm guessing it was kept from the internal site
Fixed some class properties which should have been className there might be more though
Fixed spelling of "GlobalForms" to "Global Forms"
Added required properties to both playgrounds as I'm sure that's a common request so figured it's good to add it in the playground

Some things that I think some additional guidance would be good

I didn't find contributing documentation anywhere so I just guessed what I'm supposed to do

Some things I think need to be investigated

The build:docs script fails on windows because rm doesn't exist. I've found rimraf to be useful for cross platformizing this. Not sure if the policy of this repo is "no windows" but it's a simple fix though I'm sure this isn't the only cross platform issue
Your lint-staged script runs prettier on all files including your generated doc pages. I had to work around this by rebuilding the doc site and doing a git commit --amend --no-edit which probably isn't the best solution. Not sure if this was intentional though so I didn't create a ticket
Styles seem to be a bit broken - I created #398 with information

A few other minor updates other than the title

I have had users laugh a lot about the rick roll so im inclined to keep it as it seems to brighten peoples day
Awesome thanks!
Awesome thanks!
Please if you are going to add playgrounds back, use the new sandbox tool ( see example on first page )

Some things that I think some additional guidance would be good

I will add

Some things I think need to be investigated

😱 you are using windows!?!?!?!? :trollface:
100% agree I need to ignore docs for linter
Styles are not broken, there are no styles for checkboxes and radios 😁 because it sucks to style them. ( remember this does not use our actual tesla styles )

A few other minor updates other than the title

DM about this
I didn't see the sandbox there, can definitely use that instead of the custom playground code

Some things I think need to be investigated

Depends what machine, I use linux, osx, and windows. I do this to lower barrier of entry for people attempting to contribute to repos
Leaving that discussion for the currently open ticket (no further updates here)


Data Pipeline Format

Right now there are a couple of quirks with the way that result data in formatted through the data pipeline. The biggest issue for us right now is the use of MarshalIdent on the JSON. I see that it was used in the past for some sort of Kafka Connector, but the result leaves us with JSON where each element begins on a new line with a prefix. This breaks a lot of data processing applications that expect JSON elements to be newline delimited.
A second quirk I noticed is that the JSON message frame saves the payload as a string of escaped JSON. I suspect this has something to do with the encryption option for Kafka? However, when things are not encrypted, it would be much cleaner if the all of the JSON was marshaled at once such that the payload field was simply another level of the overall JSON object as opposed to a string containing the JSON data.
I realize that these changes would amount to breaking changes in the data generated by the data pipeline, but would it be reasonable to add some sort of configuration option(s) to allow for these changes? This is something that I could address ASAP if we can figure out a way to cleanly handle this.

I think it's safe to change from MarshalIdent to MarshalI, no blockers.
For JSON message frame, we can add a field, for example, payload_raw_json with type json.RawMessage, and then env configuration to pick which field to use, what do you think?

Related to https://github.com/checkr/flagr/issues/203

Sounds like a good solution, thanks! I will get a PR put together.

I’m also working on a refactoring PR including this issue now, if you have time, I can use your review.

@crberube #233

Awesome, I will take a look.


Crash cause by the mod

Reading the crash report I saw it is related to this mod, although I don't quite understand what it is.
"Caused by: org.spongepowered.asm.mixin.injection.throwables.InjectionError: Critical injection failure: Constant modifier method modifyFogEnd(F)F in scorch.mixins.json:BackgroundRendererMixin failed injection check, (0/1) succeeded. Scanned 1 target(s). Using refmap scorch-refmap.json"
Here's the full crash report:
---- Minecraft Crash Report ----
// I bet Cylons wouldn't have this problem.
Time: 9/7/21, 2:10 PM
Description: Unexpected error
org.spongepowered.asm.mixin.transformer.throwables.MixinTransformerError: An unexpected critical error was encountered
at org.spongepowered.asm.mixin.transformer.MixinProcessor.applyMixins(MixinProcessor.java:363)
at org.spongepowered.asm.mixin.transformer.MixinTransformer.transformClass(MixinTransformer.java:208)
at org.spongepowered.asm.mixin.transformer.MixinTransformer.transformClassBytes(MixinTransformer.java:178)
at org.spongepowered.asm.mixin.transformer.FabricMixinTransformerProxy.transformClassBytes(FabricMixinTransformerProxy.java:23)
at net.fabricmc.loader.launch.knot.KnotClassDelegate.getPostMixinClassByteArray(KnotClassDelegate.java:162)
at net.fabricmc.loader.launch.knot.KnotClassLoader.loadClass(KnotClassLoader.java:154)
at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:519)
at net.minecraft.class_310.method_1523(class_310.java:1103)
at net.minecraft.class_310.method_1514(class_310.java:728)
at net.minecraft.client.main.Main.main(Main.java:217)
at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:78)
at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.base/java.lang.reflect.Method.invoke(Method.java:567)
at net.fabricmc.loader.game.MinecraftGameProvider.launch(MinecraftGameProvider.java:234)
at net.fabricmc.loader.launch.knot.Knot.launch(Knot.java:153)
at net.fabricmc.loader.launch.knot.KnotClient.main(KnotClient.java:28)
Caused by: org.spongepowered.asm.mixin.injection.throwables.InjectionError: Critical injection failure: Constant modifier method modifyFogEnd(F)F in scorch.mixins.json:BackgroundRendererMixin failed injection check, (0/1) succeeded. Scanned 1 target(s). Using refmap scorch-refmap.json
at org.spongepowered.asm.mixin.injection.struct.InjectionInfo.postInject(InjectionInfo.java:408)
at org.spongepowered.asm.mixin.transformer.MixinTargetContext.applyInjections(MixinTargetContext.java:1291)
at org.spongepowered.asm.mixin.transformer.MixinApplicatorStandard.applyInjections(MixinApplicatorStandard.java:1042)
at org.spongepowered.asm.mixin.transformer.MixinApplicatorStandard.applyMixin(MixinApplicatorStandard.java:395)
at org.spongepowered.asm.mixin.transformer.MixinApplicatorStandard.apply(MixinApplicatorStandard.java:320)
at org.spongepowered.asm.mixin.transformer.TargetClassContext.applyMixins(TargetClassContext.java:345)
at org.spongepowered.asm.mixin.transformer.MixinProcessor.applyMixins(MixinProcessor.java:569)
at org.spongepowered.asm.mixin.transformer.MixinProcessor.applyMixins(MixinProcessor.java:351)
... 16 more
A detailed walkthrough of the error, its code path and all known details is as follows:
-- Head --
Thread: Render thread
Stacktrace:
at org.spongepowered.asm.mixin.transformer.MixinProcessor.applyMixins(MixinProcessor.java:363)
at org.spongepowered.asm.mixin.transformer.MixinTransformer.transformClass(MixinTransformer.java:208)
at org.spongepowered.asm.mixin.transformer.MixinTransformer.transformClassBytes(MixinTransformer.java:178)
at org.spongepowered.asm.mixin.transformer.FabricMixinTransformerProxy.transformClassBytes(FabricMixinTransformerProxy.java:23)
at net.fabricmc.loader.launch.knot.KnotClassDelegate.getPostMixinClassByteArray(KnotClassDelegate.java:162)
at net.fabricmc.loader.launch.knot.KnotClassLoader.loadClass(KnotClassLoader.java:154)
-- Last reload --
Details:
Reload number: 1
Reload reason: initial
Finished: No
Packs: Default, Fabric Mods
Stacktrace:
at net.minecraft.class_6360.method_36565(class_6360.java:49)
at net.minecraft.class_310.method_1587(class_310.java:2406)
at net.minecraft.class_310.method_1514(class_310.java:752)
at net.minecraft.client.main.Main.main(Main.java:217)
at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:78)
at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.base/java.lang.reflect.Method.invoke(Method.java:567)
at net.fabricmc.loader.game.MinecraftGameProvider.launch(MinecraftGameProvider.java:234)
at net.fabricmc.loader.launch.knot.Knot.launch(Knot.java:153)
at net.fabricmc.loader.launch.knot.KnotClient.main(KnotClient.java:28)

Thanks for the report.
I can't seem to reproduce this. Can you please let me know:

what version of Fabric you're using
if you're using Minecraft 1.17 or 1.17.1
what other mods you have installed

Thanks for the report.
I can't seem to reproduce this. Can you please let me know:

what version of Fabric you're using
if you're using Minecraft 1.17 or 1.17.1
what other mods you have installed

I'm using Fabric 0.11.6 for Minecraft 1.17.1
Here's the list of the mods I'm using
Additional Additions 2.1.2
Adorn 2.1.4
AdvancementPlaques 1.4.0
Appleskin 2.1.3
Architectury 2.5.27
Artificial Foliage 1.9
Awoken World 1.0.1
Balm 1.3.0
Better Copper 1.0.0
Better Third Person 1.5.0
Carrier 1.8.0
Cave enabler 1.0.0
Charm 3.3.2
cloth-api 2.0.54
cloth-config 5.0.38
Consistency Plus 0.4.0
Controlling 1.2.0
Couplings 1.5.1
Crafting Tweaks 13.0.0
Doggo mod 1.0.2
Earth2Java 1.7.3
Ext Shapes 1.2.5
Fabric API 0.40.0
fabric language kotlin 1.6.4 + kotlin.1.5.30
Voxel Map 1.10.15
Flytre Lib 1.3.7
Greater Eye 1.2.9
Illuminations 1.7
Immersive Portals 0.26
Improved Stations 2.0.7
Inmis 2.3.2
Inventorio 1.6.2
Levelz 1.0.5
Luminous Wool 1.1.1
ModMenu 2.0.10
Mouse Wheelie 1.7.3
Optifabric 1.11.20
Optifine 1.17.1 HD U G9
Overgrown Blocks 1.3
Paintings+ <IP_ADDRESS>
Physics Mod 2.5.5
Repawnable Pets 1.17-3
This Rocks 1.4.0
REI 6.0.279 Alpha
Salutem 1.2.1
Sentimentality 3 1.3.2
Skylor Lib 1.0.3
Stoneholm 1.3
TeenyCoal 1.0.0
The Graveyard 1.2
Villager Names 2.0.0
WhereIsIt 1.13.5
Wraith Waystones 2.0.4

Cheers! This list helped me identify the problem.
When I saw you had Optifabric installed I had a feeling it would cause compatibility issues, which is exactly the case. I'll look into this and see if there's anything I can do on my end that will help ensure they're compatible.

The crash should now be fixed for Version 1.1.2. However, having OptiFabric installed will automatically disable the reduced fog feature of the mod in order to prevent the crash. This will be the case until I figure out how to make a BackgroundRenderer mixin without Optifine interfering with it.

Amazing! Thank you so much, I absolutely loved the mod and I can't wait to finally try it out.


[WIP] k6n10f DSP behavioral model

This PR adds behavioral model of type 1 DSP. Based on https://github.com/SymbiFlow/yosys-symbiflow-plugins/pull/226 which has to be merged first.
This is still work in progress.

There are few observation with respect to the DSP block instantiation in dsp_map.v file.
There are few port mismatch:

inputs unsigned_a_i & unsigned_b_i on the dsp_t1_xxx is not connected. I see that signed and unsigned logic control is in the dsp_map.v file but that logic is already part of the DSP IP block
Input load_acc_i on the dsp_t1_xxx is not connected
output_select_i is 3 bit vector signal ([2:0]) but in dsp_map.v its a single bit scalar signal
shift_right_iis 6 bit vector signal ([5:0]) but in dsp_map.v its a single bit scalar signal
parameters NBITS_ACC, NBITS_A, NBITS_B & NBITS_Z need to be passed into dsp_t1_xxx
what happens to clock and reset signals?

@tpagarani DSPs model were updated according to the most recent examples. I believe it is ready for final review.

@rakeshm75 please help review

Here are few observations:
Currently, I see that the DSP model (dsp_t1_sim) is under dsp_t1_20x18x64 & dsp_t1_10x9x32.
Ideally the dsp model should be under the QL_DSP2 module:
module QL_DSP2
.
.
.
dsp_t1_sim (
.
.
);
endmodule
And QL_DSP2 should be port mapped under dsp_t1_20x18x64 & dsp_t1_10x9x32:
module dsp_t1_20x18x64
.
.
.
QL_DSP2 (
.
.
);
endmodule
module dsp_t1_10x9x32
.
.
.
QL_DSP2 (
.
.
);
endmodule

In the dsp model (dsp_t1_sim) the shift_d2 assignment is wrong:
On line 825 current code is as follows:
wire [5:0] shift_d2 = output_select_i[1] ? r_shift_d2 : shift_right_i;
it should be:
wire [5:0] shift_d2 = output_select_i[1] ? shift_d1 : r_shift_d2;

@rakeshm75 thank you for your comments. I changed the structure of DSP modules as you suggested, updated shift_d2 assignment and rebased the code onto newest master resolving the conflicts.

Looks good to me, approved.

Ok, merging.


Buffer in heat infrastructure

It would be nice if the user can add a heat buffer in the heat infrastructure.

It would be nice if the user can add a heat buffer in the heat infrastructure.

Do you mean that this buffer should represent the buffer-size of the heat infra?

Yes!

Transfering the issue from me to @MarjoleinSchwachofer


jasper-deploy/ARCH=x86_64,NAME=jasper,OS=u1404,SITE=generic,VERSION=1.900.1 #15 failed

Build 'jasper-deploy/ARCH=x86_64,NAME=jasper,OS=u1404,SITE=generic,VERSION=1.900.1' is failing!
Last 50 lines of build output:
Started by upstream project "jasper-deploy" build number 15
originally caused by:
 Started by GitHub push by brucellino
[EnvInject] - Loading node environment variables.
Building remotely on local-a3547efefa61 (x86_64 u1404) in workspace /home/jenkins/workspace/jasper-deploy/ARCH/x86_64/NAME/jasper/OS/u1404/SITE/generic/VERSION/1.900.1
Cloning the remote Git repository
Cloning repository https://github.com/SouthAfricaDigitalScience/jasper-deploy
 > git init /home/jenkins/workspace/jasper-deploy/ARCH/x86_64/NAME/jasper/OS/u1404/SITE/generic/VERSION/1.900.1 # timeout=10
Fetching upstream changes from https://github.com/SouthAfricaDigitalScience/jasper-deploy
 > git --version # timeout=10
using GIT_ASKPASS to set credentials Jenkins Github token
 > git fetch --tags --progress https://github.com/SouthAfricaDigitalScience/jasper-deploy +refs/heads/*:refs/remotes/origin/*
 > git config remote.origin.url https://github.com/SouthAfricaDigitalScience/jasper-deploy # timeout=10
 > git config --add remote.origin.fetch +refs/heads/*:refs/remotes/origin/* # timeout=10
 > git config remote.origin.url https://github.com/SouthAfricaDigitalScience/jasper-deploy # timeout=10
Fetching upstream changes from https://github.com/SouthAfricaDigitalScience/jasper-deploy
using GIT_ASKPASS to set credentials Jenkins Github token
 > git fetch --tags --progress https://github.com/SouthAfricaDigitalScience/jasper-deploy +refs/heads/*:refs/remotes/origin/*
Checking out Revision d25cede87c86b595fc99892d056e1cbc3ac3e967 (refs/remotes/origin/master)
 > git config core.sparsecheckout # timeout=10
 > git checkout -f d25cede87c86b595fc99892d056e1cbc3ac3e967
 > git rev-list f5f108bd1bf1f9cb720e6115cb092df11d668d55 # timeout=10
Run condition [Current build status] enabling prebuild for step [Execute shell]
Run condition [Current build status] enabling prebuild for step [Execute shell]
[Set GitHub commit status (universal)] PENDING on repos [GHRepository@327408e8[description=A repo to contain the scripts and tests for jasper,homepage=<null>,name=jasper-deploy,license=<null>,fork=false,size=19,milestones={},language=Shell,commits={},source=<null>,parent=<null>,url=https://api.github.com/repos/SouthAfricaDigitalScience/jasper-deploy,id=44260489]] (sha:d25cede) with context:jasper-deploy/ARCH=x86_64,NAME=jasper,OS=u1404,SITE=generic,VERSION=1.900.1
Setting commit status on GitHub for https://github.com/SouthAfricaDigitalScience/jasper-deploy/commit/d25cede87c86b595fc99892d056e1cbc3ac3e967
[1.900.1] $ /bin/sh -xe /tmp/hudson6912870940607387850.sh
+ ./build.sh
REPO_DIR is
/data/artefacts/generic/u1404/x86_64/jasper/1.900.1
SRC_DIR is
/data/src/jasper/1.900.1
WORKSPACE is
/home/jenkins/workspace/jasper-deploy/ARCH/x86_64/NAME/jasper/OS/u1404/SITE/generic/VERSION/1.900.1
SOFT_DIR is
/data/ci-build/generic/u1404/x86_64/jasper/1.900.1
continuing from previous builds, using source at  /data/src/jasper/1.900.1/jasper-1.900.1.tar.gz
/data/src/jasper/1.900.1/jasper-1.900.1.tar.gz: gzip compressed data, from Unix
CMake Error: The source directory "/home/jenkins/workspace/jasper-deploy/ARCH/x86_64/NAME/jasper/OS/u1404/SITE/generic/VERSION/1.900.1/jasper-version-1.900.1" does not appear to contain CMakeLists.txt.
Specify --help for usage, or press the help button on the CMake GUI.
Build step 'Execute shell' marked build as failure

Changes since last successful build:

[Bruce Becker] d25cede87c86b595fc99892d056e1cbc3ac3e967 - using cmake now

View full output

Build was fixed!


Description for a term used in the documentation is missing

Problem description
In API documentation, there is a line under section Authentication which says "Security access keys such as OAuth 2.0 3-legged Access Tokens used by Client applications to invoke this API with dedicated scope. Client must use network based authentication methods to use this service."
The term network based authentication is not explained anywhere AFAIK and might not be known to all Camara participants.  If it is explained somewhere, and I have overseen this, kindly provide a link in the issue comment and I can gladly close this issue :)
Expected action
Details about the missing term should be added to the document. This term should also piggyback into authN-authZ doc.
Additional context

Hello @shilpa-padgaonkar,
there are some changes pending to be applied to this repo. This document (along all Mobile Connect related documents and definitions) must be removed.
We already included the documentation in the API Spec, to deprecate this one;but you're absolutely right about it. We must explain the term. We'll open a PR in order to add it to the API Spec.
Thank you for the heads up.

@monamok : Thank you very much for your feedback. Could you kindly piggyback your PR change also here -https://github.com/camaraproject/IdentityAndConsentManagement/issues/45

@bigludo7 @DT-DawidWroblewski
I think we can close this issue since it was already included into the documentation and merged

I'm concerned here as the Network Authentication description in camaraproject/IdentityAndConsentManagement#55 doesn't give the developer a clear idea/solution of how network auth works and I see it challenging for our community to unify this.

all clear


Added myself as contributor

Just a note: we have an organisation called "3 Sided Cube" and an account called "3sidedcube"

Awesome!
Please ping us through Intercom and we'll provide the coupon for you ;)
Thanks for your contribution! 🚀


Message redelivery delay with exponential back-off

Is your feature request related to a problem? Please describe.
I would like to leverage re-deliveries with exponential back-off when my consumer nacks a message. Retries with exponential back-off is often preferred over simple retries when encountering transient errors to give an immediate chance at succeeding on a retry, but to avoid overwhelming a service if it is failing a lot of messages.
Describe the solution you'd like
Allow configuration of a retry strategy (fixed interval, exponential back-off) when configuring redelivery delay.
Describe alternatives you've considered
I think that this could be hacked together in the consumer code, by checking the delivery count and scheduling one-off redeliveries based on that, but it would be a much more fragile solution.

@klevy-toast did you checkout https://pulsar.apache.org/docs/en/concepts-messaging/#retry-letter-topic?
https://github.com/apache/pulsar/wiki/PIP-58-%3A-Support-Consumers--Set-Custom-Retry-Delay

@klevy-toast did you checkout https://pulsar.apache.org/docs/en/concepts-messaging/#retry-letter-topic?
https://github.com/apache/pulsar/wiki/PIP-58-%3A-Support-Consumers--Set-Custom-Retry-Delay

Thanks @sijie -- I had not seen the retry-letter-topic. I am having a little trouble picture how it could be utilized for exponential back-off -- would I want to configure the consumer to have a single immediate, retry, and then the retry topic to have a higher delay? How would that delay be configured?
The PIP-58 proposal looks more similar to what I am imagining, without the use of additional topic. It would be even nicer to have pre-configured retry "strategies" (I believe that the AWS Java SDK has this concept), but a reconsumeLater would probably be enough to manually implement the back-off logic.

Thanks @sijie -- I had not seen the retry-letter-topic. I am having a little trouble picture how it could be utilized for exponential back-off -- would I want to configure the consumer to have a single immediate, retry, and then the retry topic to have a higher delay? How would that delay be configured?
The PIP-58 proposal looks more similar to what I am imagining, without the use of additional topic. It would be even nicer to have pre-configured retry "strategies" (I believe that the AWS Java SDK has this concept), but a reconsumeLater would probably be enough to manually implement the back-off logic.

@codelipenghui Can you take a look at this?

@codelipenghui Can you take a look at this?

@klevy-toast You are right, the PIP-58 is e enough to manually implement the back-off logic. It's easy to support exponential back-off for the redelivery since we have exposed the redelivery count to the client-side.

@klevy-toast You are right, the PIP-58 is e enough to manually implement the back-off logic. It's easy to support exponential back-off for the redelivery since we have exposed the redelivery count to the client-side.

@klevy-toast You are right, the PIP-58 is e enough to manually implement the back-off logic. It's easy to support exponential back-off for the redelivery since we have exposed the redelivery count to the client-side.

@codelipenghui would it be reasonable to create a retry strategy as I described, so that many pulsar users could quickly utilize exponential back-off without re-implementing the logic every time?

@klevy-toast Yes, It seems reasonable to me. Are you interested in pushing a PR for this issue?

@codelipenghui sure, although it may take me a while to find the spare cycles.

Hi all!
We are also interested in redelivery delay with exponential back-off feature, and while investigating possible ways to implement it I got a bit confused by different existing options and mechanisms. In particular - what is the relation between reconsumeLater api and nacking? Let's pretend I just want fixed retry delay. Is there any difference between
a. Configuring NackRedeliveryDelay option and sending Nack
b. Using reconsumeLater with same NackRedeliveryDelay
One more follow-up question. If I call reconsumeLater, do I need to send Ack after it? (in some sense I processed message to some result - rescheduling) Nack? Nothing?

The recosumeLater can works while the client crashes, if use the nack delay and the client crashes at a time, the message will retry immediately.

@codelipenghui Thank you for reply. One more point regarding the issue.

It's easy to support exponential back-off for the redelivery since we have exposed the redelivery count to the client-side.

While this is true for Nack case, which really increments the counter, reconsumeLater flow actually Ack original message under the hood and uses internal map structure to track the counter. For me redelivery count exposed by api was always 0 while testing reconsumeLater. I was reading real counter from message properties map by SysPropertyReconsumeTimes (Go client, similar property exists in Java client) key.

close by https://github.com/apache/pulsar/pull/12566


Decide which CSS framework to use

I'm thinking of using either Bootstrap (https://getbootstrap.com/) or Materialize (https://materializecss.com/).
Which one is better? Are there any other good options?

This might be good for the sign-in page: https://getbootstrap.com/docs/4.1/examples/sign-in/

This theme looks good, too. I'm wondering if I should use it: http://themes.getbootstrap.com/preview/?theme_id=1714&show_new=

Looks like there's a free version of that theme, too: https://github.com/creativetimofficial/material-kit
I'm thinking of giving it a try to see how it looks.

Just did #44 for now


fix: readme dev dep flag

The correct key for Unused devDependencies is devDependencies (not dependencies)

Thanks, but duplicate of #214. Sorry, still need to clarify that.


fix: remove module from status line

fixes #2900

Ugh, I had this locally, looks like the second git push didn't actually work because of a transient failure in the pre-push hook, and I didn't notice. Proper fix is:  https://github.com/TBD54566975/ftl/pull/2916


Attachments bug(s)?

Found during user testing Mar 29. Recording available.
Error
pandas.core.frame.DataFrame object has no element ‘URL’ Filename: next_steps_inspection_request_letter.docx

Full Error: MADE_ UpToCode.pdf

turn on skip undefined: True in attachment block

Is this the same error as above @nonprofittechy? User testing on 3/30 could download docs on review but could not sign and download because hit this error.

Demand letter did not show on download when only one in the flow. Only Housing Conditions Report did

Demand letter did not show on download when only one in the flow. Only Housing Conditions Report did

Happened again on 4/11

Demand letter did not show on download when only one in the flow. Only Housing Conditions Report did

Happened again on 4/11

seems demand letter is not enabled

Is this the same error as above @nonprofittechy? User testing on 3/30 could download docs on review but could not sign and download because hit this error.

Replicated this error again 4/12

Unclear to me why affidavitofindigency_attachment._is_docx is not returning False since it is a PDF: https://github.com/SuffolkLITLab/docassemble-AssemblyLine/blob/6d337b5869352a26b2ae27bde7bfef0a241d2a89/docassemble/AssemblyLine/al_document.py#L775-L782
@nonprofittechy This is currently preventing the fee waiver download in UpToCode.

@nonprofittechy
To replicate:
go down any path to file something in court and then say you want to see if you qualify for fee waiver

Should be closed by https://github.com/SuffolkLITLab/docassemble-AssemblyLine/pull/684

Is this the same error as above @nonprofittechy? User testing on 3/30 could download docs on review but could not sign and download because hit this error.

Replicated this error again 4/12

Unclear to me why affidavitofindigency_attachment._is_docx is not returning False since it is a PDF: https://github.com/SuffolkLITLab/docassemble-AssemblyLine/blob/6d337b5869352a26b2ae27bde7bfef0a241d2a89/docassemble/AssemblyLine/al_document.py#L775-L782
@nonprofittechy This is currently preventing the fee waiver download in UpToCode.

Resolved.

Demand letter did not show on download when only one in the flow. Only Housing Conditions Report did

Happened again on 4/11

seems demand letter is not enabled

Resolved.

@nonprofittechy any reason you reopened this issue? I just retested the two I saw and they are good now.

Hasn't been merged with Assembly Line yet


Types: Allow using datasource types in scenes

Hello,
We're testing Grafana Scenes and we're finding incredibly useful. We've gotten to the point of building some more complex queries, and it would be interesting to have access to the type definitions for queries for the different datasources, at least for the ones that are defined by default in Grafana. However, they don't seem to be exported anywhere. Would this be something easy/valuable to implement in any of the Grafana TypeScript packages, or is it better that we copy these definitions into our code?
Thanks!

Hi @gjulianm  - those types are available in grafana/schema, i.e. for Prometheus data source @grafana/schema/dist/esm/raw/composable/prometheus/dataquery/x/PrometheusDataQuery_types.gen.
But keep in mind these APIs (imports from grafana/schema/dist....) are not public and not intended to use outside of the core Grafana libraries as of now.
Long term we want to introduce query builders similar to the PanelBuilders API.
We don't have an exact timeline for this work, but we would be more than happy to welcome contributions to the library if you are thinking about building something similar.

Thanks, that works! I'm ok with those definitions not being public, we're just using them for type checking mostly so even if they go away it's not a big problem.
Regarding the query builders, that would be definitely helpful. Right now we're doing very ad-hoc code for our databases, but if you have an issue/branch/docs where you're tracking that work and the architecture style you're following we could contribute with our code.

@gjulianm We are thinking about following the builder pattern, exactly the same way we built PanelBuilders.
We would welcome contributions to query builders with <3


Added custom dismissal feature

Hi @omaralbeik. Added a feature to the to-do list.

It would certainly be the right approach. It's a good idea @omaralbeik. I'll edit the code and send it soon 🙃


Simplify and clean up data skipping logic a bit

Several cleanups to the data skipping logic (partly inspired by recently added parquet stats skipping logic):

Reorder Expression match arms to match declaration order
Add an inverted flag to the data skipping expression logic, which allows to more easily push NOT down

Remove as_inverted_data_skipping_predicate (no longer needed)
Collapse the four {tight, wide} x {null, not null} helper methods into just tight and wide helpers

Add support for boolean literals and columns

They don't necessarily have good skipping power, but defaulting them to NULL can disable skipping
i.e. FALSE OR <expr> and <col> OR <expr> no longer blocks data skipping on <expr>

No longer create new expressions that need to be passed to as_data_skipping_predicate (e.g. Equal comparison)
Make NotEqual data skipping logic a bit easier to grok

Superseded by https://github.com/delta-io/delta-kernel-rs/pull/420


fixed issue Updating the README.md file in the default branch #7744

Thanks for contributing to Wagtail! 🎉
Before submitting, please review the contributor guidelines https://docs.wagtail.io/en/latest/contributing/index.html and check the following:

Do the tests still pass? (https://docs.wagtail.io/en/latest/contributing/developing.html#testing) -  Not needed for the README
Does the code comply with the style guide? (Run make lint from the Wagtail root) Yes
For Python changes: Have you added tests to cover the new/fixed behaviour?  -  Not needed for the README
For front-end changes: Did you test on all of [Wagtail’s supported environments] (https://docs.wagtail.io/en/latest/contributing/developing.html#browser-and-device-support)? -  Not needed for the README

Please list the exact browser and operating system versions you tested. Chrome and Windows 11
Please list which assistive technologies you tested.

For new features: Has the documentation been updated accordingly? -  Not needed for the README

Merged in via 66237d09e758aa605523c6e1494ea66546c19926

@FahimFBA thanks for this, we will merge this in soon.
For smaller docs/readme fixes like this we do not add a changelog but we would love to add your name to the contributors list.
I will put you down as Fahim Bin Amin but please advise if you want your name listed differently.

Please list my name as Md. Fahim Bin Amin because that is my full name. Thanks!

@FahimFBA done - https://github.com/wagtail/wagtail/commit/75bf48d9f7cbabbada863beb700e89387da76327


[tcgc] client related features

resolve: https://github.com/Azure/typespec-azure/issues/1060
resolve: https://github.com/Azure/typespec-azure/issues/963

All changed packages have been documented.

:white_check_mark: @azure-tools/typespec-client-generator-core

Show changes
@azure-tools/typespec-client-generator-core - feature ✏

add parent client info to SdkClientType

You can try these changes here

🛝 Playground
🌐 Website
📚 Next docs

@haolingdong-msft @archerzz @chunyu3 please review and check if it is enough for your language.
also, cc: @iscai-msft

Thanks for the fix. Having parent should be enough for Java's current need. Our need for now is just to build the sub client's name


Incomplete handling of telephone numbers from XTN fields

Incomplete handling of telephone numbers from XTN fields
Converter does not handle XTN fields built with HL7 v2.3, v2.3.1, or v2.4 and may not handle all implementations of HL7 v2.5+
Current Behavior
Currently, a phone number will be populated in two circumstances:

If XTN.7: Local Number and XTN.12: Unformatted Telephone Number are both null, the value is populated by XTN.1: Telephone Number.
If XTN.3: Telecommunication Equipment Type is not x.400 or Internet, the value is populated by XTN.12: Unformatted Telephone Number.

Why This Is Incomplete

This works for HL7 v2.1 and v2.2, but only works for v2.3+ if the optional XTN.7 field and conditional XTN.12 field are left empty by the sender.
This only works if the conditional XTN.12 field is populated. This field is not present in v2.3, v2.3.1, or v2.4. Furthermore, because XTN.12 is conditional, the sending system may choose not to populate it when the telecom info can be parsed properly.

Possible Suggestions

If XTN.12.Value empty, use XTN.1.Value
Construct full telephone number from XTN.5: Country Code, XTN.6: Area/city Code, XTN.7: Local Number, XTN.8: Extension

Hi @cksavia , thanks for your submission! These templates are based off HL7 v2.8, other versions will require some customization. However, we've added your suggestion to our backlog for consideration. Thanks!


Remove crown, crest and New Transport font

The design history isn't on a GOV.UK domain so should not use the crown and crest logos, nor the New Transport font.

This has come up a few times. I was wondering if we could use the patterns that the Home Office has created, which are designed for internal tools: https://design.homeoffice.gov.uk. I did briefly look at this, forget what issues prevented me from continuing.

This has come up a few times. I was wondering if we could use the patterns that the Home Office has created, which are designed for internal tools: https://design.homeoffice.gov.uk. I did briefly look at this, forget what issues prevented me from continuing.

(But yes, in the interim remove the crown and font)

(But yes, in the interim remove the crown and font)

Let's get it hosted on .education.gov.uk

Let's get it hosted on .education.gov.uk

We can close this now as it's hosted on a *.gov.uk domain... 🙌

Sweat URL! (Though now have to update my UX London slides…)


go dependencies: bump protobuf library

Manual merge to fix https://github.com/istio/istio/issues/37788

@stewartbutler: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

release-notes_istio_release-1.11
41d55771531b0d83ae36f3ec7fec26fc14abd033
link
true
/test release-notes_istio_release-1.11

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/retest


Add clip container

useful for ui display cliped childrens

I would probably instead expose the clip api propery to all controls instead
On Jun 28, 2016 00:37, "Saniko"<EMAIL_ADDRESS>wrote:

useful for ui display cliped childrens
You can view, comment on, or merge this pull request online at:
https://github.com/godotengine/godot/pull/5455
Commit Summary

Add clip container

File Changes

M scene/gui/container.cpp
https://github.com/godotengine/godot/pull/5455/files#diff-0 (32)
M scene/gui/container.h
https://github.com/godotengine/godot/pull/5455/files#diff-1 (19)

Patch Links:

https://github.com/godotengine/godot/pull/5455.patch
https://github.com/godotengine/godot/pull/5455.diff

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/godotengine/godot/pull/5455, or mute the thread
https://github.com/notifications/unsubscribe/AF-Z25W9c2PXbPQCQ_nAyBUmc1pdkaR_ks5qQJbsgaJpZM4I_tjF
.

@reduz  this would conflict with many controls like ScrollContainer/Label/RichText/Label/Tree etc...

I was thinking of adding clip as a property in control instead, since many controls might want to clip children, like box containers, windows, etc.

Maybe something to add to #5696 then.

will add the clip property to controls I think for Godot3
On Mon, Oct 3, 2016 at 8:39 AM, Rémi Verschelde<EMAIL_ADDRESS>wrote:

Maybe something to add to #5696
https://github.com/godotengine/godot/issues/5696 then.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/godotengine/godot/pull/5455#issuecomment-251085684,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AF-Z20u1ATc80T97V-Vz673Ijs59_-nbks5qwOl2gaJpZM4I_tjF
.

The clipping property has been implemented in Control for Godot 3.0, so closing this PR as obsolete.


translateX and translateY related issues

import { StyleSheet, Pressable } from 'react-native'

import { MotiView, AnimatePresence } from 'moti'

function Shape2() {
    return (
      <MotiView
        from={{
          opacity: 0.5,
          scale:0.5,
          translateY:-200,
          translateX:200,
        }}
        animate={{
          opacity: 1,
          scale:1,
          translateY:0,
          translateX:0,
        }}

        style={styles.shape}
      />
    )
  }

export default function App() {
  const [visible, toggle] = useReducer((s) => !s, true)

  return (
    <Pressable onPress={toggle} style={styles.container}>
      <AnimatePresence>{visible && <Shape2 />}</AnimatePresence>
    </Pressable>
  )
}

const styles = StyleSheet.create({
  shape: {
    justifyContent: 'center',
    height: 250,
    width: 250,
    borderRadius: 25,
    marginRight: 10,
    backgroundColor: 'white',
  },
  container: {
    flex: 1,
    alignItems: 'center',
    justifyContent: 'center',
    flexDirection: 'row',
    backgroundColor: '#9c1aff',
  },
})

When having translateX and translateY together it acts weird, u can only see the translateY happening, it seems translateX is happening before that as a sequence and not parallely. I am not that sure but also the scale thing also freezes when u use translateX and Y with exit and all, any insight into this would be helpful

I'd have to look into this. Might be related to #74

Yeah, I noticed same. 🤦🏽♀  Using translateY and translateX... translateX works, but Y doesn't. It just jumps to its final value, 0:
    ...
    <View style={S.Login}>
      <MotiView
        style={S.logoWrapper}
        from={{
          scale: 1.5,
          translateX: (Dimensions.get('window').width - padding.md * 1.25) / 2,
          translateY: (Dimensions.get('window').height - padding.md * 8) / 2
        }}
        animate={{
          scale: 1,
          translateX: 0,
          translateY: 0
        }}
        transition={{
          type: 'timing',
          duration: 2000,
          delay: 2000
        }}>
        <Logo
          style={
            S.logo
          }
        />
      </MotiView>
    </View>
    ...

Any solutions to this yet, @nandorojo

Actually, I think using either of the CSS transform properties together will make only one of the transforms work.
I mean, if you use either of scale and translateX or scale and translateY or translateY and translateX or rotate and scale etc., only one of the properties end up animating; the others don't.

I think this is a duplicate of #76. I wonder if the object keys aren't in proper order...

I know this isn't ideal, but for now, could you use 2 moti views, and apply only one transform per component? Until I have time to look more closely at this.

Temporary solution for multiple transforms can be found here: https://github.com/nandorojo/moti/issues/85#issuecomment-895599767
TLDR: use useAnimationState instead of the from and animate props until I can investigate the proper cause of this.

Would be great if you guys could test there so I know if it's good to go.

Okay I found the cause of this. Reanimated is changing the order of the keys. It seems that the object key order is not reliable for transform.

https://github.com/software-mansion/react-native-reanimated/issues/2352
Issue there. I found the solution, though. Will be merged soon.

Fixed in 0.12.0
yarn add moti


Uom should be a LocalizedFieldContainer

It makes no sense for SI units like m or kg. But for some custom Uom's like load, unit, barril or bag we need translations.

Uom is a DescriptionContainer which allows to add language-specific description and detailedDescriptions:

Since a Uom does not have more fields than description and detailedDescription a LocalizedFieldCointainer seems to be overkill.
Note: LocalizedFieldCointainer was introduced to "localize" CrxObjects and all of its sub-classes.


Create the Upgrade Request API

https://thenewboston.com/confirmation-validator-api/upgrade-request

Working on this one today :)


Version 2.4

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

The Windows Python 2 failure is due to https://github.com/conda/conda-build/issues/188

The Python3 issue is unknown and reported to https://github.com/conda-forge/matplotlib-feedstock/issues/114


Truncate Subtitle Plugin Field

do you think that we should add three dots ?

do you think that we should add three dots ?

yess 100% i'll look at how to do that asap :) but whats the theoretical limit for author names ?

Closing this pr : it should not be merged as right now we are not planning to open the plugin store to developers. It was meant as a quick and easy fix, but since it's not part of the minimal scope (and reasons mentioned before) it should be closed. The issue will remain so we can discuss details and the best way to handle this situation.


Insert the attention mechanism in the codes to the stylegan2-ada but fail

Hello, first of all, thank you for your great work.
I just inserted the self-attention and cross-attention module to stylegan2-ada, following behind the conv1 SynthesisLayer on the 4,8,16,32 resolution. And I use the CLIP to extract txt features and the contrastive loss. However, after a few iterations, the resulting pictures became completely the same color. Could you please give me some advice on how to improve it?

@landian60 i can do a quick review of your integration code if you have a public repo or a gist

i'm actually not too sure if they also used the l2 distance attention for cross attention as well as the extra transformer blocks they appended to the clip text encoder
maybe i should make it an option to fallback to regular attention

@lucidrains Thanks for your kindness!
The results changed after a few modifications, and I will keep training to see what happens.
By the way, I am curious  why you dont't let the style codes participate in the attention process? for example, let the style codes modulate the weight of q&k on self-attention.
Tks.

glad to hear it is working!
the style codes already participate in modulating the convolutional kernels. as for the text conditioning, that is cross attended to by each image feature map token

tks! You are so nice. Waiting for your continuing work.

Hello Phil,
I have a question about training the model with cross attention.I only used clip contrastive loss and did not add any other losses. And the generative results always became the same color and the G loss was very big even to NaN. I think the reason is the model collapse. Have you encountered similar issues when training the model?
I am planning to add some losses to train the model.

@lucidrains


Dynamic addition of ion-card in ion-header does not refresh view

Ionic version:  (check one with "x")
[ ] 1.x
[x] 2.3.0
I'm submitting a ...  (check one with "x")
[x] bug report
[ ] feature request
[ ] support request => Please do not submit support requests here, use one of these channels: https://forum.ionicframework.com/ or http://ionicworldwide.herokuapp.com/
Current behavior:

Ion-Cards in ion-header that are dynamically added (in the plunker example after 2 seconds) do not refresh the view and instead overlap the ion-content. See plunker # 1.
Also if they are dynamically removed they will have header overlap. See plunker # 2.

Expected behavior:

Both of the examples should refresh the view appropriately.
Steps to reproduce:

Create 2 cards in ion-header & create 2 cards in ion-content.
Dynamically set the top card in ion-header to be removed (display:none) (after 2 second timeout).

See Plunker # 1: http://plnkr.co/edit/w3HEP4NrXuLYrO9XiqyI?p=preview

Create 2 cards in ion-header & create 2 cards in ion-content.
Dynamically set the top card in ion-header to be added (after 2 second timeout).

Plunker # 2: http://plnkr.co/edit/Opq2GHTihYs9QsItmTy6?p=preview

Demo Gif

It's worth pointing out that this only happens in the header. If I dynamically add a card in ion-content the view is refreshed: http://plnkr.co/edit/Wwwh8C6OFieJmGp9yMB3?p=preview

http://ionicframework.com/docs/api/components/content/Content/#resize
content.resize()

should be called once the size of the header changes dynamically.


Update column names or meta data "in-place" without reading in file contents

I would like to be able to do basic manipulation of parquet files stored in Azure Data Lake Storage (ADLS) Gen2 - is it possible to update ONLY the column names and/or metadata without having to recreate the file or read in all of the data?
Using the handler provided by this library https://github.com/kaaveland/pyarrowfs-adlgen2 able to connect to storage just fine to read metadata/schema, but hoping there's a way to write back (by specifying the filesystem that the aforementioned lib enables easily). Is this possible?
Looks like rename_columns is on the Table object, so data would have already been read in, and not sure about this one: https://arrow.apache.org/docs/python/generated/pyarrow.parquet.write_metadata.html?highlight=write_meta
Would appreciate any insight.

No, not really, certainly not today at the pyarrow level.  You would need to have your data and metadata in separate files or otherwise introduce some kind of padding in between them.  Changing a column name or metadata in general is likely to change the size of the metadata block.  The current reader/writer packs them together and that would clobber existing data.
In theory though, it might be possible.  I'm pretty sure (but not certain at all) the format allows for it.  Some parts of Arrow's C++ parquet library could potentially be reused but you would need to do quite a bit of novel development to get this I think.
That being said, a potentially easier approach, which would handle column names and metadata, is to simply store an authoritative schema as a metadata-only standalone file (parquet or Arrow IPC).  Then, after reading in your data, you could create a table using your authoritative schema and the column data from the file(s) you read into memory.
If you expand that concept much further you start to get into "schema evolution" and "metadata storage" concepts in something like Iceberg and so you may want to look at that project as well.

Alright thanks for the quick response.


Support custom method of gRPC HTTP endpoint

Hi!
I'm curious release plan about #4064 PR.
When I try to use enableHttpJsonTranscoding feature,
it seems armeria doesn't yet fully support custom method.
Could you let me know release plan about supporting verb suffix (#4064) ?

Hi, the PR has been worked by @hyangtack, an external contributor.
As far as I know, he spent his spare time making the feature.
So it is difficult for me to tell when it is going to release.
But I hopefully believe he could finish the PR in near future. Please stay tuned. 🙇♂


silence the dask dataframe upstream-dev errors

Some of the to_dask_dataframe tests fail on the upstream-dev CI because the behavior of pandas.DataFrame changed (see pandas-dev/pandas#38645). For now we can silence these by computing all dask arrays we pass to pandas.DataFrame.

[x] Closes #4717
[x] Passes isort . && black . && mypy . && flake8

Thanks @keewis
How should we think about changing the test code vs xfailing?
IIUC the current test code should work, but doesn't because of the pandas issue. Would we expect to revert this after pandas fixes its issue?

Thanks @keewis
How should we think about changing the test code vs xfailing?
IIUC the current test code should work, but doesn't because of the pandas issue. Would we expect to revert this after pandas fixes its issue?

How should we think about changing the test code vs xfailing?

that's a good point. I'm really not sure: in this case we don't change the behavior of the test, but in general it would probably be better to xfail.

How should we think about changing the test code vs xfailing?

that's a good point. I'm really not sure: in this case we don't change the behavior of the test, but in general it would probably be better to xfail.

It's a bug in constructing an expected dataframe. Seems OK to change it and not revert once pandas fixes its behaviour.

It's a bug in constructing an expected dataframe. Seems OK to change it and not revert once pandas fixes its behaviour.