failed to register devices udid

I recently got to know fastlane,it is an amazing tool,it saves me mass time.The issue is when I try to register like below ,it gives error,
[12:58:02]: Please provide a file according to the Apple Sample UDID file     (https://devimages.apple.com.edgekey.net/downloads/devices/Multiple-Upload-Samples.zip) ,
I did,but it still no luck.Weirdly I can manually do it with exactly the same Devices.txt file from safari .
register_devices(
devices_file: './Devices.txt'
)

Would you mind sharing your devices_file? Feel free to remove parts of the UDIDs 👍

The output :
+------------------+-------------+
|          Lane Context          |
+------------------+-------------+
| DEFAULT_PLATFORM | ios         |
| PLATFORM_NAME    | ios         |
| LANE_NAME        | ios release |
+------------------+-------------+
[16:07:13]: Please provide a file according to the Apple Sample UDID file (https://devimages.apple.com.edgekey.net/downloads/devices/Multiple-Upload-Samples.zip)
+------+-------------------------------------+-------------+
|                     fastlane summary                     |
+------+-------------------------------------+-------------+
| Step | Action                              | Time (in s) |
+------+-------------------------------------+-------------+
| 1    | Verifying required fastlane version | 0           |
| 2    | default_platform                    | 0           |
| 💥   | register_devices                    | 4           |
+------+-------------------------------------+-------------+
[16:07:13]: fastlane finished with errors
[!] Please provide a file according to the Apple Sample UDID file (https://devimages.apple.com.edgekey.net/downloads/devices/Multiple-Upload-Samples.zip)
Devices.txt File:
Devices.txt
Fastfile lane release:
lane :release do
# match(type: "appstore")
# snapshot
# gym # Build your app - more options available
# deliver(force: true)
# frameit
#cert
register_devices(
      devices_file: './fastlane/Devices.txt'
    )

end

fastlane env
✅ fastlane environment ✅
Stack

Key
Value

OS
10.12.2

Ruby
2.2.4

Bundler?
false

Git
git version 2.10.1 (Apple Git-78)

Installation Source
~/.fastlane/bin/bundle/bin/fastlane

Host
Mac OS X 10.12.2 (16C67)

Ruby Lib Dir
~/.fastlane/bin/bundle/lib

OpenSSL Version
OpenSSL 1.0.2g  1 Mar 2016

Is contained
false

Is homebrew
true

Xcode Path
/Applications/Xcode.app/Contents/Developer/

Xcode Version
8.2.1

System Locale

Variable
Value

LANG
en_US.UTF-8
✅

LC_ALL
en_US.UTF-8
✅

LANGUAGE
en_US.UTF-8
✅

fastlane files:
`./fastlane/Fastfile`
# Customise this file, documentation can be found here:
# https://github.com/fastlane/fastlane/tree/master/fastlane/docs
# All available actions: https://docs.fastlane.tools/actions
# can also be listed using the `fastlane actions` command

# Change the syntax highlighting to Ruby
# All lines starting with a # are ignored when running `fastlane`

# If you want to automatically update fastlane if a new version is available:
# update_fastlane

# This is the minimum version number required.
# Update this, if you use features of a newer version
fastlane_version "2.17.0"

default_platform :ios

platform :ios do
  before_all do

  end
  desc "Runs all the tests"
  lane :test do
    scan
  end

  desc "Submit a new Beta Build to Apple TestFlight"
  desc "This will also make sure the profile is up to date"
  lane :beta do
    # match(type: "appstore") # more information: https://codesigning.guide
    gym # Build your app - more options available
    pilot

    # sh "your_script.sh"
    # You can also use other beta testing services here (run `fastlane actions`)
  end

  desc "Deploy a new version to the App Store"
  lane :release do
    # match(type: "appstore")
    # snapshot
    # gym # Build your app - more options available
    # deliver(force: true)
    # frameit
    #cert

    register_devices(
        devices_file: './fastlane/Devices.txt')
  end

  # You can define as many lanes as you want

  after_all do |lane|
    # This block is called, only if the executed lane was successful

    # slack(
    #   message: "Successfully deployed new App Update."
    # )
  end

  error do |lane, exception|
    # slack(
    #   message: exception.message,
    #   success: false
    # )
  end
end

# More information about multiple platforms in fastlane: https://github.com/fastlane/fastlane/blob/master/fastlane/docs/Platforms.md
# All available actions: https://docs.fastlane.tools/actions

# fastlane reports which actions are used
# No personal data is recorded. Learn more at https://github.com/fastlane/enhancer

`./fastlane/Appfile`
app_identifier "com.exampe.app" # The bundle identifier of your app
apple_id<EMAIL_ADDRESS># Your Apple email address

team_id "team_id_value"  # Developer Portal Team ID such as AFHHENDHD

# you can even provide different app identifiers, Apple IDs and team names per lane:
# More information: https://github.com/fastlane/fastlane/blob/master/fastlane/docs/Appfile.md

fastlane gems

Gem
Version
Update-Status

fastlane
2.17.1
✅ Up-To-Date

Loaded fastlane plugins:
No plugins Loaded
Loaded gems

Gem
Version

slack-notifier
1.5.1

i18n
0.7.0

json
1.8.1

thread_safe
0.3.5

tzinfo
1.2.2

minitest
5.4.3

activesupport
<IP_ADDRESS>

CFPropertyList
2.3.5

claide
1.0.1

colored
1.2

nanaimo
0.2.3

xcodeproj
1.4.2

rouge
1.11.1

xcpretty
0.2.4

terminal-notifier
1.7.1

unicode-display_width
1.1.3

terminal-table
1.7.3

plist
3.2.0

public_suffix
2.0.5

addressable
2.5.0

multipart-post
2.0.0

word_wrap
1.0.0

tty-screen
0.5.0

babosa
1.0.2

highline
1.7.8

commander
4.4.3

excon
0.54.0

faraday
0.11.0

unf_ext
<IP_ADDRESS>

unf
0.1.4

domain_name
0.5.20161129

http-cookie
1.0.3

faraday-cookie_jar
0.0.6

fastimage
2.0.1

gh_inspector
1.0.3

uber
0.0.15

representable
2.3.0

retriable
2.1.0

mime-types-data
3.2016.0521

mime-types
3.1

hurley
0.2

little-plugger
1.1.4

multi_json
1.12.1

logging
2.1.0

jwt
1.5.6

memoist
0.15.0

os
0.9.6

signet
0.7.3

googleauth
0.5.1

httpclient
2.8.3

google-api-client
0.9.26

mini_magick
4.5.1

multi_xml
0.6.0

rubyzip
1.2.0

security
0.1.3

xcpretty-travis-formatter
0.0.4

dotenv
2.2.0

bundler
1.14.3

faraday_middleware
<IP_ADDRESS>

generated on: 2017-02-18

Hi, I think I know  the problem,It is about the \t ，in my case I hit  tab  on keyboard when I add device and remake the Device.txt file.
[linesNew insertObject:@"Device ID    Device Name" atIndex:0];
Then yesterday I try to change to
[linesNew insertObject:@"Device ID\tDevice Name" atIndex:0];
Then it's good to go.I think Apple is not that sensitive to the space or the \t

Thanks for following up with that @damoncoo! It's great to know that Apple is sensitive to \t. Going to close this issue for now, but please feel free to continue conversation here if there are more issues! 🐙 🚀


Updating web example links to webtest

Ola's PR https://github.com/openmicroscopy/openmicroscopy/pull/4023 removed the web examples as they are now in webtest, this updates the link in the web developer docs to point at the new location.

If the example list ends up growing we might want to create an extlink and start listing the various examples in a table. Merging as it is given the state of https://ci.openmicroscopy.org/job/OMERO-5.1-merge-docs/620/.

--rebased-to #1271


feat(chunk-proposer): include Curie block in a sole chunk

Purpose or design rationale of this PR
PR title
Your PR title must follow conventional commits (as we are doing squash merge for each PR), so it must start with one of the following types:

[x] feat: A new feature

Codecov Report
Attention: Patch coverage is 66.66667% with 3 lines in your changes are missing coverage. Please review.

Please upload report for BASE (feat-rollup-relayer-add-zstd-compression@570cea6). Learn more about missing BASE report.

Files
Patch %
Lines

...llup/internal/controller/watcher/chunk_proposer.go
66.66%
2 Missing and 1 partial :warning:

Additional details and impacted files
@@                             Coverage Diff                             @@
##             feat-rollup-relayer-add-zstd-compression    #1353   +/-   ##
===========================================================================
  Coverage                                            ?   54.31%
===========================================================================
  Files                                               ?      156
  Lines                                               ?    11922
  Branches                                            ?        0
===========================================================================
  Hits                                                ?     6475
  Misses                                              ?     4952
  Partials                                            ?      495

Flag
Coverage Δ

rollup
59.83% <66.66%> (?)

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

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

LGTM, might need to bump version.

yes. the pr is added based on codecv2 pr, because branch develop has not added codecv2 yet.


fix debian init script

My git user has it's shell set to /bin/false, which makes su -c impossible, also a flag was misplaced and this fixes that the test run is executed as root. (#1025)
Disclaimer: I'm not an experienced Debian nor System-V init user, maybe someone could review this commit before it gets merged.
(This is the same as this gogs PR)

Thanks, that looks fine.


Should the backup start from the end?

Should the backup start from the end (i.e. from the oldest messages to the newest)? This would avoid needing to know the last saved message ID to continue from there.

This is not the best option because it would involve negative offsets (something which may not be possible), and we cannot simply subtract the download chunk size from the message ID, because if a message was deleted, then the ID gap would be larger.


Help with lambda layer

Can you provide an example to how deploy this package as lambda layer? For example, in chrome-aws-lambda use this command to build a .zip file to upload to AWS Lambda Layer
git clone --depth=1 https://github.com/alixaxel/chrome-aws-lambda.git && \
cd chrome-aws-lambda && \
make chrome_aws_lambda.zip

EDIT:
I found a solution: add Makefile to this project for use the same command as chrome-aws-lambda. Also, I made a pull request with this change. Tell me if you need more info.

<EMAIL_ADDRESS>or
https://medium.com/appgambit/part-1-getting-started-with-aws-lambda-layers-1677a6b006


Smooth value transition as additional syntax element.

Feature similar to Hover in issue#8. Make a smooth transition in [value]. "For" statement should be helpful.
Example:
ard button P5 smooth-255-0
ard button P5 255-0
ard button P5 255->0
ard button P5 255>>0
or define transition speed:
slow > normal >> fast >>>
or something similar allowed to use in CSS
255 - beginning value
0 - value to fade out
Example Usage: Smoothly blink LED or move servo.
This should be acceptable for elements like hover, button, increase-decrease, radio, checkbox and toggle.

It's impossible to support this for every object (non-dynamic), this require complete redesign of Inovlt functions.


SYSTEMML-1737 BufferedReader should be closed in ParameterizedBuiltinCPFileInstruction#createCellResultFile()

Can an Admin verify this patch?

LGTM - thanks @tedyu


[Snyk] Security upgrade python from 3.6-slim to 3.13-slim

Snyk has created this PR to fix 4 vulnerabilities in the dockerfile dependencies of this project.
Keeping your Docker base image up-to-date means you’ll benefit from security fixes in the latest version of your chosen image.
Snyk changed the following file(s):

components/kubeflow/kfserving/Dockerfile

We recommend upgrading to python:3.13-slim, as this image has only 37 known vulnerabilities. To do this, merge this pull request, then verify your application still works as expected.
Vulnerabilities that will be fixed with an upgrade:

Issue
Score

Out-of-bounds Write SNYK-DEBIAN11-GLIBC-5927133
  829

Out-of-bounds Write SNYK-DEBIAN11-GLIBC-5927133
  829

Use After Free SNYK-DEBIAN11-GLIBC-1296898
  714

OS Command Injection SNYK-DEBIAN11-OPENSSL-2807596
  714

OS Command Injection SNYK-DEBIAN11-OPENSSL-2933518
  714

[!IMPORTANT]

Check the changes in this PR to ensure they won't cause issues with your project.
Max score is 1000. Note that the real score may have changed since the PR was raised.
This PR was automatically created by Snyk using the credentials of a real user.

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.
For more information:
🧐 View latest project report
📜 Customise PR templates
🛠 Adjust project settings
📚 Read about Snyk's upgrade logic

Learn how to fix vulnerabilities with free interactive lessons:
🦉 OS Command Injection
🦉 Use After Free

Commit Checker results:
**NOTE**: These are the results of the commit checker scans.
If these are not commits from upstream kfp, then please ensure
you adhere to the commit checker formatting

commitchecker verson unknown
Validating 1 commits between 1f957b5450ebe29dce30035bb85757becb90ee47...961adba8149939fcbda73accd3f29658c71cf364

UPSTREAM commit 961adba has invalid summary fix: components/kubeflow/kfserving/Dockerfile to reduce vulnerabilities.

The Data Science Pipelines team recommends testing this using the Data Science Pipelines Operator.  Check here for more information on using the DSPO.
To use and deploy a DSP stack with these images (assuming the DSPO is deployed), first save the following YAML to a file named dspa.pr-89.yaml:
apiVersion: datasciencepipelinesapplications.opendatahub.io/v1alpha1
kind: DataSciencePipelinesApplication
metadata:
  name: pr-89
spec:
  dspVersion: v2
  apiServer:
    image: "quay.io/opendatahub/ds-pipelines-api-server:pr-89"
    argoDriverImage: "quay.io/opendatahub/ds-pipelines-driver:pr-89"
    argoLauncherImage: "quay.io/opendatahub/ds-pipelines-launcher:pr-89"
  persistenceAgent:
    image: "quay.io/opendatahub/ds-pipelines-persistenceagent:pr-89"
  scheduledWorkflow:
    image: "quay.io/opendatahub/ds-pipelines-scheduledworkflow:pr-89"
  mlmd:
    deploy: true  # Optional component
    grpc:
      image: "quay.io/opendatahub/mlmd-grpc-server:latest"
    envoy:
      image: "registry.redhat.io/openshift-service-mesh/proxyv2-rhel8:2.3.9-2"
  mlpipelineUI:
    deploy: true  # Optional component
    image: "quay.io/opendatahub/ds-pipelines-frontend:pr-89"
  objectStorage:
    minio:
      deploy: true
      image: 'quay.io/opendatahub/minio:RELEASE.2019-08-14T20-37-41Z-license-compliance'

Then run the following:
cd $(mktemp -d)
git clone git@github.com:opendatahub-io/data-science-pipelines.git
cd data-science-pipelines/
git fetch origin pull/89/head
git checkout -b pullrequest 961adba8149939fcbda73accd3f29658c71cf364
oc apply -f dspa.pr-89.yaml

More instructions here on how to deploy and test a Data Science Pipelines Application.


feat: add support for oauth

Purpose

This pr add oauth support for hypercrx and users needn't to generate token on their own
https://github.com/settings/apps/
https://docs.github.com/en/developers/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps

This feature introduces a new faas backend service to help oauth login.  The backend service is not always needed and it's possible to do all the oauth in front-end side, if considering exposing the client_secret to the public:

When publishing a release, these configuration need be changed:
https://github.com/LiuChangFreeman/hypertrons-crx/commit/a4042f78a99bb3525bd1742d27ed41ad27005d1c#diff-13094b0041abdfbae45251ebf8c82f9ba73b446ac3157d28e46362862d0f8a04

Better persona

Proposed changes
Describe the big picture of your changes here to communicate to the maintainers why we should accept this pull request. If it fixes a bug or resolves a feature request, be sure to link to that issue.
Open Questions and Pre-Merge TODOs

[ ] Use github checklists. When solved, check the box and explain the answer.

Types of changes
What types of changes does your code introduce to hypertrons-crx?
Put an x in the boxes that apply

[ ] Bugfix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Documentation Update (if none of the other choices apply)

Approach
How does this change address the problem?
Checklist
Put an x in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your code.

[x] I have read the CONTRIBUTING doc
[x] I have signed the CLA
[ ] Lint and unit tests pass locally with my changes
[ ] I have added tests that prove my fix is effective or that my feature works
[x] I have added necessary documentation (if appropriate)

Further comments (Optional)
If this is a relatively large or complex change, kick off the discussion by explaining why you chose the solution you did and what alternatives you considered, etc...
Links to blog posts, patterns, libraries or addons used to solve this problem

 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.


Error in the Qgis log panel, then the QUICKSM

@Tshepo-Mokwaledi the reported issue is related to the QuickOSM plugin, not the QGIS Website. Please close this issue report and report the issue to the QuickOSM plugin devs https://github.com/3liz/QuickOSM/issues.


identity collisions diagnostics test and fixes

motivation: there are several use cases where identity collisions cause resolution errors with misleading diagnostics. We added several test cases to capture these cases, as a basis for improving identity collisions (some of them are legitimate use cases) or at the minimum by finding ways to emit more helpful / accurate diagnostics.
changes:

add several test cases to capture use cases of identity collisions
diagnose potential identity collisions and emit more actioable error messages
add FIXME highlighting where some of the issues are coming from

@swift-ci please smoke test

@swift-ci please smoke test


assertFalse has wrong name

Is your feature request related to a problem? Please describe.
Not sure what the prospects of changing this are given that assert is 1.x, but assertFalse has the wrong name (should be assertFalsy):
type Falsy = false | 0 | 0n | "" | null | undefined;
declare function assertFalse(expr: unknown, msg?: string): asserts expr is Falsy;

Describe the solution you'd like
Maybe rename to assertFalsy and deprecate assertFalse?
Describe alternatives you've considered
Do nothing

assertFalsy was also suggested when we first discussed this feature, but we decided on this name because there are many prior examples in other languages and libraries https://github.com/denoland/std/issues/2045
I personally think assertFalse is acceptable as it's conventional name in software ecosystem in general

There were also suggestions of renames like:

assertStrictEquals -> assertIs
assertEquals -> assertAlike

(I guess these are in similar direction)
But they didn't get much attention from the community https://github.com/denoland/std/issues/3513#issuecomment-1667112415

From the examples in other languages/frameworks listed in https://github.com/denoland/std/issues/2045#issuecomment-1108127613, it looks like all of them except Python's unittest strictly mean "false" rather than "falsy". Tbh doesn't seem like there's much utility in having functions that only check one specific value, given that assertEquals(val, false) works just as well. I think the only way such a function is useful at all is if it means "falsy", and even then that's only preferable over assert(!val) because it enables type narrowing in TS Actually, it looks looks like TS is now able to narrow on assert(!val), so maybe there's not much utility to this function regardless of exact semantics.
In any case, using "false" to mean "falsy" strikes me as confusing, especially given the precedent in other testing frameworks to include such strictly-equal-to-a-specific-value functions.
Happy to close this issue if the chances of changing it are slim-to-none.


License

Hey everyone,
what is the license of this project? I tried to find it but if no success.
thanks

It's as permissive as https://schema.org/docs/terms.html will allow.

thanks for the feedback @webmasterkai !
I am asking that to check if it is a opensource project and maybe contribute to this project.
it seems it uses cc-by-sa but for software it is not recommended https://creativecommons.org/faq/#can-i-apply-a-creative-commons-license-to-software
currently we are implement schema.org types on graphql but it could be very hard to do it manually .. so I am investigante what options we have now.
thanks @webmasterkai !

If you want to make a PR that includes a license file to your liking I'd be more than happy to merge it :-)

Awesome, thanks again!

thanks @webmasterkai !


Emit verify-certificate only when default verifier fails

The only use case of verify-certificate is to allow untrusted certificates, so we don't need to emit it when the certificate is trusted.

IMHO, this defeats the purpose of the API. #3318 is no longer resolved

@steelbrain What is the use case of manually verifying a trusted certificate?

@zcbenz There are certain orgs that don't trust all the CAs, they trust just a few and often pin those verified certificates. My original use case was a similar one

@steelbrain That's interesting, I'll come with a solution.


Please elaborate the process to install silq in any arch linux derivative(specifically needed for blackarch linux).

I am unable to install silq in my Blackarch Linux OS. I want to install it in terminal since I don't use any IDE's. I code in vim through terminal and then compile or interpret it with respective compiler or interpreter of the concerned language. Here, I want to do the same. Please tell me the steps to install in it my terminal and run it through commands as I request.

What is precisely your issue? Which step of the instructions is failing and with what error message?

Closing this issue now as it is unclear and inactive, feel free to reopen if you want to provide further details.


Features

Added new Commands like:
!roles
!removeRoles
!apod
Also added: StartUp message

bypass branch Protection lol


Roadmap for Static elements feature

Hi, have you got a roadmap for Static elements feature?
Thank you

Hi, we have no roadmap, sorry.  Its one of the next features to be implemented.

Hi, is there any update on this one?

Up


feat: record transaction type

when we call a transaction, the output summary contains a .transactionType which is set to READ
or WRITE.
BREAKING CHANGE: If a generated session calls readTransaction() or writeTransaction(), the
result will have in it's summary a transactionType set to READ or WRITE.  So if you are
asserting deep equality between the output summary and expected summary, you will have to update the
expected summary accordingly.
fix #38

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Update code to be compatibility with Swift 3.1

Convert all methods deprecated from Swift 2 to Swift 3.1
Tested and run using Xcode 8.3.1 using Swift 3.1

How to download swift 3.1 code


OTEL Distributed Tracing not showing up for Kafka broker and trigger portion

Describe the bug
Was following the tracing setup here, https://knative.dev/blog/articles/distributed-tracing/
Example was using the default InMemoryChannel prior and the full tracing showed up in jaeger UI, as per the example.
Tracing not showing up after changing over to Kafka broker and trigger

Expected behavior
Full end to end tracing, similar to the example with inMemoryChannel

To Reproduce
Kafka was setup using strimzi operator,
Kafka Broker setup using steps here https://knative.dev/docs/eventing/broker/kafka-broker/#installation
Tracing setup (otel collector, jaeger UI) was followed fully from  https://knative.dev/blog/articles/distributed-tracing/
Knative release version
Knative v 1.2
Used the latest eventing-kafka-broker, knative-v1.2.3
Additional context
Have tried using zipkin collector as well, having the same issue (IMC tracing appears, but not kafka components)
Saw #1546 , Not sure if this is the solution to the issue I'm facing. Tried updating the configmap and added heads-format with value b3, but did not seem to work.
Maybe I'm doing something wrong, any help will be appreciated

hi @pierDipi , have restarted all the kafka deployments using kubectl rollout restart, and the kafka traces are appearing as expected.
Thanks alot, much appreciated!

Thanks for the update, closing


Lost parameter annotation in method, when enhance the superclass's method in subclass. More details to see the issue #

Please answer these questions before submitting pull request

Why submit this pull request?

[√] Bug fix

[ ] New feature provided

[ ] Improve performance

Related issues
#1724

Bug fix

Bug description.

How to fix?

New feature or improvement

Describe the details and related test reports.

Coverage increased (+0.003%) to 14.216% when pulling 2a0a01fdefb359d5aa4e1380925f16213de508fa on nize1989:skywalking-debug into 1955e9d3cf573502a06bbe094341ace8008bd78e on apache:master.

@wu-sheng Thanks for your suggestion，I will take it. But the static method of superclass have not been overrided by subclass in enhanced byte code.

I will take it. But the static method of superclass have not been overrided by subclass in enhanced byte code.

Yes, I think you are right. We may don't need to concern about the static method. :)

@nize1989 Based on our autotests, these changes look like making these following cases failure

Spring-RestTemplate_Annotation_RestAnnotation
SOFARPC
PostgreSQL
Elasticsearch

You could find the target test codes here, https://github.com/SkywalkingTest/skywalking-agent-testcases/tree/master with same name.
I also asked @ascrutae to check, but he is busy these days. So if you have time, please do some tests on your local, and we can discuss what is happening.

@nize1989 ,sorry for reply to you so late.becase of environment, I have not  run the testcases yet. Test as soon as  the conditions are met.

@nize1989 I am removing the milestone for now, just for preparing the release of 6.0.0-alpha. We could merge this as soon as it is ready. Don't worry.

OK.thanks.
发自我的 iPhone

在 2018年10月17日，21:57，吴晟 Wu Sheng<EMAIL_ADDRESS>写道：
@nize1989 I am removing the milestone for now, just for preparing the release of 6.0.0-alpha. We could merge this as soon as it is ready. Don't worry.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.


Default nit compilation directory

The question that follow #789 is the default location of the .nit_compile directory.
The current working directory may not be the best place.
Some sensible choices are:

in tmp (like gcc and other tools). But unlike gcc the name of the file must be stable to help ccache. However, /tmp is usually a ramdisk so better performances is a possible benefit.
in ~ (or ~/.cache). So the user share its own stuff.
in the root of the project (may not work if the owner is not the user)
in the directory of the module (same issue)
in the current working directory (status quo)
in the current working directory but not hidden, and we name it NIT_COMPILE_DIRECTORY_BEUAAARG because we are proud

Other question, should nitg clean the directory after it? (with an optional --no-clean option for debugging the generated code)

I'm more for the current directory with automatic cleaning after.
But my only argument is that I like to see what happened in my directory with ls when I use a new compiler.

@Morriar the problem is that currently the build directory is hidden so that a ls will reveal you nothing without an additional -a


Some minor mostly stylistic changes

Sorry for these OCD-ish changes, but I wish to have a good level of consistency in this project.

Please submit the stylistic changes in smaller chunks and single topics. For instance: you decided that writing some_dict = {} everywhere looks better than writing some_dict = dict() everywhere (I agree!). Write a pull request for that single topic.

It'll take a lot of time to create PRs for all those changes, I instead divided them to smaller commits if you don't mind.

46 files modified, and then "Try to make tests pass" :scream:
I understand there's a lot of low-hanging fruit in the codebase, but as with the documentation PR I think there are more important things to do for the end-user.
If we want consistency, do you have some suggestions on how to set up a linter and autoformatter? That way we can make it easy for contributors to keep the code clean.
Alternatively, I think it's great to help keep the code clean by participating in reviews and doing some cleanups while updating/bugfixing a feature.

46 files modified, and then "Try to make tests pass" 😱

Yeah, It got really messy 🤣, that's my fault, I deviated from the original purpose of this PR to modifying code logic but I reverted the changes that made tests fail. You can close this if you want, setting up an autoformatter and linter is probably better, but I don't think that would remove those ugly dict(...) and list(filter(map(lambda...))) or unused lambdas.

Please open a new issue for auto formatters and standards if you want to drive it forward! Closing this now.


qt6.qtbase: patch for loading libXcursor

Description of changes
Fixes https://github.com/NixOS/nixpkgs/issues/181176 on xorg, (maybe also on wayland, I cannot reproduce this)

Things done

Built on platform(s)

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

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

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

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

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

Thankfully you found how to inject it, I tried a few hours ago with LD_LIBRARY_PATH but that didn't work.

Tested that this patch works, hope to merge it soon

What is required in order to get this merged? Is there a way to help?


Art request: FlowForge as a No-Code Ethernet/IP to Profinet Protocol Converter

Related Issue
No response
Description
Considerations:
it would be great to show the logos of Node-RED and FlowForge connected to the logos of Ethenet/IP and Profinet protocols for my new blog post.
inspiration -
https://github.com/flowforge/content/issues/120

if you google "profinet logo" and "ethernetip logo" you'll get useful image results right away

See PR for this blog post here -
https://github.com/flowforge/website/pull/870
cc @Yndira-FlowForge

Looks great Yndira!  We can close this one.

Hi @Yndira-FlowForge, can we open this issue back up so that we can change the image from "profinet" to "s7"?
Here's an image you can use to replace the profinet image.

Everything else in the image looks great, just change the title to "Node-RED as a No-Code Ethernet/IP to S7 Protocol Converter"
Thanks!

Hi @Hisma here it is ;)

Awesome that was quick, thanks @Yndira-FlowForge!
@ZJvandeWeg since you merged the branch to main, can you or someone else please replace the blog image with this one?  I'd prefer not to create a branch for such a trivial change, but I can do if required.


SC 2022 Rebate not included

It appears that the 2022 state income tax rebate is included by the emulator in siitax for RI  but not for SC.  The SC rebate is documented at
https://dor.sc.gov/rebate-2022
See  also
http://taxsim.nber.org/out2psl/sc
The emulator shows the 795 for siitax, but that does not include the rebate that brings Taxsim down to zero.
Is there a reason for the excluding the rebate in this case? What about ID MA MT and NY rebates?  Shouldn't we have uniform treatment? An argument for excluding them is that they are based on 2021 income so this gets the marginal tax rate wrong. However it does get after-tax income right, so there is no perfect answer.

Isn't this program based on 2021 income? It would show up in 2021 in our system if so.

I will go along with that reasoning, with reservations.  It doesn't seem quite right for users that want after-tax income in 2021 which is most users of Taxsim. It isn't right for users that want marginal tax rates either, since their 2021 behavior can't be affected by a  2022 change in the law.  But going along makes validation testing much easier.
MT issued in 2023 based on 2021 income
https://mtrevenue.gov/taxes/montana-tax-rebates/individual-income-tax-rebate-house-bill-192/#Rebates
NM issued in 2023 based on 2021 income
https://www.tax.newmexico.gov/wp-content/uploads/2023/05/Rebate-deadline-address-update.pdf
OR apparently the rebate is a line on the form in odd years, based on the prior year income.
https://www.oregon.gov/dor/programs/individuals/pages/kicker.aspx
RI I don't see a mention of this on the 2022 forms, and I can't tell when it was paid.
SC based on 2021 income but paid in 2022
https://dor.sc.gov/rebate-2022


Update the notifications management design to have the same features level than the webclient

The notifications have four available settings on the webclient
-> All messages (loud)
-> All messages
-> Mention only
-> Mute
the mobile clients have only two
-> enable (== All messages)
-> disable (== mention only)
see https://github.com/vector-im/vector-android/issues/472

A setting as well so that the mobile client can have notification settings that are not the same as the web client.
In this way,
Web/Decktop: you could have All Messages
Mobile: You could have Mention Only
There are channels that on my desktop I want to be notified about all of the messages, but on my mobile I only want messages that have my name in them.

It's worth noting that if you mute a specific channel (rather than disabling notifications overall) you do still get notifications on name mention. While annoying that they don't point this out, it's what I wanted. :-)

I don't experience what is outlined by @mpdehnel here, on iOS Riot client if I mute the channel I don't get any notifications, including messages with mentions.  I would like to be able to mute the channel and have the option to receive notification of mentions in a channel.

https://www.figma.com/file/M15i7l4PSPY1B5M7Zhu80H/Notifications?node-id=381%3A4882


ElasticSearch not implemented yet?

Just want to make sure if we have plans to implement Elastic Search in the near future?
Or if need help please provide some instructions, I can help develop ElasticSearch and Cloudfront if needed.

Echoing the suggestion from @PeterCui1991 -- I'd also be happy to help with that.

PR's are always welcome for new services. See our https://github.com/spulec/moto/blob/master/CONTRIBUTING.md, specifically the section on Missing services, for some examples on how to get started with this.


SCI env improvements

The following example consistently work, when building the render-fns step-by-step and using clerk/show! but fail when reloading the browser:

Also doesn't work in the static app https://snapshots.nextjournal.com/clerk/build/0c3d838215278ac6b57b13457da774ec5b49d3c2/index.html#/notebooks/viewers/code.clj

@zampino The errors probably have to do with non-top-level require and refer. Perhaps it works if you execute the require and usage of that require in two separate functions, but ultimately this is what eval-cljs-str was intended for.

non-top-level require

I see. But also using requires in a separate render-fns doesn't survive a page reload:

this is what eval-cljs-str was intended for.

yeah, that works


Best crates.io practice

Add the version as comments to the Cargo.toml. When publishing, uncomment the version and comment out the git url and then change it back.
Metadata
Example from piston-input:
[package]

name = "pistoncore-input"
version = "0.0.1"
authors = ["bvssvni<EMAIL_ADDRESS>keywords = ["keyboard", "mouse", "input"]
description = "A structure for user input"
license = "MIT"
readme = "README.md"
repository = "https://github.com/pistondevelopers/input.git"
homepage = "https://github.com/pistondevelopers/input"

There can be a maximum of 5 keywords.
When developing
Remember to increase the minor version when making changes to the source code, or else you might accidentally cause Cargo to publish other projects with old versions of your code:
[package]

name = "pistoncore-glfw_window"
version = "0.0.0"
               ^~~~~~~ increment this number

This number can be 10 or larger, so don't worry about it getting too high.
Versions as comments
Keep the version as comments next to the git url. The comments will tell people which version of the dependencies was published in the last published version:
[dependencies.pistoncore-window]
git = "https://github.com/pistondevelopers/window"
#version = "0.0.1"

Before publishing
Uncomment the version and type cargo update. This will make Cargo fail if the version does not match those in the dependencies.
[dependencies.pistoncore-window]
git = "https://github.com/pistondevelopers/window"
version = "0.0.1"

cargo update
cargo build
cargo test

When publishing
Comment the git url such that the package gets accepted by crates.io:
[dependencies.pistoncore-window]
#git = "https://github.com/pistondevelopers/window"
version = "0.0.1"

cargo publish -v

Then you change it back and send a pull request to update with new version comments.

I don't synchronizing versions has any purpose unless we are releasing a major version.


type check dynamic imports from constant string literal

🔍 Search Terms
dynamic import constant string infer type any
✅ Viability Checklist

[x] This wouldn't be a breaking change in existing TypeScript/JavaScript code
[x] This wouldn't change the runtime behavior of existing JavaScript code
[x] This could be implemented without emitting different JS based on the types of the expressions
[x] This isn't a runtime feature (e.g. library functionality, non-ECMAScript syntax with JavaScript output, new syntax sugar for JS, etc.)
[x] This isn't a request to add a new utility type: https://github.com/microsoft/TypeScript/wiki/No-New-Utility-Types
[x] This feature would agree with the rest of our Design Goals: https://github.com/Microsoft/TypeScript/wiki/TypeScript-Design-Goals

⭐ Suggestion
statically analyze type of dynamic import if path is statically analyzable, such that
export {}

const polars = "nodejs-polars" as const
//    ^? const polars: "nodejs-polars"

const pl = await import(polars)
//    ^? const pl: typeof import("file:///node_modules/nodejs-polars/bin/index")

as type of polars is "nodejs-polars", not string, typescript should treat import("nodejs-polars") the same as import(polars).
📃 Motivating Example
https://github.com/denoland/deno/issues/26965
export {}

const polars = "nodejs-polars" as const

const pl = await import("nodejs-polars")
//    ^? const pl: typeof import("file:///node_modules/nodejs-polars/bin/index")

const pl2 = await import(polars)
//    ^? const pl2: typeof import("file:///node_modules/nodejs-polars/bin/index")

Playground Link
💻 Use Cases

What do you want to use this for?

writing type safe javascript module, with version string abstracted away to manage versions easily
const preact =<EMAIL_ADDRESS>const { h, render } = await import(`https://esm.sh/${preact}`)
const { computed, effect, signal } = await import(`https://esm.sh/@preact/signals@1.3.0?deps=${preact}`)

console.log(`preact version is ${preact}`)

What shortcomings exist with current approaches?
What workarounds are you using in the meantime?

due to type check not working in above example, version string has to be duplicated, which might cause bug when naively regex-replacing.
import { h, render }  from<EMAIL_ADDRESS>import { computed, effect, signal } from "https://esm.sh/@preact/signals<EMAIL_ADDRESS>
console.log("preact version is<EMAIL_ADDRESS>

Duplicate of #32401.


Checks using unsupported bitmask compare operator and set attribute is not set for some checks

Description:
security-scan v0.2.5, v0.2.6-rc2 and master.  Did not check others but assume every tag above v0.2.5 is affected.
bitmask operator is not supported in the kube-bench binary v0.2.3-rancher-1 from leodotcloud.  The following control files contain checks using this operator in compare.
set: attribute is not set.  ·kube-benchv0.2.3-rancher-1 from leodotcloud defaults a check'ssetattribute tofalseunlike current release ofkube-bench(v0.6.6).  This is a serious problem because it will give a check false-positivePASS` state.
Control files affected:
rke2-cis-1.6-permissive/node.yaml
cis-1.6/node.yaml
cis-1.6/master.yaml
rke2-cis-1.6-permissive/master.yaml
k3s-cis-1.6-permissive/node.yaml
k3s-cis-1.6-permissive/master.yaml
k3s-cis-1.6-hardened/node.yaml
k3s-cis-1.6-hardened/master.yaml
rke-cis-1.6-hardened/node.yaml
rke-cis-1.6-hardened/master.yaml
rke2-cis-1.6-hardened/node.yaml
rke2-cis-1.6-hardened/master.yaml
rke-cis-1.6-permissive/node.yaml
rke-cis-1.6-permissive/master.yaml

Effects:
Results from scans that use any files listed above are completely untrustworthy.
Cause：
The use of kube-bench v0.2.3-rancher-1 from leodotcloud in security-scan/package/Dockerfile and developing benchmark checks based on more recent versions of kube-bench release documentation.
Work around:
Review checks defined in rke-cis-1.5-permissive benchmark version for reference to develop custom version.  Or, just check manually if security is really important for you.

This won't be an issue in rancher/security-scan tag v0.2.8-rc3.


lineage summary

Navigator captures fairly detailed lineage that links input datasets to the operation execution and then from the operation execution to the output datasets (or from the columns/fields). However, in many instances users/partners only wish to see "summarized" lineage between the inputs/outputs and skip the intermediate relationships through the operation executions. The operations can then be used by the user to annotate the summarized relationship that directly connects inputs/outputs.

closing for now. server-side work required first and we'll revisit afterwards


Is it possible to use cxx for building rust bindings for a c++ library?

Hello,
First of all, thank you for this amazing project.
I would like to write bindings for some c++ library, for what I can see in the tutorial, cxx is used to bridge rust code and c++ code into a rust binary (main.rs, fn main() {})
Is it possible to create a rust lib without a main function that binds some c++ library?

It works the same whether or not there is a main function. As an example of binding a C++ library as a Rust library using cxx, see https://github.com/vi/gaborator-rs/blob/b9b4a4b130befa7fdca24515c32e522ccab3ca91/gaborator-sys/src/lib.rs.

Thank you!


Getting started with mysql storage, batch processing is taking forever

I've set up the NVDAPI key in our projects and that helps a lot, but wanted to incorporate the database storage for caching.
I'm using a MariaDB backend, and found that specifying "character set utf8" in initialize_mysql.sql when creating the database, was needed to avoid DB errors when importing the NVD data.
Now that I'm past that, the "Downloaded ..." logs completed but now I see
[INFO] Completed processing batch 1/125 (1%) in 992,366ms
[INFO] Completed processing batch 2/125 (2%) in 1,784,160ms
...
[INFO] Completed processing batch 14/125 (11%) in 2,254,533ms
[INFO] Completed processing batch 15/125 (12%) in 2,280,112ms
[INFO] Completed processing batch 16/125 (13%) in 2,454,196ms
Here is seems to have gotten stuck.  I haven't seen process 17/125.
which seems like an incredibly long time to wait.  Is this the database taking a long time?  My slow query log doesn't show any queries over 1.5 seconds, so it seems not....   I'm not even sure what 'Completed processing batch' means.  Help?

Seeing a similar behavior over here with Aurora for PostgreSQL here. Process running for over 2hs now and still a good way to go...
2024-08-02T17:38:48+02:00 [INFO] Downloaded 258,861/258,861 (100%)
2024-08-02T17:46:59+02:00 [INFO] Completed processing batch 1/130 (1%) in 656,293ms
2024-08-02T17:52:54+02:00 [INFO] Completed processing batch 2/130 (2%) in 1,009,181ms
2024-08-02T17:52:58+02:00 [INFO] Completed processing batch 3/130 (2%) in 1,012,495ms
2024-08-02T17:53:44+02:00 [INFO] Completed processing batch 4/130 (3%) in 1,059,200ms
(....)
2024-08-02T19:34:21+02:00 [INFO] Completed processing batch 98/130 (75%) in 6,976,488ms
2024-08-02T19:36:53+02:00 [INFO] Completed processing batch 99/130 (76%) in 7,128,100ms
2024-08-02T19:36:53+02:00 [INFO] Completed processing batch 100/130 (77%) in 7,122,805ms

pretty sure that part is a bit memory-intensive. The benefit of using a DB like this is that once you have the first full update of data it is very quick to do daily updates and keep it current.


Crash with RyoamicLights

title, logs https://mclo.gs/k6eEX0T

Interesting, this mod seems to be an exact port of lambdynlights. The issue is due to the fact that we're integrating directly with lambdynclight's code, which is causing issues when replacing it with RyoamicLights because they use the same interface, but different classes. Only one of these mods will work out of the box. A possible solution is to externalize these compats into dedicated jars and then you can pick which ones you want.

there is now a Third dynamic lights mod https://www.curseforge.com/minecraft/mc-mods/dynamiclights-reforged and the same crash happens with this


connectionStringSetting in @cosmosDBOutput annotation is invalid.

According to this Microsoft document,
connectionStringSetting in @cosmosDBOutput annotation is invalid.
when I used code, I am getting error,
GETTING ERROR
[ERROR] ./javafunc/src/main/java/com/function/Function.java:[30,17] cannot find symbol
[ERROR]   symbol:   method connectionStringSetting()
[ERROR]   location: @interface com.microsoft.azure.functions.annotation.CosmosDBOutput

Its working using connection method.

Please update the correct method for future reference.

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

ID: 6dfb86c0-02ed-0abc-8789-ba91d7979762
Version Independent ID: ecbcc2c6-869e-2492-f10f-a07cf4b34209
Content: Azure Cosmos DB output binding for Functions 2.x and higher
Content Source: articles/azure-functions/functions-bindings-cosmosdb-v2-output.md
Service: azure-functions
GitHub Login: @ggailey777
Microsoft Alias: glenga

@Shandilyavivek The example provided in the doc targets version 3.x of the Azure Cosmos DB extension which uses connectionStringSetting, collectionName etc. Those properties need to be replaced with connection and container respectively (as well as few other properties). The same note has been added here and we will update the doc for the latest version.
@ggailey777 please share if you have any other thoughts.


Lazy resolver creation

Currently, a resolver is created as soon as we create a channel, even though we don't need it until the first RPC is called on this channel.

I was requested a review, but I see this PR is still in "draft". (There is a "Ready for review" button, please click it if you meant to request a review.)

This failure is real.
E0702 01:38:46.591157887      17 sockaddr_resolver.cc:87]    authority-based URIs not supported by the (null) scheme
E0702 01:38:46.591247659      17 channel.cc:83]              channel stack builder failed: {"created":"@1562031526.591229930","description":"resolver creation failed","file":"src/core/ext/filters/client_channel/resolving_lb_policy.cc","file_line":220}

Adopted another approach. See #19588


Add function to convert MonadPlus (as MaybeT) to MonadError

I apologize if there's already a straight forward way to do this, and I just couldn't figure it out. In the popular setup where you have a ReaderT instance for your application monad, you might end up writing functions that return m (Maybe String). For example, if you're fetching something from the database, then that entity may or may not be there.
To make it easier to compose different functions that all share the application monad, but not the return type, you might decide to change this to (MonadPlus m) => m String. The most convenient way for me to then handle the mzero case is through the MaybeT instance of MonadPlus. And so I often have this in my code:
(?*) :: (MonadError e m) => MaybeT m b -> e -> m b
(?*) x e = runMaybeT x >>= liftEither . note e

foobar :: (HasDB m, MonadError MyError m, MonadThrow m) => Vault.Key -> Wai.Request -> UserID -> m Wai.Vault
foobar vaultKey request userId = do
      -- Role.get has `MonadPlus m`
      roles <- Role.get userId ?* NoRoles -- NoRoles is a constructor for MyError
      let vault' = Vault.insert vaultKey (roles, userId) $ Wai.vault request
      return vault'

which is a variation of the ?? infix operator already in the library.
Is this something that might be added to this library or is there a better way of achieving the above with what's already there?

Yes, I would accept a PR for something like this


Add conftest to flaskr

In practice, it is often important to have more than one test file. Though this is in the pytest domain, I thought that it would be important to illustrate the capability of fixture sharing.
I updated the docs and flaskr code example to use a conftest.pyfile.

The more we add to this thing the less it's a simple example that beginners can look at and understand. 😞

Not anything against your pr, just a general observation.

I understand.
Would there be a better location for this? Maybe we can display a link instead.

I am going to close this for now and give it some more thought. Maybe we can explain conftest in a simpler manner.:
At the very least, I will submit another PR request to fix the issue that @ThiefMaster pointed out with the existing Flaskr example:
https://github.com/pallets/flask/blob/master/examples/flaskr/tests/test_flaskr.py#L44

I think this can go in the testing section outside the tutorial, but explaining all the options in PyTest ultimately belongs in PyTest's docs. I am working on creating a "tutorial" example and "full" example that takes the tutorial farther.


chore: add an npm script for tns preview

The new npm script will allow devs to call npm run preview, which will execute tns preview --bundle

That's a great idea! Preview is quite powerful when converting web projects. I would even go as far as naming the script npm run mobile. What do you think?


Exchange Content

When you use the actual GUI to do a Reservation Exchange it says "Exchanged reservation will have the same end date, region and quantity as the current reservation".   In your content above, however, it says "The term start date for the new reservation doesn't carry over from the exchanged reservation. The 1 or 3-year term starts from when you create the new reservation".    It doesn't appear that both can be true.   So which is correct?

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

ID: edda1fe4-6ce9-ccf2-bc1b-65e9818b1060
Version Independent ID: 5151901d-a4d3-1148-811f-8c9a959608a3
Content: Prepay for Azure virtual machines to save money
Content Source: articles/virtual-machines/windows/prepay-reserved-vm-instances.md
Service: virtual-machines-windows
GitHub Login: @yashar
Microsoft Alias: yashar

Thanks for the feedback! We are currently investigating and will update you shortly.

@yashesvi Can you please help confirm on which of the statement is true. Thanks :)

@joeljanke the term does not change for the specific exchange shown in the UI on click of exchange. example: D1 to DS1 or vice versa. The term does change when any other exchange is processed.

Thanks @yashesvi :)
@joeljanke We will now close this issue. If there are further questions regarding this matter, please tag me in a comment. I will reopen it and we will gladly continue the discussion.


Evaluate on Duke-Video datasets

i use this code to train model on Duke-video dataset,then i change the path in run_evaluate.sh and run it ,but it has something wrong.
Traceback (most recent call last):
File "evaluate.py", line 77, in
network.load_state_dict(state,strict=True)
File "/home/cczulab515/anaconda3/envs/py37/lib/python3.7/site-packages/torch/nn/modules/module.py", line 769, in load_state_dict
self.class.name, "\n\t".join(error_msgs)))
RuntimeError: Error(s) in loading state_dict for DataParallel:
size mismatch for module.classifier.weight: copying a param with shape torch.Size([702, 2048]) from checkpoint, the shape in current model is torch.Size([625, 2048]).
Then i chang the line,  network.load_state_dict(state,strict=False),but this problem still exits。Please tell me why. THANK YOU!

This is because the number of ID is mismatch.
You can either remove the classifier weight in your state_dice or create the model with the same number of ID.

Thank you for your instruction.i will try it again.


Button component does not accept dispatched events directly, does not trigger non-memoized callbacks

Bug report
Having trouble simulating button interactions in jest + jsdom.
This works:
const handleRefresh = useCallback(()=> console.log('refreshes'), [])

...
return <Button onClick={handleRefresh}>Refresh</Button>

// in test case
import {fireEvent, screen} from '@testing-library/react'
fireEvent.click(screen.getByText('Refresh'))  // it will click the button and callback will be triggered

This does not work:
const handleRefresh = ()=> console.log('refresh without memoization')

...
return <Button onClick={handleRefresh}>Refresh</Button>

// in test case
import {fireEvent, screen} from '@testing-library/react'
fireEvent.click(screen.getByText('Refresh'))  // it will click the button and callback not triggered

However, if i switch out the event simulation library to @testing-library/user-event, then the following will work:
const handleRefresh = ()=> console.log('refresh without memoization')

...
return <Button onClick={handleRefresh}>Refresh</Button>

// in test case
import {screen} from '@testing-library/react'
import userEvent from '@testing-library/user-event'
userEvent.click(screen.getByText('Refresh'))  // it will click the button and callback will be triggered

I had a scan of the Button src and suspect that it has to do with the way refs are handled, as well as how dispatched events are passed to the button instance (as compared to dom  interaction being simulated in the case of userEvent)

I think I changed the Button component in the theming branch, I remember there being something wrong with ref though. I think it was set up a bit oddly before because the ref was needed on the container, not on the button itself as a hack to get a tooltip to work.

Supabase UI is being deprecated.
As part of that, we are closing issues in this repo that are perhaps outdated.
If you'd like to still make an issue, you could consider making an issue for our package in our monorepo https://github.com/supabase/supabase/tree/master/packages/ui

We are moving the components to the main mono repo at https://github.com/supabase/supabase.
The auth component has been moved to it's own repo and package. https://github.com/supabase-community/auth-ui. You can also read the docs for auth ui here.


Add support for heartbeats on multiple local entities

Refactor to move the heartbeatmanager from the device to local entity
timeout 0s will not create a heartbeat manager for the entity, e.g. used by NodeMgmt local entity

Fixes https://github.com/enbility/spine-go/issues/31

coverage: 93.703% (+0.008%) from 93.695%
when pulling 44dcb27155bdc263692c466536943116db01626d on feature/heartbeat-entity
into b637b5392906e5020c130d6c8b86ba93be60de9e on dev.


proposal: wget qemu tarballs instead of committing the source to the git repo

Any reason not to do it like this?
https://github.com/ziglang/docker-zig/blob/ccffc9ab67bd7024eca340ea066710c2d644ef40/Dockerfile#L22

Ah ok I'll embed .tar.xz and build script.

Not sure I follow, are you suggesting to commit a .tar.xz to the source repo?

In this repo we could probably get by with nothing but a do_the_thing script that runs a docker command with another build script that runs inside the container and produces the .tar.xz.

https://github.com/ziglang/qemu-static/tree/redux

moved everything into docker build process
in order to preserve docker layering advantages, individual script-files were created for each docker step
basically we run container for the sole purpose of extracting artifacts

[I wonder why docker doesn't have a mechanism to set ARG from the output of RUN.]
If this isn't the docker use you had in mind, let me know where responsibilities for builder ends and container begins.

redux branch updated to 5.0.0-rc3
binaries: https://drive.google.com/drive/folders/12qkeNxsHHMiqDIFyAcWHMuZ45NnbC1c_?usp=sharing

Seems like you know what you're doing


Disk writer interface implementation

Main issue for the creation of an interface structure for the disk writer classes (currently in _write.py).
Objective is to define an interface that each disk writer class has to implement to fulfil basic biocypher functionality, such as accepting iterables of nodes and edges, transforming representation to conform with the downstream application (Neo4j, SQL, ArangoDB, KGX, ...), and perform integration tasks such as deduplication.
Miro board: https://miro.com/app/board/uXjVPgW-BoU=/#tpicker-content

@Maiykol and I had a meeting for the batch writer implementation; we will create an SQL version of the existing _Neo4jBatchWriter class to be selectable from BioCypher core via the get_writer() method of write.py. In addition, we will rationalise some common functionalities of all writer modules, such as a way of deduplicating entities (via a Deduplicator class, #137) and, relatedly, a way of generating relationship IDs via md5 hashes (which can be applied in the deduplicator class as well as in the individual adapters).
While writing the PostgreSQL adapter, we will also create an abstract base class to serve as an interface for the minimal functionality any batch writer must possess (e.g. for the implementation of the ArangoDB version).
We will work mainly on a new branch (disk_writer) that we will create from the main after the v0.5 has been released, which will happen later today or tomorrow at the latest.

Released v0.5.7 today. Closing.


Make rigid bodies kinematic while they are grabbed by the user in the sdk

We should really be making the rigid bodies kinematic whenever they are grabbed by the user, so that they are no longer affected by the physics system.  This will allow us to safely move them on the client during a grab without imparting any undesired forces.

I would also propose setting the rigid body velocity locally while the object is grabbed. That way objects can be thrown.


incorrect match of human gene WARS1

"There is a human gene WARS1 that is not in our background gene info on the recent version of the HIPC Dashboard.  I noticed this purely by chance.  We have a gene in our curated data WARS which should match as an alias to human WARS1, but since there is not human entry, it is matching to the mouse Wars gene.  Probably the first thing to try is a new copy of the NCBI gene file Homo_sapiens.gene_info.  That is the file you use, correct?" (from Ken's email)

8/7/2020 downloaded from ftp://ftp.ncbi.nlm.nih.gov/gene/DATA/GENE_INFO/Mammalia/Homo_sapiens.gene_info.gz
After all the data were reloaded, it is still the mouse gene that was matched.
Is there any other reason that we think the mismatch is related to the versions of the data?

I remember a similar issue reported before, but it might be in the CTD2 dashboard. Basically, the over-smart matching rule could give unexpected result when the perfect match was not found. In this case, the 'canonical' name WARS1 (http://hipc-dashboard.org/#gene/h/wars1) was expected, but a synonym WARS was entered in the data. I need to research more to confirm the problem.

I downloaded the latest version of the gene file from NCBI.  WARS1 is in the file as the primary gene symbol.  Here are the first few columns:
606	7453	WARS1	-	GAMMA-2|HMN9|IFI53|IFP53|WARS

I downloaded the latest version of the gene file from NCBI. WARS1 is in the file as the primary gene symbol. Here are the first few columns:
606 7453 WARS1 - GAMMA-2|HMN9|IFI53|IFP53|WARS
So gene symbol synonym WARS should match and give WARS1.

That was the case in the previous version of the file, so it basically confirmed that the different version is NOT the cause.

For more details, see https://github.com/CBIIT/nci-ctd2-dashboard/issues/426
Making the same changes here probably can solve the problem of this case.
Unfortunately this complexity is not intrinsic in the application itself, but caused artificially by the basic design.

In CTD2, the solution is essentially to use letter cases to differentiate human and mouse genes. I don't think that is a very solid approach. Fortunately we only need to support human genes (at least for now), so it is hard-coded to only match human genes in this case.

WARS is translated to WARS1 correctly now.


HaTS survey

Current draft for the HaTS survey for the documentation.
How it works at a high level:

doc-feedback-cta.js: It's the client side JS that verifies if the user is a candidate to show the CTA to the survey (running on docs and not having a particular cookie). If the criteria is met, then a request is done to the server to get the survey information. If the server says it's a good candidate, the survey ID is returned and the CTA will be shown (we obviously need a design):

feedback.js: The server side component. It's a new route in /docs/feedback. It verifies if the survey is open, if the user does not have the cookie (again), and eventually if the user should be shown the CTA (randomly we want to show it to ~8% of the users). If everything checks it returns the survey ID so doc-feedback-cta.js can generate the CTA. It also sets the cookie to make sure the user is not shown the CTA again for the next 3 months (unless they delete their cookies).

Pending:
feedback.js:

[x] Get the collector of the latest survey (with caching)
[x] Implement the logic to check if the survey is opened (with caching)
[x] Randomly select users
[x] Cleanup code

doc-feedback-cta.js:

[x] Add a real design to the CTA
[x] Cleanup code

Got a lot of things changed in this PR and I think it's actually ready for review. Even though we do not have yet a SM account this should be safe to merge because it will not do anything if the access token is not found.
Video of it working locally:
https://user-images.githubusercontent.com/606594/109346160-1fa61300-7826-11eb-8c1c-bf14c6b2e5c5.mp4
We should also create a few GitHub actions to automatically create surveys, report scores, etc. but I think those can go in a different PR and once we have the account.
@erickzhao the first commit of the PR has information about how everything connects. Happy to jump over hangouts if that helps.

I think that border surrounding the survey is too big 😬

I might have to override the style as well :(


"previousValue" getter does not on signal

Code provided on https://github.com/rodydavis/signals.dart/blob/main/website/src/content/docs/dart/core/signal.md#previousvalue doesn't work as "previousValue" does not exist.
Is this just outdated documentation issue?

It should still be the case. It should only be removed for value signal.
I'll double check on the code and documentation

I can confirm on 4.5.1 that previousValue doesn't exist in the above case as per the documentation.
final counter = signal(0);

effect(() {
	print('Current value: ${counter.value}');
	print('Previous value: ${counter.previousValue}');
});

counter.value = 1;

---

The getter 'previousValue' isn't defined for the type 'Signal<int>'.
Try importing the library that defines 'previousValue', correcting the name to the name of an existing getter, or defining a getter or field named 'previousValue'.

Ah it is because I moved it to TrackedReadonlySignal and Signal does not expose it.
Just an interface issue, will fix it!

Will be fixed on the next release!

Added an error via mixin for the value signals on the latest beta


feat: add hashicorp/boundary

https://github.com/aquaproj/aqua-registry/pull/7095 hashicorp/boundary: Boundary enables identity-based access management for dynamic infrastructure
$ aqua g -i hashicorp/boundary

How to confirm if this package works well
Reviewers aren't necessarily familiar with this package, so please describe how to confirm if this package works well. Please confirm if this package works well yourself as much as possible.
 Log data will stream in below:

{
  "id": "qqVn6GnPe3",
  "source": "https://hashicorp.com/boundary/dev-controller/boundary-dev",
  "specversion": "1.0",
  "type": "system",
  "data": {
    "version": "v0.1",
    "op": "worker.(Worker).createClientConn",
    "data": {
      "address": "<IP_ADDRESS>:9201",
      "msg": "connected to controller"
    }
  },
  "datacontentype": "text/plain",
  "time": "2021-12-06T11:18:33.041494-07:00"
}
{
  "id": "HXvjcn1uZ1",
  "source": "https://hashicorp.com/boundary/dev-controller/boundary-dev",
  "specversion": "1.0",
  "type": "system",
  "data": {
    "version": "v0.1",
    "op": "controller.(interceptingListener).Accept",
    "data": {
      "msg": "worker successfully authed",
      "name": "dev-worker"
    }
  },
  "datacontentype": "text/plain",
  "time": "2021-12-06T11:18:33.058218-07:00"
}

access to <IP_ADDRESS>:9200
Reference

document (Start a Development Environment)

https://learn.hashicorp.com/tutorials/boundary/oss-getting-started-dev?in=boundary/oss-getting-started

Thanks!

Released. https://github.com/aquaproj/aqua-registry/releases/tag/v3.76.0


Upgrade to Unity version 2019.4.19.f1

Thanks! Hope that solves it. Tried running it on 2019.4 tonight and no tools menu loaded. Hopefully gets merged soon if it solves that.


Is there a way to serialize only the data and not the schema from RecordBatch? [Arrow JS]

I am currently working on developing a custom Athena Dynamodb connector using Javascript. I am trying to get the ReadRecordsResponse implemented which consists of a records block which contains schema and records. Concatenating the buffers of schema and records returns a RecordBatch.
The records block looks like this:
"records" : {
    "aId" : "test-allocator-id",
    "schema" : "BAEAABAAAAAAAAoADgAGAA0ACAAKAAAAAAADABAAAAAAAQoADAAAAAgABAAKAAAACAAAAAgAAAAAAAAAAwAAAIgAAAA8AAAABAAAAJb///8UAAAAFAAAABQAAAAAAAIBGAAAAAAAAAAAAAAAhP///wAAAAEgAAAAAwAAAGRheQDK////FAAAABQAAAAUAAAAAAACARgAAAAAAAAAAAAAALj///8AAAABIAAAAAUAAABtb250aAASABgAFAATABIADAAAAAgABAASAAAAFAAAABQAAAAcAAAAAAACASAAAAAAAAAAAAAAAAgADAAIAAcACAAAAAAAAAEgAAAABAAAAHllYXIAAAAA",
    "records" : "7AAAABQAAAAAAAAADAAWAA4AFQAQAAQADAAAAJAAAAAAAAAAAAADABAAAAAAAwoAGAAMAAgABAAKAAAAFAAAAHgAAAAKAAAAAAAAAAAAAAAGAAAAAAAAAAAAAAACAAAAAAAAAAgAAAAAAAAAKAAAAAAAAAAwAAAAAAAAAAIAAAAAAAAAOAAAAAAAAAAoAAAAAAAAAGAAAAAAAAAAAgAAAAAAAABoAAAAAAAAACgAAAAAAAAAAAAAAAMAAAAKAAAAAAAAAAAAAAAAAAAACgAAAAAAAAAAAAAAAAAAAAoAAAAAAAAAAAAAAAAAAAAAAAAA/wMAAAAAAADgBwAA4QcAAOIHAADjBwAA5AcAAOUHAADmBwAA5wcAAOgHAADpBwAA/wMAAAAAAAABAAAAAgAAAAMAAAAEAAAABQAAAAYAAAAHAAAACAAAAAkAAAAKAAAA/wMAAAAAAAABAAAAAgAAAAMAAAAEAAAABQAAAAYAAAAHAAAACAAAAAkAAAAKAAAA"
  }

I am able to serialize the schema part but I was unable to find a direct method to serialize just the records (data part) from the RecordBatch without including the schema. I have tried using the RecordBatchStreamWriter to write the record batches, however, because RecordBatch consists of schema and data, the serialized output also contains a schema.
AWS Athena expects the records in ReadRecordsResponse to not have any schema as the messsage header and contain only the data. Any help would be appreciated!

We solved this scenario by overriding the RecordBatchWriter _writeSchema as a no-op:
class NoSchemaRecordBatchStreamWriter extends RecordBatchStreamWriter {
  protected _writeSchema(schema: Schema<T>) {
     return this;
  }
}


TEST: safari_7_OS_X_10_9_Desktop on Sauce fails a lot.

Here's a sample local failure:
$ time \
>   ROWDY_OPTIONS='{ "client": { "logger":true } }' \
>   ROWDY_SETTINGS="sauceLabs.safari_7_OS_X_10_9_Desktop" \
>   SAUCE_USERNAME=wml-little-loader \
>   SAUCE_ACCESS_KEY=SNIPPED \
>   SAUCE_TUNNEL_ID=dev-wml-little-loader \
>   SAUCE_CONNECT_VERSION=4.3.10 \
>   npm run test-func-raw

><EMAIL_ADDRESS>test-func-raw /Users/rye/scm/wm/little-loader
> mocha --opts test/func/mocha.opts test/func/spec/

[CLIENT] [cmd] POST /wd/hub/session {"desiredCapabilities":{"browserName":"safari","version":"7","javascriptEnabled":true,"locationContextEnabled":true,"handlesAlerts":true,"rotatable":true,"platform":"OS X 10.9","loggingPrefs":{"browser":"ALL","driver":"ALL"},"name":"wml-little-loader","tags":["wml-little-loader@local"],"public":"public","build":"local","requestOrigins":{"url":"http://webdriver.io","version":"3.2.6","name":"webdriverio"}}}
[CLIENT] [init] a91fc249975a4205a3a9a6a80d666c51
[CLIENT] [result] POST /wd/hub/session {"status":0,"sessionId":"a91fc249975a4205a3a9a6a80d666c51","value":{"takesScreenshot":true,"version":"7.1.7","cssSelectorsEnabled":true,"javascriptEnabled":true,"secureSsl":true,"platform":"MAC","browserName":"safari","webdriver.remote.sessionid":"a91fc249975a4205a3a9a6a80d666c51","hasMetadata":true},"state":null,"hCode":99137470,"class":"org.openqa.selenium.remote.Response"}
[CLIENT] [cmd] POST /wd/hub/session/a91fc249975a4205a3a9a6a80d666c51/timeouts {"type":"implicit","ms":200}
[CLIENT] [result] POST /wd/hub/session/a91fc249975a4205a3a9a6a80d666c51/timeouts {"status":0,"orgStatusMessage":"The command executed successfully."}
  advanced
[CLIENT] [cmd] POST /wd/hub/session/a91fc249975a4205a3a9a6a80d666c51/url {"url":"http://<IP_ADDRESS>:3030/test/func/fixtures/advanced.html"}
[CLIENT] [result] POST /wd/hub/session/a91fc249975a4205a3a9a6a80d666c51/url {"status":0,"orgStatusMessage":"The command executed successfully."}
[CLIENT] [cmd] POST /wd/hub/session/a91fc249975a4205a3a9a6a80d666c51/elements {"using":"css selector","value":".e2e-error"}
[CLIENT] [result] POST /wd/hub/session/a91fc249975a4205a3a9a6a80d666c51/elements {"status":0,"sessionId":"a91fc249975a4205a3a9a6a80d666c51","value":[],"state":null,"hCode":1510480563,"class":"org.openqa.selenium.remote.Response"}
NoSuchElement: An element could not be located on the page using the given search parameters.
    at elements(".e2e-error") - getText.js:42:17
    at getText(".e2e-after-load-fourth") - advanced.spec.js:39:8
    1) loads advanced scenario

  basic
[CLIENT] [cmd] POST /wd/hub/session/a91fc249975a4205a3a9a6a80d666c51/url {"url":"http://<IP_ADDRESS>:3030/test/func/fixtures/basic.html"}
[CLIENT] [result] POST /wd/hub/session/a91fc249975a4205a3a9a6a80d666c51/url {"status":0,"orgStatusMessage":"The command executed successfully."}
[CLIENT] [cmd] POST /wd/hub/session/a91fc249975a4205a3a9a6a80d666c51/elements {"using":"css selector","value":".e2e-error"}
[CLIENT] [result] POST /wd/hub/session/a91fc249975a4205a3a9a6a80d666c51/elements {"status":0,"sessionId":"a91fc249975a4205a3a9a6a80d666c51","value":[],"state":null,"hCode":981620018,"class":"org.openqa.selenium.remote.Response"}
NoSuchElement: An element could not be located on the page using the given search parameters.
    at elements(".e2e-error") - getText.js:42:17
    at getText(".e2e-after-load") - basic.spec.js:21:8
    2) loads basic script

[CLIENT] [cmd] DELETE /wd/hub/session/a91fc249975a4205a3a9a6a80d666c51 {}
[CLIENT] [result] DELETE /wd/hub/session/a91fc249975a4205a3a9a6a80d666c51 {"status":0,"sessionId":"a91fc249975a4205a3a9a6a80d666c51","value":""}

  0 passing (22s)
  2 failing

  1) advanced loads advanced scenario:
     NoSuchElement: An element could not be located on the page using the given search parameters.
      at getText(".e2e-after-load-fourth") - advanced.spec.js:39:8

  2) basic loads basic script:
     NoSuchElement: An element could not be located on the page using the given search parameters.
      at getText(".e2e-after-load") - basic.spec.js:21:8

npm ERR! Darwin 14.5.0
npm ERR! argv "node" "/Users/rye/.nvm/v0.10.40/bin/npm" "run" "test-func-raw"
npm ERR! node v0.10.40
npm ERR! npm  v2.14.12
npm ERR! code ELIFECYCLE
npm ERR<EMAIL_ADDRESS>test-func-raw: `mocha --opts test/func/mocha.opts test/func/spec/`
npm ERR! Exit status 2
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>test-func-raw script 'mocha --opts test/func/mocha.opts test/func/spec/'.
npm ERR! This is most likely a problem with the little-loader package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     mocha --opts test/func/mocha.opts test/func/spec/
npm ERR! You can get their info via:
npm ERR!     npm owner ls little-loader
npm ERR! There is likely additional logging output above.

npm ERR! Please include the following file with any support request:
npm ERR!     /Users/rye/scm/wm/little-loader/npm-debug.log

real  0m23.594s
user  0m1.295s
sys 0m0.219s

NOTE: Works fine for local Safari on my machine with ROWDY_SETTINGS="local.safari".


Chore: Structure the Repo with new added Components

Tech Required: React..
What to do?.

Add the components for new featured such as SideBar and About Page with Premade Routes

I am On it ...


Excessive space on some pages for small devices > bug fixed #72

Thanks for taking this on! Does it still look good on desktop? Can you post a screenshot of what that looks like?

@SheaBelsky sure

Is that drop shadow at the bottom of the page from your browser? Or is it actually there on the page?

@SheaBelsky there is no shadow on styles. u can check it if you open on full screen

Cool, just wanted to make sure since I saw it in the screenshot! You're all set!