Swapping three nos. without use of another variable

💥 Proposal
I am a GSSOC participant and want to work on Swapping three nos. without using of another variable
Have you read the Contributing Guidelines on Pull Requests?
YES

/assign

Pls assign it me also would like to do this In java......

Don't need such concept based problem


Anonimize/not store IP addresses

We can't afford keeping IP address, at least not anonymized ones
And I cant' find a way to customize this, because you save it in create_magiclink() helper
Could you please add some solution?
Either not store them at all, if MAGICLINK_REQUIRE_SAME_IP is set to False
Or at least anonymize it by default or by option (by removing last part for IP4? not sure about IP6)

Also are magiclinks intended to be stored permanently? What is it for? Or did make something wrong?

Hey @efojs
Very good point with the IP addresses. I'll look at not storing them when MAGICLINK_REQUIRE_SAME_IP is false as well as adding a note about them being stored.
I also like the idea of anonymising the IP by default as well. It would make the REQUIRE_SAME_IP a tiny bit more insecure but I think it's worth it. I'll add a MAGICLINK_ANONYMIZE_IP setting which is turned on by default.
As for the magic links being stored permanently. This is something I thought about when first creating the plugin.  Whether to soft delete (disable) or hard delete. I decided not destroying data and being able to show the Magic link has been used too many times and Magic link has expired errors were helpful.
If you are using any kind of background / periodic tasks via celery etc I would advise a cleanup via that. It would probably be good to add in a similar management command to Django's clearsessions though so it's easy to clean up via a cron or something. I'll look into that as well.

Hi! Any progress with this feature?
Maybe you have some suggestion for monkey-patching it?
Like can I piggyback on some signal and just delete this value?

Oh, I forgot and then overlooked "management command to Django's clearsessions" — yes, I'll try it. We don't use Celery on this project, but maybe cron will work well. So just removing IPs of expired links looks to be enough this way.

Hi @efojs
Very late but I've finally found an evening to work on these bits:

The IP addresses are now anonymized by default be replacing the last octet with a 0 - https://github.com/pyepye/django-magiclink/commit/a659d68a3c1531c98283e979074dcf1516e8c431
The IP address are only stored if REQUIRE_SAME_IP is set - https://github.com/pyepye/django-magiclink/commit/7508d48e08bf2234268e92797856eaf82997cf63
There is now a management command to remove old expired magic links - https://github.com/pyepye/django-magiclink/commit/c809859e531aa99eddd859681330ce0fff2891f6

I've just doing a few other fixes, I'll create a new version and release it to Pypi later.
Thanks
Matt

I've created a new release - version 1.1.0 - which has been pushed to Pypi


[occm] consider private network name when node contains IPs from other private networks

What this PR does / why we need it:
Cherry-pick PR #1041
Which issue this PR fixes(if applicable):
fixes #1039
Special notes for reviewers:

Release note:

NONE

/lgtm
/approve


Update mk.js

Improve mk translation

Please also update src/locale/mk.js.

@marwahaha It's okay now? https://github.com/moment/moment/pull/4921


advance-to-point advance to the end of the current block

This pull request modifies the behavior of fstar-subp-advance-or-retract-to-point such that it will advance to the end of the current block.
Previously, if the cursor is in the middle of a block, for example,
let foo (_: unit) = ()
             ^

Pressing C-c RET will pass let foo( to the sub-process, and reports an error. The updated function will pass the entirety of let foo ... to the process and succeed. This is helpful when I'm still trying to figure out the function body (especially if it spans multiple line), since I won't need to move my cursor (which I can use M-n) and back (which is more difficult).
I'm not a fstar power user and in all my use cases, I'm always advancing the proof checker on a block granularity. Maybe there is indeed a demand for sub-block advancement (maybe at tactic level, such as in Coq). If that's the case, I can create a separate function for this altered behavior and register a different key for it.

Hi Luke!
I don't know whether the "go to this exact point" behavior is still useful, but I suspect it is: the automatic logic to figure out where a block ends is not very good, and so it's good to be able to override it.
That said, I agree with you that I prefer your behavior when it works.
Doesn't C-c C-n do what you want in most cases? (Process the next block?)

Yes, C-c C-n technically do the same thing, but I prefer C-c RET for three reasons,

muscle memory from using C-c RET for years from coq-mode has trained me to that binding only,
C-c RET can both retract and advance, while I would need to hit C-p for retract otherwise.
I'm using homerow modifiers. In other words, control key is J/F for me. As you can imagine, none of J-c J-n, J-c F-n or F-c F-n is easy to work with.

Maybe we could have a setting for this.  Or maybe one of the F* devs can comment?

Being able to configure C-c C-RET to behave like C-c C-n sounds like a good idea to me.
FWIW, finding the end of the current definition is difficult without actually using F* to parse the contents of the buffer. FYI, in fstar-vscode-assistant, when the user hits Ctrl+. the editor passes the current cursor location to the F* server, F* parses the buffer and advances to checker to up to the definition that encloses the current cursor location.

FYI, in fstar-vscode-assistant, when the user hits Ctrl+. the editor passes the current cursor location to the F* server, F* parses the buffer and advances to checker to up to the definition that encloses the current cursor location.

It feels like the proper way to address the problem. Is it an API that emacs can also use or limited to vscode?


Scrapoxy crash in 3.1 - writeEnd is not defined

After updating to 3.1, getting this crash:
0|scrapoxy | ReferenceError: writeEnd is not defined
0|scrapoxy |     at Server.request (/usr/lib/node_modules/scrapoxy/server/proxies/master/index.js:78:21)
0|scrapoxy |     at emitTwo (events.js:126:13)
0|scrapoxy |     at Server.emit (events.js:214:7)
0|scrapoxy |     at parserOnIncoming (_http_server.js:602:12)
0|scrapoxy |     at HTTPParser.parserOnHeadersComplete (_http_common.js:116:23)

Not sure if the issue with the code was present before 3.1 or if it was only surfaced by a new chaneg, but writeEnd is definitely not available when this function is called :)
function request(req, res) {
			// Check auth
			if (self._token) {
				if (!req.headers['proxy-authorization'] || req.headers['proxy-authorization'] !== self._token) {
					return writeEnd(res, 407, '[Master] Error: Wrong proxy credentials', {
						'Proxy-Authenticate': 'Basic realm="Scrapoxy"',
						'Content-Type': 'text/plain',
					});
				}
			}

			return requestImpl(req, res);
		}

From the looks of it should be a really simple fix.

thanks. will be corrected in next version


Allow filter when pushing a dictionary into createOrUpdateInRealm

I was recently working with some API data to push into Realm data store formatted like the following:
[
  {
    "id": 1234,
    "confirmation": 483,
    locations: [
      {
        "id": 5678,
        "address": "54 Main Street",
        ...
        "arrive_at": "2015-03-12T17:37Z"
      },
      {
        "id": 5679",
        "address": "72 Center Street",
        ...
        "arrive_at": null
      }
    ],
    ...
  },
  ...
]

The JSON is an array of trips for a hired driver. I have models setup in Swift as follows:
class Trip: RLMObject {
  dynamic var id = 0
  dynamic var confirmation = 0
  dynamic var locations = RLMArray(objectClassName: Location.className())
  ...
}

class Location: RLMObject {
  dynamic var id = 0
  dynamic var address: String = ""
  ...
  dynamic var arriveAt: NSDate = NSDate()
  ...
}

I originally had Swift code like the following to save each block from the API:
func parseTrips (trips: JSON) {
  let realm = RLMRealm.defaultRealm()
  realm.begineWriteTransaction()
  for tripJson in trips.arrayValue {
    Trip.createOrUpdateInRealm(realm, withObject: tripJson.dictionaryObject)
  }
  realm.commitWriteTransaction()
}

The code failed because of the arriveAt property on the Location class. I'd like to see a configurator option somewhere, either in RLMObject when it's passed on object or in createOrUpdateInRealm as an argument to cast variables.
Something like:
class Location: RLMObject {
  dynamic var id = 0
  dynamic var address: String = ""
  dynamic var arriveAt: NSDate = NSDate()

  func castInputObject (data: Dictionary) -> Dictionary {
    data["arriveAt"] = NSDate.fromISO8601String(data["arrive_at"])
  }
}

Hi @davejlong, we already have a couple of issues tracking this feature request, namely https://github.com/realm/realm-cocoa/issues/694, https://github.com/realm/realm-cocoa/pull/1272, & https://github.com/realm/realm-cocoa/issues/1063. In the meantime, you'll either have to pre-process your dictionaries before passing them into createOrUpdateInRealm, or otherwise look into using something like Realm-JSON or RestKit.


Default to stronger encrytion

Since the lib already requires java 8 (just love the lambdas...) at least in theory we could default to stronger encryption. So while something like PBEWITHHMACSHA512ANDAES_256 should work without having to install any jre additions, there seems to be a bug in jascpt that prevents strong algorithms from being used (see http://sourceforge.net/p/jasypt/bugs/32/?sm_au=i6H56bRD0bPLK6jQ) - I actually couln't even get the somewhat more secure (but still insecure) PBEWITHMD5ANDTRIPLEDES to work :(

Maybe look into alternatives to jasypt (like bouncycastle)?


[eas-cli] use new graphql api in SetupBuildCredentialsFromCredentials…

…Json

Checklist

[ ] I've added an entry to CHANGELOG.md if necessary.

Why
This is part of the effort to move all credentials apiv2 calls to our graphql api. This PR allows you to setup build credentials from some credentials json using the new Graphql Api. This will eventually replace the old SetupBuildCredentialsFromCredentialsJson here:  https://github.com/expo/eas-cli/blob/main/packages/eas-cli/src/credentials/ios/actions/SetupBuildCredentials.ts#L60
Notable Changes
SetupBuildCredentialsFromCredentialsJson works slightly differently:

If there are no credentials configured already, just assign new credentials
If there are different credentials configured already, prompt user to confirm that they want to assign new credentials
If there the configured credentials are the same as the ones in credentials json, stick with the old credentials

Test Plan

[ ] i did not do any testing
[ ] new pretty printing still looks ugly

also, is SetupBuildCredentialsFromCredentialsJson supposed to work in non-Interactive mode, or is it fine to just error in this case?

@dsokal @wkozyra95 also, is SetupBuildCredentialsFromCredentialsJson supposed to work in non-Interactive mode, or is it fine to just error in this case?

I would expect that command like that would not require interaction (just upload current credentials or fail), but on the other hand there is no use case to run that on CI, so it should not matter


Not all components work

Some components do not install because the name of the component is different from the directory name.  For example, the rls component is actually rls-preview.
rustup-toolchain-install-master --component=rls

for me will fetch https://s3-us-west-1.amazonaws.com/rust-lang-ci2/rustc-builds/0a4a4ffc69f2d05eb8b8a32eaf9bd0607b69fe38/rls-nightly-x86_64-apple-darwin.tar.xz which has these files:
rls-nightly-x86_64-apple-darwin
rls-nightly-x86_64-apple-darwin/LICENSE-APACHE
rls-nightly-x86_64-apple-darwin/LICENSE-MIT
rls-nightly-x86_64-apple-darwin/README.md
rls-nightly-x86_64-apple-darwin/components
rls-nightly-x86_64-apple-darwin/install.sh
rls-nightly-x86_64-apple-darwin/rls-preview
rls-nightly-x86_64-apple-darwin/rls-preview/bin
rls-nightly-x86_64-apple-darwin/rls-preview/bin/rls
rls-nightly-x86_64-apple-darwin/rls-preview/manifest.in
rls-nightly-x86_64-apple-darwin/rls-preview/share
rls-nightly-x86_64-apple-darwin/rls-preview/share/doc
rls-nightly-x86_64-apple-darwin/rls-preview/share/doc/rls
rls-nightly-x86_64-apple-darwin/rls-preview/share/doc/rls/LICENSE-APACHE
rls-nightly-x86_64-apple-darwin/rls-preview/share/doc/rls/LICENSE-MIT
rls-nightly-x86_64-apple-darwin/rls-preview/share/doc/rls/README.md
rls-nightly-x86_64-apple-darwin/rust-installer-version
rls-nightly-x86_64-apple-darwin/version

Notice the directory is rls-preview, not rls.
I would guess that the solution is to first read the components file to get the list of directories that exist.  I'm not terribly familiar with how rustup works, but that seems like it would work.
(I can try to help implement that if it seems like a reasonable approach.)

cc @kinnison

cc @kinnison

Not sure why you're cc'ing me @lzutao

Sorry! I should have to be more clear.
Do you have any ideas on how to extract these components tarballs just like rustup?

Rustup unpacks the tarballs, ignoring the first path element, otherwise it's a pretty normal unpack.  You can see the code here: https://github.com/rust-lang/rustup.rs/blob/master/src/dist/component/package.rs#L271

I have a fix in #32


Bug: process.exit(code) always exits with zero exit code

In Electron main process:
process.exit(1);

In shell
> electron .
> echo $?
0

Electron version: 0.27.3
Doesn't happen in Node.

You need to use app.quit to exit Electron apps, process.exit will cause Weird Things™ to happen

Well it was suggested in https://github.com/atom/electron/issues/1944

Huh. Well then. Um. I think we should fix app.quit

Seems to be working fine on OSX(10.9.5) with master branch.

Looks like it's because app.quit calls a browser API close which isn't handled with process.exit().  Since the process API is part of Node, there may need to be a redefinition of that function...
https://github.com/atom/electron/blob/02bdace366f38271b5c186412f42810ecb06e99e/atom/browser/api/atom_api_app.cc#L222

update process.exit on linux causes crash with the following trace
hello-atom git:master ✗ ✩  ❯ ../atom-shell/out/D/electron ./dialog-app                                                                                ⏎
[4441:0622/090327:ERROR:browser_main_loop.cc(173)] Running without the SUID sandbox! See https://code.google.com/p/chromium/wiki/LinuxSUIDSandboxDevelopment for more information on developing with the sandbox on.

hello-atom git:master ✗ ✩  ❯ [4458:0622/090327:WARNING:ipc_message_attachment_set.cc(37)] MessageAttachmentSet destroyed with unconsumed descriptors: 0/1
[4464:0622/090327:INFO:renderer_main.cc(200)] Renderer process started
[4464:0622/090327:WARNING:ipc_message_attachment_set.cc(37)] MessageAttachmentSet destroyed with unconsumed descriptors: 0/1
Received signal 11 SEGV_MAPERR<PHONE_NUMBER>08
#0 0x7fb45e46aca8 <unknown>
#1 0x7fb456e83740 <unknown>
#2 0x7fb468b489c3 uv__async_send
#3 0x7fb468b48954 uv_async_send
#4 0x0000006da78c atom::NodeBindings::WakeupEmbedThread()
#5 0x0000006da6f8 atom::NodeBindings::~NodeBindings()
#6 0x0000006dd505 atom::NodeBindingsLinux::~NodeBindingsLinux()
#7 0x0000006dd529 atom::NodeBindingsLinux::~NodeBindingsLinux()
#8 0x000000693012 base::DefaultDeleter<>::operator()()
#9 0x000000692fc0 base::internal::scoped_ptr_impl<>::~scoped_ptr_impl()
#10 0x000000692145 scoped_ptr<>::~scoped_ptr()
#11 0x0000006e82a8 atom::AtomRendererClient::~AtomRendererClient()
#12 0x0000006e8319 atom::AtomRendererClient::~AtomRendererClient()
#13 0x00000068de32 base::DefaultDeleter<>::operator()()
#14 0x00000068e310 base::internal::scoped_ptr_impl<>::~scoped_ptr_impl()
#15 0x00000068d8c5 scoped_ptr<>::~scoped_ptr()
#16 0x00000068d13a atom::AtomMainDelegate::~AtomMainDelegate()
#17 0x00000068bfa7 main
#18 0x7fb452c24800 __libc_start_main
#19 0x00000068bdd9 _start
  r8: 000006f1b9f2b000  r9:<PHONE_NUMBER>000000 r10:<PHONE_NUMBER>000937 r11: 00007fb468b489a0
 r12:<PHONE_NUMBER>68bdb0 r13: 00007fffcc3c8f40 r14:<PHONE_NUMBER>000000 r15:<PHONE_NUMBER>000000
  di:<PHONE_NUMBER>0001c8  si:<PHONE_NUMBER>000000  bp: 00007fffcc3c8b70  bx:<PHONE_NUMBER>000000
  dx:<PHONE_NUMBER>000001  ax:<PHONE_NUMBER>0001c8  cx:<PHONE_NUMBER>000000  sp: 00007fffcc3c8b40
  ip: 00007fb468b489c3 efl:<PHONE_NUMBER>010202 cgf:<PHONE_NUMBER>000033 erf:<PHONE_NUMBER>000004
 trp:<PHONE_NUMBER>00000e msk:<PHONE_NUMBER>000000 cr2:<PHONE_NUMBER>000208
[4463:0622/090327:INFO:renderer_main.cc(200)] Renderer process started
[4463:0622/090327:WARNING:ipc_message_attachment_set.cc(37)] MessageAttachmentSet destroyed with unconsumed descriptors: 0/1
Received signal 11 SEGV_MAPERR<PHONE_NUMBER>08
#0 0x7f56b07f8ca8 <unknown>
#1 0x7f56a9211740 <unknown>
#2 0x7f56baed69c3 uv__async_send
#3 0x7f56baed6954 uv_async_send
#4 0x0000006da78c atom::NodeBindings::WakeupEmbedThread()
#5 0x0000006da6f8 atom::NodeBindings::~NodeBindings()
#6 0x0000006dd505 atom::NodeBindingsLinux::~NodeBindingsLinux()
#7 0x0000006dd529 atom::NodeBindingsLinux::~NodeBindingsLinux()
#8 0x000000693012 base::DefaultDeleter<>::operator()()
#9 0x000000692fc0 base::internal::scoped_ptr_impl<>::~scoped_ptr_impl()
#10 0x000000692145 scoped_ptr<>::~scoped_ptr()
#11 0x0000006e82a8 atom::AtomRendererClient::~AtomRendererClient()
#12 0x0000006e8319 atom::AtomRendererClient::~AtomRendererClient()
#13 0x00000068de32 base::DefaultDeleter<>::operator()()
#14 0x00000068e310 base::internal::scoped_ptr_impl<>::~scoped_ptr_impl()
#15 0x00000068d8c5 scoped_ptr<>::~scoped_ptr()
#16 0x00000068d13a atom::AtomMainDelegate::~AtomMainDelegate()
#17 0x00000068bfa7 main
#18 0x7f56a4fb2800 __libc_start_main
#19 0x00000068bdd9 _start
  r8: 000033371c864000  r9:<PHONE_NUMBER>000000 r10:<PHONE_NUMBER>000937 r11: 00007f56baed69a0
 r12:<PHONE_NUMBER>68bdb0 r13: 00007ffc4a8e91a0 r14:<PHONE_NUMBER>000000 r15:<PHONE_NUMBER>000000
  di:<PHONE_NUMBER>0001c8  si:<PHONE_NUMBER>000000  bp: 00007ffc4a8e8dd0  bx:<PHONE_NUMBER>000000
  dx:<PHONE_NUMBER>000001  ax:<PHONE_NUMBER>0001c8  cx:<PHONE_NUMBER>000000  sp: 00007ffc4a8e8da0
  ip: 00007f56baed69c3 efl:<PHONE_NUMBER>010206 cgf:<PHONE_NUMBER>000033 erf:<PHONE_NUMBER>000004
 trp:<PHONE_NUMBER>00000e msk:<PHONE_NUMBER>000000 cr2:<PHONE_NUMBER>000208

update Works fine on linux, unable to reproduce the crash anymore. Sorry for the confusion, must have been something i messed up with the code.

Confirmed on Mac OS X 10.10.3 / Electron 0.29.2. I was sure that I was doing something wrong... but, yeah it seems reasonable that app.quit should accept an exit code parameter.

Any update on this?

I just tested in v0.33.0 and it works as expected, seems that it has been fixed as part of Node.js or Chrome update.

I'm running version 0.33.3 and I'm still getting an exit code of 0 after running process.exit(1)

process.exit(code) is working in 0.35.2


Partial: Search Bar Button and Bar

An extension of #4. Subset of the original issue scope, just working on displaying a search bar icon next to the reset button implemented in #16 with issue #2.

[x] Implement extra button
[x] Implement search bar that is typeable
[ ] Implement debounce on the search bar, and console.log when a search occurs

WIP, merging this issue back into main


[Snyk] Upgrade mongoose from 6.5.1 to 6.12.6

This PR was automatically created by Snyk using the credentials of a real user.Snyk has created this PR to upgrade mongoose from 6.5.1 to 6.12.6.
:information_source: Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.

The recommended version is 47 versions ahead of your current version.
The recommended version was released 2 months ago, on 2024-01-22.

The recommended version fixes:

Severity
Issue
PriorityScore (*)
Exploit Maturity

Server-side Request Forgery (SSRF) SNYK-JS-IP-6240864
537/1000  Why? Proof of Concept exploit, CVSS 8.6
Proof of Concept

Prototype Pollution SNYK-JS-MONGOOSE-5777721
537/1000  Why? Proof of Concept exploit, CVSS 8.6
Proof of Concept

Information Exposure SNYK-JS-MONGODB-5871303
537/1000  Why? Proof of Concept exploit, CVSS 8.6
No Known Exploit

(*) Note that the real score may have changed since the PR was raised.

Release notes

Package name: mongoose

6.12.6 - 2024-01-22chore: release 6.12.6

6.12.5 - 2024-01-03

6.12.4 - 2023-12-27

6.12.3 - 2023-11-07

6.12.2 - 2023-10-25

6.12.1 - 2023-10-12

6.12.0 - 2023-08-24

6.11.6 - 2023-08-21

6.11.5 - 2023-08-01

6.11.4 - 2023-07-17

6.11.3 - 2023-07-11

6.11.2 - 2023-06-08

6.11.1 - 2023-05-08

6.11.0 - 2023-05-01

6.10.5 - 2023-04-06

6.10.4 - 2023-03-21

6.10.3 - 2023-03-13

6.10.2 - 2023-03-07

6.10.1 - 2023-03-03

6.10.0 - 2023-02-22

6.9.3 - 2023-02-22

6.9.2 - 2023-02-16

6.9.1 - 2023-02-06

6.9.0 - 2023-01-25

6.8.4 - 2023-01-17

6.8.3 - 2023-01-06

6.8.2 - 2022-12-28

6.8.1 - 2022-12-19

6.8.0 - 2022-12-05

6.7.5 - 2022-11-30

6.7.4 - 2022-11-28

6.7.3 - 2022-11-22

6.7.2 - 2022-11-07

6.7.1 - 2022-11-02

6.7.0 - 2022-10-24

6.6.7 - 2022-10-21

6.6.6 - 2022-10-20

6.6.5 - 2022-10-05

6.6.4 - 2022-10-03

6.6.3 - 2022-09-30

6.6.2 - 2022-09-26

6.6.1 - 2022-09-14

6.6.0 - 2022-09-08

6.5.5 - 2022-09-07

6.5.4 - 2022-08-30

6.5.3 - 2022-08-25

6.5.2 - 2022-08-10

6.5.1 - 2022-08-03

    from mongoose GitHub release notes

Commit messages

Package name: mongoose

09181ef chore: release 6.12.6
af123cb Merge pull request #14277 from Automattic/vkarpov15/gh-14184
6b67f9b test: add test case for #14184
900e9fa fix(collection): correctly handle buffer timeouts with `find()`
4b6d208 Merge pull request #14254 from Automattic/vkarpov15/gh-14244
cc9ac77 Merge pull request #14265 from rohanricky/pathRelativeToParent_null_check
73bea51  null check
6bc42ce test: add missing issue to test title
195b46c fix(document): allow calling `push()` with different `$position` arguments
2d68983 chore: release 6.12.5
b4e3b2f Merge pull request #14213 from Automattic/vkarpov15/gh-14024
0960fae types(document): add ignoreAtomics option to isModified typedefs re: #14024
f7e9816 docs(document): add ignoreAtomics option to docs
e3c12cf types(model): add missing strict and timestamps options to bulkWrite() re: #8778
f37b4f2 Merge pull request #14226 from Automattic/vkarpov15/gh-14205
b286b02 fix: also allow setting nested field to undefined re: #14205
6d526cd fix(document): allow setting nested path to `null`
403a28e fix: add ignoreAtomics option to isModified() for better backwards compatibility with Mongoose 5
8e141d1 perf(schema): remove unnecessary lookahead in numeric subpath check
e182fe5 Merge pull request #14198 from Automattic/vkarpov15/gh-14178
dabb2cf style: fix lint
4def302 style: fix lint and remove unused file
9725d93 fix(document): avoid flattening dotted paths in mixed path underneath nested path
44f391b chore: release 6.12.4

Compare

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.
For more information:
🧐 View latest project report
🛠 Adjust upgrade PR settings
🔕 Ignore this dependency or unsubscribe from future upgrade PRs

No longer using this app


node v8.0 there has a mistake during install v8-profiler

node v8.0 there has a mistake during install v8-profiler but it works ok in node v7.x

use v8-profile-node8 to fix the bug


fixed onUpdate receiving incorrect 'translate' and 'zoom' on force update

Hi again, @bkrem, could you please review this. It turned out that the assigning in "componentWillReceiveProps" was actually necessary, when component is force-updated.
Honestly, I don't know how to write a unit test for this, but at least I verified it works when I've put the tree inside another component and force-updated the wrapper.

Coverage increased (+0.08%) to 93.919% when pulling 4994177dca9153498d5f75e835f63d5ad3144750 on sspanak:hotfix/onUpdate-does-not-pass-correct-translate-on-force-render into d940b7c6c70e5b213f9d7b712ceb1d075cc6a3ca on bkrem:master.

Coverage increased (+0.08%) to 93.919% when pulling 4994177dca9153498d5f75e835f63d5ad3144750 on sspanak:hotfix/onUpdate-does-not-pass-correct-translate-on-force-render into d940b7c6c70e5b213f9d7b712ceb1d075cc6a3ca on bkrem:master.

Coverage increased (+0.08%) to 93.919% when pulling 4994177dca9153498d5f75e835f63d5ad3144750 on sspanak:hotfix/onUpdate-does-not-pass-correct-translate-on-force-render into d940b7c6c70e5b213f9d7b712ceb1d075cc6a3ca on bkrem:master.

Hey @sspanak,
Thanks for checking this and hotfixing it immediately 👍
Will publish 1.9.2 with this now.


feat(cheatcodes): add vm.startContractBroadcast to support simulating / transaction from smart contract wallets

Component
Forge
Describe the feature you would like
Rationale
Currently, forge scripts only support broadcasting transactions from externally owned accounts. However, many teams use smart contract wallets such as Gnosis Safe to manage their contracts which Foundry does not natively support. If teams want to use Foundry with their Gnosis Safe, they often need to write complex scripts that simulate interacting with their Safe wallet like Optimism does and use FFI to initiate transactions in production.
However, it is possible that Foundry could natively support broadcasting via Gnosis Safe or any other smart contract wallet in the future. Native support for Gnosis Safe would enable teams to write standard forge scripts, which could then be broadcast via their Gnosis Safe in production with minimal modifications to their scripts. Instead, Foundry would handle that work under the hood, similar to how it handles sending transactions via hardware wallets with the --ledger option, Gnosis Safe would simply be another sender type, i.e. --safe-multisig. This would avoid developers needing to write low-level scripts to simulate interacting with their safe or using FFI to send transactions in production. See #1232 for a more comprehensive discussion on this topic.
There are two things required for Foundry to natively support Gnosis Safe:

Accurate local simulation of scripts executed via a smart contract wallet.
A new broadcasting mode that takes transactions collected during the above simulation and handles batching and initiating their execution via the Gnosis Safe.

We'd like to clear the way for Foundry to support Gnosis Safe by addressing the first point, accurate local simulation of forge scripts executed via a smart contract wallet. There are several cases where transactions sent from a smart contract wallet differ from those sent from an EOA.
Example
For example, due to EIP-161, smart contract wallets have nonces that start at 1 and increment by 1 for every new contract deployed. Their nonces do not increment for every transaction.
Take a look at the following script:
contract CounterScript is Script {
    function run() public {
        Counter counter = new Counter(0);
        counter.increment();
        counter.increment();
        Counter secondCounter = new Counter(0);
    }
}

If this script were to be executed via an EOA with an initial nonce of 0, then the address of counter would be a function of their address and the nonce 0. Their nonce would be incremented once when deploying counter and twice when calling counter.increment(). So the address of secondCounter would be a function of the nonce 3 and their address.
However, if this script were executed from a smart contract wallet the nonces would be different, and therefore, the contract addresses would also be different. Since contract nonces start at 1, the address of counter would be a function of 1 and the wallet's address. Since contract nonces are only incremented when deploying other contracts, the address of secondContract would be a function of 2 and the wallet's address.
Currently, Foundry cannot accurately simulate this without the script including bespoke logic for interacting with the Gnosis Safe. So to natively Gnosis Safe, it's necessary to implement a mechanism that can properly simulate this type of operation.
Scope
The initial scope would just be a new cheat code, vm.startContractBroadcast intended to house functionality related to simulating transactions sent from smart contract wallets. This cheat code could initially be used by third-party wallet developers to accurately simulate forge scripts being executed via their smart contract wallet. It is expected that the third-party developer would implement their own logic to handle broadcasting the transactions.
In the long term, the scope would increase to include natively supporting Gnosis Safe and potentially other smart contract wallets.
Why we think this is useful
There are a lot of cases where transactions sent from smart contract wallets are different from those sent by an EOA. In the short term, having a better way to simulate transactions sent from smart contract wallets would enable third-party wallet developers to provide better integrations with Foundry. In the long term, it opens the door for natively supporting Gnosis Safe and other smart contract wallets.
Additional context
I am the CTO of Sphinx which is developing a DevOps platform that is designed to be tightly integrated with Foundry. Our platform uses a Gnosis Safe wallet with a custom module to enable trustless deployments via our platform. We provide a Foundry plugin that enables teams to take their existing forge scripts and execute them via our wallet and platform. You can learn more about what we do in our documentation. While developing our plugin, we noticed a variety of cases where Foundry does not accurately simulate transactions that are expected to come from a smart contract wallet. These issues both limit what scripts are compatible with our tool and also make it difficult for Foundry to natively support Gnosis Safe or other wallets.
Rather than just fixing these issues within our plugin, we'd like to contribute back to Foundry by spearheading an effort to make Foundry more compatible with smart contract wallets in general with the goal of eventually natively supporting Gnosis Safe. Obviously, this is helpful to us because it improves the UX of our wallet and platform. But we also think this benefits the Foundry community at large.

Note: This is a request for feedback. We'd love to make contributions to enable better simulation of smart contract wallets within Foundry, but we wanted to gauge community interest before doing so. Please let us know if you think contributions like this would be beneficial to the project.

looks similar with https://github.com/foundry-rs/foundry/issues/7248 , we're going to keep track of the request with it. thank you!


Not working with private tracker

I’m trying to download a torrent that uses private tracker that supports BitTorrent but it’s not working wit this client. It can’t find any peers or anything I verified it works with BitTorrent

Hi Billy.
This was originally meant to be a BitTorrent 1.0 implementation. If you'd like include support for private trackers I encourage you to implement it and submit a PR and I'll be more than happy to include this functionality to the main branch.


Add Nong Song

Song Name
Clubstep x Angry Birds
Artist Name
DJ-Nate
Source
Direct file download
Youtube Link
No response
Direct File Link
https://drive.google.com/file/d/1EYZFk_YbDACPz3g2TkkEqB_xOfzoq1A7/view?usp=drive_link
Song ID
13
Extra
No response

Auto nong doesn't work with google drive. can you upload it to youtube?

Does it work for direct discord dl links?

nope

need a proper CDN or upload to youtube

reject
non-YouTube sources are not supported


Cursor

The skinchanger works pretty fine in the CS:GO main menu; but when i load a map and open the menu, my cursor gets stuck in the middle. Any fixes? A lot of people say it works fine. I wonder if i cause this issue. But I haven't changed anything in the source. Even reinstalling didn't help.

Happens the same to me, after opening the menu press ESC to open the pause meno and the mouse will work then

Fixed in 2db69b008855bd9c5033a74b5651df74304293a3


Improve README

fix swift 4 package entry
add/fix routes
add password reset token explanation
mention the user related forms in description of how to customize

[ ] add explanation on the Signer keys. (Length, type, how to generate, etc)


Block for blocks

Base block classes refactoring

Block splitted to Block + ActivityBlock + UploaderBlock
Context properties initialization flow have been simplified
init$ prop types are temporary removed
ShadowWrapper added
UploadList switched to native Symbiote repeat
Symbiote version updated

Wrong target branch


Update the tab colors some more

Again, to reflect continuing discussion with the WinUI team. A doc may have been misread - these are the colors they're proposing, which are generally a lot better.
See also: #12400, #12356, #12398

how it look in light?


Pop/up

Functionality:
Improved Pop-Up alerts
Solution:
Improved pop-up alerts for log-work, edit-task and edit functions in the profile component
Risk level:

[ ] high
[x] medium
[ ] low

How to test:
ng serve
firebase emulators:start

This branch can we merged after my footer changes


Reordered Power of 2 in C++

💥 Proposal
Starting with a positive integer N, we reorder the digits in any order (including the original order) such that the leading digit is not zero.
The task is to return true if and only if we can do this in a way such that the resulting number is a power of 2.
Examples:

Input: 10
Output : false
Input: 46
Output: true

Have you read the Contributing Guidelines on Pull Requests?
Yes

Please assign this to me in C++

/assign

/assign


Cannot find module 'electron-squirrel-startup' again

I'm trying to compile latest code to date: MavensMate-Desktop-0.0.11-beta.7 on Arch Linux with the help I've found somewhere:
Download MavensMate server and run npm commands.
https://github.com/joeferraro/MavensMate
Download the Zip file.
Run: npm install
Run: npm start

Run your MavensMate in your browser
http://localhost:56248/app/home

but just running "npm install" was stuck in the loop with the following:

undefined postinstall /home/geb/soft/MavensMate/MavensMate-Desktop-0.0.11-beta.7
install-app-deps

so then I've tried "sudo npm install" and installation finished with some warnings:

npm WARN lifecycle undefined~postinstall: cannot run in wd %s %s (wd=%s) undefined install-app-deps /home/geb/soft/MavensMate/MavensMate-Desktop-0.0.11-beta.7
npm WARN optional SKIPPING OPTIONAL DEPENDENCY<EMAIL_ADDRESS>(node_modules/electron-builder/node_modules/appdmg):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for<EMAIL_ADDRESS>wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})
npm WARN optional SKIPPING OPTIONAL DEPENDENCY<EMAIL_ADDRESS>(node_modules/7zip-bin/node_modules/7zip-bin-osx):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for<EMAIL_ADDRESS>wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})
npm WARN optional SKIPPING OPTIONAL DEPENDENCY<EMAIL_ADDRESS>(node_modules/7zip-bin/node_modules/7zip-bin-win):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for<EMAIL_ADDRESS>wanted {"os":"win32","arch":"any"} (current: {"os":"linux","arch":"x64"})
npm WARN optional SKIPPING OPTIONAL DEPENDENCY<EMAIL_ADDRESS>(node_modules/chokidar/node_modules/fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for<EMAIL_ADDRESS>wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})
npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none was installed.
npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>|| ^4.0.0 but none was installed.
npm WARN MavensMate-Desktop-0.0.11-beta.7 No repository field.
npm WARN MavensMate-Desktop-0.0.11-beta.7 No license field.

The problem is when I run "npm start" or "sudo npm start" it gives me an error

Cannot find module 'electron-squirrel-startup'

I've search and found a few closed cases related to this issue, but there are no real solution or no proper explanation for external developer (using other languages)  to follow. What I can do to fix it?
related issues:
https://github.com/electron/windows-installer/issues/193
https://github.com/mongodb-js/electron-squirrel-startup/issues/27
https://github.com/mongodb-js/electron-squirrel-startup/issues/25

Should open agains MavensMate not against electron, sorry. Link new issue:
https://github.com/joeferraro/MavensMate/issues/1012


[DOCS] Documentation update for issue #102

Description
Solving Issue #102 will hide the API key and thus it won't be visible. However, users/contributors can generate their own API keys for their use or for testing purpose.
Documentation/installation instructions need to be updated proceeding this upgrade.
Raw steps:

Create a firebase project
create a web application
enable authorization as well as cloud firestore for the app.
in project settings find the api key and that's it! paste it in your local installation firebase.js!

Screenshots
No response
Additional information
These steps can be elaborated and presented clearly in the readme.
Help would be appreciated!

I can do this.!

under?


Add Vertica Database support for Airflow

I added the Vertica Database support. It reference the MySQL interrelated code.
It include:

Vertica Hook
VerticaOperator and VerticaToHiveTranser
pip install airflow[vertica]

Nice!

I'm merging it, but I might move it to a contrib/ folder later since there are no unit tests and I couldn't run them anyhow...


Load user-customisations lazily

This is primarily motivated by reducing the amount of work that trimming is unable to remove.
It will require applications (by which I mean the actual thing that uses StyledStrings, for example the REPL) to call load_customisations! itself. If there's a good spot to add that so it automatically gets done "at the right time, when appropriate to do so" that would be even better, but I'm not sure there's an obvious spot that can be done without the potential for headaches (e.g. what if it comes up within a withfaces call).
For now at least, perhaps this is a reasonable compromise.

I'm not sure it's worth doing this way; all users needing to call this manually seems like a much worse API and of course carries the risk that they will call it from their init method :smile:
As an alternative, we're ok as long as it's easy to avoid loading this package, i.e. Base and most stdlibs don't depend on it.

I'm not sure it's worth doing this way; all users needing to call this manually seems like a much worse API and of course carries the risk that they will call it from their init method 😄

The reason why I'm proposing this is because I think (perhaps I'm mistaken) the vast majority of users won't need to call this method manually. Most interactive/rich output comes up in the REPL, and if just the REPL calls load_customisations!() then nothing else will need to.
User scripts and certain statically-compiled files are the two cases that come to mind where a user might want to call it manually, but maybe that's a worthwhile tradeoff?

OK, that's good news. I'm ok with this then.

Let's give this a shot then :slightly_smiling_face:

Most interactive/rich output comes up in the REPL, and if just the REPL calls load_customisations!() then nothing else will need to.

Ok, but then when you all of a sudden run something outside the REPL things will no longer work? So you might have code that works as you expect because you have a transitive dependency on the REPL but when that dependency is dropped by some of your own dependencies all of a sudden you lose all customisation.

Yea, different visuals when running things in vs. out of the REPL is the potential downside.
I wonder if maybe this could be a good spot to use Preferences.jl so that this init step can be enabled by default, by disabled when trying to static-compile minimal executables?

I think this is not a good way to do this and should be reverted. If something like this is to be done it should be done actually lazily by having the library itself initialize the customizations the first time it uses something that needs it. Not requiring an explicit call to it.

I think this is not a good way to do this and should be reverted.

I'm open to reverting this.
I wonder if that Preferences idea I mentioned above might be a viable way of approaching this compromise from another (better) direction?

If something like this is to be done it should be done actually lazily by having the library itself initialize the customizations the first time it uses something that needs it. Not requiring an explicit call to it.

This is how I originally wanted to approach this, but it's not entirely straightforward which makes me slightly wary. For instance, we could just add it to the printing in io.jl, but then if printing occurs within a withfaces call then that risks the wrong styling being applied to both the active context as well as the top-level context values.
Loading on first printing/withfaces invocation might be viable though? I'll want to roll this idea around for a bit longer before giving it a shot though.

I don't think the lazy init approach solves our original problem, which was minimize the "surface area" of StyledStrings, esp. w.r.t. to code size + dependencies.
I'm not sure the TOML parser is actually a very heavy dependency w.r.t. code size (it's self-contained and a pretty simple grammar/spec) - might be worth a measurement. But it does seem undesirable to have, e.g., all Julia-built CLI apps dynamically loading StyledStrings faces on startup / first print.

TBH, I feel skeptical about the global Faces dictionary in the first place...
It seems like it creates a namespacing problem. If I called addface!(:emphasize => ...) in my library there's no guarantee that I won't pick up a conflicting :emphasize definition from another library. This makes it hard to make sure things will print "right" once composability is considered.
Even providing a global dictionary of Faces as a TOML seems challenging to me. If the "theming" included a standard set of Face names, so that the intended purpose of each Face was more-or-less standardized it would be more plausible to me that you could do a "palette swap" for accessibility, etc. without ruining printing for someone.
I feel like instead of working with a global dictionary of Faces, this feature should either (a) be removed, or (b) be reworked to work in terms of complete "palettes" instead of a global dictionary of Faces.

Cody and I have have had a chat about the concerns he raised in the above comments, and I think it's fair to say that we both see the single global faces dict as non-ideal, but not a terrible compromise. He's proposed an idea of "Palettes" that we're both interested in exploring and could come along in the future.
This is separate to the near-term future of the changes that Kristoffer has expressed dissatisfaction with. From here, our options are to:

Make no further changes
Revert this PR
Use a compile-time preference (can we do this reasonably without Preferences.jl, given it's not in the stdlib?), to set whether load_customisations! is called on init or not
Come up with a better balance of concerns/behaviour

The relevant considerations I'm aware of currently are:

Face customisations are done via parsing a TOML file
This was done unconditionally as an __init__ step
For static compiling in particular, we want it to be possible to not do this
load_customisations! achieves this, but runs the risk of non-REPL-run/static-compiled code behaving differently to how people expect

This makes me wonder if perhaps a good (4) would be something like this (it it possible?)
@static if !we_are_static_compiling()
    const __init__ = load_customisations!
end


Update api for modifying reservations

From the openpbs source it appears calling pbs_modify_resv with force as the extend arg is equivelent to the -Wforce option of pbs_ralter which enables admins to change things they usually couldn't, like: resv start time, end time, duration, and oversubscribe resources.
Add an option for this to the api

implemented by 379ccb3


fix: try to address an issue with client-side routing due to regex changes

I've been seeing issues with client-side routing, where it would not match paths. It looks like there have been some recent changes in this area, and if I make the leading / in this regex optional, things start working again.
I can't claim to totally understand what's going on here, but this seems to fix the weird issues I was seeing.

The tests seem to be failing with this PR

The failing tests (at least the ones I've looked at) are failing on a test that compares the route output to an expected value. The route output contains, among other things, the pattern used to match the route. So if you change the pattern from '\\/' to '\\/?', the tests are going to fail because the expected value of the route pattern still contains '\\/'. You'll need to adjust the relevant tests to expect a pattern containing '\\/?' before the unit tests will pass.
Also, it would help if you included, either in #1454 or better yer in this PR (written as a set of tests), a list of routes that fail with the code as-is, but pass with your suggested change.

See also #918 and #1049 for some previous routing issues that were fixed by changing the route-matching regex pattern. Please make sure that your change doesn't cause those issues to come back.

@rmunn can you offer any guidance? For me, every route client-side is broken without this fix. I can get to the first page through SSR, but then all subsequent links are broken.
I'm not sure how this is working for other people. Maybe I have something screwed up in my setup.
I assume there are regression tests for the other issues mentioned? If I get the tests passing, would that tend to indicate that everything is working as expected?

For clarity: before the change to this line, my setup was working flawlessly. Updating svelte broke things for me. Maybe there was some change in a changelog that I missed that outlined what I needed to do to keep things working with a new version?

@andyburke - Everything's working for me, so I can't really help you without specific examples. Can you create a reproduction with specific examples, please? I'm not going to be able to help unless you show me something that used to work and doesn't, and preferably make it a GitHub repo so I can clone it and reproduce it.
As I said last week:

Also, it would help if you included, either in #1454 or better yer in this PR (written as a set of tests), a list of routes that fail with the code as-is, but pass with your suggested change.

See https://github.com/sveltejs/kit/issues/1454#issuecomment-847542444


Using Sockets in Hyperswarm

I'm a little new to using Hyperswarm and moreover the entire space of communicating via Sockets.
I'm trying to build a simple chat application between two peers on the same machine. Super basic but just so I can try out Hyperswarm on a basic level.
I have two files that are both running the same code:
swarm.on("connection", (socket, details) => {
    console.log("new connection!", details);
    socket.write("send-message", { msg: "Client 1 has Joined" });
    socket.on("send-message", data => {
        console.log(data.msg);
        AskForUserInput(socket);
    });
});

function AskForUserInput(socket) {
    const rl = readline.createInterface({
        input: process.stdin,
        output: process.stdout
    });
    rl.question("What do you want to say: ", (answer) => {
        socket.write("send-message", { msg: "Client 2: " + answer });
        rl.close();
    });
}

Running the program in two terminals - I can see that they have both connected to each other, but I don't see any messages being transmitted. Is there something wrong with my approach?

Hi, I think your example is assuming that sockets behave kind of like socket.io where you can emit events on either side. Sadly, that isn't the case as sockets in Node are Duplex Streams which can only work with writing binary data.
I'd suggest looking into ndjson streams which will enable you to send objects between the two sides and have some sort of type field for the message type along with whatever other data you want for your message.

What @RangerMauve said


New commit.

Fixes #<issue_number_goes_here>

It's a good idea to open an issue first for discussion.

[x] Tests pass
[x] Appropriate changes to README are included in PR

Made a new commit

Hi


add a multiple node forward benchmark

Some users found that the number of nodes decrease the performance of dora-0.3.2. So I add this benchmark to test multiple-nodes case.
In the current version, with the growing number of nodes, the latency is stable, but the throughput drop down.
rust-node-0 -> rust-node-1 -> rust-node-2 -> ... -> rust-sink

Am I missing something?
Please be free to try it with cargo run --release --example multi-node-benchmark -- 20 (CPU Intel i9-12900H)

I'm sorry but I don't think that this is a good example to get started with dora. Could we move this to dora-benchmark.
Put this in the dora folder.
We can then compare this to other framework such as ROS2 or equivalent.

I'm sorry but I don't think that this is a good example to get started with dora. Could we move this to dora-benchmark.
Put this in the dora folder.
We can then compare this to other framework such as ROS2 or equivalent.

Cool! I never know this repo.
Thanks.


🔃 Refactor sending otp codes

A user signs up with an identifier through  post request to api/v1/profiles/.
This creates a Profile model and sends a post_save signal.
The post_save signal sends a 4 digit otp verification code to the provided identifier.
The signal was written quickly and isn't great code. Rewrite the signal to

only send otp codes if the otp_verified Profile model attribute is false
rewrite the signal code

Related files

profile view
post_save signal
profile model

Another perfectly valid fix to this is moved the creation of an otp code to the views file. Signals are out of date, so create a file for making and sending otp codes, and implement it into the necessary views.


multicore merlin

I have a fork of this repo with merlin and dot-merlin-reader. I've patched them to work with the 4.10 multicore fork. I based it off of HEAD so they have a few extra commits. Meaning, they don't technically match the current merlin release, 3.4.1.
I've bumped a long standing issue in the merlin repo to see if they'll house a branch that can track the multicore fork. Until I can get matched back up with a proper release number, would you accept a PR that is few patches ahead of the current merlin release?
https://github.com/mattpallissard/multicore-opam/tree/dev/multicore_410
https://github.com/mattpallissard/merlin
ocaml/merlin#823
Thanks in advance.

Thanks @mattpallissard. This is a valuable contribution. I haven't looked at the details of https://github.com/ocaml/merlin/issues/1197, but from your message it might be the case that a merlin branch to track multicore is tricky. Correct me if I am wrong.
If you can make a PR to this repo with your changes that point to your own repo, for now, it would already be useful.

I don't use merlin, but if someone who uses merlin can try it out, it would be quite useful feedback. @shakthimaan @Sudha247 @Engil?

@kayceesrk you're correct.  Up until recently merlin had support for multiple ocaml versions.  This made it easy to wire up a multi-core version that was detected at compile time.  However, going forward they decided to only support the latest version of ocaml.  As far as I can tell this makes implementing multi-core upstream impossible until it's merged into mainline.
PR opened, #40

Thank you for your efforts @mattpallissard! I tried your merlin multicore branch on VSCode and Atom, and it works great.

When I was using it with ocaml-lsp-server, the server crashed many times and stopped working on my multicore switch after a point. This probably has something to do with the lsp-server itself and not merlin.
I also see that effect syntax is not recognized by merlin, is this expected?

@Sudha247 I'm curious as to why it'd be crashing.  If you could come up with a reproduce able case I'd dig into it.
As for the effect syntax, I overlooked that let me look into fixing that and get back to you.

ocaml-lsp crashes even when using the no-effect-system branch with merlin, will try to debug it

My workaround
https://github.com/EduardoRFS/ocaml-lsp/commit/31a7b708f384458c807105e244557688c228d830

I've gone and added the effect syntax. I force-pushed so the git history was clean.
I haven't got around to testing it more than the output below.  I also haven't tried to use ocmal-lsp-server with the patched dot-merlin-reader yet.  I'll try to get around to that in the next day or two.
opam repo add matt-multicore "git+https://github.com/mattpallissard/multicore-opam.git#dev/multicore_410"
opam install dot-merlin-reader=3.4.1

~  cat test.ml
effect Conversion_failure : string -> int

~  ocamlmerlin single errors -filename test.ml < test.ml | jq
{
  "class": "return",
  "value": [],
  "notifications": [],
  "timing": {
    "clock": 6,
    "cpu": 4,
    "query": 0,
    "pp": 0,
    "reader": 1,
    "ppx": 0,
    "typer": 3,
    "error": 0
  }
}

~  echo $(ocamlmerlin single dump -what parsetree -filename test.ml < test.ml | jq '.["value"]')

"[
 structure_item (test.ml[1,0+0]..[1,0+41])
 Pstr_effect
 effect_constructor (test.ml[1,0+7]..[1,0+41])
 peff_name = \"Conversion_failure\"
 peff_kind =
 Peff_decl
 [
 core_type (test.ml[1,0+28]..[1,0+34])
 Ptyp_constr \"string\" (test.ml[1,0+28]..[1,0+34])
 []
 ]
 core_type (test.ml[1,0+38]..[1,0+41])
 Ptyp_constr \"int\" (test.ml[1,0+38]..[1,0+41])
 []
]

Thanks @EduardoRFS and @mattpallissard! https://github.com/ocaml-multicore/ocaml-multicore/pull/458 removes effect syntax from typed tree. I tested @mattpallissard's latest patch of merlin on top of that branch, ocaml-lsp seems not to crash anymore.

I patched ocaml-lsp-server to work with this version of merlin and verified that dot-merlin-reader works inas expected with the ocaml-multicore/ocaml-multicore:parallel_minor_gc branch. attached is my vim output using ocaml-lsp-server.
~  opam repo add matt-multicore "git+https://github.com/mattpallissard/multicore-opam.git#dev/multicore_410"
~  opam install dot-merlin-reader=3.4.1
~  opam pin add ocaml-lsp-server https://github.com/mattpallissard/ocaml-lsp.git

Thank you @mattpallissard! I can confirm that the patched ocaml-lsp works fine on both parallel_minor_gc and no-effect-syntax. Could you please add this ocaml-lsp patch to #40? It will be very useful.

I tried it and it works partially on the no-effect-syntax, on a Reason project that I've it keeps crashing, but with .ml files it works, maybe something related to ppx?

@Sudha247 I updated the PR, adding ocaml-lsp-server to it. I required the 3.4.1 version of merlin-dot-reader, which is included in the PR.
opam repo add matt-multicore "git+https://github.com/mattpallissard/multicore-opam.git#dev/multicore_410"
opam install ocaml-lsp-server

@EduardoRFS , I wound up rebasing off up upstream ocaml-lsp so there are quite a few changes.  If it still doesn't work after re-installing can you provide a minimal reproduce able example?

@mattpallissard just create a executable using .re(on dune you just need to install @opam/reason) write
open String;
let get = get;

And hover anything, your LSP will crash when using the no-effect-syntax

@mattpallissard just create a executable using .re(on dune you just need to install @opam/reason) write
open String;
let get = get;

And hover anything, your LSP will crash when using the no-effect-syntax

@EduardoRFS I don't plan on spending time debugging reason.   I did do a quick test and was unable to reproduce your issue.  Please make sure that you're using the correct versions from the multicore repo I posted above.

@EduardoRFS I don't plan on spending time debugging reason.   I did do a quick test and was unable to reproduce your issue.  Please make sure that you're using the correct versions from the multicore repo I posted above.

Merlin with multicore support has been added in #40. Closing this issue.
@EduardoRFS mentioned in a private thread that merlin and ocaml-lsp work with Reason now. If there are any other issues on Reason please feel free to open a new one.

Merlin with multicore support has been added in #40. Closing this issue.
@EduardoRFS mentioned in a private thread that merlin and ocaml-lsp work with Reason now. If there are any other issues on Reason please feel free to open a new one.


Cannot find module X from test suite

Setup:

GHC: 8.8.3
ghcide: 0.1.0
Editor: VSCode 1.43.2
Editor Extension: ghcide 0.0.2
OS: Windows 10 v1909

I'm trying out the tool and I find that there are some imports that ghcide cannot resolve, but GHCi  through cabal can.
My project structure is something like the following:
- src
   - ModuleA.hs
- test
  - ModuleATest.hs
- myproject.cabal
- ...

In ModuleATest I'm importing ModuleA for testing but ghcide reports Could not find module 'ModuleA'. On the other hand, GHCi (through cabal repl MyProject-test) can find the module and run the test suite with no problems.
The exact error I get is:
Could not find module `ModuleA'
It is not a module in the current program, or in any known package

Also, warnings like -Wunused-imports are not being picked up, but that's not the main issue here.
This is a part of my MyProject.cabal file
name:                MyProject
...
library
  exposed-modules:
    ModuleA
  build-depends:     base >= <IP_ADDRESS>
  hs-source-dirs:    src
  default-language:  Haskell2010
  ghc-options:
    -Wall
    -Wincomplete-record-updates

test-suite MyProject-test
  type:             exitcode-stdio-1.0
  main-is:          ModuleATest.hs
  hs-source-dirs:   test
  default-language: Haskell2010
  build-depends:
      MyProject
    , base >= <IP_ADDRESS>

I think this might be a duplicate of #470, but in this case, I'm not using any third-party libraries and I'm not getting a "hidden package error" but a "could not find module".

Your myproject.cabal files looks wrong, to be specific, your test-suite. In your build-depends, you specify ModuleA which looks like it is the module from your library. This is invalid, the build-depends section is only for package dependencies, e.g. you could have written:
test-suite myproject-test
  type:             exitcode-stdio-1.0
  main-is:          ModuleATest.hs
  hs-source-dirs:   test
  default-language: Haskell2010
  build-depends:
      myproject
    , base >= <IP_ADDRESS>

which signals cabal that your test-suite depends on the library of your project, assuming your package is named myproject.
I would have expected that cabal test and cabal repl test:myporject-test show some warnings, but maybe not.

Indeed, this is wrong. I changed some module names since this is a personal project but it seems like a made a mistake. I'll correct it.
The issue stands. Please, check the updated issue description

You should provide the debug output, e.g. from ghcide test/ModuleATest.hs or share your exact project if it is on github.
Alternatively, you could check if adding a hie.yaml such as
cradle:
  cabal:
    component: "test:myproject-test"

to the root of your project solves the problem. If yes, this is likely a mistake in the automatic project detection.

The provided solution works flawlessly. Adding a hie.yaml file like that to the root of the project allows ghcide to correctly check the import.
Should I report the bug to another repo as well, or this is strictly a ghcide bug?

I think this is expected behaviour of hie-bios which also has more documentation for the hie.yaml specification. Note though, that ghcide does not support multi-cradles yet, see #361.

Closing since this issue is related to hie-bios and not ghcide.


RuntimeError: unreachable executed when the underlying Rust crate panicked

We could reproduce some panicking of the underlying Rust crate using a specific area of interest.
The issue also arises when using the cli from a/b street.
Would you be so kind what causes the crash. Some common practices narrowing the data error down are needed. From a geospatial engineer perspective, we can easily validate and correct topology errors using our favorite geospatial tools. But, we don't know how to refer to the underlying OSM id by using the homebrewn "Road Ids" like "Road #704".
Here is the area of interest causing the crash:
Area of Interest
[2023-08-05T17:41:27Z WARN  osm2streets::road] named lane doesn't exist
[2023-08-05T17:41:27Z ERROR streets_reader::split_ways] Skipping Road #704: PL with total length 50.2574m and 10 pts has dupe non-adjacent pts
[2023-08-05T17:41:27Z ERROR streets_reader::split_ways] Skipping Road #860: PL with total length 54.0387m and 10 pts has dupe non-adjacent pts
thread 'main' panicked at 'called Option::unwrap() on a None value', /home/runner/.cargo/git/checkouts/osm2streets-fbbbdf753e406749/aba1831/osm2streets/src/lanes/classic.rs:522:13
note: run with RUST_BACKTRACE=1 environment variable to display a backtrace
[2023-08-05T17:41:27Z ERROR abstutil::time] dropping Timer while doing progress split roads, due to panic?

Hi, thanks for reporting this bug! I've fixed it in the osm2streets web app. The problem is https://www.openstreetmap.org/way/148338681 has sidewalk:left:width, but there's no sidewalk=left or sidewalk=both tag. In this case, arguably sidewalk=left is implied by the presence of the other tags, but I'm not sure what tagging standards people are adopting.
osm2streets doesn't currently use tagged lane or sidewalk widths. The code I removed above was outdated and actually had no effect (a later apply_width call overwrote it). I've had #222 and #223 in mind for a long time, but haven't gotten to starting them yet. I did file issues to track.
I'll keep this issue open to track better error handling in this part of the code in general. You're right that the logged IDs aren't helpful. When lane parsing code fails, the error message should clearly state the OSM way that failed, at least

Seems to work fine now, including the sidewalk width parsing, thanks to the switch to https://gitlab.com/LeLuxNet/Muv/


postgresql update, better formatting for create function

Update keyword, better formatting for create function

Sorry, not accepting this. Too many different changes in this pull request and no tests or examples of what exactly it fixes.


OpenStack node driver

We are using Rancher on our internal OpenStack.
Rancher has an OpenStack Node driver.
We have issues:
It does not appear possible to use an existing key (the config option is present, but it doesn't work).
Nodes are given Rancher-created keypairs therefore, but these are not cleaned up on cluster deletion.
Nodes are assigned floating IPs, but these are not properly cleaned up on node/cluster deletion. (we do not believe all nodes need floating IPs, but if they have them they need to be properly deleted when the node is deleted)
We have terraform that does node creation the way we like them, it might be helpful to be able to tie our terraform into rancher cluster deployment, is this a supported option?

Version 2.2.2 seems to work. Everything above it doesn't. Here is what I said in issue #22507
https://github.com/rancher/rancher/issues/22507#issuecomment-534901984


Update jGit to 6.2.0

Seems to have compile errors in Java 8
https://github.com/line/centraldogma/runs/7390942695?check_suite_focus=true#step:5:144

Oops, we need JDK 11 to use this jGit 11 version.
https://wiki.eclipse.org/JGit/New_and_Noteworthy/6.0
Let me leave this PR until we change to using JDK 11. (At least for server module)

We can close this since #808 is merged.


IPv6 addresses that begin with ::ffff: aren't processed as IPv4

For example, ::ffff:<IP_ADDRESS> is return as an IPv6 address instead of <IP_ADDRESS> IPv4

Intended behavior: it's an IPv4-mapped IPv6 address.


Fix no attributed class in Class attributes and instance attributes

Hi @dE-Falt
Can you please explain why this change is necessary. The output snippets run fine without it as well 😅

Hey @satwikkansal , I have tested current code snippet and snippet suggested in this PR, everything is the same on python 3.9 - 3.13. So this PR is suggested to close as not relevant


.isin() Assertion Error

I'm getting an assertion error with .isin() for blaze when the pandas returns the expected result.
# recentHist is a blaze object
historiesDF = bz.into(bz.DataFrame, recentHist)
In [22]: recentUserInteractionsDF = historiesDF[historiesDF.userID.isin(['5539cf3471e30cdb503c0dd8'])]
# Returns expected result

In [23]: recentUserInteractions = recentHist[recentHist.userID=='5539cf3471e30cdb503c0dd8']
in [24]: recentUserInteractions
# Returns expected result

in [25]: recentUserInteractions = recentHist[recentHist.userID.isin(['5539cf3471e30cdb503c0dd8'])]
in [26]: recentUserInteractions
Traceback (most recent call last):

  File "/Users/Dalton/anaconda/envs/dopamine/lib/python2.7/site-packages/IPython/core/formatters.py", line 339, in __call__
    return method()

  File "/Users/Dalton/anaconda/envs/dopamine/lib/python2.7/site-packages/blaze/interactive.py", line 329, in <lambda>
    Expr._repr_html_ = lambda x: to_html(x)

  File "/Users/Dalton/anaconda/envs/dopamine/lib/python2.7/site-packages/multipledispatch/dispatcher.py", line 163, in __call__
    return func(*args, **kwargs)

  File "/Users/Dalton/anaconda/envs/dopamine/lib/python2.7/site-packages/blaze/interactive.py", line 301, in to_html
    return to_html(concrete_head(expr))

  File "/Users/Dalton/anaconda/envs/dopamine/lib/python2.7/site-packages/blaze/interactive.py", line 193, in concrete_head
    return odo(head, DataFrame)

  File "/Users/Dalton/anaconda/envs/dopamine/lib/python2.7/site-packages/odo/odo.py", line 90, in odo
    return into(target, source, **kwargs)

  File "/Users/Dalton/anaconda/envs/dopamine/lib/python2.7/site-packages/multipledispatch/dispatcher.py", line 163, in __call__
    return func(*args, **kwargs)

  File "/Users/Dalton/anaconda/envs/dopamine/lib/python2.7/site-packages/blaze/interactive.py", line 316, in into
    result = compute(b, **kwargs)

  File "/Users/Dalton/anaconda/envs/dopamine/lib/python2.7/site-packages/multipledispatch/dispatcher.py", line 163, in __call__
    return func(*args, **kwargs)

  File "/Users/Dalton/anaconda/envs/dopamine/lib/python2.7/site-packages/blaze/interactive.py", line 178, in compute
    return compute(expr, resources, **kwargs)

  File "/Users/Dalton/anaconda/envs/dopamine/lib/python2.7/site-packages/multipledispatch/dispatcher.py", line 163, in __call__
    return func(*args, **kwargs)

  File "/Users/Dalton/anaconda/envs/dopamine/lib/python2.7/site-packages/blaze/compute/core.py", line 470, in compute
    result = top_then_bottom_then_top_again_etc(expr3, d4, **kwargs)

  File "/Users/Dalton/anaconda/envs/dopamine/lib/python2.7/site-packages/blaze/compute/core.py", line 164, in top_then_bottom_then_top_again_etc
    expr2, scope2 = bottom_up_until_type_break(expr, scope, **kwargs)

  File "/Users/Dalton/anaconda/envs/dopamine/lib/python2.7/site-packages/blaze/compute/core.py", line 348, in bottom_up_until_type_break
    for i in inputs])

  File "/Users/Dalton/anaconda/envs/dopamine/lib/python2.7/site-packages/blaze/compute/core.py", line 371, in bottom_up_until_type_break
    **kwargs)}

  File "/Users/Dalton/anaconda/envs/dopamine/lib/python2.7/site-packages/multipledispatch/dispatcher.py", line 163, in __call__
    return func(*args, **kwargs)

  File "/Users/Dalton/anaconda/envs/dopamine/lib/python2.7/site-packages/blaze/compute/mongo.py", line 215, in compute_up
    assert isinstance(predicate, Broadcast)

AssertionError

Hey @TDaltonC thanks for digging in on these issues! I don't think isin was implemented for mongo. Still, that shouldn't trigger an AssertionError. I'll take a look.

No problem @cpcloud! Just glad to hear I'm not a nuisance. Here's the ex-issue that made me think about trying it: https://github.com/ContinuumIO/blaze/issues/637
I think that this is a really great project. And I'm glad to play with it.


Mark a front side of point entities

(Especially, but not only because) while there is no support of loading models for point entities, it could be very useful to mark somehow a front side of point entities to show how entities are oriented in space (at least, selected ones). So we can easily check a monster's gaze direction etc. It could be an additional arrow, or specific color of front side or its' wireframe.

@Qwertyus3D
I do it in my bspguy fork :

https://github.com/UnrealKaraulov/newbspguy
But I don't have time that upport two bspguy versions, i want to make bspguy works for more games, instead of only one Sveen Coop (I just don't play this game) for this reason i can't support this bpsguy and pull request...


(PUP-8761) Make convert_to() accept additional arguments

Before this it was only possible to call convert_type() with just the
type but not with arguments to the type's new() function.
This is now possible.

CLA signed by all contributors.


[BUG] New-PnPAzureADGroup returns Object reference not set to an instance of an object with all the required fields.

Reporting an Issue or Missing Feature
New-PnPAzureADGroup not works as expected.
Expected behavior
New-PnPAzureADGroup -DisplayName a3 -MailNickname a3 -Description a3 should create a group.
Actual behavior
New-PnPAzureADGroup -DisplayName a3 -MailNickname a3 -Description a3 gives the following error:
New-PnPAzureADGroup: Object reference not set to an instance of an object.
Steps to reproduce behavior
Connect-PnPOnline
New-PnPAzureADGroup -DisplayName a3 -MailNickname a3 -Description a3
What is the version of the Cmdlet module you are running?
PnP.PowerShell 2.2.0
Which operating system/environment are you running PnP PowerShell on?

[X] Windows

It works if you use members AND owners with all the required fileds.
New-PnPAzureADGroup -DisplayName a3 -MailNickname a3 -Description a3 -IsSecurityEnabled -Members<EMAIL_ADDRESS>-owners "xxx@xxx"

The issue has been fixed , will be available in tomorrow's nightly.
You should also specify -IsSecurityEnabled or -IsMailEnabled parameter , if both are false, then also it wont work.


There should be the option to select countries

Hi,
first nice addon, congrats.
I need to select countries. The polygon tool is an awesome way to do that. It would be very pratical to have the option to select a country. Something like:
// returns a polygon list of the borders of the united states
ArrayList points = new CountryPoints_US<>();
GoogleMapPolygon overlay = new GoogleMapPolygon(points,
"#ae1f1f", 0.8, "#194915", 0.5, 3);
map.addPolygonOverlay(overlay);
Is there a plan to do something like that?

That's something that isn't definitely part of the addon. Anyone could make a separate project that has the borders of each country defined as polygons.


CORE-4991 - added option to enable dumplogging directories

replacing for https://github.com/corda/corda-runtime-os/pull/1901


Logout button missing padding on mobile devices

There seems to be some padding missing on the logout button on the account page on smaller devices.

Oh nice catch! If you fixed it on our side, would you be interested in making a PR with the styling changes?

Hi @Martinsos
I've fixed the issue. Please review the changes in PR #243.
Thank you!


Binary sensor for Doorbell button with "Pressed" and "Released" states

Is your feature request related to a problem? Please describe.
Currently HA users only have access to the "last_doorbell_ring" sensor, and the only available states are "Unavailable" and "Unknown".
My doorbell automation sends chimes through my house speakers. It's set to trigger on any state change. This works when the doorbell button is pressed, but the state sometimes changes randomly without apparent reason, causing doorbell chimes at odd hours like 3:30am. Not at all wife approved.
I'm wondering if another sensor can be added that supports "Pressed" and "Released" states.
Describe alternatives you've considered
I'm not aware of alternatives, but open to using a workaround if someone has one in mind.
Additional context
No response
Code of Conduct

[X] I agree to follow this project's Code of Conduct

Are you willing to resolve this issue by submitting a Pull Request?

[ ] Yes, I have the time, and I know how to start.
[X] Yes, I have the time, but I don't know how to start. I would need guidance.
[ ] No, I don't have the time, although I believe I could do it if I had the time...
[ ] No, I don't have the time and I wouldn't even know how to start.

Currently HA users only have access to the "last_doorbell_ring" sensor, and the only available states are "Unavailable" and "Unknown".

That kinda seems like a bug? Is there an open issue in HA?

I'm wondering if another sensor can be added that supports "Pressed" and "Released" states.

The doorbell should now be implemented as an event entity.  The event entity was not available when it was originally added to Home Assistant hummus integration is looking for a maintainer, and I’m just helping out to keep it warm until someone can be found, so we have to wait for them to take a look at that

Currently HA users only have access to the "last_doorbell_ring" sensor, and the only available states are "Unavailable" and "Unknown".

That kinda seems like a bug? Is there an open issue in HA issues?

I do not believe there is an open issue at HA, would you recommend I create one?
Than you for all your efforts @bdraco, I've followed the events here and appreciate the work you all do.

Currently HA users only have access to the "last_doorbell_ring" sensor, and the only available states are "Unavailable" and "Unknown".

That kinda seems like a bug? Is there an open issue in HA issues?

I do not believe there is an open issue at HA, would you recommend I create one?

Yes please. Hopefully someone knows what's wrong.
I will have access to a UI doorbell next month when I'm visiting family so I can try to replicate it than if nobody has come up with a solution by than.

Thank you for all your efforts @bdraco, I've followed the events here and appreciate the work you all do.

I'm happy to send you G4 Doorbell to keep if you like. It's a non-Pro version but it should work. Let me know.

My doorbell works fine, it is in HA as binary_sensor.g4_doorbell_pro_doorbell and can be Occupied and Clear as states.
This still works after HA version 2024.6.2.

My doorbell works fine, it is in HA as binary_sensor.g4_doorbell_pro_doorbell and can be Occupied and Clear as states.
This still works after HA version 2024.6.2.

That is an Occupancy sensor and not associated with the physical doorbell button on the device.

I'm happy to send you G4 Doorbell to keep if you like. It's a non-Pro version but it should work. Let me know.

I just logged into my family members's HA install and noticed that these sensors are disabled by default.  Once I enabled it, its showing the last ring as expected.

Is there a chance the sensor is disabled in HA?

My doorbell works fine, it is in HA as binary_sensor.g4_doorbell_pro_doorbell and can be Occupied and Clear as states.
This still works after HA version 2024.6.2.

That is an Occupancy sensor and not associated with the physical doorbell button on the device.

I am sorry, then I have misunderstood the issue...

I'm happy to send you G4 Doorbell to keep if you like. It's a non-Pro version but it should work. Let me know.

I just logged into my family members's HA install and noticed that these sensors are disabled by default. Once I enabled it, its showing the last ring as expected.

Is there a chance the sensor is disabled in HA?

Correct, I did the same thing. The "Last Doorbell Ring" entity is disabled by default. It's the closest entity type I can find that meets my needs. But I'm afraid the only available states are Unknown and Unavailable; nothing that is associated with button presses on the device itself.
Is there something else in HA I have to enable?

On second thought, that sensor I mentioned is the one I use to detect the button being pressed... pretty sure that is what it is for... Is that not what you want?

Yes, that binary sensor is what I also use for the doorbell press. However, it's just marked as an Occupancy sensor by default.

Is it not occupied as long as it's pressed? I cannot test that now as the family is already sleeping...

On second thought, that sensor I mentioned is the one I use to detect the button being pressed... pretty sure that is what it is for... Is that not what you want?

It's exactly what I want, but that specific sensor doesn't function that way for me. It seems to flip between Cleared and Detected based on camera detection. This I've tested. Pressing the doorbell does not toggle this state.
I have the G4 Doorbell Pro PoE if this matters.

Is it not occupied as long as it's pressed? I cannot test that now as the family is already sleeping...

I'm afraid not. Pressing the physical doorbell button does not toggle this state for me. Does it for you?

Is it not occupied as long as it's pressed? I cannot test that now as the family is already sleeping...

I'm afraid not. Pressing the physical doorbell button does not toggle this state for me. Perhaps you can test when your family wakes? Haha

Yes it does, I just tested it...

Is it not occupied as long as it's pressed? I cannot test that now as the family is already sleeping...

I'm afraid not. Pressing the physical doorbell button does not toggle this state for me. Perhaps you can test when your family wakes? Haha

Yes it does, I just tested it... I made sure to not be in frame as well...

I do know that the specific sensor you are referring to changes states from Cleared to Occupied on camera movement in my case. So for my automation, the chime will be ringing through the house speakers when motion is detected. Very not wife approved.
I'll test again when I get home in case something has changed in recent updates.

Since this is turning into a discussion, I'm going to go ahead and convert it


Add Menja Game

it's a game of cube cutting like fruit ninja @theDeviser please assign me

the issue has been assigned to you. Don't forget to add a readme.md file that contains information about the game


docs(Adopters): Add HELLA Aglaia

Just adding us to the Adopters list, which was long overdue.
Signed-off-by: Jens Keim<EMAIL_ADDRESS>

Not sure why the dead link check fails with 403 on https://hella-aglaia.com/... is there another link we could use @pepper-jk?

Not sure why the dead link check fails with 403 on https://hella-aglaia.com/...

I hope to get this fixed with https://github.com/oss-review-toolkit/ort/pull/9578.

Not sure why the dead link check fails with 403 on https://hella-aglaia.com/... is there another link we could use @pepper-jk?

We could try our parent company: https://www.hella.com
Would that be OK, @jens-erdmann ?

I hope to get this fixed with https://github.com/oss-review-toolkit/ort/pull/9578.

Okay, that would be preferable. If not I can try the alternative domain tomorrow, to see if it would technically work.

@pepper-jk please rebase and resolve conflicts.

Not sure why the dead link check fails with 403 on https://hella-aglaia.com/... is there another link we could use @pepper-jk?

We could try our parent company: https://www.hella.com Would that be OK, @jens-erdmann ?

I hope to get this fixed with #9578.

Okay, that would be preferable. If not I can try the alternative domain tomorrow, to see if it would technically work.

Should be fine. Not sure why we get errors on the first one.

The FunTest failing should be unrelated to the changes.
Should be ready for merge.

Since it can not auto-merge with the failing FunTest, it needs a manual merge.
I would prefer to force push again with my PGP signature first though, if that is alright we you.

Since it can not auto-merge with the failing FunTest, it needs a manual merge.

The test in question was already fixed. What we now saw on the last run was just test flakyness.

I would prefer to force push again with my PGP signature first though, if that is alright with you.

Fine with me.


soc: ti_simplelink: cc32xx: Remove ARMV7_M guard from CMSIS_IRQn_Type

Remove unnecesary #ifdef CONFIG_ARMV7_M guard in soc.h file.
Signed-off-by: Gil Pitney<EMAIL_ADDRESS>

Codecov Report

Merging #6009 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master    #6009   +/-   ##
=======================================
  Coverage   52.51%   52.51%
=======================================
  Files         406      406
  Lines       39683    39683
  Branches     7715     7715
=======================================
  Hits        20839    20839
  Misses      15663    15663
  Partials     3181     3181

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 6324d11...8067f16. Read the comment docs.


Please opt-out of HTML5 processing of ISO 8601 dates via setHTML5(false) if using setDateFormat()

All of the reports with dates are pulling up this error:
[Emergency] Uncaught LogicException: Please opt-out of HTML5 processing of ISO 8601 dates via setHTML5(false) if using setDateFormat()

Hi @Anytech I was passing :runner:  by and I take this opportunity to be useful to you and someone else, to use the HTML5 calendar you can use the setValue () method
DateField::create('Date')->setValue('YYYY-MM-DD')->setHTML5(true)

https://github.com/silverstripe/silverstripe-framework/blob/e63b73ad983f2ad402c5cdbfef4ba1e12461bc5b/src/Forms/DateField.php#L332

I am getting the same issue, but as a workaround added the following to config. Not sure if it would impact anything else though.
SilverShop\Reports\ShopPeriodReport:
disable_set_date_format: false

Fixed in https://github.com/silvershop/silvershop-core/pull/815/files


Add "Hidden" option to comamnds and options

A small branch that adds a way to hide internal options from the help output. Tests are missing, I'm happy to write them if there is a chance for this branch to get merged :)

Hm, not sure if the travis failure is related to my changes, but I can investigate if the direction of the branch looks ok.

Travis is happy now, yay! Is there anything I can do to help with this pull request? I would love to get feedback how its looking and what the chances for merging are :) Sorry for my impatience!

What is the use case for this?

On Sat, Apr 25, 2015 at 02:53:35AM -0700, Jesse van den Kieboom wrote:

What is the use case for this?

Our application needs to drop privileges for an unpack operation that
deals with untrusted data. With golang the best way to do that is to
exec a new binary. So we have a "--internal-unpack" switch that we use
for that. We could use a new binary of course, but that would increase
the on-disk footprint of the app quite considerable. Its really just
for internal use and there is no reason to show that on --help. But I
can imagine more use-cases for this like internal debug or self-test
options.
Cheers,
Michael

We've been using go-flags and love it. I came here looking for a way to achieve this functionality and would love to see this merged pending approval. Our use case is we have some options for a user facing binary that we intend to support in the future but do not wish to support now. The code is written with these options but we do not want to expose unsupported options in the help.

@mvo5: I'm not really convinced by your use case. Can't you just use environment variables for this?
@wcrissman: Also not very convinced about this use case, this is not a 90% case. If you don't want certain options yet, can't you just not make them go-flags options in the first place? (i.e. keep them in your options struct, but don't mark them with go-flags tags).
I'm being resistant here to avoid feature creep, and because I have not seen the issue of hiding options come up before.


kernel: _ClassInfo nodes own a lot of empty Sets

In my large ACX app compile scenario, 51288 _ClassInfo nodes retain 68.9MB, or about 1400 bytes on average.
146730 of the 153864  directExtenders, directMixers and directImplementers Sets are empty, i.e. 95%.
This is expected because leaf classes dominate in the application - all enum classes, protobuf messages classes and ACX template classes are leaf classes.
If these Sets were created lazily just before adding, it would save ~35MB, or half of the current heap retained by the _ClassInfo nodes (genericSuperType and genericSuperTypes are created this way but are actually less sparse in the app).

It is possible that a fix for #26081 would reduce the empty-Set overhead from 100% to 25%.


fix: use certification hours consistently

Since the value appearing on the /learn map was hardcoded, it could have
gone out of sync with the certifications, which were relying on
certification-settings
Also, for simplicity (and because it's hard to estimate accurately), all
the certifications are set to 300 hours.  Fullstack being the exception,
as it is a set of certifications.
Checklist:

[x] I have read freeCodeCamp's contribution guidelines.
[x] My pull request has a descriptive title (not a vague title like Update index.md)
[x] My pull request targets the main branch of freeCodeCamp.
[x] I have tested these changes either locally on my machine, or GitPod.

Closes #XXXXX

After a discussion in chat, the consensus was that the 300 hours on the learn map can go.  The certifications don't need changing.  Not beyond the changes already present in this PR.

So - the PR is unblocked now because we have a consensus?

It could go in, yeah, but I was going to remove the 300hrs from the learn map.

I vote to remove it from map.
Here is my reasoning from chat for our reference:
"We do communicate the difficulty of certificates when people sign in for freecodecamp, so there is no need for those 300hr estimates."

@ahmadabdolsaheb do you think we should remove the "Thousands of hours of challenges" bit from the map and mention that in the intro?

Yes. :)

After removing the hours:


使用mp.spawn启动比torch.distributed.launch慢很多

作者您好，我最近测试多GPU训练时遇到了使用mp.spawn启动比torch.distributed.launch慢很多的情况。
我发现使用mp.spawn方法后，每次个epoch开始时都会等待很久，但使用torch.distributed.launch启动时就没有出现这种情况。请问作者您在使用过程中有出现这种情况吗？

First, m afraid distributed.launch is the best practice if u don't need to custom the multiprocessing process.
mp.spawn is slow because its initialization or re-initialization is time-consuming, especially when you start multiple workers to load the dataset. This process is necessary to help you move data to the shared memory and perform the Tensor transfers between processes. Of course, you can handle it manually with Process(), share_memory(), and other APIs. For more detail, please refer to the document.

Thank you for your reply.


Change executable description

Can I change the description that is in task manager and others places in Windows?

You can use node-rcedit module to change FileDescription, ProductName and other properties of nw.exe file from NW.js package. These properties will get into your .exe file after build.

Works fine! The file properties was changed.
But the package files disappeared, the nwjs go back to default application, without my files.

You should change the properties of the nw.exe file from NW.js package (it's usually located at the "cache" folder) and only after that build you own application using nw-builder. In this case your files will remain.
Maybe there is a better solution.

Works fine! Thanks!


Update Excel.PivotCache.Refresh.md

The original text mentions a Chart Object, this is wrong.

Docs Build status updates of commit 525ea50:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

api/Excel.PivotCache.Refresh.md
:bulb:Suggestion
View
Details

api/Excel.PivotCache.Refresh.md

Line 2, Column 1: [Suggestion-description-missing] Missing required attribute: 'description'.

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel


feat: add security quality gates

add security quality gates

 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.


Avoid PHP notice logs (when enabled) about session already started

I have checked and it's the "Session already started" notice that with current EB repeatedly logs. So that's what this PR will address.
I've not seen "headers already sent". I'm curious to hear how and when to trigger this (and if it still triggers with this patch).


H2o Module Not available error from the Azure Portal Function App (Python runtime)

Related to One of the fellow's SO Thread.
Azure Function App - Python Runtime (3.9v) - Timer Trigger + H2o Module
Working locally with the H2o module versions <IP_ADDRESS> & <IP_ADDRESS>!
In the Portal, we are also getting the same error: "Module Not Found Error: No module named "h2o"
Code:
import datetime
import logging

import azure.functions as func
import h2o

def main(mytimer: func.TimerRequest) -> None:
    utc_timestamp = datetime.datetime.utcnow().replace(
        tzinfo=datetime.timezone.utc).isoformat()

    if mytimer.past_due:
        logging.info('The timer is past due!')

    h2o.init()
    h2o.demo("glm")

    logging.info('Python timer trigger function ran at %s', utc_timestamp)

requirements.txt:
azure-functions
h2o==<IP_ADDRESS>

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

ID: 542c2bdc-5868-71d5-1d1a-a2c6d61744b0
Version Independent ID: 1bba15a0-227a-8137-a023-90b8df19881b
Content: Create a Python function using Visual Studio Code - Azure Functions
Content Source: articles/azure-functions/create-first-function-vs-code-python.md
Service: azure-functions
GitHub Login: @ggailey777
Microsoft Alias: glenga

@HariKrishnaRajoli-MT Thanks for reporting this error. We will review and update as appropriate.

@HariKrishnaRajoli-MT MicrosoftDocs Github issue is mainly related to the document issue and not related to troubleshooting issue. I will recommend creating a thread on the forums - Microsoft Q&A or Stack Overflow
As you are getting h2o module not found error make sure you have installed the added h20 module in your requirement.txt file. For more details refer to package management section
Module Not Found Error: No module named h2o
If the modules can be installed using pip then you can mention the same in your requirements.txt
But in case if those module or dependencies cannot be installed using pip then you need to use build native dependencies or enable remote build.
You can refer to python troubleshooting document for more details.
I will go ahead and close this thread as I don't see any document issue. Feel free to tag me in if you have any queries or concerns.


Copy attachments for dev mailbox

The development mode mock adapter is extremely useful, but currently has a significant limitation: the attached file appears to simply be a pointer to wherever in the filesystem the attachment was located at the time the email was created.
Normal program operation might involve that attachment being deleted immediately after the email is sent, or it might involve a file whose contents change over time.
Copying the attachment data into a new file would make the dev mock adapter considerably more useful for workflows which involve attachments.

Closing with #306


How to execute?

How do I run openconnect-gui after installing it? I have tried openconnect-gui from the terminal command-line and searched for it with spotlight but cannot find a way to execute the program.

The formula builds a .app that you want to copy to your Applications folder. Something like
cp "$(brew --prefix)/Cellar/openconnect-gui/build-release/bin/OpenConnect-GUI.app" /Applications

although I probably have the paths slightly wrong.

open /usr/local/Cellar/openconnect-gui/1.5.3/OpenConnect-GUI.app will do the trick :)

Thanks, I had forgotten about this old issue. IIRC it was a path and dependancy issue. Differences on Linux and Mac. Closing.


After updating project to 0.5.1 Firefox gives error

Edge and Chrome are working normally, Firefox no.
Error: Exception Double Fault blazor.webassembly.js:1:35409
Please check site

After clearing browser history problem solved.
There is still problem - why browser not updates cached files automatically when new version detected.


AppImage does not run on Ubuntu 14.04

The AppImage does not run on Ubuntu 14.04 which currently is the oldest still-supported distribution: AppRun: /usr/lib/x86_64-linux-gnu/libstdc++.so.6: version 'CXXABI_1.3.9' not found
Please see https://github.com/AppImage/AppImageKit/wiki/Creating-AppImages#creating-appimages-that-are-compatible-with-many-systems and especially https://github.com/AppImage/AppImageKit/wiki/Creating-AppImages#libstdcso6.
References:

https://github.com/AppImage/appimage.github.io/pull/552
https://travis-ci.org/AppImage/appimage.github.io/builds/398998404#L618

Well, since Sielo event not build on Ubuntu 14.04 beceause it use C++17, I'll not support Ubuntu below the 16.04 :smile:
Thank you!

Thanks for the clarification @Feldrise. Is it a good idea to depend on C++17 already when there are still plenty of still-supported distributions out there that do not support it? This means that you are essentially cutting off users running on otherwise still-supported distributions from using Sielo.

I don't really have the choice since I'm using ndb.
It's true that it's make Sielo not available on some distribution, but now it's not always hard to have at least GCC 7 or clang 5.
Sielo is still available on most Linux distribution though :wink: