Recording - Group Channel/ iOS - Mention other members in message

MentionUsersInMessageGroupChannel
Click ‘Create’ to create new group channel
Under ‘Choose member’, add users & select ‘OK’
Click on ‘Channel Name’ box to input channel name
Name channel ‘Puppy playdate’
Click ‘Create’
Click ‘Puppy playdate’ to enter conversation

Joyce: Are we still meeting at the park later?

Click the text box and type ‘Daniel, if you’re coming please bring the ball!’
Click the send button
Under ‘Choose Member’, click the user you want to mention: ‘Daniel’ & click ‘OK’

Ready

@justinbaldwin review with Olivia.
@petru-gherghel Olivia and I are going to meet about speeding up only certain segments of the video. Will report back.

@michellewong27 @chrischabot
Ready for review: https://drive.google.com/file/d/16RkC74XEIDnC-iK_WkmgQ70uAP1QfTR-/view?usp=sharing

@justinbaldwin please speed up the text entry

@justinbaldwin
https://drive.google.com/file/d/1ar7Mea0lqQ-8dbbw9Sy3ZJkide30gVCf/view?usp=sharing

@justinbaldwin reviewed, good for publishing


OKTAT3-4: Migrate to Okta

Go ahead and merge the okta branch into staging and push up staging, then do the same for the front-end after this finishes deploying. Then we can test in staging.


404 errors on parse errors

When a profile, group, ignition, etc is malformed a 404 error is logged. this is really annoying. Looks like you miss-configured something with the profiles  but at the end, the most usual common is that you have a extra colon.
The message and the code is not helpful at all. I will be happy to do a PR changing this 404 error with a 500 error and a more verbose error message.

This is also true when you have a missing template parameter, but the definitions themselves are valid syntax-wise. I'm not sure if that case warrants an issue of its own.

Check the server logs to find the error in the /var/lib/matchbox configs. I'm open to using a different message. There was concern that bubbling up any errors might be surprising or reveal data in an unexpected way, but I think most of those concerns are moot.

Depending of the log level the errors are confusing, since it says profile not match. Is really confusing and and bad use of HTTP errors.

@dghubble  and @mcuadros
Additionally, when looking at the logs on the provisioner within a Tectonic install... The logs are misleading stating incorrectly the line number:
ovisioner.coreos systemd-machined[875]: New machine rkt-561f8ea9-c87b-4851-92d3-3a32e0116a05.
Mar 27 13:04:47 genesis.provisioner.coreos rkt[1844]: [ 1321.987178] matchbox[5]: time="2017-03-27T13:04:47Z" level=info msg="Starting matchbox gRPC server on <IP_ADDRESS>:8081"
Mar 27 13:04:47 genesis.provisioner.coreos rkt[1844]: [ 1321.989530] matchbox[5]: time="2017-03-27T13:04:47Z" level=info msg="Using TLS server certificate: /etc/matchbox/server.crt"
Mar 27 13:04:47 genesis.provisioner.coreos rkt[1844]: [ 1321.990323] matchbox[5]: time="2017-03-27T13:04:47Z" level=info msg="Using TLS server key: /etc/matchbox/server.key"
Mar 27 13:04:47 genesis.provisioner.coreos rkt[1844]: [ 1321.991069] matchbox[5]: time="2017-03-27T13:04:47Z" level=info msg="Using CA certificate: /etc/matchbox/ca.crt to authenticate client certificates"
Mar 27 13:04:47 genesis.provisioner.coreos rkt[1844]: [ 1321.992761] matchbox[5]: time="2017-03-27T13:04:47Z" level=info msg="Starting matchbox HTTP server on <IP_ADDRESS>:8080"
Mar 27 13:04:50 genesis.provisioner.coreos rkt[1844]: [ 1325.596082] matchbox[5]: time="2017-03-27T13:04:50Z" level=info msg="HTTP GET /ignition?uuid=ebca75f8-fbf4-40f5-8344-754bfedd38eb&mac=56-00-00-5f-51-d7&os=installed"
Mar 27 13:04:50 genesis.provisioner.coreos rkt[1844]: [ 1325.607601] matchbox[5]: time="2017-03-27T13:04:50Z" level=debug msg="Matched an Ignition or Fuze template" group=tectonic-node-56-00-00-5f-51-d7 labels=map[uuid:ebca75f8-fbf4-40f5-8344-754bfedd38eb mac:56:00:00:5f:51:d7 os:installed] profile=tectonic-controller
Mar 27 13:04:50 genesis.provisioner.coreos rkt[1844]: [ 1325.614189] matchbox[5]: time="2017-03-27T13:04:50Z" level=error msg="error parsing Fuze config: error: yaml: line 298: could not find expected ':'"
Mar 27 13:05:50 genesis.provisioner.coreos systemd[1]: Started OpenSSH per-connection server daemon (<IP_ADDRESS>:53539).
Mar 27 13:05:50 genesis.provisioner.coreos sshd[1930]: Accepted publickey for core from <IP_ADDRESS> port 53539 ssh2: RSA SHA256:SGpftLWBgWtXPdApxW2T6vTTjsRaCpyPcvNE5H3FPro
Mar 27 13:05:51 genesis.provisioner.coreos sshd[1930]: Received disconnect from <IP_ADDRESS> port 53539:11: disconnected by user
Mar 27 13:05:51 genesis.provisioner.coreos sshd[1930]: Disconnected from <IP_ADDRESS> port 53539

In this case the line no. was much further down.


A page on benchmarking, perhaps under Standard Library

Benchmarking is mostly documented in the README of std/testing but it would be good to have a manual page on this
I'm willing to PR this, just opening for tracking purposes

Benchmarking documentation currently available here: https://docs.deno.com/runtime/manual/tools/benchmarker


1463 remove beanutils

Made the changes you requested. I'm not sure what spam you were getting previously, but I did the following and did not get any results:
mvn clean verify -Psunny
find */target/surefire-reports -name *.txt -exec grep -H beanutils {} \;
find */target/failsafe-reports -name *.txt -exec grep -H beanutils {} \;

Just realized I looked at the wrong files. Ran the following and didn't get any matches either:
find */target/surefire-reports -name *-output.txt -exec grep -H beanutils {} \;
find */target/failsafe-reports -name *-output.txt -exec grep -H beanutils {} \;

Just realized I looked at the wrong files. Ran the following and didn't get any matches either:
find */target/surefire-reports -name *-output.txt -exec grep -H beanutils {} \;
find */target/failsafe-reports -name *-output.txt -exec grep -H beanutils {} \;

The spam was in the log4j logs when starting up. They may show up in Mini logs, or maybe via Uno. You can see what I mean by removing the logging config changes without your other changes.

To be clear, you are saying that the spam is showing up in the master or tserver logs when starting Accumulo, and the entries in  test/src/main/resources/log4j2-test.properties suppress that? There are no logger settings in the conf directory for beanutils.

To be clear, you are saying that the spam is showing up in the master or tserver logs when starting Accumulo, and the entries in  test/src/main/resources/log4j2-test.properties suppress that? There are no logger settings in the conf directory for beanutils.

If you do this on the main branch:
--- a/test/src/main/resources/log4j2-test.properties
+++ b/test/src/main/resources/log4j2-test.properties
@@ -121,3 +120,0 @@ logger.29.level = info
-logger.30.name = org.apache.commons.beanutils.converters
-logger.30.level = info
-

Then, do mvn clean verify -Dtest=blah -Psunny -Dspotbugs.skip -Dcheckstyle.skip
Then, do grep converters test/target/mini-tests/org.apache.accumulo.test.functional.ReadWriteIT_interleaved/logs/*
You will see them. You probably aren't seeing it because you're looking for beanutil, but our log4j configuration is set to only show the last two elements of the logger name, so the part with beanutil gets truncated.

I ran the commands you gave me on the main branch (after removing the lines in the log4j properties file) and I saw the log statements you were talking about. Then I switched over to this branch and ran the same commands, nothing.

@dlmarion This change seems to have caused a regression. VolumeIT is failing, seemingly due to something related to SetGoalState. I am not sure exactly what is broken, but it could be the use of FileReader for arguments passed in as URLs. Some test files may be stored in jars, and my suspicion is that you cannot do url.toFile() for these. I'm also seeing errors reading Metrics configuration files, likely due to the same reason, because the config properties are probably contained in a jar, and we need to have a Reader that uses the URL directly, rather than call toFile(). This is only a theory at this point.

@dlmarion This change seems to have caused a regression. VolumeIT is failing, seemingly due to something related to SetGoalState. I am not sure exactly what is broken, but it could be the use of FileReader for arguments passed in as URLs. Some test files may be stored in jars, and my suspicion is that you cannot do url.toFile() for these. I'm also seeing errors reading Metrics configuration files, likely due to the same reason, because the config properties are probably contained in a jar, and we need to have a Reader that uses the URL directly, rather than call toFile(). This is only a theory at this point.

I believe I have fixed it in #1795

Looks good. Thanks for the assist.


Add Japanese translation for v3.1.0-beta.0

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

Proposed changes
Added additional translations for dev branch.
Checklist

[x] I have read the contribution guidelines
[ ] For non-bugfix PRs, I have discussed this change on the forum/slack team.
[x] I have run grunt to verify the unit tests pass
[ ] I have added suitable unit tests to cover the new/changed functionality

Coverage: 68.198%. Remained the same when pulling a661bc1d237987850d3398b1a5739933cd022cfe on kazuhitoyokoi:dev-jpn into 270eb5671839d7bbf2f540143e4d7e0ee66b46e2 on node-red:dev.

Thank you.


Bug 1746811: Make packagemanifest list return all valid packages

Fixes an issue where invalid packages (e.g. missing a bundle) prevents successive packagemanifests from being returned on list.

/retest

/retest

/cherry-pick release-4.1


Add Row field selector

Other databases have options of skip and limit to help with pagination.  I'm thinking I'll handle this by adding a Row field selector similar to how you can compare against the Key with bolthold.Key()
So a query may look like this:
bolthold.Where(bolthold.Row()).Ge(0).And(bolthold.Row()).Lt(100))

It allows you to skip and limit.

While I think bolthold.Row() makes for a better cleaner interface, keeping track of the current row for each index entry along with tracking the row past Seek calls would be impossible, and would mean that implementing Row() correctly would hurt performance.  Not worth it.  I'll just implement Skip() and Limit() instead.


Provide a choice to replace revision counter

The record of revision counter results in one additional direct_io writes to the disk, which caused the performance penalty, especially this feature is more for data validation purpose.
We will see if we can replace the revision counter using some existing mechanism.

The basic design:

The engine will ask replica for the FIEMAP of the volume head and compare them. They should be the same.
If not all replicas report the same FIEMAP, check the timestamp for the last access time of volume head (precision is nanoseconds). Accept the latest one and the ones with the same FIEMAP as it.
2.1. This will require servers to have NTP servers running.
2.2. One enhancement is Longhorn manager should warn about time disparity on the different nodes.

On top of this, the user can still manually choose which replicas to be taken into consideration when salvage the volume from faulted state.

Created UI issue at https://github.com/longhorn/longhorn/issues/1839

@khushboo-rancher , can you use this UI image wangsiye/longhorn-ui:71f804a to test this feature? Since I just filed a UI issue for this feature, and it's a long holiday in China now, @smallteeths probably can't work on this UI changes very soon, and we can unblock our side with this UI image. Please let me know if you have any concern. Thanks.

Filed engine integration test at #1840

Validation: WIP
Steps to test:

Diable Revision Counter Setting should be disabled by default.  (PASS)
Disable Revision Counter property can be set per volume at creation time.

General Steps:

Disable scheduling on Node2, and Node3
Set Replica Node Level Soft Anti-Affinity to True
Create a volume with 2 replicas, all replicas should scheduled to Node1
Attach a volume to a node, mount it to a directory
Identify and exec to instance-manager-r-xxx pod scheduled to Node1
Identify volume replicas names and PIDs.

Replica Name
Replica PID

Replica 1
PID1

Replica 2
PID2

Using the following line, write data to the volume to data.txt file
$ for x in {1..1000000}; do echo $x >> <PATH_TO_VOLUME_MNT_DIR>/data.txt ; sleep 0.01; sync; echo $x ;done

Test case (1): Automatic salvage: True, Disable Revision Counter:  False
Test case (2): Automatic salvage: True, Disable Revision Counter:  True
Test case (3): Automatic salvage: False, Disable Revision Counter:  False
Test case (4): Automatic salvage: False, Disable Revision Counter:  True

Validation(2/2): PASS
Steps to test(1):

Install Longhorn v1.0.2
Create a volume used by some workload
Upgrade Longhorn  master,
Verify Disable Revision Counter property doesn't exist for volume before upgrading Longhorn engine image
Upgrade Longhorn engine image.
Volumes should have Disable Revision Counter set to False.  (PASS)
Verify global Disable Revision Counter is set to False by default.

Steps to test(2):

Create a new StogrageClass using:

    kind: StorageClass
    apiVersion: storage.k8s.io/v1
    metadata:
      name: no-rev-count-longhorn
    provisioner: driver.longhorn.io
    allowVolumeExpansion: true
    parameters:
      numberOfReplicas: "2"
      disableRevisionCounter: "true"
      staleReplicaTimeout: "2880" # 48 hours in minutes
      fromBackup: ""

Create a PVC using

apiVersion: v1
kind: PersistentVolumeClaim
metadata:
  name: longhorn-simple-pvc
spec:
  accessModes:
    - ReadWriteOnce
  storageClassName: no-rev-count-longhorn
  resources:
    requests:
      storage: 1Gi

Create a workload to consume the created PVC
Check created volume replicas,  revision.counter file should NOT exist.

UI changes has been Merged https://github.com/longhorn/longhorn/issues/1839

Validation: PASSED

/reopen
Missing integration test changes: https://github.com/longhorn/longhorn-tests/pull/418/files


Alpn support

By adding ALPN support, s2n clients will be able to negotiate SPDY and HTTP/2 protocols with supporting servers.

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@81357c2). Click here to learn what that means.
The diff coverage is n/a.


While upgrading remove dangling entries in service when a service pool was removed in 3.0.2

While upgrading remove dangling entries in service when a service pool was removed in 3.0.2

Thanks @raju-saravanan  for the patch. Merged #1195 to master.


Cannot write delta table from pandas DataFrame with Timestamp column

Environment
Delta-rs version: 0.5.8
Binding:  Python
Environment:

OS: OSX
Other: Arrow 8.0.0

Bug
What happened: The python delta lake writer cannot handle pandas DataFrames with Timestamp columns natively because of the nanosecond precision:
from deltalake.writer import write_deltalake

df = pd.DataFrame({"timestamp": [pd.Timestamp('2022-01-01')]})
write_deltalake("test_with_timestamp", df)

yields the following traceback:
---------------------------------------------------------------------------
ArrowException                            Traceback (most recent call last)
Input In [403], in <module>
      1 from deltalake.writer import write_deltalake
      3 df = pd.DataFrame({"timestamp": [pd.Timestamp('2022-01-01')]})
----> 4 write_deltalake('test_with_timestamp', df)

File ~/Library/Caches/pypoetry/virtualenvs/test-GfuZs_x0-py3.8/lib/python3.8/site-packages/deltalake/writer.py:226, in write_deltalake(table_or_uri, data, schema, partition_by, filesystem, mode, file_options, max_open_files, max_rows_per_file, min_rows_per_group, max_rows_per_group, name, description, configuration, overwrite_schema)
    208 ds.write_dataset(
    209     data,
    210     base_dir=table_uri,
   (...)
    222     max_rows_per_group=max_rows_per_group,
    223 )
    225 if table is None:
--> 226     _write_new_deltalake(  # type: ignore[call-arg]
    227         table_uri,
    228         schema,
    229         add_actions,
    230         mode,
    231         partition_by or [],
    232         name,
    233         description,
    234         configuration,
    235     )
    236 else:
    237     table._table.create_write_transaction(
    238         add_actions,
    239         mode,
    240         partition_by or [],
    241         schema,
    242     )

ArrowException: Schema error: Invalid data type for Delta Lake: Timestamp(Nanosecond, None)

The same issue happens if I do write_deltalake("test_with_timestamp", pyarrow.Table.from_pandas(df))
What you expected to happen:
I would have expected this to work out of the box with pandas, without having a priori knowledge of which columns contain timestamps and having to create a new arrow table with downcasted values. Note that the call to pyarrow.dataset.write_dataset() is not the issue.

I would have expected this to work out of the box with pandas, without having a priori knowledge of which columns contain timestamps and having to create a new arrow table with downcasted values.

That's a good point. Delta Lake has a limited set of types that it supports. We don't do any automatic casting now, but perhaps we should create a mapping so that most Pandas and Arrow types can be automatically converted for writes.

FYI it's microsecond precision that is the only timestamp precision that is supported by Delta Lake.

@erinov1 Thanks for reporting. I've created a new feature request out of this, and we'll track progress there. https://github.com/delta-io/delta-rs/issues/686

Thanks! Out of curiosity, does Delta Lake support per-column timezones (like a pandas DataFrame or arrow Table)?

It does not support types with stored timezones, but that's at the row-level. https://github.com/delta-io/delta/blob/master/PROTOCOL.md#primitive-types
For per-column, that's not specified in the protocol, but it might just be undocumented. Theoretically, timezone info could be stored in the column metadata, so it's technically feasible. Just a question of what is recognized by other readers. I'll look into this.

I am facing the same issue


[6.1 🍒] Ignore in-package transitive dependencies when building from non-package textual interface

Cherry-pick of https://github.com/swiftlang/swift/pull/77686
This change ensures that when loading some module dependency 'Bar' which has a package-only dependency on 'Foo', only the following clients attempt to resolve/load 'Foo':

Source compilation with package-name equal to that of 'Bar'.
Textual interface compilation of a 'package' interface with package-name equal to that of 'Bar'.

Ensuring that the following kinds of clients do not attempt to resolve/load 'Foo':

Source compilation with package-name different to that of 'Bar'
Textual interface compilation of a public or private interface, regardless of package name.

This fixes the behavior where previously compilation of a Swift textual interface dependency 'X' from its public or private interface, with an interface-specified package-name, from a client without a matching package-name, resulted in a lookup of package-only dependencies of modules loaded into 'X'. This behavior is invalid if we are not building from the package textual interface, becuase the module dependency graph is defined by the package name of the source client, not individual module dependency package name. i.e. In-package module dependencies are resolved/loaded only if the parent source compile matches the package name.
Resolves rdar://139979180

@swift-ci test

@swift-ci test


Session management

This pull request fixes an issue that would cause the client to not clear an expired session.

Coverage increased (+0.2%) to 100.0% when pulling 9fca13f1e6f955bb5a6ba6442555a6a070b99433 on session-management into b637c2ff218f0e8648881cd72c37dd81e876c4e1 on master.


Disable forms and buttons

Would it be out of scope to disable input buttons or forms within an element containing ngBusy? This would help prevent multiple form submissions while the observables or promises are being processed.

Hi radyz,
Thank you for your suggestion. In my opinion, it is not quite proper for a loading plugin to modify the element's attributes. It only has rights to add the indicator thing into the element.
In order to achieve your aim, you could set a variable binding to the 'disable' attribute of the button, then disable it before a form submission, and enable it in the submission's resolve. This is an appreciate method.


Add a Flax guided tour

We want to add a guided tour of Flax, walking users through a real world workflow:

[x] JAX basics
[x] Core module abstraction
[x] Storing and inspecting data
[x] Different types of parameters
[ ] More complicated layers like transformers
[ ] Model and performance inspection
[x] Creating your own layers

For reference : the current guided tour has the following structure (in a single notebook):

JAX intro : mostly links to JAX documentation and tutorials
NN in JAX without Flax : init/apply in two separate functions
Flax modules : starting with an example of Dense and then going into more details:

composition
parameter sharing
shape inference
Model
state

Optimizer : plots of sampled 2d dots, then approximating with linear regression, and then with momentum optimizer
Serialization : converting objects to dictionaries of arrays, serializing with messagepack
Advanced features

MultiOptimizer
Multiple methods
Transforming sub module parameters.

I'm closing this issue since I think the guided tour is actually in a great state. For the two remaining points:

Model inspection:  see the Model surgery HOWTO
More complicated layers: I am not sure if this is necessary for the guided tour. We can add those as HOWTOs if necessary, but right now I don't see a real need, I guess if someone would like to understand a Transformer they can read one of the many great "Annotated Transformer" tutorials.


ci: downgrading coverage to debug

ci showed a failure in Protocols/DownstreamProtocolIntegrationTest.ManyRequestHeadersTimeout/IPv4_Http2Downstream_HttpUpstream
(https://dev.azure.com/cncf/4684fb3d-0389-4e0b-8251-221942316e06/_apis/build/builds/44319/logs/73)
which involved nghttp2 dumping 340024 lines of logs at trace level.  None of these log at debug.
downgrading coverage build to debug to reduce logspam and hopefully resolve the timeout.
Risk Level: low
Testing: checking CI
Docs Changes: n/a
Release Notes: n/a

Let's see how CI came out, but I doubt it contribute to timeout a lot. In coverage setup the bazel sandbox base is on top on tmpfs (which is memory), and then bazel print the log file to terminal at the end (this part is not calculated in timeout).

Even not logging to disk that's an extra 300,000 string copies many times over over, because we vsnprintf to a temporary buffer then fmt::append to logs, before actually logging which even if it's logging to file-in-memory has to allocate and copy again.

Yeah, I meant comparing to the previous one (logging to /dev/null), which still does all vsnprintf/buffer/append

Ah, that's a fair point, though one of the failure modes we were trying to debug was unexpected timeouts
I think that wasn't the biggest one Matt was after / worst culprit though :-P

de-drafting -  if it passes the coverage level checks it's ready to merge.

Huh, that's a lot of bits of failed coverage.
That said it does look like the test that timed out ran significantly faster (only comparing to 2 runs, could just be luck of the draw)
I'll check out tomorrow to see if I can find another way of silencing the spammy logs or otherwise debugging that flake iff flakes continue.

It drops 60-ish lines of coverage so I guess it's ok? some extensions definitely loses though.

yeah, but it's below the bar for a bunch, and I don't want to tweak tests in a bunch of extensions or lower.  Have another potential fix out - looks like this particular test is known to be slow so I'm just upping the timeout for coverage since it is doing a lot of (instrumented) work.


Fix. Tests and MoF improved accessibility

Overview of changes
With this PR, we have got two major objectives accomplished:

the tests are passing again
the MoF response from occurrences.search() function now returns as a list of pandas dataframes.

Notes for reviewers
I'm sorry for this huge PR, but the initial work like getting all modules to work, writing and making all tests work was I guess the first priority before accomplishing the primary objectives for this summer.
Next Steps
I am now working on dropping the obisDownloads, and on update-specific branches.

The edits look good overall, but there is a lot here.
@ayushanand18 : can you resolve the merge conflicts noted below?

Thanks a ton @7yl4r, I am working on resolving the merge conflicts.

@ayushanand18 : can you resolve the merge conflicts noted below?

I have removed changes to those files. Maybe, we need one more PR get those changes back after this PR gets merged.
The changes which I had to revert include,

removing the obsolete functions from taxa,
README updates for module usage examples,
the EXAMPLES usage for occurrence and other modules,
and new functions from the occurrences included in the pyobis/init.py.

However, this might make some tests to fail.

Let's try to get PRs a bit cleaner in the future by making smaller PRs on feature branches, but I am going to go ahead and merge this one and whatever else we need to get things caught up with your dev environment.

Thanks a ton @7yl4r! I will make sure I address only one objective for one PR for all subsequent PRs.
I am now working on making commits to revert back those changes I had to undo to resolve merge conflicts.


Update all available URLs from HTTP to HTTPS

Detected and changed HTTPS URLs automatically using my HTTPS Spotter script, and then tested all changed recipes manually to ensure download success.

Thanks, works here.

Thanks, works here.


NOTICE file

Added some missing notice files for some modules.
Updated nbbuild/notice-stub.txt "preamble" to acknowledge previous copyright notices in the codebase.
Updated build.xml and created CreateNoticeFile.java ant task to create the NOTICE file.

The NOTICE file depends on the build as follows:

For source builds (binaryBuild="false") only the "preamble" and any "[module]/**notice.txt" are included in the NOTICE file.
For binary builds (binaryBuild="true") the preamble, any "[module]/**notice.txt" and any "[module]/external/**notice.txt" files are included.

The list of modules to include depends on "nb.clusters.list" (if present) or "cluster.config.${cluster.config}.list". See "CreateNoticeFile.java" for the exact algorithm.
This task has to be reviewed. It seems to be working properly when running "ant build-platform", "ant" and "ant build-source-zips", generating different NOTICE files in each situation.

Great. But there seems to be a Travis problem.

I'd like to know if:
a) I'm computing correctly the modules that conform the build.
b) If I'm hooking at appropriate places in "build.xml" for generating the NOTICE file.
Note that as the Apache requirements mandate only the binaries that form part of the build must be included in the final NOTICE file (so, for instance, platform builds will have a NOTICE file different to an ide build).

First: Thank you for looking into this!
Jan did some work on this - see here:
https://github.com/apache/incubator-netbeans/commits/generate-license-notice-dependencies
The branch is far behind master, but it might be good to have a look.
For the added notice files, I think in many cases they need to be smaller:
http://www.apache.org/dev/licensing-howto.html#alv2-dep

If the dependency supplies a NOTICE file, its contents must be analyzed and the relevant portions bubbled up into the top-level NOTICE file.

And
http://www.apache.org/dev/licensing-howto.html#bundle-asf-product

It is not necessary to duplicate the line "This product includes software developed at the Apache Software Foundation...", though the ASF copyright line and any other portions of NOTICE must be considered for propagation.

So the "This product includes software developed by The Apache Software Foundation (http://www.apache.org/)." should be removed from the additional notices.

Hi Matthias.
Thank you for looking into this too. This is one of those boring tasks that should be done to move forward.
Yep, I took a look at Jan's branch but we were repeating notice files and AFAIK the notices were all the same for all builds. Note that this PR is about the NOTICE file only, not about the rest of licensing/dependencies/whatever (that would require another PR).
The expression "its contents must be analyzed and the relevant portions bubbled up into the top-level NOTICE file" in the requirements doesn't make sense to me: I need a clear definition of what "relevant portion" means. From my point of view, and since I'm not a lawyer, all the content is a "relevant portion", otherwise it won't be there. Maybe we want to ask legal what "relevant portion" means.
Finally regarding the "It is not necessary to duplicate the line ..." the "it is not necessary" does not imply per se, that we should remove it.  But as you well point out there's another requirement stating that the NOTICE file should be kept small, so there's a bug in the requirements. The line "It is not necessary to duplicate the line..." should be rephrased to read "It is mandatory to remove the line...".
I'll modify the ant task later on to remove these lines automatically from the NOTICE files when adding them to the final one (but I think we should keep the original NOTICE files intact, as their authors wrote them).
Thanks again,
Antonio

Hi all,
I'll be doing some improvements today (and adding some bugs as well ;-), and will be abusing the Travis-ci builds. Is this ok for you? May I?
Thanks,
Antonio

Sure. However, please focus on specifically anything that needs to be done for the Beta release, so that we can start the vote on that as soon as possible.

I think the NOTICE file is now ready for the Beta release.
We may improve performance and reorganize the binaries & checks later on, when there's no time pressure.

Great. Merging. If there's problems or additions, we can do that in a new pull request.


[DUP] sub-0038_ses-03_task-shortvideo_acq-mb8_run-01

TODO

BOLD TR is 1640

Expected TR is 1616

How is this possible? The expected TR is shorter than what is collected? Was this even a parameter baked into the scans?

[x] evaluate and delete bold and dup altogether

scannotes
No notes on shortvideo task

Align video code was run while short vid ran on scanner. Repeated the run.

c0940dc881edf6c564dc40d0bbd0238a87aaa188
./code/spacetop-prep/spacetop_prep/datalad/remove_dups_anatfmap.sh


regression in nilearn is broken for voxels with no signal

somehow regression of confounds induces a signal, instead of leaving the time series at zero.


prefix for multi robot system

Hi,
I'm trying to control multi robots using ros2_control.
The information in this repository has been very helpful and I appreciate it.
Now, the code says that "If changed then also joint names in the controllers' configuration have to be updated."
So, I must modify a .yaml file for each robot, right?
I think it is useful for multi-robot control to be able to automatically add a prefix for the controller's joint name.
Is there any chance that this feature will be implemented?
https://github.com/ros-controls/ros2_control_demos/blob/2dc7c3717c1ceaaabd1576033d3f33b8c09882f6/ros2_control_demo_bringup/launch/diffbot_system.launch.py#L58-L62
Thanks,
Daisuke

This is an interesting feature.
Could you elaborate on the scenario ? Do you have a working example to start with ?

I assuming multi-robots controlled with autonomous or teleoperation.
They are homogeneous and have a unique identifier (such as hostname or mac address, anything unique).
I'll use the identifier to divide the namespace.
Basically, they work autonomously but when any trouble occurs, it should solve by teleoperation.
I would have to modify controller.yaml for each robot.
It might be good with few robots but the more we have, the harder it gets.
Ideally, I would like to be able to join the multi-robot ROS2 network as soon as I clone the system and turn it on.
For now, I put the substitution characters in controller.yaml and replace them in launch.py.

Hi, this is very intriguing feature. Just to clarify your use-case:

you are using the same URDF/XACRO for each robot in our multi-robot system
then for each robot you set different prefix so that their joint names are unique
the issue you have is that you theoretically need a separate "controllers.yaml" file for each robot because of mapping of controller to joints

Did I get this right?
Your approach seems correct and simplest to implement as of now.
What is actually disturbing with it?
How do you imagine this should be handled?
Which controller are you using? A potential solution could be to add "joint_name_prefix" parameter in the controller and then support it. (Not sure if this will solve the problem directly).

use-case

Yes, that's right.
I use forward_command_controller/ForwardCommandController ( rrbot_system_position_only.launch.py based).
I want to handle multiple similar groups easily, like namespace.
My approach seems symptomatic.
Getting it to work well is a very enjoyable task for me, but it can be very annoying for others.

to add "joint_name_prefix" parameter

It seems a good way than my approach.
I consider making a controller that ForwardCommandController based for use that method.
It might be confusing with namespaces and prefixes, but I'll try it anyway.
I think the multi-robot use case is one of the most important features of ROS2.
It would be nice to have some typical use cases as an example in ros2_control.

I agree, but they are several possible scenarios.
For now the most "simple" one seems to have one HardwareInterface with several systems.
Checking already this scenario would be interesting.
It could be for instance two rrbot and a slider which have all a fixed base.
It seems to me that this one could be done with the current version of ros_control
Another scenario could an be an intemittent compound robot. A mobile robot with an arm (mobile_robot=diffbot + rrbot) moving around independently, approching another rrbot (snd_rrbot),  create temporarly a combined robot (mobile_robot + snd_rrbot) to interact. This one seems way more complicated. Several implementations are possible and honestly I do not have a strong opinion on this and would be interested to have feedback on this one.

I assumed the first scenario but interesting in the second one.
It's a task like an excavator loading a dump truck.
The idea which creating temporarily a combined robot looks good to me.
We can attend to main tasks and be able to don't care which robot we teleoperate with.
I haven't enough idea about the second scenario.
However, the collaboration of robots will increase in the future.
I'll think about it.

We have a multi-robot example (13) now, maybe not exactly what was asked for. The framework has evolved in the past three years, I'll close this issue due to inactivity.


Updated readme details

Removed the Beta details

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


build fails

hello. i'm trying to build the example that ships with this repo and getting the following namespace collision for the camelize package:
Error building DependencyGraph:
 Error: Naming collision detected: ~/react/react-native-relay/node_modules/react/node_modules/fbjs/lib/camelize.js collides with ~/react/react-native-relay/node_modules/react-native/node_modules/fbjs/lib/camelize.js
    at HasteMap._updateHasteMap (HasteMap.js:132:13)
    at HasteMap.js:103:28
    at tryCallOne (/Users/206603/Sites/FUN/react/react-native-relay/node_modules/react-native/node_modules/promise/lib/core.js:37:12)
    at /Users/206603/Sites/FUN/react/react-native-relay/node_modules/react-native/node_modules/promise/lib/core.js:123:15
    at flush (/Users/206603/Sites/FUN/react/react-native-relay/node_modules/react-native/node_modules/promise/node_modules/asap/raw.js:50:29)
    at nextTickCallbackWith0Args (node.js:415:9)
    at process._tickCallback (node.js:344:13)

Thanks for the report (and sorry for the delay in responding). Tested current master and everything seems to be ok, so going to close this one for now. Feel free to open another issue if this problem arises again, or another one does.


static vs per instance snapshot

In current proposal snapshot() is a static method capturing full context of all AsyncContext variables.
As a result snapshot.run() impacts all AsyncContext users.
This differs from asyncVar.run() usage where current context entries for other asyncVar instances are not impacted.
This global context restore sounds reasonable for library authors (or runtime internally) which knows and defines the global context flow. For example restoring JS context after interacting with some scheduling outside of JS (e.g. interacting with OS sockets,...).
But with the discussions ongoing in #83 or AsyncContext.callingContext() I'm not that sure if this global snapshot/restore is a good thing in general.
Once some AsyncContext user starts to call snapshot() to customize/tune it's context flow it might break other users.
Not sure a an instance snapshot() API is the way to go. Maybe it is more a doc topic to tell users to prefer const myData = asyncVar.get() and asyncVar.run(myData) instead snapshot().

I think static snapshot is fine, we just need per-instance escape routes. I think we should have a recommended default path which is usable in most cases, we just would want some tools to reach the other paths in the few cases which don't quite fit. Ideally though the need for manual work should be kept to a minimum through reasonable defaults.

I agree, especially if we go with call-time context being propagated by default, that the global snapshot will likely lead to broken behavior. Shay is discussing a "delimited continuation" idea what might work better. Instead of capturing all variables globally, it captures all variables up until the last time my variable was set:
const mine = new Variable();
const outer = new Variable();
const childOther = new Variable();

const snap = outer.run(1, () => {
  // outer is outside the last `mine.run()`, so it won't be captured.

  return mine.run('abc', () => {
    // child other is inside the last `mine.run()`, so it is captured.
    return childOther.run(true, () => {
      return Snapshot.partial(mine);
    });
  });
});

snap.run(() => {
  assert.equal(outer.get(), undefined);
  assert.equal(mine.get(), 1);
  assert.equal(childOther.get(), true);
});

I don't think that the nesting should matter here. Either the variables are independent or they aren't.
Consider other and mine are context variables created by independent tools using some sort of instrumentation/hook instrumentation at the same place because both are interested in it for their own special and private thing.
The sequence of the run calls only depends in the init sequence of these tools. This is an unwanted hidden binding in my opinion.
I see value for a global snapshot and for a per variable snapshot:

global is useful for interaction with the outside (e.g. OS)
private is useful to tune propagation for my needs

What would a per-variable (instance) snapshot look like?  Isn't it just myVar.get()/myVar.run()?
const snapshot = myVar.get();
// ...
myVar.run(snapshot, () => ...);

Overall, I don't really understand the point of any solution that doesn't handle all variables implicitly by default.  The whole point of a "context" is to remove the need for intervening layers to have any knowledge of the data that's passing through them - the moment you add a requirement to handle any variables explicitly, they're no longer propagated through the intervening code that doesn't (or can't) know about them.

Yes, it's myVar.get()/myVar.run().
Main point is if a dedicated API for this should be visible in the AsyncContext API surface to avoid that people go for global even if they shouldn't.
The global handing is nice for library authors to express how context flows through their scheduler,...
Local handling is needed for users which do not agree to this for whatever reason.
Or if some 3rd party tooling (e.g. OTel instrumentations) "adds" context handling via monkey patching because a library hasn't implemented it yet/correct. Such tools usually do not want to create global side effects.


Use new install_location attribute everywhere

The install_location attribute was used only for the copy part.
The provider was assuming that nssm is in the path and the recipe guard that it's in c:\windows
So I added 2 helpers to determine the binary path and whether it's present or not; then I leverage them in the provider and recipe.

I'm wondering if this could be simplified by explicitly specifying the executable path:
For example:
  batch 'copy_nssm' do
    code <<-EOH
      xcopy #{Chef::Config[:file_cache_path].gsub('/', '\\')}\\#{basename}\\#{system}\\nssm.exe \
"#{node['nssm']['install_location']}" /y
    EOH
    not_if { ::File.exist?("#{node['nssm']['install_location']}\\nssm.exe") }
  end

and
    batch "Install #{new_resource.servicename} service" do
      code <<-EOH
        #{node['nssm']['install_location']}\\nssm.exe install "#{new_resource.servicename}" "#{new_resource.program}" #{new_resource.args}
      EOH
      not_if { service_installed }
    end

Would this accomplish the same thing?
Thanks,
Dennis

I'm quite sure we can simplify the provider :) You are right.
But I don't understand why you merged this PR, if you changed everything in the next commit.

I started to fix the failing tests and got carried away.
On Sat, Aug 8, 2015 at 5:28 PM, Baptiste Courtois<EMAIL_ADDRESS>wrote:

I'm quite sure we can simplify the provider :) You are right.
But I don't understand why you merged this PR, if you changed everything
in the next commit.
—
Reply to this email directly or view it on GitHub
https://github.com/dhoer/chef-nssm/pull/3#issuecomment-129078313.

Thanks for pull request. I like the environment thing you did. Version 1.2 is released. Let me know if you have any issues.

@Annih I wanted to give you a better explanation as to why I merged the PR and then changed it:

I want to make sure you get credit under Contributions. I don't know any other way except merge PR.
Style preference, I only like to use libraries if their methods are used in 2 or more recipes or provisioners.
I like to use separation of concern pattern, so the business logic to determine weather to install or update nssm should be only in the concern of the default recipe, not both default recipe and provisioner.

I hope I didn't offend you by making these change.  Thanks again for the PR and making nssm better.


SAA-1149: Remove pen test IPs from allow list

Codecov Report
Patch has no changes to coverable lines.

:exclamation: Current head 4b246f9 differs from pull request most recent head fbb69fd. Consider uploading reports for the commit fbb69fd to get more accurate results

:loudspeaker: Thoughts on this report? Let us know!.


pull request for e2e test at 12/29/2016 09:45:07

:white_check_mark: Validation status: passed
For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Use case: robotic components should have transparent state representation

When using hardware components they can be in different states. This is really considered in hardware_interface in ROS1, which often leads to a completely new start of the whole control system.
The states could be:

LOADED: objects of components and interfaces are created (e.g. classes are loaded using pluginlib)
CONFIGURED: parameters for the robot are read from parameter server and the objects are configured according to them
INITIALIZED: there is communication with a real hardware (or simulation) and components are ready to start. No active movement allowed.
RUNNING: active movement/control is allowed.
STOPPED: as initialized, but previous state was running
HALTED: similar to initialized, but an unexpected event occurred and the robot should be further used with caution. The next state is INITIALIZED, after the is solved.

done


All NPC companion comes with you

If you go into allness and have Vasco or the fan as a companion, he comes with you into allness and is there to support you.
I haven't noticed this with other companions.

Game Version
<IP_ADDRESS>
Language
Deutsch (DE)
New Game
Yes
Reproduction Steps
If you go into allness and have Vasco or the fan as a companion, he comes with you into allness and is there to support you.
I haven't noticed this with other companions.

This was a bug specific to Vasco, and it was fixed in SFCP 1.0.0.


Set the background color of RenderViewHost to transparent

This removes the white flash when loading a page on Windows and Linux.
Fix #4985.
Fix #1626.

:+1:


IsEffectivelyVisible should be a proper property just like IsEffectivelyEnabled is

Is your feature request related to a problem? Please describe.
The problem is: control doesn't know when it becomes invisible due to it's parent IsVisible being changed to false.
This causes me problem with two cases:

I tried to design a control which plays an animation when becomes visible. This worked fine if you manipulate IsVisible of the control itself, but broke if you change IsVisible of parent control
I deisgn an Ui Voice Control Engine and parse logical tree to search for controls which spawn content like ItemsControl and ContentControl, and subscribe to its events to know when their content is changed and I need to re-parse it. The problem is, if content is changed when control is not visible, the content is not actually spawned, and despite event being fired, I will load nothing by parsing them, until they becomes Visible, and I can't monitor their Visibility, unless it is directly controlled

Describe the solution you'd like
I would very much prefer IsEffectivelyVisible being an actualy property just like IsEffectivelyEnabled which can be monitored via PropertyChanged event
Describe alternatives you've considered
The current workaround is to subscribe to IsVisible change of every logical parent of control in tree, which is hacky and very unstabled solution for obvious reasons
Additional context
No response

I'd be hesitant to do this because of the performance overhead: the property change handler will have to be called for potentially the entire visual tree each time the property value changes, even if the property has no listeners (we don't know what people are doing in their OnPropertyChanged/PropertyChanged handlers so have to raise the event whether there are subscribers or not).
A potential alternative solution would be to add an EffectivelyVisibleChanged CLR event: this way we can explicitly tell when there are subscribers and avoid the overhead when there are none.


Automate Users/Retentions/Dashboard with Helm Chart

Issue / Case

We want to automate the followings:

Create/Register the admin user within helm chart deployment
Modify retention period for logs, trace and metrics within helm chart deployment.
Import Signoz Dashboard with helm chart deployment. --- just like its available in grafana chart.

Efforts

I checked the helm chart and your docs, all of the above can only be done only from UI.

Feature/Request/Enhancement

Is it possible to add this soon, because deploying the chart on multiple clusters will be a hectic process.

Chart Version

Chart version used at this time is 0.11.3

Thanks in advance.

These are all the issues that are preventing us from using SigNoz, since we have multiple environments and don't want to have to configure them all by hand.

Would terraform be helpful?
We have a terraform provider (https://github.com/SigNoz/terraform-provider-signoz) for managing alerts right now.
We plan on adding dashboards as well.


belated PR :)

@rtyler the main commits are
https://github.com/lookout/fast-rsa-engine/commit/3839c553d09fbec5e4b5b20cdb5579c07e0ffb68
https://github.com/lookout/fast-rsa-engine/commit/6fce61b10a37fd348de1d0028902b939fecb0b08
https://github.com/lookout/fast-rsa-engine/commit/896a079f4a317d764c987fa35887b7e20e691ffc

There's some stuff here that I think we need to clean up before release, but I'll either file that in Issues or we can talk about it in person


WIP Feat/storage usage

Q
A

Bug fix?
N

New feature?
Y

BC breaks?
Y

Deprecations?
N

Fixed tickets
N

Replace the read-only/skip system by a type of usage for storages organised by level:

cache (i.e. storage processor outputs)
config (i.e asset processor config)
asset (i.e. document uploaded in the CMS
backup (i.e. used by the ems:asset:synch command)
external (i.e. read-only)

So, if a want to upload an asset, it will be saved on cache, config and cache storages, And config will be save on cache and config storages

Perfect 👍


Removes splash patches

This removes the splash screen patches (ref #76 and #100) because they're causing problems on bare ignite new Foo -b ir-boilerplate-bowser projects.
I've generated a new Ignite plugin that could be run on an Ignited project with ignite add splash. It's not ready yet (waiting on @leonskim and @robinheinze to review and fix whatever's wrong with it right now).

@jamon This looks good to me, since it's just the removal of the patches. The CI failures don't look related...

Another test confirmed https://github.com/infinitered/ignite-ir-boilerplate-bowser/issues/131#issuecomment-444381435

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Poland Based Toll Free Numbers do not pass validation

The phone number in question is: 0-0-800-141-0203.

https://tollfreeforwarding.com/ - note that when you select Poland from their country selection, all of the numbers that they show use the same number format as the number provided above.
We had someone in Warsaw, Poland call the number exactly as is, and they were able to make a successful connection.

Hi,
Thanks for reporting this issue.
I have created an issue in issue tracker with all the details you have provided. We will be soon disabling issue creation in GitHub. We will triage this at:
https://issuetracker.google.com/issues/74296959


Plowing infected spots on the board with a shield.

How to play your game?

Press WASD to move, Push the shield (blue) into the infected tiles (green) to plow them away. Hit ‘I’ for Info.

Code
Check off the items that are true.

[x] The game was made using the Sprig editor.
[x] The game is placed in the in the /games directory.
[x] The code is significantly different from all other games in the Sprig gallery (except for games labeled "demo").
[x] The game runs without errors.
[x] The name of the file/game contains only alphanumeric characters, -s, or _s.
[x]The game name is not the same as the others from gallery

Image (If an image is used)

[x] The image is in the /games/img directory.
[x] The name of the image matches the name of your file. Example: sokoban_plus.js -> sokoban_plus.png.

Thanks for PR!

I'll do just one more test and I'll merge

I learned about sprig while reading an online article
It can be found here: https://www.geeky-gadgets.com/open-source-game-console-11-11-2022/

Thank you for your time, have a wonderful day!

thanks for contributing to the Sprig!


Cannot install on Ubuntu 14.04: premature member 'control.tar.xz' before 'control.tar.gz'

Issue Title
I am following the instructions from: https://dotnet.microsoft.com/download/linux-package-manager/ubuntu14-04/runtime-2.2.4
But it fails to install:
Get:1 https://packages.microsoft.com/ubuntu/14.04/prod/ trusty/main dotnet-runtime-deps-2.2 amd64 2.2.4-1 [2,608 B]
Get:2 https://packages.microsoft.com/ubuntu/14.04/prod/ trusty/main dotnet-host amd64 2.2.4-1 [36.4 kB]
Get:3 https://packages.microsoft.com/ubuntu/14.04/prod/ trusty/main dotnet-hostfxr-2.2 amd64 2.2.4-1 [145 kB]
Get:4 https://packages.microsoft.com/ubuntu/14.04/prod/ trusty/main dotnet-runtime-2.2 amd64 2.2.4-1 [20.7 MB]
Get:5 https://packages.microsoft.com/ubuntu/14.04/prod/ trusty/main aspnetcore-runtime-2.2 amd64 2.2.4-1 [22.8 MB]
Fetched 43.7 MB in 3s (11.0 MB/s)
Selecting previously unselected package dotnet-runtime-deps-2.2.
(Reading database ... 38023 files and directories currently installed.)
Preparing to unpack .../dotnet-runtime-deps-2.2_2.2.4-1_amd64.deb ...
Unpacking dotnet-runtime-deps-2.2 (2.2.4-1) ...
Preparing to unpack .../dotnet-host_2.2.4-1_amd64.deb ...
Unpacking dotnet-host (2.2.4-1) over (1.1.0-preview1-001100-00-1) ...
Selecting previously unselected package dotnet-hostfxr-2.2.
Preparing to unpack .../dotnet-hostfxr-2.2_2.2.4-1_amd64.deb ...
Unpacking dotnet-hostfxr-2.2 (2.2.4-1) ...
Selecting previously unselected package dotnet-runtime-2.2.
Preparing to unpack .../dotnet-runtime-2.2_2.2.4-1_amd64.deb ...
Unpacking dotnet-runtime-2.2 (2.2.4-1) ...
dpkg-deb: error: archive '/var/cache/apt/archives/aspnetcore-runtime-2.2_2.2.4-1_amd64.deb' has premature member 'control.tar.xz' before 'control.tar.gz', giving up
dpkg: error processing archive /var/cache/apt/archives/aspnetcore-runtime-2.2_2.2.4-1_amd64.deb (--unpack):
 subprocess dpkg-deb --control returned error exit status 2
Processing triggers for man-db (<IP_ADDRESS>-1ubuntu1) ...
Errors were encountered while processing:
 /var/cache/apt/archives/aspnetcore-runtime-2.2_2.2.4-1_amd64.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)

Looks like a duplicate of https://github.com/dotnet/core/issues/2381
A sudo apt-get update && sudo apt-get upgrade before sudo apt-get install aspnetcore-runtime-2.2 should fix things.

@omajid Thank you!


feat: add mock function to overrides non-configurable props

Based on #100. Fixes #99.
I don't know, if mock is the best name. Maybe override? I don't know. 🤷♀ 😄

Can someone review this 🙏  ?

I could very much use this PR.  I'm stuck on 0.6.0 until there's some way to mock onbeforeunload

I could very much use this PR.  I'm stuck on 0.6.0 until there's some way to mock onbeforeunload

Hey @simonihmig! I know you probably have more important things to do 😅 But is there any chance we could get this PR merged? It'd be very helpful 🙏🏻 Thanks in advance for all your work!

Hey folks, so the thing here is that this is based (contains those commits) on #100, which had some longer discussions a (even longer) while ago, and which seems to not have been finalized.
I am really not aware anymore of the exact state of those PRs, would need some time to dig into it again. AFAIR the work in #100 is technically required before we can land this, right?
@buschtoens what about you, are you still interested in working on these? Somehow the momentum was interrupted at some point unfortunately, and the PRs became dormant. Not intending to blame anyone here, not having the time to continue work would be totally understandable, just want to figure out if/how we can move this forward!

I'm stuck on 0.6.0 until there's some way to mock onbeforeunload

Sorry @boydkr for the late reply. Could you explain why you need this PR to mock onbeforeunload. It is a writeable prop after all, right? So that should work, unless I am missing something. In case there is an issue, but it is unrelated to this PR here - which is about overriding non-configurable, non-writable properties AFAIU - then please file a separate issue!

Closing this as the work is abandoned and way out of sync.


eval monitor not working correctly

Describe the bug
Docs unclear or app not working as intended. I'm not getting the eval monitor to work
To Reproduce
Steps to reproduce the behavior:
Copy just the eval monitor from the docs, paste it in an empty monitor config.
Expected behavior
A working monitor
Additional context
On latest release. I tried everything with the syntax, without any luck.
Kener is running on port 3000! undefined:1 SyntaxError: Unexpected end of JSON input     at JSON.parse (<anonymous>)     at eval (eval at Startup (file:///app/scripts/startup.js:114:32), <anonymous>:2:19)     at eval (eval at Startup (file:///app/scripts/startup.js:114:32), <anonymous>:12:1)     at Startup (file:///app/scripts/startup.js:114:32)     at process.processTicksAndRejections (node:internal/process/task_queues:95:5)

This is resolved


⚠ DDoS-Relay EU-C-fsn1-4 has degraded performance

In 8617d4a, DDoS-Relay EU-C-fsn1-4 (http://<IP_ADDRESS>:42069/;csv) experienced degraded performance:

HTTP code: 200
Response time: 296 ms

Resolved: DDoS-Relay EU-C-fsn1-4 performance has improved in ef54ce0 after 5 minutes.


Is this the correct way to do regional MFD inversion constraints

Hi @kevinmilner
I've got this running, and I think its OK but can you take a quick look please?
https://github.com/GNS-Science/nshm-nz-opensha/blob/a5e5b0c9aceb62d66cea732004b4ed21b8b2b481/src/main/java/nz/cri/gns/NSHM/opensha/inversion/NSHMInversionRunner.java#L283
I've created two Regions  - SanTVZ and TVZ, and  Equality + Inequality MFDs with different bvalues (A & B) .
       constraints.add(new MFDEqualityInversionConstraint(rupSet, mfdEqualityConstraintWt,
               Lists.newArrayList(equalityConstrA, equalityConstrB), null));
...
       constraints.add(new MFDInequalityInversionConstraint(rupSet, mfdInequalityConstraintWt,
               Lists.newArrayList(inequalityConstrA, inequalityConstrB)));

We're parametrizing our NSHMIinversionRunner, so I'm keen to get this bit right before I finalise our automation API.
Cheers :)

ref branch 94_parametrize_inversion

ref branch 94_parametrize_inversion


Change default branch from master to main

Don't rush, though. Nobody cares but yourself ☀

Done


开启的服务器无响应

在 ipa 文件所在文件夹运行 ios-ipa-server后，出现提示https://<IP_ADDRESS>:1234/download
然后在浏览器中浏览https://<IP_ADDRESS>:1234/download长时间无响应，命令行中运行curl https://<IP_ADDRESS>:1234/download，出现一大坨提示

curl: (60) SSL certificate problem: Invalid certificate chain
More details here: https://curl.haxx.se/docs/sslcerts.html

curl performs SSL certificate verification by default, using a "bundle"
 of Certificate Authority (CA) public keys (CA certs). If the default
 bundle file isn't adequate, you can specify an alternate file
 using the --cacert option.
If this HTTPS server uses a certificate signed by a CA represented in
 the bundle, the certificate verification probably failed due to a
 problem with the certificate (it might be expired, or the name might
 not match the domain name in the URL).
If you'd like to turn off curl's verification of the certificate, use
 the -k (or --insecure) option.

我之前使用 Mac 中的 Apache 使用自签名的证书成功开启过 https 服务，不知道是否有影响。上述错误需要怎么处理呢？

@Navimark 你是什么浏览器，试试chrome


card command

display user skills with a card command.
the card image can be made using html+css and converting it to a .png file format.

use https://github.com/YoruNoKen/HanamiCard to generate the card


pyansys.jobname uses default/init jobname

The fix for #90 does not work in all cases.
https://github.com/akaszynski/pyansys/commit/9021630249675824361491a1b5cd0e1ab92540e6
Thats because pyansys.jobname is not set when calling
ansys.Run("/FILNAME,...
or
ansys.Filename()

Good catch!  Sorry, I've been a bit slow on getting to issues with pyansys and I'm busy with other work at the moment.  I'll try to patch these issues today or tomorrow.

Patched in #108


Small version bump to redshell port

Bump version of redshell port.

Thanks for making this PR! Could you also update the "built-using" field in the CONTROL file so we can keep track?

Just took a look, this new version was built using the exact same libs, as well as the same versions of those libs. No changes.
Let me know if you would like me to change anything else.
Thanks for the quick response!

I know that in the case of cpprestsdk there were several memory leaks and crashes fixed in the latest (2.10). In openssl, two releases have gone by (we're on 1.0.2m now) which has several security fixes associated with it.
I don't think this blocks the update if you do not want those fixes, but I think your users would appreciate it :).

Rebuilt and updated deps.
Thanks for letting me know about that!

Thanks!


quantization script doesn't use the right eval metric and hence leading to accuracy drop

Model : facebook/bart-large-cnn
Script : optimum-intel/examples/neural_compressor/summarization/run_summarization_post_training.py
Quant type : Static
Sample command : python run_summarization_post_training.py --model_name_or_path facebook/bart-large-cnn --dataset_name cnn_dailymail --dataset_config "3.0.0" --apply_quantization --quantization_approach static --num_calibration_samples 50 --do_eval --verify_loading --predict_with_generate --per_device_train_batch_size=4 --per_device_eval_batch_size=4 --output_dir output --pad_to_max_length --num_beams 1
Issue : Since the script doesn't pass some relevant eval metric (like RougeLM), neural-compressor is defaulting to TopK. Hence the accuracy of the quantized model is bad. Ideally optimum-intel should have passed an eval-metric like RougeLM to ensure a proper accuracy aware quantization.
Quantization log :

@echarlaix Do we have any document to help user add the eval_func themselves?

Here is the document about adding customized eval_func for tuning: https://huggingface.co/docs/optimum/main/en/intel/optimization_inc#dynamic-quantization.
Thanks to @echarlaix


test: addition of the connectors_mgmt test to the ci pipeline

I'm not sure why this is failing, when pulled and ran locally this passes with only a couple of warnings.
It should be operational as this has been merged.
I'm looking into it

@dimakis have this change been merged on SDK level?


criu: 3.15 -> 3.17.1

Description of changes
https://criu.org/Download/criu/3.16
https://criu.org/Download/criu/3.17
Things done

Built on platform(s)

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

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

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

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

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

[x] Fits CONTRIBUTING.md.

Also removed prefixing PATH since iptables can be passed with the CR_IPTABLES environment variable: https://github.com/checkpoint-restore/criu/blob/7d7d25f946e10b00c522dc44eb9c60d9eba2e7a0/criu/net.c#L1974


My personal goals

ADDED my personal GOALS
Kindly review the changes.

Some checks were not successful. Consider keeping an emphasis on style as it should be consistent [Expected: underscore; Actual: asterisk]


Eco preset / quiet mode swapped

My unit (CS-RZ25WKRW) has a quiet mode for fan speed as well as an eco function
Setting the eco mode in the panasonic app turns on the eco light however setting it in this integration turns on quiet mode for the fan. I don't seem to have any other options to turn on Eco mode.
Is this an known issue or something that can be added?
I'm using the CZ-TACG1 adaptor if it is related to that.

Hi @brywithawhy, I think I might be able to expose the eco preset mode.
One thing you could try is calling climate.set_preset_mode with eco and see if it does anything.

Hi @sockless-coding
Calling the service sets quiet mode on the unit, but eco is reported in the integration. Same as doing it via the lovelace card

I have a similar issue:
my units CS-X35ZKEW-H feature a "quiet mode". However in order to engage it via this integration I have to set preset to "Eco mode"

This is an old bug/sin... fixing it would introduce a breaking change... the HA built-in PRESET_ECO was used for Quiet from day 1

Ok i see, personally I would be fine with a breaking change but I totally get it that it might not be worth it for many

@Kugelfang666 there should now be a switch to toggle the eco navi feature

Thanks for putting effort into this. I just updated to 1.0.51 but I don’t see that button, am I looking at the right spot?

It should be a separate switch

I have a similar issue:
my units CS-X35ZKEW-H feature a "quiet mode". However in order to engage it via this integration I have to set preset to "Eco mode"

It's been a while since I raised this and can't quite remember what the result was, but I ended up using an esp32 instead of the cz-tacg device to control it all without the comfort cloud and the functionality matches that of the remote control
https://github.com/DomiStyle/esphome-panasonic-ac
If you're interested

It should be a separate switch

this setting did not show up for any of my devices after updating

I've added a new configuration option (in the next release) that should be default True for new installations and False for existing ones.

That switches to the panasonic naming of presets:

I can confirm this is now working for me! Thanks a lot for putting the effort into this, much apprechiated!


[Sprint: 51] XD-3172 Add file source option splitWithMarkers

Enables the SOF/EOF markers when splitting a file into lines

Upgrade Spring Integration dependency from 4.1.4.RELEASE to 4.1.5.RELEASE
Add test
Add documentation

Jira: https://jira.spring.io/browse/XD-3172

Pushed an update (hopefully) addressing all issues. Also added one more test.

However, since you've done the work already I'll go ahead and merge.

@ghillert can you rebase? There are doc conflicts; thanks

Rebased, merged as 9a05d494befb2ce8655fb05283c4b7c73a49b8fb


testing coverage: add matrix / table of what configuration options of daemon we are currently testing (and need to test!)

Subtasks

[ ] https://github.com/cilium/cilium/issues/11486 - Direct-routing + (L7) policy

Dimensions
Included in matrix below

Endpoint devices - veth / ipvlan
Cluster connectivity - direct-routing (endpoint routes) / direct-routing (tailcall) /  tunnel-mode
Service connectivity - kube-proxy nodeport / BPF nodeport
Traffic security - encryption / no encryption
Endpoint security - L7 / no L7
Socket acceleration - sockops / no sockops

Excluded from matrix below
The below are excluded to keep the matrix to a manageable size; their impact on dataplane connectivity is lower than those in the above list.

Host services - host-reachable / none
Host security - encrypt-node / none
IP connectivity - IPv4 / IPv6 / both

Commandline arguments for configuration

--datapath-mode (veth / ipvlan)
--ipam (This actually controls not only IPAM, but also ENI mode for CNI)
--tunnel, --auto-direct-node-routes
--enable-node-port
--masquerade
--enable-host-reachable-services
--install-iptables-rules (impacts ipsec, L7 policy, NodePort via kube-proxy)
--enable-ipsec
--encrypt-interface (should be covered by --enable-ipsec)
--encrypt-node
--single-cluster-route (incompatible with tunnel disabled)
--enable-endpoint-routes
--sockops-enable
--enable-ipv4 / --enable-ipv6

Configuration Matrix
Reading the matrix

The top of the matrix determines settings related to security
The left of the matrix determines settings related to connectivity

Key

X -- Invalid combination
N -- No known testing
M -- Manually tested during 1.6 cycle
A -- Automatically regression-tested by CI (basic connectivity)

Matrix
Note, eni is the cluster connectivity device type + configuration, not endpoint device type. ENI is typically onfigured with veth devices. This matrix needs updating.

[5] via https://docs.cilium.io/en/latest/gettingstarted/ipvlan/#ipvlan-based-networking-beta
[6] I can't find any documentation related to this, but I don't think ENI + Tunnel works. ENI + Tunnel works but it's pretty pointless. I've manually tested it but don't expect anybody to use it.

Notes and limitations

This matrix is focused on configuration elements that affect datapath configuration such as BPF programs, iptables rules, rule and route configurations. It does not attempt to distinguish policy cases such as in-cluster/out-cluster; L3/L4/L7 Policy (other than for the L7 redirects); etc.
The datapath configuration tests configure different combinations of the above dimensions, however they do not cover the matrix with L7 policy; nor do they make calls through services; only directly via pod IPs.
Per-endpoint routes is considered orthogonal to tunnel and only compatible with direct-routing, hence only an option for direct routing in the table above.

host services / security could be added trivially to the matrix by adding them to the encryption / services column/row, though AFAIK the current status is pretty much that they were presumably manual tested when the feature went in but there is no CI coverage on these features.

Thanks for doing this although I don't actually think this statement is correct "The below are excluded to keep the matrix to a manageable size; they are also typically orthogonal to the dataplane connectivity." Sockmap and encryption both change the datapath quite a bit IMO.

For encryption I have a patch that can enable encryption for the entire CI run so we may want to consider running this at some cadence, nightly, weekly, at minimum before RC releases?

Any objections to adding a test to connectivity tests that also adds L7 policy. For CI this would be good to run in all cases so we bounce through proxy  in ipsec/sockmap cases.

It's been a while since I looked at the cross-section of features here. The existing features are likely still applicable, we probably just have a bunch more in various dimensions. Moving to CI-improvement projects. We may want to split out some of the tasks into subtasks with references to other issues to make this item more manageable.

The table we wrote up in the main description of this issue above is no longer up-to-date, given that we've deprecated ipvlan; there's now the connectivity check YAMLs and the Cilium CLI regularly tests various combinations, including against cloud providers and against configurations with/without IPsec (based on github actions infrastructure, see .github/).
Probably the main thing that was missing also from the table above is whether the traffic stays entirely within the node, or whether it crosses to other nodes. This is also covered by the newer testing primitives.
At this point I don't think it's necessary to keep this open and it doesn't reflect the reality of testing coverage today. We can always use this as a template for further analysis of the testing coverage, but I'd suggest we open new issues to analyse the conditions we care about if that's the case. Closing out.


Debug options don't show up when accessible in a new notebook

Applies To

[X] Notebooks (.ipynb files)
[ ] Interactive Window and/or Cell Scripts (.py files with #%% markers)

What happened?

"Create: New Jupyter Notebook"
Enter print('hello world') in a cell and run it. Select an environment with a modern Jupyter kernel when prompted
Notice no debugging options show up (the RBL button for example) 🐛
Switch to a different tab and back to the notebook again
Now the debugging options show up

VS Code Version
1.74.0-insiders
Jupyter Extension Version
v2022.11.1003371924
Jupyter logs
No response
Coding Language and Runtime Version
No response
Language Extension Version (if applicable)
No response
Anaconda Version (if applicable)
No response
Running Jupyter locally or remotely?
Local

https://github.com/microsoft/vscode-jupyter/issues/6898


example.py does not run well and what is the time format of last_update

The recovered does not exist in one and the country by id not exist in the others.  Hence the example.py does not run well.  My possible solution below.
Still what is the time format of the field " 'last_update':<PHONE_NUMBER>000 "? Not sure how to resolve this.

See attachment
example_covid.txt

For the time part I think the last 3 000 is extra (not sure how it is being generated)
`
timestamp = date.fromtimestamp(1678454462) #000)
print(timestamp) # 2023-03-10
date_time = datetime.fromtimestamp(1678454462) #000)
print("Datetime from timestamp:", date_time) # 2023-03-10 21:21:02
print("This align with the message - This repository has been archived by the owner on Mar 10, 2023. It is now read-only. -")
`

Sorry for the delay, I will investigate

@kwccoin: Which source are you using? John Hopkings or worldometers?

It is John Hopkings, yes it should be archived


[Frontend][Torch] Fix up graph input handling

Thanks for contributing to TVM!   Please refer to guideline https://tvm.apache.org/docs/contribute/ for useful information and tips. After the pull request is submitted, please request code reviews from Reviewers by @ them in the pull request thread.
From: https://discuss.tvm.ai/t/pytorch-frontend-graph-input-names-can-change-using-loaded-torchscript/6055
Split as two commits to make it easier to review:

Simplify operator input handling

remove outputs and output_index_map and extend use of input_vars

Allow user supplied input names to override graph inputs

PyTorch inputs now expected as list rather than dictionary - [(name, shape), (name, shape)...]
Input names given with from_pytorch() are now set as the graph input names and should be used in set_input()

Review request: @masahi

@jjohnson-arm need to update the tutorial too.

please update the doc here https://github.com/apache/incubator-tvm/blob/e722301a1c8be3c7052273961b8a408ca5524c76/python/tvm/relay/frontend/pytorch.py#L1434-L1436
We should warn that this names need be around until deployment time. Our suggestion is to choose something obvious, that doesn't require remembering. Something like "input0", "input1" etc

I still like to retain the original meaning of input_vars, because this is really relay.Var and represents values that come from outside. outputs is for storing intermediate outputs from preceding relay ops.
I think you can simply replace input_vars with outputs and also inputs with outputs everywhere except a few places.

cc @alexwong @jwfromm @pyjhzwh This is a API change and will break your code, but for a good reason. See the discussion above.

Update the tutorial
Update the doc
Remove _update_inputs_from_pairs and use Dict's update method directly everywhere
Minor code style change (for loop)
input_vars -> outputs and inputs -> outputs.

Ok - will do. I wasn't sure about the inputs rename, happy to change it back.

@jjohnson-arm need to update the tutorial too.
Will look at this now.

@jjohnson-arm Unfortunately, you've just hit a known flaky test failure. Please comment out the get_valid_count test. See https://github.com/apache/incubator-tvm/pull/4901#issuecomment-595040094
Also have you verified that torch frontend tests work with this PR? I'm not sure some of the usage of update() method is supported.

@jjohnson-arm Unfortunately, you've just hit a known flaky test failure. Please comment out the get_valid_count test. See #4901 (comment)
Also have you verified that torch frontend tests work with this PR? I'm not sure some of the usage of update() method is supported.

Will comment out the test.
I have been runnning the tests/python/frontend/pytorch/test_forward.py tests for all my changes, and it works fine (using Python 3.6.10). Seems that python from 3.5 has supported tuples etc - https://docs.python.org/3.5/library/stdtypes.html?highlight=update#dict.update, so should be okay?

ok good to know. I was thinking the arg of update should be dict.

Thanks @jjohnson-arm this is merged!


Using ngSemantic with Webpack

Hi,
I am using the angular2 webpack in my project. Besides using npm install for this library, how do i setup ngSemantic for webpack?

Install both semanticui and ngsemantic from npm:
npm install semantic-ui --save
npm install ng-semantic --save
Assuming you installed semanticui in root folder of you project (which is default), then you need to include semanticui assets from dist folder within your main.ts (src/main.ts) angular2 file:
import '../semantic/dist/semantic.css';
import '../semantic/dist/semantic.js';

After that you use it in ng2 app like described in readme https://github.com/vladotesanovic/ngSemantic#use

Hey i did all that, but presently it is showing me this error
ERROR in ./~/ng-semantic/ng-semantic/popup/popup.js
Module not found: Error: Cannot resolve module 'null-loader' in C:\Users\gemini
Desktop\angular2-dashboard\node_modules\ng-semantic\ng-semantic\popup
@ ./~/ng-semantic/ng-semantic/popup/popup.js 1:0-17
ERROR in ./~/ng-semantic/ng-semantic/modal/modal.js
Module not found: Error: Cannot resolve module 'null-loader' in C:\Users\gemini
Desktop\angular2-dashboard\node_modules\ng-semantic\ng-semantic\modal
@ ./~/ng-semantic/ng-semantic/modal/modal.js 1:0-17
ERROR in ./~/ng-semantic/ng-semantic/visibility/visibility.js
Module not found: Error: Cannot resolve module 'null-loader' in C:\Users\gemini
Desktop\angular2-dashboard\node_modules\ng-semantic\ng-semantic\visibility
@ ./~/ng-semantic/ng-semantic/visibility/visibility.js 1:0-17
ERROR in ./~/ng-semantic/ng-semantic/dropdown/dropdown.js
Module not found: Error: Cannot resolve module 'null-loader' in C:\Users\gemini
Desktop\angular2-dashboard\node_modules\ng-semantic\ng-semantic\dropdown
@ ./~/ng-semantic/ng-semantic/dropdown/dropdown.js 1:0-17
ERROR in ./~/ng-semantic/ng-semantic/select/select.js
Module not found: Error: Cannot resolve module 'null-loader' in C:\Users\gemini
Desktop\angular2-dashboard\node_modules\ng-semantic\ng-semantic\select
@ ./~/ng-semantic/ng-semantic/select/select.js 1:0-17
ERROR in ./~/ng-semantic/ng-semantic/input/input.js
Module not found: Error: Cannot resolve module 'null-loader' in C:\Users\gemini
Desktop\angular2-dashboard\node_modules\ng-semantic\ng-semantic\input
@ ./~/ng-semantic/ng-semantic/input/input.js 1:0-17
ERROR in ./~/ng-semantic/ng-semantic/sidebar/sidebar.js
Module not found: Error: Cannot resolve module 'null-loader' in C:\Users\gemini
Desktop\angular2-dashboard\node_modules\ng-semantic\ng-semantic\sidebar
@ ./~/ng-semantic/ng-semantic/sidebar/sidebar.js 1:0-17
ERROR in ./~/ng-semantic/ng-semantic/tab/tab.js
Module not found: Error: Cannot resolve module 'null-loader' in C:\Users\gemini
Desktop\angular2-dashboard\node_modules\ng-semantic\ng-semantic\tab
@ ./~/ng-semantic/ng-semantic/tab/tab.js 1:0-17
ERROR in ./~/ng-semantic/ng-semantic/dimmer/dimmer.js
Module not found: Error: Cannot resolve module 'null-loader' in C:\Users\gemini
Desktop\angular2-dashboard\node_modules\ng-semantic\ng-semantic\dimmer
@ ./~/ng-semantic/ng-semantic/dimmer/dimmer.js 1:0-17
ERROR in ./~/ng-semantic/ng-semantic/accordion/accordion.js
Module not found: Error: Cannot resolve module 'null-loader' in C:\Users\gemini
Desktop\angular2-dashboard\node_modules\ng-semantic\ng-semantic\accordion
@ ./~/ng-semantic/ng-semantic/accordion/accordion.js 1:0-17
ERROR in ./~/ng-semantic/ng-semantic/rating/rating.js
Module not found: Error: Cannot resolve module 'null-loader' in C:\Users\gemini
Desktop\angular2-dashboard\node_modules\ng-semantic\ng-semantic\rating
@ ./~/ng-semantic/ng-semantic/rating/rating.js 1:0-17

Are you using that 'null-loader' loader in your webpack config? (I dont even have it installed in my setup)

Yes I am using it as I have jQuery installed directly with npm & typings
On 18 Aug 2016 14:29, "Daniel Zolnjan"<EMAIL_ADDRESS>wrote:

Are you using that 'null-loader' loader in your webpack config? (I dont
even have it installed in my setup)
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/vladotesanovic/ngSemantic/issues/49#issuecomment-240664628,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AQo6KGXkj9bMDXlMCS3PyoNkEpxir0dmks5qhB7zgaJpZM4JnPSv
.

If its just for jquery you can remove null-loader and import jquery using the ProvidePlugin (standard jquery import setup)
new webpack.ProvidePlugin({ $: 'jquery', jQuery: 'jquery' })

Hey, I have removed the null loader for jQuery but now they are asking to use a loader for the semantic.css wince there are things like @import etc.
Could you please tell me what would be the appropriate loader for this css file?

Presently after doing all the steps above mentioned I am getting this: Uncaught TypeError: core_1.NgModule is not a function
For ng-semantic.js :
NgSemanticModule = __decorate([
core_1.NgModule({
declarations: [exports.SEMANTIC_DIRECTIVES, exports.SEMANTIC_COMPONENTS],
exports: [exports.SEMANTIC_COMPONENTS, exports.SEMANTIC_DIRECTIVES],
imports: [common_1.CommonModule, forms_1.FormsModule, forms_1.ReactiveFormsModule]
}),
__metadata('design:paramtypes', [])
], NgSemanticModule);
return NgSemanticModule;

Hey,
Last night i updated everything on Angular RC.5...
There is no backward compitability so you will need to update your app too.
On 19 Aug 2016 11:59, "Beck Technology"<EMAIL_ADDRESS>wrote:

Presently after doing all the steps above mentioned I am getting this:
Uncaught TypeError: core_1.NgModule is not a function
For ng-semantic.js :
NgSemanticModule = __decorate([
core_1.NgModule({
declarations: [exports.SEMANTIC_DIRECTIVES, exports.SEMANTIC_COMPONENTS],
exports: [exports.SEMANTIC_COMPONENTS, exports.SEMANTIC_DIRECTIVES],
imports: [common_1.CommonModule, forms_1.FormsModule,
forms_1.ReactiveFormsModule]
}),
__metadata('design:paramtypes', [])
], NgSemanticModule);
return NgSemanticModule;
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/vladotesanovic/ngSemantic/issues/49#issuecomment-240978460,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAtFTmq9WX40XMDgW3QgeIwjr9GNL33kks5qhX5pgaJpZM4JnPSv
.

Could you please add how to install ngSemantic in webpack to readme. Angular CLI has switched to webpack and I am not getting ngSemantic to work any more.

Oh, things are changing to fast :)
I will update my README for webpack configuration.
Best regards!
Check it out: www.pinmap.io http://www.pinmap.io
On 19 August 2016 at 15:53, papoola<EMAIL_ADDRESS>wrote:

Could you please add how to install ngSemantic in webpack to readme.
Angular CLI has switched to webpack and I am not getting ngSemantic to work
any more.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/vladotesanovic/ngSemantic/issues/49#issuecomment-241024292,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAtFTpgUFTdD6OHgZMhF2IcdqeDhJNEVks5qhbVVgaJpZM4JnPSv
.

@papoola
Repository generated by Angular CLI with ngSemantic included
https://github.com/vladotesanovic/angular2-cli-webpack
// @ToDO
I need to find proper way to load semantic.min.css here....

Thank you @vladotesanovic ! I will check it out tonight. In the mean time you might wanna check https://github.com/angular/angular-cli/pull/1747 once this has been merged it will make importing libraries JS and CSS much easier

Yep, i saw that.
Repository is just proof, i will try to improve it. If you find anything
where you can contribute, please feel free to do that.
Best regards!
Check it out: www.pinmap.io http://www.pinmap.io
On 21 August 2016 at 19:45, papoola<EMAIL_ADDRESS>wrote:

Thank you @vladotesanovic https://github.com/vladotesanovic ! I will
check it out tonight. In the mean time you might wanna check
angular/angular-cli#1747
https://github.com/angular/angular-cli/pull/1747 once this has been
merged it will make importing libraries JS and CSS much easier
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/vladotesanovic/ngSemantic/issues/49#issuecomment-241271090,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAtFTib38D3r8lYFr3i1yeMSR3-y_8KSks5qiI63gaJpZM4JnPSv
.


Status of node  node-red-contrib-eq3-bluetooth is still "connected" when it becomes disconnected.

I have noticed using btmon that after 90 sec of inactivity the BLE connection automatically disconnects but this is not reported in the node status.  (it remains in status connected).
> HCI Event: Disconnect Complete (0x05) plen 4                                                                                #60 [hci0] 218.531131
        Status: Success (0x00)
        Handle: 64
        Reason: Connection Terminated By Local Host (0x16)
@ MGMT Event: Device Disconnected (0x000c) plen 8                                                                                {0x0004} [hci0] 218.531197
        LE Address: 00:1A:22:0F:07:67 (eQ-3 Entwicklung GmbH)
        Reason: Connection terminated by local host (0x02)
@ MGMT Event: Device Disconnected (0x000c) plen 8                                                                                {0x0002} [hci0] 218.531197
        LE Address: 00:1A:22:0F:07:67 (eQ-3 Entwicklung GmbH)
        Reason: Connection terminated by local host (0x02)
@ MGMT Event: Device Disconnected (0x000c) plen 8                                                                                {0x0001} [hci0] 218.531197
        LE Address: 00:1A:22:0F:07:67 (eQ-3 Entwicklung GmbH)
        Reason: Connection terminated by local host (0x02)

I have updated the status so that it also reports when the node is no longer connected.


feat(cluster): initial commit for scale-out cluster

What type of PR is this?

Which issue does this PR fix:
What does this PR do / Why do we need it:
If an issue # is not available please add repro steps and logs showing the issue:
Testing done on this change:

Automation added to e2e:

Will this break upgrades or downgrades?
Does this PR introduce any user-facing change?:

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

Proposal:

Single nodes have an upper limit on CPU, memory and storage. So eventually, have to grow out of single nodes.
Repository "name" based static routing.
Each node either can handle the request locally, or must route.
HTTP redirect based (3xx) or proxy?
Choose proxy in 4. since not clear if clients handle 3xx, however, there is an extra cost in proxy/networking.
But nice in the sense that we can expose all nodes via DNS or a stateless ingress can hide and spray to these nodes.
The cluster size can grow or shrink, which means the new lookup may not find data locally.
However, since content-based lookups, we can add the other nodes as an implicit "sync" rule for a particular "name". If the data is not found locally, "sync" will get it from other members, so the cluster re-balances over time.

previously i have worked with seaweedfs, which allows for side-adjustable clusters with discovery similar to how you describe. they use raft for this: https://github.com/seaweedfs/seaweedfs/blob/master/weed/server/raft_server.go
that said, what is the rationale to implement your own cluster system? i feel like this is something better solved separately, since as a user i would probably feel more comfortable using zot on top of redis/ceph instead of making zot do the replication/sharding.

Let's close this, as https://github.com/project-zot/zot/pull/2385 accomplishes what this PR was supposed to.


Tank issues

Fuel tank foes inside walls
Water tank is broken

I fixed the water tank issue.

Closing in favor of #967

These are completely unrelated issues.

Adding to this: water tanks have item components, so you can pick them up.


Scroll on sponsors page.

On the sponsors page when fully zoomed out, the side scroll option is still availible.

fixed in 05d11bb70e94d77757ade6ad33b1c051256866bf


[5.9] Disfavor default implementations and synthesized symbols in link collisions

Explanation: Avoid need for some link disambiguation by deprioritizing synthesized symbols and default implementations in link collisions.
Scope: Symbol link disambiguation.
Issue: rdar://98781530
Risk: Low. Existing links with disambiguation continue to work the same as before. New links can avoid disambiguation.
Testing: Updated test assertions verify that link collisions with deprioritized symbols can omit disambiguation.
Original PR: #540
Reviewers: @QuietMisdreavus

@swift-ci please test

@swift-ci please test

@swift-ci please test


This may fix #2616

Index.html is generated incorrectly if System.Text.Json's default serializer options are changed, e.g. if WriteIndented is true and DefaultIgnoreCondition is JsonIgnoreCondition.Never, it produces the following text inside index.html:
var interceptors = JSON.parse('{
  "requestInterceptorFunction": null,
  "responseInterceptorFunction": null
}');

... which will generate index.html:100 Uncaught SyntaxError: Invalid or unexpected token error and show blank document in the browser.

Hey guys! It seems like appveyor tests fail because .NET 6 is not installed. I didn't work with appveyor before. How this can be fixed?

Thanks for contributing - if you'd like to continue with this pull request, please rebase against the default branch to pick up our new CI. Could you also add a test for this scenario?


Parsing an Expr fails with embedded macros in expression position

As in the title, let expr: Expr = input.parse()?; fails on content containing a macro.
I'm not actually sure whether this should be supported, though it works for declarative macros.
Related: https://github.com/rust-lang/rust/issues/54727 (procedural macros can't currently be used in expression position; though declarative macros can be).

You may need to enable the "full" feature if you are parsing expressions: https://github.com/dtolnay/syn#optional-features. By default we only parse the basic subset of expressions that typically appear as array lengths.
For procedural macros in expression position check out https://github.com/dtolnay/proc-macro-hack.

Oh, was wondering whether I should try that, but didn't think a feature combination would allow only limited parsing. Will do.
Awesome! Thanks for all the hacks around macros. I'm currently using nightly-only and only at the proof-of-concept stage, so just using the nightly feature flag.


Bug: sdk help <subcommand> doesn't work

Bug report
According to the docs:

[...] You can add qualifier to this command to get help about a specific sub-command.
$ sdk help install

In reality, sdk help install just outputs the same thing as sdk help. Either the docs are wrong/outdated or the sdk help command is broken.
System info
SDKMAN! version: 5.18.1
OS: macOS Ventura 13.4
Shell: zsh 5.9

@talbenari-okta It might be helpful if you print what you are seeing.

Either the docs are wrong/outdated, or the sdk help command is broken.

Highly unlikely because all regression tests are passing for all supported platforms.
On my machine, I see the following:
❯ sdk help

NAME
    sdk - The command line interface (CLI) for SDKMAN!

SYNOPSIS
    sdk <subcommand> [candidate] [version]

DESCRIPTION
    SDKMAN! is a tool for managing parallel versions of multiple JVM related
    Software Development Kits on most Unix based systems. It provides a
    convenient Command Line Interface (CLI) and API for installing, switching,
    removing and listing Candidates.

SUBCOMMANDS & QUALIFIERS
    help         [subcommand]
    install      <candidate> [version] [path]
    uninstall    <candidate> <version>
    list         [candidate]
    use          <candidate> <version>
    config       no qualifier
    default      <candidate> [version]
    home         <candidate> <version>
    env          [init|install|clear]
    current      [candidate]
    upgrade      [candidate]
    version      no qualifier
    offline      [enable|disable]
    selfupdate   [force]
    update       no qualifier
    flush        [tmp|metadata|version]

EXAMPLES
    sdk install java 17.0.0-tem
    sdk help install

❯ sdk help install

NAME
    sdk install - sdk subcommand to install a candidate version

SYNOPSIS
    sdk install <candidate> [version] [path]

DESCRIPTION
    Invoking this subcommand with only the candidate as parameter will install
    the currently known default version for that candidate. Provide a second
    qualifier to install a specific non-default version. Provide a third
    optional qualifier to add an already installed local version. This final
    qualifier is the absolute local path to the base directory of the SDK to
    be added. The local version will appear as an installed version of the
    candidate. The version may not conflict with an existing version, installed
    or not.

EXIT CODE
    The subcommand will return a non-zero exit code for versions not found or
    for an invalid path.

MNEMONIC
    i - may be used in place of the install subcommand.

EXAMPLES
    sdk install java
    sdk install java 17.0.0-tem
    sdk install java 11-local /usr/lib/jvm/java-11-openjdk

No response, too little information and can't replicate the issue. Closing this issue.


Event naming inconsistency

In the documentation and constants in Event you have all events in capital letters however when emitting certain events discordPHP has them in lowercase so for example
emitting 'ready'
while listening for Event::READY ('READY') will not function.
Some clearer documentation or use of the above constant(s) needed.

as far as I know @davidcole1340 was planning to make them case insensitive in order to fix that

Isnt DiscordPHP using the Evenement.EventEmitterTrait, That is already case sensitive by use of array keys.

yes, the goal is to make it case INsensitive :P

Event::READY is not actually the same as the 'ready' event, so it will probably be removed. The bot isn't 'ready' until you have received all the guilds, which are sent in GUILD_CREATE events after the READY event, which is when 'ready' is emitted.
But yes, ideally we will change it to be case insensitive in a later update, but due to 'READY' !== 'ready' there will be breaking changes.


Ashton post-processing does not respect Apple Retina displays

Running the ashton examples on my 2012 MacBook Pro Retina, the gosu window is created at four times the size (given 640 x 480, OS X gives gosu a 1280 x 960 viewport), however the Ashton post-processing still draws in the original 640 x 480 window. Below is a screenshot of the bloom example exhibiting this issue:

Is it possible to instruct Ashton to do post-processing over a larger area, or possibly detect the presence of a retina display and adjust accordingly?

I'm guessing that Gosu::Window#height and Gosu::Window#width returns the incorrect size, which is what Ashton uses to create the full-screen buffers it needs to perform post-processing.
See: https://github.com/jlnr/gosu/issues/244


☠  Coda Daemon crashed

2020-12-05 17:59:09 UTC [Faulty_peer] Peer $peer failed to serve requested epoch ledger: "refusing to serve genesis ledger"
peer: {
"host": "<IP_ADDRESS>",
"peer_id": "12D3KooWA4kaMsCeY15mL8L5ZT949SSkDFwPhrBp1kcBHTB6Vyq1",
"libp2p_port": 8302
}
2020-12-05 17:59:09 UTC [Fatal] Unhandled top-level exception: $exn
Generating crash report
exn: {
"string": "failed to synchronize epoch ledger",
"tags": [ { "tag": "Local state sync failed" } ],
"backtrace": [
"Raised at file "src/error.ml" (inlined), line 9, characters 14-30",
"Called from file "src/lib/transition_router/transition_router.ml", line 350, characters 18-75",
"Called from file "src/deferred1.ml", line 17, characters 40-45",
"Called from file "src/job_queue.ml" (inlined), line 131, characters 2-5",
"Called from file "src/job_queue.ml", line 171, characters 6-47"
]
}
coda_crash_report_2020-12-05_17-59-09.071145.tar.gz

This is failed to synchronize epoch ledger which is https://github.com/MinaProtocol/mina/issues/6952 and resolved by https://github.com/MinaProtocol/mina/pull/6959

This was fixed in #6959. Closing.


Taxonomypicker - support for term suggestions based on containing

Added support for something that people have been asking me for when using SharePoints own taxonomypicker - being able to find things on terms not only starting by, but also containing. The problem is that users don't always know exactly the term they are looking for and sometimes have a  hard time finding the correct term. This can result in "duplicate" terms because users create new ones instead of using the existing ones.
Thanks @pbjorklund for fixing my git issues!

Hi @jansenbe - I already signed a cla once but maybe I need to sign a new one since I am in new company since I signed the last one? Didn't receive any form to sign yet in any case...

Hi Henrik,
you should have received an email with electronic form to sign for. Company change does impact on this one. You can also access the CLA signing just by using following url: https://cla.microsoft.com. When the form has been submitted, status of this PR will change automatically.

Thanks Vesa, went with the direct link and signed it.

Excellent. We'll have a look at this PR.

Nice work :-) Merged.


Stateless components cannot be arrow functions

A bug in isFunctionalComponent is causing an error to be thrown when passing an arrow function as a stateless component. This is because arrow functions doesn't have a prototype, which is used in this function.
Compare these two identity functions:

This is the very simple app that I'm using together with browserify:
const { h, render } = require('preact')

const App = (props) =>
  h('h1', null, 'Hello World')

render(h(App), document.body)

Note that I'm not using babel here. This works when using babel because it converts the arrow functions to normal functions.

Ah, very good catch. Should be a quick fix.

Thanks for the quick fix, if you could publish a patch release right away I would be so happy! 🎉

@LinusU yes sorry - meant to publish but I had to step out for a sec. Will publish in ~20 minutes. Cheers!

By the way, not sure if it helps but I've been publishing alphas here: https://gist.github.com/developit/75e724607fe33de9e63f
For larger changes I generally publish a beta dist-tag to NPM.

Nice! 🙌
I'm using npm so it might be a bit tedious to include the gist...

For sure, yup.

Released as 4.6.1. Thanks!

Thank you!


Change elasticsearch indices

I'm trying to make the APM indicies less frequent. I've tried looking for some settings, but unable to find any. I've also tried to send the APM logs through my Logstash, but I can't seem to make it work. Is there support for either of these options? If so, any documentation?

@JonasKs please open a topic in the Discuss forum: https://discuss.elastic.co/c/apm. GitHub issues are meant for reporting bugs or previously-discussed feature requests. Thanks!

Sure, cheers!