Parent relation doesn't honor del-attribute claims

If you add a child to a permanode via either camliMember or camliPath:*, then del-attribute it, it will cease to show up in the permanode's description, but searches via the parent relation will still find it.
You can reproduce this by patching https://camlistore-review.googlesource.com/#/c/4318/ against bc5fd6ea9d1b3f3a93874225f18716643de33765, then following these steps:

Add a file to the UI.
Select the file and click "Create set with items" in the sidebar
In the resulting view, go to the permanode aspect - note the camliMember row for the file
Go to the contents aspect, select the file, then click "Remove from set" in the sidebar
Note that the item is still in the content aspect
Go back to permanode aspect and note that camliMember row is gone

The permanode aspect is reading from the description of the permanode. The contents aspect is using a search with the 'parent' relation.
You can see the raw queries and responses in the network tab of Chrome's developer tools.

Everytime I hear about del-attribute I have to think about why we can't get rid of it and do everything with delete claims instead, and it makes me sad to realize that we can't.
@bradfitz You want me to have a look at that or you got it?

For the uninitiated, can you remind why we can't use the delete claim instead?
Also, for this use case should I be using the delete claim?

I think you actually could achieve the same thing with a delete claim. But it would be more work since you'd first have to find the original claim that set the attribute you want to undo (so that you can delete said claim).
Also, if we ever get to doing claims that set multiple things atomically, then there would be cases where we can't achieve a del-attribute with a delete claim without deleting other attributes in the operation, which we certainly don't want.
And there's probably another reason that I forget.

I see. It seems like atomic updates could be implemented by actually generating n claims, and linking them together, like, roughly:
{
camliType: 'claim',
permanode: 'xyz',
attr: 'foo',
value: 'bar',
inGroup; true,
}
{
camliType: 'claim-group',
claims: ['abc', 'def', 'ghi'],  // blob refs of grouped claims
}
This way a group of changes can still be created (and later, deleted) individually ... but the indexer and other parties will know when they see it that it was meant to be part of a group, and can ignore until they see and validate the group.

That is #110 ... see comment 4 there.

Oh, that's better. So out of curiosity, is there still need for del-attribute, apart from backward compat and the convenience issue that mathieu pointed out?

Answering own question: Yes, because you could end up needing to unwind a long chain of set/add-attributes which would be error prone and expensive.

I can't reproduce the original issue. I think maybe it was a caching issue, somewhere, that is better now. I tested with both camliPath:* and camliMember attrs, by deleting them from the "Permanode" aspect and then switching to the "Contents" aspect and seeing that they are gone. Closing.


Feature: Privacy Page

Feature description
There is no Privacy Policy page in the website . When we click on the Privacy Policy in Footer it redirects us to top .
Expected Behavior
When we click on Privacy Policy in Footer it should take us to the new Page which will be Privacy Policy Page .
Video
https://github.com/SauravMukherjee44/Aec-Library-Website/assets/85991449/f538d58d-e924-4da4-868b-227418b2f695
👀 Have you spent some time to check if this issue has been raised before?

[X] I checked and didn't find similar issue

🏢 Have you read the Code of Conduct?

[X] I have read the Code of Conduct

Can you assign this issue to me under GSSOC ' 23 .


add ClientFilter to HttpReplicationClient

Connects to #1211

@elandau Based on your comment of "only allow adding filters at creation time", I did this quick spike on how that could look like: https://github.com/Netflix/eureka/compare/master...LittleBaiBai:add-additional-filters-on-creation.
I haven't tested this yet. Do you think this is on the right (or better) direction?

@LittleBaiBai I think the current implementation (this PR) is fine.  I actually view the existing pattern of passing in an object of optional dependencies as poor api design.  That pattern came about as a hack around Guice's poor support for optional injection.  If we ever decide to refactor this code I'd prefer to deprecate all constructors and switch to the builder pattern.


OpenCSPM not picking up custom output.json

Describe the bug
Having followed instructions at https://github.com/OpenCSPM/opencspm/blob/main/site/data_collection.md#aws-cloud-resources, OpenCSPM does not pick up my custom data.
# ls -l assets/custom
total 316
-rw-r--r-- 1 christophetd christophetd     12 nov.  16 12:35 manifest.txt
-rwxr-xr-x 1 christophetd christophetd 316195 nov.  16 12:35 output.json

$ cat assets/custom/manifest.txt
output.json

$ cat config/config.yaml
---
db:
  host: redis
  port: 6379
buckets:
  # - gs://darkbit-collection-us-cspm
  # - s3://my-other-bucket-here
local_dirs:
  - /app/data/custom
  # - /app/data/test

I did run docker-compose down && docker-compose up after making these modifications.
No visible error in logs
Expected behavior
OpenCSPM should pick up the new resources file
Screenshots
UI:

Docker information (please complete the following information):
$ docker --version
Docker version 19.03.13, build 4484c46d9d

$ docker-compose --version
docker-compose version 1.27.4, build 40524192

Cloud provider (if applicable):
AWS

Solved: I had to manually delete Docker volumes (docker volume rm opencspm_core opencspm_postgres opencspm_redis) and restart OpenCSPM. Might be worth mentioning in the docs

This is a UI bug. The new files will be loaded since the config.yaml is re-read every time the background job runs, but it is not reflected correctly in the UI.


How to deal with the vehicle params when we want to adapt apollo to trailer

Dear apollo team developers,
   We want to adapt apollo to a trailer, but now, apollo is used for those cars that they are a rigid body, do you have any ideas or suggestions about this situation? It involves so many aspects to take consideration, if we want to simplify it now, can we make it work only by adjusting vehicle params, like the wheel_base, wheel_rolling_radius, min_turn_radius?
  If any other team or project that is doing something similar to ours, welcome you to give us some advice or we can talk about relative problems.

Simply modifying the vehicle params won't work if the vehicle has a trailer. Different planning (maybe control) module(s) will be needed.

Closing this issue as there has been no communication in a while. @xinwf feel free to reopen it if you have additional questions. Thanks!


[Feature request] Automatic conversion from other front-end links to esteem

I always like the simplistic way of esteem to address the link in relation to the blockchain and not towards a web-front-end.
Although I must admit that the switching between many (now) fron-ends would be kind of nice. Copy this post from whatever and paste it on esteem to work my way out, would be simply amazing.
Probably can be only supported between known front-ends, but if steemit is supported I would be already 99% happy!

I just realized this one might be quite hard to implement... and not very "high" in demand.


[Feature Request] Do git add to the selected files in git_status?

As title. It will be very helpful for me if I can add some file-update to git without typing git add. Currently, I can only use require'fzf-lua'.git_status() to open these files, but I will like to git add them at ease.

The issue here is that it will require much more work than just git_add because then I have to refresh the list and add an indicator marking it as "Staged" and then also adding an option for git_unstage, that also requires to run a different command than git status -s to display staged/unstaged files and may other git intriciacies, then why stop here? why not enable git_status between two different commits? it's endless.
Whenever I get to the point I need that type of functionality, I use vim-fugitive which can do practically anything with git repos, if I need more fine grained control on the chnges (or wish to compare two different commits) I use diffview.nvim, both are geared specifically towards git and are much more suitable tools for the job.
Doing this inside fzf-lua requires more work and complexity than I wish to enter ATM, perhaps one day I'll revisit this but for now I consider this out of scope of fzf-lua.

What if we just close the window (so no need to refresh) and if the user wants to unstage then it should do it by CLI? I'm still somehow hope this can be done.

That you can do by yourself, just add a custom action mapping and call git add using vim.fn.system.
Something like this (make sure to add proper flags, working dir if needed, etc):
actions = {
  ["ctrl-y"]      = function(selected)
     vim.fn.system('git add  .. 'selected[1])
  end
}

That you can do by yourself, just add a custom action mapping and call git add using vim.fn.system.
Something like this (make sure to add proper flags, working dir if needed, etc):
actions = {
  ["ctrl-y"]      = function(selected)
     vim.fn.system('git add ' .. selected[1])
  end
}

Thank you, let me try it now. I think this is exactly what I need!

That you can do by yourself, just add a custom action mapping and call git add using vim.fn.system.
Something like this (make sure to add proper flags, working dir if needed, etc):
actions = {
  ["ctrl-y"]      = function(selected)
     vim.fn.system('git add ' .. selected[1])
  end
}

This resolves the issue. Thank you!

I'm pretty sure you know this but if you neded to iterate all selected files, this is how it's done in lua:
for _, file in ipairs(selected) do
  -- do whatever you want with the file
  print(file)
end

This doesn't work anymore. And selected[1] seems not able to work when I select multiple files now.

I'm pretty sure you know this but if you neded to iterate all selected files, this is (one of the ways) how it's done in lua:

I thought I know what you were talking about. Now I realize I need to fix something, lol.

This was just a sketch function, inspect the selected table properly, you may need to parse the line and remove parts of it  (the M at the start for example`).
I use the below to print objects in neovim :messages:
-- help to inspect results, e.g.:
-- ':lua _G.dump(vim.fn.getwininfo())'
-- use ':messages' to see the dump
function _G.dump(...)
  local objects = vim.tbl_map(vim.inspect, { ... })
  print(unpack(objects))
end

I'm pretty sure you know this but if you neded to iterate all selected files, this is (one of the ways) how it's done in lua:
for _, file in ipairs(selected) do
  -- do whatever you want with the file
  print(file)
end

Indeed your sketch is correct. I just forgot that I need to add this loop for my actions = { ["ctrl-y"] .... (So I encountered an error that I only git add one file while I selected multiple.)

FYI, since the resume made this much easier I decided to add stage/unstage operations, I reworked git_status entirely, it now matches the output of git status -s where the left markers are staged and right are unstaged.
By default <left> will stage a file (move the icon from right to left) and vice versa with <right>:

@ibhagwan Astonishing! I'm happy to upgrade my editor and try this now!

This not only makes me feel productive but also provides a fun experience.


Feature Request: The ability to validate a form, not an individual field

In my case I have a dynamic form that allows the user to add multiple rows to a form. The requirement is that at least one row is required. I added a custom validation method, however, in order for it to work I need to attach it to a field. It would be nice if I could attach it to the form or a div tag and have it work.

1


Linter should not complain on usage of variable

Current example from readme:
func fd(p int) int {
	v_b := p * 2 // want "v_b is used under score. You should use mixedCap or MixedCap."

	return v_b // want "v_b is used under score. You should use mixedCap or MixedCap."
}

I think it should be following:
func fd(p int) int {
	v_b := p * 2 // want "v_b is used under score. You should use mixedCap or MixedCap."

	return v_b
}

Reasons:

No need to duplicate errors
If I want to ignore the error, now I have to repeat //nolint many times
If snake case is declared in generated code (for example in protobuf), it should not be an error

Thanks

A similar issue is with the usage of types. The linter will complain when I use built-in types (or types from other libraries) like syscall.Stat_t. I have no option but to use it, yet the linter complains. It would be better only to check declarations and not usages in general. That way you may use the names that are "not preferred", but out of your control, while still not allowing you to create such types/variables/etc.


feat(core/dropdown-button): add dropdown-button

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

[ ] Tests for the changes have been added (for bug fixes / features)
[ ] Docs have been reviewed and added / updated if needed (for bug fixes / features)
[x] Build (yarn build) was run locally and any changes were pushed
[ ] Unit tests (yarn test) were run locally and passed
[ ] Visual Regression Tests (yarn visual-regression) were run locally and passed
[ ] Linting (npm lint) was run locally and passed

Pull request type

Please check the type of change your PR introduces:

[ ] Bug fix
[x] Feature
[ ] Refactoring (no functional changes, no API changes)
[ ] Build related changes
[ ] Documentation content changes
[ ] Other (please describe):

What is the new behavior?
Implemented new component dropdown-button as requested in #173

A new prop in icon-button was also implemented to let the small triangle to be toggle when its used on a dropdown-button.
Build is not passing because of the problem that i'm Windows, so the file component-doc.json needs to be re-commited by someone with mac.
Visual-regression tests for this new component are created, but it is needed to check if any onther tests are failing and the new
snapshots need to be commited.
 Added documentation and examples.
Triangle color is not correct, it cannot inherit, so a variable is needed to match the colors of the icons with the triangle.

@goncalosard

Please merge with latest main the branch looks stale to me
After merge with latest you must adapt the documentation regarding the playground component (see other docs e.g. buttons.md)
Dropdown without icon looks broken

@goncalosard

Please merge with latest main the branch looks stale to me
After merge with latest you must adapt the documentation regarding the playground component (see other docs e.g. buttons.md)
Dropdown without icon looks broken

@danielleroux
Added all the requests you made. Please check if its ok.
Build failed because component-doc.json, add your file.


Installation problems with cocoapods

Pod spec
source 'https://github.com/CocoaPods/Specs.git'
platform :ios, '7.0'
xcodeproj 'Test.xcodeproj'
pod 'ILPDFKit', '0.0.6'

If you open up the ILPDFKit folder while it's installing, you'll see the code downloading as it should but at the last phase it'll delete all the source files.
I have no idea why it'd do that.
Here's the terminal printout
dtmac:trunk dt$ pod install --verbose
Preparing
Analyzing dependencies
Updating spec repositories
$ /usr/bin/git rev-parse  >/dev/null 2>&1
Updating spec repo master
$ /usr/bin/git pull --ff-only
Already up-to-date.
Inspecting targets to integrate
Using ARCHS setting to build architectures of target Pods: (``)
Resolving dependencies of Podfile
Resolving dependencies for target `Pods' (iOS 7.0)

ILPDFKit (= 0.0.6)

Comparing resolved specification to the sandbox manifest
A ILPDFKit
Downloading dependencies
-> Installing ILPDFKit (0.0.6)

Git download
Git download
$ /usr/bin/git clone https://github.com/iwelabs/ILPDFKit.git /Users/dtan/Projects/BMS/trunk/Pods/ILPDFKit --single-branch --depth 1 --branch 0.0.6
Cloning into '/Users/dt/Projects/test/trunk/Pods/ILPDFKit'...
Note: checking out 'c2590b9db8d81c1c26887b0d126119428dd77f5d'.

 You are in 'detached HEAD' state. You can look around, make experimental
 changes and commit them, and you can discard any commits you make in this
 state without impacting any branches by performing another checkout.

 If you want to create a new branch to retain commits you create, you may
 do so (now or later) by using -b with the checkout command again. Example:

   git checkout -b new_branch_name

Generating Pods project

Creating Pods project
Adding source files to Pods project
Adding frameworks to Pods project
Adding libraries to Pods project
Adding resources to Pods project
Linking headers
Installing targets

Installing target Pods-ILPDFKit iOS 7.0
Installing target Pods iOS 7.0

Running post install hooks
Writing Xcode project file to Pods/Pods.xcodeproj
Writing Lockfile in Podfile.lock
Writing Manifest in Pods/Manifest.lock

Integrating client project
Integrating target Pods (test.xcodeproj project)

Fixed

why this error happens?


Export object with class, not class itself

Landed in https://github.com/metarhia/config/commit/3884f03fe48cc6fc36003532144d0a566468f1ea


Failed to build from source ?

I tried to build phantomjs following http://phantomjs.org/build.html ,
but i find there's no build.py in git repo after I clone it.
Is the instructions for compiling is old ?
And how to build the latest release version such as 2.1.3 now ?
by the way I tried to download the linux binary, but there are missing libraries,
I prefer build from source.
thanks!

qmake & make

Any plan beyond 2.1.1 is currently abandoned, see #15344 for more details.


BRIDGE-1172 Make the plot markers circles that are tinted, gray or filled.

Legend is still hardcoded in the dashboard, but the circles are in and it's marginally more flexible.

looks good


Use batcher and queued-retry on perf tests

The typical usage is expected to have both the batcher and the queued-retry so changing the perf tests to use them. Also adding a test with addattributesprocessor that requires a different configuration file, the intention here is that adding this processor should not cause major difference between not having it enabled.

Codecov Report

Merging #183 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #183   +/-   ##
=======================================
  Coverage   72.74%   72.74%
=======================================
  Files         104      104
  Lines        6094     6094
=======================================
  Hits         4433     4433
  Misses       1435     1435
  Partials      226      226

Continue to review full report at Codecov.

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


WIP: Pick first location on confirm if none is selected

I would like to wait a little bit with this one. I think the problem where the styling of the confirm button does not update is linked to our text component. I thought it might be a rerender issue with react-navigation

@tbergq Can you please replicate this issue in a minimal example so we can fix it?

Yes, I will look into it soon, make a playground for it, and try to solve it

closing this since we confirm on click on first location


Feature upgrade.

Please create edit profiles options and deactive account feature as soon as possible in the profile page.
I am waiting for that feature.
Please provide with slight security fixes in profile section.
Thank you!
I hope you consider my request and do the needful.

Surely I will consider your upgrade features and the feature you asked is under development.
I will give much security features than you expect in the profile page of the users.
Soon you can expect that release.
Thank you for your suggesstions. if any thing else please create a issue and notify me.
Thank you once again.

Your requested feature is pushed in the latest update.
Please check the code here: Version 3 - v3.0


bump kubernetes version to 1.13.7

Codecov Report

Merging #1622 into v0.13.x will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff            @@
##           v0.13.x    #1622   +/-   ##
========================================
  Coverage    25.54%   25.54%
========================================
  Files           98       98
  Lines         5038     5038
========================================
  Hits          1287     1287
  Misses        3608     3608
  Partials       143      143

Continue to review full report at Codecov.

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


Execution failed for task ':app:packageRelease'.

I don't get where I am wrong
Here my key.properties
storePassword=**
keyPassword=**
keyAlias=key
storeFile=C:\\Users\\mdhvk\\weather.jks

build.gradel
def localProperties = new Properties()
def localPropertiesFile = rootProject.file('local.properties')
if (localPropertiesFile.exists()) {
    localPropertiesFile.withReader('UTF-8') { reader ->
        localProperties.load(reader)
    }
}

def flutterRoot = localProperties.getProperty('flutter.sdk')
if (flutterRoot == null) {
    throw new GradleException("Flutter SDK not found. Define location with flutter.sdk in the local.properties file.")
}

def flutterVersionCode = localProperties.getProperty('flutter.versionCode')
if (flutterVersionCode == null) {
    flutterVersionCode = '1'
}

def flutterVersionName = localProperties.getProperty('flutter.versionName')
if (flutterVersionName == null) {
    flutterVersionName = '1.0'
}

apply plugin: 'com.android.application'
apply from: "$flutterRoot/packages/flutter_tools/gradle/flutter.gradle"

def keystoreProperties = new Properties()
def keystorePropertiesFile = rootProject.file('key.properties')
if (keystorePropertiesFile.exists()) {
    keystoreProperties.load(new FileInputStream(keystorePropertiesFile))
}

android {
    compileSdkVersion 28

    lintOptions {
        disable 'InvalidPackage'
    }

    defaultConfig {
        // TODO: Specify your own unique Application ID (https://developer.android.com/studio/build/application-id.html).
        applicationId "co.mdhv.weather"
        minSdkVersion 16
        targetSdkVersion 28
        versionCode flutterVersionCode.toInteger()
        versionName flutterVersionName
        testInstrumentationRunner "androidx.test.runner.AndroidJUnitRunner"
    }

    signingConfigs {
        release {
            keyAlias keystoreProperties['keyAlias']
            keyPassword keystoreProperties['keyPassword']
            storeFile file(keystoreProperties['storeFile'])
            storePassword keystoreProperties['storePassword']
        }
    }

    buildTypes {
        release {
            // TODO: Add your own signing config for the release build.
            // Signing with the debug keys for now, so `flutter run --release` works.
            signingConfig signingConfigs.release
        }
    }
}

flutter {
    source '../..'
}

dependencies {
    testImplementation 'junit:junit:4.12'
    androidTestImplementation 'androidx.test:runner:1.1.0-alpha4'
    androidTestImplementation 'androidx.test.espresso:espresso-core:3.1.0-alpha4'
}

Here logs -
[  +26 ms] executing: [C:\flutter\] git log -n 1 --pretty=format:%H
[  +61 ms] Exit code 0 from: git log -n 1 --pretty=format:%H
[        ] 20e59316b8b8474554b38493b8ca888794b0234a
[        ] executing: [C:\flutter\] git describe --match v*.*.* --first-parent --long --tags
[  +72 ms] Exit code 0 from: git describe --match v*.*.* --first-parent --long --tags
[        ] v1.7.8+hotfix.4-0-g20e59316b
[  +10 ms] executing: [C:\flutter\] git rev-parse --abbrev-ref --symbolic @{u}
[  +36 ms] Exit code 0 from: git rev-parse --abbrev-ref --symbolic @{u}
[        ] origin/stable
[        ] executing: [C:\flutter\] git ls-remote --get-url origin
[  +34 ms] Exit code 0 from: git ls-remote --get-url origin
[        ] https://github.com/flutter/flutter.git
[  +61 ms] executing: [C:\flutter\] git rev-parse --abbrev-ref HEAD
[  +37 ms] Exit code 0 from: git rev-parse --abbrev-ref HEAD
[        ] stable
[  +46 ms] executing: C:\Users\mdhvk\AppData\Local\Android\sdk\platform-tools\adb.exe devices -l
[  +31 ms] Exit code 0 from: C:\Users\mdhvk\AppData\Local\Android\sdk\platform-tools\adb.exe devices -l
[   +1 ms] List of devices attached
[  +18 ms] No connected devices.
[  +10 ms] "flutter run" took 97ms.
[        ] "flutter run" took 97ms.

#0      throwToolExit (package:flutter_tools/src/base/common.dart:28:3)
#1      RunCommand.validateCommand (package:flutter_tools/src/commands/run.dart:284:7)
<asynchronous suspension>
#2      FlutterCommand.verifyThenRunCommand (package:flutter_tools/src/runner/flutter_command.dart:462:11)
<asynchronous suspension>
#3      FlutterCommand.run.<anonymous closure> (package:flutter_tools/src/runner/flutter_command.dart:383:33)
<asynchronous suspension>
#4      AppContext.run.<anonymous closure> (package:flutter_tools/src/base/context.dart:153:29)
<asynchronous suspension>
#5      _rootRun (dart:async/zone.dart:1124:13)
#6      _CustomZone.run (dart:async/zone.dart:1021:19)
#7      _runZoned (dart:async/zone.dart:1516:10)
#8      runZoned (dart:async/zone.dart:1463:12)
#9      AppContext.run (package:flutter_tools/src/base/context.dart:152:18)
<asynchronous suspension>
#10     FlutterCommand.run (package:flutter_tools/src/runner/flutter_command.dart:375:20)
#11     CommandRunner.runCommand (package:args/command_runner.dart:197:27)
<asynchronous suspension>
#12     FlutterCommandRunner.runCommand.<anonymous closure>
(package:flutter_tools/src/runner/flutter_command_runner.dart:396:21)
<asynchronous suspension>
#13     AppContext.run.<anonymous closure> (package:flutter_tools/src/base/context.dart:153:29)
<asynchronous suspension>
#14     _rootRun (dart:async/zone.dart:1124:13)
#15     _CustomZone.run (dart:async/zone.dart:1021:19)
#16     _runZoned (dart:async/zone.dart:1516:10)
#17     runZoned (dart:async/zone.dart:1463:12)
#18     AppContext.run (package:flutter_tools/src/base/context.dart:152:18)
<asynchronous suspension>
#19     FlutterCommandRunner.runCommand (package:flutter_tools/src/runner/flutter_command_runner.dart:356:19)
<asynchronous suspension>
#20     CommandRunner.run.<anonymous closure> (package:args/command_runner.dart:112:25)
#21     new Future.sync (dart:async/future.dart:224:31)
#22     CommandRunner.run (package:args/command_runner.dart:112:14)
#23     FlutterCommandRunner.run (package:flutter_tools/src/runner/flutter_command_runner.dart:242:18)
#24     run.<anonymous closure>.<anonymous closure> (package:flutter_tools/runner.dart:62:22)
<asynchronous suspension>
#25     _rootRun (dart:async/zone.dart:1124:13)
#26     _CustomZone.run (dart:async/zone.dart:1021:19)
#27     _runZoned (dart:async/zone.dart:1516:10)
#28     runZoned (dart:async/zone.dart:1500:12)
#29     run.<anonymous closure> (package:flutter_tools/runner.dart:60:18)
<asynchronous suspension>
#30     AppContext.run.<anonymous closure> (package:flutter_tools/src/base/context.dart:153:29)
<asynchronous suspension>
#31     _rootRun (dart:async/zone.dart:1124:13)
#32     _CustomZone.run (dart:async/zone.dart:1021:19)
#33     _runZoned (dart:async/zone.dart:1516:10)
#34     runZoned (dart:async/zone.dart:1463:12)
#35     AppContext.run (package:flutter_tools/src/base/context.dart:152:18)
<asynchronous suspension>
#36     runInContext (package:flutter_tools/src/context_runner.dart:56:24)
<asynchronous suspension>
#37     run (package:flutter_tools/runner.dart:51:10)
#38     main (package:flutter_tools/executable.dart:62:9)
<asynchronous suspension>
#39     main (file:///C:/flutter/packages/flutter_tools/bin/flutter_tools.dart:8:3)
#40     _startIsolate.<anonymous closure> (dart:isolate-patch/isolate_patch.dart:299:32)
#41     _RawReceivePortImpl._handleMessage (dart:isolate-patch/isolate_patch.dart:172:12)

We're closing this issue because it seems to be a question or request for help rather than a clearly reproducible bug, regression or new feature request.
Good places to ask questions or work through problems where you're more likely to get a fast response include:

Stack Overflow
Gitter
Flutter Community Slack

Thanks for using Flutter!


Add date-range filtering to additional Itemizable resources

Summary
We currently have the ability to filter by date range on Donations and Purchase. We'd like to extend this functionality to other resources as well. You should be able to copy it over, though it will require you to look in a few locations.
Our filtering stack involves model, view, and controller for each resource. It's always done in the :index action. Look to Donation and Purchase for how it's done. There should also be a concern or partial that you can re-use.
Criteria for completion

[ ] Distributions#index
[ ] Adjustments#index
[ ] Transfers#index
[ ] Test coverage that each works

Bonus Round
Since we're using it in so many places, this is a great opportunity to create an RSpec shared example and use that for the tests! Feel free to try that out if you want to! We use shared examples for a couple things already.

Hi, I'd like to try to solve this issue!

@armahillo , quick question. While adding date ranges, should I also remove selected ranges such as the ability to select "This week to date", etc?

@armahillo , I was wondering if this issue could be updated. I think the best thing to do is to have a separate issue for just Distributions because it already has the migrations needed in the backend to implement the frontend.
I think for the other pages Adjustments and Transfers we should do a separate migration for each and then create a rake task to set issued_at to created_at and then we should create a separate release for the UI elements.

@botanical Sorry, just saw your comments!
Distribution can use issued_at -- if you'd like to do that as a solo-PR that's totally fine!
Adjustment / Transfer should not have an issued_at field because they are not issued -- we can just filter on created_at for those.
If you'd like to do a separate PR for each of those, that's fine. I agree they should be separate issues, in hindsight. I'll break them apart - for this one, just do Distribution


added alma realschule

@eddisch Thank you for your patience while waiting for a review and processing your request. Pull request merged. Please start applying for JetBrains educational subscription at https://www.jetbrains.com/shop/eform/students in an hour, to allow the changes to propagate through JetBrains systems.


support tables

This patch added support tables. Example:
json2md({
    table: {
        headers: [ "a",  "b" ],
        rows: [
            { a: 'row1, col1' ,  b: 'row1, col2' }
        ]
    }
})

This is a great feature! :sparkles:
I have to admit I wanted to build support for tables didn't have time. Glad to see it here! :smile:
Regarding the rows, I think it would be cleaner to be like:
[
  ["row1, col1", "row1, col2"],
  ["row2, col1", "row2, col2"]
]

It looks better. Can you do that?

it would be cleaner

Yes, but we would lose compatibility with other libraries, such as mysql. It may be worth using both formats?

Sure, having both is also good! :+1:

Thanks once again for this, @ReklatsMasters! :sparkles:
Landed on master!
:ship: 1.5.0 :tada:


Timezone

How can I find the Timezone inside the container?
BR,
Itamar

The timezone in the container is the same as the host. It should almost always be utc as many sources do not indicate their tz legacy BSD devices should also be set to utc

@itamartz the default timezone for any container is GMT and can be customized by using the 'TZ' environment variable.
If you still want to validate you could start the container and connect into it using docker exec -it <container name> /bin/bash then just run the date command like normal.
References:
https://medium.com/rahasak/configure-docker-timezone-in-linux-71893fe51499


Type tuples no longer inferred properly from rest arguments with mapped generic type tuples.

I recently updated the dependencies for a TypeScript-based project and unfortunately ended up with some unexpected breakage.
The TypeScript version was changed from 4.6 to 4.7 and type tuples are no longer inferred properly from rest arguments with mapped generic type tuples.
type MyMappedType<Primitive extends any> = {
	primitive: Primitive;
};

The project uses several helper types to map type tuples to other type tuples as shown below.
type TupleMapperOld<Tuple extends any[]> = {
	[Key in keyof Tuple]: Tuple[Key] extends Tuple[number] ? MyMappedType<Tuple[Key]> : never;
};

After updating to TypeScript 4.7 it is still possible to use the helper directly. TypeScript will correctly infer the type as expected.
// Type should be [MyMappedType<string>, MyMappedType<number>] in TypeScript 4.6 and TypeScript 4.7.
type MyMappedTupleOld = TupleMapperOld<[string, number]>;

However, type inference breaks when using the mapper to map the rest arguments of a generic function as shown below.
function extractPrimitivesOld<Tuple extends any[]>(...mappedTypes: TupleMapperOld<Tuple>): Tuple {
	return mappedTypes.map((mappedType) => mappedType.primitive) as Tuple;
}

// Inferred type should be [string, number] but becomes [unknown, unknown] in TypeScript 4.7.
const myPrimitiveTupleOld = extractPrimitivesOld({ primitive: "" }, { primitive: 0 });

The problem can be mitigated by explicitly specifying the generic type tuple argument. It can also be solved by removing the mapping constraints in the mapper as shown below.
type TupleMapperNew<Tuple extends any[]> = {
	[Key in keyof Tuple]: MyMappedType<Tuple[Key]>;
};

I decided to open this issue and let you decide if this is something worth investigating since I couldn't find any information about the difference in behaviour in the release notes.
🔎 Search Terms
tuple mapping
type inference
rest arguments
generics
🕗 Version & Regression Information
This changed between versions 4.6 and 4.7.
⏯ Playground Link
Playground 4.6.4
Playground 4.7.2
💻 Code
type MyMappedType<Primitive extends any> = {
	primitive: Primitive;
};

type TupleMapperOld<Tuple extends any[]> = {
	[Key in keyof Tuple]: Tuple[Key] extends Tuple[number] ? MyMappedType<Tuple[Key]> : never;
};

// Type should be [MyMappedType<string>, MyMappedType<number>] in TypeScript 4.6 and TypeScript 4.7.
type MyMappedTupleOld = TupleMapperOld<[string, number]>;

function extractPrimitivesOld<Tuple extends any[]>(...mappedTypes: TupleMapperOld<Tuple>): Tuple {
	return mappedTypes.map((mappedType) => mappedType.primitive) as Tuple;
}

// Inferred type should be [string, number] but becomes [unknown, unknown] in TypeScript 4.7.
const myPrimitiveTupleOld = extractPrimitivesOld({ primitive: "" }, { primitive: 0 });
//    ^?

type TupleMapperNew<Tuple extends any[]> = {
	[Key in keyof Tuple]: MyMappedType<Tuple[Key]>;
};

// Type should be [MyMappedType<string>, MyMappedType<number>] in TypeScript 4.6 and TypeScript 4.7.
type MyMappedTupleNew = TupleMapperNew<[string, number]>;

function extractPrimitivesNew<Tuple extends any[]>(...mappedTypes: TupleMapperNew<Tuple>): Tuple {
	return mappedTypes.map((mappedType) => mappedType.primitive) as Tuple;
}

// Inferred type should be [string, number] in TypeScript 4.6 and TypeScript 4.7.
const myPrimitiveTupleNew = extractPrimitivesNew({ primitive: "" }, { primitive: 0 });

🙁 Actual behavior
The type tuple is inferred as [unknown, unknown] in TypeScript 4.7.
🙂 Expected behavior
The type tuple is inferred as [string, number] in TypeScript 4.7.

@typescript-bot bisect good v4.6.4 bad v4.7.4

type TupleMapperOld<Tuple extends any[]> = {
  [Key in keyof Tuple]: Tuple[Key] extends Tuple[number] ? MyMappedType<Tuple[Key]> : never;
};

What was the purpose of this conditional type? At a glance it seems like it should always evaluate true.

So, at first glance, the above appears to be intended to filter the keys of a tuple type to only the numeric indexes (so, filter out any named things like if you had any[] & { foo: number }, except that it seems to not really work correctly because if you have [string, number] & { foo: number }, foo wouldn't be filtered out because it has a value type of number and that is one of the values of the indexed types. It would seem like the right thing to write would be:
type TupleMapper2<Tuple extends any[]> = {
  [Key in keyof Tuple]: Key extends number ? MyMappedType<Tuple[Key]> : never;
};

This doesn't doesn't compile and has a confusing error at the call.
But, depending on what we think keyof Tuple is supposed to be comprised of, this would feel like it should always be true.
#48837 seems to be intended to change indexed accesses to arrays/tuples to not only be number but also `${number}`. So, if you change the above such that it is still always true (presumably, #48837 was a breaking change in that way), you can write:
type TupleMapper3<Tuple extends any[]> = {
  [Key in keyof Tuple]: Key extends (number | `${number}`) ? MyMappedType<Tuple[Key]> : never;
};

And this compiles with the original example in 4.7, so maybe it's a workaround?
If we go back to the original example, it would seem like we could make the same transformation by adding `${number}` and write:
type TupleMapper4<Tuple extends any[]> = {
	[Key in keyof Tuple]: Tuple[Key] extends (Tuple[number] | Tuple[`${number}`]) ? MyMappedType<Tuple[Key]> : never;
};

Except that we get an error that says that Tuple cannot be indexed by `${number}`, which is what #48837 seems to have been intended to change, so that feels incongruent (as though there's some other part of the checker that also needs to be updated to allow this). I'm not sure if that's the entirety of the problem or if it's that + the fact that #48837 sort of broke the assumptions that code can make about what keys can be in arrays/tuples.
All examples better laid out here: Playground Link

I think the upshot of this is that the purpose of the conditional type was to do exactly what #48837 does unconditionally, so it can just be removed. The conditional type is a workaround for the previous weird behavior of mapping over generic tuples/arrays. That said, I think the lost inference in the original example is still probably a bug.

Just to complete my side investigation, the "Type '`${number}`' cannot be used to index type 'Tuple'." message is caused by our definition of the index type for Array, which is defined as [n: number]: T; changing this to n: number | `${number}`]: T makes the error go away, but does not fix the inferencing problem reported in this issue, so I doubt it is the cause like you say. (It also breaks a number of other things in mysterious ways, so I doubt it is a desirable change anyhow, at least not the prototype I tested.)

This seems to have turned out to just be a bug; see #52848.


[Incremental] JENKINS-55523: Add support for zone selection with dropdown

This change brings in a light ComputeClient in order to retrieve the list of available zones for a project. Much of the ComputeClient was inspired by the jenkinsci/google-compute-engine-plugin with some stylistic differences, and the difference that we will not enable filtering by region with this change. The UI allows the user to select either text or dropdown by choosing one of the radio buttons (currently, one is not chosen by default but I know that's not ideal and I'm open to suggestions on which one to make the default).

Looking good, a few suggestions.


Two Factor Authentication :  Disable Fallback

The two factor authentication in OPNSense even though works fine is somewhat broken for most scenarios.  The TFA requires a fallback option which is Global and not set at per user / group level.  So while fallback for a root account is is a desirable option, the fallback feature to the local database defeats the purpose of TFA for regular users.  Disabling the fallback affects the root user also making the WebGUI inaccessible unless reset from the console.
Request to enable per user / group configurable fallback where fallback is enabled for root but disabled  for all other users

You can always choose to enable ssh with a pub/priv key combination as fallback for emergencies if a general fallback is not desired.
A per user override is not a feature we're considering at the moment.


KAFKA-9020: Streams sub-topologies should be sorted by sink -> source relationship

Subtopologies are currently ordered alphabetically by source node, which prior to KIP-307 happened to always result in the "correct" (ie topological) order. Now that users may name their nodes anything they want, we must explicitly order them so that upstream node groups/subtopologies come first and the downstream ones come after.

@guozhangwang @bbejeck @vvcephei

ping @bbejeck @vvcephei could you guys take a look?

Java 11/2.12 failed with Task :connect:mirror:integrationTest FAILED
Java 11/2.13 failed with kafka.api.ConsumerBounceTest.testRollingBrokerRestartsWithSmallerMaxGroupSizeConfigDisruptsBigGroup
Java 8 failed with FATAL: Unable to delete script file /tmp/jenkins6761014166594532618.sh 06:53:19 java.io.EOFException
retest this please

Java 8 and Java 11.12 passed
Java 11 says this failed but when you click to see the stacktrace it says it passed, sooo...?
KTableKTableForeignKeyJoinIntegrationTest.doLeftJoinFilterOutRapidlyChangingForeignKeyValues

ping either of @guozhangwang @vvcephei for a second review

on this PR builder run Java 11/2.12 and Java 11/2.13 passed
on previous PR builder run Java 8 and Java 11/2.12 passed, so between the two all passed.
Merging this now.

Merged #7495 into trunk.

cherry-picked to 2.4


Revert "Switch to per-thread default stream (#9396)"

This reverts commit f7f673b00c15458fb4dd74a2a0d2ba80369c5faf.
Close https://github.com/dmlc/xgboost/issues/9410 .
@rongou .

Merging it for now to restore the CI.


Tile.tileset incorrectly holds an array

Version
Phaser Version: 3.14.0
Description
Tile.tileset now incorrectly holds an array of tilesets instead of a tileset object. This breaks Tile.getCollisionGroup and Tile.getTileData.

Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

Tilemap layers now support multiple Tilesets as of 3.14. This is intentional. The real issue is getCollisionGroup and getTileData not supporting this new feature.

Tilemaps have multiple tilesets, but shouldn't a tile only need to reference the tileset it's actually using?
If tiles are supposed to hold an array we should change the docs to reflect this. @iamchristopher

Any news on this issue?
I am trying to get collision to work with a Tilemap from Tiled.
myLayer.setCollisionFromCollisionGroup() works with Phaser v3.13, but I need Phaser v3.15+ because of other improvements (webgl performance on iOS). Any alternatives to setCollisionFromCollisionGroup() in v3.15+ ?
Thanks!

Thank you for submitting this issue. We have fixed this and the fix has been pushed to the master branch. It will be part of the next release. If you get time to build and test it for yourself we would appreciate that.

Thank you for submitting this issue. We have fixed this and the fix has been pushed to the master branch. It will be part of the next release. If you get time to build and test it for yourself we would appreciate that.

Can confirm it is working. Just ran into the problem on 3.15.1 and after messing around with different Tiled versions and different Phaser versions, building from source was the only thing that I could do to get around this issue and actually see the collision boxes correctly using Matter physics

I can confirm it works too.
By the way, not sure if it's been mentioned already, some of the matter examples have the same problem.


Update README.md

Description
Added a new article on how to make a custom Django cookiecutter template.
Rationale
As many people might want to implement their own standards in their Django projects, they might need to design their own cookiecutter templates and add the tools they might usually use. This article shows how people can make their own Django templates using the cookiecutter package.

Nice post!


feat: implement middleware provider

We are using middleware which on global level. Why don't we provide middleware using Provider?
<Provider middleware={middleware}>
  <App />
<Provider/>

https://github.com/tannerlinsley/react-query/blob/7bab9534cfb322f23a01549d464e0e618e204897/src/react/QueryClientProvider.tsx#L37

https://github.com/tannerlinsley/react-query/blob/7bab9534cfb322f23a01549d464e0e618e204897/src/react/QueryClientProvider.tsx#L37

I've look up codes for a while and found that Provider needs only for useActionListener.
So it may be verbose to apply.


Modal affecting Swipeable Gesture on Android

Environment

Platforms

Versions

Android:
iOS:
react-native-modal:
react-native:
react:

Description

When using "Modal" for Android; the "Swipeable" gesture handler does not work only on android
Reproducible Demo

@jackilex did you find any solution about this issue

@jackilex did you find any solution about this issue

@jackilex did you find any solution or trick about this issue

I went with another technique (hold gesture) In the meantime. I will be going over it again to see what the problem... It seems that it is the modal. I need to review my codes. It might also be because I have a  inside the modal. Not sure yet until I review it... But iOS didn't have that issue

@jackilex did you find any solution or trick about this issue

I went with another technique (hold gesture) In the meantime. I will be going over it again to see what the problem... It seems that it is the modal. I need to review my codes. It might also be because I have a  inside the modal. Not sure yet until I review it... But iOS didn't have that issue

@jackilex  hi were u able to figure out why

No sorry. At that time I ended switching over to Flutter


Implement Rewind in SVM package

As per title. This PR is a follow-up to https://github.com/spacemeshos/go-spacemesh/pull/2864 and closes https://github.com/spacemeshos/go-spacemesh/issues/2832.
Changes
The LoadState function is fully replaced with Rewind, which in the future will wrap a call to its equivalent go-svm Rewind counterpart. State root hash is also returned, which will be free information once SVM integration happens and can simplify ergonomics (avoid a call to GetStateRoot).
Test Plan
Covered by existing testing.
DevOps Notes

[x] This PR does not require configuration changes (e.g., environment variables, GitHub secrets, VM resources)
[x] This PR does not affect public APIs
[x] This PR does not rely on a new version of external services (PoET, elasticsearch, etc.)
[x] This PR does not make changes to log messages (which monitoring infrastructure may rely on)

bors merge

bors try

bors try

bors try

bors merge


CASMPET-6940 1.4 : Automate import of resourcequotas and limitranges

Description
Automate import of resourcequotas and limitranges for system recovery
Resolves CASMPET-6940
Also need to backport to release/1.5 and release/1.6
Tested on wasp and TDSY
Checklist

[ ] If I added any command snippets, the steps they belong to follow the prompt conventions (see example).
[ ] If I added a new directory, I also updated .github/CODEOWNERS with the corresponding team in Cray-HPE.
[x] My commits or Pull-Request Title contain my JIRA information, or I do not have a JIRA.

/backport release/1.5 release/1.6


Package stability

I was looking for a package like this for Laravel and this seems to be the best looking option!
I was wondering how stable it is as I have seen some comments inside suggesting it may get changes in future.

At the moment the features it provides is minimal, so there will be a enhancements in the next months.
But what the package does already will either not change or if there will be a BC, then we'll clearly state that in the UPGRADE doc, so you will know how to handle it.
These are the upcoming improvements:

configurable state machine (add arbitrary order states and define transitions between them)
more order events (like OrderWasCancelled, OrderWasCompleted, etc)
Payment and Shipment handling (optional)
Handling Taxes (optional)
Handling Promotions (optional)


[WIP] Clear up fragments of the old api

As everything is being moved over to the new container api
removing files that depended on the old api
Signed-off-by: umohnani8<EMAIL_ADDRESS>

Waiting on https://github.com/projectatomic/libpod/pull/106 and https://github.com/projectatomic/libpod/pull/113

@umohnani8 looks like you need to rebase.

@umohnani8 Needs a rebase.

Ready to merge once tests are green

LGTM
@rhatdan PTAL

@rh-atomic-bot r+


$edinChannel Dosent works

$editChannel dosent works on voice channels.
i run $editChannel[$voiceID;$default;$default;$default;$default;$default;1;no]
and this do nothing.
pls fix this

well u cant set bitrate of a channel to 1 so it wont do anything
plus u are setting userLimit to no which is also wrong

well u cant set bitrate of a channel to 1 so it wont do anything
plus u are setting userLimit to no which is also wrong

i used $editChannel[$voiceID;$default;$default;$default;$default;$default;$default;1] and nothing had happened

what are u trying to do

what are u trying to do

i am trying to set limit of users in voice channel

if u only want that then just do
$editChannel[$voiceId;{
  "userLimit" : 1
  }]

and how to rename channel?
use this: $editChannel[$voiceId;{   "name" : "name lol"   }] ?


Fix external name configuration of TransitGatewayVPCAttachmentAccepter resource

Description of your changes
Fix external name configuration of TransitGatewayVPCAttachmentAccepter resource
Fixes #816
I have:

[x] Run make reviewable test to ensure this PR is ready for review.

How has this code been tested
Tested locally. The issue was reproduced by following the steps in the description of #816. Then after applying the proposed fix in this PR, the issue was resolved.

/test-examples="examples/ec2/transitgatewayvpcattachmentaccepter.yaml"

Successful Job: https://github.com/upbound/provider-aws/actions/runs/6980792906


Be stricter about the onboarding checklist

/cc @brittag

Yes, good plan! I added a new commit that consolidates this guidance a bit, with more active voice.

Do you think we also need a stricter notice on the checklist page itself? (Leaving to you to merge...)

Let's look at the checklist separately - I see a few specific things to do there: https://github.com/18F/cg-product/issues/321


Include bootloader arrangement in build-iso

Related rancher/elemental#263
Signed-off-by: David Cassany<EMAIL_ADDRESS>

Note that for the efi stuff iso, we only need a grub.efi and a grub.cfg. We can generate the grub.cfg in the elemental-cli and the grub.efi can come from the rootfs directly, no need to use toolkit packages for that, we only need to copy it to /EFI/BOOT/bootx64.efi and drop the grub.cfg into the same place.
And for the boot modules, I think for the iso the default grub should contain evertyhing, so Im willing to say that it would be possible to drop them directly.

And for the boot modules, I think for the iso the default grub should contain evertyhing, so Im willing to say that it would be possible to drop them directly.

I am not sure what are you referring to, but note most of the logic we have in packages/livecd/grub2 build recipe is related to support legacy bios firmware, not efi. I could not find a prebuild core.img for i386-pc.
But yes there several files we are including that are not needed in those packages.
For ISOs the boot matrix expands to 4 as we build hybrid images. In short all these should boot fine:
qemu-kvm -m 2048 -cdrom test.iso
qemu-kvm -m 2048 -hda test.iso
qemu-kvm -m 2048 -cdrom test.iso -bios /usr/share/qemu/ovmf-x86_64.bin
qemu-kvm -m 2048 -hda test.iso -bios /usr/share/qemu/ovmf-x86_64.bin

Then we just need to include two more for the secure boot 😅 , but one step at a time.

@agracey 👆🏻 - our test/support matrix is expanding. (And will double again when we add ARM). Can we limit it somehow ?

Finally this is something is consider good for a first round. This produces functional ISOs with the following command and setup:
elemental --config-dir . build-iso docker:registry.opensuse.org/home/dcassany/elemental/teal53/15.4/rancher/elemental-teal/5.3:15.1

Having a manifest.yaml file like that in current dir:
iso:
  bootloader-in-rootfs: true
  grub-entry-name: Elemental

name: "test"
label: "ELEM_LIVE"

I don't think we need to support legacy boot modes going forward

I don't think we need to support legacy boot modes going forward

:eyes:
Does that mean dropping support for booting bios isos and systems?????????? That would make everything really easy lol

I don't see any reason why to do the extra work. IMO, the only reason to keep it around would be for older systems but we would typically be included in rollouts of new hardware that should not be using a bios from the 25 years ago.
We may want to document how to install the UEFI firmware on raspberry pis (or link to a guide we trust)

damn, then this changes things. For EFI removable devices It its as simple as:

dd if=/dev/zero of=isorootfs/EFI/BOOT/efiboot.img bs=1M count=10
mkfs.msdos -F 12 -n 'EFI_BOOT' isorootfs/EFI/BOOT/efiboot.img
mmd -i isorootfs/EFI/BOOT/efiboot.img ::EFI
mmd -i isorootfs/EFI/BOOT/efiboot.img ::EFI/BOOT
mcopy -i isorootfs/EFI/BOOT/efiboot.img grub.efi ::EFI/BOOT/BOOTX64.EFI
xorriso -as mkisofs -V 'MY_ISO' -e EFI/BOOT/efiboot.img -no-emul-boot -o OUTPUT_ISO isoroot/

That would simplify things. Also on the grub part, we could drop the non-efi install which would also make it easier.

I don't think we need to support legacy boot modes going forward

I agree it is unlikely to face the need to provide legacy firmware support for any production deployment these days, however note that BIOS support is handy for testing with hipervisors. In fact, some of our tests make use of VirtualBox to run VMs in github workers and those are running on legacy firmware because EFI support in VirtualBox is just buggy and not reliable.

I agree it is unlikely to face the need to provide legacy firmware support for any production deployment these days, however note that BIOS support is handy for testing with hipervisors. In fact, some of our tests make use of VirtualBox to run VMs in github workers and those are running on legacy firmware because EFI support in VirtualBox is just buggy and not reliable.

Maybe we can just move those to qemu? We only use those for the raw image + installer tests IIRC, so it should be fairly straightforward. In fact it will probably be easier than dealing with vBox lol

What kind of documentation changes to we need ?

From user PoV there are no changes, so probably nothing on rancher/elemental, but the new option should be documented somehow into the rancher/elemental-toolkit docs.


No installation instructions, really?

Please update README.md to include installation instructions. Thanks,

Sorry for our unclear documents, I add a Quick Start to README.md.


[Question] How to run Joyflix-CloudGaming?

@guozanhua Currently Joyflix is part of oneplay.in
We are in the process of open sourcing oneplay source code soon.


Add devise

Hello ✋🏾 ,
In this feature branch, I performed the following activities:

[ ] Removed the current_user method in ApplicationController
[ ] Install and setup devise
[ ] Implement registration of a new user.
[ ] The user logs in with a combination of email and password.
[ ] Hashed passwords are stored in the database.
[ ] Ask for confirmation of email after registration
[ ] Users can reset passwords.
[ ] Modify the views in devise for registration and login to match the wireframes from the Sneak Peek

Thanks @Deepakdanger for your time and effort in reviewing my work.


fix(TDI-40751): Regain AccessType for sending createNotExist

What is the current behavior? (You can also link to an open issue here)
AccessType is always off
What is the new behavior?
Regain correct behavior
Please check if the PR fulfills these requirements

[x] The commit message follows Talend standard
[ ] Tests for the changes have been added (for bug fixes / features)
[ ] Docs have been added / updated (for bug fixes / features) ?
[ ] The code coverage on new code >75%
[ ] The new code does not introduce new technical issues (sonar / eslint)

What kind of change does this PR introduce?

[x] Bugfix
[ ] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] Build / CI related changes
[ ] Other... Please describe:

Does this PR introduce a breaking change?

[ ] Yes
[x] No

If this PR contains a breaking change, please describe the impact and migration path for existing applications: ...
Other information:

Pull request test result: failure :x:

Pull request test result: success :star:
Sonar results


set node-version output (2022 edition)

I am unable to update the original PR with a rebase and re-build so I'm opening a new one.
Description:
This adds a node-version output similar to setup-python so that the exact installed node version can be used e.g. as part of a cache key for following build steps.
Related issue:
#150 #173
Check list:

[ ] Mark if documentation changes are required.
[ ] Mark if tests were added or updated to cover the changes.

Hello @panva. Could you please run npm run build and npm run format commands?

Could you please run npm run build and npm run format commands?

done.

Could you please revert changes to previous one and add mock for getExecOutput in installer.test.ts ?
    // @actions/exec
    getExecOutputSpy = jest.spyOn(exec, "getExecOutput");
    getExecOutputSpy.mockImplementation(() => "16.15.0");

Thank you guiding this through @dmitry-shibanov.


ValueError: Tokenizer class GPTNeoXTokenizer does not exist or is not currently imported.

when I downloaded and loaded the LLM pretrained model, it showed that "ValueError: Tokenizer class GPTNeoXTokenizer does not exist or is not currently imported.", can you help me with this issue?

okay, I already sovled it, that's because my version of transformers is too low, so upgrade the transformers can solve it.

We are glad you solved the problem. For compatibility and reproducibility, we highly recommend using the provided dependencies of the conda virtual environment.


Use function instead of arrow for pre ES6 support

I think it's a little too soon to use ES6, so this PR just uses a function instead of an arrow

why are you changing just one arrow instead of all?

@cauburtin jezuz, I wasn't myself. It's been corrected

@noahlaux Please, forward PR into dev-branch.


Flaky expect failures in resolver

Getting the following segfault:
thread 'main' panicked at crates/uv-resolver/src/resolution.rs:135:30:
Every package should have metadata

Repro:
In [5]: Counter(subprocess.run("rm -rf .venv; uv venv --seed; uv pip install --no-cache --link-mode=copy --no-deps gpustat==1.1.1", shell=True).returncode for _ in range(100))
Out[5]: Counter({101: 73, 0: 27})

https://github.com/astral-sh/uv/pull/1583 should improve the error message (I had to do some bisection to narrow it down to a single package)
With #1583 it appears there's some connection to setuptools-scm
Similar message reported in this comment: https://github.com/astral-sh/uv/issues/1484#issuecomment-1948863469

Awesome, thanks! Will fix.

I can reproduce this on some old commits (I randomly tried c1eb6130e1cb46a7ce5c34bccdfcb9245e29e8a8), but not on main, so I think it's resolved, at least on main? Will re-open if not.

I bisected to #1607 , hopefully there's something in there that explains non-deterministic behaviour


Remove Alembic comments

We generally remove these auto-generated comments to indicate that the migration code has been reviewed and adjusted where necessary.

Just removes some auto-generated comments.  I'm going to :+1: myself and merge once Travis allows me to.


Fix the use of socket server in connectors example

Python 3 renamed this and import will fail on case sensitive filesystems.

Fixes #2752.


fix argument documentation of transpile functions

Summary
Details and comments

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
2 unchanged lines in 1 file lost coverage.
Overall coverage increased (+0.001%) to 89.2%

Files with Coverage Reduction
New Missed Lines
%

crates/qasm2/src/lex.rs
2
92.19%

Totals

Change from base Build<PHONE_NUMBER>:
0.001%

Covered Lines:
58816

Relevant Lines:
65937

💛  - Coveralls

https://github.com/Mergifyio backport stable/0.46


makeStyles() crashes in cypress test suite with sheetManager is undefined

When running multiple Cypress tests for several components, makeStyles() crashes when multiple components tests are run in sequence, but passes when only a single component test is run.

[x] The issue is present in the latest release.
[x] I have searched the issues of this repository and believe that this is not a duplicate.

Current Behavior 😯
Running multiple component tests in Cypress triggers the following error in the test runner's console, causing tests to fail.
TypeError: The following error originated from your application code, not from Cypress.

  > sheetManager is undefined

When Cypress detects uncaught errors originating from your application it will automatically fail the current test.

This behavior is configurable, and you can choose to turn this off by listening to the `uncaught:exception` event.
     detach makeStyles.js:156
     useStyles/</< makeStyles.js:240
     useSynchronousEffect/</< makeStyles.js:194
    React 2
react-dom.development.js:19504
    React 11
    unstable_runWithPriority scheduler.development.js:653
    React 5
    unstable_runWithPriority scheduler.development.js:653
    React 3
    workLoop scheduler.development.js:597
    flushWork scheduler.development.js:552
    performWorkUntilDeadline scheduler.development.js:164
    (Async: EventHandlerNonNull)
    js scheduler.development.js:187
    js scheduler.development.js:857
    Webpack 74

Expected Behavior 🤔
No console errors, multiple unit tests pass in the same way as running only a single unit test passes.
Steps to Reproduce 🕹
Public Github repository and branch: https://github.com/TheDiveO/lxkns/tree/wip/test-webui
Steps:

clone branch wip/test-webui
cd web/lxkns
yarn run cypress
click on "Run # component specs"

Context 🔦
It's not possible to run an automated full test suite.
Your Environment 🌎
Browsers are Firefox 84 and Electron 87

`npx @material-ui/envinfo`
 System:
    OS: Linux 5.4 Ubuntu 20.04.2 LTS (Focal Fossa)
  Binaries:
    Node: 10.19.0 - /usr/bin/node
    Yarn: 1.22.5 - /usr/local/bin/yarn
    npm: 6.14.6 - /usr/local/bin/npm
  Browsers:
    Chrome: Not Found
    Firefox: 84.0.2
  npmPackages:
    @material-ui/core: ^4.11.3 => 4.11.3
    @material-ui/icons: ^4.9.1 => 4.11.2
    @material-ui/lab: ^4.0.0-alpha.56 => 4.0.0-alpha.57
    @material-ui/styles:  4.11.3
    @material-ui/system:  4.11.3
    @material-ui/types:  5.1.0
    @material-ui/utils:  4.11.2
    @types/react:  17.0.0
    react: ^16.13.1 => 16.14.0
    react-dom: ^16.13.1 => 16.14.0
    typescript: ^4.0.3 => 4.1.3

@TheDiveO Do you have strict mode enabled? I'm not sure we will be able to help much as we are migrating to emotion/styled-components in v5.

Wrapping the mounted component under test into <React.Strict> removes the "sheetManager is undefinied" error and brings up instead the usual findDOMNode issue:
Warning: findDOMNode is deprecated in StrictMode. findDOMNode was passed an instance of Transition which is inside StrictMode. Instead, add a ref directly to the element you want to reference. Learn more about using refs safely here: https://fb.me/react-strict-mode-find-node
    in div (created by ForwardRef(Paper))
    in ForwardRef(Paper) (created by WithStyles(ForwardRef(Paper)))
    in WithStyles(ForwardRef(Paper)) (created by Transition)
    in Transition (created by ForwardRef(Grow))
    in ForwardRef(Grow) (created by Unstable_TrapFocus)
    in Unstable_TrapFocus (created by ForwardRef(Modal))
    in div (created by ForwardRef(Modal))
    in ForwardRef(Portal) (created by ForwardRef(Modal))
    in ForwardRef(Modal) (created by ForwardRef(Popover))
    in ForwardRef(Popover) (created by WithStyles(ForwardRef(Popover)))
    in WithStyles(ForwardRef(Popover)) (created by ForwardRef(Menu))
    in ForwardRef(Menu) (created by WithStyles(ForwardRef(Menu)))
    in WithStyles(ForwardRef(Menu)) (created by HelpViewer)
    in div (created by HelpViewer)
    in HelpViewer
    in Router (created by MemoryRouter)
    in MemoryRouter
    in StrictMode

But why is Material-UI crashing when not in strict mode?

As an additional note: as Cypress seems to use hot module reload in its browser-based runner and also loads into an iframe, I see this warning once:
It looks like there are several instances of `@material-ui/styles` initialized in this application.
This may cause theme propagation issues, broken class names, specificity issues, and makes your application bigger without a good reason.

But why is Material-UI crashing when not in strict mode?

I have no idea. Maybe @DomnicAmalan (#24758) has an idea. Feel free to explore more in-depth the issue, I'm not aware of anybody that has the bandwidth to look into your issue.

as Cypress seems to use hot module reload

Then their implementation might be unsafe.

The issue is in the bundler steps as mentioned by @oliviertassinari.
Thank you @oliviertassinari
Case :
If your index.html has script tag that includes bundle.js and you have HtmlWebpackPlugin in your webpack or any other bundlers then the issue happens.
##Reason:
Two times the bundle.js is included in your project, which cause duplicate node modules which causes duplicate react and react dom in your project
Solution:
Either remove script tag in index.html that injects ## bundle.js ## or use {inject: false} in your HtmlWebpackPlugin options

I'll take a look on this :)

As I unfortunately lack knowledge for webpack configuration I would be glad if someone could help me here. The project I linked to in the issue is an un-ejected create-react-app project. In consequence there is no explicit webpack configuration, but only what is hidden inside cra.

Do u use HtmlWebpackPlugin

Material UI is 4.11.3, the most recent 4.x version, but not alpha 5.0.
I don't use webpack explicitly, unless create-react-app use it under the hood. The direct dependencies do not list webpack. In consequence, no HtmlWebpackPlugin, unless create-react-app uses it under its hood.

Can u check any script tag that injects bundle.js

I'm not sure where to look for bundle.js exactly. I've fired up a cypress runner in Firefox 84 with a set of component tests and then used Firefox' developer tools to hunt for some bundle.js. At the top level, there's only /__cypress/runnter/cypress_runner.js pulled in via a <script> element. Additionally, there's the iframe for the test(s), referencing /__cypress/iframes/__all. There's a single cypress script in there that then calls Cypress.onSpecWindow().

Are u using jss?

Also at last line of error it clearly shows u r using the webpack

And also ran through your project
Its most definitely problem with bundling

How can I fix this? I worked according to instructions for cra and cypress plus react, so I would have expected it to be correct.

I'm looking at your issue now I will comment if i google hold of anything
Also, gentle note this same kind of error happened to me I was working for a week to solve it. So please hang in there

Are u using jss?

only via makeStyles().

It looks like the crush is not reproducing anymore in your branch. All tests are passing except this hook problem. It looks like this is a cypress problem because the "run x specs" feature is really buggy in cypress right now especially for experimental features.
It passes when running standalone

I also noticed a problem that you are not connecting your webpack config at all, this may lead to the problems
--- a/web/lxkns/cypress/plugins/index.js
+++ b/web/lxkns/cypress/plugins/index.js
@@ -12,10 +12,12 @@
 // This function is called when a project is opened or re-opened (e.g. due to
 // the project's config changing)

 /**
  * @type {Cypress.PluginConfig}
  */
 module.exports = (on, config) => {
+  require('@cypress/react/plugins/react-scripts')(on, config)
   // `on` is used to hook into various events Cypress emits
   // `config` is the resolved Cypress config
   return config
diff --git a/web/lxkns/src/components/muimarkdown/ChapterSkeleton.spec.tsx b/web/lxkns/src/components/muimarkdown/ChapterSkeleton.spec.tsx
index 354779a..8a8776a 100644

My advice – do not use this feature for development, only run specific specs. Anyway, this feature is removed for the next stable major release of component testing. Here is a little sneak peek of UI for you :)

Closing this issue because it is not related to Material-UI at all.
If you have any problems after all  @TheDiveO please make another issue in https://github.com/cypress-io/cypress/issues and tag me directly. Thank you :)

Thank you very much for taking the time to look into this! I've seen different variants for handling the configuration so I'm thankful for any mistakes getting spotted and pointed out to me, so I can fix them and avoid having them lurking in the dark, waiting for the right time to come back to me. With the situation clarified here I'll take the hook issue to the cypress project. So, thank you very much for your time and effort!


YieldTxns fails when a block >20k transactions

Summary
YieldTxns is designed so that it includes all results for the transaction, the way it detects this also requires that it contains results for 2 rounds.
When the batch size (20k) is reached, the function attempts to truncate the results so there are no partial blocks. This function can never succeed if there are >20k transactions.
There is also a bug which prevents the panic from occurring:
		if pos == txnQueryBatchSize {
			// figure out last whole round we got
			lastpos := pos - 1
			lastround := rounds[lastpos]
			lastpos--
			for lastpos >= 0 && rounds[lastpos] == lastround {
				lastpos--
			}
// At this point lastpos is -1 so we fail to trigger the panic.
// Fortunately we crash because of an out of bounds array access later on.
			if lastpos == 0 {
				panic("unwound whole fetch!")
			}
			pos = lastpos + 1
		}

Scope/Requirements
YieldTxns should use intra so that it can support this case.
We need to check that other parts of the code do not rely on the behavior that all transactions for a round are included.
Urgency/Relative Priority

That would also work, but why not just page normally? Do you remember if this was a "feature"?

My design motivations were to load 'at least one round' worth of transactions so that the next query could start on a round boundary; and also to not be RAM bloaty by loading unknown millions of transactions.
I think the round:offset next-token came later. But still that's slightly less good because it's two queries (r=a,i>b)(r>a).
So one part premature optimization and one part making sure the RAM usage of any one query isn't too high. If we make more code follow the round:offset next style we could have smaller buffers if the API has a limit of what it will return.
But I think the other thing YieldTxns() is used for is in accounting, and that internal so can be allowed different properties than API returns.


fitsio: fix float64 formatting #54

fix: Change printing of float64 from %f to %#20g.

Codecov Report

Merging #57 into master will decrease coverage by 1.46%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##           master      #57      +/-   ##
==========================================
- Coverage   69.95%   68.48%   -1.47%
==========================================
  Files          14       14
  Lines        2922     2618     -304
==========================================
- Hits         2044     1793     -251
+ Misses        728      675      -53
  Partials      150      150

Impacted Files
Coverage Δ

utils.go
65.12% <100.00%> (-0.77%)
:arrow_down:

file.go
72.22% <0.00%> (-4.20%)
:arrow_down:

image.go
54.60% <0.00%> (-2.54%)
:arrow_down:

encode.go
51.51% <0.00%> (-2.34%)
:arrow_down:

fltimg/image.go
52.00% <0.00%> (-2.24%)
:arrow_down:

rows.go
87.17% <0.00%> (-1.84%)
:arrow_down:

header.go
66.50% <0.00%> (-1.76%)
:arrow_down:

table.go
58.61% <0.00%> (-0.59%)
:arrow_down:

binary.go
92.76% <0.00%> (-0.41%)
:arrow_down:

... and 5 more

Continue to review full report at Codecov.

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

While re-reading the spec, I realized that the exponent letter need to be uppercased. So I change the formatting to do that and I did add few other test.
I kept the commit separated for review, but I can squash them before the merge.
Ben

(I'll squash when I'll merge that PR in)

needs https://github.com/astrogo/license/pull/5

thanks again.


Add support to publish all tormenta's modules with Scala 2.12

Add support to publish all 2.12 modules

Current coverage is 44.71% (diff: 100%)

Merging #75 into develop will not change coverage

@@            develop        #75   diff @@
==========================================
  Files            14         14
  Lines           123        123
  Methods         118        118
  Messages          0          0
  Branches          5          5
==========================================
  Hits             55         55
  Misses           68         68
  Partials          0          0

Powered by Codecov. Last update d9fa54b...204f74b

👍

👍


Why can't using multiple GPUs speed up the training process?

I tried running the program with the command for dual GPU usage provided in the text, as well as with a single GPU, but it seems that using multiple GPUs did not speed up the code.

The batch size used in this codebase is a per-GPU batch size. By increasing the number of GPUs, you are also increasing the total batch size.


[Flink 7694][REST][Webfrontend]Port JobMetricsHandler to new REST handler

What is the purpose of the change
Port JobMetricsHandler to new REST handler
Brief change log

added JobMetricEntry, JobMetricEntryList, JobMetricId, JobMetricIdList for json serialization. They all implement JobMetricsOverview so the LegacyRestHandler can have a single type of ResponseBody
implemented JobMetricsHandler#handleRequests()
added JobMetricsHeaders

Verifying this change
This change added tests and can be verified as follows:

Added unit tests for marshalling JobMetricIdList and JobMetricEntryList

Does this pull request potentially affect one of the following parts:

Anything that affects deployment or recovery: JobManager (and its components)

Documentation

Does this pull request introduce a new feature? (yes)
If yes, how is the feature documented? (not applicable)

@tillrohrmann  @tzulitai  Hi guys, I want to have you take an early look at my work for porting the handler. I'm haven't fully figured out the following issues:

I don't know where JobMetricsHeaders should fit...
Is there an integration test for this handler?
How to test the job handler manually? I started the flip6 cluster, tried to submit the SocketWindowWordCount example, but I couldn't see a running job on my web UI

It would be really nice if you can write up a single doc explaining the REST API workflow before and after flip6, and have a test manual I can follow.
Thanks!

Do note that you don't have to implement this using the LegacyHandlerAdapter; you could also extend the AbstractRestHandler directly.

Hi @bowenli86, what's the state of this handler? Are you still working on it?

Hi @tillrohrmann , I'm spending time on issues of 1.4.0. This handler is not on my top priority right now. Please feel free to continue working on this if you'd like to :)

Alright, thanks for letting me know.

Once this PR is merged, I'll migrate other metrics handlers and abstract the common code away.

@bowenli86 I am about to finish my work on FLINK-7718, which is quite similar to your ticket. Unfortunately I missed that you are also migrating an implementation of AbstractMetricsHandler. My PR (#5055) is ready to merge so I suggest that we try to rebase your changes on top of mine as soon as it is in the master. If you don't have time to do that, I can take it over. What do you think?

Hi @GJL , you can take over this PR


ModuleNotFoundError: No module named 'lab1'

Hi, quick solution for importing this modules?
ModuleNotFoundError                       Traceback (most recent call last)
 in ()
8 from IPython import display as ipythondisplay
9
---> 10 import introtodeeplearning_labs as util
11
12 is_correct_tf_version = '1.14.0' in tf.version
/content/introtodeeplearning_labs/init.py in ()
----> 1 from lab1 import *
2 from lab2 import *
3 # from lab3 import *
4
5

It is not recognising the folder lab1 and so not importing it directly. I had this issue as well, just find the functions you need and apply them directly.

change introtodeeplearning_labs/init.py:
from .lab1 import *
from .lab2 import *
change lab1/init.py  and  lab2/init.py:
from .util import *


JVM Crash with SIGSEGV on libnet.so NET_POLL

Please provide a brief summary of the bug
I am getting a JVM crash on OpenJDK 11
The core dump created shows a Problematic Frame in "native code" libnet.so NET_POLL
hs_err_pid8831.log
The core dump error is

A fatal error has been detected by the Java Runtime Environment:

SIGSEGV (0xb) at pc=0x00007f7f093a1146, pid=8831, tid=11962

JRE version: OpenJDK Runtime Environment Temurin-11.0.18+10 (11.0.18+10) (build 11.0.18+10)
Java VM: OpenJDK 64-Bit Server VM Temurin-11.0.18+10 (11.0.18+10, mixed mode, tiered, g1 gc, linux-amd64)
Problematic frame:
C  [libnet.so+0xf146]  NET_Poll+0x186

Core dump will be written. Default location: Core dumps may be processed with "/usr/libexec/abrt-hook-ccpp %s %c %p %u %g %t e %P %I %h" (or dumping to /opt/NetScout/rtm/bin/core.8831)

If you would like to submit a bug report, please visit:
https://github.com/adoptium/adoptium-support/issues
The crash happened outside the Java Virtual Machine in native code.
See problematic frame for where to report the bug.

Please provide steps to reproduce where possible
No response
Expected Results
The crash should not happen
Actual Results
JVM crashes
What Java Version are you using?
OpenJDK 64-Bit Server VM Temurin-11.0.18+10
What is your operating system and platform?
CentOS Linux release 7.9.2009
How did you install Java?
No response
Did it work before?
No response
Did you test with the latest update version?
No response
Did you test with other Java versions?
No response
Relevant log output
No response

@kumars1980 Please try 11.0.19 and post back here

Hi, we already have another setup with 11.0.9. The issue is seen there also.

11.0.20 will be coming out this week or next, if you can try and and send in an crash log that would be ace!

@kumars1980 can you try <IP_ADDRESS> and report back?


setup-ebpf.ps1 -Uninstall fails after recompilation

Describe the bug
setup-ebpf.ps1 is not able to uninstall arbitrary efW .msi package. It can only uninstall the identical .msi.
OS information
No response
Steps taken to reproduce bug

Compile, install via setup-ebpf.ps1
Recompile
Executing setup-ebpf.ps1 -Uninstall

Expected behavior
setup-ebpf.ps1 -Uninstall should succeed even if the source code was recompiled.
Actual outcome
setup-ebpf.ps1 -Uninstall fails with:
.\x64\Debug\setup-ebpf.ps1 -Uninstall
PSScriptRoot is C:\Users\lmbauer\ebpf-for-windows\x64\Debug
WorkingDirectory is C:\Users\lmbauer\ebpf-for-windows\x64\Debug
Uninstalling eBPF MSI package at 'msiexec.exe /x C:\Users\lmbauer\ebpf-for-windows\x64\Debug\ebpf-for-windows.msi /qn /norestart /l*v msi-uninstall.log'...
Uninstallation FAILED. Exit code: 1638
MSI uninstallation FAILED. Exit code: 1638.
At C:\Users\lmbauer\ebpf-for-windows\x64\Debug\setup-ebpf.ps1:45 char:9
+         throw ("MSI uninstallation FAILED. Exit code: $($process.Exit ...
+         ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : OperationStopped: (MSI uninstallat...xit code: 1638.:String) [], RuntimeException
    + FullyQualifiedErrorId : MSI uninstallation FAILED. Exit code: 1638.

Additional details
No response

The setup script should try to uninstall using the cached MSI.


Hydra service fails to correctly set PostgreSQL configuration when services.postgresql.authentication is already set

Issue description
The Hydra module for NixOS contains a configuration setting that, on deployments with a local PostgreSQL database, is meant to add an authentication line to the pg_hba.conffor PostgreSQL to allow access to all Hydra-related users.
However, when the services.postgresql.authentication option is already set elsewhere in the system configuration, this line does not get added due to conflicting options - or presumably, the existing authentication configuration could be overwritten by the Hydra-specified configuration in different circumstances.
Instead, the Hydra service should append this authentication line to the existing authentication configuration when one already exists.
Workaround in the meantime: manually add local hydra all ident map=hydra-users to your services.postgresql.authentication configuration option, wherever you have currently specified it.
For the issue search: the following is the error that shows in Hydra when authentication fails due to this issue:
DBIx::Class::Storage::DBI::catch {...} (): DBI Connection failed: DBI connect('dbname=hydra;user=hydra;','',...) failed: FATAL: Peer authentication failed for user "hydra" at /nix/store/76s6zdh8m1zvr1rclvfsvpn1k3y7vjrl-hydra-perl-deps/lib/perl5/site_perl/5.24.3/DBIx/Class/Storage/DBI.pm line 1517. at /nix/store/f9vv25rfq30k03r8dsjb25g9hbl8jpjn-hydra-2017-11-21/libexec/hydra/lib/Hydra/Helper/CatalystUtils.pm line 356

... and the PostgreSQL service logs show the following:
Nov 26 09:28:34 desktop-home postgresql-start[29383]: LOG:  provided user name (hydra) and authenticated user name (hydra-queue-runner) do not match
Nov 26 09:28:34 desktop-home postgresql-start[29383]: FATAL:  Peer authentication failed for user "hydra"
Nov 26 09:28:34 desktop-home postgresql-start[29383]: DETAIL:  Connection matched pg_hba.conf line 1: "                                local all all ident"

Steps to reproduce

Enable the PostgreSQL service and add a services.postgresql.authentication option to your system configuration (eg. /etc/nixos/configuration.nix).
Enable the Hydra service; the exact configuration does not matter, so long as you do not specify a services.hydra.dbi option and let it default to the local database.
Load the Hydra web interface at the configured port (default: 3000).

For completeness' sake, below is my Hydra configuration:
    services.hydra = {
        enable = true;
        port = 3333;
        hydraURL = "http://localhost:3333/";
        notificationSender =<EMAIL_ADDRESS>        useSubstitutes = true;
        minimumDiskFree = 20;
        minimumDiskFreeEvaluator = 20;
    };

Technical details

system: "x86_64-linux"
host os: Linux 4.9.61, NixOS, 17.09.2182.7f6f0c49f0 (Hummingbird)
multi-user?: yes
sandbox: no
version: nix-env (Nix) 1.11.15
channels(sven): ""
channels(root): "nixos-17.09.2182.7f6f0c49f0"
nixpkgs: /nix/var/nix/profiles/per-user/root/channels/nixos/nixpkgs

@joepie91 do you still have this issue?


Add files via upload

Apologies, we have already completed the Zhejiang testing and no longer are supporting changes via CLWP after the hard fork

I'll go ahead and review the pull request, but if you will need to submit the request yourself to a node. Cheers

Ok, thank you anyway for your guidance,


Custom 3D model?

How can I add a custom 3D model?  What rigging should it have?

The class supports full-body Ready Player Me avatars (GLB). Here is an example that you can download:
https://models.readyplayer.me/64bfa15f0e72c63d7c3934a6.glb?morphTargets=ARKit,Oculus+Visemes,mouthOpen,mouthSmile,eyesClosed,eyesLookUp,eyesLookDown&textureSizeLimit=1024&textureFormat=png
Their rig has a Mixamo-compatible bone structure described here:
https://docs.readyplayer.me/ready-player-me/api-reference/avatars/full-body-avatars
Please note that contrary to what is mentioned on that page, the texture atlassing is off by default. Therefore, as of now, the class assumes the presence of separate meshes for 'EyeLeft', 'EyeRight', 'Wolf3D_Head', and 'Wolf3D_Teeth'.
For lip-sync and facial expressions, you also need to have ARKit and Oculus compatible blend shapes (including the additional ones) all listed here:
https://docs.readyplayer.me/ready-player-me/api-reference/avatars/morph-targets/apple-arkit
https://docs.readyplayer.me/ready-player-me/api-reference/avatars/morph-targets/oculus-ovr-libsync

I just updated the TalkingHead class to support texture atlas, thus eliminating the need for separate meshes. I will close this issue, but feel free to ask further questions if any.


Add api to programmatically change the style of status bar for ios

Issue details
If an app draws under the status bar then it could be very useful to be able to change the style of the status bar (f.e. if app background is light then programmatically set the status bar style as Dark).
There is a deprecated method UIApplication.setStatusBarStyle() but Apple suggests to override UIViewController.getPreferredStatusBarStyle() to change the style. Seems the same thing is already done in LibGDX to change the visibility of status bar via overridingUIViewController.prefersStatusBarHidden() in IOSGraphics.IOSUIViewController to return 'visibility' value from IOSApplicationConfiguration.statusBarVisible.
Is it possible to add a field public UIStatusBarStyle statusBarStyle into IOSApplicationConfiguration and override UIViewController.getPreferredStatusBarStyle() in IOSGraphics.IOSUIViewController to return app.config.statusBarVisible value?
Version of LibGDX and/or relevant dependencies
1.9.10
Please select the affected platforms

[x] iOS (robovm)

I think this is an edge case, so instead of a change to libgdx you can inject your own UIViewController overriding the method.
In IosLauncher:
   IOSApplication app = new IOSApplication(game, config) {
        @Override
        protected IOSGraphics.IOSUIViewController createUIViewController(IOSGraphics graphics) {
            return new MyUIViewController(this, graphics);
        }

And new file:
public class MyUIViewController extends IOSGraphics.IOSUIViewController {
    protected MyUIViewController(IOSApplication app, IOSGraphics graphics) {
        super(app, graphics);
    }

   // override here

Closing this. If you think you cannot use my given solution, please reopen.


cmd/go: "ldflags -X" variable setting does not error on bad paths

What version of Go are you using (go version)?
1.12 or 1.11
Does this issue reproduce with the latest release?
The latest release on Docker, yes, I have not tried master
What operating system and processor architecture are you using (go env)?
The golang:1.12 docker.
What did you do?
go run -ldflags "-X bad/path/bob.Worked=yes" alpha.go
What did you expect to see?
Some error telling me that I have a bad path.
What did you see instead?
The build succeeded and ran.
Discussion
The project I work on recently updated the version of Go we are using, and as part of the update some of the variables we are setting using ldflags "-X" stopped getting set because the path we were using was no longer recognized. I know that that mechanism changed, and that is not my objection.
Rather my objection is that the builds continued on without any errors to say we were now trying to set variables on modules that did not exist in the build. There should have been build-breaking errors to prompt us to figure out the problem immediately.

@larkost-fetch - would you mind providing some more information about this issue, specifically a code sample and the output that you received after running that command?

I couldn't find the issue, but this is an explicit decision, because some build systems pass the same -X options to all programs, but not all programs include the variables being set.  The -X option intentionally sets the variable if present and does nothing if absent.


New Mendix Cloud region

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.0 out of 2 committers have signed the CLA.:x: Sarel Joubert:x: loadpiSarel Joubert seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.


API logs for airlock endpoints are in ERROR level

All airlock logs are marked as "error", even though they are supposed to be INFO

This is probably a bug in Azure, since in App Insights the look appear in the correct way.
However, there is log duplication whenever debugging


docs: update the spec with how square construction is currently implemented

Ref: https://github.com/celestiaorg/celestia-app/pull/1905#discussion_r1228034039_

are we still planning on adding more here or can we close this?

bump @cmwaters , is this still currently being worked on or can we remove assignment?


Remove console.log

Just remove the console.log that remain in hsl function :)

This is in the 1.2.1 release that is now in the nam registry, thanks.


Unable to retrieve data from AEMET

Hi there, thanks for this great component. I've been finding this issue lately
Unable to retrieve data from AEMET. HTTPSConnectionPool(host='opendata.aemet.es', port=443): Max retries exceeded with url: /opendata/api/observacion/convencional/datos/estacion/1505?api_key=secret (Caused by SSLError(SSLError("bad handshake: Error([('SSL routines', 'tls_process_server_certificate', 'certificate verify failed')])")))
what's weird about it is that if I go to opendata.aemet.es/opendata/api/observacion/convencional/datos/estacion/1505?api_key=secret
data shows up as it should
thanks in advanced

Same in here ... I can see also this error:
ssl.SSLCertVerificationError: [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: unable to get local issuer certificate (_ssl.c:1108)
It may be related to the latest HA 113 version
Thanks for making this great component for the Spaniards 👍

This problem has nothing to do with the component but with the remote server. The best solution is to fix the website. And that's out of my hands.
If a check is made in SSL Labs we can find among the conclusions that: "This server's certificate chain is incomplete"
The opendata.aemet.es web server is apparently incorrectly configured. Precisely the error that is being reported is that the SSL certificate cannot be verified
On our side, we could ignore any certificate error by modifying line 141 of the aemet/aemet.py file
response = requests.get(data_url, params=params, verify=False)

I am wondering whether this would be a final solution or whether it would be irresponsible of me to skip the check.
Maybe you find that I make this change in a future but right now you should modify it by your self in your local copy.

one last thing, I'm a newbie so.. is this really unsafe to set the verify=False?

Si no se verifica la conexión cualquiera puede ponerse en medio de la comunicación y hacer un ataque de MITM.
https://web.archive.org/web/20170829220032/http://www.cs.utexas.edu/~shmat/shmat_ccs12.pdf

Muchas gracias :)


WIP added more quaternion methods

@yyassa This is the PR for the required quaternion methods. We need to provide 100 % test coverage to bring this in!
In the diff you can see that I did one example for a test.

@yyassa I implemented almost all tests, just one function missing.

Great work! One consideration is that axis angle could derive from vector 3. This would be more aligned with the conversion in the rest of the library:
For instance, this is what I would expect the conversion from euler to axis-angle would look like to the end user.
Euler euler(1,2,3);
AxisAngle axisAngle(euler);
Vector3 axis = axisAngle.axis();
float angle = axisAngle.angle();

AxisAngle axisAngle2(10, 0, 0); // angle 10, axis (1,0,0);

@jgoppert That's a good idea. Let me finish this up and after that I can add the axis angle class,

Manually merged.


[ENH] Faster and more flexible code, and code sharing for kernel tests

Towards: #15
Changes proposed in this pull request:

refactors code to setup for kcd test
allows any of the pairwise kernel strings to be passed in from sklearn (which is significantly faster than using partial because sklearn optimizes the in-house kernels)
also requires kernel functions to be a specific API, so it's easier to test, implement and document

This should all make implementation of the kcd test pretty straightforward
Before submitting

[ ] I've read and followed all steps in the Making a pull request
section of the CONTRIBUTING docs.
[ ] I've updated or added any relevant docstrings following the syntax described in the
Writing docstrings section of the CONTRIBUTING docs.
[ ] If this PR fixes a bug, I've added a test that will fail without my fix.
[ ] If this PR adds a new feature, I've added tests that sufficiently cover my new functionality.
[ ] I have added a changelog entry succintly describing the change in this PR in the whats_new relevant version document.

After submitting

[ ] All GitHub Actions jobs for my pull request have passed.

Tldr re: https://github.com/py-why/pywhy-stats/pull/19#discussion_r1287466282
I will put up a sep commit after Neurips rebuttal period is over to see if we can converge :)

Can you investigate the failing checks?

@bloebp lmk wdyt. I addressed the two issues:

use RNG, so the seed does not universally affect the tests
I refactored, but I think there might be still a discrepancy:

on one hand pairwise_kernels can take a callable that is defined on (X, Y) 1D row vectors and will run a joblib parallelization
on the other hand if you define your own kernel callable that can compute this in a vectorized fashion, then you want to do that.

E.g.
    def my_custom_kernel(X):
        # X here is multidimensional, where the first dimension is continuous and the second categorical. We can handle
        # this by combining two kernels.
        return delta_kernel(X[:, 0].reshape(-1, 1)) * rbf_kernel(X[:, 1].reshape(-1, 1))

we want to call directly, but for the following, we would want to call it via pairwise_kernels.
def unvectorizable_pairwise_kernel(X, Y=None):
     ...

Should we have a rule that if the number of arguments in the kernel callable is exactly 1, then it is assumed to be some optimized kernel callable that is already vectorized and hence should be called directly?
Otoh, if not, then it is better to pass it through pairwise_kernels

I addressed the issue above and just made it clear that we assume the following:
If the metric is a callable, it will have either one input for ``X``, or two inputs for ``X`` and
    ``Y``. If one input is passed in, it is assumed that the kernel operates on the entire array to compute
    the kernel array. If two inputs are passed in, then it is assumed that the kernel operates on
    pairwise row vectors from each input array. This callable is parallelized across rows of the input
    using :func:`~sklearn.metrics.pairwise.pairwise_kernels`. Note that ``(X, Y=None)`` is a valid input
    signature for the kernel function and would then get passed to the pairwise kernel function. If
    a callable is passed in, it is generally faster and more efficient if one can define a vectorized
    operation that operates on the whole array at once. Otherwise, the pairwise kernel function will
    call the function for each combination of rows in the input arrays.

@bloebp I will let you merge if it looks good to you


Provide permalink for agents comparison

Sometimes you want to send comparison to your colleagues, for this it would be great to have a permalink to agents diff.

Added permalink to diff page


made webshell wasm+xtermjs usable, but feats still missing

preparing webshell (shell in a browser) which is wasm version of Rye + xterm.js. Main part is handled by new MicroLiner which is much more minimal rewrite with similar behavior than peterh/liner. I will commits to this PR. Just wanted to see what the CI shows. Linter will require some cleanup of empty branches, if not else at this point.
More about webshell here: https://www.reddit.com/r/ryelang/comments/19djs4k/rye_webshell_stdout_works/

Would be nice to have an online playground like https://go.dev/play/ with some samples and examples.
I know there is https://ryelang.org/nauci-se/ but that is a linear walk-trough tutorial.

Would be nice to have this as an online playground like https://go.dev/play/ with some samples and examples.
I know there is https://ryelang.org/nauci-se/ but that is a linear walk-trough tutorial.

Yes, something similar is in plans. First, I wanted to experiment with trying to add "try it live" for every code block in https://ryelang.org/meet_rye/ (which I also need to continue writing).
But something more similar to a Go playground with multiple examples would also be nice, yes. I plan to integrate browser based code editor + webshell so the experience would be even more interactive. And Rye also has "enter-console" function, which still makes me wonder about possibilities with it in development / experiment process, and  it will be easier to try in such browser setup.


Modexpw-107

Use "application/vnd.api+json" accept content type
Throw exception if export fields are empty
Merge jobParams (recordId, recordType, et.) to one exportConfig object
Set offset 1 instead of 0 (page 0 gives error from kb-ebsco module)

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


Docker image issues

Using the Docker image, multiple issues occur:

Fatal error: Allowed memory size of 134217728 bytes exhausted
Failed to download wsdltophp/packagebase from dist: The zip extension and unzip command are both missing, skipping.

fixed in https://github.com/WsdlToPhp/PackageGenerator/releases/tag/3.3.3 and https://github.com/WsdlToPhp/PackageGenerator/releases/tag/2.12.3