draggableRange allows to drag into restricted regions

Steps to reproduce

Have a slider with a restricted region and draggableRange set to true
Drag the slider bar

Demo: http://jsfiddle.net/xk5tmq64/
Expected behaviour
You can't drag in the restricted region
Actual behaviour
You can drag into the restricted region, ending up with invalid values.

you could detect when user stopped using the UI event, then evaluate if any of the two values is inside the forbidden area, and whether the first can be at the lowest in range, else move it to the highest and do the same with the second value.
it must be solved from the library, but this way you can work while it gets solved.

I've missed this issue 3 months ago. Indeed this should be pretty simple to handle this as part of the library. This behavior is actually a bug.
However, I'll probably won't have the time to implement a fix. I could provide some guidance if someone wants to submit a PR though 🙂


Target_Encounter Dangling References in Wiki

Although target_encounter has been removed from many of the states, some of their examples still show the field:

MedicationOrder
CarePlanStart

Updated the wiki and the example module. See: https://github.com/synthetichealth/synthea/commit/2519bd13dc6fe2bd4c953b939b567288c1f28709


Provide MP config profile support for application.yaml (#5565)

Change includes the following:

Create a new interface MpConfigSourceProvider that extends ConfigSourceProvider and adds profile support.
Use MpConfigSourceProviderWithProfile as the provider for Java Service Loader when processing application.yaml.
Added unit tests to exercise setting of mp.config.profile using system property or config source.

Will resolve backport request https://github.com/helidon-io/helidon/issues/5583


avoid assigning to function parameters

Assigning to function parameters should be avoided. Two occurences of this can be found in KYBER.NETWORK,
specifically in the ConversionRates contract:
• In the recordImbalance function, the argument rateUpdateBlock is written to.
• In the getRate function the unsigned integer qty is overwritten.

Fixed in https://github.com/KyberNetwork/smart-contracts/pull/422


Restic repository corrupted with error: ciphertext verification failed

Output of restic version
restic 0.16.4
What backend/service did you use to store the repository?
Mongodb, postgresql, zookeeper and Schema Registry dump
Problem description / Steps to reproduce
We are facing issue with restic backup wherein we 2 of our repositories have been corrupted leading us to not have backup and also we are not able to access existing snapshots.
This is not reproducible and we ourselves are facing this issue with 2 of our backup jobs mongodb backup and schema registry backup.
We are using gcs bucket as our repository and running restic as a kubernetes cronjobs.
Exception:
open repository
lock repository
load index files
ciphertext verification failed
github.com/restic/restic/internal/crypto.init
	/restic/internal/crypto/crypto.go:30
runtime.doInit1
	/usr/local/go/src/runtime/proc.go:6740
runtime.doInit
	/usr/local/go/src/runtime/proc.go:6707
runtime.main
	/usr/local/go/src/runtime/proc.go:249
runtime.goexit
	/usr/local/go/src/runtime/asm_amd64.s:1650

Steps tried to recover:

restic snapshots ls -r
Ignoring "<id>": failed to load snapshot <id>: ciphertext verification failed
Ignoring "<id>": failed to load snapshot <id>: ciphertext verification failed
Ignoring "<id>": failed to load snapshot <id>: ciphertext verification failed
Ignoring "<id>": failed to load snapshot <id>: ciphertext verification failed
Ignoring "<id>": failed to load snapshot <id>: ciphertext verification failed
Ignoring "<id>": failed to load snapshot <id>: ciphertext verification failed
Ignoring "<id>": failed to load snapshot <id>: ciphertext verification failed

restic unlock --remove-all -r gs:<gcs-bucket-name>:/<foldername>/schema-registry
enter password for repository:
repository 7400edb4 opened (version 2, compression level auto)

╰─ restic check --read-data -r gs:<gcs-bucket-name>:/<foldername>/schema-registry
using temporary cache in /var/folders/l2/<id>/T/restic-check-cache-<>
enter password for repository:
repository <repo> opened (version 2, compression level auto)
created new cache in /var/folders/l2/<indexId>/T/restic-check-cach<id>
create exclusive lock for repository
load indexes
[0:44] 100.00%  463 / 463 index files loaded
error: error loading index <indexId>: ciphertext verification failed
error: error loading index <indexId>: ciphertext verification failed
error: error loading index <indexId>: ciphertext verification failed
....
....
Fatal: LoadIndex returned errors

Tried:
restic repair index --read-all-packs -r gs:<gcs-bucket-name>:/<foldername>/schema-registry

Command worked but still was not able to get restic snapshots list or push a new snapshot

Documentation and Issues Checked:
https://restic.readthedocs.io/en/latest/077_troubleshooting.html#find-out-what-is-damaged
https://forum.restic.net/t/help-with-fatal-load-index-invalid-data-returned/4147/2
https://github.com/restic/restic/issues/4168
Expected behavior
Restic should not get corrupted and we should be able to access existing snapshots and take new snapshots
Actual behavior
Currently restic is blocked and we are not able to take backup
Do you have any idea what may have caused this?
Went through docs and older issues not able to investigate the issue as the same thing work for other backups
Please help and we are not able to build confidence into using this in production

When were the config file and any file in the keys folder of the repository last modified? Were there any errors right before the errors started to show up? Did the automation for some reason call the init command of restic?
The errors look like the used key file does not match the key used to encrypt the repository content. That is somewhat similar to https://github.com/restic/restic/issues/4832 , but you're using the GCS backend so there could be a separate problem.

We had initialized the repo on 27th May 2024 for rest of our backups out of postgresql, zookeeper, schema-registry, mongodb i see that the key was changed for mongodb and schema-registry back up on  Jun 3, 2024
We use below code to check if we want to initialize the backup or not
                  # Init the backup Dir
                  {{- if .Values.restic.enabled}}
                  if restic snapshots >/dev/null 2>&1; then
                  echo "restic repo exists"
                  else
                  restic init
                  fi
                  {{- else }}
                  mkdir -p {{.Values.defaultBackupDir}}
                  {{- end}}

We have one job calling one gcs bucket path so there is no way any other job would initialise the repo or use it.
I also tried to restore by using repair index and unlock option but no luck

if restic snapshots >/dev/null 2>&1; then

That logic is unreliable as it cannot distinguish between a non-existent repository and problems with the backend communication. But even in the latter case, restic init wouldn't reinitialize a repository, unless the backend claimed that it does not contain a config file. Do you have the output generated by the init command runs on Jun 3, 2024?

i see that the key was changed

What exactly do you mean with that? Initializing a repository a second time generates a second key in the keys folder, but does not modify the old one.

I also tried to restore by using repair index and unlock option but no luck

This cannot work as the used key no longer matches the key used to encrypt the older data.
Does the old key files still exist and are you able to retrieve an old copy of the config file? If yes, then you can repair the repository by reverting the config file and removing the new key file.
If you only have the old key file, then it would be possible to create a new fake config file that allows accessing the data in the backup again. However, deduplication would likely suffer in future snapshots. Creating a fake config file require some experimental code, so I'd only recommend going down that road if really necessary.
If you do not have the old key file, then the repository is permanently inaccessible.

Thanks for your reply!
Unfortunately i didn't had log for the job I mentioned above but there was same job in another env which started failing today. I saw that new key was generated.
+ set -e
+ cd /tmp
+ suffix=<>
+ postgresDir=postgresql-backup
+ restic snapshots
+ restic init
created restic repository <> at gs:<bucket>:/<folder>

Please note that knowledge of your password is required to access
the repository. Losing your password means that your data is
irrecoverably lost.
+ echo ''
+ echo 'running postgresql dump'

running postgresql dump
+ pg_dump -h postgresql -U postgres -F c -b -v -f  <>  <>
<pg_dump details.........removed these lines.......>
+ rm -rf postgresql-backup.tgz
+ doBackup postgresql-backup.tgz
+ bkpFile=postgresql-backup.tgz
+ cat postgresql-backup.tgz
+ restic --verbose backup --stdin --stdin-filename postgresql-backup.tgz -g paths
open repository
lock repository
load index files
ciphertext verification failed
github.com/restic/restic/internal/crypto.init
	/restic/internal/crypto/crypto.go:30
runtime.doInit1
	/usr/local/go/src/runtime/proc.go:6740
runtime.doInit
	/usr/local/go/src/runtime/proc.go:6707
runtime.main
	/usr/local/go/src/runtime/proc.go:249
runtime.goexit
	/usr/local/go/src/runtime/asm_amd64.s:1650
+ finish

No we don't have older config/key. Also one of the reason i see this being a issue is below:

But not quite sure as I see that restic key is replaced and a new key is added so if I am not wrong it reinitialised it but then in the end not sure why we ended up with ciphertext verification failed error
Can you recommend another command to verify existence of the repository instead of listing snapshots ?

No we don't have older config/key. Also one of the reason i see this being a issue is below:

That lifecycle rule is the reason for the broken repositories. The config and keys files are only created when initializing a repository and do not change over the lifetime of a repository (unless you explicitly tell restic to modify the keys / upgrade the repo format).
You must remove the lifecycle rule; it's effectively deleting random files from the repository, no wonder that it is broken. After that you'll have to create new repositories.

a new key is added so if I am not wrong it reinitialised it but then in the end not sure why we ended up with ciphertext verification failed error

The password that you pass to restic is used to decrypt the key file, which contains the actual master password used to encrypt data. Initializing a repository a second time will result in a new master password, which cannot decrypt already existing data.

Can you recommend another command to verify existence of the repository instead of listing snapshots ?

There's currently no perfectly well suited command, but take a look at https://restic.readthedocs.io/en/stable/075_scripting.html#check-if-a-repository-is-already-initialized .
The init command already includes a check that there's not yet a repository, which makes that above construction safe enough.


tests: fix ChangingDirectoryTests: cd back in tearDown

Ref: https://github.com/pytest-dev/pytest-django/issues/637#issuecomment-414372207

Coverage remained the same at ?% when pulling 53d605f851190f0c3ca3f606fea5fa0f04f402a3 on blueyed:fix-ChangingDirectoryTests into d843ca8b53517f4c6919d3b9469d827c91a16019 on django-extensions:master.

Coverage remained the same at ?% when pulling 53d605f851190f0c3ca3f606fea5fa0f04f402a3 on blueyed:fix-ChangingDirectoryTests into d843ca8b53517f4c6919d3b9469d827c91a16019 on django-extensions:master.

Coverage remained the same at ?% when pulling 53d605f851190f0c3ca3f606fea5fa0f04f402a3 on blueyed:fix-ChangingDirectoryTests into d843ca8b53517f4c6919d3b9469d827c91a16019 on django-extensions:master.

Reduces failures to "3 failed, 231 passed, 2 skipped, 1 warnings".

Thanks !


Fix containers and rename namespace

Description of the problem

Some containers defined in the data containers of the DEM where not used everywhere
Some maps were remaining that needed to be refactored
I don't think it is a good idea to have a seperate namespace for the container, moved them to the DEM namespace

Description of the solution

Fixed the container usage
Renamed the namespace to DEM

How Has This Been Tested?

All tests pass so this is good to go.

Everything should be fixed now back with map for the forces. I'll merge once CI passes @acdaigneault. It's really a partial cleanup, more will need to be done, but I'll get back into it.


Estimate Aruco pose relative to camera.

This description is also in the commit's comment.
The initial goal of this branch was to ensure that the estimator outputs the pose of the marker relative to the camera. The ArUco tutorial seems to say that the function cv::aruco::estimatePoseSingleMarkers estimates the pose of the camera relative to the marker. However, the documentation for the function says that the function estimates the pose of the marker relative to the camera. Personal experimentation verifies that the function estimates the pose of the marker relative to the camera.
To ensure a specific default behavior, I added estimation parameters to estimatePoseSingleMarkers function in ArucoMarkerEstimator.


Fix Intellij Bazel Plugin support for scrooge_scala_library rule

Overview
This fixes intelliJ support for scrooge_scala_library targets using the new aspect based implementation (#524). Without this fix, symbol resolution and jump-to-def support does not work.
Previously, the scrooge_scala_library rule would return a scala field on its provider struct, which contained output jars (full path: scala -> outputs -> [].jars -> class_jar). This IJ plugin would inspect this field and collect the jars for IDE support.
The new scrooge_scala_library does not return a scala field, breaking IJ support. It does return a JavaInfo provider, which the IJ plugin does pick up, but it lacks an outputs field. One seemingly straightforward solution would be to simply set the outputs field on the existing JavaInfo provider. There are two reasons this doesn't work:

There is at least one place several JavaInfos need to be merged together, and the current implementation of java_common.merge strips the outputs field. There is a fix forthcoming for this, but it's not landing until 0.16.0.
There is no way AFAIK for setting multiple output_jars on a JavaInfo. The JavaInfo constructor only accepts one output jar and java_common.create_provider doesn't set the outputs field at all.

The solution in this PR threads the output jars through and puts them in the scala field that the IJ plugin expects. Concretely, this means using the JavaInfo constructor to set output_jar explicitly, and going back to old style providers, where the rule implementation returns a struct rather than a list of providers.
I believe this is an acceptable fix because once the java_common.merge fix is released in 0.16.0, the scala field can be removed in favor of putting the jars JavaInfos outputs, and we can go back to new-style providers (returning a list rather than a struct).
Testing
Tests pass (./test_all.sh) and I've verified the fix works with the IJ plugin on our repos at Stripe.
That said, this is my first bazel rules PR and would appreciate extra scrutiny, in particular in making sure I've constructed all the JavaInfos correctly.

@johnynek: A splendid idea: https://github.com/bazelbuild/intellij/pull/366

Regarding exports, my thinking is: for schemas, all dependencies should are things that show up on the API: if schema foo depends on schema bar, the user of foo is going to need bar to use foo, pretty much 100% of the time. Requiring explicit dependencies, seems like just adding more toil.
Secondly: the motivation for thin dependencies is so you can avoid recomputation, but when a schema changes, almost always the API changes, so you don't get to avoid a recomputation, so the motivation from a caching perspective also disappears.
So, that's why I put the transitive dependencies into exports.


Bad indetation

Hi,
i just copied code from SAP to Atom and this is what i get (i think it's a bug):

try coping the code into a SAP system, and execute the pretty printer with indentation enabled
usually the code for each event is indented with 2 spaces:
START-OF-SELECTION.
  PERFORM run.

* Hide Execute button from screen
AT SELECTION-SCREEN OUTPUT.
  PERFORM output.

* SAP back command re-direction
AT SELECTION-SCREEN ON EXIT-COMMAND.
  PERFORM exit.

You are right, But still SAP don't mind that you have no spaces before PERFORM (you can execute it without any error) so neither should Atom. So it would be nice to have settings in your plugin to enable/disable checking for spaces (even those on the end of lines).  But that's just suggestion, thanks for great plugin!

abaplint will complain about a lot of ABAP code that syntax-checks in SAP, that is the idea.
There are many opinions on what is good or bad ABAP code, so I'm aiming to have all the checks configurable :o)

I'm just testing Atom so i'm using copy and paste from Atom to SE38 and the other way round. In SE38 i hit check and then pretty printer, so all the things i don't care about when writing code (like those spaces) will fix themselves :)

yea, first step is detecting the issues, then later I'd also like to implement some auto-correction possibilities like eslint.org have
Btw, I dont update the Atom package very often. But I'm working on http://larshp.github.io/abaplint/ it might be updated a bit more often

btw, you might also want to take a look at https://github.com/larshp/abapOpenChecks it many of the same checks as abaplint plus a lot more. And it runs inside the SAP system via code inspector/ATC. All checks are configurable


Standardize connection string for simple connections

Problem
Connection strings come in many different formats. This lack of standardization can make it confusing for newcomers to understand how to connect to their database.
To give you a flavor of the various connection strings out in the wild:

jdbc:sqlserver://localhost:1433\MY_INSTANCE
mssql://username:password@localhost:1433/database?encrypt=true
Server=localhost,1433;Database=database;User Id=username;Password=password;Encrypt=true Driver=msnodesqlv8;Server(local)\INSTANCE;Database=database;UID=DOMAIN\username;PWD=password;Encrypt=true

If you're lucky, your database host  provides you a connection string that you can copy and paste into your database client, but this isn't always the case.
Suggested solution
I think that the URL format is the most familiar format and a good default for basic use cases.
schema://username:password@hostname:port/database_name?key=value

For Microsoft SQL Server that could look like this:
mssql://username:password@localhost:1433/database?encrypt=true

The URL format shouldn't be the only supported format. It would just be our 1 common format across datasources. If a popular database host provides a copy-pasteable connection string that is not a URL, we should also handle that.
Additionally, sometimes it's unreasonable to enforce a standard URL format, especially when we start talking about replicas across hosts. For example, this isn't a valid URL and that's okay:
mongodb://mongodb0.example.com:27017,mongodb1.example.com:27017,mongodb2.example.com:27017/?replicaSet=myRepl

So perhaps we could have a list of different connection string parsers to try for a given datasource, so for MSSQL, you could have 3 connection string parsers:

jdbc:sqlserver://localhost:1433\MY_INSTANCE
mssql://username:password@localhost:1433/database?encrypt=true
Server=localhost,1433;Database=database;User Id=username;Password=password;Encrypt=true Driver=msnodesqlv8;Server(local)\INSTANCE;Database=database;UID=DOMAIN\username;PWD=password;Encrypt=true

I think it would be nice is if we at least support the (2) format for all of our datasources. Then for the advanced use-cases like (1) and (3), it's datasource-specific.
I'm mostly thinking about this from a user-perspective, less about the tradeoffs. Being consistent for the simple cases would probably be helpful.

We'd be the first ones using mssql in the string. The correct version is always sqlserver!

Edited, thanks.

We have moved away from inventing our own things, and just make it work with what is common. There is little value in us adding the overhead of mapping and parsing these formats in our own.
So we will not look further into this.


Update CSP for CodeEditor

Issue #, if available:
Description of changes:
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Can you verify how you tested the change in the PR description

Build output:
======== Cleaning out patches ========
No patch removed

======== Delete data in vs code module if present ========
rm: "." and ".." may not be removed

======== Updating submodule ========
Submodule 'vscode' (https://github.com/microsoft/vscode.git) registered for path 'vscode'
Cloning into '/Users/goelakas/git-workspace/sagemaker-code-editor/vscode'...
Submodule path 'vscode': checked out 'f1b07bd25dfad64b0167beb15359ae573aecd2cc'

======== Applying patches ========
Applying patch patches/sagemaker-extension.diff
patching file vscode/extensions/sagemaker-extension/src/extension.ts
patching file vscode/extensions/sagemaker-extension/src/sessionWarning.ts
patching file vscode/extensions/sagemaker-extension/.vscodeignore
patching file vscode/extensions/sagemaker-extension/package.json
patching file vscode/extensions/sagemaker-extension/README.md
patching file vscode/extensions/sagemaker-extension/tsconfig.json
patching file vscode/extensions/sagemaker-extension/yarn.lock
patching file vscode/build/gulpfile.extensions.js
patching file vscode/build/npm/dirs.js
patching file vscode/extensions/sagemaker-extension/extension-browser.webpack.config.js
patching file vscode/extensions/sagemaker-extension/extension.webpack.config.js
patching file vscode/extensions/sagemaker-extension/src/constant.ts

Applying patch patches/disable-online-services.diff
patching file vscode/src/vs/platform/update/common/update.config.contribution.ts
patching file vscode/src/vs/workbench/contrib/preferences/common/preferencesContribution.ts
Hunk #1 succeeded at 144 (offset -7 lines).
patching file vscode/src/vs/workbench/services/assignment/common/assignmentService.ts

Applying patch patches/disable-telemetry.diff
patching file vscode/src/vs/platform/telemetry/common/telemetryService.ts
patching file vscode/src/vs/workbench/electron-sandbox/desktop.contribution.ts
Hunk #1 succeeded at 263 (offset -7 lines).
patching file vscode/src/vs/platform/telemetry/common/1dsAppender.ts
Hunk #1 succeeded at 18 with fuzz 1 (offset 1 line).

Applying patch patches/update-csp.diff
patching file vscode/src/vs/server/node/webClientServer.ts
Hunk #1 succeeded at 371 (offset -4 lines).

Applying patch patches/base-path.diff
patching file vscode/src/vs/base/common/network.ts
patching file vscode/src/vs/base/common/product.ts
patching file vscode/src/vs/code/browser/workbench/workbench-dev.html
patching file vscode/src/vs/code/browser/workbench/workbench.html
patching file vscode/src/vs/code/browser/workbench/workbench.ts
patching file vscode/src/vs/platform/extensionResourceLoader/common/extensionResourceLoader.ts
patching file vscode/src/vs/platform/remote/browser/browserSocketFactory.ts
patching file vscode/src/vs/server/node/webClientServer.ts
patching file vscode/src/vs/server/node/serverEnvironmentService.ts

Applying patch patches/webview.diff
patching file vscode/src/vs/workbench/services/environment/browser/environmentService.ts
patching file vscode/src/vs/server/node/webClientServer.ts
Hunk #1 succeeded at 331 (offset 8 lines).
patching file vscode/src/vs/workbench/contrib/webview/browser/pre/index.html
patching file vscode/src/vs/workbench/contrib/webview/browser/pre/index-no-csp.html
patching file vscode/src/vs/workbench/services/extensions/worker/webWorkerExtensionHostIframe.html

Applying patch patches/local-storage.diff
patching file vscode/src/vs/server/node/webClientServer.ts
patching file vscode/src/vs/workbench/browser/web.api.ts
patching file vscode/src/vs/workbench/services/environment/browser/environmentService.ts

Applying patch patches/sagemaker-integration.diff
patching file vscode/src/vs/workbench/browser/client.ts
patching file vscode/src/vs/workbench/browser/web.main.ts
patching file vscode/product.json
Hunk #2 succeeded at 34 with fuzz 2.
patching file vscode/src/vs/platform/product/common/product.ts
patching file vscode/src/vs/workbench/contrib/welcomeGettingStarted/browser/gettingStarted.ts
patching file vscode/extensions/git/package.nls.json
patching file vscode/src/vs/workbench/contrib/welcomeGettingStarted/common/gettingStartedContent.ts

Applying patch patches/license.diff
patching file vscode/LICENSE
patching file vscode/LICENSE-THIRD-PARTY
patching file vscode/LICENSE.vscode.txt
patching file vscode/ThirdPartyNotices.vscode.txt

Now at patch patches/license.diff

======== Generate Licenses ========
cp: ../LICENSE-THIRD-PARTY: No such file or directory

https://paste.amazon.com/show/goelakas/1727829734


Question: Nesting DND

@isaacHagoel this utility is fantastic. I've been able to use it successfully in a project that requires extremely complex DND functionality. Here's an example of my current prototype: https://radius-stage.pilotio.workers.dev/
The next battle I'm facing is making the cards sortable within nested cards. Imagine if I could "expand" a card which reveals a drop area allowing me to move cards from anywhere into it.
Do you have any suggestions on how to solve this? I'd appreciate the pointers!

so u basically need another level of nesting?
what can go inside from where (as in does it have a different "type")
maybe if you draw something on paper and attach it would be easier for me to understand what you're after

Hi, I made an example for multi drag in the svelte implantation (should be transferrable to Solid). Just FYI
https://svelte.dev/repl/c4eb917bb8df42c4b17402a7dda54856?version=3.24.1


Do not store the server information of the image block in the block

Wouldn't this get fixed by the deserializer on the image block? Of course, right now we have who knows what versions of blocks, with who knows what data inside.
https://github.com/plone/plone.restapi/blob/master/src/plone/restapi/deserializer/blocks.py#L145
I think we're missing a serializer for the image block, though. I don't have a test website with latest code, but I'll try to test this next week.

@tiberiuichim I think in this case it was a bug I introduced when I wrote the block in the first place, so it's sensible that we should fix it in the source. It's going to work anyways, since it also keeps the backwards compat. I plan to write a Plone script to migrate too, just in case.


find_transactions requires tx hashes on iota.lib.py but it should require bundle hashes

https://iota.readme.io/reference#findtransactions
According the reference this call should require list of bundle hashes not Transaction hashes
   :param bundles:
      List of transaction IDs.

Well spotted @oskyk!

I have tried to change it here #189

Scheduled for release: 2.0.7
Thanks @oskyk !!


Documentation: Merge NixOS Wiki article on NixOS modules into the manual

Problem
Currently there are two prominent pieces of documentation on NixOS modules. This is confusing for beginners in two ways:

It misleads them into thinking the NixOS Wiki is the authoritative and curated source of documentation, which it is not.
It requires them switching back and forth between different resources, which have high overlap but are both incomplete ("tab explosion").

Related:

https://discourse.nixos.org/t/usability-study-session-4/21422
https://discourse.nixos.org/t/usability-study-session-10/21456
https://discourse.nixos.org/t/usability-study-session-5/21424

Proposal
Merge into NixOS Wiki: NixOS Modules into NixOS manual: Writing NixOS modules and link from the Wiki article to the manual.
This can be done in multiple steps, but in any case will be quite some work untangling the overlap and the differences.
Checklist

[x] checked latest Nixpkgs manual (source) and latest NixOS manual (source)
[x] checked open documentation issues for possible duplicates
[ ] checked open documentation pull requests for possible solutions

Note: Did not check the entire list of possible PRs.

This issue has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/tweag-nix-dev-update-44/25546/1


[IOTDB-927] Remove fastjson introduced by rocketmq

@liuruiyiyang , can you have an evaluation for this change?  I am not sure whether RocketMQ client can run as normal if there is no a JSON dependency.
By the way, is there some useful UT/IT that can be introduced from RocektMQ here?

The fastJson is a dependency of rocketmq-client indeed, since it is used in the rocketmq-remoting component for serialization which is used by almost all rocketmq component including broker, name server and client.


Add tests for sign function, change sign to return Int type

This PR addresses #234. Also changes sign to return Int type

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


Docker - Spark installation problem

Hello,
I download last version if git and I have this issue :
Can you help me ?
docker-compose build
Building elasticsearch
Step 1 : FROM elasticsearch:2.1.1
---> 6f609da577b7
Step 2 : MAINTAINER vspiewak
---> Using cache
---> c2287a0451fa
Step 3 : ENV PATH /usr/share/elasticsearch/bin:$PATH
---> Using cache
---> b90d29d86c3a
Step 4 : RUN plugin install mobz/elasticsearch-head
---> Using cache
---> 2e45724c17af
Successfully built 2e45724c17af
Building spark
Step 1 : FROM java:8
---> 6c9a006fd38a
Step 2 : MAINTAINER vspiewak
---> Using cache
---> 1cb8abf01c10
Step 3 : WORKDIR /opt
---> Using cache
---> 5a1a9f990453
Step 4 : ENV SPARK_VERSION 1.5.2
---> Using cache
---> c2b58646147e
Step 5 : RUN curl -o spark.tgz http://d3kbcqa49mib13.cloudfront.net/spark-$SPARK_VERSION.tgz
---> Using cache
---> cdcc4a3cb188
Step 6 : RUN tar xvzf spark.tgz
---> Using cache
---> 10f720c58dc4
Step 7 : RUN rm spark.tgz
---> Using cache
---> ea879762a036
Step 8 : RUN ln -s spark-$SPARK_VERSION spark
---> Using cache
---> 3ae136d6e56e
Step 9 : WORKDIR spark
---> Using cache
---> 87283edd276f
Step 10 : RUN sbt/sbt assembly
---> Running in 60e6788f38de
NOTE: The sbt/sbt script has been relocated to build/sbt.
Please update references to point to the new location.
  Invoking 'build/sbt assembly' now ...

Using /usr/lib/jvm/java-8-openjdk-amd64 as default JAVA_HOME.
Note, this will be overridden by -java-home if it is set.
Attempting to fetch sbt
Our attempt to download sbt locally to build/sbt-launch-0.13.7.jar failed. Please install sbt manually from http://www.scala-sbt.org/
ERROR: Service 'spark' failed to build: The command '/bin/sh -c sbt/sbt assembly' returned a non-zero code: 255

Are you still seeing the error?

Yes.

Well, I actually don't see that error in Ubuntu 16.04, the build process seemed to get to the very end, only to fail. I am rerunning it right now, what seemed worrisome was that some twitter library towards the middle of the build was not to be found, as well as the immediately next library. Was it really necessary to hardwire all those version numbers? Can the build process recover from "error] SERVER ERROR: Service Temporarily Unavailable url=http://maven.twttr.com/org/apache/hadoop/hadoop-yarn-server/2.2.0/hadoop-yarn-server-2.2.0.jar" , or will that be another 30 minutess when I am forced to restart the build? Thanks anyway, will be great to make it work again!

Facing the same issue as outlined at the very start here. It doesn't work after Invoking 'build/sbt assembly' now ...


memory leak in subscriber-collection.js in case of complex bindings

I'm submitting a bug report

Library Version:
1.2.1

Please tell us about your environment:

Operating System:
Windows 10

Node Version:
6.9.1

NPM Version:
4.0.5

JSPM OR Webpack AND Version
JSPM 0.16.46

Browser:
Chrome 57

Language:
ESNext

Current behavior:
When using complex binding expressions inside of a repeat, old subscribers do net get cleaned-up on itemsChanged.
Expected/desired behavior:
The example is a list of 100 items that can be filtered by a search box:
https://gist.run/?id=ed14778cdbeccb3888c6ee0c16b8fc71
Set a breakpoint to: https://github.com/aurelia/binding/blob/1d6e826dbbc401ca21ad0deaf7acca498cd71c8b/src/subscriber-collection.js#L49
and enter a search value, e.g. '1' into the search box.
Each time you change the search value the repeat items change and the size of this._callablesRest grows (~200, ~300, ~500, ...).

What is the expected behavior?
Outdated subscriptions are not retained by the framework since they may keep a large amout of memory from being freed by the GC.

What is the motivation / use case for changing the behavior?
Allowing to implementing re-usable UI components which require more complex binding expressions, e.g. a data driven list with search and "add new row" capabilities.

@jdanyow have you had a chance to look at this? It is related to https://github.com/aurelia/router/issues/456 this is affecting a client of mine.
Thanks!

@jdanyow I don't think complex binding is the root cause here. As hinted by @reinholdk , it is because the way rest works currently in subscriberCollection:
if (!rest
  || !rest.length
  || (index = rest.indexOf(context)) === -1 // Issue here, context in repeat are often the same
  || this._callablesRest[index] !== callable) // thus this line will be wrong, as the index is of something else

Potential PR: break the if into smaller chunk to handle it correctly
  let rest = this._contextsRest;
  let callablesRest = this._callablesRest;
  let index;
  // this is normal
  if (!rest || !rest.length) {
    return false;
  }
  // we can't rely on context, since it's repeated when it comes to rest
  // So we have to use the callable
  if ((index = callablesRest.indexOf(callable)) === -1) {
    return false;
  }
  // Still it's not reliable enough, same callable may have both
  // sourceContext and targetContext
  // Need to check one more round
  if (rest[index] !== context) {
    let len = callablesRest.length;
    while (len > index) {
      if (rest[index] === context) {
        break;
      }
      index++;
    }
    if (index === len) {
      return false;
    }
  }
  // If every condition passed, splice:
  rest.splice(index, 1);
  callablesRest.splice(index, 1);
  return true;

Related: Memory leak #555
Temporary fix: Replace the whole removeSubscriber in aurelia-binding/src/subscriber-collection with following function (expand detail). It's quite impossible to patch in Gist so can't put it there.

function removeSubscriber(context, callable) {
  if (this._context0 === context && this._callable0 === callable) {
    this._context0 = null;
    this._callable0 = null;
    return true;
  }
  if (this._context1 === context && this._callable1 === callable) {
    this._context1 = null;
    this._callable1 = null;
    return true;
  }
  if (this._context2 === context && this._callable2 === callable) {
    this._context2 = null;
    this._callable2 = null;
    return true;
  }
  let rest = this._contextsRest;
  let callablesRest = this._callablesRest;
  let index;
  if (!rest || !rest.length) {
    return false;
  }
  if ((index = callablesRest.indexOf(callable)) === -1) {
    return false;
  }
  if (rest[index] !== context) {
    let len = callablesRest.length;
    while (len > index) {
      if (rest[index] === context) {
        break;
      }
      index++;
    }
    if (index === len) {
      return false;
    }
  }
  rest.splice(index, 1);
  callablesRest.splice(index, 1);
  return true;
}

@jdanyow @EisenbergEffect I dont know if this will have impact on benchmark tests, so I haven't created a PR. What do you think ?


768: added support for missing values

this is fixed in the 777 branch and is an improper fix, closing this out.


Fix/seo

Everything seems to be ok regarding the recent patch! An X-Robots = Noindex tag has been detected but must come from the sandbox principle provided by Vercel


add --stdout flag to dotenvx encrypt

this will allow you to send to stdout rather than overwrite/change the file - pipe to commands, write to a different file. whatever your tooling and processes need.
i considered the -O or -o flag as that is common but never really liked them. they didn't feel significant enough and also confusing to read - is it a 0 or a O? going with the loud --stdout. i think it also better communicates the terminology to junior devs just learning to pipe.

https://github.com/dotenvx/dotenvx/pull/298

https://github.com/dotenvx/dotenvx/pull/298


Howto pass array in path parameter

Information

Version: 4.34.4
Type: Question

Description
How to pass array as path parameter?
Example
Controller:
  @Get("/:criteria")
  public async get(
    @PathParams("criteria", String) @Required() criteria: string[]) {
    // criteria is string here "[abc,asd]" or "abc,asd"
  }

I tried following URL's:
/api/controller/[abc,asd]
/api/controller/abc,asd
Acceptance criteria

[ ] criteria is string[] = ["abc", "asd"]

Hello @antonovicha
Is not possible. But you can parse the string or add create your own filter:
import {ParamTypes} from "../interfaces/ParamTypes";
import {PathParamsFilter} from "../filters/PathParamsArrayFilter";
import {ParamRegistry, ParamTypes} from "@tsed/common";

export function PathParamsArray(expression?: string | any, useType?: any): Function {
  return ParamRegistry.decorate(PathParamsArrayFilter, {
    expression,
    useType,
    paramType: ParamTypes.PATH
  });
}

import {ParseService, IFilter, Filter} from "@tsed/common";

@Filter()
export class PathParamsArrayFilter implements IFilter {
  constructor(private parseService: ParseService) {}

  transform(expression: string, request: any, response: any) {
      const value = this.parseService.eval(expression, request["params"])
      // parse value

      return value
  }
}

And finally:
@Get("/:criteria")
  public async get(
    @PathParamsArray("criteria", String) @Required() criteria: string[]) {
    // criteria is string here "[abc,asd]" or "abc,asd"
  }

@Romakita Thank you for fast response. Will use query parameters for time being.
I have follow up question regarding then. I can not use string delimited values in query parameter like:

http://localhost:3000/classification/?criteria=P1,P2

It is again parsed as string instead of string[].
However following one is parsed as array (I guess by express itself):

http://localhost:3000/classification/?criteria=P1&criteria=P2

Express doesn't parse criteria field when you have coma inside. So if you want change that, you have to develop your own filter also :)

Got it. Thanks for answers.
Would it make sense to extend tsed implementation of @ParamsArray and @QueryArray to accept those scenarios? I expected such behavior in first place. If so, I may try to do it as soon as I have little bit more time.

Hum... what do you by extending tsed implementation ?
In your case, you have two choices. Override PathParamsFilter and QueryParamsFilter or define custom PathParamsArray and his filter.
See you :)

After reading about converters and *Params decorators I was under impression that tsed support parsing of array parameters of JS basic types out of the box, see http://v4.tsed.io/docs/converters.html#type-converters . And according to documentation it is possible to define custom converter and use it transparently with [Path|Query]Params decorator, see here http://v4.tsed.io/api/common/filters/decorators/QueryParams.html#description.
That is why I tried to use string[] path param with just PathParams decorator.

Yes. It's supported for QueryParams when you send a request like that:
http://localhost:3000/classification/?criteria=P1&criteria=P2
This feature is supported because Express parse the query and store it in request.query.criteria as an array.
For pathParams, express does nothing and it store information as string on request.path. So If you want a specific behavior, you have to implement custom filter :)
See you,
Romain Lenzotti

My question is answered therefore I believe issues is closed. Thank you for your answers.
If you believe that adjusting tsed implementation is not right course of action, may be making a note in documentation of *Params decorators will be an option?

Hum PathParamsArray decorator can be implemented. A PR are welcome :)

In such case there will be an inconsistency between deserialization using custom serializer  and *Params decorator:
get(@QueryParams('users', User) users: User[]) {

vs
get(@QueryArrayParams('users', String) users: string[]) {

Also isn't it the fact that user parameter is an array is available in metadata?


Azure API reference for Reserved Instances is missing 'write' operations

🛑 IMPORTANT: You can get your feedback addressed faster if you use the comment section for the article in which you encountered a problem.
Understood. This issue relates to the Azure REST API reference, which doesn't (yet) have a comments section.
Link to article:
https://docs.microsoft.com/en-us/rest/api/reserved-vm-instances/
Problem:
Look at the various sub-pages for resources/operations relating to Reserved Instances.
All I can see are 'Read' operations. Where is the API reference for the 'Write' operations? How do I use the REST API to create a Reserved Instance?
According to the sample output at https://docs.microsoft.com/en-us/rest/api/reserved-vm-instances/operation/list there should be write operations on 'reservations' and 'reservationOrders'.

@hellosnow Can you find the right person to follow up?

@jtuliani I transferred the issue to https://github.com/Azure/azure-rest-api-specs/issues/3574, please check update there.


[BUG][2.5.10] Implementation-Version is incorrect

The manifest info of the newly released 2.5.10 is incorrect, which causes com.alibaba.dubbo.common.Version#getVersion() returns the wrong version - 2.0.1.
The following is the manifest of 2.5.10:
Manifest-Version: 1.0
Implementation-Vendor: The Dubbo Project
Implementation-Title: Dubbo
Implementation-Version: 2.0.1
Implementation-Vendor-Id: com.alibaba
Built-By: ken.lj
Build-Jdk: 1.7.0_80
Specification-Vendor: The Dubbo Project
Specification-Title: Dubbo
Created-By: Apache Maven 3.1.1
Specification-Version: 2.0.0
Archiver-Version: Plexus Archiver

Here is the manifest of 2.5.8, which is correct:
Manifest-Version: 1.0
Implementation-Vendor: Alibaba
Implementation-Title: Dubbo
Implementation-Version: 2.5.8
Implementation-Vendor-Id: com.alibaba
Built-By: ken.lj
Build-Jdk: 1.6.0_32
Specification-Vendor: Alibaba
Specification-Title: Dubbo
Created-By: Apache Maven 3.1.1
Specification-Version: 2.5.8
Archiver-Version: Plexus Archiver

This has been changed since 2.5.9, does this change has some side effects on your project?

On 14 Mar 2018, at 11:25 AM, Jason Song<EMAIL_ADDRESS>wrote:
The manifest info of the newly released 2.5.10 is incorrect, which causes com.alibaba.dubbo.common.Version#getVersion() returns the wrong version - 2.0.1.
The following is the manifest of 2.5.10:
Manifest-Version: 1.0
Implementation-Vendor: The Dubbo Project
Implementation-Title: Dubbo
Implementation-Version: 2.0.1
Implementation-Vendor-Id: com.alibaba
Built-By: ken.lj
Build-Jdk: 1.7.0_80
Specification-Vendor: The Dubbo Project
Specification-Title: Dubbo
Created-By: Apache Maven 3.1.1
Specification-Version: 2.0.0
Archiver-Version: Plexus Archiver
Here is the manifest of 2.5.8, which is correct:
Manifest-Version: 1.0
Implementation-Vendor: Alibaba
Implementation-Title: Dubbo
Implementation-Version: 2.5.8
Implementation-Vendor-Id: com.alibaba
Built-By: ken.lj
Build-Jdk: 1.6.0_32
Specification-Vendor: Alibaba
Specification-Title: Dubbo
Created-By: Apache Maven 3.1.1
Specification-Version: 2.5.8
Archiver-Version: Plexus Archiver
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub https://github.com/alibaba/dubbo/issues/1466, or mute the thread https://github.com/notifications/unsubscribe-auth/ARQlibiLp75nQ36yl5VeDV9uhIqZOwqVks5teI2OgaJpZM4Spx8r.

We have integrated dubbo with our tracing system, which will include dubbo version in each rpc call event.
The version information is one of the key diagnosis information when some service meets something wrong.
So yes, this change does have some side effects. Not on my project but on many services using our sdk.

Hi Jun,
We have integrated dubbo with our tracing system, which will include dubbo version in each rpc call event.
The version information is one of the key diagnosis information when some service meets something wrong.
So yes, this change does have some side effects. Not on my project but on many services using our sdk.
Thanks!
Jason
On 14/03/2018, 14:27, "Jun Liu"<EMAIL_ADDRESS>wrote:

This has been changed since 2.5.9, does this change has some side effects on your project?

On 14 Mar 2018, at 11:25 AM, Jason Song<EMAIL_ADDRESS>wrote:
The manifest info of the newly released 2.5.10 is incorrect, which causes com.alibaba.dubbo.common.Version#getVersion() returns the wrong version - 2.0.1.
The following is the manifest of 2.5.10:
Manifest-Version: 1.0
Implementation-Vendor: The Dubbo Project
Implementation-Title: Dubbo
Implementation-Version: 2.0.1
Implementation-Vendor-Id: com.alibaba
Built-By: ken.lj
Build-Jdk: 1.7.0_80
Specification-Vendor: The Dubbo Project
Specification-Title: Dubbo
Created-By: Apache Maven 3.1.1
Specification-Version: 2.0.0
Archiver-Version: Plexus Archiver
Here is the manifest of 2.5.8, which is correct:
Manifest-Version: 1.0
Implementation-Vendor: Alibaba
Implementation-Title: Dubbo
Implementation-Version: 2.5.8
Implementation-Vendor-Id: com.alibaba
Built-By: ken.lj
Build-Jdk: 1.6.0_32
Specification-Vendor: Alibaba
Specification-Title: Dubbo
Created-By: Apache Maven 3.1.1
Specification-Version: 2.5.8
Archiver-Version: Plexus Archiver
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub https://github.com/alibaba/dubbo/issues/1466, or mute the thread https://github.com/notifications/unsubscribe-auth/ARQlibiLp75nQ36yl5VeDV9uhIqZOwqVks5teI2OgaJpZM4Spx8r.

Jason,
Pls. file an issue on github.
Thanks,
-Ian.

On 14 Mar 2018, at 3:52 PM, ken.lj<EMAIL_ADDRESS>wrote:
Hi Jun,
We have integrated dubbo with our tracing system, which will include dubbo version in each rpc call event.
The version information is one of the key diagnosis information when some service meets something wrong.
So yes, this change does have some side effects. Not on my project but on many services using our sdk.
Thanks!
Jason
On 14/03/2018, 14:27, "Jun Liu"<EMAIL_ADDRESS><EMAIL_ADDRESS>wrote:

This has been changed since 2.5.9, does this change has some side effects on your project?

On 14 Mar 2018, at 11:25 AM, Jason Song<EMAIL_ADDRESS><EMAIL_ADDRESS>wrote:
The manifest info of the newly released 2.5.10 is incorrect, which causes com.alibaba.dubbo.common.Version#getVersion() returns the wrong version - 2.0.1.
The following is the manifest of 2.5.10:
Manifest-Version: 1.0
Implementation-Vendor: The Dubbo Project
Implementation-Title: Dubbo
Implementation-Version: 2.0.1
Implementation-Vendor-Id: com.alibaba
Built-By: ken.lj
Build-Jdk: 1.7.0_80
Specification-Vendor: The Dubbo Project
Specification-Title: Dubbo
Created-By: Apache Maven 3.1.1
Specification-Version: 2.0.0
Archiver-Version: Plexus Archiver
Here is the manifest of 2.5.8, which is correct:
Manifest-Version: 1.0
Implementation-Vendor: Alibaba
Implementation-Title: Dubbo
Implementation-Version: 2.5.8
Implementation-Vendor-Id: com.alibaba
Built-By: ken.lj
Build-Jdk: 1.6.0_32
Specification-Vendor: Alibaba
Specification-Title: Dubbo
Created-By: Apache Maven 3.1.1
Specification-Version: 2.5.8
Archiver-Version: Plexus Archiver
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub <https://github.com/alibaba/dubbo/issues/1466 https://github.com/alibaba/dubbo/issues/1466>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ARQlibiLp75nQ36yl5VeDV9uhIqZOwqVks5teI2OgaJpZM4Spx8r https://github.com/notifications/unsubscribe-auth/ARQlibiLp75nQ36yl5VeDV9uhIqZOwqVks5teI2OgaJpZM4Spx8r>.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub https://github.com/alibaba/dubbo/issues/1466#issuecomment-372933200, or mute the thread https://github.com/notifications/unsubscribe-auth/ARybXAD_T7khgeHmXg8deL_vCKoj0VSeks5teMxAgaJpZM4Spx8r.

i think 2.5.10 is better

Sorry for bothering you.
I have checked the design purpose and implementation code before made this change. I believe the version here means the implementation version of the RPC Protocol,  also the Protocol-Specific-Version means the specification of RPC Protocol. If i understand the version in a right way, don’t think it should be changed for every release(or at least don’t have to be the same with the jar version).
I know that there maybe some compatible problems if someone relies on this “version number the same with the jar version” rule, but this change should not cause any critical problems on remote procedures. I tend to do this when i have to do a compatible upgrade for RPC protocols, check this PR(https://github.com/alibaba/dubbo/pull/1442#issuecomment-371776703 https://github.com/alibaba/dubbo/pull/1442#issuecomment-371776703, not completely finished yet). I think it would be better for us to keep a stable version number instead of change every release.
Only my opinion. And I believe when we follow the apache way by using the dev mailing list -<EMAIL_ADDRESS>we can avoid any changes before they are fully discussed.

On 14 Mar 2018, at 3:51 PM, ss宋顺<EMAIL_ADDRESS>wrote:
Hi Jun,
We have integrated dubbo with our tracing system, which will include dubbo version in each rpc call event.
The version information is one of the key diagnosis information when some service meets something wrong.
So yes, this change does have some side effects. Not on my project but on many services using our sdk.
Thanks!
Jason
On 14/03/2018, 14:27, "Jun Liu"<EMAIL_ADDRESS>wrote:

This has been changed since 2.5.9, does this change has some side effects on your project?

On 14 Mar 2018, at 11:25 AM, Jason Song<EMAIL_ADDRESS>wrote:
The manifest info of the newly released 2.5.10 is incorrect, which causes com.alibaba.dubbo.common.Version#getVersion() returns the wrong version - 2.0.1.
The following is the manifest of 2.5.10:
Manifest-Version: 1.0
Implementation-Vendor: The Dubbo Project
Implementation-Title: Dubbo
Implementation-Version: 2.0.1
Implementation-Vendor-Id: com.alibaba
Built-By: ken.lj
Build-Jdk: 1.7.0_80
Specification-Vendor: The Dubbo Project
Specification-Title: Dubbo
Created-By: Apache Maven 3.1.1
Specification-Version: 2.0.0
Archiver-Version: Plexus Archiver
Here is the manifest of 2.5.8, which is correct:
Manifest-Version: 1.0
Implementation-Vendor: Alibaba
Implementation-Title: Dubbo
Implementation-Version: 2.5.8
Implementation-Vendor-Id: com.alibaba
Built-By: ken.lj
Build-Jdk: 1.6.0_32
Specification-Vendor: Alibaba
Specification-Title: Dubbo
Created-By: Apache Maven 3.1.1
Specification-Version: 2.5.8
Archiver-Version: Plexus Archiver
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub https://github.com/alibaba/dubbo/issues/1466, or mute the thread https://github.com/notifications/unsubscribe-auth/ARQlibiLp75nQ36yl5VeDV9uhIqZOwqVks5teI2OgaJpZM4Spx8r.

Thanks for the clarification, I'm OK with this for now.
However, I'm not sure whethere it's a good idea to bind RPC protocol Version to the Specification-Version in a Jar Manifest file.
In my opinion, they are 2 different concepts. For example, one jar file could provide several different rpc protocols, in that case, we won't be able to use the Specification-Version in one Jar Manifest file to represent multiple RPC protocol Versions.

However, I'm not sure whethere it's a good idea to bind RPC protocol Version to the Specification-Version in a Jar Manifest file.
In my opinion, they are 2 different concepts. For example, one jar file could provide several different rpc protocols, in that case, we won't be able to use the Specification-Version in one Jar Manifest file to represent multiple RPC protocol Versions

Agree with you. Maybe we should figure out a new way for identifying RPC version, separate  RPC protocol Version from the Manifest specification/implementation version.

On 18 Mar 2018, at 4:00 PM, Jason Song<EMAIL_ADDRESS>wrote:
Thanks for the clarification, I'm OK with this for now.
However, I'm not sure whethere it's a good idea to bind RPC protocol Version to the Specification-Version in a Jar Manifest file.
In my opinion, they are 2 different concepts. For example, one jar file could provide several different rpc protocols, in that case, we won't be able to use the Specification-Version in one Jar Manifest file to represent multiple RPC protocol Versions.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub https://github.com/alibaba/dubbo/issues/1466#issuecomment-373979652, or mute the thread https://github.com/notifications/unsubscribe-auth/ARQlicYXRMmaZn87ejbW_mbd1uSCgixNks5tfhQmgaJpZM4Spx8r.

https://github.com/apache/incubator-dubbo/blob/master/dubbo-common/src/main/java/com/alibaba/dubbo/common/Version.java
Version.java read version from MANIFEST.MF or jar name.
Now you debug in classes generated by IDE, no MANIFEST.MF or jar name found
Must we support the IDEA debug environment?
If so，we can refer this Generate a Version.java file in Maven

#1843

dubbo协议版本从2.0.1变更为2.0.2，原因原来是这个引起。

We also meet the problem. This must mislead many developers.

We also meet the problem. This must mislead many developers.

You can refer the code  here
https://github.com/apache/dubbo/blame/2.6.x/dubbo-config/dubbo-config-api/src/main/java/com/alibaba/dubbo/config/ServiceConfig.java#L372
Acturally, we use the jar with version 2.6.6.


Add parameter codesigning_identity for CODE_SIGN_IDENTITY setting

Checklist

[x] I've run bundle exec rspec from the root directory to see all new and existing tests pass
[x] I've followed the fastlane code style and run bundle exec rubocop -a to ensure the code style is valid
[x] I've read the Contribution Guidelines
[x] I've updated the documentation if necessary.

Motivation and Context
update_project_provisioning(
                xcodeproj: "iOSArchive.xcodeproj",
                profile: "./#{profilename}", # optional if you use sigh
                target_filter: "iOSArchive", # matches name or type of a target
                build_configuration: "Release",
              )

When Release Archive a project with the development export method
The Release XCBuildConfiguration's CODE_SIGN_IDENTITY[sdk=iphoneos*] defualt value is "iPhone Distribution"
This will cause the profile doesn't include distribution signing certificate

The same as the Debug Archive with ad-hoc export method for Debug XCBuildConfiguration's                 CODE_SIGN_IDENTITY defualt value is iPhone Developer
So I add a parameter for update_project_provisioning to change the CODE_SIGN_IDENTITY in XCBuildConfiguration so that the certificate will be find
update_project_provisioning(
                xcodeproj: "iOSArchive.xcodeproj",
                profile: "./#{profilename}", # optional if you use sigh
                target_filter: "iOSArchive", # matches name or type of a target
                build_configuration: "Release",
                codesigning_identity: "iPhone Developer" #specified the codesigning identity
              )

  gym

I use the changed update_project_provisioning action in my local project It worked well
Description
Add parameter codesigning_identity for action update_project_provisioning which you can set to iPhone Developer or iPhone Distribution according to the demand

@googlebot
I signed it!

@HarrisHan Are you still interested in getting this merged in?


Can't use coursier bootstrap --standalone --deterministic

Trying out coursier bootstrap --standalone for packaging Almond for use w/o network access.
coursier bootstrap almond:0.6.0 \
      --scala-version 2.11.12 \
      --standalone \
      --deterministic \
      -o almond

Unfortunately jvm-repr artifacts being served by jitpack seem to get new timestamps each time, invalidating the deterministic aspect.
This is really just a downstream consequence of https://github.com/jupyter/jvm-repr/issues/15

Nice catch @jameskoch.
jitpack actually does provide timestamps:
$ curl -I https://jitpack.io/com/github/jupyter/jvm-repr/0.4.0/jvm-repr-0.4.0.jar | grep -i last-modified
last-modified: Wed, 09 Jan 2019 18:50:09 Z

It seems they just aren't picked by java.net.HttpURLConnection#getLastModified, that coursier uses under-the-hood, because of the use of the Z time zone in the Last-Modified HTTP header. I opened https://github.com/coursier/coursier/issues/1806 for it.

I'll try to find time to look into https://github.com/jupyter/jvm-repr/issues/15, it'd be nice to be able to get rid of jitpack.

Nice diagnosis! I ended up just post-processing the jar to reset all timestamps. I'm not done testing yet, but hopeful I can finally move from off my custom classloader hierarchy and onto stock Almond.
While I have you, do you know if the cmd line parsing support passing multiple predef files (--predef file1 --predef file2)? I need one to load all my libraries (interp.load.cp) and then I think another to do some initialization and imports using those libraries.

do you know if the cmd line parsing support passing multiple predef files

It should (and does per its implementation). Doesn't it when you try?

I was asking before I got around to trying it, sorry.
0.6.0 ended up working fine using --predef file1 --predef file2. Only small thing was that the syntax shown in --help made me think it would accept --predef file1 file2:
  ...
  --predef-code  <string>
  --predef  <string*>
  ...


Ensure that schema file path can work as web urls or files

fetch_schema_tables function in cli.rb file in csvlint is responsible for this functionality in ruby implementation.
Need to be done in conjunction with #47

Done


Laravel 8 update

Hello, I would really need this package, could you update it for Laravel 8 please. Thank you

Have you got the update?


node wrapper for dart:io

From @jmesserly on January 29, 2016 18:8
We can now compile & run on nodejs. But we don't have a dart:io impl.
Copied from original issue: dart-lang/dev_compiler#436

From @vsmenon on April 22, 2016 12:26
Have you tried the preliminary node usage instructions near the end of #485 ?

From @Kleak on April 22, 2016 12:37
Nop, thanks, i will retry with this :)

From @Kleak on April 22, 2016 9:52
Hey maybe i can help on this task.
I'm wrapping nodejs with the js package : nodejs.dart
And a beginning of electron : electron.dart
The only problem i have is that i am not able to launch generated js file in node with this CL
dartdevc --v8-binary node -o build --modules node example/test_ddc_example.dart
it throw an error:
Error: Cannot find module 'dart/_runtime'
    at Function.Module._resolveFilename (module.js:339:15)
    at Function.Module._load (module.js:290:25)
    at Module.require (module.js:367:17)
    at require (internal/module.js:16:19)
    at Object.<anonymous> (/home/kleak/Work/test_ddc/build/test_ddc_example.js:2:12)
    at Module._compile (module.js:413:34)
    at Object.Module._extensions..js (module.js:422:10)
    at Module.load (module.js:357:32)
    at Function.Module._load (module.js:314:12)
    at Function.Module.runMain (module.js:447:10)

yeah you may want to sync to "master" as well. The newer compiler won't generate "dart/_runtime" anymore, it should be trying to require("dart_sdk")

From @Kleak on May 5, 2016 17:57
ok is there a starting point where i can look how to wrap an API ? Or is it the same as with the js package ?

Has i have saied i have started a wrap of node.js, this wrap follow the node.js api.
My question is : do you want the api of this be the same as the dart api ?
if not i have move the source to github so you can take a look :)
nodejs.dart
All the api are not cover for the moment but the basic is almost here.

Yeah this would be pretty cool. I'm building an HTML server and I want to use PugJS to render templates. I thought of creating a PugJS wrapper but realized dart:io server stuff is probably not portable to JavaScript. What is the current state of that?

The library is here https://github.com/electron-dart
Not all the nodejs api is covered at this time but you have all the base.
Also this package follow the nodejs api and the electron api not the dart one.
If you have question dont hesitate yo open issues ;)

No immediate plans to do this.


super-linter: update flake8 conf and move fils to linters dir

super-linter: update flake8 conf and move fils to linters dir

@enolfc it's included some changes/improvements related to test in another repo.
Let me also know if you feel there are things from your work on cloud-info-provider worth to add there.


Naming Convention

I have renamed
local -> Local
InPut -> Input
routes -> Routes

git merge  saravanadev-master

The changes has been made but i unable to merge your this request due to issue with github and i unable to hanel it
thank you so much appreciated @saravanadev


 Once he has that finished, we'll revert this PR and make Lecture Hall beautiful using his work.
Before:

After:

Going to merge this myself once tests pass because I'm the only FTE on this project.


Port the same change made in JSAPI lerc2Codec

Address RangeError caused by incorrect byteLength set for DataView

Hi @tmaurer3 , could you please help review the change? Thanks!
/cc @wju


owner.name  always return null

Most probably this depends on your Gerrit server. Please request the JSON result with a HTTP client (e.g. curl or your web browser and check if this property is available there.

could you give  me the url i can use  please

@samyzemmouri: Which API method are you calling? Then I can tell you.
You can find URLs here: https://gerrit-review.googlesource.com/Documentation/rest-api-changes.html

@samalg91: Do you have some news?

@samalg91: Feel free to reopen.


[REQ] Add an option to hide retweets of a specific profile

Describe the problem that needs solving
There is an option on Twitter to hide retweets of a specific profile. It is very useful when an account retweets a lot.
Describe the solution you'd like
Add an option to hide retween of a specific profile as Tweeter do

Closing as the feed has now been removed, due to Twitter blocking access permanently. Please see https://github.com/jonjomckay/fritter/issues/668#issuecomment-1528784190


Request with auth parameter throw an exception on IE11

Hello !
Everything was working fine, until I had to test some code using Axios under IE11
When using the auth param Axios throw an error on btoa https://github.com/mzabriskie/axios/blob/master/lib/adapters/xhr.js#L42
axios.post('/sessions', {}, {
    auth: {
      username: 'username',
      password: 'password'
    }
  });

error TypeError: Invalid calling object
Browser: Internet Explorer 11.0.9600
OS: Windows 7
Axios package.json version: 0.15.2
Thanks !

Fixed via 417913b


vue-apollo with Nuxt getting constantly errors if the root_query is changing

Hello,
I receive constant error message like following:
            throw new Error("Can't find field ROOT_QUERY on object (" + objId + ") " + JSON.stringify(obj, null, 2) + ".");

This happens if I navigate between pages with different query names. The apollo readStoreResolver function tries to update the caches and looks up old query inside of the new query:
oldQuery page1:
allPages{
  ...allPages
}

newQuery page2: ==> ERROR: can't find ROOT_QUERY on object "allPages"
allTravels{
  ...allTravels
}

Is there anything more I would need to set up?

Do you still have this issue with the newer versions?

Oh this is a really old one, will close it for now because I think thats not an issue any longer


[SPARK-9464] [WIP] [SQL] Property checks for UTF8String

This pull request adds ScalaCheck property-based tests for UTF8String.
I'm going to push a followup commit to add additional tests; opening this early to get high-level feedback first.

Merged build triggered.

Merged build started.

Test build #38994 has started for   PR 7780 at commit c7925f8.

Test build #38994 has finished for   PR 7780 at commit c7925f8.

This patch fails RAT tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
class UTF8StringPropertyChecks extends FunSuite with GeneratorDrivenPropertyChecks with Matchers

Merged build finished. Test FAILed.

Merged build triggered.

Merged build started.

Actually, I do not have time to work on this right now, but would be glad to have someone else take over and finish this.  Note that this has uncovered a few bugs already: substring() and contains() can crash with ArrayIndexOutOfBounds exceptions and it looks like the trim() functions do not handle non 0x20 whitespace characters.

Test build #39012 has started for   PR 7780 at commit 81a8a4f.

Test build #39012 has finished for   PR 7780 at commit 81a8a4f.

This patch fails RAT tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
class UTF8StringPropertyChecks extends FunSuite with GeneratorDrivenPropertyChecks with Matchers

Merged build finished. Test FAILed.

I'll take this over if you don't mind :)

Sounds good to me; thanks @yjshen!


docs-components: Use PrismJS for all highlighting

Switches Highlight.js for PrismJS when applying syntax highlighting to
HTML. This simplifies the code bringing it into alignment with React. It
also means that visually there is more symmetry between the two.
It does come at the cost of reduced contrast in the colours. - We may
want to re-create the old colour scheme with PrismJS.

Example: Tag component
HTML before

HTML after

React


Add support for DRAT reset command to Proteus

Allow reset and replace Go select command with Reset.

done!


Avoid setting memory configs for Basic SKU cache

Avoid setting memory configs for Basic SKU cache. Fixes #2902
This checklist is used to make sure that common guidelines for a pull request are followed.

[x] The PR has modified HISTORY.rst describing any customer-facing, functional changes. Note that this does not include changes only to help content. (see Modifying change log).

[x] I adhere to the Command Guidelines.

@haroldrandom Can you please review this PR


Add rangeConstraint prop

First off, thank you for this nice looking component. I needed a component that allows selecting weeks that correspond to timesheets. This PR adds a rangeConstraint prop that currently only supports "week". This enables selecting entire weeks. Could be expanded to address #1

Coverage decreased (-0.9%) to 89.552% when pulling 5a7082aa9bf9cf704d085a1deb069ab7ae1015ad on kevinchappell:feature/selectWeek into acd6b0b7a7b1e58185d6a912b0e9441838a1fbe5 on Tinysymphony:master.

Coverage increased (+1.6%) to 92.04% when pulling c916749bc5334cb0336bf07607ccfbd1ca2ab77f on kevinchappell:feature/selectWeek into acd6b0b7a7b1e58185d6a912b0e9441838a1fbe5 on Tinysymphony:master.


Link to github source leads to 404

Clicking on

with href
https://github.com/davedawkins/Sutil/src/Sutil/DOM.fs#L1217-1217

leads to Not Found.
A link that does work is
https://github.com/davedawkins/Sutil/blob/main/src/Sutil/DOM.fs#L1217-1217

The difference is the blob/main/ insert. How did I fix this?

Wong repo :-D


Broken autofix for ESLint's spaced-comment rule

Is your feature request related to a problem? Please describe.
It looks like the comment node are extracted here: https://github.com/B2o5T/graphql-eslint/blob/4bcee4a7849602076fb9e0d9ab33e78141e20a8e/packages/plugin/src/estree-converter/utils.ts#L109
but since the API conforms to the SourceLocation type from estree, there's no actual comment field exposed.
Therefore it's not possible to disable a rule on a per field basis.

Describe the solution you'd like
Expose the comment field to the Node type:
https://github.com/B2o5T/graphql-eslint/blob/c33bde9c1c5bd8aa780a8ef6c1737eaaaa95f3b0/packages/plugin/src/estree-converter/types.ts#L106-L116
This way we can detect the comment on a field like https://github.com/relayjs/eslint-plugin-relay/blob/main/src/utils.js#L111-L114
which lets us disable a rule on a field level.

Describe alternatives you've considered
n/a

Additional context
n/a

Hi, can you send code example of

Therefore it's not possible to disable a rule on a per field basis.

@B2o5T  hi yes, something like this:
https://github.com/relayjs/eslint-plugin-relay/blob/fcacf1ed69097dd3a47856be8984de45a81c92f7/test/unused-fields.js#L88-L91

the following comment disables report of error on my side

@B2o5T that's interesting, I wonder if it's because the file is a JS file and it's the babel parser in play? Could you try to see if the comment works for a .graphql file?

I don’t need to test, it works, please create a reproduction of your problem with your configuration with minimal dependencies installed if you need help

@B2o5T ah yeah it actually works. It turns out this rule is causing some kind of conflicts with the comment line in my .graphql file, after disabling that rule it's working as expected, I'm guessing it's handled at higher level by eslint instead of needs to be explicitly supported by the parser itself.

@shogunsea I reopened your PR to figure out why there are conflicts with spaced-comment rule when I'll have a time

type TEST {
  _id: ID! # eslint-disable-line @graphql-eslint/naming-convention

type TEST {
  _id: ID! #eslint-disable-line @graphql-eslint/naming-convention

The error occurs when comments are written without a space in the schema (Second one)

as @taejs GraphQL-ESLint doesn't have any conflicts with spaced-comment, even it works very well with the default ESLint spaced-comment rule 😅
closing

@B2o5T why was this issue closed? we're still seeing a bug where the autofix is broken if you're using spaced-comment with graphql-eslint.

can you please share a reproduction?

@shogunsea https://github.com/eslint/eslint/issues/17145

Since this rule has problems with autofix for graphql files and ESLint rejected making this rule agnostic:
I suggest either disable it for *.graphql files or continuing to use it but without auto-fixing his errors


Spelling error

[Enter feedback here]
Specifies he time that the file was last written to.
Should be the
Document Details
⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.

ID: 8de2bc24-bcf6-8c8e-46a0-be6c4934d175
Version Independent ID: b9315d9a-6a43-d433-63ec-471daa1a45b2
Content: _FILE_NETWORK_OPEN_INFORMATION (wdm.h) - Windows drivers
Content Source: wdk-ddi-src/content/wdm/ns-wdm-_file_network_open_information.md
Product: windows-hardware
Technology: wdk-api-reference
GitHub Login: @barrygolden
Microsoft Alias: bagold

Thanks @DarkLinux appreciate the sharp eye.  I just pushed a fix, should be on the live site within the hour.


tests: add alert snapshot test

Preview environments are getting posted here, as soon as they are ready!


Request: Add Markdown as Output Option

Markdown is practically supported everywhere in terms of parsing and displaying. I think markdown tables could work nicely.
You can use markdown lists for the tree affect as well.
I'm looking to want to generate outputs whenever it changes and store it along with my documentation which is all written in markdown already. Would be nice to run and redirect output to file to include in my docs.

@ekristen thanks, I think this is a good idea. We also use markdown outputs for the CI/CD integrations.
Do you see the markdown output being similar to the infracost breakdown cli output or the infracost diff output?

I was originally thinking the breakdown as a table?

If this could work to update a section Readme that would be ideal, well for me anyway.

@ekristen and @JamesWoolfenden any thoughts on the following output options? Markdown tables don't have cell-merge, and indentation isn't supported AFAIK :(
BTW, there's also https://github.com/infracost/infracost/issues/43 if your use-case lends itself more to linking to a badge/shield in the readme?
Option 1: markdown list
Monthly cost estimate from Infracost.io: $742.64

aws_instance.web_app

Instance usage (Linux/UNIX, on-demand, m5.4xlarge), 730  hours, $560.64
root_block_device

Storage (general purpose SSD, gp2),                             50  GB-months,                    $5.00

ebs_block_device[0]

Storage (provisioned IOPS SSD, io1),                         1,000  GB-months,                  $125.00
Provisioned IOPS,                                              800  IOPS-months,                 $52.00

aws_lambda_function.hello_world

Requests,                                            Cost depends on usage: $0.20 per 1M requests
Duration,                                            Cost depends on usage: $0.0000166667 per GB-seconds

Option 2: markdown table
Monthly cost estimate from Infracost.io: $742.64

Name
Monthly Qty
Unit
Monthly Cost

aws_instance.web_app

- Instance usage (Linux/UNIX, on-demand, m5.4xlarge)
730
hours
$560.64

- root_block_device

-- Storage (general purpose SSD, gp2)
50
GB-months
$5.00

- ebs_block_device[0]

-- Storage (provisioned IOPS SSD, io1)
1,000
GB-months
$125.00

-- Provisioned IOPS
800
IOPS-months
$52.00

aws_lambda_function.hello_world

- Requests
Cost depends on usage: $0.20 per 1M requests

- Duration
Cost depends on usage: $0.0000166667 per GB-seconds

PROJECT TOTAL

$742.64

Option 3: current table format wrapped in a markdown code block
Monthly cost estimate from Infracost.io: $742.64

 Name                                                        Monthly Qty  Unit                  Monthly Cost

 aws_instance.web_app
 ├─ Instance usage (Linux/UNIX, on-demand, m5.4xlarge)               730  hours                      $560.64
 ├─ root_block_device
 │  └─ Storage (general purpose SSD, gp2)                             50  GB-months                    $5.00
 └─ ebs_block_device[0]
    ├─ Storage (provisioned IOPS SSD, io1)                         1,000  GB-months                  $125.00
    └─ Provisioned IOPS                                              800  IOPS-months                 $52.00

 aws_lambda_function.hello_world
 ├─ Requests                                            Cost depends on usage: $0.20 per 1M requests
 └─ Duration                                            Cost depends on usage: $0.0000166667 per GB-seconds

 PROJECT TOTAL                                                                                $742.64

I might be biased but I think option 3 seems more readable.

I like the third option, I was  manually copying in the output and using codeblocks and that seems to give the best layout.

I'm going to close this issue as Option 3 above seems the most readable, which doesn't require any changes since the text output can be wrapped in code blocks in markdown. Feel free to comment with better suggestions and we can revisit it.

I personally would love to see a markdown table like option #2 as well as a command that will update my Readme for me like terraform-docs does. How can we get something like this going?

I ended up just wrapping the standard infracost breakdown text in markdown codefences. Quick and dirty but better than any of the other options.


New Integrations

Amalgamates the integration PRs into one and bumps the version with the aim of releasing a feature-less hotfix.
The new integrations are listed below:

Decentralized Lending Network (DLN)   (Pending Approval :yellow_circle:)
Credentia                 (Pending Approval :yellow_circle:)
Casper Analytics              (Pending Approval :yellow_circle:)
Gitcoin                     (Approved :heavy_check_mark:)
BoringSwap                (Pending Approval :yellow_circle:)

and there respective URLs:
        "*://*.dlndao.org/*",
        "*://*.dln.org/*",
        "*://*.casper.credentia.me/*",
        "*://analytics.caspercommunity.io/*",
        "*://*.gitcoin.co/*",
        "*://gitcoin.co/*",
        "*://*.boringswap.com/*",
        "*://boringswap.com/*"

@George-cl
Not sure if you added
"://.dlndao.org/",
"://.dln.org/",
Manifest Matches List
but I can't see it in the current signer version
Is there any problems with the above PR?


HKG: combine platforms

Combining the platforms and detecting features on Hyundai will allow us to improve fingerprinting by aggregating as many FW versions as possible to fewer platforms. It also forces us to define the platforms/API in such a way that is agnostic to minor differences in the cars (like if it's hybrid, plug-in hybrid, ICE, EV), etc. We can use the platform code or CAN message presence to differentiate these if needed.

[ ] Niro Hybrid and Plug-in Hybrid platforms (different platform codes, but fwdCamera dates are shared. we already had the hybrid 2021, but not phev 2021): https://github.com/commaai/openpilot/pull/31275
[ ] G70 platforms https://github.com/commaai/openpilot/pull/31366
[ ] All CAN platforms
[ ] All CAN FD platforms

@sshane still an issue?

yes, but doesn't need to be an unactionable issue


Add general use meta/damage data support to flags....

Add general use meta/damage data support to flags that take an item or block name/id as a target.
A lot of mods are programmed to have items/blocks share item names/ids but with different meta/damage data to differentiate between them.
And no, that includes stuff that's completely different and/or completely unrelated.
Take Vazkii's Psi mod for example.
All of the components of a specific type share the same item name/id with only meta/damage data to differentiate them.
It makes far more sense to have generalized support for meta/damage data tags in the item names/ids then to hard code support for all of the various mods' items/blocks as options to use in the "[]" brackets.

It makes far more sense to have generalized support for meta/damage data tags in the item names/ids then to hard code support for all of the various mods' items/blocks as options to use in the "[]" brackets.

Blockstates are NOT hardcoded as they have been the standard since 1.8 and will not be going away. Every single mod is required to use blockstates for blocks in 1.8+.
To handle blocks in GP, you simply specify the [property=value] after the flag. However, non item blocks are still an issue as damage value seems to still be the the only thing that can be used to distinguish an item from another of the same type. I'll add support for meta soon. Just keep in mind that this will be changed the moment Mojang adds a similar system to blockstates for items.


Some error in using CASSCF

HI, every one , I am new to quamtum chemistry and PYSCF. I just tried to use PYSCF to make a  casscf pactice. But some error occur

Could anyone help me to solve this problem, please

myhf = scf.ROHF(mol).kernel() should be replaced by
myhf = scf.ROHF(mol).run()

or
myhf = scf.ROHF(mol)
myhf.kernel()

myhf = scf.ROHF(mol).kernel() should be replaced by
myhf = scf.ROHF(mol).run()

or
myhf = scf.ROHF(mol)
myhf.kernel()

Thank you so much for your reply!
Ummm, Is this a syntax about Python？How much knowledge of Python do I need to acquire, in order to learn PySCF?

No. It's a convention of PySCF. The kernel() function and run() do the same calculation, but run() returns a SCF object while kernel() not. So you cannot let myhf = scf.ROHF(mol).kernel().
Yeah, you need a little python knowledge to understand the documentation.

Hi @newuserofpyscf , thanks for using pyscf and for posting this question. Has it been answered?


Update ut_seattlelib_time_interface_updatetime_before_registermethod.r2p...

...y
create a else block to fail the test if it does not raise exception for not registering time method

Thanks Vlad. Yes, That way its more clear. Made the changes to the comment. Please check once.


feat: make usage statistics opt-in

Fixes #1001

Pull Request Test Coverage Report for Build 722696146

0 of 2 (0.0%)  changed or added relevant lines in 2 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 18.04%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

lib/ZwaveClient.js
0
1
0.0%

src/store/mutations.js
0
1
0.0%

Totals

Change from base Build 722371579:
0.0%

Covered Lines:
2022

Relevant Lines:
11496

💛  - Coveralls


vendor: unfork tcell

Hello @maiamcc,
Please review the following commits I made in branch nicks/tcell:
d83bf15ae5d998d33c5feb61f08cb4cd022e445c (2018-12-06 15:59:25 -0500)
vendor: unfork tcell

was poking at this while looking into what it would take to have windows support. seems like there are no good reasons to fork it anymore.


Conditionally require properties to be specified

E.g when when some checkbox or select have approprate value, then toggle other fields visibility (and mandatory / mark required or not)

done in 3.x


CODEOWNERS: Clean up file before turning mandatory reviews on

The CODEOWNERS file was being used as a notification method for those
who were interested in specific domains. However, it was decided to
repurpose it and make reviews from CODEOWNERS mandatory. As a result of
which, we need to clean it up in order to prevent dragging people into
reviews before they sign up for it.

Yes this PR removes all reviewers except for the file itself. Mandatory reviews only become applicable for patterns in this file which are none right now.


Add Storm-7B to AlpacaEval

🤗 Card model: https://huggingface.co/jieliu/Storm-7B

We also added Storm-7B (num_beams=10).

Very impressive results @yifan123 !
I must say that I'm a shocked that a 7B gets that performance. What data was it trained on? What's the magic sauce to get such performance?

We follow the same setup as in Starling-7B, using the same base model (openchat-3.5-0106) and fine-tuning on the same offline preference dataset (Nectar), without adding any additional datasets.
Our LM only differs in the optimization algorithms: apply DPO iteratively on newly generated responses ranked by the reward model (Starling-RM-34B). Note that Starling-RM-34B is also trained on Nectar by the K-wise maximum likelihood estimator, which means no extra data is used.
Our improvement stems mainly from the iterative training. The figure below shows that using only the first iteration's dataset in the second iteration results in minimal improvement.

We need to highlight the limitations of our study:
Storm-7B is a quick demonstration that a language model, fine-tuned with AI feedback, can easily surpass or match state-of-the-art models, as assessed by the same AI feedback. However, this improvement on the automatic leaderboard may not necessarily indicate better alignment with human intentions. Our model therefore represents a critical, preliminary reevaluation of the RLAIF paradigm, questioning how much learning from and being evaluated by AI feedback aligns with actual human preferences.


adds Day1: PowerShell

Adds my solution to challenge 1.

Hi @Ba4bes !
Once you have the challenge result, you will compare it to the challenge you created. And after make all the necessary changes in your code, we will close this PR.
Remember that all challenges must be developed in your repository. That's why is very important to fork this repository.
And thank you for your awesome contribution @Ba4bes  !

I have updated the Readme to add the second challenge 👍

We checked out your repository. We're thrilled to say your solution is now listed in our Hall of Fame
Thank you for your contributions!
This PR is now closed! 🎉


refactor: changed color from white to red

Fixes : #87
Description :
Changed RGB value of heart's color.
Screenshot of changes :

Please ensure Checkmark the following :

[x] - Tested Localy
[x] - Checked in IE11 and Firefox
[x] - Checked in mobile
[] - Backend work
[x] - Frontend work
[] - Bug Fixes
[x] - Enhancements

Thank you 👍


Error 403

Hi,
I just published my first Blazor succesfully!

When i open the website i get:

After publish the host contains:

hi. when you use VS to publish, it creates additional folders. what you need to do is - just pick the contents of the folder DIST and upload those contents to your hosting provider... in your case the publish has published everything …
just upload the contents of the dist folder.

Thx! I moved the contents of the dist folder to public_html and now it works. Thank you again.

cool. glad i could help you out 👍


Welcome Onur Bey

To establish the correct git environment in locals and this assignment for all,
*Everyone to clone the repo master branch
*Create one issue with "Versioning" tag
*Make one commit with #Closes

Git update will be updated. .vscode and .idea folders will be ignored and deleted from branch.


Allow buildRequest to log error

I was fiddling around and couldn't get jenkins working, so I added logging of an extra line to output in order to make it clear why jenkins is not working. Example:
before
error: [jenkins] jenkins.job.klear-dev-test  - status code: undefined

after
error: [jenkins] Error: unable to verify the first certificate
error: [jenkins] jenkins.job.klear-dev-test  - status code: undefined

Great, thanks! Can you just please fix the travis build before I can merge ?

@plouc done


Adds information regarding linking models on the hub to a HF Space

@osanseviero - lmk if this is okay for you.

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint.

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint.


Add CDL adapter

** Please note **
This PR includes the same changes and replaces the closed PR here: https://github.com/AcademySoftwareFoundation/OpenTimelineIO/pull/1368
This is to avoid messy fixes solving commits missing the Sign-off after a merge with main to fix unrelated linting errors.
Link the Issue(s) this Pull Request is related to.
https://github.com/AcademySoftwareFoundation/OpenTimelineIO/issues/1366
Fixes #1366
Summarize your change.
This change adds a new adapter, 'cdl', which exports individual .cdl files to a user-provided directory for each clip/timeline event in an OTIO instance.
This change does not change anything in the OTIO core.
Please note: Due to the nature of this adapter exporting multiple files instead of a single file, the provided export method name write_to_file is slightly semantically confusing. The output provided to the method should be the directory (not a file) in which you wish to export the .cdl's to. Because of this, it is also necessary to directly provide the adapter_name to use this adapter (there is no file extension to read):
otio.adapters.write_to_file(timeline, '/your/cdl/output/directory', adapter_name='cdl')
Reference associated tests.
/contrib/opentimelineio_contrib/adapters/tests/test_cdl_adapter.py provides a straightforward test which takes a sample EDL, ingests into OTIO and exports temporary .cdl files via the adapter. Two of these CDL's are read in as samples and checked.

Hi, could you try out this template for making new adapters? We are planning to move the other contrib adapters to separate repos, so instead of accepting a new one in that area & then moving it, we would prefer to have new adapters built from this template: https://github.com/OpenTimelineIO/otio-plugin-template
Also, in future, when you have merge/rebase problems, you can force-push to your branch instead of making a new PR - that way the previous discussion is not lost.

e are planning to move the other contrib adapters to separate repos, so instead of accepting a new one in that area & then moving it, we would prefer to have new adapters built from this template: https://github.com/OpenTimelineIO/otio-plugin-template

Hi there, I have implemented this using that new template here:
https://github.com/josh-mission/otio-cdl-adapter
Deployed to PyPi here:
https://pypi.org/project/otio-cdl-adapter

Awesome!
You should add your plugin to the list of tools and projects

Closed. This PR has been refactored into an external adapter repo available here:
https://github.com/josh-mission/otio-cdl-adapter
Deployed to PyPi here:
https://pypi.org/project/otio-cdl-adapter


[web]: exact same code works on device but xmlhttprequest error on chrome

Code posting to asmx webservice works perfectly on android device vut generate XmlHttpRequest error om chrome

I found the errocertain headers are not allowed under CORS policy whe the requests are handled over the webr.


AVAsset may expensive, can asset property be public to check and reuse

AVAsset may expensive, can asset property be public to check and reuse？
also, make a method to set player by assert

Also the playerLayer

not at this time, but thanks for the suggestion


net: inet.h match inet_sockif.c definition

Summary
When using the minimal CONFIG_NET configuration for SocketCAN.
Ifup would fail with the following error code.
Fixes psock_socket: ERROR: socket address family unsupported: 2
This was caused because AF_INET got defined but inet_sockif() would return NULL because either ICMP, TCP or UDP dependency didn't met. This patch changes the ifdef logic for AF_INET and AF_INET6 to include those checks so that other SOCK_FAMILY will work with minimal IPv4 or IPv6 config.
Impact
Net
Testing
Tested on MR-CANHUBK344 net config

[Experimental Bot, please feedback here]
No, this PR summary does not fully meet the NuttX requirements. While it addresses the "what" and "how" of the change, it lacks crucial details.  Here's a breakdown:

Insufficient Summary:

Missing "Why": While it mentions the error, it doesn't clearly explain why this error is a problem. What functionality was broken? Why is supporting minimal SocketCAN configurations important?
Vague "What functional part":  "Net" is too broad. Be more specific – e.g., "Networking stack, specifically socket initialization and address family support."
Missing Issue References:  Are there any related NuttX issues or PRs?  Even if there aren't, explicitly stating "None" is better.

Incomplete Impact Assessment:

Impact on user: Does this fix an existing issue users were facing? Will it enable new use cases? Be explicit.  E.g., "YES. Users will now be able to use SocketCAN with a minimal network configuration, which was previously not possible due to the reported error."
Impact on build:  Likely NO, but state it explicitly.
Impact on hardware: Specify which architectures/boards are affected.  "MR-CANHUBK344" should be mentioned here, not just in the Testing section.
Impact on documentation:  Does the documentation need updates to reflect this change?
Impact on security/compatibility: Even if the answer is NO, explicitly state it for each.
Anything else to consider?  This is meant to catch edge cases.  Think about potential unintended consequences.

Insufficient Testing Information:

Build Host Details Missing: Provide the OS, CPU architecture, and compiler version used for testing.
Target Details Incomplete: "MR-CANHUBK344 net config" is vague.  Specify the exact board configuration used.
Missing Logs:  The template specifically requests "Testing logs before change" and "Testing logs after change."  Include the relevant log output showing the error before the change and the successful operation after the change.  This provides concrete evidence that the fix works.

Example of a Better Summary:
This PR fixes an issue where SocketCAN initialization would fail with the error psock_socket: ERROR: socket address family unsupported: 2 when using a minimal network configuration.  This was caused by incorrect dependency checking for AF_INET and AF_INET6 address families.  The patch modifies the address family selection logic to ensure that SocketCAN functions correctly even when TCP/UDP/ICMP are disabled. This allows users to leverage SocketCAN with a reduced network stack footprint, which is beneficial for resource-constrained environments.  No related NuttX issues found.
Example of a Better Impact Section:

Impact on user: YES.  This fix resolves an issue that prevented users from using SocketCAN with minimal network configurations. This enables new use cases where a full TCP/IP stack is not required.
Impact on build: NO.
Impact on hardware: YES. This fix specifically addresses issues on platforms utilizing SocketCAN, such as the MR-CANHUBK344.
Impact on documentation:  YES.  The networking configuration documentation should be updated to reflect the ability to use SocketCAN with minimal configurations.  (Documentation update provided in this PR).
Impact on security: NO.
Impact on compatibility: NO.
Anything else to consider?  None.

By providing more complete information, you make it much easier for reviewers to understand and evaluate your changes, leading to a smoother and faster review process.

@PetervdPerk-NXP @xiaoxiang781216
I noticed that the renew command does not work with lm3s6965-ek:discover config.
$ /home/ishikawa/opensource/QEMU/qemu-9.0.0/build/qemu-system-arm -net nic,model=stellaris -net user,hostfwd=tcp::20023-:23,hostfwd=tcp::20021-:21,hostfwd=tcp::25001-:5001 -M lm3s6965evb -kernel ./nuttx/nuttx -nographic
Timer with period zero, disabling
telnetd [4:100]

NuttShell (NSH) NuttX-12.0.0
nsh> uname -a
NuttX  12.0.0 f6a72ad0f4 Nov  5 2024 08:24:15 arm lm3s6965-ek
nsh> ps
  PID GROUP PRI POLICY   TYPE    NPX STATE    EVENT     SIGMASK            STACK    USED FILLED COMMAND
    0     0   0 FIFO     Kthread   - Ready<PHONE_NUMBER>000000 0001008 0000444  44.0%  Idle_Task
    1     0 224 RR       Kthread   - Waiting  Semaphore<PHONE_NUMBER>000000 0001984 0000292  14.7%  hpwork 0x20000104 0x20000128
    2     0  60 RR       Kthread   - Waiting  Semaphore<PHONE_NUMBER>000000 0001984 0000292  14.7%  lpwork 0x200000cc 0x200000f0
    3     3 100 RR       Task      - Running<PHONE_NUMBER>000000 0002008 0001544  76.8%  nsh_main
    4     4 100 RR       Task      - Waiting  Semaphore<PHONE_NUMBER>000000 0002016 0000580  28.7%  telnetd
nsh> free
      total       used       free    maxused    maxfree  nused  nfree name
      45812      13348      32464      13704      32464     30      1 Umem
nsh> ifconfig
             IPv4   TCP   UDP  ICMP
Received     0000  0000  0000  0000
Dropped      0000  0000  0000  0000
  IPv4        VHL: 0000   Frg: 0000
  Checksum   0000  0000  0000  ----
  TCP         ACK: 0000   SYN: 0000
              RST: 0000  0000
  Type       0000  ----  ----  0000
Sent         0000  0000  0000  0000
  Rexmit     ----  0000  ----  ----
nsh> renew eth0
ERROR: netlib_obtain_ipv4addr() failed
nsh> ifconfig
             IPv4   TCP   UDP  ICMP
Received     0000  0000  0000  0000
Dropped      0000  0000  0000  0000
  IPv4        VHL: 0000   Frg: 0000
  Checksum   0000  0000  0000  ----
  TCP         ACK: 0000   SYN: 0000
              RST: 0000  0000
  Type       0000  ----  ----  0000
Sent         0000  0000  0000  0000
  Rexmit     ----  0000  ----  ----

When using the minimal CONFIG_NET configuration for SocketCAN. Ifup would fail with the following error code. Fixes psock_socket: ERROR: socket address family unsupported: 2 This was caused because AF_INET got defined but inet_sockif() would return NULL because either ICMP, TCP or UDP dependency didn't met.

Hi @PetervdPerk-NXP, we're curious about the situation you encountered.  We found situations (e.g. as a usrsock client) that need to use AF_INET as NET_SOCK_FAMILY without local stack and we want to make sure your situation is not broken when we do later changes. Meanwhile, enabling CONFIG_NET_IPv4 for SocketCAN without any network protocol seems a little bit strange, may you share the reason?

When using the minimal CONFIG_NET configuration for SocketCAN. Ifup would fail with the following error code. Fixes psock_socket: ERROR: socket address family unsupported: 2 This was caused because AF_INET got defined but inet_sockif() would return NULL because either ICMP, TCP or UDP dependency didn't met.

Hi @PetervdPerk-NXP, we're curious about the situation you encountered. We found situations (e.g. as a usrsock client) that need to use AF_INET as NET_SOCK_FAMILY without local stack and we want to make sure your situation is not broken when we do later changes. Meanwhile, enabling CONFIG_NET_IPv4 for SocketCAN without any network protocol seems a little bit strange, may you share the reason?

Hi @wengzhe this is because CONFIG_NET_IPv4 is enabled to get the IPv4 headers in to work with ip packets without having an ip sockets.


IGNITE-22278 Sql. Refactor base and planning contexts

https://issues.apache.org/jira/browse/IGNITE-22278
This patch refactors contexts used within sql engine:

BaseQueryContext is removed. Instead lightweight SqlOperationContext is introduced. All planning-related metadata moved to PlanningContext
PrepareService is not aware of SchemaManager. It accepts operation time as input and resolve active schema itself
schemaVersion renamed to catalogVersion in numerous places to better reflect semantic

Thank you for submitting the pull request.
To streamline the review process of the patch and ensure better code quality
we ask both an author and a reviewer to verify the following:
The Review Checklist

[ ] Formal criteria: TC status, codestyle, mandatory documentation. Also make sure to complete the following:
- There is a single JIRA ticket related to the pull request.
- The web-link to the pull request is attached to the JIRA ticket.
- The JIRA ticket has the Patch Available state.
- The description of the JIRA ticket explains WHAT was made, WHY and HOW.
- The pull request title is treated as the final commit message. The following pattern must be used: IGNITE-XXXX Change summary where XXXX - number of JIRA issue.
[ ] Design: new code conforms with the design principles of the components it is added to.
[ ] Patch quality: patch cannot be split into smaller pieces, its size must be reasonable.
[ ] Code quality: code is clean and readable, necessary developer documentation is added if needed.
[ ] Tests code quality: test set covers positive/negative scenarios, happy/edge cases. Tests are effective in terms of execution time and resources.

Notes

Apache Ignite Coding Guidelines

There are few places in sql-engine module where schemaVersion is still being used:

KeyValueModifyPlan has a field schemaVersion
KeyValueGetPlan has a field schemaVersion
SqlSchemaManager defines a method table(schemaVersion, tableId)
ExecutionServiceImpl FragmentCacheKey has a field schemaVersion

Are the names of these fields/variables kept unchanged on purpose?

@lowka my bad, thanks for noticing. I didn't use full text search, just changed names in those places I stumbled upon.
Renamed also mentioned places.