npm fails: "Cannot find module 'semver' (node v8.4.0)

If this is a question about how to use NVM4W, please use stackoverflow instead.
If this is an issue regarding antivirus, make sure you search the existing issues first.
My Environment

[ ] Windows 7 or below (not truly supported due to EOL - see wiki for details)

[ ] Windows 8

[ ] Windows 8.1

[X] Windows 10

[ ] Windows 10 IoT Core

[ ] Windows Server 2012

[ ] Windows Server 2012 R2

[ ] Windows Server 2016

[ ] My Windows installation is non-English.

I'm using NVM4W version:

[ ] 1.1.6
[X] 1.1.5
[ ] 1.1.4
[ ] 1.1.3
[ ] 1.1.2
[ ] 1.1.1
[ ] Older
[ ] OTHER (Please Specify)

I have already...

[X] read the README to be aware of npm gotchas & antivirus issues.
[X] reviewed the wiki to make sure my issue hasn't already been resolved.
[X] verified I'm using an account with administrative privileges.
[X] searched the issues (open and closed) to make sure this isn't a duplicate.
[X] made sure this isn't a question about how to use NVM for Windows, since gitter is used for questions and comments.

My issue is related to (check only those which apply):

[ ] settings.txt
[ ] proxy support (Have you tried version 1.1.0+?)
[ ] 32 or 64 bit support (Have you tried version 1.1.3+?)
[ ] Character escaping (Have you tried version 1.1.6+?)
[X] A standard shell environment (terminal/powershell)
[ ] A non-standard shell environment (Cmder, Hyper, Cygwin, git)

Expected Behavior
Return correct version number.
Actual Behavior
module.js:491
throw err;
^
Error: Cannot find module 'semver'
at Function.Module._resolveFilename (module.js:489:15)
at Function.Module._load (module.js:439:25)
at Module.require (module.js:517:17)
at require (internal/module.js:11:18)
at Object. (C:\Users\leofu\AppData\Roaming\nvm\nvm\v8.4.0\node_modules\npm\lib\utils\unsupported.js:2:14)
at Module._compile (module.js:573:30)
at Object.Module._extensions..js (module.js:584:10)
at Module.load (module.js:507:32)
at tryModuleLoad (module.js:470:12)
at Function.Module._load (module.js:462:3)
module.js:491
throw err;
^
Error: Cannot find module 'semver'
at Function.Module._resolveFilename (module.js:489:15)
at Function.Module._load (module.js:439:25)
at Module.require (module.js:517:17)
at require (internal/module.js:11:18)
at Object. (C:\Users\leofu\AppData\Roaming\nvm\nvm\v8.4.0\node_modules\npm\lib\utils\unsupported.js:2:14)
at Module._compile (module.js:573:30)
at Object.Module._extensions..js (module.js:584:10)
at Module.load (module.js:507:32)
at tryModuleLoad (module.js:470:12)
at Function.Module._load (module.js:462:3)
Steps to reproduce the problem:
nvm install 8.4.0
nvm use 8.4.0
npm -v

This is an npm error, not entirely an NVM error. I'd suggest reinstalling node 8.4.0.... perhaps the npm download was bad or something was corrupted.

@coreybutler It won't work, keeps failing even deactivating, uninstalling, manually removing the folder reinstalling and reactivating. Same error.
I even copied the npm's node_modules dependencies from another working normal installation of node 8.5.0 and still having troubles. Could you look more into it, and see what the problem is?
The nvm is a really handy tool but not working anymore, and it's a pity :(

Not sure what to tell you.... I can install semver just fine with the same setup.

@coreybutler just opened a new issue with the details

My own environment and the steps I used to replicate the issue here (closed duplicate): #305

Same on the latest 8.8.1.

thanks @roman-spiridonov just ran into the same bug on node 8.8.1 installed via nvm on windows and your workaround seems to do the job

Seems to have also worked using the latest version of node (9.1.0).

seems npm thats installed from npm doesnt compatible with the node itself, you must download the zip and replace the npm module like @roman-spiridonov suggested

@coreybutler is this not going to be addressed?  I am seeing the exact same error exactly - anything above =< 8.0.
Unfortunately, I can't run npm i semver I get the same error.

@roman-spiridonov I don't find that "npm" is a folder, but a file in the downloaded .zip.  Replacing it with the downloaded one doesn't seem to resolve the semver issues for me (I know others have been successful)

I have the same problem.
The @roman-spiridonov 's workaround work for me.
node 8.9.1
npm 5.5.1

@hyndsite you need to look inside the node_modules directory - inside that is npm directory. Use that and it should work.

Thanks @powellian I found that yesterday and was going to post a new update to @roman-spiridonov message - that the correct path is %APPDATA%/nvm/v8.8.1/node_modules/npm
The "npm" file in the /nvm/vx.x.x  path helped to confuse the matter.

Thank you, it works, But now I am wondering why is the package that nvm downloads & the one we download is different ?

Solution:
If you encounter this issue and you're using Windows 10, enable long paths using Registry Editor or Local Group Policy Editor.
Ref: https://github.com/coreybutler/nvm-windows/issues/305#issuecomment-345024594
Ref: https://msdn.microsoft.com/en-us/library/aa365247(VS.85).aspx?f=255&MSPPError=-2147217396#maxpath

alternative it to move nvm root. do nvm root C:\nvm before installing new node.
if already installed, then:
nvm uninstall 8.x.x
nvm root C:\nvm
nvm install 8.x.x

I experienced the same problem (Error: Cannot find module 'semver').
Some hints to get you going:
File compare (using official zip file) showed that there are indeed > 4k files and folders missing under node_modules\npm. It looks like the unzipping is aborted. Checked for v8.9.1 and v8.9.4: all node_modules alphabetically behind libnpx are missing. Wouldn't be surprised if it relates to those ridiculously nested folder structure: ...\nvm\v8.9.4\node_modules\npm\node_modules\libnpx\node_modules\yargs\node_modules\read-pkg-up\node_modules\read-pkg\node_modules\load-json-file\node_modules\parse-json\node_modules\error-ex\node_modules\is-arrayish\
I took the current master of nvm-windows, added some debug information to the install function within nvm.go, compiled it (with Go 1.10 win x64) and exchanged the nvm.exe with the new one. Result:

The npm zip file which is downloaded to the temp directory is in fact the official one. (@benavern , @Akamaozu )
The zip file was fully extracted within the temp directory and moved to the version-specific folder. No missing files.

Now for the surprising part, as I tried finding the regression:

Checked out tag 1.1.6, compiled (without any changes), replaced nvm.exe with the new one, deleted v8.9.4, ran nvm install 8.9.4 => successful, no missing files
Checked out tag 1.1.5, compiled (without any changes), replaced nvm.exe with the new one, deleted v8.9.4, ran nvm install 8.9.4 => successful, no missing files
Replaced nvm.exe with the original one from the official nvm-windows setup (1.1.5), deleted v8.9.4, ran nvm install 8.9.4 => still error, files missing.

It looks for me like there is an issue with the build process and/or environment.
Would be great if someone else could try if recreating the nvm.exe via build.bat or go build src/nvm.go solves the problem for him/her as well.
HTH, codeshell

Delete npm folder from below folder
C:\Users\username\AppData\Roaming\npm
after install
npm install

Just ran into this issue today and this worked for me.

Open a bash terminal
CD into C:\Users[username]\AppData\Roaming\npm\node_modules\
should see a package.json
yarn install

helped me:
https://stackoverflow.com/questions/33870520/npm-install-cannot-find-module-semver

@codeshell Thanks for your analysis. I found the issue to be due to the long paths that are not supported on Windows. For me even after downloading npm zip file and replacing contents of C:\Users\yourname\AppData\Roaming\nvm\9.11.1\npm I got the error. In fact I could not copy all files from downloaded npm zip file due to long names.
To avoid this I uninstalled node version 9.11.1, then uninstalled nvm. Reinstalled nvm at C:\nvm. Now my normal 'nvm install 9.11.1' works just fine and 'npm' is also in good state confirmed by running 'npm -v'.
I know this is a pretty drastic fix but just need to do one time.

I followed These steps and it solved my issue

uninstall Node.js
Remove the content of the following folders
C:\Users<user-name>\AppData\Roaming\npm-cache
C:\Users<user-name>\AppData\Roaming\npm
C:\Program Files\nodejs
Then again install Node _https://nodejs.org/en/_

installing the node through nvm 1.6.0 worked for me

In my case, the paths were just too long.  I chose c:\nvm as the install directory version manager and c:\nodejs for the symlink directory. That seemed to resolve the issue for me.

I had the same problem with node v10.4.0 and the workaround from roman-spiridonov worked for me.
I had already removed %AppData%\npm etc. before installing nvm-windows.

Tried getting 10.4.1 up and running, had problems at first.
Got it to work after deleting the folder from install location manually and installing via nvm again. Not sure whether this is too long of a path (obviously not) C:\Users\muser\AppData\Roaming\nvm\v10.4.1.

Same problem with v10.5.0 and roman-spiridonovs solution worked for me as well.

I have the same probem when have the latest node v10.6.0, then I just uninstalled it and switched to v8.11.3, problem solved.
I also tried download directly the npm-v6.1.0.zip, it do have some errors when unzipping.

Experienced the same issue @shadeofgod with 10.6.0.  Switching to 8.11.3 solved it.

problem persists with 10.6.0-64bit for a complete clean first install. (no node/npm before).  roman-spiridonovs solution  continues to work (for me the npm-folder can now bew found in [...node]\node_modules\npm)

Why is this still an issue after almost an entire year?

Just encountered this issue on Windows 10.
Enabling Win32 long paths fixed the issue. See post from @apptaro (2018-02-15)
I feel, nvm under Windows should issue warnings if long paths aren't enabled. nvm install also should not fail silently.

For me:

nvm install 9.11.2 was the last version I found that worked through nvm.
Overwriting with the zip file from the website works on any version.
The long paths fix didn't seem to work (possibly I hadn't tried a machine restart after changing the registry setting though).

I believe @momochanmo had just forgotten to install the semver package in their project. It has the same error message but this is a totally different issue.
To recap: This thread is about the fact that nvm installs a corrupted version of npm with a missing/corrupted version of the semver package, which renders it inoperable.
The most likely root cause suggested so far is that a bug / behaviour change introduced into the Go compiler about 3 years ago causes an error that's being silently swallowed during installation. See https://github.com/coreybutler/nvm-windows/pull/370.
So if you know someone who works with Windows stuff and is enthusiastic about Go, now's a good time to tap them on the shoulder and offer them this excellent career development opportunity 😅

I followed These steps and it solved my issue

uninstall Node.js
Remove the content of the following folders
C:\Users\AppData\Roaming\npm-cache
C:\Users\AppData\Roaming\npm
C:\Program Files\nodejs
Then again install Node _https://nodejs.org/en/_

Following this worked for me. You are a life saver!!!!! thanks <3

I am using NVM for Node versions 10.21.1, 10.23.0, 12.20.0, 14.15.4

I cannot run "npm -v"

However, if I specify the actual location of npm - that works:
C:\Users\cclark\AppData\Roaming\nvm\v12.20.1\npm -v
I have tried:

delete directory of node version in C:\Users\cclark\AppData\Roaming\nvm\
download zip file of node version from https://nodejs.org/download/release/v12.20.1/
copy files from zip file to directory
run 'nvm use 12.20.1'

npm -v will not run - semver error
nvm version 1.1.7
Windows version 10.0.17763


fix: avoid jumping menu item when it is collapsing

I thought it was the Docusaurus bug, but actually such a jump lag happens because of the added margin in custom CSS, I think it is better to remove it.

Thanks, this looks very good!


Layout test failure in inspector/evaluate-in-console

A recent change to the VM makes the webkit layout test dart/inspector/evaluate-in-console fail.
For some reason, the class of the receiver in a thrown exception has changed from 'Test' to '`K2'.
Also, there is an "Observatory listening" message that is unexpected.
It looks like it is the change https://codereview.chromium.org//1322043002 that has caused this error.
The status file for these tests is at http://src.chromium.org/blink/branches/dart/2171_3/dartium/LayoutTests/TestExpectations
A new status line would have to be added at the top of the file, this would have to be committed (I think that this SVN repository is still writable - the main chromium branches became read-only a year ago), and the new revision needs to be set as "dartium_webkit_revision" in tools/deps/dartium.deps/DEPS.
The text diff between the expected and actual results is:
--- /mnt/data/b/build/slave/dartium-lucid64-inc-be/build/src/webkit/Release/layout-test-results/dart/inspector/evaluate-in-console-expected.txt
+++ /mnt/data/b/build/slave/dartium-lucid64-inc-be/build/src/webkit/Release/layout-test-results/dart/inspector/evaluate-in-console-actual.txt
@@ -1,3 +1,5 @@
+Observatory listening on http://<IP_ADDRESS>:42624
+CONSOLE INFO: Observatory listening at http://<IP_ADDRESS>:48570/
CONSOLE MESSAGE: Hello Instance of 'Window'
CONSOLE MESSAGE: foo
@@ -12,10 +14,10 @@
test.foo = 3 = 3
test.foo = 3
test.somePropertyThatDoesntExist = Uncaught Unhandled exception:
-Class 'Test' has no instance getter 'somePropertyThatDoesntExist'.
+Class '` K2' has no instance getter 'somePropertyThatDoesntExist'.
NoSuchMethodError: method not found: 'somePropertyThatDoesntExist'
-Receiver: Instance of 'Test'
+Receiver: Instance of ' K2'  Arguments: []  #0      Object._noSuchMethod (DART_CORE_LIBRARY_SOURCE_LOCATION)  #1      Object.noSuchMethod (DART_CORE_LIBRARY_SOURCE_LOCATION) @@ -23,10 +25,10 @@  #3      handleMessage (FILE_SOURCE_LOCATION/evaluate-in-console.dart:13:5)  test.toString() = "<Test instance with instanceField = new value>"  test.toString(1) = Uncaught Unhandled exception: -Class 'Test' has no instance method 'toString' with matching arguments. +Class ' K2' has no instance method 'toString' with matching arguments.
NoSuchMethodError: incorrect number of arguments passed to method named 'toString'
-Receiver: Instance of 'Test'
+Receiver: Instance of '` K2'
Tried calling: toString(1)
Found: toString()
#0      Object._noSuchMethod (DART_CORE_LIBRARY_SOURCE_LOCATION)

@sgmitrovic

Fixed in df29a93b0dfd


Add aws fulfillment app

lol @giantswarm/team-honeybadger ignore, i'm not sure why you're a code owner here, i'll fix it :d

lol @giantswarm/team-honeybadger ignore, i'm not sure why you're a code owner here, i'll fix it :D

That's a problem of the template. We own the template and this has to be changed via giantswarm/github ownership or manually in https://github.com/giantswarm/aws-fulfillment/blob/main/CODEOWNERS


HTTPs "strict: false" is not working

I am trying to monitor the API endpoint of a Kubernetes cluster.  The endpoint is using a self signed cert so I set the strict: false but I am getting a error.
Get https://<IP_ADDRESS>:6443/healthz: x509: certificate signed by unknown authority
Here is what i have in the monitor config section.
  - name: k8-istio2
    target: https://<IP_ADDRESS>:6443/healthz
    strict: false
    method: GET
    component_id: 4
    #metric_id: 4

    template:
      investigating:
        subject: "{{ .Monitor.Name }} - {{ .SystemName }}"
        message: "{{ .Monitor.Name }} check **failed** (server time: {{ .now }})\n\n{{ .FailReason }}"
      fixed:
        subject: "I HAVE BEEN FIXED"

    interval: 1
    timeout: 1
    threshold: 80
    expected_status_code: 200

I would hope marking it false would ignore the x509 error.

it now switched that was odd.

@andelhie did strict false worked?i still see issues when i used strict false on one of the api


MobileApplicationClient and non-https token redirects

I use MobileApplicationClient in a desktop application that doesn't rely on any other servers than the OAuth and resource ones. In order to avoid any token leakage, I instruct the server to redirect to an URI with a custom scheme, which is then catched by my application (which only can be done per-scheme). Something like the following redirect URI:
myapplication:access_token#access_token=...

Unfortunately, MobileApplicationClient.parse_request_uri_response doesn't think this URI is secure enough (since it's not HTTPS). But in fact it is more secure than having the OAuth server redirect to a third-party HTTPS server.

The above example is only hypothetical, the actual usecase involves a command-line application which can't catch any URIs at all, while the server supports only one auth flow.

Feel free to open a PR if still wanted.


Update urdf/model.h -> urdf/model.hpp

The old header is marked obsolete.

BTW for reference, seems the deprecation warning came in with a linting PR: https://github.com/ros2/urdf/pull/39

@sjahr shared this PR with me as an idea, which we could use here since MoveIt definitely can incur dependencies on rclcpp: https://github.com/moveit/moveit2/pull/2978

@rhaschke I took your PR and added SebC's proposed changes. :crossed_fingers: this fixes CI

@sjahr: I added srdfdom to the upstream workspace, which should fix CI.

Looks like workspace overlay doesn't work correctly: Although srdfdom is part of the upstream_ws, MoveIt still finds srdfdom headers in /opt/ros... Same issue in #3026.

I think there isn't anything we can do at the moment to get CI working - however, for the future, we can fix srdfdom to install it's headers slightly differently (into include/${PACKAGE_NAME} as noted in https://github.com/ros2/ros2/issues/1150) so that overlays could work - this is what most of the core ROS packages do to work around the underlay/overlay issue

Worst case @JafarAbdi and I already put in a new release of srdfdom for the next sync, so... yeah.

https://github.com/moveit/moveit2/pull/3026#pullrequestreview-2361148434

Do we need the selective include here in the moveit2 repo? As far as I understood, that was only necessary for srdfdom, which only has a single branch for ros2. Here, we have different branches for rolling and older releases.

The main branch is supposed to support multiple versions of ROS 2 because it acts as a "dev" branch that contains the latest (breaking) features and the distribution branches contain a stable version that is branched and only receives bug fixes (@tylerjw wrote a nice article about this in the moveit blog a while ago). Without the selective include we'd break support for Humble and Iron and personally, I'd be in favor of adding the selective includes at least for a year. Feel free to take what you need from https://github.com/moveit/moveit2/pull/3026


Change version to 2.1.0.

Changes for Releases page
Output time formatting is much better now, showing proper hours, minutes and seconds wording. Same pleasant numbers with better human ouput!

@ming13 what about example(s) of old vs new time output? Just to make it more clear.
What about #150?

@artem-zinnatullin Don’t think docs are worth mentioning, users download the script and not the documentation. References are fixed, so everything should work on the web.


[feature] support H265 video format

Hey I got an error "unknown cid 36" when merging. It seems cid 36 == H265 as defined in gomedia:
TS_STREAM_H265 TS_STREAM_TYPE = 0x24

Thanks in advance for adding this feature.

The latest version(v1.24.1) has supported H265，please try again.

The latest version(v1.24.1) has supported H265，please try again.

Thank you for the quick fix! Unfortunately, tried on this m3u8 but the merged file (mp4) is audio only. Without merging, all TS files can play video.

This is a mistake, please retry version v1.24.2 again.

This is a mistake, please retry version v1.24.2 again.

Yeah, working now. Thanks!


Update contributors.txt

there is no contributor named "tsuu2092" for this repo
verified using this
https://github.com/Avaiga/taipy/graphs/contributors

The contributor has changed its name, but the account still exists.

sir may I add his updated name/username?


Added command to refresh topseller

1. Why is this change necessary?
Topseller can currently only be refreshed via backend or cron.
2. What does this change do, exactly?
Adds a console command to refresh the topseller index.
3. Describe each step to reproduce the issue or behaviour.
4. Please link to the relevant issues (if any).
5. Which documentation changes (if any) need to be made because of this PR?
6. Checklist

[ ] I have written tests and verified that they fail without my change
[X] I have squashed any insignificant commits
[X] This change has comments for package types, values, functions, and non-obvious lines of code
[X] I have read the contribution requirements and fulfil them.

@FiveDigital the wrong frontend dependency has been fixed with Shopware 5.5.3 (https://github.com/shopware/shopware/pull/1262) 😃

Ah nice - the PR with the birthday party 😬 👍

It should pass now.

Hello,
thank you for creating this pull request.
I have opened an issue on our Issue Tracker for you. See the issue link: https://issues.shopware.com/issues/SW-23120
Please use this issue to track the state of your pull request.


Add git alias to diff tags from remote and prune local tags no longer…

See http://stackoverflow.com/questions/1841341/remove-local-tags-that-are-no-longer-on-the-remote-repository

The Stack Overflow license at the time that was posted was CC-BY-SA, which it's not clear is compatible with the MIT license. They've since switched, which is good.

Good catch Paul.
These look useful, however it most likely cannot be merged as-is because of the license compatibility issues with gtd.
For this to be merged, the new aliases should be added to the readme and a different snippet would need to be used.
Because of this (and the conflicts) I'm going to close this for now, but please feel free to open up a new pull request if those issues get resolved. :)


EntityPath should be deleted

when copy the Primary Connection String from SAS policy, it contains entity path inside the connection string, duplicate with queue name, should delete it.
for example:
"Endpoint=sb://{servicebus-name}.servicebus.windows.net/;SharedAccessKeyName=test-queue-sender;SharedAccessKey={SharedAccessKey}=;EntityPath=test-queue";
need change to:
"Endpoint=sb://{servicebus-name}.servicebus.windows.net/;SharedAccessKeyName=test-queue-sender;SharedAccessKey={SharedAccessKey}=;";

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

ID: 217f29ba-3552-f406-58d3-d2e0c3bd4d2c
Version Independent ID: 003342a6-6fc5-fae4-31f4-369b561cfd89
Content: Get started with Azure Service Bus queues
Content Source: articles/service-bus-messaging/service-bus-dotnet-get-started-with-queues.md
Service: service-bus-messaging
GitHub Login: @axisc
Microsoft Alias: aschhab

@tantingjun Thank you for providing feedback. We will review this and provide an update as appropriate.

@tantingjun The document is referencing the connection string from the shared access policy of the service bus namespace RootManageSharedAccessKey . If you copy the connection string from shared access policies of an entity like Queue or Topic than it will add the EntityPath attribute at the end of connection  string and you have to remove when you are passing it in the QueueClient or TopicClient .

@tantingjun Checking in to see if the above post helped answering your question.

@tantingjun Since we have not heard back from you we will now proceed to close this thread. If there are further questions regarding this matter, please tag me in your reply. We will gladly continue the discussion and we will reopen the issue.

I want to bring up this one again @KetanChawda-MSFT
Consider the following scenario:

Azure Function using SB Queue Trigger / Binding

[ServiceBusTrigger] and [ServiceBus] requires a queue name to be provided as the first parameter.
Users can spin up SB Namespace and Queue including tailored Authorization Rules for the Queue using Azure CLI.
However, with the latest CLI, I am not able to get the ConnectionString for an Authorization Rule without EntityPath.
Specifying the given connection string (including EntityPath ... ) in Azure Functions will result in a runtime exception.
This means I have to manually remove the EntityPath from connection string. However, if I could request the connection string without EntityPath using az servicebus queue authorization-rule key ... I would be able to handover the result directly to func settings ...
az --version
azure-cli                         2.0.81

command-modules-nspkg              2.0.3
core                              2.0.81
nspkg                              3.0.4
telemetry                          1.0.4

Extensions:
aks-preview                       0.4.17

I think the real takeaway here is that the documentation should be a little bit more helpful in pointing out that EntityPath should be stripped out under specific use cases.
Basically, it comes down to if someone was confused enough to open a ticket then the documentation failed.

bumping this thread for i have encountered "Microsoft.Azure.ServiceBus: NamespaceConnectionString should not contain EntityPath" when trying to connect to a queue ( my SAS policy was also constructed with the "manage" role)
Code example:
public void Run([ServiceBusTrigger("%QueueName%",
Connection = "QueueSaSConnectionStringPk")]string command, ILogger log)
{
It seems deleting the EntityPath at the end of the connection string makes it work???????
Before: " "CommandQueueSaSConnectionStringSk": "Endpoint=sb://<>.servicebus.windows.net/;SharedAccessKeyName=<>;SharedAccessKey=<>=;EntityPath=<>","
After: "QueueSaSConnectionStringPk": "Endpoint=sb://<>.servicebus.windows.net/;SharedAccessKeyName=<>;SharedAccessKey=<>=;",
I feel like a documentation update needs to happen, or a code change to correct this error.


Add Windows OS to tests workflow

Changes:

Add windows

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

[ ] Bugfix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Documentation Update
[ ] Code style update (formatting, renaming)
[ ] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[x] Other (please describe): Github Workflows

Testing
Requires testing

[ ] Yes
[x] No

Codecov Report
Base: 56.29% // Head: 56.29% // No change to project coverage :thumbsup:

Coverage data is based on head (f85ec29) compared to base (ee5b007).
 Consider uploading reports for the commit ecb9888 to get more accurate results

Additional details and impacted files
@@           Coverage Diff            @@
##           develop     #211   +/-   ##
========================================
  Coverage    56.29%   56.29%
========================================
  Files           57       57
  Lines         3693     3693
========================================
  Hits          2079     2079
  Misses        1527     1527
  Partials        87       87

Flag
Coverage Δ

unittests
56.29% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


Using a mesos credential interferes with the job scheduler's leader latch...

In the branch "jason/mesoscredential" I attempted to add support for specifying a mesos credential as a command-line flag. However this causes problems with the job scheduler's leader latch (Curator's LeaderLatch), causing it to return the active leader with an empty id.

Verified that this works once you specify a credentials flag (with principal + secret) on the mesos master. Thanks @adam-mesos for the help!

Note: Also need to use echo -n "secret" > secret_file to write the secret to file without trailing newline.

Once this is verified, please submit a PR with documentation on how to do the framework authentication with Chronos


Reject message on failure

If a message received by the plugin fails at the output stage (for example, due to an indexing issue in ES), is it possible to have the message rejected so that it is dead-lettered in RabbitMq?
What I'm currently seeing is that a message that fails to be indexed to ES is still ACKed and therefore is lost forever.

Version: logstash 6.8.2
Operating System: ubuntu 18.04
Config File:

input {
    rabbitmq {
      host => "blah.eu-west-2.compute.amazonaws.com"
      queue => "reading-elastic"
      durable => true
      arguments => {
          "x-dead-letter-exchange" => "reading-retry"
          "x-dead-letter-routing-key" => "elastic"
      }
   }
}
filter{
    mutate {
        add_field => {
            "deviceId" => "%{[payload][deviceId]}"
            "readingDate" => "%{[payload][readingDate]}"
            "value" => "%{[payload][value]}"
            "readingTypeId" => "%{[payload][readingTypeId]}"
            "collectionDate" => "%{[payload][collectionDate]}"
            "propertyReference" => "%{[payload][propertyReference]}"
            "propertyId" => "%{[payload][propertyId]}"
            "deviceSerialNumber" => "%{[payload][deviceSerialNumber]}"
            "manufacturerReference" => "%{[payload][manufacturerReference]}"
            "modelReference" => "%{[payload][modelReference]}"
        }

        remove_field => [ "[payload]", "[queuedAt]" ]
    }
    mutate {
        convert => { "value" => "float" }
    }
    date {
        match => [ "readingDate", "UNIX_MS" ]
    }
    date {
        match => [ "collectionDate", "UNIX_MS" ]
        target => "collectionDate"
    }
    date {
        match => [ "readingDate", "UNIX_MS" ]
        target => "readingDate"
    }
}
output {
  elasticsearch { hosts => ["https://blah.eu-west-2.es.amazonaws.com:443"]
                  index => "readings-%{+YYYY.MM.dd}"
  }
}

I have the same problem as you. I tried with many ways, but I have not success.
Today I opened a topic in elastic discuss, waiting for some help.
https://discuss.elastic.co/t/logstash-rabbitmq-input-send-ack-after-event-processed/203709
If it will not possible, I will try implement it and send a pull request, although I not a expert with ruby.
Thx.

There have been efforts in the past to add end-to-end ACKs to Logstash (which the above request would require; https://github.com/elastic/logstash/issues/8514), but these efforts have largely stalled out due to complexity and resulting poor performance.
Without end-to-end acknowledgement in the Logstash pipeline, the Elasticsearch Output Plugin supports the Dead Letter Queue, which persists failed events to disk along-side failure metadata, and the dead_letter_queue Input Plugin can be used in a separate pipeline to hand these events back over to another system or queue for later processing.


Integration test for REST endpoint

@stephane-segning
Wrote an integration test to the test REST endpoint of the Lynx scanner backend application.
[Add intergration test for REST endpoint](https://github.com/stephane-segning/lynx-scanner-
backend/pull/23/commits/0f442e1c9e94542c09d719be1dd9bf55ed6a7bf7)

@stephane-segning
Wrote an integration test to test the REST endpoint of the Lynx scanner backend application.
Add intergration test for REST endpoint

Who asked you to work on a ticket which is in backlog?

@stephane-segning
Sir i had no idea it was in the backlog. i took it cuz it was among the last ticket i worked on that's setting up github action workflow in the spring boot action.


Add new cases from metadata

Adds some test cases form the canonical json file as discussed in #204

A-we-some!


fix fix 'show create table' return null

Proposed changes

this pr is used to solve the problem caused by #11743 when run 'show create table'.
Issue Number:  close #11911
#7570

Problem summary
Describe your changes.
Checklist(Required)

Does it affect the original behavior:

[ ] Yes
[x] No
[ ] I don't know

Has unit tests been added:

[ ] Yes
[ ] No
[x] No Need

Has document been added or modified:

[ ] Yes
[ ] No
[x] No Need

Does it need to update dependencies:

[ ] Yes
[x] No

Are there any changes that cannot be rolled back:

[ ] Yes (If Yes, please explain WHY)
[x] No

Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

LGTM


Bump up version

Publish a new gem version

What is this new version for?

Me missing out on pushing the tag


kde crashes my entire chromebook

Please paste the output of the following command here: sudo edit-chroot -all
```name: focal
encrypted: no
Entering /mnt/stateful_partition/crouton/chroots/focal...
crouton: version 1-20220111101058~master:a9eafaee
release: focal
architecture: amd64
xmethod: xorg
targets: core,xorg
host: version 14388.52.0 (Official Build) stable-channel grunt
kernel: Linux localhost 5.10.83-13632-g02eb545eaaaf #1 SMP PREEMPT Wed Feb 2 22:50:26 PST 2022 x86_64 x86_64 x86_64 GNU/Linux
freon: yes

#### Please describe your issue: using the command startplasma-x11 crashes my entire chromebook

#### If known, describe the steps to reproduce the issue: sudo apt install plasma-desktop then using command startplasma-x11

yes KDE install the current chromium products , it seem to reset the machine on  ever -r install as soon as X starts
I use mate, xfce works fine


update active codes & test

Actually, I am not sure why these codes are listed. I remember now I removed them for the following reasons:

SVC has officially been discontinued and is obsolete: https://en.wikipedia.org/wiki/Salvadoran_colón
ZWL has officially been discontinued and is obsolete: https://en.wikipedia.org/wiki/Zimbabwean_dollar

You are correct about BYN though, the BYR has been replaced (last year): https://en.wikipedia.org/wiki/Belarusian_ruble
I'm not sure how I feel about adding SVC and ZWL back into this library.

Ouch, sounds complicated. I don't think I can argue...

Well if you could reduce the change to just BYN I'll merge it asap. Otherwise I'll merge it manually on Monday without the other changes :-)


Duplicated class documentation when extended and constructor is documented

When generating documentation for a class that extends another, and the base class has it's constructor documented, JSDoc generates duplicated documentation pages for the class that is being extended.
Input code
I was able to reproduce the bug on a minimal example project containing 2 files:
classes/Foo/index.js
/**
 * Represents foo.
 */
export class Foo {
    /**
     * @param {object} props - Initial properties.
     */
    constructor(props) {

    }
}

classes/Bar/index.js
import { Foo } from "../Foo/index.js";

/**
 * Represents bar.
 * @extends Foo
 */
export class Bar extends Foo {
    constructor(props) {
        super(props);
    }
}

JSDoc configuration
Not using any configuration files. Only running jsdoc -r ./classes without anything else. Default template.
JSDoc debug output
DEBUG: JSDoc 3.6.4 (Mon, 06 Apr 2020 19:30:09 GMT)
DEBUG: Environment info: {"env":{"conf":{"plugins":[],"recurseDepth":10,"source":{"includePattern":".+\\.js(doc|x)?$","excludePattern":"(^|\\/|\\\\)_"},"sourceType":"module","tags":{"allowUnknownTags":true,"dictionaries":["jsdoc","closure"]},"templates":{"monospaceLinks":false,"cleverLinks":false,"default":{"outputSourceFiles":true}}},"opts":{"_":["./classes"],"debug":true,"recurse":true,"destination":"./out/","encoding":"utf8"}}}
DEBUG: Parsing source files: ["D:\\Wazy\\Projects\\web\\jsdoc-test\\classes\\Bar\\index.js","D:\\Wazy\\Projects\\web\\jsdoc-test\\classes\\Foo\\index.js"]
Parsing D:\Wazy\Projects\web\jsdoc-test\classes\Bar\index.js ...
Parsing D:\Wazy\Projects\web\jsdoc-test\classes\Foo\index.js ...
DEBUG: Finished parsing source files.
DEBUG: Adding inherited symbols, mixins, and interface implementations...
DEBUG: Adding borrowed doclets...
DEBUG: Post-processing complete.
Generating output files...
Finished running in 0.81 seconds.

Expected behavior
This should generate one page with documentation for the Foo class, and another page with documentation for the Bar class, with a link to the Foo documentation.
Current behavior
JSDoc is generating Bar.html with documentation for the Bar class, and Foo.html, BarFoo.html and BarBarFoo.html with documentation for the Foo class with linking messed up.
Bar.html looks normal:

Foo.html displays Foo documentation, but with the sidebar showing the other Foo pages and a "Classes" section with a link to Foo.html itself:

Both BarFoo.html and BarBarFoo.html shows the same, a Foo class that is inside Bar and inherits from Foo (linked to Foo.html) and have the same documentation that's present in Foo.html:

Your environment

Software
Version

JSDoc
3.6.4

Node.js
10.14.2

npm
6.4.1

Operating system
Windows 10 1909 (Build 18363.778)

A (not elegant) workaround I found was to first declare the classes and assign them to a differently named variable, then export them later with the correct name. Like:
classes/Foo/index.js
/**
 * Represents foo.
 * @class
 * @name Foo
 * @param {object} props - Initial properties.
 */
let foo = class Foo {
    constructor(props) {

    }
}

export const Foo = foo;

classes/Bar/index.js
import { Foo } from "../Foo/index.js";

/**
 * Represents bar.
 * @class
 * @name Bar
 * @extends Foo
 */
let bar = class Bar extends Foo {
    constructor(props) {
        super(props);
    }
}

export const Bar = bar;

This generated the right documentation, with only two pages for the classes.
Foo.html

Bar.html

A big downside is that every exported class that extends another one will need to be changed to something like that, sometimes in a huge codebase.


fix(composer) Updated multisites version to symbiote vendor namespace

Just double checking there's not some particular reason this was left on a version that has the silverstripe-australia vendor namespace?

No issues here. The vendor name was changed across everything, however dependency versions haven't been updated to match (the plan was to do this over time rather than everything immediately, since this introduced the risk of breaking things).


Persistency model changes

Currently supported persistency types are:

cache volume
ephemeral volume

These changes are over csi v1.0, so might not work on kuberntes < v 1.13. The idea is we should maintain pre csi-1.0 changes in a branch(csi-0.0.3). I will review supported persistency models within the limitations of csi v0.0.3 and submit PR to csi-0-0.3 branch.

Amarnath Valluri<EMAIL_ADDRESS>writes:

What you are saying is that users need to rewrite their app deployment logic and can't use controllers like ReplicaSet.

"cache" volume are best suits for ReplicaSet/Deployment . Pre-create
the cached PVC with no of replicas and ask to use that PVC by
ReplicaSet.

Whether such a ReplicaSet should use "cache" or "ephemeral" volumes
depends on the application. The app might expect empty volumes on
startup and might get confused when it finds old data when using "cache"
volumes. It's also a waste of disk space to keep the data around after
the app has terminated if the data is not going to be used again.

and "ephemeral" volumes are supposed to use by StatefulSet, because
StatefulSets supports volumeClaimTemplate where each volume tied to
a PVC, the volumes are not shared.

StatefulSet is meant for "stateful" applications, i.e. those which need
to retain data across restarts. I can imagine that also those apps may
need local, ephemeral storage, but the way
https://akomljen.com/kubernetes-persistent-volumes-with-deployment-and-statefulset/
describes it, volumeClaimTemplate was meant to provide each pod with its
own persistent volume.

@pohly, updated the document with Usage details, can you check if it helps.

@okartau and @pohly  I updated the PR with:

reverting ephemeral support
merged default {identity,node}servers code with actual implementation
updated the documentation with persistent models and usage.

That doesn't look right. I did make push-images before rebuilding the cluster, so I should be running the latest driver. However, this is hard to verify because the driver does not identify itself in the log output and has no unique version number. I've filed #183 to track this.
From the logs it looks like the driver treated this volume as a cache volume?
$ kubectl log pmem-csi-controller-0 pmem-driver
...
I0301 10:35:10.049651       1 glog.go:58] GRPC call: /csi.v1.Controller/CreateVolume
I0301 10:35:10.049673       1 glog.go:58] GRPC request: name:"pvc-b0354387-3c0d-11e9-895f-deadbeef0100" capacity_range:<required_bytes:8589934592 > volume_capabilities:<mount:<fs_type:"ext4" > access_mode:<mode:SINGLE_NODE_WRITER > > accessibility_requirements:<requisite:<segments:<key:"kubernetes.io/hostname" value:"host-0" > > requisite:<segments:<key:"kubernetes.io/hostname" value:"host-1" > > requisite:<segments:<key:"kubernetes.io/hostname" value:"host-2" > > requisite:<segments:<key:"kubernetes.io/hostname" value:"host-3" > > preferred:<segments:<key:"kubernetes.io/hostname" value:"host-0" > > preferred:<segments:<key:"kubernetes.io/hostname" value:"host-1" > > preferred:<segments:<key:"kubernetes.io/hostname" value:"host-2" > > preferred:<segments:<key:"kubernetes.io/hostname" value:"host-3" > > >
I0301 10:35:10.049861       1 glog.go:79] CreateVolume: Name: pvc-b0354387-3c0d-11e9-895f-deadbeef0100 req.Required:<PHONE_NUMBER> req.Limit: 0
I0301 10:35:10.049965       1 glog.go:79] Connecting to <IP_ADDRESS>:10001
I0301 10:35:10.114505       1 glog.go:79] node host-3 has requested capacity
I0301 10:35:10.114536       1 glog.go:79] Connecting to <IP_ADDRESS>:10001
I0301 10:35:10.181366       1 glog.go:79] node host-1 has requested capacity
I0301 10:35:10.181404       1 glog.go:79] Connecting to <IP_ADDRESS>:10001
I0301 10:35:10.249569       1 glog.go:79] node host-2 has requested capacity
I0301 10:35:10.249621       1 glog.go:79] Found nodes: [host-3 host-1 host-2]
I0301 10:35:10.249667       1 glog.go:79] CreateVolume: Record new volume as {b03c6245-3c0d-11e9-ba0d-26c6b0ca2305 pvc-b0354387-3c0d-11e9-895f-deadbeef0100<PHONE_NUMBER> 1  true fsdax}

I doubt if your cluster is built on https://github.com/intel/pmem-CSI/pull/177/commits/e81ec79a014f79487060584559a6cfec6233aaab . The logs you shared

node host-3 has requested capacity

are not present in this commit. Can you please verify this.

Indeed, I was one commit before the persistency changes. We need this embedded version number to catch such mistakes faster :-/
I'll continue testing.

Commit message e81ec79:

the newly created volume to that node by using 'Volume.Topology'. OC has to make

s/OC/The container orchestrator/
Done

You've spelled "Cache" and further down also "Persistent" with capital letter when talking about the model. I think "cache volume" and "persistent volume" are normal English words and not specific names, so normal capitalization seems more appropriate.

s/Cache/cache, s/Persistent/persistent. Done.

deploy/kubernetes-1.13/pmem-pvc.yaml says storageClassName: pmem-csi-sc # defined in pmem-csi.yaml. That should say deploy/kubernetes-1.13/pmem-storageclass.yaml.

Fixed the comment.

Offline, @okartau agreed to merge this change.


Sk/terraform changes

to: @airbnb/binaryalert-maintainers
size: small
resolves #
Background
I just started to setup binary alert in my environment. I had two issues wrt terraform.

Referencing the local terraform modules.
missed carbon_black_timeout terraform variable.

Changes

Summary of changes
...

Testing
Steps for how this change was tested and verified

Coverage remained the same at 90.52% when pulling 6de91bae84297dac1c6e6824d45a0a11ba6648d6 on sivakg2000:sk/terraform-changes into 3877787c9ec6acd9b289c586481324faa5c0a5e2 on airbnb:master.


Driver framework

@LorenzMeier Not really to merge yet, but you can start to try it. I've integrated DriverFramework into ADCSIM and GYROSIM.

Looking good in the diff.

Nice! Can we get this into shape so it builds with Travis?

sec, I might have fixed this, pushing..

I ran into two issues I need to resolve: One is you hardcoded clang-3.6 in the DriverFramework. Can we fix that? The second one is related to Mac Os differences and I have already resolved them last time.

And we either need to move the repo to PX4 or you need to give me permissions to push.

Almost got this linking with a few changes in the DriverFramework:
Undefined symbols for architecture x86_64:
  "DriverFramework::DevMgr::releaseHandle(DriverFramework::DevHandle&)", referenced from:
      _adcsim_main in libplatforms__posix__drivers__adcsim.a(adcsim.cpp.o)
      gyrosim::test() in libplatforms__posix__drivers__gyrosim.a(gyrosim.cpp.o)
  "DriverFramework::DevMgr::getHandle(char const*, DriverFramework::DevHandle&)", referenced from:
      _adcsim_main in libplatforms__posix__drivers__adcsim.a(adcsim.cpp.o)
      gyrosim::test() in libplatforms__posix__drivers__gyrosim.a(gyrosim.cpp.o)
      gyrosim::reset() in libplatforms__posix__drivers__gyrosim.a(gyrosim.cpp.o)
  "DriverFramework::DevObj::updateNotify()", referenced from:
      GYROSIM::_measure() in libplatforms__posix__drivers__gyrosim.a(gyrosim.cpp.o)
      GYROSIM_gyro::parent_poll_notify() in libplatforms__posix__drivers__gyrosim.a(gyrosim.cpp.o)
  "DriverFramework::DevObj::setSampleInterval(unsigned int)", referenced from:
      GYROSIM::_set_sample_rate(unsigned int) in libplatforms__posix__drivers__gyrosim.a(gyrosim.cpp.o)
  "DriverFramework::DevObj::stop()", referenced from:
      vtable for ADCSIM in libplatforms__posix__drivers__adcsim.a(adcsim.cpp.o)
      GYROSIM::~GYROSIM() in libplatforms__posix__drivers__gyrosim.a(gyrosim.cpp.o)
      vtable for GYROSIM in libplatforms__posix__drivers__gyrosim.a(gyrosim.cpp.o)
      vtable for GYROSIM_gyro in libplatforms__posix__drivers__gyrosim.a(gyrosim.cpp.o)
  "DriverFramework::DevObj::start()", referenced from:
      vtable for ADCSIM in libplatforms__posix__drivers__adcsim.a(adcsim.cpp.o)
      GYROSIM::start() in libplatforms__posix__drivers__gyrosim.a(gyrosim.cpp.o)
      vtable for GYROSIM_gyro in libplatforms__posix__drivers__gyrosim.a(gyrosim.cpp.o)
  "DriverFramework::DevObj::devIOCTL(unsigned long, void*)", referenced from:
      vtable for ADCSIM in libplatforms__posix__drivers__adcsim.a(adcsim.cpp.o)
      GYROSIM::devIOCTL(unsigned long, void*) in libplatforms__posix__drivers__gyrosim.a(gyrosim.cpp.o)
      GYROSIM::gyro_ioctl(unsigned long, void*) in libplatforms__posix__drivers__gyrosim.a(gyrosim.cpp.o)
      GYROSIM_gyro::devIOCTL(unsigned long, void*) in libplatforms__posix__drivers__gyrosim.a(gyrosim.cpp.o)
  "DriverFramework::DevObj::devWrite(void*, unsigned long)", referenced from:
      vtable for ADCSIM in libplatforms__posix__drivers__adcsim.a(adcsim.cpp.o)
      vtable for GYROSIM in libplatforms__posix__drivers__gyrosim.a(gyrosim.cpp.o)
      vtable for GYROSIM_gyro in libplatforms__posix__drivers__gyrosim.a(gyrosim.cpp.o)
  "DriverFramework::DevObj::DevObj(char const*, char const*, DriverFramework::DeviceBusType, unsigned int)", referenced from:
      ADCSIM::ADCSIM(unsigned int) in libplatforms__posix__drivers__adcsim.a(adcsim.cpp.o)
      GYROSIM::GYROSIM(char const*, char const*, Rotation) in libplatforms__posix__drivers__gyrosim.a(gyrosim.cpp.o)
      GYROSIM_gyro::GYROSIM_gyro(GYROSIM*, char const*) in libplatforms__posix__drivers__gyrosim.a(gyrosim.cpp.o)
      GYROSIM_gyro::GYROSIM_gyro(GYROSIM*, char const*) in libplatforms__posix__drivers__gyrosim.a(gyrosim.cpp.o)
  "DriverFramework::DevObj::~DevObj()", referenced from:
      ADCSIM::~ADCSIM() in libplatforms__posix__drivers__adcsim.a(adcsim.cpp.o)
      GYROSIM::~GYROSIM() in libplatforms__posix__drivers__gyrosim.a(gyrosim.cpp.o)
      GYROSIM_gyro::~GYROSIM_gyro() in libplatforms__posix__drivers__gyrosim.a(gyrosim.cpp.o)
      GYROSIM_gyro::~GYROSIM_gyro() in libplatforms__posix__drivers__gyrosim.a(gyrosim.cpp.o)
  "DriverFramework::SyncObj::lock()", referenced from:
      ADCSIM::devRead(void*, unsigned long) in libplatforms__posix__drivers__adcsim.a(adcsim.cpp.o)
      ADCSIM::_measure() in libplatforms__posix__drivers__adcsim.a(adcsim.cpp.o)
  "DriverFramework::SyncObj::unlock()", referenced from:
      ADCSIM::devRead(void*, unsigned long) in libplatforms__posix__drivers__adcsim.a(adcsim.cpp.o)
      ADCSIM::_measure() in libplatforms__posix__drivers__adcsim.a(adcsim.cpp.o)
  "DriverFramework::SyncObj::SyncObj()", referenced from:
      ADCSIM::ADCSIM(unsigned int) in libplatforms__posix__drivers__adcsim.a(adcsim.cpp.o)
  "DriverFramework::SyncObj::~SyncObj()", referenced from:
      ADCSIM::~ADCSIM() in libplatforms__posix__drivers__adcsim.a(adcsim.cpp.o)
  "DriverFramework::DevHandle::read(void*, unsigned long)", referenced from:
      _adcsim_main in libplatforms__posix__drivers__adcsim.a(adcsim.cpp.o)
      gyrosim::test() in libplatforms__posix__drivers__gyrosim.a(gyrosim.cpp.o)
  "DriverFramework::DevHandle::ioctl(unsigned long, void*)", referenced from:
      gyrosim::test() in libplatforms__posix__drivers__gyrosim.a(gyrosim.cpp.o)
      gyrosim::reset() in libplatforms__posix__drivers__gyrosim.a(gyrosim.cpp.o)
  "DriverFramework::DevHandle::~DevHandle()", referenced from:
      _adcsim_main in libplatforms__posix__drivers__adcsim.a(adcsim.cpp.o)
      gyrosim::test() in libplatforms__posix__drivers__gyrosim.a(gyrosim.cpp.o)
      gyrosim::reset() in libplatforms__posix__drivers__gyrosim.a(gyrosim.cpp.o)
  "DriverFramework::Framework::initialize()", referenced from:
      _main in main.cpp.o
  "vtable for DriverFramework::DevHandle", referenced from:
      _adcsim_main in libplatforms__posix__drivers__adcsim.a(adcsim.cpp.o)
      gyrosim::test() in libplatforms__posix__drivers__gyrosim.a(gyrosim.cpp.o)
      gyrosim::reset() in libplatforms__posix__drivers__gyrosim.a(gyrosim.cpp.o)
  NOTE: a missing vtable usually means the first non-inline virtual member function has no definition.
ld: symbol(s) not found for architecture x86_64

Test output:
Added driver 0x7fff5736e828 /dev/test0
Read 3 messages
message 0: 9951
message 1: 9949
message 2: 9950
Read 12 bytes (message = 4 bytes)
Read 3 messages
message 0: 19932
message 1: 19933
message 2: 19931
ioctl TEST_IOCTL_RESULT received
Read 3 messages
message 0: 19932
message 1: 19933
message 2: 19934
Read 3 messages
message 0: 19932
message 1: 19933
message 2: 19934
test PASSED (0)
Stopped samples
timed out 60
test PASSED (60)
timed out 60
test FAILED (60)

I got it to link, but I'm not sure how to test / proceed from here.

changes pushed. https://github.com/PX4/DriverFramework created and changes pushed as well.

Did accidentally delete the branch, but its all back to normal, looking forward to the CI results.

So the remaining work is:

Enable c++11 mode for the standalone lib target
Not set the CXX flags for the included in PX4 target
Fix building for the arm-none-eabi targets

If we get there we have the full port in place and won't need to go back to compilers.

@mcharleb I've updated to your most recent driver framework version and kicked the unit tests.


Merge variable paragraphs into one in overseas passports

We used to have three nearly identical paragraphs for countries with different
IPS configuration. I've suggested a content designer the meaning of those
variations is the same and they advised always using the first variation.

LGTM :+1:


Correcting path recording in the recent directory list

Fixes Issue #49453. Paths ending in slashes should now be treated the same as paths not ending in a slash in editor pop-up windows.
The bug arises from string's get_file() function only getting the path ending when the file name is after the final slash(/). Thus, I've added an if statement and a string::erase to revise the string in the event that a user enters a path ending in a slash.
Bugsquad edit: Fix #49453

In the end I merged #49604 which was slightly more efficient using substr() instead of erase(), as erase() calls left() + substr():
void String::erase(int p_pos, int p_chars) {
	*this = left(MAX(p_pos, 0)) + substr(p_pos + p_chars, length() - ((p_pos + p_chars)));
}

But both solutions were good and equivalent, thanks for your contribution!


NativeAOT support for GarnetServer

This PR makes progress towards supporting NativeAOT publish of GarnetServer. For now, NativeAOT support for the nuget itself is out of scope as I suspect the users first and foremost care about the application itself.
If the size of PR gets too large, it may be split into multiple as there are a few areas that need to be refactored to be AOT-compatible:

Custom "configuration binder" for Options and RedisOptions
Options validator
ArrayCommands

Ideally, it should overall improve the state of codebase as there are existing tools like System.CommandLine or M.E.C.ConfigurationBinder (or similar) which provide the features required by Garnet in a more robust, trim and AOT compatible way.

@microsoft-github-policy-service agree

Hey @neon-sunset! Thanks for your willingness to contribute to Garnet!
I'm not sure if what you're suggesting here is possible to support, as we do support custom commands that are dynamically loaded from local dlls on the server (See RespServerSession.RegisterCustomCommands in Garnet.server/Resp/ArrayCommands.cs).
Let me know what you think!
Tal.

It maybe possible to introduce a compile time feature-switch for the custom command support, which can be enabled by default but toggled by the developers who want the AOT benefits.
I haven't investigated how much work introducing such switch would be in Granet's case but the feature switches are common approach in .NET to toggle some functionality that can't be trimmed. The .NET runtime itself uses such feature switches, for example, to disable and trim reflection stack in its entirety.

@TalZaccai @PaulusParssinen Indeed, I was mostly going over the list of trim and AOT warnings, and either addressing them or writing down for future work.
Yes, it makes sense to guard the dependent loading with a check and add an informative error else clause when NAOT is targeted. Once NAOT binaries are published and released, there could simply be a notice regarding JIT-dependent feature(s). I don't think it makes sense to add a toggle to explicitly disable this feature for JIT deployment too, or at least, if that is still desired, it can be done separately. I will continue to work on this a little bit later, thank you for the assistance :)

The PR is rather out of date, so we will close it for now. When you get back to this, it would be great to re-open a new PR from the latest. Thanks all!


No options for the flat lit toon shader

when i select the flat lit toon shader the inspector is blank, i cant add outlines, change the rendering mode, anything, the other cubed shaders show options properly, ive tried deleting, reimporting, then restarting my unity but no luck, materials that the shader was put on before this started happening still show their options, but new ones do not

This doesn't sound like an issue with the shader, and I can't repro it. make sure you've loaded the editor scripts for the toon shader, and not just the shader files.


[Backport 1.4.latest] Test ddtrace dependency range (#733)

Backport #733

This is only needed for older versions.


Addition of detachment flag to parameter set

To kill a detached dynamodb, use the stopChild command with the child.
Highly recommended to use the async await functionality from ES8+ as it
saves a lengthy promise chains.
Fixed the verbose flag, to default to false
Fixed a type on the child.close that stated start instead of close
Added -Xrs flag to be able to kill the child without running into exit
code 143.

Thanks! Will update in npm shortly


[C++][Parquet] On switching from dictionary to the fallback encoding, an incorrect encoding is set

Reporter: Uwe Korn / @xhochy
Assignee: Uwe Korn](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=uwe) / @xhochy
Note: This issue was originally created as PARQUET-760. Please see the migration documentation for further details.

Uwe Korn / @xhochy:
PR: https://github.com/apache/parquet-cpp/pull/182

Wes McKinney / @wesm:
Issue resolved by pull request 182
https://github.com/apache/parquet-cpp/pull/182


[Symfony] Skip sprintf no space on StringToArrayArgumentProcessRector

Given the following code:
use Symfony\Component\Process\Process;

$command = sprintf("FOO=%s", 10);

$process = new Process($command);

it currently produce:
-$command = sprintf("FOO=%s", 10);
+$command = ['FOO=%s'];

which should be skipped.
Fixes https://github.com/rectorphp/rector-symfony/issues/188

Fixed 🎉 /cc @Blacksmoke16

All checks have passed 🎉 @TomasVotruba it is ready for review.


[Power Automate] token name should display names

Describe the Bug with repro steps
https://msazure.visualstudio.com/One/_workitems/edit/17527907
Workflow JSON
No response
Screenshots or Videos
No response
Browser
Chrome
Additional context
No response

Dupe of #1764 and #1690.


fix: update proposal parsing

[x] update Proposal46 type to include missing fields
[x] add terra.sc to url whitelist

TODO

[ ] populate gov versions for chains in asset repo
[ ] use strategy pattern to detect governance version and parse results based on gov version

Current
https://station.terra.money/proposal/phoenix-1/4790

After
https://fix-terra-props-after-upgrad.station-1a1.pages.dev/proposal/phoenix-1/4790


Support of PHP54 - get_class(X) instead of X::class

Should fix #3

I will check it tonight, thank you @kachkaev

This is not working on my side. I got [Symfony\Component\Debug\Exception\ContextErrorException]                         Notice: Use of undefined constant RouteCollection - assumed 'RouteCollection'   for each replacement.

I close this PR in favor of 514d007470e7f357a5c648ee248503158a4ede78. I have replace get_class(CLASS) with FQCN and remove test to rewrite them with phpspec (they are currently broken and unmaintanable).
Thank you.

Cool, thanks!


Documentation for Krishnamurthy Number

I would like to add an article for Krishnamurthy Number. The basic layout for the article will be:
What is Krishnamurthy Number?
Explanation for Krishnamurthy Number
Algorithmic Steps
Code (Use C++/Java and Python; At least two languages should be present and pick up code from NeoAlgo with apt credits to author)
Sample I/O
Time & Space Complexity
This article should be between 500-700 words in length. You should use traditional Markdown to prepare the content and the use of external images is prohibited. You can however create your own images. Run a proper Grammarly Lint check before submitting the PR.
Have you read the Contributing Guidelines on Pull Requests?
YES

Kindly assign me this issue @HarshCasper

Heya - Hope you are working on this ✨
We have just pushed some new features on the main so it would be great if you can pull the changes from the main branch, so that we don't run into any merge conflicts.
Second, I have some important notes for you. While adding the articles, it would be preferred if you use the mdx file extension instead of md. mdx provides us to combine Markdown + React. And we will be using it for a good reason.
First, we want to tab the codes like these:

Using standard markdown won't be beneficial for us. We can use some React Code to make it possible. Don't fret out if you don't know React. Here is an official documentation that you can refer to format the Code in separate tabs. Have a look and let me know if you are still in trouble.
Also try to keep the I/O samples same for both the Code. If it requires minor altercations, feel free to do them. Thanks!


Syntax for rendering ViewComponent

Instead of:
<%= render(ExampleComponent.new(title: "my title")) do %>
  Hello, World!
<% end %>

write something like:
<example-component title="my title">
  Hello, World!
</example-component>

Notes: Handle .with_collection too.

Idea: detect if component exists via defined?(MyComponent), so I can use the same syntax as for partials.

Better idea for syntax: everything that ia CamelCased will be treated as component.

Done.


[Fix #50] Update rubocop version to 0.73

TODO list here #50

Can we somehow control rubocop version so that we see that we are at the latest all the time?

@AleksSenkou sorry, I don't understand your question

@roman-dubrovsky I mean to know if we are at the latest rubocop version. Maybe we can add a badge to the readme showing if we are on the latest version
Is it better?

@AleksSenkou I still don't understand your idea. Why should we do it? Or how can this badge help us?
Anyway, let's continue this discussion in the separate issue (fill free to create a new one) or in the slack


minor updates given the feedback on issue 1767

tiny little changes, also this detection should be moved to prod since it has data ..

This PR was created by Automated Detection Testing Service :robot:
Tested detections:
Windows AdFind Exe :white_check_mark:

diskUsage: 528384
runDuration: 17.871s
scanCount: 29045


Implement registration process

Flow proposal

User registers with email and selects lab from drop-down menu
Lab-admin is notified and confirms registration. If Lab has no lab-admin associated, site-admin is notified and confirms registration
Lab- and site-admin get notified about new user

Closing in favor of #61


Remove arrow on Home page

Remove arrow on Home page (see image below)

Rationale
The arrow doesn’t currently do anything
Difficulty, impact:
|--(technical difficulty = easy?)--| -- high user importance (SHOULD have) -- |
Acceptance Criteria:

[ ]  Arrow on home page is removed

Steps for QA

Here is the iOS and android screenshots in that order:

Tested on iPhone 7 Plus (iOS 13.2.3) - AA Staging V1.12.0, server V1.3.18:
confirmed Arrow on Home Page was removed

Tested on Nexus 5 (Android 6.0.1) - AA Staging V1.12.0, server V1.3.18:
confirmed Arrow on Home Page was removed


Add warning when user tries to re-OCR proofread page

To avoid accidentally losing proofread text.

Being fixed in #403.


Add translation plan to CXX transpiler documentation

Add tables with how the Val nodes would be transpiled into CXX nodes (not yet complete). This forms a rough plan on what CXX nodes we need to build and how different Val structures translate to those nodes.

No objections but I also can't really evaluate it. It would be a lot more useful if it contained some code examples showing how these constructs might be translated.

This document aims at being a rough guide for me, to know what I should tackle. I doesn't need to be 100%; actually I would expect it to change parts of it, while we are working on the transpiler.
I'll merge it as is, and make changes to it, as we move along with the implementation.


Can't extend enums

Currently there is no way to extend enums in Dart. I want to extend an enum (which I can't directly modify) by adding a custom toString method. Neither of these work:
enum Attempt1 extends SomeEnum { ... }

class Attempt2 extends SomeEnum { ... }

I want to be able to do something like:
enum Letter {
  a, b, c
}

enum GroceryItem extends Letter {
  @override
  String toString() => switch (this) {
    Letter.a => 'Apple',
    Letter.b => 'Banana',
    Letter.c => 'Carrot',
  };
}

It would be great to also require that all enum constants be re-defined (almost as an override), if the subclass has a custom constructor, e.g.:
enum Letter {
  a, b, c
}

enum GroceryItem extends Letter {
  // There would be an error if any of these is not defined, since there is a custom constructor
  a('Apple'),
  b('Banana'),
  c('Carrot');

  final String _text;

  const Fruit(this._text);

  @override
  String toString() => _text;
}

I think this raises the issue though that a subclass of an enum should not be able to add additional enum constants, because that would break casting an object of the subclass type to the superclass type.

That is just not possible.
You cannot change the toString of the existing insurances of the enum type, if you don't have access to modifying the declaration.
If you could create a subclass with another toString, and an instance of that subclass which would have that toString method, then you have created a new insurance of the enum, different from all existing instances.
It's not the same enum element as the superclass instance that has the same name, or same index, because even element identity is object identity.
It will break exhaustiveness checking of switches.
To make that work, we'd have to completely change how enums work, with them not simply a known finite number of canonicalized instances of a final class.
We'd have to introduce some kind of logical identity, which more objects could share, and the enum type would not be an interface type, more like a logical, structural type containing a specific set of object enum element identities.
Not impossible, I think (after all of 5 minutes of contemplation), but a major change to the language.
It better be worth it.
(It might, if it can allow an enumeration to declare itself as containing a union of other, existing, enumerated values from other enums, which is a common request.)

I see. OK, so if we forget about overriding toString or other methods, what about simply being able to add methods or fields?
enum GroceryItem extends Letter {
  // There would be an error if any of these is not defined, since there is a custom constructor
  a('Apple'),
  b('Banana'),
  c('Carrot');

  final String text;

  const Fruit(this.text);
}

It will break exhaustiveness checking of switches.

Right, that's why I suggested that probably enum constants should not be able to be added in a subclass.
Basically I'm looking to extend the functionality of enums by adding properties and/or methods.
What about if this could be done as an extension or mixin?

Would an extension type work for your use case? These additions would only be resolved statically though.
enum Letter {
  a, b, c;
}

extension type GroceryItem(Letter l) {
  String get text => switch (l) {
    Letter.a => 'Apple',
    Letter.b => 'Banana',
    Letter.c => 'Carrot',
  };
}

void main() {
  final a = GroceryItem(Letter.a);
  print(a.text); // Prints 'Apple'
}

@parlough Yes, I think that solves my problem, although I can't test it, because I can't seem to figure out how to enable this (brand new) feature (I get an error in VS Code even after upgrading to the latest Dart >3.2.0 and Flutter beta versions).
I'll close this, since it looks like this is intended to work. Thanks!

@lukehutch Extension types are still experimental and in-progress. You'll have the best experience on 3.3.0 main or dev builds and you'll need to enable the inline-class experiment.
You should also be able to try them out on the DartPad main channel.


Some random changes to help with debugging/analysis

-Fixing null pointer
-Changes for smoother graph with datastax
-Added meter to track incoming requests
-Using shaded jar for datastax
-Added some logging

Looks ok to me.

Oh, also Travis seems to fail :-(. Probably just need a job restart.

@ChandraAddala , please also update the CHANGES.md to mention the upgrade to datastax driver 3.1.x

Coverage increased (+0.04%) to 76.043% when pulling a7f5901722eb424ebeea5294a52d130c20ebcbd4 on ChandraAddala:datastax-perf-issues into 9207c18b22409bf3f585f4f4a661e60e11ee0b15 on rackerlabs:master.

@shintasmith I had addressed your comments. Pls take a look

Coverage increased (+0.1%) to 76.11% when pulling 752ae1a8e6a0087fc5f54e3ab334c9938af26938 on ChandraAddala:datastax-perf-issues into 9207c18b22409bf3f585f4f4a661e60e11ee0b15 on rackerlabs:master.


[Feature]: Dedicated page for PHP under Web Dev

Is your feature request related to a problem? Please describe.
Similar to html, css, and js page creating a php page for webdev
Describe the solution you'd like
No response
Describe alternatives you've considered
No response
Additional context
No response

assign it to me

resolved


Needs to be packaged for Godot 4.2 and above

Sine Godot's plugin system changed to v2, packaging became a lot more complicated. If you have experience with this, don1t hesitate to push the packaged zip inot build.

Pleasure keep support for Godot 3 if you decide to make the plugin work for version 4 as there's still a big version 3 user base.
Thank you.

@Momo90k, Sure, I'm also using Godot 3 at the moment, and not planning to move up to v4 for quite a while, (which is why I don't even know how to package things properly)
I am planning to keep this updated for both v3 and v4 if I can, but my main focus is on v3, so nothing to worry about (yet).


[TESTING] Before ad change

https://github.com/DataDog/datadog-agent/tree/alex/before_ad_change

/azp run PR Changes


Mention docker-desktop log spam issue in Linux section of README

I ran into https://github.com/docker/desktop-linux/issues/102 today, which was filling up my /var/log/syslog file and thus also my root partition. (It was also filling up the systemd journal, but the systemd journal is capped at 4 GB on my system while I don't have syslog capped). We should probably update the README section for Linux devs to include the workaround, which is to create a systemd drop-in file in your user configuration location ($HOME/.config/systemd/user/docker-desktop-service.d), as follows:

Run mkdir -p $HOME/.config/systemd/user/docker-desktop-service.d
Create a file called $HOME/.config/systemd/user/docker-desktop-service.d/no-log-spam.conf (it can be any filename, as long as it's in that directory and ends in .conf) with the following content:

[Service]
StandardError=null

No urgency to this task, because we don't expect any new Linux devs to join the team in the next few weeks. But it would be nice to give any new Linux devs a heads-up so they don't also experience their hard disk filling up with debug log messages.

I thought we had installation instructions for Docker Desktop in the README, but it turns out we don't. So there isn't really a good place to put the mention of that bug in the README. Closing.

Actually, if we create developer instructions as suggested in #1265, then this would definitely belong in DEVELOPER-linux.md. So I'll tentatively reopen this, pending us making a decision on #1265.


Questions about discriminative_fine_tuning

In Section 5.4.3  " We find that assign a lower learn- ing rate to the lower layer is effective to fine-tuning BERT, and an appropriate setting is ξ=0.95 and lr=2.0e-5."
Compared to the code in https://github.com/xuyige/BERT4doc-Classification/blob/master/codes/fine-tuning/run_classifier.py#L812
Seem that you divide the bert layer into 3 part (4 layers for one part) and set different learning rate for each part.
Some questions about it:

How could the decay factor 0.95  match the number 2.6 in code ?
And the last classify layer seem not be contained , no need to set lr for it ?

Thank you for your issue!

The number 2.6 was set for the beginning experiments, after that, we use run_classifier_discriminative.py for discriminative fine-tuning.
The link to run_classifier_discriminative.py is https://github.com/xuyige/BERT4doc-Classification/blob/master/codes/fine-tuning/run_classifier_discriminative.py
The classifier layer is contained in run_classifier_discriminative.py.

Thanks for your reply, I will try it!


rate limited

Type: Bug
it seems to get stuck in a rate limited loop, where it just adds random numbers after please wait.
Ill wait 7 mins after it say wait 3 seconds, then it will say I need to wait 15 seconds, then 3 seconds, then 1 second.
It contiunes in this loop for an extremely long time
Extension version: 0.21.2
VS Code version: Code 1.94.2 (384ff7382de624fb94dbaf6da11977bba1ecd427, 2024-10-09T16:08:44.566Z)
OS version: Windows_NT x64 10.0.22631
Modes:

System Info

Item
Value

CPUs
Intel(R) Core(TM) i7-7700 CPU @ 3.60GHz (8 x 3600)

GPU Status
2d_canvas: enabledcanvas_oop_rasterization: enabled_ondirect_rendering_display_compositor: disabled_off_okgpu_compositing: enabledmultiple_raster_threads: enabled_onopengl: enabled_onrasterization: enabledraw_draw: disabled_off_okskia_graphite: disabled_offvideo_decode: enabledvideo_encode: enabledvulkan: disabled_offwebgl: enabledwebgl2: enabledwebgpu: enabledwebnn: disabled_off

Load (avg)
undefined

Memory (System)
31.87GB (23.36GB free)

Process Argv
--crash-reporter-id 16cb0f5b-70de-408b-aecd-6577600d258c

Screen Reader
no

VM
0%

A/B Experiments
vsliv368:30146709
vspor879:30202332
vspor708:30202333
vspor363:30204092
vscod805:30301674
binariesv615:30325510
vsaa593:30376534
py29gd2263:31024239
vscaat:30438848
c4g48928:30535728
azure-dev_surveyonecf:30548226
962ge761:30959799
pythongtdpath:30769146
pythonnoceb:30805159
asynctok:30898717
pythonmypyd1:30879173
2e7ec940:31000449
pythontbext0:30879054
accentitlementsc:30995553
cppperfnew:31000557
dsvsc020:30976470
pythonait:31006305
dsvsc021:30996838
9c06g630:31013171
a69g1124:31058053
dvdeprecation:31068756
dwnewjupytercf:31046870
impr_priority:31102340
nativerepl1:31139838
refactort:31108082
pythonrstrctxt:31112756
wkspc-onlycs-t:31132770
wkspc-ranged-t:31151552
cf971741:31144450
autoexpandse:31146404
iacca1:31156133
notype1cf:31157160
5fd0e150:31155592
icondisabled:31158250

The rate limits occur when you utilize an excessive amount of tokens in comparison to other users of Copilot chat. The number of seconds shown to you is based on completing the exact same request. If the request is changed in anyway then it will not be completed as you will not have enough tokens left in your pool.
The rate limit is something we're always adjusting and not something you should be hitting often. It's also not something that can really be fixed. Let me know if you're hitting this often and how you're hitting it!


Allow cacheback mode for disk devices

Signed-off-by: Cedric Hauber<EMAIL_ADDRESS>
What this PR does / why we need it:
Today Kubevirt only support writethough cache.
Writeback allow less secure but better io speed.
Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #
Special notes for your reviewer:
Release note:

Added Writeback cache support

@vladikr any insights?

I'm sorry, I've missed this...
@davidvossel  I think migration is possible with the recent QEMU. Let me double-check and update.

It seems (according to [1]) that migration with writeback will be allowed in libvirt 5.6, that we are not yet using.
[1] https://bugzilla.redhat.com/show_bug.cgi?id=1660575

We should be able to migrate workloads with disks that have write-back cache, after updating libvirt and qemu.
@cedbossneo would you be able to implement the changes @davidvossel has recommended ( except for the second and the third bullet)?

any updates on that?


add new Keen IO Tutorial

Description of the change: no change, just a ➕
Reason for the change: be helpful to customers
Link to original source: https://keen.io/docs/integrations/sendgrid/
@ksigler7

 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.

@ksigler7 got the cla signed :shipit:

thanks @elof. This is so great. Thanks again for taking the time to do this!!

Hello @elof,Thanks again for the PR! We want to show our appreciation by sending                                              you some swag. Could you please fill out                                              this form so we can send it to you? Thanks!                                             Team SendGrid DX


using "simu" instead of "sim"

It's not a bug, it's an idea。I strongly recommend changing "sim" to "simu". The "sim" is easy to confuse, especially when using sim card.

sim is a well-established abbreviation for simulate.
simu is not.
i guess you can just use "nuttx simulator" and "sim card" when it's confusing.

This would be a breaking change in lots of places (including docs). I don't think the benefit of the rename are good enough to justify the work, IMHO.


Add integration writing guide

We should write up a nice guide on how to write an integration under docs/.  An outline would be:

Two ways to write integrations to send data to Zulip: using the Zulip API (if the sending end can format the payloads appropriately) or by writing a webhook handler.  The former is easier and thus preferred, but not always possible.  Good example is generic git integration
For writing a webhook handler there are a bunch of examples in zerver/view/webhooks.py.
If the integration involved a hook, write tests in zerver/test_hooks.py.  Use fixtures so that the tests can run without any secret keys or internet access.
Remember to document in templates/zerver/integrations.html

I'd love it if someone were to pick a desired integration, implement it, and write such a guide in the process!
What I would recommend for actually developing a webhook integration is using a service like http://requestb.in/ to receive the webhook payload from the service, and then you can put that into a test fixture under zerver/fixtures (and write a test class in zerver/test_hooks.py), and then you can can do your testing mostly just using the fixed payload(s) from the cases you're interested via the Zulip test-backend command for just your new tests (see https://github.com/zulip/zulip/blob/master/README.dev.md#running-the-test-suite).

See http://zulip.readthedocs.org/en/latest/integration-guide.html for the new integration writing guide.

@timabbott
I think we can also mention something about most usefull decorators for webooks with short description of them.
I also propose to make integrations more standardized:
My solution:
https://github.com/zulip/zulip/pull/648/files
Split functionalities into Parser(access to payload) and into Handler(generate content).
I think it is more clearly way and easy to reproduce in the future. Zulip will have lot of integrations in the future and its should be easy to maintain.

Opened https://github.com/zulip/zulip/issues/660 for that idea, since I think it deserves its own discussion.


The parser of C# is so slow. Can you offer the dataset  processed by C# parser?

Could you try changing the antlr-python2-runtime to 4.5.3 (instead of 4.5.2) ?
That runs a lot faster. I think 4.5.2 has some kind of a performance bug.


[BUG] Texture colors are not saved.

Describe the bug
Texture's main colors are not saved. Then if I put in Diffuse (example) a color there instead of a texture. When I save the scene the color is not stored then when I load the color is again white. Same happen when Play and Stop.
To Reproduce
Steps to reproduce the behavior:

Go to a model without texture.
Click on Color.
Select one different from black
Play or Save scene and then Stop or Load scene.
See error

Expected behavior
Colors being saved.

Solved in commit 22f1b2f


How to change values separator?

Hello,
Is there any setting available after importing the plugin - that will let me change the delimiter for the selected values.
Thanks for your support.
Regards,
Rupesh R

@rupesh28
No, there is no option to do it from APEX App Builder. The intention was to be consistent with other native components where the default separator is ":".
But if you need to change it for the whole application you can just modify the pl/sql source and javascript file. At the moment:

in javascript it is just one variable C_VALUE_SEPARATOR.
in PL/SQL there are multiple lines where separator is used.

For the future release, I will consider exposing separator as the plugin attribute.
Btw. What is the reason behind that requirement?

@bostrowski Thanks for your response. I am trying to use multiples values selected in the list directly in a select query, to populate a grid. I was thinking if I can change the separator then I can directly pass it to the query without having to do any parsing.

@rupesh28
the current release doesn't support IG. The next release which is almost finished will support it.


Register to brightness notifications of the request screen only

Otherwise, you may hear notifications about brightness events of other screens. iOS allows externals screens to be attached. If these screens report brightness information, your implementation will hear notifications for those screens as well.

I see the API already allows the user to specify a screen. So you should be registering to notifications of that screen only.
    func subscribeToNotifications() {
        let center = self.notificationCenter
        center.addObserver(self,
                           selector: #selector(onScreenBrightnessDidChange),
                           name: UIScreenBrightnessDidChangeNotification,
                           object: screen!)
    }

Thank you! I will address it shortly.

This has been addressed in #3.


Cordova Support

Does Kadira support Cordova ?
I am using meteor build --debug ... to generate a APK file and install it on my android phone.
When I inspect my app (using USB Debugging & Chrome) I see the following error on my console:
GET http://<IP_ADDRESS>:39455/undefined/simplentp/sync 404 (Not Found)
When using a regular desktop or mobile browser everything goes fine...

Got this on iOS Cordova
This issue is related to #148
It is gone after I've set the whitelist
[Error] Failed to load resource: Origin http://meteor.local is not allowed by Access-Control-Allow-Origin. (errors, line 0)
[Error] XMLHttpRequest cannot load https://engine.kadira.io/errors. Origin http://meteor.local is not allowed by Access-Control-Allow-Origin. (m, line 0)

Thanks @xumx for updating. I hope we can't automatically add this to the app? Do you know a way to update this automatically.

XMLHttpRequest cannot load https://enginex.kadira.io/simplentp/sync.
No 'Access-Control-Allow-Origin' header is present on the requested resource.
The response had HTTP status code 522.

On Meteor <IP_ADDRESS> [release]
meteorhacks:kadira 2.23.0

We had a downtime.
Sorry about the issue.
Now everything is back online :)
On Sat, Aug 8, 2015 at 5:12 AM Damon Blais<EMAIL_ADDRESS>wrote:

XMLHttpRequest cannot load https://enginex.kadira.io/simplentp/sync.
No 'Access-Control-Allow-Origin' header is present on the requested resource.
The response had HTTP status code 522.
On Meteor <IP_ADDRESS> [release]
meteorhacks:kadira 2.23.0
—
Reply to this email directly or view it on GitHub
https://github.com/meteorhacks/kadira/issues/89#issuecomment-128859758.


Web UI Refused to Connect after Updating

Hello!
Firstly, thank you for the great work on this plugin. I just upgraded to the latest version of the plugin on my Raspberry Pi, and seem to be facing an issue where the Web UI if refusing to connect
Describe The Bug:
The Homebridge UI just prompted me for an update from version 4.18.0 to the latest (4.24.0). After clicking update (and then restart) on the Web UI, I get the error: the server refused to connect. I was using the   http://:8541 URL to connect to the UI.
Expected behavior:
The Web UI should work.
What I've tried
After the plugin stopped working, I've since tried:

Using the port 8080 (as mentioned in the current README of the project) to connect. Didn't work.
Upgrading homebridge to the latest version (from 1.0.4 -> 1.1.1)
Uninstalling and installing this package homebridge-config-ui-x again.
Tried adding the platform config to my homebrige config.json. After adding this explicitly, I now get the error mentioned in the logs below when running homebridge:

Logs:
[02/08/2020, 10:29:03] [HB Supervisor] OS: Linux 4.19.58-v7+ arm
[02/08/2020, 10:29:03] [HB Supervisor] Node.js v13.5.0 /usr/local/bin/node
[02/08/2020, 10:29:03] [HB Supervisor] Homebridge Path: /usr/local/lib/node_modules/homebridge/bin/homebridge
[02/08/2020, 10:29:03] [HB Supervisor] UI Path: /usr/local/lib/node_modules/homebridge-config-ui-x/dist/bin/standalone.js
[02/08/2020, 10:29:03] [HB Supervisor] Starting Homebridge with extra flags: -I
[02/08/2020, 10:29:04] [HB Supervisor] Started Homebridge v1.1.1 with PID: 24952
[02/08/2020, 10:29:06] [HB Supervisor] ERROR: The user interface threw an unhandled error
/usr/local/lib/node_modules/homebridge-config-ui-x/node_modules/uuid/dist/esm-browser/index.js:1
export { default as v1 } from './v1.js';
^^^^^^

SyntaxError: Unexpected token 'export'
    at wrapSafe (internal/modules/cjs/loader.js:1055:16)
    at Module._compile (internal/modules/cjs/loader.js:1103:27)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:1159:10)
    at Module.load (internal/modules/cjs/loader.js:988:32)
    at Function.Module._load (internal/modules/cjs/loader.js:896:14)
    at Module.require (internal/modules/cjs/loader.js:1028:19)
    at require (internal/modules/cjs/helpers.js:72:18)
    at Object.<anonymous> (/usr/local/lib/node_modules/homebridge-config-ui-x/node_modules/@nestjs/common/decorators/core/injectable.decorator.js:4:16)
    at Module._compile (internal/modules/cjs/loader.js:1139:30)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:1159:10)
[02/08/2020, 10:29:06] [HB Supervisor] Homebridge Process Ended. Code: null, Signal: SIGTERM

Homebridge Config:
{
  "bridge": {
    "name": "Homebridge",
    "username": "--",
    "port": 51826,
    "pin": "--"
  },
  "accessories": [
    {
      "accessory": "ServoSwitch",
      "name": "Lights"
    }
  ],
  "platforms": [
    {
      "platform": "BelkinWeMo",
      "name": "WeMo Platform"
    },
    {
      "platform": "config",
      "name": "Config",
      "port": 8541,
      "sudo": false
    }
  ]
}

Screenshots:

Environment:

Node.js Version: v13.5.0
NPM Version: 6.14.7
Homebridge Version: 1.1.1
Homebridge Config UI X Version: 4.24.0
Operating System: Raspbian (Linux 4.19.58-v7+ arm)
Process Supervisor: pm2

Upgrade Node.js.
13.0.0 to 13.6.0 have a bug that prevent a certain dependency from loading. Fixed in 13.7.0 or later (or 10.17.0 or later).

See https://github.com/oznu/homebridge-config-ui-x/releases/tag/4.22.0

Thank you so much for the quick reply! Upgrading Node to 14.7.0 fixed the issue


Nl

This PR/Translation is about #32 .
files translated:

[ ] def/--LOCALE-CODE--/about.cson
[ ] def/--LOCALE-CODE--/context.cson
[ ] def/--LOCALE-CODE--/menu_darwin.cson
[ ] def/--LOCALE-CODE--/menu_linux.cson
[ ] def/--LOCALE-CODE--/menu_win32.cson
[ ] def/--LOCALE-CODE--/settings.cson

validation

[ ] I've validated my translation locally by running

npm run validation -- --locale MY_LOCALE

resolving conflict according to PR #64 and #66
new 3 items required translation according PR #64, @laurensbrand  would you like to update them?

nl/about.cson

upToDate: "Atom is up to date!"
checkingForUpdates: "Checking for updates..."
checkUpdatesNow: "Check now"


panther7 suggestion + rename Available Updates to Software Updates

closes #558

You can squash into one commit.

I don't know how

Try, learn, example via git rebase -i main

https://gitready.com/advanced/2009/02/10/squashing-commits-with-rebase.html

Thanks! I am gonna take a look on that so I don't make the same mistake next time!


Get file extension from file name.

Hello ALASQL team,
I have got a new challenge:
I have got a field value like:
"Name":"W-LB-FD-3.3 testmethode rotatoire wrijving lab eigenmethode.doc"

And I need:
"fileName":"W-LB-FD-3.3 testmethode rotatoire wrijving lab eigenmethode", "fileType":"doc""

Any idea?
Kind regards,
Mario

Make a user defined function
alasql.fn.fileName = function(name) {
    var all = name.split('.')
    all.pop();
    return all.join('.');
};

alasql.fn.fileType = function(name) {
    return name.split('.').pop();
};

So you can
select fileName(name) as fileName, fileType(name) as fileType from ?
Code not tested


Apologies for creating an issue, new to github and not sure how to ask a question!

Your code is brilliant.  Thank you for sharing.
I have written a node.js server that connects to bt devices....it works fine but stops scanning after a bit.  What is it that causes noble to stop scanning?
I receive the stopScan event....just have no idea what triggers it.
I worked around by just starting a scan every 15 secs if necessary.
I am running on a Raspberry Pi 3 with Raspbian Jessie......all installed fine and works apart from this

read through some of the other bugs. Some adapters won't let you connect while scanning (and perhaps vice versa).  try to stop scanning while connected.

Thanks  Apologies if I failed at researching thoroughly.   Appreciate your time in answering


Ingester failed to find pending ingester on upgrade, didn't flush chunks.

time="2017-03-17T10:11:16Z" level=fatal msg="Failed to transfer chunks to another ingester: cannot find ingester to transfer chunks to" source="ingester_lifecycle.go:194"
time="2017-03-17T10:11:13Z" level=warning msg="No pending ingesters found..." source="ingester_lifecycle.go:381"
time="2017-03-17T10:11:10Z" level=warning msg="No pending ingesters found..." source="ingester_lifecycle.go:381"
time="2017-03-17T10:11:07Z" level=warning msg="No pending ingesters found..." source="ingester_lifecycle.go:381"
time="2017-03-17T10:11:04Z" level=warning msg="No pending ingesters found..." source="ingester_lifecycle.go:381"
time="2017-03-17T10:11:01Z" level=warning msg="No pending ingesters found..." source="ingester_lifecycle.go:381"
time="2017-03-17T10:10:58Z" level=warning msg="No pending ingesters found..." source="ingester_lifecycle.go:381"
time="2017-03-17T10:10:55Z" level=warning msg="No pending ingesters found..." source="ingester_lifecycle.go:381"
time="2017-03-17T10:10:52Z" level=warning msg="No pending ingesters found..." source="ingester_lifecycle.go:381"
time="2017-03-17T10:10:49Z" level=warning msg="No pending ingesters found..." source="ingester_lifecycle.go:381"
time="2017-03-17T10:10:46Z" level=warning msg="No pending ingesters found..." source="ingester_lifecycle.go:381"
time="2017-03-17T10:10:46Z" level=info msg="Changing ingester state from ACTIVE -> LEAVING" source="ingester_lifecycle.go:310"
time="2017-03-17T10:10:46Z" level=info msg="=== received SIGINT/SIGTERM ===\n*** exiting"

D'oh, a log.Fatal where I meant to have a log.Errorf

Also, why did it only look for 27s?

Joining ingester log:
time="2017-03-17T10:11:18Z" level=info msg="Entry not found in ring, adding with no tokens." source="ingester_lifecycle.go:230"
time="2017-03-17T10:11:36Z" level=warning msg="GET /ready (500) 117.425µs"
time="2017-03-17T10:11:46Z" level=warning msg="GET /ready (500) 109.275µs"
time="2017-03-17T10:11:48Z" level=info msg="Auto-joining cluster after timout." source="ingester_lifecycle.go:162"

So it can take more than 30s to schedule the new pod.  Will extend the timeout.


Support switching between virtualenvs

Hello,
Thank you for this nice extension!
It'd better if you can add a config/setting that allows user to choose which pip to manage.
Imagine we have many virtualenvs (different python paths), this option will allow user switching between his environments and easily manage pip packages from each env.

I came from Node Package Manager and immediately noticed that all the listed packages are the global ones, not the current venv ones. So +1 for this feature! Thanks.


add readme badges, codecov

This PR adds readme badges, codecov, MIT license file

Codecov Report

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

@@           Coverage Diff           @@
##             main      #68   +/-   ##
=======================================
  Coverage        ?   94.37%
=======================================
  Files           ?       12
  Lines           ?     3057
  Branches        ?      275
=======================================
  Hits            ?     2885
  Misses          ?      161
  Partials        ?       11

Continue to review full report at Codecov.

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


Adding iree_bitcode_library using our own clang build.

Our own clang build allows us to cross-compile to all targets we care about with a consistent version separate from system compilers where we may not even have clang, or an ancient version of clang-12, or a clang that can't compile CUDA, etc etc.
This initial PR enables the clang build and changes the custom_dispatch samples and the iree/builtins/device library to use it. The CUDA sample still includes nvcc to demonstrate how that can be used. The device builtins change allows us to remove the checked in bitcode files and instead compiles them from source as a normal part of building the compiler.
Ergonomic improvements are needed before scaling this out such as a matrix rule for reducing the BUILD boilerplate. iree/builtins/musl will need to move off of using make but iree/builtins/ukernel should be easier to glob and use directly but has grown a bit too complex to directly use this right now (arch/config rewriting goo).
This will bump up compiler build times as we're now building clang. I tried to avoid needing to do this but it's way better than any alternative (checking in bitcode, only being able to build microkernels on certain platforms, supporting random user errors with outdated/misconfigured clangs, etc).

Need to figure out how to either ship clang in our host tools or conditionally enable it all based on IREE_BUILD_COMPILER - the bitcode files are only needed to build the compiler and that's probably the easiest option.

Hmmm iree_cuda_deps seems to be messing with things - looks like it's not in a layout matching the CUDA toolkit and clang looks for things in certain places.

I think this pushes us over the edge of really needing to support externally installed llvm's. Among other benefits, would give people a way to better manage their dev flow when not regularly making llvm changes.

Sounds like the job for someone who knows how to deal with that and wants to support those users bringing their own random LLVM builds without the things we need (appropriate target backends, properly configured base headers, etc) - I call not it ;)
The cost of our devs wanting microkernels written in textual C source is that they have to build some more files when the llvm submodule bumps and that feels reasonable. I'd still have preferred asm we can parse directly or C++ intrinsic emitters that go right in the compiler code but I grew weary of trying to convince people after all these years 😔
At least here clang is cheaper to compile than mlir or llvm itself - generating the single riscv tablegen output takes as long as compiling all of clang for me... which also makes me sad.

I think the remaining failure is because the .o files for the sample need to be stashed in the install dir so that the subsequent bots can find them. This has likely always been an issue but they weren't running before this PR as they required external tooling and disabled themselves before they could fail in this way.

Filed #12112 after brainstorming with benoit about next steps for extending this to the ukernel library.

CUDA compilation is disabled for now and #12267 has been filed to get that working.

@stellaraccident I rebased onto your llvm external project changes - does this look ok?


Imports are incorrectly sorted and/or formatted Error occured

Type: Bug
i haven't touch any of modules nor code
but after i update my VScode
this error is occured in python code
'Imports are incorrectly sorted and/or formatted'
VS Code version: Code 1.72.2 (d045a5eda657f4d7b676dedbfa7aab8207f8a075, 2022-10-12T22:15:18.074Z)
OS version: Windows_NT x64 10.0.19044
Modes:
Sandboxed: No

System Info

Item
Value

CPUs
Intel(R) Core(TM) i7-8750H CPU @ 2.20GHz (12 x 2208)

GPU Status
2d_canvas: enabledcanvas_oop_rasterization: disabled_offdirect_rendering_display_compositor: disabled_off_okgpu_compositing: enabledmultiple_raster_threads: enabled_onopengl: enabled_onrasterization: enabledraw_draw: disabled_off_okskia_renderer: enabled_onvideo_decode: enabledvideo_encode: enabledvulkan: disabled_offwebgl: enabledwebgl2: enabledwebgpu: disabled_off

Load (avg)
undefined

Memory (System)
23.85GB (4.40GB free)

Process Argv
--crash-reporter-id f68ed2b4-f1fb-405d-83b7-a8bf4788ed72

Screen Reader
no

VM
0%

Extensions (16)

Extension
Author (truncated)
Version

blackbox
Bla
0.3.0

vscode-mysql
for
0.4.1

mysql-syntax
jak
1.3.1

git-graph
mhu
1.30.0

vscode-docker
ms-
1.22.1

isort
ms-
2022.3.12861052

python
ms-
2022.17.12871028

vscode-pylance
ms-
2022.10.20

jupyter
ms-
2022.9.1202862440

jupyter-keymap
ms-
1.0.0

jupyter-renderers
ms-
1.0.10

vscode-jupyter-cell-tags
ms-
0.1.6

vscode-jupyter-slideshow
ms-
0.1.5

remote-containers
ms-
0.255.3

LiveServer
rit
5.7.9

project-tree
zhu
0.3.0

A/B Experiments
vsliv368cf:30146710
vsreu685:30147344
python383cf:30185419
vspor879:30202332
vspor708:30202333
vspor363:30204092
vswsl492:30256859
vstes627:30244334
vslsvsres303:30308271
pythonvspyl392:30443607
vserr242cf:30382550
pythontb:30283811
vsjup518:30340749
pythonptprofiler:30281270
vshan820:30294714
vstes263:30335439
vscorecescf:30445987
pythondataviewer:30285071
vscod805:30301674
binariesv615:30325510
bridge0708:30335490
bridge0723:30353136
cmake_vspar411:30581797
vsaa593:30376534
pythonvs932:30410667
cppdebug:30492333
vsclangdc:30486549
c4g48928:30535728
dsvsc012cf:30540253
azure-dev_surveyone:30548225
i497e931:30553904
pyindex848cf:30577861
nodejswelcome1:30587005
fc301958:30573243

/extPython

I downgraded to 1.71
everything works fine in 1.71

This is caused by the python extension. Please file the issue against them

This issue is caused by an extension, please file it with the repository (or contact) the extension has linked in its overview in VS Code or the marketplace for VS Code. See also our issue reporting guidelines. If you don't know which extension is causing the problem, you can run Help: Start extension bisect from the command palette (F1) to help identify the problem extension.
Happy Coding!


How do you install and use the command line interface?

Summary
I'd like to use both wasm-bindgen and wasm2es6js from the command line. How are those installed?

It's not stated anywhere obvious, but the intention is for you to run
cargo install wasm-bindgen-cli [crates.io]

Yep, what @nhynes mentioned should do the trick!


Add Mexico SCT (Red Compartida) scraper

Low priority as not expected to continue publishing.
https://datos.gob.mx/redcompartida/

That link 404's - is that as expected now?

In this link https://datos.gob.mx/busca/dataset/proceso-de-contratacion-del-proyecto-de-la-red-compartida if you try to download the json file, redirects us to a file that does not exist https://drive.google.com/uc?export=download&id=0B5wc002kIlpheVV3a29YbFJaSUU