Set DevelopmentDependency to true

Setting the DevelopmentDependency to true will make NuGet client set the assets to private.
Currently NuGet shows the following:

NuGet shows the following on a package that has the flag set:

I came here to raise this same PR 😆


[content] stuff to surface for current contributors

[ ] api-conventions.md (source: gh issues, focus groups)
[ ] Test debugging docs and other general testing/ci docs (source: survey)
[ ] Other Devel doc links as resources - maybe list a table of contents? the devel README? (source: survey, gh issues)
[ ] how to contribute to docs / release notes
[ ] community-membership.md (source: survey)
[ ] About contributor experience (source: survey)
[ ] KEPs - what they are and where to find them (source: everyone)
Ideal state: python peps
[ ] How the project is organized
[ ] Sig list
[ ] Governance (high level blurb with resource links to full details)
[ ] Subproject OWNERs, approvers, and reviewers
Think about this group in the next iteration
Rewards and recognition - tbu

Taking from this doc and setting as an issue so we can close the doc down.

confirming with github analytics against the community repo that we should definitely surface api-conventions as a first class piece of content on the site. in order of highest views:
api-convention.md
Entire community repo
Architecture
Horizontal pod autoscaler
Entire devel folder
Sig list
Contributor guide
Resource metrics api

Per a conversation with @parispittman--I am going to be taking this on. :)

/assign @celanthe

Specific content can be imported pretty easily. The scripts are in place, the documentation though is not 😬 I'll create an issue to update that.
/remove-lifecycle stale

Hello, @mrbobbytables and @parispittman , I am outreachy applicant and have applied for Technical Writer, Can I start contributing to this issue, since there is around a month in results 😄 ?

I'm happy to let @vishakhanihore contribute to this as well @parispittman @mrbobbytables -- It would be nice to have some help! :)

Hi all, just an update, wanted to circle back with @parispittman @mrbobbytables about having @vishakhanihore and I collaborate on this with y'all once things calm down a bit after KubeCon! :) If that sounds good, let me know! :) Looking forward to it and thanks so much!

/remove-lifecycle stale
On Mon, 17 Feb, 2020, 00:00 fejta-bot<EMAIL_ADDRESS>wrote:

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually
close.
If this issue is safe to close now please do so with /close.
Send feedback to sig-testing, kubernetes/test-infra and/or fejta
https://github.com/fejta.
/lifecycle stale
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/kubernetes-sigs/contributor-site/issues/60?email_source=notifications&email_token=AM6PS4SAWEKV4RC4BZ6UERLRDGA4XA5CNFSM4HJG7MXKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEL4ON5I#issuecomment-586737397,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AM6PS4WIYWP6M3MJE4UNSPDRDGA4XANCNFSM4HJG7MXA
.

Hi all--As I'm stepping back from contributing outside of my Storyteller role on the Upstream Marketing team, I've unassigned myself from this issue. Was wondering if @vishakhanihore was still interested in taking it on?

/lifecycle frozen

I'd like to see the content currently in https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api_changes.md published on https://k8s.dev/ so that it has a stable URI (and there's an opportunity to redirect to it if there is ever a change).

Looking at https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md I think this is also elevant to people who aren't planning to contribute to Kubernetes (eg: someone writing a CustomResourceDefinition or a controller).
Should that page move to within https://kubernetes.io/ ?

/assign

/remove lifecycle-frozen

/remove-lifecycle frozen


⚠ Bofrost.be has degraded performance

In e53d99b, Bofrost.be (https://www.bofrost.be) experienced degraded performance:

HTTP code: 200
Response time: 1610 ms

Resolved: Bofrost.be performance has improved in 0991483 after 11 minutes.


4YI: Yet another catastrophic failure of NoScript

Name 	Firefox
Version 	78.0.1
Build ID<PHONE_NUMBER>5452
NoScript	11.0.33	true	{73a6fe31-595d-460b-a920-fcc0f8843232}
The OS is Ubuntu 20.04.
All the other webexts are disabled and the browser has been restarted.
<!doctype html>
<html>
	<head>
		<title>NoScript bypass</title>
		<script>
			alert("Maone, your NoScript is shit.");
		</script>
	</head>
</html>

P.S. The file has been served over HTTP using a local web server on <IP_ADDRESS>. In the wild the bypass has been observed in Google search results (not all the queries, it seems it depends on a query, the query was a constant from a very popular open source library written in C).

This was a  11.0.33 regression from the fix for https://bugzilla.mozilla.org/show_bug.cgi?id=1650305, and it's fixed in 11.0.34 (already in auto-update).
@KOLANICH, if you wanted to do something useful you could have reported in a place where I could actually notice it.
I've seen your troll "report" just because someone else reported it here: https://forums.informaction.com/viewtopic.php?p=102453#p102449
And fortunately I had already fixed the issue by that time.

Agreed. If there are bugs, report them to the dev. Especially given this is used tightly in Tor Browser
@hackademix Apologies, I've edited the first post and title

@hackademix,

My main goal was to warn the people to be careful. When I saw the bug, I had to flip javascript.enabled to mitigate it. I was pretty sure that somewhen it will reach you and be fixed.
It was not the first time NoScript CSP-based protection has been bypassed (including compromise within Tor Browser, so for Tor Browser I recommend not to rely on NoScript and just set javascript.enabled into false, even if it will break pdf.js and some of the about: pages).

I cannot blame you for Mozilla's design choices (the proper solution is to implement capabilities equivalent to javascript.enabled but per a browser tab, and allow extensions to change them, see https://bugzilla.mozilla.org/show_bug.cgi?id=1553791 for more info). But it is obvious that any protection based on CSP is pretty unreliable, CSP was not designed for this use case, in fact the browsers have not been designed with supporting such usage of webextensions in mind. I feel like CSP-based protection is not enough and should be supplemented by filterResponseData: we should just cut all the active content out of the HTML. Of course it will cause overhead and latency (again, the proper solution with smaller overhead can be https://bugzilla.mozilla.org/show_bug.cgi?id=1553791 ) and some maintaince burden (we also need to sanitize on* attrs in HTML, and the list of them needs maintainment, I wonder if we can parse the list from Firefox source code available on DXR), but it is better than allowing malware to be run, right?

https://forums.informaction.com

Long ago I have tried to sign-up there, but was presented with an unsolvable reCAPTCHA. As you see, your forum is very visitor-friendly. Have never visited that forum after that.


Solarthing stopped working after installing updates

Hi, I've been using solarthing for about a year and it's been working great - thanks for sharing your awesome work!
I installed some updates on the Raspberry Pi today and solarthing stopped working.  Logs below.
Any ideas as to what is wrong?
Thanks,
Mark

2023-05-10 15:29:31.085 [main] INFO  me.retrodaredevil.solarthing.program.SolarMain - [LOG] Beginning main. Jar: Jar: solarthing-2023.2.0.jar Last Modified: 2023-03-11T23:11:53Z Java version: 11.0.18
2023-05-10 15:29:31.470 [main] INFO  me.retrodaredevil.solarthing.program.SolarMain - Running as pi
2023-05-10 15:29:31.471 [main] INFO  me.retrodaredevil.solarthing.program.SolarMain - Using base configuration file: config/base.json
2023-05-10 15:29:32.753 [main] INFO  me.retrodaredevil.solarthing.program.RequestMain - Beginning request program
2023-05-10 15:29:32.758 [main] INFO  me.retrodaredevil.solarthing.analytics.AnalyticsManager - Google Analytics is ENABLED!
2023-05-10 15:29:33.758 [main] INFO  me.retrodaredevil.solarthing.analytics.AnalyticsManager - Sending program type to Google Analytics
2023-05-10 15:29:34.685 [main] INFO  me.retrodaredevil.solarthing.program.PacketHandlerInit - Commands are disabled
2023-05-10 15:29:34.980 [main] INFO  me.retrodaredevil.solarthing.program.SolarMain - Got an UnsatisfiedLinkError which is uncommon. If setup correctly, after this crash program will relaunch (hopefully successfully).
2023-05-10 15:29:34.981 [main] ERROR me.retrodaredevil.solarthing.program.SolarMain - [LOG] Ending SolarThing. Jar: solarthing-2023.2.0.jar Last Modified: 2023-03-11T23:11:53Z Java version: 11.0.18
2023-05-10 15:29:34.982 [main] ERROR me.retrodaredevil.solarthing.program.SolarMain - (Fatal)Got throwable
java.lang.UnsatisfiedLinkError: /tmp/jSerialComm/1683728974974-libjSerialComm.so: /tmp/jSerialComm/1683728974974-libjSerialComm.so: cannot open shared object file: No such file or directory
	at java.lang.ClassLoader$NativeLibrary.load0(Native Method) ~[?:?]
	at java.lang.ClassLoader$NativeLibrary.load(ClassLoader.java:2445) ~[?:?]
	at java.lang.ClassLoader$NativeLibrary.loadLibrary(ClassLoader.java:2501) ~[?:?]
	at java.lang.ClassLoader.loadLibrary0(ClassLoader.java:2700) ~[?:?]
	at java.lang.ClassLoader.loadLibrary(ClassLoader.java:2630) ~[?:?]
	at java.lang.Runtime.load0(Runtime.java:768) ~[?:?]
	at java.lang.System.load(System.java:1837) ~[?:?]
	at com.fazecast.jSerialComm.SerialPort.<clinit>(SerialPort.java:248) ~[solarthing-2023.2.0.jar:?]
	at me.retrodaredevil.io.serial.JSerialIOBundle.createSerialPortFromName(JSerialIOBundle.java:77) ~[solarthing-2023.2.0.jar:?]
	at me.retrodaredevil.solarthing.config.io.SerialIOConfig.createIOBundle(SerialIOConfig.java:45) ~[solarthing-2023.2.0.jar:?]
	at me.retrodaredevil.solarthing.io.ReloadableIOBundle.reload(ReloadableIOBundle.java:56) ~[solarthing-2023.2.0.jar:?]
	at me.retrodaredevil.solarthing.io.ReloadableIOBundle.<init>(ReloadableIOBundle.java:31) ~[solarthing-2023.2.0.jar:?]
	at me.retrodaredevil.solarthing.config.request.modbus.ModbusDataRequester.create(ModbusDataRequester.java:51) ~[solarthing-2023.2.0.jar:?]
	at me.retrodaredevil.solarthing.program.RequestMain.lambda$startRequestProgram$1(RequestMain.java:53) ~[solarthing-2023.2.0.jar:?]
	at java.util.stream.ReferencePipeline$3$1.accept(ReferencePipeline.java:195) ~[?:?]
	at java.util.ArrayList$ArrayListSpliterator.forEachRemaining(ArrayList.java:1655) ~[?:?]
	at java.util.stream.AbstractPipeline.copyInto(AbstractPipeline.java:484) ~[?:?]
	at java.util.stream.AbstractPipeline.wrapAndCopyInto(AbstractPipeline.java:474) ~[?:?]
	at java.util.stream.ReduceOps$ReduceOp.evaluateSequential(ReduceOps.java:913) ~[?:?]
	at java.util.stream.AbstractPipeline.evaluate(AbstractPipeline.java:234) ~[?:?]
	at java.util.stream.ReferencePipeline.collect(ReferencePipeline.java:578) ~[?:?]
	at me.retrodaredevil.solarthing.program.RequestMain.startRequestProgram(RequestMain.java:54) ~[solarthing-2023.2.0.jar:?]
	at me.retrodaredevil.solarthing.program.RequestMain.startRequestProgram(RequestMain.java:40) ~[solarthing-2023.2.0.jar:?]
	at me.retrodaredevil.solarthing.program.SolarMain.doMainCommand(SolarMain.java:151) ~[solarthing-2023.2.0.jar:?]
	at me.retrodaredevil.solarthing.program.SolarMain.doMain(SolarMain.java:212) ~[solarthing-2023.2.0.jar:?]
	at me.retrodaredevil.solarthing.program.SolarMain.determineMainSubprogram(SolarMain.java:272) ~[solarthing-2023.2.0.jar:?]
	at me.retrodaredevil.solarthing.program.SolarMain.main(SolarMain.java:286) ~[solarthing-2023.2.0.jar:?]

There are a few possible issues that this relates to: (leaving these here for documentation purposes, you can ignore them)

https://github.com/Fazecast/jSerialComm/issues/313#issuecomment-974340495

May need to specify -Dos.arch_full=armv7-hf in command line parameters.

https://github.com/Fazecast/jSerialComm/issues/486#issuecomment-1503779079

May need to do System.setProperty("fazecast.jSerialComm.appid", "YOUR_APPLICATION_IDENTIFIER"). (Unlikely to be the problem unless you are running multiple SolarThing instances)

Linking this relevant issue: https://github.com/wildmountainfarms/solarthing/issues/74

Can you run uname -a and paste its output? What kind of Raspberry Pi do you have? Can you run ls -la /tmp/jSerialComm/ and paste its output? I want to see if the permissions on that temporary directory are weird for any reason.
Secondly, have you always run SolarThing using the pi user or were you just doing that to see the output of the program more easily? If you normally run SolarThing using the solarthing user (configured by default for systemd setups), can you see if the output is any different when doing sudo -u solarthing ./run.sh rather than just ./run.sh. Alternatively, you can just let the systemd service crash and then look in the logs directory inside /opt/solarthing/program/custom_rover/logs/log_info.log and confirm the error is the same as above.
As a worse case scenario, I can update SolarThing to allow the option to use a different serial library. I think I had that option a while back but I scrapped it when I realized I didn't need it anymore.

Thanks for looking into this.
It's a Pi 4 Model B
uname -a gives
Linux ShedPi 6.1.21-v8+ #1642 SMP PREEMPT Mon Apr  3 17:24:16 BST 2023 aarch64 GNU/Linux

Output of ls -la /tmp/jSerialComm/:
total 8
drwxrwxrwx  2 solarthing solarthing 4096 May 10 18:22 .
drwxrwxrwt 20 root       root       4096 May 10 18:22 ..

I have always used pi.  Just tried running as solarthing and got the same error.

Alright I want you to try a couple of things. I suspect this has something to do with the arm64 architecture. I want to try to modify some of the arguments being passed to the java command so first, as a control, I'll have you run this:
pi@ShedPi:/opt/solarthing/program/custom_rover$ java --add-opens=java.base/java.lang.invoke=ALL-UNNAMED -jar ../solarthing.jar config/base.json

That should give you the same error. Now I want you to try to run this:
java --add-opens=java.base/java.lang.invoke=ALL-UNNAMED -Dos.arch_full=armv8_64 -jar ../solarthing.jar config/base.json

If that gives you the same error I want you to try this:
java --add-opens=java.base/java.lang.invoke=ALL-UNNAMED -Dos.arch_full=armv8_32 -jar ../solarthing.jar config/base.json

If that still does not work, try this command:
java --add-opens=java.base/java.lang.invoke=ALL-UNNAMED -Dos.arch_full=armv7-hf -jar ../solarthing.jar config/base.json

And then also try this:
java --add-opens=java.base/java.lang.invoke=ALL-UNNAMED -Dos.arch_full=armv7 -jar ../solarthing.jar config/base.json

Notice I am just changing this: -Dos.arch_full=arm*** in the above commands. I'm not sure if it's going to fix it, but it's worth a shot. (This relates to https://github.com/Fazecast/jSerialComm/issues/313)

All of those give errors, including the following:
Unknown argument: config/base.json

I suspect there's a flag missing?

That's my bad. Before that argument you need to include run --base config/base.json. I'll update my comment now.

Ooh!  Looks like -Dos.arch_full=armv7-hf did it!
Thank you so much!
Now, how do I make that stick?

Brilliant, I'm back up and running. Cheers for your help, I've thrown a pint or two your way :)

Thanks for the donation :smile:. I'm going to reopen this issue as it's something I need to come back to. I believe more RPi4s may be affected by this. Glad your setup is working, though.

@MarkSmurph I was curious if you had any problems with this since you got it working?

No, it's worked flawlessly since you sent me the fix. Thanks!


Parser and tokenizer implemented

Closes: #11

PR-Codex overview
This PR adds new classes and functionality to the Flatty language.
Detailed summary

Added new classes: Token, ArrowToken, BracketToken, StringToken, Entity, Empty, Data, Lambda, Locator, FlatObject, ObjectWithApplication, and Tokenizer
Added a new Parser class for parsing Flatty code
Added new methods and fields to existing classes
Updated DummyTest and added a new ParsingTests class for testing the new functionality.

The following files were skipped due to too many changes: src/main/java/org/objectionary/Parser.java

✨ Ask PR-Codex anything about this PR by commenting with /codex {your question}

998 linter errors, I will fix it later

@yegor256 I've been trying for hours to solve the checkstyle problems, but there are still too many. I will have to postpone this activity for a while, unless you have another solution.

@volodya-lombrozo please, review this one

@yegor256 @volodya-lombrozo I will close this PR and create several smaller PRs.


Page Speed Insights complaint

First of all I want to thank for this nice and handy module. Want to use it for an upcoming project and did some performance testing. Google Page Speed Insights complains with Eliminate render-blocking resources when using this module. Looks like /css2?family=Inter:wght@400;700&display=swap is blocking loading.
I configured the module like this:
googleFonts: {
    families: {
      Inter: [400, 700],
    },
    display: 'swap',
  },

Any idea how to solve this? Thanks!

Hi @bart
We must use one of these ways:
https://stackoverflow.com/questions/25230264/how-to-keep-css-from-render-blocking-my-website
https://frontmend.com/asynchronous-google-fonts

Hi @bart
Fixed on v1.1.0

Awesome, thanks a lot @ricardogobbosouza

This makes AMP pages invalid. There's a way to make this an option? #24

Fixed on v1.1.3

Question guys, where am I to place this link tags. app.html?

Question guys, where am I to place this link tags. app.html?

Just add @nuxtjs/google-fonts to the buildModules section of nuxt.config.js:
https://google-fonts.nuxtjs.org/setup


💡 Ideas: Type systems for numbers

📝 Description
Similarly to the discussion #28 for Double numbers, we would like to create ideas in GitHub Discussions for adding new type systems for numbers represented by the following types: Byte, Short, Long and Float.
✅ Checklist

[ ] Create the discussion for Byte numbers.
[ ] Create the discussion for Short numbers.
[ ] Create the discussion for Long numbers.
[ ] Create the discussion for Float numbers.

We are planning to provide a good representation of real-world integers (#620), fractions and decimals. So we will not implement this issue.


PWA offline mode not working

I did a fresh install of a new project:
vue init pwa testingpwa
cd testingpwa
yarn

After that I generate the build for production:
npm run build

Then start that build using a local server:
cd dist
started my web server: http://localhost:8080

I access the app using Samsung Galaxy Tab 2 using the IP of my computer
http:<IP_ADDRESS>:8080

The web app opened and I added the application to Homescreen
After I go offline using airplane mode and try to open application using the icon on my homescreen.
The PWA not worked, It show offline. My browser is Google Chrome 58.0.3029.83

Are you browsing Google.com.br or your webapp?

No, I get the screenshot in my pc because I do not know how to do this in mobile :D , I only wanna show the image tha appears.

Yep, maybe I've understood the issue, you browsed and are browsing from <IP_ADDRESS>, but currently, this PWA is implemented to be tested only using <IP_ADDRESS>/8 subnet
So you have to browse <IP_ADDRESS>, turn off the Internet and reload, everything should work fine.

But if I test with a mobile? I only can access using my IP address.

If I remove this line in condition it will work?
(window.location.protocol === 'https:' || isLocalhost)
I will test here

I tried and not worked, I need HTTPS?

Well, I tried with https, on port 443, and not worked, I think that have a problem caching files, and in my PC browser always have many errors that can not fetch manifest.json and service-worker.js

You generally need to either be directly running off of localhost (whitelisted) or a domain with HTTPS setup in order for the Service Worker to successfully register.
I'm unsure about the specifics of the setup above, but if you're trying to test on mobile I'd recommend plugging your phone up to your system over USB and using DevTools remote debugging which will let you test your local version with SW correctly: https://developers.google.com/web/tools/chrome-devtools/remote-debugging/

Well, I will waiting for #12 , because it apears to me and i will try again another day, but I think this is strange, I created a PWA that works offline, without vue, and it worked like I expected, doing the same tests here, I did it manually, maybe I miss something using with vue-cli. Thanks and regards everyone.

@addyosmani
sorry to dig up this old issue, but kinda have the same issue, not abble to make offile work...
not sure i do smth wrong...
what i did :

init the vue pwa app with vue-cli
add codes
ran yarn dev
then in network panel of devtool set offline
reload
and it fails

is there smth that i don't get ?
thanks

Should be reopened as i have the same problem.
I typed : vue init pwa test, cd test, npm install, npm run dev
Then i checked the offline box on Chrome devtools once the page was loaded, and i got an error as i have no longer internet, that means Service worker doesn't work correctly.

@eMerzh Unless you modified your webpack config, offline shouldn't work in dev mode. You don't want assets to be cached while in development.


Add test cases for int32 and int64 type

Codecov Report

Merging #89 (5eaa3c0) into master (8b3bc49) will increase coverage by 4.49%.
The diff coverage is 91.53%.

@@            Coverage Diff             @@
##           master      #89      +/-   ##
==========================================
+ Coverage   59.17%   63.66%   +4.49%
==========================================
  Files          38       38
  Lines       25985    28008    +2023
==========================================
+ Hits        15377    17832    +2455
+ Misses      10110     9626     -484
- Partials      498      550      +52

Impacted Files
Coverage Δ

encode_vm_escaped.go
67.44% <85.50%> (+4.69%)
:arrow_up:

encode_vm.go
53.16% <90.38%> (+5.60%)
:arrow_up:

encode_vm_indent.go
61.04% <95.48%> (+6.04%)
:arrow_up:

encode_vm_escaped_indent.go
67.74% <95.55%> (+5.33%)
:arrow_up:

encode_opcode.go
62.34% <0.00%> (+0.61%)
:arrow_up:

decode_compile.go
82.64% <0.00%> (+0.82%)
:arrow_up:

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 8b3bc49...5eaa3c0. Read the comment docs.

Codecov Report

Merging #89 (5eaa3c0) into master (8b3bc49) will increase coverage by 4.49%.
The diff coverage is 91.53%.

@@            Coverage Diff             @@
##           master      #89      +/-   ##
==========================================
+ Coverage   59.17%   63.66%   +4.49%
==========================================
  Files          38       38
  Lines       25985    28008    +2023
==========================================
+ Hits        15377    17832    +2455
+ Misses      10110     9626     -484
- Partials      498      550      +52

Impacted Files
Coverage Δ

encode_vm_escaped.go
67.44% <85.50%> (+4.69%)
:arrow_up:

encode_vm.go
53.16% <90.38%> (+5.60%)
:arrow_up:

encode_vm_indent.go
61.04% <95.48%> (+6.04%)
:arrow_up:

encode_vm_escaped_indent.go
67.74% <95.55%> (+5.33%)
:arrow_up:

encode_opcode.go
62.34% <0.00%> (+0.61%)
:arrow_up:

decode_compile.go
82.64% <0.00%> (+0.82%)
:arrow_up:

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 8b3bc49...5eaa3c0. Read the comment docs.


Submit data to data-raw folder

Hi @albossard, please add your (raw) data to this folder:
https://github.com/Global-Health-Engineering/chembebricks/tree/main/data-raw
Thanks

Please also edit the dictionary.csv to add documentation for the added data set.


idempotent requests should be retryable irrespective of the state of the connection

According to RFC  ( https://tools.ietf.org/html/rfc7231#section-4.2.1 ) all the idempotent methods should be retryable but we can at least try to retry the safe requests. The methods GET, HEAD, OPTIONS, and TRACE are considered safe.
ATS does not retry any requests based on the connection state with Origin Server and bytes sent to Origin Server. ATS should retry all the safe requests to give a chance to serve the request instead of responding with 502.
Also, we can make this configurable so that ATS can handle special scenarios.

Closing, since we have a PR already.

This is the PR for this issue: #1404


Error with libcurl

Hello everybody,
I currently trying to compile your example on my ubuntu maschine. I also installed libcurl by running the command "sudo apt-get install libcurl4-openssl-dev". Unfortunately I receive the following compilation errors:
ews.hpp:7196:78: error: macro "curl_easy_setopt" passed 4 arguments, but takes just 3
auto retcode = curl_easy_setopt(handle_.get(), option, arg1, arg2);
^
ews.hpp: In member function ‘void ews::internal::http_request::set_option(CURLoption, T1, T2)’:
ews.hpp:7205:46: error: cannot convert ‘CURLcode ()(void, CURLoption, ...)’ to ‘CURLcode’ for argument ‘2’ to ‘ews::internal::curl_error ews::internal::make_curl_error(const string&, CURLcode)’
retcode);
^
ews.hpp:7211:46: error: cannot convert ‘CURLcode ()(void, CURLoption, ...)’ to ‘CURLcode’ for argument ‘2’ to ‘ews::internal::curl_error ews::internal::make_curl_error(const string&, CURLcode)’
retcode);
Any ideas?

Hi. Can you run
$ g++ --version

and
$ dpkg -s libcurl4-openssl-dev|grep ^Version

and paste the output here?
Did you build the example with CMake?

G++ says:
g++ (Ubuntu 5.4.0-6ubuntu1~16.04.9) 5.4.0 20160609
Copyright (C) 2015 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

dpkg says:
Version: 7.47.0-1ubuntu2.7
I'm not using CMake. I just use a simple main.cpp in which I include the ews.hpp. I compile with the following command:
g++ --std=c++11 main.cpp -o main


coverage

Codecov Report

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

@@            Coverage Diff            @@
##             master      #35   +/-   ##
=========================================
  Coverage          ?   93.42%
=========================================
  Files             ?        5
  Lines             ?     1292
  Branches          ?        0
=========================================
  Hits              ?     1207
  Misses            ?       85
  Partials          ?        0

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 8081d63...af0d11b. Read the comment docs.


Fix addgrad for cleargrad

TODO: write test

This bug is reported on a blog post in Japanese http://hiho-developer.hatenablog.com/entry/20160922/1474541060.

I wrote test.
And, please merge #1778 before this PR.

I removed a print. LGTM except that point. I'll ask other members to review it.

Could you add test cases in which both clear_src_grad and clear_dst_grad is True?

Added a test case.

Thanks. Now LGTM.

Thank you!


'staticImplements' is not exported by<EMAIL_ADDRESS>

Getting
Rollup: Missing Export: node_modules/@transmute/ed25519-key-pair/dist/ed25519-key-pair.esm.js:3:9
           'staticImplements' is not exported by<EMAIL_ADDRESS>
When running
npm run build and npm run start

Thanks for bringing this our attention. I created a ticket to track this.

@Nicolascoding27 which directory are you running these commands from? The root directory, or a specific package?

Closing as stale, but I bet the issue remains, its likely something to do with the typescript version.
All these packages needs to be refreshed to remove tsdx.


security: make commitments to DA posted proofs and check them when data is retrieved

We should post a commitment to the proof posted to the DA solutions and check it matches on the AVS, so we don't have to trust the DA. This should work no matter where the data is stored

We will re implement DA solution later with the new design


Removed print in get_response

Removed print in get_response. Because it prints url for every request

@nagaraj-gohush thank you for getting in touch and the noticing it. Looks good to me 👍
@ilyazub what do you think?

Yes, let's remove the print.

This is working fine here but pypi.org also needs to be updated for pip installs. We have two users who have access to package on pypi: lf2225 and vikoky.
@ilyazub @hartator


when map is showing secrets instead of checkmarks, it doesnt show yellow room as completed

same issue with fairy and puzzle rooms, maybe when 0 secrets go back to checkmarks?


Error: [SSL: CERTIFICATE_VERIFY_FAILED]

It seems that python (both 2.7.9 and 3.4.3) has problems with ssl cert verification with many hosts. In my project I have to make requests to trakt.tv, which seems to have a certificate not present in the python database.
You can replicate the bug just making a request to it:
import urrlib
trakttv = urllib.request.urlopen('https://trakt.tv')

which will raise a urllib.error.URLError: <urlopen error [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:600)>
The same code with https://www.google.com works just fine. This is a big deal for flask-oauthlib, since it uses the python stdlib urllib/urllib2. Is there any workaround/fix?

SSL(3?) is becoming a big issue, i'm seeing this in API requests on api.github.com.
Since Debian Jessie (8.0) came out this weekend, i've migrated to python 3.4.1, and am not seeing any more issues. Tried requests.get with your url, works fine. So does the github api.  And indeed, like you i tried an https request into google and it was fine earlier too, with 2.7.9, while github's API broke.
I really don't know of a fix, and can't see how flask-oauthlib can solve this issue. It's a python community thing. The whole PY2 vs PY3 is a huge issue. For example, flask-socketio doesn't work on PY3, since it relies on gevent, which doesn't support PY3(!). This whole SSL problem quickly escalated for me too. Little relief on your end; am writing to get as many people on board, initiating issues on the various libraries to get things moving.
I'd tell you to try downgrading to 3.7.1 just to see if this resolves your issues. I know 2.7.9 has a bug working with SSL. But downgrading is a horrible solution to a problem.

Well, there is an alternative: it seems that the requests library solves this issue by using it's own cacert.pem certificate store.
Is that a viable option to rebuild this flask-oauthlib on top of  the requests library? If the answer is positive, I could start to work on this.

@youtux There is an experimental client in contrib.client https://github.com/lepture/flask-oauthlib/tree/master/flask_oauthlib/contrib/client which is using requests.

@youtux There is an experimental client in contrib.client https://github.com/lepture/flask-oauthlib/tree/master/flask_oauthlib/contrib/client which is using requests.

I have already seen that module, but I didn't find the OAuth2Provider class so I didn't bother too much. Now that I gave a better look I have found out that the equivalent for OAuth2Provider in the contrib.client package is the OAuth2Application!
Thank you for the tip.

I have the same problem (with OAuth1) and using the contrib client almost works.
The client relies on the OAuth1Session from requests-oauthlib which does a POST call in _fetch_token without the ability to pass any parameter such as the certificate to use for verification. (See here).
And while I did not  test it, it appears that the same problem is present with OAuth2Session (See here)
Thankfully, lukasa over at #python-requests suggested a nice work around to specify the certificate. Requests uses certifi which we can mock to return the path to the certificate you need. My code looks like this:
import sys

class FakeCertifi(object):
    def where(self):
        return '<path/to/your/cert.crt>'

sys.modules['certifi'] = FakeCertifi()

I will open an issue directly to requests-oauthlib and hopefully they will provide an option for the certificate's path. And then it would be great if Flask-OAuthlib could expose the option as well, at least in the contrib client.

@youtux Upgrading to Python 2.7.9 is an alternative way to resolve this issue. It has a new SSL module with SNI support.

@tonyseek I am already using Python 2.7.9 on Mac OS 10.10.3 (from homebrew)

It works on my local machine.
 Now it works for me too. Could it be that trakt.tv updated its certificate?
I suppose you can close this issue then.

Could it be that trakt.tv updated its certificate?

You are right. I misled myself before. It is no possible to meet SNI caused hostname issue with urllib/urllib2.

Python < 2.7.9 + urllib/urllib2: no SSL/TLS verifying.
Python < 2.7.9 + requests: SSL/TLS verifying without SNI support. (e.g. https://tonyseek.com could not be verified here)
Python 2.7.9 / Python 3.x + urllib/urllib2: SSL/TLS verifying with SNI support.
Python 2.7.9 / Python 3.x + requests: SSL/TLS verifying with SNI support.


What is happening with adding padding?

Reading through the code I see here: https://github.com/geaxgx/depthai_yunet/blob/fdc53e50dc46c491973daba6ab0b43de48ed024d/YuNetEdge.py#LL240C20-L240C20
        points = [
                [0, 0],
                [self.padded_size[0], 0],
                [self.padded_size[0], self.padded_size[1]],
                [0, self.padded_size[1]]]
        point2fList = []
        for p in points:
            pt = dai.Point2f()
            pt.x, pt.y = p[0], p[1]
            point2fList.append(pt)
        manip.initialConfig.setWarpTransformFourPoints(point2fList, False)

I am trying to understand why a point list is made twice. Also how does setWarTransformFourPoints add padding, doesn't it warp the image?

@geaxgx I figured this one out and thought maybe it would be helpful to let you know of DepthAIs  setResizeThumbnail which does the padding automatically. You can then resize the detections by how much each aspect was scaled.


Edit publication / posting guidance copy in bulk import flow to reflect situation, and shorten

Story
Edit publication / posting guidance copy in bulk import flow to reflect situation, and shorten.
Context

For certain import flows there will be fewer steps (for instance, "Complete" is left out)
For reviewers the text did not reflect the reviewing situation (reviewers will edit records themselves)
The text is quite long and could use structure

Suggestion
Publications

Next steps

After completing your publications below, click Publish to Biblio to make them visible to the public in the Academic Bibliography Biblio of UGent. The Biblio team will review your publication, and make slight corrections if applicable.

Click "Save as draft" to publish later.

Datasets

Next steps

After completing your dataset registration below, click Publish to Biblio to make them visible to the public in the Academic Bibliography Biblio of UGent. The data curator team will review your publication, and will contact you in case any changes are needed.

Click "Save as draft" to publish later.

Current situation
Publications

Datasets

Not so relevant anymore, import flow is annoying as is. Reworking.


Fix the baseline

I changed the baseline to:
baseline: spec

	<baseline>
	spec for: #common do: [
		spec
			package: 'Coypu'
			with: [ spec repository: 'github://lucretiomsp/Coypu' ];
			package: 'Phausto'
			with: [ spec repository: 'github://lucretiomsp/phausto' ];
			package: 'CoypuIDE' with: [ spec repository: 'github://lucretiomsp/CoypuIDE'] .

		"Internal dependencies"
		spec package: 'MasterLu' ]

Changes:

I updated the links to the form github://<user>/<repo>
I removed spec requires: 'Toplo' (it must be in CoypuIDE)
I changed the dependency of pharo-graphics/CoypuIDE to lucretiomsp/CoypuIDE because it needs the changes in this PR

This almost works: just Block is missing, but it is a dependency of Toplo that is a dependency of CoypuIDE.
But, if you already have Block loaded in the image, it should work.
Tested in Pharo 12

I am changing the baseline and check the behaviour on a fresh image


Roflcoptor should close connections if clients go away

Reproduce:

Run ricochet in oz in SGOS
Kill oz-daemon while sandbox up/app running
Start oz-daemon
Try to run ricochet again in oz in SGOS
TorHS collision, ricochet can't setup listener
Probably roflcoptor's fault: ephemeral hidden services go away when the client connection to the tor control port is closed.

so... if there were multiple applications that were relying on their own onion services via roflcoptor... and roflcoptor sees a connection close it should close it's control port destroying all the onion services?
i think the solution here is for roflcoptor to DEL_ONION the specific onion service corresponding to the application that closed it's connection to roflcoptor.

Tracking ADD_ONION and issuing DEL_ONION when the app->roflcopter connection is closed would work for this case, but it's going to be fragile and it will leave similar problems like GETINFO onions/current unsolved.
I think a much better solution would be to make one roflcopter->tor connection for each application->roflcopter connection, and close them at the same time. All of tor's per-connection behavior would then be automatically correct.


RoleAssignments GUID based on CC VM PrincipalID

not using the Resource Group ID means that we can redeploy in the same Resource Group.
The delete role script is no longer required hence the roleAssignmentCleanup.bicep. With this new method it's no longer possible to retrieve the GUID of the role once the CC VM is removed as we lose it's PrincipalID.

How does this affect people deploying the new bicep over an existing install to "update" it? Is that a supported use case?

as new roles IDs will be created this would allow updating an existing installation. to be confirmed

and confirm it failed, so need to find a better way

I successfully tested the following scenarios after my initial deployment:

Redeploying into the same RG after deleting all initial resources
Redeploying using the same RG name after deleting the initial RG

I had the same results as @dougclayton when trying to update attributes of my CC installation.
Should we consider keeping a legacy version of the delete_roles script for the users who will have clusters created prior to our next release? The new script won't properly delete their role assignments.


rails 4 support?

this gem is mentioned in the rails_12factor docs in the "rails 4 section" but init.rb doesn't seem to do anything with rails v4

Init.rb is executed only when using this as a plugin. Rails4 dropped the support for plugins in favor of gems and engines.
We have several internal apps using this gem on rails 4 which work properly. Are you seeing a specific issue when adding the gem to your dependencies?

thanks for the quick reply, the issue I had was that nothing was being logged to STDOUT. I has since moved to just setting logger to Logger.new(STDOUT) in my env so I am not sure this still happens or what might have caused it, I just happened to notice that line again today and thought I'd quickly check the code, which led me to submit the issue
Might have been related to setting the log_level to something other than the default or interaction with some other gem, so I think you can close this issue and I'll create a new one if I can replicate the problem and isolate it.
Thanks!

The most common problem is people putting this in their "production" group but running on a "staging" app environment.


Incorrect documentation: DatabaseChangeLog - IncludeAll - errorIfMissingOrEmpty

Description
The documentation here states that the errorIfMissingOrEmpty attribute defaults to false. However, the code here shows that the default is actually true.
Steps To Reproduce
List the steps to reproduce the behavior.
Create a changelog that includes some valid change sets and an includeAll attribute. For the includeAll attribute do not specify the errorIfMissingOrEmpty attribute and set the path attribute to a non-existent path.
Actual Behavior
The errorIfMissingOrEmpty default is true, rather than false and liquibase will fail to run any change sets.
Expected/Desired Behavior
Documented behavior says this should not fail. I believe the documentation should be change to reflect the default value is "true" and that the code should remain the same.

Hello! I tried to reproduce the behavior but in my case errorIfMissingOrEmpty is defaulted to false, can you send a changelog example? Thanks!

I can reproduce with the following setup and change log example. Liquibase errors for me when I leave out the errorIfMissingOrEmpty attribute (commented out in the example below). However, if I include errorIfMissingOrEmpty and set it to false (the supposed default), Liquibase runs just fine.
My structure (notice, no directory called non_existent):
.
├── changelog.yml
└── liquibase.properties

changelog.yml:
databaseChangeLog:
- changeSet:
    id: 1
    author: jlyle
    runOnChange: true
    runAlways: true
    preConditions:
        - onFail: MARK_RAN
        - onError: HALT
        - not:
            - tableExists:
                - tableName: tab_a
    changes:
        - createTable:
            tableName: tab_a
            columns:
                - column:
                    name: id
                    type: int
                    autoIncrement: true
                    constraints:
                        primaryKey: true
                        nullable: false
- includeAll:
    path: non_existent
    # errorIfMissingOrEmpty: false

Output if I don't include the errorIfMissingOrEmpty property:
####################################################
##   _     _             _ _                      ##
##  | |   (_)           (_) |                     ##
##  | |    _  __ _ _   _ _| |__   __ _ ___  ___   ##
##  | |   | |/ _` | | | | | '_ \ / _` / __|/ _ \  ##
##  | |___| | (_| | |_| | | |_) | (_| \__ \  __/  ##
##  \_____/_|\__, |\__,_|_|_.__/ \__,_|___/\___|  ##
##              | |                               ##
##              |_|                               ##
##                                                ##
##  Get documentation at docs.liquibase.com       ##
##  Get certified courses at learn.liquibase.com  ##
##  Free schema change activity reports at        ##
##      https://hub.liquibase.com                 ##
##                                                ##
####################################################
Starting Liquibase at 11:27:01 (version 4.18.0 #5864 built at 2022-12-02 18:02+0000)
Liquibase Version: 4.18.0
Liquibase Community 4.18.0 by Liquibase
[2022-12-13 11:27:04] INFO [liquibase.lockservice] Successfully acquired change log lock
[2022-12-13 11:27:05] INFO [liquibase.lockservice] Successfully released change log lock
[2022-12-13 11:27:05] WARNING [liquibase.configuration] Potentially ignored key(s) in file exists at path liquibase.properties
 - 'changeLogFile'
 - 'password'
 - 'url'
 - 'username'
[2022-12-13 11:27:05] SEVERE [liquibase.integration] Error parsing changelog.yml
  - Caused by: Could not find directory or directory was empty for includeAll 'non_existent'
liquibase.exception.CommandExecutionException: liquibase.exception.ChangeLogParseException: Error parsing changelog.yml
	at liquibase.command.CommandScope.execute(CommandScope.java:178)
	at liquibase.integration.commandline.Main.handleUpdateException(Main.java:2191)
	at liquibase.integration.commandline.Main.doMigration(Main.java:1835)
	at liquibase.integration.commandline.Main$1.lambda$run$0(Main.java:396)
	at liquibase.Scope.lambda$child$0(Scope.java:180)
	at liquibase.Scope.child(Scope.java:189)
	at liquibase.Scope.child(Scope.java:179)
	at liquibase.Scope.child(Scope.java:158)
	at liquibase.integration.commandline.Main$1.run(Main.java:395)
	at liquibase.integration.commandline.Main$1.run(Main.java:217)
	at liquibase.Scope.child(Scope.java:189)
	at liquibase.Scope.child(Scope.java:165)
	at liquibase.integration.commandline.Main.run(Main.java:217)
	at liquibase.command.AbstractCliWrapperCommandStep.run(AbstractCliWrapperCommandStep.java:33)
	at liquibase.command.CommandScope.execute(CommandScope.java:172)
	at liquibase.integration.commandline.CommandRunner.call(CommandRunner.java:55)
	at liquibase.integration.commandline.CommandRunner.call(CommandRunner.java:24)
	at picocli.CommandLine.executeUserObject(CommandLine.java:2041)
	at picocli.CommandLine.access$1500(CommandLine.java:148)
	at picocli.CommandLine$RunLast.executeUserObjectOfLastSubcommandWithSameParent(CommandLine.java:2461)
	at picocli.CommandLine$RunLast.handle(CommandLine.java:2453)
	at picocli.CommandLine$RunLast.handle(CommandLine.java:2415)
	at picocli.CommandLine$AbstractParseResultHandler.execute(CommandLine.java:2273)
	at picocli.CommandLine$RunLast.execute(CommandLine.java:2417)
	at picocli.CommandLine.execute(CommandLine.java:2170)
	at liquibase.integration.commandline.LiquibaseCommandLine.lambda$execute$1(LiquibaseCommandLine.java:352)
	at liquibase.Scope.child(Scope.java:189)
	at liquibase.Scope.child(Scope.java:165)
	at liquibase.integration.commandline.LiquibaseCommandLine.execute(LiquibaseCommandLine.java:317)
	at liquibase.integration.commandline.LiquibaseCommandLine.main(LiquibaseCommandLine.java:84)
	at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
	at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.base/java.lang.reflect.Method.invoke(Method.java:566)
	at liquibase.integration.commandline.LiquibaseLauncher.main(LiquibaseLauncher.java:107)
Caused by: liquibase.exception.ChangeLogParseException: Error parsing changelog.yml
	at liquibase.parser.core.yaml.YamlChangeLogParser.parse(YamlChangeLogParser.java:90)
	at liquibase.Liquibase.getDatabaseChangeLog(Liquibase.java:406)
	at liquibase.Liquibase.getDatabaseChangeLog(Liquibase.java:391)
	at liquibase.Liquibase.lambda$update$1(Liquibase.java:247)
	at liquibase.Scope.lambda$child$0(Scope.java:180)
	at liquibase.Scope.child(Scope.java:189)
	at liquibase.Scope.child(Scope.java:179)
	at liquibase.Scope.child(Scope.java:158)
	at liquibase.Liquibase.runInScope(Liquibase.java:2445)
	at liquibase.Liquibase.update(Liquibase.java:235)
	at liquibase.Liquibase.update(Liquibase.java:220)
	at liquibase.integration.commandline.Main.doMigration(Main.java:1833)
	... 32 more
Caused by: liquibase.exception.SetupException: Could not find directory or directory was empty for includeAll 'non_existent'
	at liquibase.changelog.DatabaseChangeLog.includeAll(DatabaseChangeLog.java:688)
	at liquibase.changelog.DatabaseChangeLog.handleChildNode(DatabaseChangeLog.java:490)
	at liquibase.changelog.DatabaseChangeLog.load(DatabaseChangeLog.java:376)
	at liquibase.parser.core.yaml.YamlChangeLogParser.parse(YamlChangeLogParser.java:84)
	... 43 more
Caused by: liquibase.exception.SetupException: Could not find directory or directory was empty for includeAll 'non_existent'
	at liquibase.changelog.DatabaseChangeLog.includeAll(DatabaseChangeLog.java:678)
	... 46 more

Unexpected error running Liquibase: Error parsing changelog.yml
  - Caused by: Could not find directory or directory was empty for includeAll 'non_existent'

liquibase.exception.CommandExecutionException: liquibase.exception.ChangeLogParseException: Error parsing changelog.yml
	at liquibase.command.CommandScope.execute(CommandScope.java:178)
	at liquibase.integration.commandline.Main.handleUpdateException(Main.java:2191)
	at liquibase.integration.commandline.Main.doMigration(Main.java:1835)
	at liquibase.integration.commandline.Main$1.lambda$run$0(Main.java:396)
	at liquibase.Scope.lambda$child$0(Scope.java:180)
	at liquibase.Scope.child(Scope.java:189)
	at liquibase.Scope.child(Scope.java:179)
	at liquibase.Scope.child(Scope.java:158)
	at liquibase.integration.commandline.Main$1.run(Main.java:395)
	at liquibase.integration.commandline.Main$1.run(Main.java:217)
	at liquibase.Scope.child(Scope.java:189)
	at liquibase.Scope.child(Scope.java:165)
	at liquibase.integration.commandline.Main.run(Main.java:217)
	at liquibase.command.AbstractCliWrapperCommandStep.run(AbstractCliWrapperCommandStep.java:33)
	at liquibase.command.CommandScope.execute(CommandScope.java:172)
	at liquibase.integration.commandline.CommandRunner.call(CommandRunner.java:55)
	at liquibase.integration.commandline.CommandRunner.call(CommandRunner.java:24)
	at picocli.CommandLine.executeUserObject(CommandLine.java:2041)
	at picocli.CommandLine.access$1500(CommandLine.java:148)
	at picocli.CommandLine$RunLast.executeUserObjectOfLastSubcommandWithSameParent(CommandLine.java:2461)
	at picocli.CommandLine$RunLast.handle(CommandLine.java:2453)
	at picocli.CommandLine$RunLast.handle(CommandLine.java:2415)
	at picocli.CommandLine$AbstractParseResultHandler.execute(CommandLine.java:2273)
	at picocli.CommandLine$RunLast.execute(CommandLine.java:2417)
	at picocli.CommandLine.execute(CommandLine.java:2170)
	at liquibase.integration.commandline.LiquibaseCommandLine.lambda$execute$1(LiquibaseCommandLine.java:352)
	at liquibase.Scope.child(Scope.java:189)
	at liquibase.Scope.child(Scope.java:165)
	at liquibase.integration.commandline.LiquibaseCommandLine.execute(LiquibaseCommandLine.java:317)
	at liquibase.integration.commandline.LiquibaseCommandLine.main(LiquibaseCommandLine.java:84)
	at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
	at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.base/java.lang.reflect.Method.invoke(Method.java:566)
	at liquibase.integration.commandline.LiquibaseLauncher.main(LiquibaseLauncher.java:107)
Caused by: liquibase.exception.ChangeLogParseException: Error parsing changelog.yml
	at liquibase.parser.core.yaml.YamlChangeLogParser.parse(YamlChangeLogParser.java:90)
	at liquibase.Liquibase.getDatabaseChangeLog(Liquibase.java:406)
	at liquibase.Liquibase.getDatabaseChangeLog(Liquibase.java:391)
	at liquibase.Liquibase.lambda$update$1(Liquibase.java:247)
	at liquibase.Scope.lambda$child$0(Scope.java:180)
	at liquibase.Scope.child(Scope.java:189)
	at liquibase.Scope.child(Scope.java:179)
	at liquibase.Scope.child(Scope.java:158)
	at liquibase.Liquibase.runInScope(Liquibase.java:2445)
	at liquibase.Liquibase.update(Liquibase.java:235)
	at liquibase.Liquibase.update(Liquibase.java:220)
	at liquibase.integration.commandline.Main.doMigration(Main.java:1833)
	... 32 more
Caused by: liquibase.exception.SetupException: Could not find directory or directory was empty for includeAll 'non_existent'
	at liquibase.changelog.DatabaseChangeLog.includeAll(DatabaseChangeLog.java:688)
	at liquibase.changelog.DatabaseChangeLog.handleChildNode(DatabaseChangeLog.java:490)
	at liquibase.changelog.DatabaseChangeLog.load(DatabaseChangeLog.java:376)
	at liquibase.parser.core.yaml.YamlChangeLogParser.parse(YamlChangeLogParser.java:84)
	... 43 more
Caused by: liquibase.exception.SetupException: Could not find directory or directory was empty for includeAll 'non_existent'
	at liquibase.changelog.DatabaseChangeLog.includeAll(DatabaseChangeLog.java:678)
	... 46 more

Output if I do include the errorIfMissingOrEmpty property set to false:
####################################################
##   _     _             _ _                      ##
##  | |   (_)           (_) |                     ##
##  | |    _  __ _ _   _ _| |__   __ _ ___  ___   ##
##  | |   | |/ _` | | | | | '_ \ / _` / __|/ _ \  ##
##  | |___| | (_| | |_| | | |_) | (_| \__ \  __/  ##
##  \_____/_|\__, |\__,_|_|_.__/ \__,_|___/\___|  ##
##              | |                               ##
##              |_|                               ##
##                                                ##
##  Get documentation at docs.liquibase.com       ##
##  Get certified courses at learn.liquibase.com  ##
##  Free schema change activity reports at        ##
##      https://hub.liquibase.com                 ##
##                                                ##
####################################################
Starting Liquibase at 11:18:23 (version 4.18.0 #5864 built at 2022-12-02 18:02+0000)
Liquibase Version: 4.18.0
Liquibase Community 4.18.0 by Liquibase
[2022-12-13 11:18:26] INFO [liquibase.lockservice] Successfully acquired change log lock
[2022-12-13 11:18:31] INFO [liquibase.changelog] Reading from LB.DATABASECHANGELOG
Running Changeset: changelog.yml::1::jlyle
[2022-12-13 11:18:32] INFO [liquibase.changelog] Marking ChangeSet: "changelog.yml::1::jlyle" as ran despite precondition failure due to onFail='MARK_RAN':
          changelog.yml : Not precondition failed

[2022-12-13 11:18:33] INFO [liquibase.lockservice] Successfully released change log lock
Liquibase command 'update' was executed successfully.

the documentation has been fixed! Thanks again


Download Video/Image Progress

I read in the documentation you provided that a future effort will be to add downloading of the images/video. Have you made any progress on this or do you have any recommended hacks that might work in the meantime? Everything in your library works great, I just cannot get the images from the gopro hero4 I am connected with onto my computer to process.

You should be able to get snapshots of the live camera feed, but I have not worked on getting the existing images and videos off of the SD card.
To explore this more yourself: The GoPro opens up a standard file server when connected via wifi. You'd simply need to use something (Python?) to read the list of files on the file server and copy over a file (via HTTP) to a local folder.

@joshvillbrandt putting a progress bar does not seem to be a big work
We can use progressbar library for this and here is a sample code for showing a simple progress bar
import time
import progressbar

bar = progressbar.ProgressBar(redirect_stdout=True)
for i in range(100):
    print 'Some text', i
    time.sleep(0.1)
    bar.update(i)

Hope this helps. :smile_cat: :smile_cat:

also using http://<IP_ADDRESS>/gp/gpMediaList it shows a JSON list of photos and videos.

Hi guys! Do you know which URL (the syntax) would lead to the download of a file? I'm actually trying to understand how I could download pics from my gopro ;)

@arthurpattee you can't download files with this library, but you can use gopro.image() to save a screencap of the stream. Not trying to take away the spotlight but with my library gopro_py_api you can use .dl_last() to downlast the last media taken.

@KonraIT Hi there! Juste sent you a mail about your API ;)

@arthurpattee replied.


Translate the code from C# to C++

500 RUB reward can be claimed by anyone who completes this task.

C# to C++ translation example generated with help of GitHub Copilot
#include <iostream>

namespace Platform::IO
{
    class ConsoleHelpers
    {
        public: static void PressAnyKeyToContinue()
        {
            std::cout << "Press any key to continue..." << std::endl;
            std::cin.get();
        }

        // Output to console on in debug mode
        public: static void Debug(auto&& message)
        {
#ifndef NDEBUG
            std::cout << message << std::endl;
#endif
        }
    };
}

int main(int argc, char *argv[])
{
    // Output to console
    Platform::IO::ConsoleHelpers::Debug("Hello World!");
}

https://github.com/linksplatform/IO/blob/87317dd0ed6dbb8d52ea9da5b35c2e4bd09106f3/cpp/Platform.IO/ConsoleHelpers.h#L5

Hey, could you give more information about this issue?
I might wanna give it a try!

Hey, could you give more information about this issue? I might wanna give it a try!

The idea is to make translation of csharp folder to cpp folder. You can notice that cpp folder already contains basic translation generated by our translator.


API documentation is out of date

http://googlechrome.github.io/chrome-platform-analytics/
We have a new docs generator so we should be able to wire that up without too much work and make it part of the MOE push process.

WIP?

Tyler. Should we close this as obsolete?

I'm not actively working on this but it would be a good thing to do. It shouldn't be hard, just need to find the time.

Does anyone have a link to the current documentation?


Initial release

[x] Get simple workflow working
[x] Test new install
[x] Rename to starsim
[x] Set up basic docs (pkgdown)
[x] Set up website hosting

Done


adding pub fn len in List

Upstream: #609

close #536
Description
I added the methods for List.
A structure with the name "list" can be length-checked in many libraries, so I added the methods in this library too.
Testing guidelines

I added the tests.
Checklist

[x] I have read the contributing guidelines.
[x] I have added relevant tests.
[ ] I have documented all new additions.

Thank you in advance.

Rebased against main. LGTM

Fixed clippy issues.

conventional commit


Add WatchResults endpoint

This endpoint allows a user to watch a list of results and be notified when there is any change.
The user sends the list of ids they want to watch.
The submitter will then send the statuses for all requested ids immediately and keep the stream open.
The submitter will send updates to the client via the opened stream.
Any reply can be implicitely chunked if there are too many event to report at the same time (or for the first reply).
It is possible to filter out specific statuses from events with options

Implements https://github.com/aneoconsulting/ArmoniK/issues/333

WaitForAvailability should be removed.
It can very easily be implemented in API or in samples.

Agreed.

I am also wondering whether it would not be a good idea to have a stream for the watchResultrequest. It would allow either to chunk the list of result wanted or to add other result along with the submition of new tasks

Could be nice indeed. I will try something.


ESP: ability to see damaged structures

Hi :)
it would be nice to be able to see the damaged structures to know which ones to repair.
or increase the radius of effects of the repair hammer.

Added by @WoodenSquid


Changed system_time into ROS_time

Changed system_time into ROS_time to fix different time source comparison bug when running on use_sim_time

@Chrislai502 is this PR still something you want to merge?

Yes
On Tue, Nov 7, 2023 at 12:58 PM Siddharth Saha @.***>
wrote:

@Chrislai502 https://github.com/Chrislai502 is this PR still something
you want to merge?
—
Reply to this email directly, view it on GitHub
https://github.com/airacingtech/autoware.universe/pull/2#issuecomment-1800107211,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AP6KLPI7TZL3SBBRSJLR6M3YDKOINAVCNFSM6AAAAAA245AGKCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMBQGEYDOMRRGE
.
You are receiving this because you were mentioned.Message ID:
@.***>

Cherry picked in art-iron. Closing this since it also contains the polygon remover for some reason


ReSub v2 setState not working?

Hey you all - I'm testing out the 2.0.0-rc.1 and vs 1.2.2 I have a component that fails to setState correctly.

  private _onNextPage = () => {
    console.log(
      'TIPI::_onNextPage - was on page ' + this.state.pageIndex + ' (max is ' + this.MAX_PAGE + ')'
    );
   let nextIndex = this.state.pageIndex + 1;
    this.setState({ pageIndex: nextIndex >= this.MAX_PAGE ? this.MAX_PAGE : nextIndex });
    console.log('TIPI::_onNextPage - will be on page ' + this.state.pageIndex);
  };

It's a simple pager, and I get 'will be on page 0' (the initial state) every click with 2.0.0-rc.1 but it increments nicely with 1.2.2.
That's a vague report in and of itself but it is a clear regression with this code between those two versions.
I'm trying to get a repro together but in the meantime I also see this on an npm test execution
mike@isabela:~/work/react-random/resub (master) % npm test

><EMAIL_ADDRESS>test /home/mike/work/react-random/resub
> run-s clean:* karma:single-run

><EMAIL_ADDRESS>clean:dist /home/mike/work/react-random/resub
> rimraf dist*

><EMAIL_ADDRESS>karma:single-run /home/mike/work/react-random/resub
> karma start --singleRun

Starting type checking service...
Using 1 worker with 2048MB memory limit
Type checking in progress...
ℹ ｢wdm｣: Compiled successfully.
ℹ ｢wdm｣: Compiling...
ERROR in /home/mike/work/react-random/resub/test/AutoSubscribe.spec.tsx(128,7):
TS2417: Class static side 'typeof OverriddenComponent' incorrectly extends base class static side 'typeof SimpleComponent'.
  Types of property 'getDerivedStateFromProps' are incompatible.
    Type 'GetDerivedStateFromProps<SimpleProps, SimpleState>' is not assignable to type 'GetDerivedStateFromProps<unknown, unknown>'.
      Types of parameters 'nextProps' and 'nextProps' are incompatible.
        Property 'ids' is missing in type 'Readonly<unknown>' but required in type 'Readonly<SimpleProps>'.
Version: typescript 3.5.3
Time: 2315ms
ℹ ｢wdm｣: Compiled successfully.

Any chance that pageIndex is set inside _buildState?

Just whipped up an example with 2.0.0-rc.1 and things work as expected - here's a snippet
If you could provide any more context, that would be helpful to investigate

Here's a reproduction - I didn't mean to leave it vague but you are faster to respond than I can code tiny repro apps :-)
Do this:
npx react-native init ReSubStateTest
cd ReSubStateTest
npm add<EMAIL_ADDRESS>
Replace your entire App.js with this:
import React from 'react';
import { View, Button, Text } from 'react-native';
import { ComponentBase } from 'resub';

interface CounterProps {}

interface CounterState {
  counter: number;
}

class Counter extends ComponentBase<CounterProps, CounterState> {

  _buildState(props, state) {
    if (!this.state || this.state.counter == undefined) {
      console.log('_buildState - no initial state, initializing to 0');
      return { counter: 0 };
    } else {
      console.log('_buildState - counter already set to ' + this.state.counter);
      return { counter: this.state.counter };
    }
  }

  _handleClick = () => {
    console.log('_handleClick - incrementing from ' + this.state.counter + ' to ' + (this.state.counter + 1));
    this.setState({ counter: this.state.counter + 1 });
    console.log('_handleClick - counter is now ' + this.state.counter);
  }

  render() {
    return (
      <View>
        <Text>Counter is { this.state.counter }</Text>
        <Button title="Increment" onPress={this._handleClick}/>
      </View>
    );
  }
}

const App: () => React$Node = () => {
  return (
    <>
      <Counter/>
    </>
  );
};

export default App;

Run it? (start your android emulator and npm start + npm run android or the equivalent for ios)
I get this:
 LOG  _buildState - no initial state, initializing to 0
 LOG  _handleClick - incrementing from 0 to 1
 LOG  _handleClick - counter is now 0
 LOG  _buildState - counter already set to 0
 LOG  _handleClick - incrementing from 0 to 1
 LOG  _handleClick - counter is now 0
 LOG  _buildState - counter already set to 0
 LOG  _handleClick - incrementing from 0 to 1
 LOG  _handleClick - counter is now 0
 LOG  _buildState - counter already set to 0
 LOG  _handleClick - incrementing from 0 to 1
 LOG  _handleClick - counter is now 0
 LOG  _buildState - counter already set to 0

:thinking:  I am usually doing something wrong. But I can't see it. And it works in this style with<EMAIL_ADDRESS> LOG  _buildState - no initial state, initializing to 0
 WARN  Warning: componentWillMount has been renamed, and is not recommended for use. See https://fb.me/react-async-component-lifecycle-hooks for details.

* Move code with side effects to componentDidMount, and set initial state in the constructor.
* Rename componentWillMount to UNSAFE_componentWillMount to suppress this warning in non-strict mode. In React 17.x, only the UNSAFE_ name will work. To rename all deprecated lifecycles to their new names, you can run `npx react-codemod rename-unsafe-lifecycles` in your project source folder.

Please update the following components: Counter
 WARN  Warning: componentWillReceiveProps has been renamed, and is not recommended for use. See https://fb.me/react-async-component-lifecycle-hooks for details.

* Move data fetching code or side effects to componentDidUpdate.
* If you're updating state whenever props change, refactor your code to use memoization techniques or move it to static getDerivedStateFromProps. Learn more at: https://fb.me/react-derived-state
* Rename componentWillReceiveProps to UNSAFE_componentWillReceiveProps to suppress this warning in non-strict mode. In React 17.x, only the UNSAFE_ name will work. To rename all deprecated lifecycles to their new names, you can run `npx react-codemod rename-unsafe-lifecycles` in your project source folder.

Please update the following components: Counter
 WARN  Warning: componentWillUpdate has been renamed, and is not recommended for use. See https://fb.me/react-async-component-lifecycle-hooks for details.

* Move data fetching code or side effects to componentDidUpdate.
* Rename componentWillUpdate to UNSAFE_componentWillUpdate to suppress this warning in non-strict mode. In React 17.x, only the UNSAFE_ name will work. To rename all deprecated lifecycles to their new names, you can run `npx react-codemod rename-unsafe-lifecycles` in your project source folder.

Please update the following components: Counter
 LOG  _handleClick - incrementing from 0 to 1
 LOG  _handleClick - counter is now 0
 LOG  _handleClick - incrementing from 1 to 2
 LOG  _handleClick - counter is now 1
 LOG  _handleClick - incrementing from 2 to 3
 LOG  _handleClick - counter is now 2

(although my log messages are already suspicious there)
It's late here so I'll be AFK till the morning, but I appreciate the look already.
Hopefully it's something obvious, I was enjoying getting rid of the lifecycle method deprecations, and was hoping I'd test the RC for you without stumbling on anything :-)

I see what's going on here - setState triggers a getDerivedStateFromProps, which runs _buildState. I think _buildState is going to need to have prevState passed to it - this.state probably can't be trusted in _buildState

The short-term mitigation is to remove setting current state back to state - but that's not a true "fix" - I'm investigating now but I think it'll involve passing state into buildState and having to use that

  _buildState(props, state) {
    if (!this.state || this.state.counter == undefined) {
      console.log('_buildState - no initial state, initializing to 0');
      return { counter: 0 };
    }
  return undefined;
  }

Didn't mean for this to auto-close - publishing rc.2, lemme know if that helps you

Good morning :-), I actually didn't see you'd published rc.2 until after I tested but I just added berickson1/resub#incomingState and built it in node_modules to test - same effect.
It does work with this code now as _buildState:
  _buildState(props, initial, state) {
    if (!state || state.counter == undefined) {
      console.log('_buildState - no initial state, initializing to 0');
      return { counter: 0 };
    } else {
      console.log('_buildState - counter already set to ' + state.counter);
      return { counter: state.counter };
    }
  }

:clap: :clap:
(basically doing what the new README says - adding a state variable as a third variable, and referencing that local var instead of this.state)
I'm still a little confused on why referencing state immediately after setting it returns a stale value. That is unexpected and I may have just never noticed it before, but it is not a regression from v1->v2
So I have three side notes for this issue:

npm test produces an ERROR but does not fail?
the README might get a migration guide linked around from other places with a fuller description
using state immediately after setting it is odd?

But clearly the actual issue is resolved, which is great. That was my only issue with rc.1 so I believe I can rely on it in my project. I'm not using it in a very complicated way, but it is fundamental to the project, so hopefully that helps as a test.
As a final side note I really appreciate how the team ships source ready to build with reactxp releases so that (if needed) you can use something like patch-package to patch the .ts files then as postinstall cd into node_modules && install && build. I may not have started contributing personally if that wasn't the case. I liked the style so much I copied it and made it a requirement when we migrated react-native-device-info to typescript - I made sure people had the source and a working build setup in their normal project install so I could capture what I think of as "drive by contributions" from library users (which usually start as node_modules hacks I think). I notice that resub doesn't do this but it seems close, it's just missing the .eslintrc and a couple other things and it would build.

Sorry, I'm full of side-notes. I just remembered that a separate breaking change it that I had a pattern (valid or not) in my constructors where I would:
this.state = {
  somevar: "initial state",
};

...initializing to the empty state during construction. Is that useful or is it an anti-pattern? Side-stepping that debate, it was not an error in v1, but in v2 it triggered https://github.com/microsoft/ReSub/blob/master/src/ComponentBase.ts#L78
So that was a breaking change for me. Easy to fix, but if there is a migration guide it might be an entry

Hey,
at first, you can't rely on a state update after calling setState. SetState is called asynchrounously.
Have a look here.
Secondly, with ReSub you should initialize your state inside the _buildState method, if 'initialBuild' is true. That is beacuse of ReSub setting some internal values to the State in the constructor of ComponentBase.
And yes, that could be stated in the migration guide, but in my opinion, the documentation stated that already clearly before: During initial component construction, initialBuild will be true. This is where you should set all initial state for your component..
So usage of this.state = .. worked before, but was not the way to use it (as i interpret the docs).

@BiggA94 thanks for that link on setState - I'm still getting up to speed on all things React so that is useful reading.
No disagreement that I should have used initialBuild - I conveniently side-stepped the "debate" (knowing it was the wrong style) in my comment, I just wanted to point out that it was a breaking behavior change in the context of a possible migration guide. The goal would be to reduce future support load for maintainers - any breaking change inevitably turns in to 2-3 issues in my experience if not documented explicitly as such

@mikehardy The more I think about your example, the more I think, the usage of buildState is not correct here.
You don't need to return the whole state in the _buildState, only the objects that should be updated.
In your case, you update your state with the call of the setState method.
If you want to log the counter, you should use the callback of the setState function.
Also I think I found a 'Problem' with the concept of v2..
React seems to not set the State before calling getDerivedStateFromProps.
So this leads to the breaking change, that you can't rely on this.state inside the buildState function.
Using the state, that is now provided via properties seems to fix this.
I think I will further investigate this, if i have some spare time..
@berickson1
One Problem with your update is, that you use Readonly<S> | {}.
If one is using an Interface, you can't check, if the state is of type S (only by checking every property).
I think it would be best to use Readonly<S> | undefined here.
The state is undefined on initialBuild, after that, it is of Type S.
This would improve usage greatly.

@BiggA94

@mikehardy The more I think about your example, the more I think, the usage of buildState is not correct here.
You don't need to return the whole state in the _buildState, only the objects that should be updated.
In your case, you update your state with the call of the setState method.

This was critical to untangling my work project, thank you.

Also I think I found a 'Problem' with the concept of v2..
React seems to not set the State before calling getDerivedStateFromProps.
So this leads to the breaking change, that you can't rely on this.state inside the buildState function.

This is where I was tangled. I found I was not even able to rely on the passed in state. But it was true (in my project) that there was separation between the items in state I was managing in the component with UI handlers and the items I that were in an external Store. So by returning Partial State objects from _buildState that were only concerned with the external Store, everything is working
in v1's method/render lifecycle, _buildState had access to an updated / correct state so it wasn't a concern.

@mikehardy I think I have to dig deeper into the react lifecycle to find the correct solution to this..
Seems, that not all is documented.. :D
Could you provide a repro, or show the code, where you see, that you couldn't rely on the new state argument?

Not quickly, but I think the heart of a minimal repro will be do have the setState call in the handler be asynchronous.
The setup on this screen is with react-navigation
I have a focus listener that calls an async method
That async method does a setState
When _buildState is called as a result of the setState in the async from the focusListener, the state provided as 3rd parameter in 2.0.0-rc.2 does not have the value I just set into it
It may be possible to mock this up with timers etc (that's how I'd do it) but unfortunately I'm out of time to play with it for a while

Just to clarify a little bit on expected internal behaviour or ReSub

Setting the entire State object in _buildState is somewhat of an anti-pattern. Ideally _buildState would only query your resub stores and grab state relating to that (except on initial build).  Anti-pattern or not, we should still provide consumers as way to to this (the new incomingState argument on _buildState should fulfill this)
Calling setState triggers a getStateFromProps call before state is applied - which calls _buildState. This is why you were seeing an 'old' value in this.state while inside _buildState. We don't have any tests to cover this case - but we should add some to help prevent future regressions

As for Mike's last question - I tried doing a setTimeout before calling setState and couldn't repro :(
I can play around a little more this evening to see if I can find a repro

echoing that, my main takeaway is that I was dealing with state terribly (in my subjective opinion), so in that way the v1->v2 behavior change has been quite illuminating and resulted on a big project improvement.
Also I took a quick stab at a reproduction starting with the very code I saw it in and I must retract my assertion that the new 3rd argument was not updated. I can no longer reproduce it. I assume it was still a reference to this.state. vs state..
So I return to my previous assertion that with 2.0.0-rc.2 (and my state-handling reorganization) my project is working fine.

As part of this v2 moveover, we're continuing to try to simplify the happy path, and make it harder to hose yourself.  So it's still really good for us to flesh out cases like this, and see how we can add more exceptions/checking to help people down the happy path.


Broken, after new directory created

After operations with created folder on remote host (SFTP), plugin seems broken, "listing {dirname}" at bottom all time.
http://puu.sh/n5tS6/4f5ed2f2bc.png
Endless.
Only disconnect-connect work, but when try some operation with this folder, "listing" again appear and hold.
Windows 10, plugin version 0.7.19, atom 1.5.2

I have the exact same problem.
My config is also Windows 10, same plugin version (0.7.19), and atom 1.5.3

Same problem on my linux system with same remote dir. So, i guess,
something badly broken.
14 Фев 2016 г. 21:06 пользователь "LordAvenfold"<EMAIL_ADDRESS>написал:

I have the exact same problem.
My config is also Windows 10, same plugin version (0.7.19), and atom 1.5.3
—
Reply to this email directly or view it on GitHub
https://github.com/mgrenier/remote-ftp/issues/290#issuecomment-183941128
.

Same issue. Probably related with #292 as well.


Inifinite text replication after dragging selection (CodeMirror)

In demo app, if you select CodeMirror editor, then select some text and try to drag it into another place, it gets automatically replicated until the browser crashes.
I'd like to try and fix that, but do you have any suggestions where to start looking for it?

I also have an issue regarding to sudden endless replication of text during writing in two different browsers. browser is crashing. don't know really where to look at the moment.

Is this still an issue?


Added UnitTests for WorldAnchor.

I have added the promised UnitTests.
(#1074)

 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.:x: eluchsinger sign nowYou have signed the CLA already but the status is still pending? Let us recheck it.

I was not able to reproduce that error. What could be the cause my tests run through? It is hard for me to know if I am doing it right like this.
I have added a Setup method to clear the scene and add a WorldAnchorManager to the scene before the tests run. Can you tell me if it fixed your problems?

They try the test on a clean scene.  If the test requires a game object setup, then the test initialisation should add it to the scene.   The other tests seem to do this as I tested with a blank scene.
Hope that helps.

@eluchsinger I think it's fine like this. I'm undecided whether to move the logic into a separate utility class or not. Maybe someone else has some input on that.

Ideally we should not have duplicated cod for any reason.
If the code is used by both test and apps, it should be in or as an extension of the main class.
If it is only used by tests, then it should only exist in the tests project so that it does not contaminate the main code stream.
So does this extension function have any use outside of tests?

I'll give this another test now if you think it's ready @eluchsinger ?

@DDReaper yes, I thought it had to be duplicated, because that was the only way of testing it without initializing the WorldAnchorManager. Zod said in #1074 that I should extract the method's logic because it won't run in the editor, and I somehow misinterpreted it as to put it directly into the tests. I fixed that now and it shouldn't need to initialize a WorldAnchorManager object.
I couldn't reproduce your test failure, so I am not 100% sure that this time the test won't fail, but I believe the code is now at the right place. Please re-run the tests, I think it should work now.

@eluchsinger AttachAnchor will just return null in the editor. That's what I meant with that it won't run in the editor. You had to extract the logic because it was in the #else block of this compiler directive.
https://github.com/Microsoft/MixedRealityToolkit-Unity/blob/bf98b15bd7ce6154e9366bf5368a2bf09888dbd8/Assets/HoloToolkit/Utilities/Scripts/WorldAnchorManager.cs#L183-L188

Was going to ask for another test to ensure thenegative case would be true but then noticed a possible error.  If you call this function with a new proposed name, it is NOT stored against the anchor, only returned.
Is that the intended behaviour
        public static string GenerateAnchorName(GameObject gameObjectToAnchor, string proposedAnchorname = null)
        {
            return string.IsNullOrEmpty(proposedAnchorname) ? gameObjectToAnchor.name : proposedAnchorname;
        }

so calling this function currently :
var name = GenerateAnchorName(anchor,"newname")

is exactly the same as:
var name = newname

It doesn't update the name of the anchor itself??

Ignore my last comment.  I'm now ok with this change.


Add a hotkey for shop

Right now, you can only open the shop by typing out !shop which can be tedious at times
A hotkey like O or U can be really helpful in such cases

Hello, could you assign me to this issue?

Oh, also wanted to ask if there was a way to test the module without having an account with 1000 cheese. I shouldn't necessarily need to test it, but I want to make sure it works before submitting the pull request.

The gathered cheese to load lua was reduced upto 100 (IIRC). So accounts with that amount of gathered cheese will work. Also I'll check the PR soon. Thanks for the contribution! :heart:


Rancher is denying namespace creation: error creating namespace: admission webhook "rancher.cattle.io.namespaces.create-non-kubesystem" denied the request: Unauthorized

I tried to install Korifi on a RKE2 cluster.
I use standard settings/options and didn't restrict something, but rancher denies Korifi to create namespaces when creating an organization (CfOrg resource).
error creating namespace: admission webhook "rancher.cattle.io.namespaces.create-non-kubesystem" denied the request: Unauthorized
How can I configure Rancher to allow namespace creation for Korifi? Where can I get more information about why Rancher denies that?
Related Issue:

https://github.com/cloudfoundry/korifi/issues/3545

Problem solved. The role bindings of Korifi need the updatepsa permission.
Would be great if the error message contains such a hint in the future.


Hello. How to add SSL, https to magic mirror /js/server.js nodejs. Thank you

Hello. How to add SSL, https to magic mirror /js/server.js nodejs. Thank you

see
https://stackoverflow.com/questions/11744975/enabling-https-on-express-js

See answer sdetweil. Closing.


Minor improvements in runners + Fix type of YII_DEBUG + Add entry points to psalm

Q
A

Is bugfix?
✔

New feature?
❌

Breaks BC?
❌

Fixed issues
-

👍


Spamming with lock[bot]

What are you guys doing?
I am receiving tonns of notification emails about issues closing down due to noone writing in them.
They are all like this:
lock[bot]<EMAIL_ADDRESS>| lock[bot]<EMAIL_ADDRESS>| 13:46 (6 minutes ago)
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

This would go on for some time now for old issues (See https://github.com/prometheus/prometheus/pull/5392). Best you can do is add a filter to automatically archive emails from lock[bot].
Closing this as this is not an issue with Prometheus itself.

Well it's still a huge pain and I'm also being spammed with lockbot notifications and I expect it to be the same for others following the project. I think the best thing to do would be for someone to go and manually close all the issues that are older than 180days.
I'll do it tomorrow unless someone else volunteers.

It was not like that before. I was receiving emails only about on-going discussions and updates. But this - this is pure spam.
I agree that it might not be related to Prometheus and instead something the Github has changed.

@gouthamve Yes, I agree, I don't like the spam either. The bot is actually locking old closed issues, and not exactly closing open issues as far as I can see. I don't think you want to go over ~2k issues (which is just of prometheus/prometheus).
@SuperQ  is it possible to reduce the frequency? Like some X number of issues to lock per day. That might reduce the effort to browse through relevant mails and all the closed issues will be locked eventually.

@SuperQ is it possible to reduce the frequency? Like some X number of issues to lock per day. That might reduce the effort to browse through relevant mails and all the closed issues will be locked eventually.

Or increase the frequency so that all issues are done at once and we don't have to delete mail dail (or set up extra filter rules). I am highly annoyed by these mails as well (although I understand the motivation for using the app).

I added a gmail filter for the closed emails and called it a day.


Ability to "pad" host serial numbers for creation of new hosts.

When adding new hosts to rancher, enable the ability to pad the serialnumber to x digits
e.g. rather than
aws-host1
...
aws-host9
I want the result of
aws-host001
...
aws-host009
This helps with inventorying and sorting.

The UI does exactly that  if you enter aws-host001 as the name.  And next time you can continue with aws-host010.


[SPARK-44353][CONNECT][SQL] Remove StructType.toAttributes

What changes were proposed in this pull request?
This PR removes StructType.toAttribute. It is being replace by DataTypeUtils.toAttribute(..).
Why are the changes needed?
We want to move the DataType hierarchy into sql/api. We need to remove any catalyst specific API.
Does this PR introduce any user-facing change?
No.
How was this patch tested?
Existing tests.

cc @amaliujia

Merging. Failure is related to ongoing buf work.

It seems remove StructType.toAttributes will lead to break change.
Users always use this method.


BatchDataLoader within nested resolver does not batch requests from multiple nodes correctly

Is there an existing issue for this?

[X] I have searched the existing issues

Product
Green Donut
Describe the bug
I am not sure if it is an issue with my implementation or whether there is a bug.
Given the following query:
{
  rooms(searchCriteria: {campusCode: "V", roomTypeId: 1}, first: 15)
  {
    pageInfo {
      startCursor,
      endCursor,
      hasNextPage,
      hasPreviousPage
    }
    nodes
    {
      roomCode,
      bookings
      {
        startTime,
        endTime,
        source
      }
    }
  }
}

In the Query-class I have the following resolver to get the rooms:
public class Query
{
    [UsePaging]
    public async Task<IEnumerable<api.SchemaTypes.Room>> GetRooms(RoomsByArgsDataLoader RoomsDataLoader,
        [Service] api.SchemaTypes.Room.ReservationDescriptionsConfiguration ReservationDescriptionsConfiguration,
        List<RoomsDataLoaderFetchingArgs> searchCriteria
        )
    {
        IReadOnlyList<api.DataLoaders.Roomsdb.Room[]> allRoomResults = await RoomsDataLoader.LoadAsync(searchCriteria);
        List<api.SchemaTypes.Room> results = new List<api.SchemaTypes.Room>();
        foreach (api.DataLoaders.Roomsdb.Room[] roomResults in allRoomResults)
        {
            foreach (api.DataLoaders.Roomsdb.Room room in roomResults)
            {
                results.Add(new api.SchemaTypes.Room(room, ReservationDescriptionsConfiguration));
            }
        }
        return results;
    }

This is the Room-class with the Bookings-resolver to fetch the bookings:
public class ReservationDescriptionsConfiguration
{
    public required List<int> ReservationObjectRelationTypeIds { get; set; } = new List<int>();
    public required List<int> DescriptiondefiningObjectRelationFieldIds { get; set; } = new List<int>();
    public required int RoomNameFieldId { get; set; }
}

private readonly string _roomcode;
private readonly ReservationDescriptionsConfiguration _ReservationDescriptionsConfiguration;

public Room(api.DataLoaders.Roomsdb.Room room, ReservationDescriptionsConfiguration ReservationDescriptionsConfiguration)
{
    _roomcode = room.RoomCode;
    _roomsdbroom = room;
    _ReservationDescriptionsConfiguration = ReservationDescriptionsConfiguration;
}
private DataLoaders.Roomsdb.Room _roomsdbroom;
public int? Id() => _roomsdbroom.Id;
public string RoomCode() => _roomsdbroom.RoomCode ?? _roomcode;
public string? RoomName() => _roomsdbroom.RoomName;
public int? LocationId() => _roomsdbroom.LocationId;
public int? RoomTypeId() => _roomsdbroom.RoomTypeId;
public string? CampusAbbreviation() => _roomsdbroom.Location?.Abbreviation;
public string? Campus() => _roomsdbroom.Location?.Name;

public async Task<List<UserCalendarEvent>> Bookings(DataLoaders.AzureAd.UsersByDisplayNameDataLoader aadusersbydisplaynamedataloader, DataLoaders.AzureAd.UserCalendarEventsDataLoader aadusercalendareventsdataloader, DataLoaders.bookingsystem.bookingsystemRoomByCampusRoomCodeDataLoader bookingsystemRoomByCampusRoomCodeDataLoader, DataLoaders.bookingsystem.bookingsystemReservationsByObjectDataLoader bookingsystemReservationsByObjectDataLoader, bookingsystemObjectsByIdsDataLoader bookingsystemObjectByIdsDataLoader)
{
    List<UserCalendarEvent> bookings = new List<UserCalendarEvent>();
    IReadOnlyList<Microsoft.Graph.Models.User> roomaadusers = await _aadusersbydisplaynamedataloader.LoadAsync($"{((RoomTypeId()) == 7 ? "Meetingroom" : "Resource")} {CampusAbbreviation()} {RoomCode()}");
    List<DataLoaders.bookingsystem.InternalTypes.ObjectDto> bookingsystemrooms = await _bookingsystemRoomByCampusRoomCodeDataLoader.LoadAsync($"{CampusAbbreviation()}_{RoomCode()}");
    List<DataLoaders.bookingsystem.InternalTypes.ReservationDto> reservationDtos = bookingsystemrooms.Any() ? await _bookingsystemReservationsByObjectDataLoader.LoadAsync(new Tuple<int, int>(bookingsystemrooms.First().types[0], bookingsystemrooms.First().id)) : new();
    IReadOnlyList<DataLoaders.bookingsystem.InternalTypes.ObjectDto> objectRelations = reservationDtos.Any() ? await _bookingsystemObjectByIdsDataLoader.LoadAsync(reservationDtos.Select(x => x.objects.Select(y => y.objectId)).SelectMany(x => x).Distinct().ToList()) : new List<DataLoaders.bookingsystem.InternalTypes.ObjectDto>();
    foreach (Microsoft.Graph.Models.User userresult in roomaadusers)
    {
        bookings.AddRange((await _aadusercalendareventsdataloader.LoadAsync(userresult.UserPrincipalName!)).Select(x => new UserCalendarEvent() { Source = $"Exchange ({userresult.UserPrincipalName})", StartTime = DateTime.Parse(x.Start.DateTime).ToLocalTime(), EndTime = DateTime.Parse(x.End.DateTime).ToLocalTime(), Description = x.Subject }));

    }
    foreach (DataLoaders.bookingsystem.InternalTypes.ObjectDto bookingsystemroomresult in bookingsystemrooms )
    {
        bookings.AddRange
        (
            reservationDtos.Select(x =>
                new UserCalendarEvent()
                {
                    Description = objectRelations.FirstOrDefault(y => x.objects.FirstOrDefault(z => _ReservationDescriptionsConfiguration.ReservationObjectRelationTypeIds.Contains(z.typeId))?.objectId == y.id)?
                    .fields.FirstOrDefault(y => _ReservationDescriptionsConfiguration.DescriptiondefiningObjectRelationFieldIds.Contains(y.fieldId))?.values.FirstOrDefault(),
                    Source = $"bookingsystem ({bookingsystemroomresult.fields.FirstOrDefault(y => y.fieldId == _bookingsystemReservationDescriptionsConfiguration.RoomNameFieldId).values.First()}({bookingsystemroomresult.id})) (Reservation-Id:{x.id})",
                    StartTime = DateTimeOffset.FromUnixTimeSeconds(x.begin).ToLocalTime().DateTime, EndTime = DateTimeOffset.FromUnixTimeSeconds(x.end).ToLocalTime().DateTime
                }
            )
        );
    }
    return bookings.OrderBy(x => x.StartTime).ToList();
}

All the dataloaders in Bookings are CacheDataLoaders except for bookingsystemObjectByIdsDataLoader which is a BatchDataLoader. This is where the error occurs; When HotChocolate executes the Bookings-resolver in parallel for each node in rooms, the bookingsystemObjectByIdsDataLoader-dataloader only returns the response for some of the nodes and it seems completely random which nodes get results from the DataLoader. Additionally, batching does not work and LoadBatchAsync gets called for every node. Isn't it meant to wait until all the nodes have made their requests and then run LoadBatchAsync once for the whole query, or have i misunderstood something?
I was able to workaround this issue by making the Bookings-method synchronus, but this is not an acceptable solution because it makes batching impossible and thus the query becomes slow.
Steps to reproduce

Resolve a list of objects whose class contain an async nested resolver
Within the nested resolver use results from a dataloader as arguments to a batchdataloader

Relevant log output
No response
Additional Context?
No response
Version
13.3.0 (however this also happened in 12.16)

I do not think that there is a bug but its due to how its used in your code. Its difficult to tell. If you think there is an issue create a very small repro that shows your issue in a simple an understandable way and we will have a look at it.
Closing this issue for now.

@michaelstaib Just wanted to bring you an update to tell you that you were absolutely right and that there was no bug. Turns out I had forgotten to run HttpResponseMessage.EnsureSuccessStatusCode in my DataLoader and I was being rate-limited by the API when running asynchronously. Probably as requests were being sent almost at the same time. Can't believe I missed something so obvious. Anyways, thanks for pointing me in the right direction :)


Change reference to karma-cli in README

To use a global karma script from the command line, it's better to install the karma-cli package, as detailed here:
http://karma-runner.github.io/1.0/intro/installation.html .

I signed it!


New Metric: Time Waiting for a Reviewer Action

This ticket comes from a broader discussion related to responsiveness metrics.
This ticket aims at discussing the Time Waiting for a Reviewer Action metric.
Google doc is available at https://docs.google.com/document/d/1crnjUcnnowPp5CSLoKGa2B19xldwbZT0ws87JMRs8z8/edit?usp=sharing

We are currently working on this and the discussion is happening in the google doc.

Help me!

How can I help @germonprez ? :)

Haha! What is the status of this metric? Right now, we're evaluating our set of metric. We have started this discussion in the metrics WG and will be bringing it to the community call next week.


error occured in dart analysis server

Analyzer Feedback ,
Unhandled exception:
FormatException: Invalid character (at character 11)
/home/p-c/[PATH_TO_FLUTTER_GIT_DIRECTORY]/flutter/bin/cache/flutter_tools.s...
          ^

#0      _Uri._fail (dart:core/uri.dart:1614)
#1      _Uri._normalize (dart:core/uri.dart:2309)
#2      _Uri._normalizeOrSubstring (dart:core/uri.dart:2265)
#3      _Uri._makePath (dart:core/uri.dart:2113)
#4      new _Uri.notSimple (dart:core/uri.dart:1477)
#5      Uri.parse (dart:core/uri.dart:1012)
#6      _resolveScriptUri (dart:_builtin:223)

@karan7701, were there anymore lines in the stacktrace? Somebody is trying to parse the file path and having issues. Can you also append the first ~20 chars or so of the file path? It looks like you've elided some of it above. Thanks!

After changing the path name the problem did not occur more, but I am not sure why it occurred though. The error was showed as I have given in Android studio.

I wonder if this might be a front-end issue? cc @kmillikin
The error above:
Unhandled exception:
FormatException: Invalid character (at character 11)
/home/p-c/[PATH_TO_FLUTTER_GIT_DIRECTORY]/flutter/bin/cache/flutter_tools.s...
          ^

looks like it ones generated by the FE. @karan7701, [PATH_TO_FLUTTER_GIT_DIRECTORY] was explicitly in your path?

Thanks for reporting this error! This was previously reported at https://github.com/dart-lang/sdk/issues/32532; please follow along there.

Duplicate of https://github.com/dart-lang/sdk/issues/32532


How to perform a grasp experiment using robotiq 3f-gripper?

It is easy to perform a grasp experiment using 2f_gripper.

But how to perform the same using 3f-gripper like this?

How to control the gripper?

This manipulation task uses a Robotiq gripper attached to a Franka Emika Panda arm. This task could be modified to use a different end effector.

Thanks a lot


Traceback error after install on Elementary OS (ubuntu)

Getting this error after installing
When I run trackerjacker -h I get this
Traceback (most recent call last):   File "/usr/local/bin/trackerjacker", line 9, in <module>     load_entry_point('trackerjacker==1.8.7', 'console_scripts', 'trackerjacker')()   File "/usr/lib/python2.7/dist-packages/pkg_resources/__init__.py", line 542, in load_entry_point     return get_distribution(dist).load_entry_point(group, name)   File "/usr/lib/python2.7/dist-packages/pkg_resources/__init__.py", line 2569, in load_entry_point     return ep.load()   File "/usr/lib/python2.7/dist-packages/pkg_resources/__init__.py", line 2229, in load     return self.resolve()   File "/usr/lib/python2.7/dist-packages/pkg_resources/__init__.py", line 2235, in resolve     module = __import__(self.module_name, fromlist=['__name__'], level=0)   File "/usr/local/lib/python2.7/dist-packages/trackerjacker/__main__.py", line 269     print('Vendor for {} not found'.format(args.mac_lookup), file=sys.stderr)                                                                  ^ SyntaxError: invalid syntax

I believe this is a result of not having scapy installed.
sudo apt-get install python-scapy


Devel improvements

I wanna test this some more on a vm before merging

Ehm.... sorry! I seem to have ignored your label and comment :-/

probably should've opened it as a draft anyway :)

probably should've opened it as a draft anyway :)

You know me and green buttons... I can't be trusted with them...


Add derive(PartialEq) for enums in event::inner

I noticed we don't have these, but they seem like a natural addition.

Thanks!