feat(profiles): server-required profiles

This is one final section from #1195 that I realized never made it over to the current spec.

#1999 does not exist :) Not sure which issue/PR you're referring to?

Whoops. I've updated the OP.

To @wimleers' question in https://github.com/json-api/json-api/pull/1354#issuecomment-453464835

If the client is already updated to specifically send a JSON:API document with a profile applied, then why is requiring that profile to be specified in the media type as well unreasonable?

I think this is precisely because profile functionality has predated the official release of json:api 1.1. E.g., I have a client that is implementing Drupal's fancy filtering without sending a content-type parameter indicating so. I don't think we can require clients to upgrade their request parameters simultaneous with the server.
However, that doesn't mean this improvement is for nothing, in so far as it aids in compatible profile negotiation; as @dgeb points out:

Of course, it would still need to respond with an error if a conflicting profile has been applied OR if the required profile has been applied incorrectly.

Again, in Drupal's case, this could mean we detect some sort of problem in the fancy-filtering request parameters, and can throw and translate exceptions to the json:api implementation to indicate that we should tell the client precisely which profile they must implement (correctly) to remedy the problem.

This PR was written at a time when we were considering "profiles" to provide a single answer to the separate roles that profiles and extensions now play in v1.1. As such it is outdated, although the work has definitely informed the current state of the spec. Many thanks to @ethanresnick for his work here!

Again, in Drupal's case, this could mean we detect some sort of problem in the fancy-filtering request parameters, and can throw and translate exceptions to the json:api implementation to indicate that we should tell the client precisely which profile they must implement (correctly) to remedy the problem.

@bradjones1 Yes, I think this is reasonable. And hopefully clients / servers will soon start explicitly negotiating profiles.


Update Composer dependencies (2023-05-27-00-10)

Visual regression test passed!
View the visual regression test report


Fix broken link to server dev setup instructions

The existing link in the README is broken! This commit suggests that the correct link should be this Read the Docs page.
Please feel free to change if this should point somewhere else instead. :)

Automated message from Dropbox CLA bot
@lazerwalker, thanks for the pull request! It looks like you haven't yet signed the Dropbox CLA. Please sign it here.

(Just signed the CLA)

Automated message from Dropbox CLA bot
@lazerwalker, thanks for signing the CLA!

Thanks @lazerwalker !


Pull in latest charts and make bower versions static for release.

Pulls in charts version with hovers Gabriel cleaned up and a sparkline fix for when values are 0 they render below the x-axis

Merged #709


kapacitord - Type mismatch for 'run.Config.influxdb'

I am currently running a master build (git: master 39c711a6db2c75703ff21e22a23e6487261c3588)
in a dev. environment with InfluxDB 0.10.3.
The current Kapacitor nightly was working fine in the setup, but as I replaced the binaries with the master builds, Kapacitor failed to start up with the following message:
E! parse config: Type mismatch for 'run.Config.influxdb': Expected slice but found 'map[string]interface {}'.
run: parse config: Type mismatch for 'run.Config.influxdb': Expected slice but found 'map[string]interface {}'.

I could not decide where to post this, because it seems like something with the InfluxDB config, but I couldn't figure out whats wrong there, because the config is working.
[meta]
  # Controls if this node should run the metaservice and participate in the Raft group
  enabled = true

  # Where the metadata/raft database is stored
  dir = "/mnt/database/influxdb/meta"

  bind-address = ":8088"
  retention-autocreate = true
  election-timeout = "1s"
  heartbeat-timeout = "1s"
  leader-lease-timeout = "500ms"
  commit-timeout = "50ms"
  cluster-tracing = false

[data]
  enabled = true

  dir = "/mnt/database/influxdb"
  max-wal-size = 104857600 # Maximum size the WAL can reach before a flush. Defaults to 100MB.
  wal-flush-interval = "10m" # Maximum time data can sit in WAL before a flush.
  wal-partition-flush-delay = "2s" # The delay time between each WAL partition being flushed.

  wal-dir = "/var/lib/influxdb/wal"
  wal-logging-enabled = true
  data-logging-enabled = true
  wal-ready-series-size = 25600
  wal-max-series-size = 20971520
  wal-flush-cold-interval = "10m"

  cache-max-memory-size = 524288000
  cache-snapshot-memory-size = 26214400
  cache-snapshot-write-cold-duration = "1h"
  compact-full-write-cold-duration = "24h"

[hinted-handoff]
  enabled = true
  dir = "/mnt/database/influxdb/hh"
  max-size =<PHONE_NUMBER>
  max-age = "168h"
  retry-rate-limit = 0

  retry-interval = "1s"
  retry-max-interval = "1m"

  purge-interval = "1h"

[cluster]
  shard-writer-timeout = "5s" # The time within which a remote shard must respond to a write request.
  write-timeout = "10s" # The time within which a write request must complete on the cluster.

[retention]
  enabled = true
  check-interval = "30m"

[shard-precreation]
  enabled = true
  check-interval = "10m"
  advance-period = "30m"

[monitor]
  store-enabled = true # Whether to record statistics internally.
  store-database = "_internal" # The destination database for recorded statistics
  store-interval = "10s" # The interval at which to record statistics

[admin]
  enabled = true
  bind-address = ":8083"
  https-enabled = false
  https-certificate = "/etc/ssl/influxdb.pem"

[http]
  enabled = true
  bind-address = ":8086"
  auth-enabled = false
  log-enabled = true
  write-tracing = false
  pprof-enabled = false
  https-enabled = false
  https-certificate = "/etc/ssl/influxdb.pem"

[[graphite]]
  enabled = true
  bind-address = ":2034"
  protocol = "tcp"
  database = "cloudwatch"
  consistency-level = "one"
  name-separator = "."

  templates = ["cloudwatch.aws.* ..namespace.service.measurement*"]

  batch-size = 10240 # will flush if this many points get buffered
  batch-timeout = "1s" # will flush at least this often even if we haven't hit buffer limit

[[graphite]]
  enabled = true
  bind-address = ":2033"
  protocol = "tcp"
  database = "jmx"
  consistency-level = "one"
  name-separator = "."

  templates = [".env.service.container_id.measurement*"]

  batch-size = 10240 # will flush if this many points get buffered
  batch-timeout = "1s" # will flush at least this often even if we haven't hit buffer limit

[[udp]]
  enabled = false

[continuous_queries]
  log-enabled = true
  enabled = true

All useful hints are welcome.
Regards
hrzbrg

@hrzbrg Can you post your Kapacitor config? The config posted above looks like an InfluxDB config.

sure:
# The hostname of this node.
# Must be resolvable by any configured InfluxDB hosts.
hostname = "localhost"
# Directory for storing a small amount of metadata about the server.
data_dir = "/var/lib/kapacitor"

[http]
  # HTTP API Server for Kapacitor
  # This server is always on,
  # it servers both as a write endpoint
  # and as the API endpoint for all other
  # Kapacitor calls.
  bind-address = ":9092"
  auth-enabled = false
  log-enabled = true
  write-tracing = false
  pprof-enabled = false
  https-enabled = false
  https-certificate = "/etc/ssl/kapacitor.pem"

[logging]
    # Destination for logs
    # Can be a path to a file or 'STDOUT', 'STDERR'.
    file = "/var/log/kapacitor/kapacitor.log"
    # Logging level can be one of:
    # DEBUG, INFO, WARN, ERROR, or OFF
    level = "INFO"

[replay]
  # Where to store replay files, aka recordings.
  dir = "/var/lib/kapacitor/replay"

[task]
  # Where to store the tasks database
  dir = "/var/lib/kapacitor/tasks"
  # How often to snapshot running task state.
  snapshot-interval = "60s"

[deadman]
  # Configure a deadman's switch
  # Globally configure deadman's switches on all stream tasks.
  # NOTE: for this to be of use you must also globally configure at least one alerting method.
  global = false
  # Threshold, if globally configured the alert will be triggered if the throughput in points/interval is <= threshold.
  threshold = 0.0
  # Interval, if globally configured the frequency at which to check the throughput.
  interval = "10s"
  # Id -- the alert Id, NODE_NAME will be replaced with the name of the node being monitored.
  id = "node 'NODE_NAME' in task '{{ .TaskName }}'"
  # The message of the alert. INTERVAL will be replaced by the interval.
  message = "{{ .ID }} is {{ if eq .Level \"OK\" }}alive{{ else }}dead{{ end }}: {{ index .Fields \"collected\" | printf \"%0.3f\" }} points/INTERVAL."

[influxdb]
  # Connect to an InfluxDB cluster
  # Kapacitor can subscribe, query and write to this cluster.
  # Using InfluxDB is not required and can be disabled.
  enabled = true
  urls = ["http://localhost:8086"]
  username = "telegraf"
  password = "telegraf"
  timeout = 0
  # Subscriptions use the UDP network protocl.
  # The following options of for the created UDP listeners for each subscription.
  # Number of packets to buffer when reading packets off the socket.
  udp-buffer = 1000
  # The size in bytes of the OS read buffer for the UDP socket.
  # A value of 0 indicates use the OS default.
  udp-read-buffer = 0

  [influxdb.subscriptions]
    # Set of databases and retention policies to subscribe to.
    # If empty will subscribe to all, minus the list in
    # influxdb.excluded-subscriptions
    #
    # Format
    # db_name = <list of retention policies>
    #
    # Example:
    # my_database = [ "default", "longterm" ]
  [influxdb.excluded-subscriptions]
    # Set of databases and retention policies to exclude from the subscriptions.
    # If influxdb.subscriptions is empty it will subscribe to all
    # except databases listed here.
    #
    # Format
    # db_name = <list of retention policies>
    #
    # Example:
    # my_database = [ "default", "longterm" ]

[slack]
  # Configure Slack.
  enabled = false
  # The Slack webhook URL, can be obtained by addding
  # an Incoming Webhook integration.
  # Visit https://slack.com/services/new/incoming-webhook
  # to add new webhook for Kapacitor.
  url = "https://hooks.slack.com/services/*****"
  # Default channel for messages
  channel = "#slack-tests"
  # If true the all alerts will be sent to Slack
  # without explicity marking them in the TICKscript.
  global = false

[alerta]
  # Configure Alerta.
  enabled = false
  # The Alerta URL.
  url = "http://alerta.company.it/api"
  # Default authentication token.
  token = "*****************"
  # Default environment.
  environment = ""
  # Default origin.
  origin = "kapacitor"

[reporting]
  # Send anonymous usage statistics
  # every 12 hours to Enterprise.
  enabled = true
  url = "https://usage.influxdata.com"

[stats]
  # Emit internal statistics about Kapacitor.
  # To consume these stats create a stream task
  # that selects data from the configured database
  # and retention policy.
  #
  # Example:
  #  stream.from().database('_kapacitor').retentionPolicy('default')...
  #
  enabled = true
  stats-interval = "10s"
  database = "_kapacitor"
  retention-policy= "default"

[udf]
# Configuration for UDFs (User Defined Functions)
[udf.functions]
    # Example go UDF.
    # First compile example:
    #   go build -o avg_udf ./udf/agent/examples/moving_avg.go
    #
    # Use in TICKscript like:
    #   stream.goavg()
    #           .field('value')
    #           .size(10)
    #           .as('m_average')
    #
    # uncomment to enable
    #[udf.functions.goavg]
    #    prog = "./avg_udf"
    #    args = []
    #    timeout = "10s"

    # Example python UDF.
    # Use in TICKscript like:
    #   stream.pyavg()
    #           .field('value')
    #           .size(10)
    #           .as('m_average')
    #
    # uncomment to enable
    #[udf.functions.pyavg]
    #    prog = "/usr/bin/python2"
    #    args = ["-u", "./udf/agent/examples/moving_avg.py"]
    #    timeout = "10s"
    #   [udf.functions.pyavg.env]
    #       PYTHONPATH = "./udf/agent/py"

A change in master made influxdb an array of objects. You need to add [] around [influxdb] in your config. See kapacitord config output for an example.

facepalm...I didn't realize that
thank you


Feature request: Show first or n classes

Hi, I'm loving your extension but I find myself sometimes lost in nested divs, would It be possible to allow for 1 or n classes to be visible and hide the rest to ease glance readability? I tried using regex but failed miserably.
Thanks and regards

is this what you are looking for? if yes, i will push it up to main.
["body", "red", "grid"]

This is looking great! Maybe the partial hits like body for text-body can be specified with asterisks? (body* for body-text for example)
Also how does it look with full hits on first classes like group? Does it have the leading "..." as well in those cases?
I'm sorry if I'm too nit-picky! Thanks again!

Hi again,
I made it so it shows the hold thing instead of just the word. for example, if you want to see "body" you see text-body
The ... indicates collapsed content (the default value for class-collapse.collapsedText). You can change this setting, but it will affect all instances.

Not having exact matches makes it a bit noisy. Partial matches are great, but being able to support both would allow for a cleaner interface. What do you think?
Thanks again!

Thanks for the release!


javascript bug about object literals

i find  that run the next code will throw error:
let a = { b }

the error is:
Uncaught ReferenceError: b is not defined

i think that the prevous code equals to:
let a = { 'b':b }

just only undefined next to point sign . it throw error:
Uncaught TypeError: Cannot read property 'xx' of undefined

calling undefined itself don't thow any error. so instead throw error, the a should equal to:
a === {'b':undefined}

do you agree with me?

If you didn't define b, it's valid to get a ReferenceError when trying to access b. Since that's the normal behavior of JavaScript, it's not a TypeScript bug.

Also please follow the template


Discord rich presence isn't installing.

Error -
Yarn error warning package-lock.json found. Your project contains lock files generated by tools other than Yarn. It is advised not to mix package managers in order to avoid resolution inconsistencies caused by unsynchronized lock files. To clear this warning, remove package-lock.json.
warning discord.js ><EMAIL_ADDRESS>use node-fetch instead
warning<EMAIL_ADDRESS>The engine "ender" appears to be invalid.
warning " ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>- 3".
warning " ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>warning " ><EMAIL_ADDRESS>has unmet peer dependency "register-scheme@github:devsnek/node-register-scheme".
warning " ><EMAIL_ADDRESS>has unmet peer dependency "<EMAIL_ADDRESS>warning Error running install script for optional dependency: "C:\Users\Shanker\AppData\Local\Temp\insomnia_2020.5.2\insomnia-plugin-discord-rich-presence-1610124828199@newrelic\native-metrics: Command failed.
Exit code: 1
Command: node ./lib/pre-build.js install native_metrics
Arguments:
Directory: C:\Users\Shanker\AppData\Local\Temp\insomnia_2020.5.2\insomnia-plugin-discord-rich-presence-1610124828199@newrelic\native-metrics
Output:
Attempting install in native-metrics module. Please note that this is an
OPTIONAL dependency, and any resultant errors in this process will not
affect the general performance of the New Relic agent, but event loop and
garbage collection metrics will not be collected.
node-gyp.cmd clean configure
Failed to execute native-metrics install: No pre-built artifacts for your OS/architecture."
—

Are you trying to install this manually or through Insomnia?

Are you trying to install this manually or through Insomnia?

Are you trying to install this manually or through Insomnia?

I have tried to install the plugin via application and website of Insomnia.

Are you trying to install this manually or through Insomnia?

I have tried to install the plugin via application and website of Insomnia.

Hi, i have another error :
Error: Yarn error warning insomnia-plugin-discord-rich-presence > discord-urpc ><EMAIL_ADDRESS>Please upgrade  to version 7 or higher.  Older versions may use Math.random() in certain circumstances, which is known to be problematic.  See https://v8.dev/blog/math-random for details.
at file:///C:/Users/monst/AppData/Local/insomnia/app-2021.7.2/resources/app.asar/bundle.js:117539:16
at ChildProcess.exithandler (child_process.js:303:7)
at ChildProcess.emit (events.js:315:20)
at maybeClose (internal/child_process.js:1021:16)
at Socket.<anonymous> (internal/child_process.js:443:11)
at Socket.emit (events.js:315:20)
at Pipe.<anonymous> (net.js:674:12)


Pages with / in title do not open correctly

I have a note named kode/aaron but when I try and open it with this workflow it opens a new page kode%2Faaron. The page itself is saved on my filesystem as kode%2Faaron.md though.
Edit: I fixed by changing the lqs script filter to:
ObjC.import('stdlib')

function run(argv) {

let path = $.getenv('MyPKMPath')

let secondPath = `${path}/pages`
  var query = argv[0];
	let items = {"items": []}
function getAllFiles(){

	let files = Application('System Events').folders.byName(secondPath).diskItems.name()
	for (const x in files){
		if (files[x].toLowerCase().includes(argv[0].toLowerCase())){
		items.items.push({"title": files[x].replace("%2F", "/"), "subtitle": files[x].replace("%2F", "/"), "arg": files[x]})
}
	}

}
getAllFiles()
return(JSON.stringify(items));
}

and the associated run script to:
ObjC.import('stdlib')

function run(argv) {

var app = Application.currentApplication()
app.includeStandardAdditions = true

let path = $.getenv('MyPKMPath')
var query = argv[0]
	var file = `${path}/pages/${argv[0]}`
console.log(file)
	function readFile(file) {
    // Convert the file to a string
    var fileString = file.toString()

    // Read the file and return its contents
    return app.read(Path(fileString))
}
let match = readFile(file).match(/title::.*\n/)

let return2;
if (match != null) {
	return2 = match[0].replace("title::", "").trim()
}
else {
	return2= argv[0]
}

let title = path.split("/")
let titleFinal = title[title.length -1]
return(`logseq://graph/${titleFinal}?page=${return2.replace(".md", "").replace("%2F", "/")}`)

}

Technically you only really need to change the run script, but I changed the search script also to replace the ugly %2F on title names on search.
I would open a PR, but the scripts are inside the massive workflow file, so it's not PRable, to fix this we could pull the scripts out and reference them from the workflow by path instead of directly inserting the scripts inside the workflow itself.

@waynehoover, with the enhancement made with the namespace file name in logseq, this change may not be needed since the new standard is ___ as a separator of namespace in the filename. The encoded character is no longer used. Thoughts?


Windows.Storage.StorageLibrary.RequestAddFolderAsync() throws COMException

Describe the bug
This could be reproduced easily with a simple API call below. Similarly, StorageLibrary.RequestRemoveFolderAsync() does not work either.
It's probably caused by the underlying folder picker requiring an initialization with WinRT.Interop.InitializeWithWindow() call, but Windows.Storage.StorageLibrary API does not expose the folder picker to the API caller.
Steps to reproduce the bug
var libraryFolders = await StorageLibrary.GetLibraryAsync(KnownLibraryId.Music);
var folder = await libraryFolders.RequestAddFolderAsync();

Expected behavior
A folder picker shows up
Screenshots
No response
NuGet package version
Windows App SDK 1.5.5: 1.5.240627000
Packaging type
Packaged (MSIX)
Windows version
Insider Build (xxxxx)
IDE
Visual Studio 2022
Additional context
No response

Unfortunately this is documented. Issues like these are major sticking points in using packaged applications in an AppContainer.
If you are not targetting an AppContainer (i.e. setting the entrypoint to windows.partialTrustApplication or you explicitly set uap10:TrustLevel to AppContainer), the shell library API is usable. If you are targetting an AppContainer, be aware that the file pickers also don't work.

Hi, you might try following the instructions here if you haven't already: https://github.com/microsoft/CsWinRT/blob/master/docs/interop.md#windows-sdk
Please let us know if it didn't work for you.
Thanks!


Add Sample Datasets

See https://github.com/clarity-h2020/csis/issues/12

Data Sources can be configured in clarityCatalog.xml. Thereby it is possible specify a directory of netCDF files that is scanned by Thredds. This works fine for EURO-CORDEX Hazard Maps which can be made available via WMS and WCS:

MUKLIMO and SWICCA netCDF files however are not available via WMS out-of-the box, probably due to their different CRS / EPSG.

Thredds no longer needed: netCDF wil be converted to GeoTIF.


The dashboard only shows at most 20 projects.

If I use the below configuration:
maxAge: 0
fetchCount: 60

the fetchCount parameter is not used in the api/v4/projects call. I am unable to load more than 20 projects. It seems like the paging for projects call has not been implemented at all, or is buggy.

Thanks for reporting! Fixed with 2440d3fda558dc36b54406de0aac1ced43b9d8be


Definition in .js.flow ignored

Hello. I'm trying to go away from [ignore] ; <PROJECT_ROOT>/node_modules/. I got package @streetstrider/rootpath and rootpath.js.flow in it. Previously I got definitions for it in <PROJECT_ROOT>/flow-typed/rootpath.js where declare module '@streetstrider/rootpath' { … was defined.
I turned off ignore rule in my flowconfig and removed flow-typed/rootpath.js definition. Now, when I import Rootpath from '@streetstrider/rootpath the type is determined as any instead of proper Rootpath$Constructor type.

@StreetStrider I think you forgot // @flow comment at the top of this file
https://unpkg.com/<EMAIL_ADDRESS>

@TrySound, thanks, Bogdan. That did the trick. But as far as I remember, previously, doc says that flow pragma is not required inside files, like in flow-typed/* and .js.flow, since they are already considered as typedefs. I can't find anything in docs right now. The doc completely miss .js.flow info, like it's deprecated :scratch:.

 Just ping me.

This must be a person with expertise in the codebase. If someone like me would prepare a PR, he would definitely require help from some core guys. However, the docs in dire need of help.


'No' outputs missing

The two outer small purple decision boxes, 'is z a subdomain of x' and 'is y a subdomain of z', are both missing the 'NO' output.
Document Details
⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.

ID: 7861a800-7643-dca5-1046-232a51d6e61e
Version Independent ID: d78fc416-516b-15ab-4719-068f7d13ecca
Content: Use DMARC to validate email, setup steps - Office 365
Content Source: microsoft-365/security/office-365-security/email-authentication-dmarc-configure.md
Service: microsoft-365-security
Sub-service: mdo
GitHub Login: @MSFTTracyP
Microsoft Alias: tracyp

@MSFTTracyP Please help us in resolving this issue. Thanks

That's something a colleague and I also wondered more than once and we just guessed it might result in a DMARC failure. Would be great to actually see this clarified in the process schematic though 😃

@chrisda
Thanks for fixing!
Closing this issue.


Hook is not called for associations

GORM Playground Link
https://github.com/go-gorm/playground/pull/266
Description
Hi,
i'm trying to get rid of orphans for associations as soon as they are not in use anymore.
So i would like to create a hook for this associated entity to remove it after the reference id is set to nil.
But i looks like hooks are not working for as expected for associations.
This not solved! As the updated association is not calling a hook.


Create terraform for SLOs and alerting policies for paymentservice

#WHAT: Create two SLOs for the paymentservice (1 for availability and 1 for performance) and an alerting policy on budget burn for each one. SLO defined as 99.9% availability/performance over 30 day rolling window. Alert when 10% budget expended over 1 hour.
#WHY: Demonstrate best practice alerting on SLO error budget burn through terraform for this service
#HOW: Terraform resources added into initialization terraform scripts

Closed via #316


[ENG-1689] styles: update design system variables and layout

Summary
This PR syncs up designs closer to mocks and converts global variables to use semantic variables from our ui pallete.

match design system variables to UI Pallette
remove computed doc styles (temporary bridge from migration)
update button styles
update neutral colors to match UI Pallette
make combobox menu items smaller
make combobox input same size as label
exposes font-family as a override css variable

Screensthots
auth

disabled button

combobox

Install Integration

Object Field Mapping

Uninstall

[ENG-1680, ENG-1682]


Precompile for native token ERC-20 interface

The native token is special and has first-class support in our account model (as in all other EVM chains that I know of). Usually, developers need to handle this special case in their contracts. For example an exchange might need functions to swap tokens for other tokens, tokens for ZIL and ZIL for tokens.
To make life easier for developers, we should add a precompile which exposes an ERC-20-compatible interface to the chain's native token.
We'll have to think about how exactly to support allowances and events.

It probably makes sense to split this implementation into two:

A stateless, but incomplete version which doesn't support allowances.
A stateful and complete version later.

#804 has started doing this.


Refactor parsing logic

The regular expression can extract groups, and we should take advantage of that to do the parsing instead of relying on manual string splitting.

Honestly at this point we should just do a full rewrite.


vLLM OpenAI compatible server integration

Your vLLM integration works beautifully, I was wondering if you were looking to support their OpenAI-compatible server as well

+1, interested in this as well.


Automator: update istio/client-go@master dependency in istio/istio@master

Generated by Automator - 2021-05-20T17:53:18+00:00

@istio-testing: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-pilot-multicluster-tests_istio
202311cecf9c28b4c51887f093d52985bd3686a7
link
/test integ-pilot-multicluster-tests_istio

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

@istio-testing: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-pilot-multicluster-tests_istio
202311cecf9c28b4c51887f093d52985bd3686a7
link
/test integ-pilot-multicluster-tests_istio

integ-telemetry-mc-k8s-tests_istio
202311cecf9c28b4c51887f093d52985bd3686a7
link
/test integ-telemetry-mc-k8s-tests_istio

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

/retest

@istio-testing: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-telemetry-mc-k8s-tests_istio
202311cecf9c28b4c51887f093d52985bd3686a7
link
/test integ-telemetry-mc-k8s-tests_istio

integ-pilot-multicluster-tests_istio
202311cecf9c28b4c51887f093d52985bd3686a7
link
/test integ-pilot-multicluster-tests_istio

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

@istio-testing: PR needs rebase.

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

@istio-testing: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-pilot-multicluster-tests_istio
202311cecf9c28b4c51887f093d52985bd3686a7
link
/test integ-pilot-multicluster-tests_istio

integ-multicluster-k8s-tests_istio
e70c1a8fb213eb327a5ffeaaa3de7ad6a763bd71
link
/test integ-multicluster-k8s-tests_istio

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

@istio-testing: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-pilot-multicluster-tests_istio
202311cecf9c28b4c51887f093d52985bd3686a7
link
/test integ-pilot-multicluster-tests_istio

integ-multicluster-k8s-tests_istio
e70c1a8fb213eb327a5ffeaaa3de7ad6a763bd71
link
/test integ-multicluster-k8s-tests_istio

integ-security-multicluster-tests_istio
e70c1a8fb213eb327a5ffeaaa3de7ad6a763bd71
link
/test integ-security-multicluster-tests_istio

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

@istio-testing: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-pilot-multicluster-tests_istio
202311cecf9c28b4c51887f093d52985bd3686a7
link
/test integ-pilot-multicluster-tests_istio

integ-multicluster-k8s-tests_istio
e70c1a8fb213eb327a5ffeaaa3de7ad6a763bd71
link
/test integ-multicluster-k8s-tests_istio

integ-security-multicluster-tests_istio
e70c1a8fb213eb327a5ffeaaa3de7ad6a763bd71
link
/test integ-security-multicluster-tests_istio

integ-telemetry-mc-k8s-tests_istio
e70c1a8fb213eb327a5ffeaaa3de7ad6a763bd71
link
/test integ-telemetry-mc-k8s-tests_istio

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

/retest

@istio-testing: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-security-multicluster-tests_istio
e70c1a8fb213eb327a5ffeaaa3de7ad6a763bd71
link
/test integ-security-multicluster-tests_istio

integ-telemetry-mc-k8s-tests_istio
e70c1a8fb213eb327a5ffeaaa3de7ad6a763bd71
link
/test integ-telemetry-mc-k8s-tests_istio

integ-helm-tests_istio
51c593926294280bdebfcd72727596d935f0521c
link
/test integ-helm-tests_istio

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

/test integ-helm-tests_istio


Remove unnecessary predefined keycode.

This deleted the error handling - I rather keep the list complete even if it can be derived like you code shows. Thanks!


It is better to disable the action 'Download All…' on the 'Deleted only' context view against one ADLS Gen2 blob container

Storage Explorer Version: 1.27.0-dev
Build Number: 20221028.2
Branch: main
Platform/OS: Windows 10/Linux Ubuntu 22.04/MacOS Monterey 12.6 (Apple M1 Pro)
Architecture: ia32/x64
How Found: Ad-hoc testing
Regression From: Not a regression
Steps to Reproduce

Expand one ADLS Gen2 storage account -> Blob Containers.
Open one blob container -> Upload one blob then soft delete it.
Switch to the context view 'Deleted only'.
Check whether the action 'Download All' is disabled.

Expected Experience
It is better to disable the action 'Download All' on the context view 'Deleted only'.
Actual Experience
The action 'Download All' is enabled.

Verified this issue on the build main/20221111.1. Fixed.


nit: replacing redundant 'JWT token' with 'JWT'

"JWT" stands for "JSON web token" (https://datatracker.ietf.org/doc/html/rfc7519), so "JWT token" would mean "JSON web token token." This is a minor pet peeve of mine, so I feel it is my duty to fix this.

Thanks. I've squash merged it locally in the develop branch to avoid the back-and-forth as the autogenerated types files shouldn't be updated by hand.


Fix login with email for ldap users

authenticator.Authenticate has assume the login name is not an email, but username maybe an email. So when we find the user via email address, we should use user.LoginName instead of username which is an email address.

Are we sure about this?

Codecov Report

:exclamation: No coverage uploaded for pull request base (main@83c9035). Click here to learn what that means.
The diff coverage is 100.00%.

@@           Coverage Diff           @@
##             main   #18800   +/-   ##
=======================================
  Coverage        ?   46.49%
=======================================
  Files           ?      853
  Lines           ?   122473
  Branches        ?        0
=======================================
  Hits            ?    56947
  Misses          ?    58638
  Partials        ?     6888

Impacted Files
Coverage Δ

services/auth/signin.go
44.92% <100.00%> (ø)

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 83c9035...85f0048. Read the comment docs.

make lgtm work


Bjorncs/perf service dump

I confirm that this contribution is made under the terms of the license found in the root directory of this repository's source tree and that I have the authority necessary to make this contribution on behalf of its copyright owner.

@hakonhall PTAL

The idea is to tackle config id -> possibly service name or process name later?

Yes, that will be a future improvement. It's scope is too big to do now.


add graph_op builder

This hides all the name mangling logic from code that builds graph_ops, which makes that code simpler. It'll also make it easier to change name mangling behind the scenes to support more structures (like nested lists).
This should address some of the API comments @mhong had in #19361.

@swift-ci please test tensorflow linux cpu

@swift-ci please test tensorflow linux cpu

@swift-ci please test tensorflow linux cpu


Add click emit on step.vue

Add click emit on step.vue.
Permit to make action when user click on element step.
Please make sure these boxes are checked before submitting your PR, thank you!

[x] Make sure you follow Element's contributing guide (中文 | English | Español).
[x] Make sure you are merging your commits to dev branch.
[x] Add some descriptions and refer relative issues for you PR.

Use @click.native.


Refactor integration tests to use retries

Which Issue(s) this Pull Request Fixes

Resolves #354
Release Note

NONE

Notes for Reviewers

I requested Andrea's review but she is on PTO, I will merge this and address any things she has when she is back.


Failed to prepare environment for using test_mode

All tests failed:
(py_3_5_autoxtrabackup) [vagrant@localhost test]$ bats prepare_env.bats
 ✗ Running test_clone_percona_qa
   (in test file prepare_env.bats, line 10)
     `[ $status -eq 0 ]' failed

 ✗ Running test_clone_ps_server_from_conf
   (in test file prepare_env.bats, line 16)
     `[ $status -eq 0 ]' failed

 ✗ Running test_clone_pxb
   (in test file prepare_env.bats, line 22)
     `[ $status -eq 0 ]' failed

 ✗ Running test_build_pxb
   (in test file prepare_env.bats, line 28)
     `[ $status -eq 0 ]' failed

 ✗ Running test_build_server
   (in test file prepare_env.bats, line 34)
     `[ $status -eq 0 ]' failed

 ✗ Running test_rename_basedirs
   (in test file prepare_env.bats, line 40)
     `[ $status -eq 0 ]' failed

 ✗ Running test_prepare_startup
   (in test file prepare_env.bats, line 46)
     `[ $status -eq 0 ]' failed

 ✗ Running test_prepare_start_dynamic
   (in test file prepare_env.bats, line 52)
     `[ $status -eq 0 ]' failed

 ✗ Running test_start_server
   (in test file prepare_env.bats, line 58)
     `[ $status -eq 0 ]' failed

 ✗ Running test_extract_xb_archive
   (in test file prepare_env.bats, line 64)
     `[ $status -eq 0 ]' failed

 ✗ Running test_generate_config_files
   (in test file prepare_env.bats, line 70)
     `[ $status -eq 0 ]' failed

11 tests, 11 failures

For first failed test -> test_clone_percona_qa
class CloneBuildStartServer(TestModeConfCheck):
    """
    Class for cloning from git, building server from source and starting test server etc.
    This class will include all necessary actions for preparing test environment.
    Please see specific methods for clarity.
    """
    def __init__(self, config='/etc/bck.conf'):
        self.conf = config
        super().__init__(config=self.conf)
        #self.git_cmd = GeneralClass().gitcmd
        #self.xb_configs = GeneralClass().xb_configs
        # Creating needed path here
        t_obj = TestModeConfCheck(config=self.conf)
        if t_obj.check_test_path(t_obj.testpath):
            self.testpath = t_obj.testpath

It seems to be the default config file path hard-coded there.
Should be changed to reflect recent changes on config path.

It was because I have not enabled [TestConf].
Shame :)
Closing.


'engine' properties not stored properly

Hello,
I am trying to run a small simulation(TIS) using OPS. When loading back the storage, the engine properties like 'engine.options' and 'engine.name' do not show the right values.
I am concerned with 'n_steps_per_frame'. I do not know if this is being right in the simulation.
Following is the link to the files
TIS_engine_issue.zip
In the tis_running_script.py, the values are as follows (for example)
'n_frames_max': 6,
'n_steps_per_frame': 3
When I load back the engine, it shows me
'n_steps_per_frame': 50000,
'n_frames_max': 2000,
To run the script on GPU , type
nohup ./tis_running_script.py > log &
I get that somehow the values are being cached from the inital_trajectory.nc. Is there a way to correct it ? Or is there a silly mistake that I am making ? Please feel free to correct
My OPS version is : 0.9.3
Python 2

How are you loading the engine back in? My guess is loading by number (storage.engines[0])?
If that's the case, then the problem is that you have multiple engines. Every snapshot knows the engine that created it, so as soon as you save the initial trajectory, you also save the engine that created that trajectory (with options 50k steps per frame, 2k frames max).
You can instead load by name (that's the main purpose of naming objects).
I checked out 0.9.3, ran your script (although I set number of MC steps to 0, since it will save everything before running the dynamics), and ran the following:
In [1]: import openpathsampling as paths

In [2]: storage = paths.Storage("./result_storage.nc", mode='r')

In [3]: len(storage.engines)
Out[3]: 2

In [4]: storage.engines[0].options
Out[4]:
{'n_frames_max': 2000,
 'n_steps_per_frame': 50000,
 'on_error': 'fail',
 'on_max_length': 'fail',
 'on_nan': 'fail',
 'on_retry': 'full',
 'retries_when_error': 0,
 'retries_when_max_length': 0,
 'retries_when_nan': 2}

In [5]: storage.engines[0].name
Out[5]: u'TPS_280K_TIS'

In [6]: storage.engines[1].options
Out[6]:
{'n_frames_max': 6,
 'n_steps_per_frame': 3,
 'on_error': 'fail',
 'on_max_length': 'fail',
 'on_nan': 'fail',
 'on_retry': 'full',
 'retries_when_error': 0,
 'retries_when_max_length': 0,
 'retries_when_nan': 2}

In [7]: storage.engines[1].name
Out[7]: u'Random_name'

In [8]: storage.engines['Random_name'].options['n_steps_per_frame']
Out[8]: 3

The last line shows how to load an engine by name (and verifies that the n_steps_per_frame is correct).
Note that the scheme, when reloaded, is using the correct engine:
In [9]: len(storage.schemes)
Out[9]: 1

In [10]: scheme = storage.schemes[0]  # only 1 exists!

In [11]: scheme.movers['shooting'][0].movers[0].engine.name
Out[11]: u'Random_name'

Let me know if that fixes it!

Thanks @dwhswenson for the quick reply and solving it.
Yes, it fixes it (& indeed it was a silly one).
Cheers

Glad that was all that was needed, and it's a useful issue because it points out that we should change some of the examples to use best practices for naming/reloading objects. In my opinion, the best practices are:

Use names whenever possible: If you're likely to reload it, and if it can be given a name, then give it a name (and then reload by name).
Special instances of objects that can't be given names (snapshots, trajectories, etc.) can be assigned a name by putting then in tags store, e.g., storage.tags['name_of_snapshot'] = snapshot, and reloaded from that.
Reloading by number should almost never by used. Analysis will typically use an iterator, and I think everything else falls into the two cases above. I think reloading by number is mainly useful for debugging.

That said, I definitely don't always follow these best practices, even though I should. For example, since I know there's usually only one network and one scheme in my file, I almost always reload those by number. Probably a bad habit.


feat(mellow-react): Button component

Add Button Component for mellow-react template
Implementation

Use prop-types for type checking - https://www.npmjs.com/package/prop-types
Implement button variant via prop

primary

outline

Implement button width via prop

fullwidth (boolean)

Implement button inactive state via prop

inactive (boolean)

Implement button link via href prop
Implement events in via other props

.take

is there any way to get the UI for this so I could work on the issue


Fit to screen

Is your feature request related to a problem? Please describe.
I need to add a functionality to 'fit to screen' ,for example for content very wide.
Describe the solution you'd like
A function to adjust the scale automatically to have all content inside wrapper.
Describe alternatives you've considered
At the moment I do not know hoy to solve it

Hi, can you show an example of what are you trying to do?

Imagine a very big diagram. And it is very wide. At scale of 1 (100%) you can't see everything because it is bigger than the container. With a fit to screen function, the scale would be automatically set in order to have all content visible. In our example, scale would be lower than 1 in order to make content smaller and visible.

Have same problem. Did you find any solution to this?

If one of you provide the codesandbox example I can come up with a solution

I think we cannot provide a codesandbox as this is a requested feature.
Let me know if what I said it is not clear and I will try to explain.

I've found a way to do this, you can either use the centerView or setTransform handler functions. If you have a ref to the wrapper component (something that might have a fixed width / height on your page) and also a ref to the actual content itself (you can wrap it in a div and attach the ref to that), then you can easily calculate the "scale" needed to call one of the above functions. For example:
// assume wrapperRef and contentRef are declared and attached

  const fitContentToWrapper = useCallback(
    (centerView: (scale: number) => void) => {
      if (wrapperRef.current && contentRef.current) {
        const wrapperWidth = wrapperRef.current.clientWidth;
        const wrapperHeight = wrapperRef.current.clientHeight;

        const contentWidth = contentRef.current.clientWidth;
        const contentHeight = contentRef.current.clientHeight;

        const widthScale = wrapperWidth / contentWidth;
        const heightScale = wrapperHeight / contentHeight;

        const scale = widthScale < heightScale ? widthScale : heightScale;

        centerView(scale);
      }
    },
    []
  );

  ...

return (

      <TransformWrapper>
        {({ centerView }) => (
          <>

              <button onClick={() => fitContentToWrapper(centerView)}>fit</button>

            <TransformComponent>

{CONTENT HERE}

            </TransformComponent>
          </>
        )}
      </TransformWrapper>

  );


update .env examples

to disable provider_allow_list and models_config…path by default

Modified config.go default for proxy port from 8080 to 8082 to remove conflict on packaged releases (where Llama.cpp is currently listening on 8080.  This reduces the need to have more variables for the packaged builds.
Also, based on discussion with @shev-titan - reduced the .env.example to the mininmum requirements for packaging (that we'll eventually inject via GitHub variables since most of them change with testnet or mainnet deploys.
Finally, included env.full example file that is taken right from config.go so that we have a full list of variables that the more advanced folks can work with.  Eventually will have to add further descriptions.  If anyone has an easy way to generate a .env.full.example file from config.go ... please go for it :-)


[Docs] Documentation for using DocumentSelectionState

In the TextInput docs, it has a prop for selectionState. I tried creating an instance of DocumentSelectionState, and adding a listener, but no events come through. Whats more, is that there is another undocumented prop (onSelectionChange) for TextInput that should do the same thing, however the function never seems to be called.
https://rnplay.org/apps/eZnvIA
Is there an example of using DocumentSelectionState somewhere?

I'm not familiar with this myself, any idea @vjeux?

cc @sahrens

I think onSelectionChange is only supported in our internal TextView comonent that we haven't released (it's tangled with some other internal FB infra), so unfortunately this isn't going to work without a bit of effort....

Hi there! This issue is being closed because it has been inactive for a while.
But don't worry, it will live on with ProductPains! Check out it's new home: https://productpains.com/post/react-native/docs-documentation-for-using-documentselectionstate


Topic/drawable symbol

rebased

Something isn't quite right with the layout:

Seems to be text-variable-anchor...

Turns out SymbolBucket.hasVariablePlacement changes during the layout phase, which may happen after we create drawables.  I wonder if the render tests are sensitive to that?

I saw the icons rendering incorrectly, like the atlas or offsets were wrong, but Xcode crashed before I could debug it, and I haven't been able to reproduce it.
Otherwise, it seems to be working.

I found one problem: when changing between styles that contain the same layer, RenderLayer::update() may be called up to several times with the old bucket still in place after the tile drawables have been removed.  That caused new drawables to be created based on the old bucket data, which those drawables would later be updated by the tweaker with properties from the new style, leading to various strange results.
I suspect we want to avoid creating drawables until the bucket layout is complete, but I don't see any way to check for that directly.  Checking needsUpload did not work.  For now, I'm detecting when an ID value in the bucket is changing, and that seems to suffice.


Installation issue on Mac

I have a student and she tried to install it on MAC.
This is what she got.
-- The C compiler identification is GNU 7.5.0

-- The CXX compiler identification is GNU 7.5.0

-- Detecting C compiler ABI info

-- Detecting C compiler ABI info - done

-- Check for working C compiler: /usr/bin/cc - skipped

-- Detecting C compile features

-- Detecting C compile features - done

-- Detecting CXX compiler ABI info

-- Detecting CXX compiler ABI info - done

-- Check for working CXX compiler: /usr/bin/c++ - skipped

-- Detecting CXX compile features

-- Detecting CXX compile features - done

-- Found PythonInterp: /home/jh/anaconda3/envs/test/bin/python (found version "3.8")

-- Python output: /home/jh/anaconda3/envs/test/lib/python3.8/site-packages/hoomd

-- Looking for a HOOMD installation at /home/jh/anaconda3/envs/test/lib/python3.8/site-packages/hoomd

-- Found hoomd installation at /home/jh/anaconda3/envs/test/lib/python3.8/site-packages/hoomd

-- Found HOOMD include directory: /home/jh/anaconda3/envs/test/lib/python3.8/site-packages/hoomd/include

CMake Error at cmake/Modules/FindHOOMD.cmake:84 (include):

  include could not find requested file:

    hoomd_cache

Call Stack (most recent call first):

  CMakeLists.txt:13 (find_package)

CMake Error at cmake/Modules/FindHOOMD.cmake:87 (include):

  include could not find requested file:

    CMake_build_options

Call Stack (most recent call first):

  CMakeLists.txt:13 (find_package)

CMake Error at cmake/Modules/FindHOOMD.cmake:88 (include):

  include could not find requested file:

    CMake_preprocessor_flags

Call Stack (most recent call first):

  CMakeLists.txt:13 (find_package)

CMake Error at cmake/Modules/FindHOOMD.cmake:90 (include):

  include could not find requested file:

    CMake_install_options

Call Stack (most recent call first):

  CMakeLists.txt:13 (find_package)

CMake Error at cmake/Modules/FindHOOMD.cmake:93 (include):

  include could not find requested file:

    HOOMDPythonSetup

Call Stack (most recent call first):

  CMakeLists.txt:13 (find_package)

CMake Error at cmake/Modules/FindHOOMD.cmake:95 (include):

  include could not find requested file:

    HOOMDCUDASetup

Call Stack (most recent call first):

  CMakeLists.txt:13 (find_package)

CMake Error at cmake/Modules/FindHOOMD.cmake:97 (include):

  include could not find requested file:

    HOOMDCFlagsSetup

Call Stack (most recent call first):

  CMakeLists.txt:13 (find_package)

CMake Error at cmake/Modules/FindHOOMD.cmake:99 (include):

  include could not find requested file:

    HOOMDOSSpecificSetup

Call Stack (most recent call first):

  CMakeLists.txt:13 (find_package)

CMake Error at cmake/Modules/FindHOOMD.cmake:101 (include):

  include could not find requested file:

    HOOMDCommonLibsSetup

Call Stack (most recent call first):

  CMakeLists.txt:13 (find_package)

CMake Error at cmake/Modules/FindHOOMD.cmake:103 (include):

  include could not find requested file:

    HOOMDMacros

Call Stack (most recent call first):

  CMakeLists.txt:13 (find_package)

CMake Error at cmake/Modules/FindHOOMD.cmake:105 (include):

  include could not find requested file:

    HOOMDMPISetup

Call Stack (most recent call first):

  CMakeLists.txt:13 (find_package)

-- Downloading CPM.cmake to /home/jh/git/hoomd-dlext/build/cmake/CPM_0.34.2.cmake

-- CPM: adding package<EMAIL_ADDRESS>(v0.6)

-- No build type specified; defaulting to CMAKE_BUILD_TYPE=Release.

-- C++11 support has been enabled by default.

-- Install plugin to: /home/jh/anaconda3/envs/test/lib/python3.8/site-packages/hoomd

CMake Error at python/CMakeLists.txt:3 (pybind11_add_module):

  Unknown CMake command "pybind11_add_module".

-- Configuring incomplete, errors occurred!

See also "/home/jh/git/hoomd-dlext/build/CMakeFiles/CMakeOutput.log".

I didn't dive in too deep yet.
Guesses of what could go wrong

HOOMD-blue base installation doesn't provide these files for some reason
Mac does things differently

Maybe we can add a CI test and try to install it on MAC?
I don't have access to a mac otherwise.

There's an issue on MacOS unrelated to what you're seeing here (PR coming). This issue I suspect has to do with the student installing
conda install -c glotzer hoomd
instead of
conda install -c conda-forge hoomd

With #12 I'm able to build on MacOS both by compiling HOOMD manually and installing through conda with conda install -c conda-forge hoomd

Thank you Pablo for looking into this. Appreciated
Sent from my iPhone
On Mar 3, 2022, at 10:07 PM, Pablo Zubieta @.***> wrote:

Closed #11https://urldefense.com/v3/__https://github.com/SSAGESLabs/hoomd-dlext/issues/11__;!!BpyFHLRN4TMTrA!tNh3qoCN1z26_irAyOR_tBR93arT3PU1IL9oigmQ-gCY_7rClI_A41bfgFRO_-rABt2uz9By$.
—
Reply to this email directly, view it on GitHubhttps://urldefense.com/v3/__https://github.com/SSAGESLabs/hoomd-dlext/issues/11*event-6182653442__;Iw!!BpyFHLRN4TMTrA!tNh3qoCN1z26_irAyOR_tBR93arT3PU1IL9oigmQ-gCY_7rClI_A41bfgFRO_-rABsu7O_yn$, or unsubscribehttps://urldefense.com/v3/__https://github.com/notifications/unsubscribe-auth/AG7R7HARVIHCIWD4EMDY3QTU6GEBDANCNFSM5P34CYJA__;!!BpyFHLRN4TMTrA!tNh3qoCN1z26_irAyOR_tBR93arT3PU1IL9oigmQ-gCY_7rClI_A41bfgFRO_-rABlyssOGZ$.
Triage notifications on the go with GitHub Mobile for iOShttps://urldefense.com/v3/__https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675__;!!BpyFHLRN4TMTrA!tNh3qoCN1z26_irAyOR_tBR93arT3PU1IL9oigmQ-gCY_7rClI_A41bfgFRO_-rABnzUDAM9$ or Androidhttps://urldefense.com/v3/__https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign*3Dnotification-email*26utm_medium*3Demail*26utm_source*3Dgithub__;JSUlJSU!!BpyFHLRN4TMTrA!tNh3qoCN1z26_irAyOR_tBR93arT3PU1IL9oigmQ-gCY_7rClI_A41bfgFRO_-rABkaGEUe3$.
You are receiving this because you authored the thread.Message ID: @.***>


[BEAM-7389] Add Python snippet for FlatMap transform

Add Python snippet for FlatMap transform

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

[x] Choose reviewer(s) and mention them in a comment (R: @username).
[x] Format the pull request title like [BEAM-XXX] Fixes bug in ApproximateQuantiles, where you replace BEAM-XXX with the appropriate JIRA issue, if applicable. This will automatically link the pull request to the issue.
[x] If this contribution is large, please file an Apache Individual Contributor License Agreement.

R: @aaltay Can you have a look please?

R: @ibzib  could you review this PR when you get a chance?

LGTM


Incompliant encoding of GeneralizedTime in OCSP Repsonse

While X.680 and X.690 allow any number of digits behind the decimal point for a GeneralizedTime, RFC 5280, Section <IP_ADDRESS>.2 says that "GeneralizedTime values MUST NOT include fractional seconds" for X.509 certificates and CRLs. This also applies to OCSP responses as per RFC 6960, Section <IP_ADDRESS>.
Before 879bb29bb0058a0723326de6edebb201e4cbc0b8, Bouncy Castle always encoded GeneralizedTime without fractional seconds; after the change, it always uses up to 7 digits, because of the format string @"yyyyMMddHHmmss.FFFFFFFK", see https://github.com/bcgit/bc-csharp/blob/master/crypto/src/asn1/Asn1GeneralizedTime.cs#L270.
When encoding an OCSP Response, if you pass in values with fractions of a second, it will incorrectly also encode the fractions of seconds. This happens in at least four places of a usual OCSP Response:

thisUpdate (https://github.com/bcgit/bc-csharp/blob/master/crypto/src/asn1/ocsp/SingleResponse.cs)
nextUpdate (dto.)
producedAt (https://github.com/bcgit/bc-csharp/blob/master/crypto/src/asn1/ocsp/ResponseData.cs)
revocationTime (https://github.com/bcgit/bc-csharp/blob/master/crypto/src/asn1/ocsp/RevokedInfo.cs)

As a workaround, the caller may remove the fractions of seconds, for example by calling a method like this:
        public static DateTime RemoveSubSecondsFromDateTime(DateTime dateTimeWithFractionOfSeconds)
            => dateTimeWithFractionOfSeconds.AddTicks(-(dateTimeWithFractionOfSeconds.Ticks % TimeSpan.TicksPerSecond));

Otherwise, the generated OCSP Response is incompliant and some clients reject it.
I suggest we search for all uses of GeneralizedTime in CRLs, X.509 certificates, and OCSP messages and remove the fraction of seconds with a call like the one above.

I've now (finally) reviewed all uses of GeneralizedTime and auto-adjusted the precision when constructed from a DateTime, for X.509 and related specs. This includes the mentioned OCSP fields and most other usages, except a couple in CMP and TSP.
Note that we do not enforce this for parsed values, and we also do not auto-adjust existing instances of Asn1GeneralizedTime provided during construction.


Possibility of negative values in threshold overrides

The problem
Es wäre schön wenn negative Wert bei Schwellenwert-Überschreitungen möglich wären.
Version of nodejs
16
Version of ioBroker js-controller
4.0.24
Version of Adapter
0.8
Version of awtrix-light firmware
0.88
Operating system running ioBroker
Linux
Checklist of files to include below

[X] iobroker.current.log (Please share the logs in debug mode)
[ ] Contents of the JavaScript browser console (always include in cases of issues with the user interface)

Additional information & file uploads
No response

Da gibt es eigentlich keine Limits?


Enhance search addons custom keybinding support.

At my place of work we've had several requests to change the editor's search functionality to mimic the browser's search.  Specifically:

Search bar should remain displayed while user cycles through matches.
When closing search, the highlighted searches should disappear.
Use same shortcuts Enter (Next) / Shift-Enter (Previous) as browser.

I do not believe this is possible to accomplish in the current state due to the search addons current usage of the dialog addon.  It would be useful to expose the dialog onClose and onKeyDown extension options through the search addon to allow for further customization of the search key bindings.

Done via #3338


relationship with details

How can I add a related field that has one more detail, for example:
table_os
->id,nome
table_itens
->id,nome
table_os_item
->os_id,item_id,amount
I usually use jquery to create the inputs dynamically, but I wanted to use the bread

You're looking for the hasManyThrough relation.  Voyager doesn't currently support this in its UI(and there's no easy way to make it), but you're free to add the relation to your models for the purposes of your site's front-end.  Please refer to the laravel docs for further information on its usage.


Uglify fails to minify

I'm using create-react-app and it fails to generate the build with this module because Uglify does not support ES6 template strings.

Will fix this soon. Thanks for pointing that out!

Fixed in version 1.0.3

@ytiurin Thank you very much!


Caused by: java.lang.IllegalAccessError: tried to access method android.support.v4.net.ConnectivityManagerCompat.:(Lcom/facebook/react/bridge/ReactApplicationContext;)V from class com.facebook.react.modules.netinfo.NetInfoModule

compile 'com.android.support:design:23.2.1'
compile 'com.android.support:support-v13:23.2.1'
compile 'com.facebook.react:react-native:+'
please help me!How to solve the problem?I wann't to reduced my support version,thanks!

I get this too, using React Native 0.41.2
E/AndroidRuntime: FATAL EXCEPTION: AsyncTask #1
                  Process: com.aadhk.woinvoice, PID: 2862
                  java.lang.RuntimeException: An error occurred while executing doInBackground()
                      at android.os.AsyncTask$3.done(AsyncTask.java:309)
                      at java.util.concurrent.FutureTask.finishCompletion(FutureTask.java:354)
                      at java.util.concurrent.FutureTask.setException(FutureTask.java:223)
                      at java.util.concurrent.FutureTask.run(FutureTask.java:242)
                      at android.os.AsyncTask$SerialExecutor$1.run(AsyncTask.java:234)
                      at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1113)
                      at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:588)
                      at java.lang.Thread.run(Thread.java:818)
                   Caused by: java.lang.IllegalAccessError: Method 'void android.support.v4.net.ConnectivityManagerCompat.<init>()' is inaccessible to class 'com.facebook.react.modules.netinfo.NetInfoModule' (declaration of 'com.facebook.react.modules.netinfo.NetInfoModule' appears in /data/data/com.aadhk.woinvoice/files/instant-run/dex/slice-com.facebook.react-react-native-0.20.1_dd7e8361611dc34898c750d11b5ece4d3990a0aa-classes.dex)
                      at com.facebook.react.modules.netinfo.NetInfoModule.<init>(NetInfoModule.java:55)
                      at com.facebook.react.shell.MainReactPackage.createNativeModules(MainReactPackage.java:67)
                      at com.facebook.react.ReactInstanceManagerImpl.processPackage(ReactInstanceManagerImpl.java:793)
                      at com.facebook.react.ReactInstanceManagerImpl.createReactContext(ReactInstanceManagerImpl.java:730)
                      at com.facebook.react.ReactInstanceManagerImpl.access$600(ReactInstanceManagerImpl.java:91)
                      at com.facebook.react.ReactInstanceManagerImpl$ReactContextInitAsyncTask.doInBackground(ReactInstanceManagerImpl.java:184)
                      at com.facebook.react.ReactInstanceManagerImpl$ReactContextInitAsyncTask.doInBackground(ReactInstanceManagerImpl.java:169)
                      at android.os.AsyncTask$2.call(AsyncTask.java:295)
                      at java.util.concurrent.FutureTask.run(FutureTask.java:237)
                      at android.os.AsyncTask$SerialExecutor$1.run(AsyncTask.java:234)
                      at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1113)
                      at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:588)
                      at java.lang.Thread.run(Thread.java:818)

Using com.android.support:appcompat-v7:23.3.0

use compile 'com.facebook.react:react-native:+',make sure the build package is up to date,then in your activity to extends ReactActivity,in your Application to implement ReactApplication.

I solved my problem, the problem was that I was using com.facebook.react:react-native:+ which pulled in version 21 from the web, instead of 0.41.2 locally due to a path error.  I changed it to specify 0.41.2 specifically, then it failed to find it, enabling me to discover and fix the path issue.

Hi there! This issue is being closed because it has been inactive for a while.
But don't worry, it will live on with Canny! Check out its new home: https://react-native.canny.io/feature-requests/p/caused-by-javalangillegalaccesserror-tried-to-access-method-androidsupportv4netc


Code updated to work with Dart 2

I made some minor changes in order to make the project work with Dart 2.x, basically enforced strong typing and removed deprecated constants from code.

Thank you, I think it's a great pr and having it working in Dart@2 is awesome.


fix warning in ip6.cpp with logging enabled

When logging enabled, a line in ip6.cpp causes format warnings, this fixes that warning

this got polluted by mistake, I will redo it


auto ingest generatejson failed

(ocp)abaden@Alexs-MBP-3:~/Projects/Research/cookingest$ python generatejson.py
Traceback (most recent call last):
  File "generatejson.py", line 21, in <module>
    import ndio.remote.ndingest as NI
ImportError: No module named ndingest

I followed the instructions here: http://docs.neurodata.io/ndstore/sphinx/ingesting.html but I seem to be missing something. Do I need a different version of ndio?

So it looks like @j6k4m8 hasn't rolled the latest into a 1.0.1, I'll poke him about it

We're on a monthly rollout cycle, scheduled to roll to 1.1.0 on Sunday (first day of the month) if everything is stable.

Ah, nice, my understanding was flawed then, I thought the release cycle was bi-monthly :) Thanks!

Got it. I followed Jordan's instructions and am now running the ndio from the master branch in the repo.
But, I'm still getting an error (though a new one this time):
Traceback (most recent call last):
  File "generatejson.py", line 87, in <module>
    main()
  File "generatejson.py", line 84, in main
    ni.post_data(SITE_HOST)
  File "/Users/abaden/.virtualenvs/ocp/lib/python2.7/site-packages/ndio/remote/ndingest.py", line 517, in post_data
    raise OSError("Error opening file")
OSError: Error opening file

I'm using the generatejson from the docs: https://github.com/neurodata/ndstore/blob/master/ingest/autoingest/generatejson.py

@alexbaden Did this not work? If not let's resolve this with @Aeusman.

No, I ended up writing an ingest script instead. I attached my generatejson.py script, but the data has already been ingested using those parameters, so you will want to try slightly different ones.
It turned out that the size of the tif image was different than the size of the catmaid stack (the catmaid stack was bigger to keep powers of 2). I forget exactly what the image was, but it was something like 6500 x 4500 instead of 65xx by 45xx. You can find out in the cook16 projinfo.
generatejson.py.zip

Figured out the problem, generatejson in ndstore was incorrectly passing a parameter in post_data(), usage has been changed. I've created a pull request to fix @kunallillaney


[Bug]: UZB Stick hangging

Checklist

[X]  I am not using Home Assistant. Or: a developer has told me to come here.
[X] I have checked the troubleshooting section and my problem is not described there.
[X] I have read the changelog and my problem is not mentioned there.

Deploy method
Docker
Z-Wave JS UI version
<IP_ADDRESS>d0208
ZwaveJS version
10.3.0
Describe the bug
System works perfectly after a reboot. Always after different times (sometimes only 2minutes or 5minutes) my blue LED on the Zwave Stick (UZB) lights up permanently and all battery powered devices show ES.
Only after a reboot the stack works for maybe 5 minutes.
To Reproduce

Expected behavior

Additional context
No response

zwavejs_2022-10-14.log
zwavejs_current.log
Here are the logs. This time it took a little longer. The thermostat now shows ES according to the UI but continues to send it merrily. But this happens with all devices.

Is this an UZB or an UZB 7?

UZB from zwave.me
https://z-wave.me/products/uzb/
freundliche Grüße
Niklas Fischbach
Niklas Fischbach | Software Engineer
Phone +49-2761-859858-43tel:+49-2761-859858-43 |<EMAIL_ADDRESS>[cid:logoneu_bb270a0c-350e-4063-93f1-2037feddc936.png]          MEHRWERT SYSTEMHAUS GMBH
IN DER TRIFT 1
DE 57462 OLPE
https://mehrwert.net
Sitz der Gesellschaft: Olpe, AG Siegen HRB 7711 | Geschäftsführer: Marcus Schneider

Von: Joachim Marthinsen Giæver @.>
Gesendet: Sunday, October 16, 2022 2:09:14 PM
An: zwave-js/node-zwave-js @.>
Cc: Niklas Fischbach @.>; Author @.>
Betreff: Re: [zwave-js/node-zwave-js] [Bug]: UZB Stick hangging (Issue #5161)
Is this an UZB or an UZB 7?
—
Reply to this email directly, view it on GitHubhttps://github.com/zwave-js/node-zwave-js/issues/5161#issuecomment-1279956771, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AKXMNTBVGD5FFAZR6SOLH3TWDPV6VANCNFSM6AAAAAARFFIXZE.
You are receiving this because you authored the thread.Message ID: @.***>

500 series then.

By the way: I am currently surprised that the blue LED on my ZME_UZB1 is permanently lit very often a day. I've had this for a few weeks. I don't know if that helps. But that came from some ZWaveJS version.

So I've a fresh installed docker instance.
I have added 1 wall plug and get a network error. Here are the logs.
zwave-js-ui-store.zip
Is my stick broken?
Thanks!

2022-11-08T13:22:33.167Z DRIVER   version 10.3.0
2022-11-08T13:22:33.167Z DRIVER
2022-11-08T13:22:33.167Z DRIVER   starting driver...
2022-11-08T13:22:33.167Z DRIVER   opening serial port /dev/zwave
2022-11-08T13:22:33.169Z DRIVER   serial port opened
2022-11-08T13:22:33.169Z SERIAL » [NAK]                                                                   (0x15)
2022-11-08T13:22:33.169Z DRIVER   loading configuration...
2022-11-08T13:22:33.170Z CONFIG   Using external configuration dir /usr/src/app/store/.config-db
2022-11-08T13:22:33.170Z CONFIG   version 10.3.0
2022-11-08T13:22:33.368Z SERIAL « [DISCARDED] invalid data 0xc01cd7000c0005000253efa7b75afcc0         (16 bytes)
2022-11-08T13:22:33.505Z DRIVER   beginning interview...
2022-11-08T13:22:33.505Z DRIVER   added request handler for AddNodeToNetwork (0x4a)...
1 registered
2022-11-08T13:22:33.505Z DRIVER   added request handler for RemoveNodeFromNetwork (0x4b)...
1 registered
2022-11-08T13:22:33.505Z DRIVER   added request handler for ReplaceFailedNode (0x63)...
1 registered
2022-11-08T13:22:33.505Z CNTRLR   querying controller IDs...
2022-11-08T13:22:33.507Z SERIAL » 0x01030020dc                                                         (5 bytes)
2022-11-08T13:22:33.508Z DRIVER » [REQ] [GetControllerId]
2022-11-08T13:22:34.509Z CNTRLR   Failed to execute controller command after 1/3 attempts. Scheduling next try i
n 100 ms.
2022-11-08T13:22:34.610Z SERIAL » 0x01030020dc                                                         (5 bytes)
2022-11-08T13:22:34.610Z DRIVER » [REQ] [GetControllerId]
2022-11-08T13:22:35.612Z CNTRLR   Failed to execute controller command after 2/3 attempts. Scheduling next try i
n 1100 ms.
2022-11-08T13:22:36.713Z SERIAL » 0x01030020dc                                                         (5 bytes)
2022-11-08T13:22:36.713Z DRIVER » [REQ] [GetControllerId]
2022-11-08T13:22:37.715Z DRIVER   Failed to initialize the driver: ZWaveError: Timeout while waiting for an ACK
from the controller (ZW0200)
at Driver.sendMessage (/usr/src/app/node_modules/zwave-js/src/lib/driver/D
river.ts:3990:23)
at ZWaveController.identify (/usr/src/app/node_modules/zwave-js/src/lib/co
ntroller/Controller.ts:713:33)
at Driver.initializeControllerAndNodes (/usr/src/app/node_modules/zwave-js
/src/lib/driver/Driver.ts:1208:26)
at Immediate. (/usr/src/app/node_modules/zwave-js/src/lib/drive
r/Driver.ts:1015:16)
2022-11-08T13:22:37.715Z DRIVER   destroying driver instance...
2022-11-08T13:22:37.717Z DRIVER   driver instance destroyed
2022-11-08T13:22:37.720Z DRIVER   ███████╗ ██╗    ██╗  █████╗  ██╗   ██╗ ███████╗             ██╗ ███████╗
╚══███╔╝ ██║    ██║ ██╔══██╗ ██║   ██║ ██╔════╝             ██║ ██╔════╝
███╔╝  ██║ █╗ ██║ ███████║ ██║   ██║ █████╗   █████╗      ██║ ███████╗
███╔╝   ██║███╗██║ ██╔══██║ ╚██╗ ██╔╝ ██╔══╝   ╚════╝ ██   ██║ ╚════██║
███████╗ ╚███╔███╔╝ ██║  ██║  ╚████╔╝  ███████╗        ╚█████╔╝ ███████║
╚══════╝  ╚══╝╚══╝  ╚═╝  ╚═╝   ╚═══╝   ╚══════╝         ╚════╝  ╚══════╝
2022-11-08T13:22:37.720Z DRIVER   version 10.3.0
2022-11-08T13:22:37.720Z DRIVER
2022-11-08T13:22:37.720Z DRIVER   starting driver...
2022-11-08T13:22:37.721Z DRIVER   opening serial port /dev/zwave
2022-11-08T13:22:37.722Z DRIVER   serial port opened
2022-11-08T13:22:37.723Z SERIAL » [NAK]                                                                   (0x15)
2022-11-08T13:22:37.723Z DRIVER   loading configuration...
2022-11-08T13:22:37.724Z CONFIG   Using external configuration dir /usr/src/app/store/.config-db
2022-11-08T13:22:37.724Z CONFIG   version 10.3.0
2022-11-08T13:22:38.065Z DRIVER   beginning interview...
2022-11-08T13:22:38.066Z DRIVER   added request handler for AddNodeToNetwork (0x4a)...
1 registered
2022-11-08T13:22:38.066Z DRIVER   added request handler for RemoveNodeFromNetwork (0x4b)...
1 registered
2022-11-08T13:22:38.066Z DRIVER   added request handler for ReplaceFailedNode (0x63)...
1 registered
2022-11-08T13:22:38.066Z CNTRLR   querying controller IDs...
2022-11-08T13:22:38.068Z SERIAL » 0x01030020dc                                                         (5 bytes)
2022-11-08T13:22:38.068Z DRIVER » [REQ] [GetControllerId]
2022-11-08T13:22:38.368Z SERIAL « [DISCARDED] invalid data 0xc01cd8000c0005000253efa7b759fcc0         (16 bytes)

@AlCalzone any known bug?

No known issues. Unfortunately the UZB(1) is one of the sticks that cannot be automatically restarted. If it is hanging it needs to be done manually by re-plugging it.

Strangely enough, it works briefly on a reboot.
Why does the connection break? Do I then have to restart the container regularly?

Here is an other log entry from docker:
2022-11-08 14:32:18.140 INFO Z-WAVE: Client closed
2022-11-08 14:32:18.142 INFO Z-WAVE: Connecting to /dev/zwave
Logging to file:
/usr/src/app/store/logs/zwavejs_2022-11-08.log
2022-11-08 14:32:31.982 INFO Z-WAVE: Controller status: Driver: Failed to initialize the driver: ZWaveError: Timeout while waiting for a response from the controller (ZW0200)
at Driver.sendMessage (/usr/src/app/node_modules/zwave-js/src/lib/driver/Driver.ts:3990:23)
at ZWaveController.identify (/usr/src/app/node_modules/zwave-js/src/lib/controller/Controller.ts:713:33)
at Driver.initializeControllerAndNodes (/usr/src/app/node_modules/zwave-js/src/lib/driver/Driver.ts:1208:26)
at Immediate. (/usr/src/app/node_modules/zwave-js/src/lib/driver/Driver.ts:1015:16) (ZW0100)
2022-11-08 14:32:31.985 INFO Z-WAVE: Client closed
2022-11-08 14:32:31.987 INFO Z-WAVE: Connecting to /dev/zwave
Logging to file:
/usr/src/app/store/logs/zwavejs_2022-11-08.log
2022-11-08 14:32:36.574 INFO Z-WAVE: Controller status: Driver: Failed to initialize the driver: ZWaveError: Timeout while waiting for an ACK from the controller (ZW0200)
at Driver.sendMessage (/usr/src/app/node_modules/zwave-js/src/lib/driver/Driver.ts:3990:23)
at ZWaveController.identify (/usr/src/app/node_modules/zwave-js/src/lib/controller/Controller.ts:713:33)
at Driver.initializeControllerAndNodes (/usr/src/app/node_modules/zwave-js/src/lib/driver/Driver.ts:1208:26)
at Immediate. (/usr/src/app/node_modules/zwave-js/src/lib/driver/Driver.ts:1015:16) (ZW0100)
2022-11-08 14:32:36.576 INFO Z-WAVE: Client closed
2022-11-08 14:32:36.578 INFO Z-WAVE: Connecting to /dev/zwave

What can I do now? It used to work without any problems. Should I try to downgrade the version? Which version would be best?
Thanks

Please make a driver log of the startup until it breaks, loglevel debug and attach it here as a file (drag & drop into the text field).

Here are the logs....
zwave-js-ui-store.zip
Thanks!

2022-11-11T09:45:19.970Z DRIVER   Serial port errored: The serial port closed unexpectedly! (ZW0100)

Everything looks Ok, then this happens (stick disconnects) and no further communication with the stick is possible.
This is either something on the hardware side (power supply, loose contact,...) or a problem on the host system. In any case, this is not an issue in zwave-js and you'll probably need to look at system logs to figure out why that happens.

Error detected.
Without Docker it works. Probably there are problems in the Docker stack.

@AlCalzone Couldn't it be caused by soft reset?

No. Soft reset happens at startup (if not disabled/blacklisted), not in the middle of communication.


BUG: Dark theme not working

Description of  the bug
The dark theme button provided on the home page, when clicked is not working.
Expected behaviour
It should turn on the dark mode when the dark theme button is clicked.
Video (Mandatory)

https://github.com/apu52/Travel_Website/assets/117789470/f3f7c1d9-9edf-41a0-9157-880e4aee8f96
Are you contributing under any open-source program ?
JWOC 2024

Please assign me this issue under JWOC 2024!
Thanks!

@gitgoap I will assign you . But as you have already assigned to an issue . I will assign you after the completion of the previous PR

@apu52 Assign it to somebody else, I am currently not taking up any issue.

@apu52 i would like to contribute on this issue. Assign me under JWOC

This issue is in waiting. you can make a new issue on which you want to work on

@apu52 I have asked you first for this issue to contribute. so, now please assign it to me

@apu52 i would like to contribute on this issue. Assign me under JWOC

This issue is in waiting. you can make a new issue on which you want to work on

@apu52 I have asked you first for this issue to contribute. so, now please assign it to me

#112 this issue is already present

@apu52 i would like to contribute on this issue. Assign me under JWOC

This issue is in waiting. you can make a new issue on which you want to work on

@apu52 I have asked you first for this issue to contribute. so, now please assign it to me

#112 this issue is already present

Assign this issue to me


Show multiple kanji component forms

as shown on https://www.kanshudo.com/component_details/standard_radicals
also: radical search by text

Not applicable to the RADKFILE stuff if I understand correctly.


Fix bug with basepath reservation

Resolves a bug and introduces some refactoring.

Woo 👏  a PR on day one 🎉

One style comment, and the build has also failed on lint error. Otherwise :+1:

For future reference, here is the Git styleguide. In particular, on this branch you don't always use the present tense, and don't always wrap to 72 characters.

(I've only just realised that the styleguide includes Git, otherwise I would have pointed this out at the time)


Authorization issue when trying to publish

As discussed in Discourse. I'm able to publish the library to Hex e.g. https://hex.pm/packages/gleam_validator
But when I do:
gleam docs publish --version 0.2.0

I get
error: Hex API failure

There was a problem when using the Hex API.

This was error from the Hex client library:

    this account is not authorized for this action

Relevant code https://github.com/gleam-lang/hexpm-rust/blob/main/src/lib.rs#L477
Thanks

I found the issue looking at the rust code.
The api will give the 403 error if you try to publish a package that doesn't belong to you.
I was able to publish to hex because I had:
{application, gleam_validator, ...

In gleam_validator.app.src
But in gleam.toml I had just validator.
After changing this to gleam_validator too, the publishing worked.
This can be confusing. Maybe something could check that these names are the same.

Ah that explains it! I'm glad you found the cause of the problem.
The .app.src / gleam.toml split is confusing for sure. I'm hoping to remove the .app.src and have it generated (like mix does) so this won't be a problem then.
Maybe we could include the name of the package in the error- that could help.


Rancher server or agent freezes when rebooting

RancherOS Version: (ros os version)
version 1.0.3
Where are you running RancherOS? (docker-machine, AWS, GCE, baremetal, etc.)
VMWare vSphere
When try to reboot a Rancher server or agent the VM freezes. Sometimes it freezes before rebooting and see the message acpid: exiting nothing more and sometimes it reboots but can't do anything and still need to reboot the VM.

Pmease upgrade to 1.0.4. The shutdown rewrite was done specifically due to this issue.
What version of esxi are you using?
And what services and containers are you running?

How can we upgrade if the systems are behind a proxy?
As far as I know they run ESX 5.5.
System containers overview:
$ sudo system-docker ps -a
CONTAINER ID        IMAGE                               COMMAND                  CREATED             STATUS                     PORTS               NAMES
41af9171605a        rancher/os-console:v1.0.3           "/usr/bin/ros entrypo"   7 minutes ago       Up 7 minutes                                   console
e99a800a46f9        rancher/os-console:v1.0.3           "/usr/bin/ros entrypo"   8 minutes ago       Exited (0) 7 minutes ago                       shutdown
858758fc713f        rancher/os-docker:17.03.1           "ros user-docker"        24 hours ago        Up 6 minutes                                   docker
575abf85dfe9        rancher/os-zfs:v1.0.3               "/usr/bin/ros entrypo"   24 hours ago        Exited (0) 6 minutes ago                       zfs
b8b6c207116f        rancher/os-console:v1.0.3           "/usr/bin/ros entrypo"   24 hours ago        Exited (0) 24 hours ago                        reboot
61683d3f16dd        rancher/os-headers:4.9.34-rancher   "/headers.sh"            2 days ago          Exited (0) 7 minutes ago                       kernel-headers-system-docker
346753f96dde        rancher/os-openvmtools:latest       "/usr/bin/ros entrypo"   3 days ago          Up 7 minutes                                   open-vm-tools
2e3d1718c002        rancher/os-base:v1.0.3              "/usr/bin/ros entrypo"   8 days ago          Exited (0) 7 minutes ago                       preload-user-images
9929caff247d        rancher/os-base:v1.0.3              "/usr/bin/ros entrypo"   8 days ago          Exited (0) 7 minutes ago                       cloud-init-execute
211f2e621ba5        rancher/os-base:v1.0.3              "/usr/bin/ros entrypo"   8 days ago          Up 7 minutes                                   ntp
1cd1741a7dbd        rancher/os-base:v1.0.3              "/usr/bin/ros entrypo"   8 days ago          Up 7 minutes                                   network
96414a7f6b20        rancher/os-base:v1.0.3              "/usr/bin/ros entrypo"   8 days ago          Up 7 minutes                                   udev
5288afca0ec2        rancher/os-base:v1.0.3              "/usr/bin/ros entrypo"   8 days ago          Created                                        all-volumes
c786977c48e8        rancher/os-acpid:v1.0.3             "/usr/bin/ros entrypo"   8 days ago          Up 7 minutes                                   acpid
5dc7c1a48f2a        rancher/os-base:v1.0.3              "/usr/bin/ros entrypo"   8 days ago          Up 7 minutes                                   syslog
f740504fda99        rancher/os-base:v1.0.3              "/usr/bin/ros entrypo"   8 days ago          Exited (0) 7 minutes ago                       udev-cold
e4098b7cbc4c        rancher/os-base:v1.0.3              "/usr/bin/ros entrypo"   8 days ago          Created                                        user-volumes
200df809591b        rancher/os-base:v1.0.3              "/usr/bin/ros entrypo"   8 days ago          Created                                        command-volumes
bd74bd890640        rancher/os-base:v1.0.3              "/usr/bin/ros entrypo"   8 days ago          Created                                        media-volumes
cc3cdd0f4794        rancher/os-base:v1.0.3              "/usr/bin/ros entrypo"   8 days ago          Created                                        system-volumes
48b0d907026c        rancher/os-base:v1.0.3              "/usr/bin/ros entrypo"   8 days ago          Created                                        container-data-volumes

Within Docker (not system-docker) we don't have any containers running at the moment.

ah - that bug - its on my list of fixes for 1.0.5.
you should be able to run ros os upgrade -i anyimagename  - and the upgrade images are on Docker hub as rancher/os:v1.0.4 - if your system-docker has the proxy set, then you should be able to system-docker pull rancher/os:v1.0.4 first, and if not, are you using a local registry? or docker load&save?

We are deploying Rancher first in DTA, unfortunately we don't have yet a local registry in place.


add timeout option

From #63

you don't want to wait for the images to load for over than 10 sec.

Implementing timeout is a good idea. Adding to to-do list.

+1 this issue if you would like to see this feature added to imagesLoaded.

I'm also looking for a way to abort/cancel/destroy the image loading like @ahoward suggests.

:+1:

:+1:

updates on this issue? this is very important from a UX perspective


missing input files generate a panic

Hi,
If /tmp/tst is missing (I had created /tmp/test by mistake, following your README), I get a panic.  The panic message explains the error, but then it is followed by a long
backtrace (truncated below).
./microfts input -file /tmp/bubba /tmp/tst
panic: Error: stat /tmp/tst: no such file or directory, args: [/tmp/bubba /tmp/tst]

goroutine 1 [running]:
main.check(0x59fe60, 0xc00007a720)
        /home/bill/work/microfts/fulltext.go:205 +0x150
main.(*lmdbConfigStruct).openInputFile(0x686980, 0x7fff9d4de550, 0x8, 0xc00013baa0, 0x4e740c, 0x7f9cec003ffb, 0x4)
        /home/bill/work/microfts/fts-lmdb.go:535 +0x79
main.(*lmdbConfigStruct).indexLines(0x686980, 0x7fff9d4de550, 0x8)
        /home/bill/work/microfts/fts-lmdb.go:579 +0x5d
main.(*lmdbConfigStruct).index(0x686980, 0x7fff9d4de550, 0x8)
        /home/bill/work/microfts/fts-lmdb.go:529 +0x6f
main.cmdInput.func1()

Makes sense.  The important thing is that is returns a non-zero result (which it does) but I could have in a friendlier error message...


FindFiles and ListFiles might want to trim newlines from the path

Hi @bitfield , thanks for this awesome package. I just ran into an issue that is surely an easy thing to improve.
Issue: the output of Pipe.String() may include a newline. FindFiles and ListFiles cannot find a path that ends in a newline. Hence these two methods cannot consume the output of Pipe.String() without prior removal of newlines.
Suggestion: Have FindFiles and ListFiles trim trailing newlines from the input path.
Example:
package main

import (
	"log"
	"github.com/bitfield/script"
)

func main() {
	r, _ := script.Args().String()
	log.Printf("args: [%s]\n", r)
	p := script.ListFiles(r)
	_, err := p.Stdout()
	log.Println(err)
}

Call:
go run main.go .

Output:
2020/09/08 13:57:58 args: [.
]
2020/09/08 13:57:58 stat .
: no such file or directory

Severity: minor annoyance but can cost time to track down.

Hi @christophberger, nice suggestion, thank you! It seems like there are actually a bunch of pipe sources which could struggle with a newline-terminated string. Maybe another solution is to provide a way to trim the trailing newline from the pipe's output? Ruby and Perl call this chomp(), I think. We could do the same. Ideas welcome!

I think you can best decide which approach fits best into the pipe design. My own bias would be towards automatic stripping of newlines from path strings. After all, a file path never contains newlines.
The reason for this bias is that I needed a while to figure out why FindFiles or ListFiles did not seem to work the way they should. Only after adding all the missing error handling and logging, I discovered the trailing newline as the reason for the malfunction. (Yeah, PEBCAK definitely. Lesson learned: Never neglect proper error handling, even for simple throw-away scripts.) If the newlines are stripped automatically, user errors like this one cannot happen anymore.

Lesson learned: Never neglect proper error handling, even for simple throw-away scripts

As a Go teacher, I naturally agree with this 😁

My own bias would be towards automatic stripping of newlines from path strings. After all, a file path never contains newlines.

That is a very good point, so any method which accepts file paths could trim them automatically.
Are you interested in working on this? If not, no problem, but if you are, we could work together on a PR for the fix.

Hi John,
No problem, I have created a PR https://github.com/bitfield/script/pull/63 just now. Let me know what you think.
Best,
Christoph

On 9. Sep 2020, at 18:51, John Arundel<EMAIL_ADDRESS>wrote:
Lesson learned: Never neglect proper error handling, even for simple throw-away scripts
As a Go teacher, I naturally agree with this 😁
My own bias would be towards automatic stripping of newlines from path strings. After all, a file path never contains newlines.
That is a very good point, so any method which accepts file paths could trim them automatically.
Are you interested in working on this? If not, no problem, but if you are, we could work together on a PR for the fix.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/bitfield/script/issues/62#issuecomment-689687135, or unsubscribe https://github.com/notifications/unsubscribe-auth/AA5IP4SS57HOJLLXC545OH3SE6W7NANCNFSM4Q74OTCA.


Run tests for this monorepo with test-runner

Have a fairly basic PR out for running tests for the subprojects with a bash script, but ideally we should use test-runner to test the repo itself :)

100%, Chalk and Rely (formerly test-runner) currently use it

Thanks @davesnx !!


UNET package for HoloLens collboration compatible with HoloToolkit 20…

2<IP_ADDRESS>
Overview
Sharing with HoloLens through UNET which has been shown in the tutorial MR Sharing 250 works fine if you simply follow the tutorial by downloading the files but if you try to use that same files in your new project with HoloToolkit of version 2<IP_ADDRESS> it will not work and will throw lots of warnings and errors.  So I made changes in the scripts as per the new methods in the latest version to make it compatible with the latest version.
So this package contains the HoloToolkit 2<IP_ADDRESS> and UNET sharing package for sharing coordinates of Hologram to get an idea of sharing in HoloLens.
Changes

Fixes:  #2365 (Maybe solving other issues also I'm not sure!)

Unity Version -  2017.4.17f1 (LTS)
Visual Studio Community 2017

@virendrasuryavanshi, you mention in the title that this PR is for HoloToolkit 2017. however, the source base you used for it is Mixed Reality Toolkit v2 (mrtk_release). Please recreate this using the htk_development branch.
Thanks and sorry for the mixup with my retargeting.

Do not know how I inadvertently closed this PR (and why GitHub wont let me reopen it).


fuzzers: don't use EXCLUDE_PLACEMENT on ROI

Fixes: https://github.com/SymbiFlow/prjxray/issues/212
A recent change got the ROI X/Y out of sync with the ROI primitives. This caused issues for many fuzzers which used EXCLUDE_PLACEMENT to create a sharp boundary between the ROI and the rest of the FPGA. This is problematic because the site ROI was expanded to include most of the chip, and this precluded placing harness test logic in the top module.
Really, we need to separate out the ROI that we are using for tilegrid generation vs fuzzers. Or, if the idea is to no longer use an ROI for tilegrid, we should just remove the ROI entirely from that fuzzer

FYI roi_harness still has this set, since it may be more critical for that


Update code blocks card

Build status - All builds passed
https://github.com/OfficeDev/Microsoft-Teams-Samples/actions/runs/8659114381


refactor: change computedMatch to match

!important: this is a breaking change.
Possible effects: any library or tests directly relied on computedMatch would fail.
rationale behind this pr: eliminate unknown prop warning in react development env.
ref: https://reactjs.org/warnings/unknown-prop.html

Heads up: You're using an outdated version of npm. Make sure you upgrade to something newer (npm install -g npm).
Something else is likely at play here. There isn't a match attribute on any DOM element as far as I know. That error only affects DOM element props and we're not dealing with any of those in this code. Check your implementation. You are likely blindly passing in props from a Route somewhere.

@timdorr Thanks, I understand the true cause of the problem now.
For people who come into the same issue as unknown prop warning of react, here is the code:

TLDR:  https://reacttraining.com/react-router/web/api/Switch/children-node
**All children of a  should be  or  elements. **

before(with warning):
    <Router>
      <Switch>
        <Route path="/" render={() => {
          return (

              {/* mock component/Header */}

Header

                {/* mock component/Menu */}

Menu

                  <Switch>

some content

                  </Switch>

          )
        }} />
      </Switch>
    </Router>

after(correct usage of Switch and no warning):
    <Router>
      <Switch>
        <Route path="/" render={() => {
          return (

              {/* mock component/Header */}

Header

                {/* mock component/Menu */}

Menu

                  <Switch>
                    <Route path="/app" render={() => {
                      return (

some content

                      )
                    }}
                  />
                  </Switch>

          )
        }} />
      </Switch>
    </Router>


Browser compability detection

Dear Tarek,
First of all a big thanks for this great package!
Is your feature request related to a problem? Please describe.
I just had a user (with an old browser though...) complaining that my site is not working. :cry:
Thoroughly Describe the solution you'd like
I would like to use a feature detection.
Please Describe alternatives you've considered
One option would be to test for ES6, right? Haven't really thought it through, but this could be an option: https://gist.github.com/bendc/d7f3dbc83d0f65ca0433caf90378cd95
But as you know your code best, you probably have even better ideas for what would be an appropriate test?

Hello @bbo2adwuff,
I'm glad that it came in handy for you. :)
Sorry to hear that.
I would assume that that user was using IE11 or below because that is the only browser that's not supported.
Yet, you could use an easy online ES6 transpiler like Babeljs.io's REPL or ES6 Console to solve the browser's backward compatibility issue. Still, you have to know what's broken for that user to be able to fix it while tuning the transpiler's settings.
Try giving it a shot and let me know how it went, I would always be glad to support you.
Cheers! :)


Preserve content across retries during edit

Fixes #1593
RELEASE_NOTES=[UX] Preserve content across retries
Signed-off-by: Dominik Schulz<EMAIL_ADDRESS>

Codecov Report

Merging #1608 into master will increase coverage by 0.04%.
The diff coverage is 63.64%.

@@            Coverage Diff             @@
##           master    #1608      +/-   ##
==========================================
+ Coverage   57.67%   57.72%   +0.04%
==========================================
  Files         204      204
  Lines        9821     9843      +22
==========================================
+ Hits         5664     5681      +17
- Misses       3490     3493       +3
- Partials      667      669       +2

Impacted Files
Coverage Δ

internal/action/edit.go
50.00% <63.64%> (+1.85%)
:arrow_up:

internal/secrets/plain.go
86.84% <0.00%> (-4.82%)
:arrow_down:

pkg/gopass/secret/mime.go
49.33% <0.00%> (-1.37%)
:arrow_down:

internal/cui/cui.go
13.33% <0.00%> (-0.95%)
:arrow_down:

internal/action/env.go
60.61% <0.00%> (ø)

internal/action/find.go
59.68% <0.00%> (ø)

internal/action/fsck.go
59.09% <0.00%> (ø)

internal/action/grep.go
64.00% <0.00%> (ø)

internal/action/repl.go
0.00% <0.00%> (ø)

internal/action/sync.go
45.35% <0.00%> (ø)

... and 8 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 4b6cd88...b0bbd4f. Read the comment docs.


Add support for cloud functions in zip file

It's necessary to look inside zip file to determine the language of cloud functions.

Partially implemented, it currently works for Python functions inside zip file. It's theoretically prepared also for other languages, but it's not enabled because tests are not written yet.


fix: remove fields empty check

Which issue does this PR close?
Closes #
Rationale for this change
Sometime there is no fields in a table,  error occurs when data writing :
java.lang.IllegalArgumentException: Empty.fields
        at io.shaded.ceresdb.common.util.Requires.requireTrue(Requires.java:72)
        at io.shaded.ceresdb.models.Point$PointBuilder.check(Point.java:84)
        at io.shaded.ceresdb.models.Point$PointBuilder.build(Point.java:78)

What changes are included in this PR?
Remove  fields empty check.
Are there any user-facing changes?

How does this change test

 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.MachaelLee 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.

 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.MachaelLee 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.


SQLITE_DETERMINISTIC not defined in iOS 8.1 SDK

SQLITE_DETERMINISTIC is not defined in sqlite3.h from iOS SDK 8.1, causing a build failure on Xcode 6.1.1 in SQLite-Bridging.c (61).

Thanks for the report! I've been running tests on the Mac framework (which has a newer version of SQLite) and when I've tested iOS it's been Xcode 6.3 (same story). Let me add an #ifdef for iOS 8.1.

Fixed by https://github.com/stephencelis/SQLite.swift/commit/6355b6d367244ca3d3bd25581536163a9ee78d5e


[Bug] handle reverted eth_calls on declared eth_calls

Bug report
Declared eth_calls executes before eth_calls on handlers triggered. But when declared eth_calls get reverted, subgraph get stuck in syncing.
Repo that can reproduce this error - Link
Deployment ID: QmfH5xCioLUqd1zM2b2QGE6Br5uZdks2tx2A1NPB1dZQSK
Subgraph that sync when declared eth_call is removed
Deployment ID: QmaWD3fz3Y6PZdEmZ9QQ79fkVwTzh49JBqLcbzG85wDMrr
Relevant log output
Error: Ethereum node returned an error for an eth_call: RPC error: Error { code: ServerError(-32015), message: "VM execution error.", data: Some(String("Reverted ERC721URIStorage: URI query for nonexistent token")) }

IPFS hash
QmfH5xCioLUqd1zM2b2QGE6Br5uZdks2tx2A1NPB1dZQSK
Subgraph name or link to explorer
No response
Some information to help us out

[ ] Tick this box if this bug is caused by a regression found in the latest release.
[ ] Tick this box if this bug is specific to the hosted service.
[X] I have searched the issue tracker to make sure this issue is not a duplicate.

OS information
None

@Shiyasmohd can i close it? this is non-issue now right?

Yes. Closing this issue.