Failed to instrument gcc.

I encountered an issue while compiling gcc using afl-gcc/afl-g++. During the compilation process, it printed that instrumentation was being performed. However, when I tried running fuzzing, it aborts and saying that No instumentation detected.
test target: gcc-10.2.0
the configure parameters: configure --prefix=/gcc_build/gcc_binary --enable-checking=release --enable-languages=c,c++ --disable-multilib
while compiling, it shows that it has been instrumented:

when I run fuzzing:

Did I miss any settings or something else somewhere?

We had this problem before. It is related to how GCC compilation works. If I remember correctly, building GCC will first compile a small working compiler, and then use that compiler to compile the rest of GCC. So you might need to figure out how to avoid that. (We chose to use the QEMU mode instead :) )

We had this problem before. It is related to how GCC compilation works. If I remember correctly, building GCC will first compile a small working compiler, and then use that compiler to compile the rest of GCC. So you might need to figure out how to avoid that. (We chose to use the QEMU mode instead :) )

During the compilation configuration, I added the parameter --disable-bootstrap to solve this problem. Thank you for your reply.


include Typescript definitions

Includes Typescript type definitions for strict typing.

I'm not sure if this PR is going to be accepted or not so I created a typing that could be consumed publicly if it ever comes up...
https://github.com/DefinitelyTyped/DefinitelyTyped/pull/43011
@hughsk Let me know if you prefer the typing to be in this package.

I'm not sure if this PR is going to be accepted or not so I created a typing that could be consumed publicly if it ever comes up...
DefinitelyTyped/DefinitelyTyped#43011
@hughsk Let me know if you prefer the typing to be in this package.

PR was merged! :tada:


openai.error.InvalidRequestError: The model: gpt-4 does not exist

I thought this will work with GPT-3.5 and also thought that OpenAI made it possible to anyone to use GPT-4 API but after several hours tinkering with this I am not able to get it to work, I see the webpage but it keeps throwing an error after another (fixed them all) but I am unable to make it work because of this error

I have the same problem.

Hi! I’m one of the founders of Sweep, a github app that solves issues(like small bugs) by writing pull requests.
This looks like a good issue for Sweep https://github.com/sweepai/sweep to try. It might need more details from the maintainers though.
We have onboarding instructions here, I’m also happy to help you onboard directly :)

I have the same error "openai.error.InvalidRequestError: The model: gpt-4 does not exist" just stopped.

The model is configured here
https://github.com/assafelovic/gpt-researcher/blob/master/config/config.py#L25
By accessing an enviroment variable
self.smart_llm_model = os.getenv("SMART_LLM_MODEL", "gpt-4")
If you are having issues with access to gpt-4, you can set an environment variable with a model name that you do have access to e.g. gpt-3.5-turbo
For example:
export  SMART_LLM_MODEL="gpt-3.5-turbo"

Hi!
By making the following modifications, I was able to resolve the issue:

In gpt-researcher/config/config.py, substitute in line 25 "gpt-4" with "gpt-3.5-turbo-16k"
In gpt-researcher/config/config.py, substitute in line 27: 8000 with 4000

Upon executing this modified script, I encountered another error: "json.decoder.JSONDecodeError: Extra data: line 2 column 1 (char 58)". So, if you also get the same error, all you need to do is:
In gpt-researcher/agent/research_agent.py line 92, substitute "return json.loads(result)" with " return result". This avoids the double-parsing as result itself is a JSON Object.
Hope this helps!

@madiha1ahmed I did it your way and it worked. thanks!

It works for me now. Thanks


Release visibility

This is an absolute minor issue.
You probably want to mark v1.3 on the Release page as the latest. Currently, it displays the 2-years old v0.2 as the most recent, which can be slightly misleading on first look.

👍


Middle mouse button scrolling not working

VSCode Version: 1.47.3
OS Version: Windows 10

Steps to Reproduce:

Click with the scroll wheel in the code editor
Drag the mouse

Expected outcome: window scrolls
What happens instead: some kind of unnecessary highlighting

Does this issue occur when all extensions are disabled?: Yes
If you notice some familiarity with this issue, is because there is a neglected issue opened 4(FOUR) years ago without any attempt at fixing. And before stamping feature request on this, it is a BUG.

/gifPlease

/nogifforsomethingcommonsense

It is a bug not a feature request.

@vscode-triage-bot here's a screen recording, in case anyone is genuinely confused

Voted (immediately as soon as this post was created)... This would be very helpful to me...

We have more than 20 upvotes on this issue now. Just like with this issue.
What is the further process of this improvement request? Is the "20 upvotes limit" just a mirage?

We have more than 20 upvotes on this issue now. Just like with this issue.
What is the further process of this improvement request? Is the "20 upvotes limit" just a mirage?

FWIW, I wouldn't call this a bug.  It's definitely a feature request.  The current functionality appears to be modeled after Sublime's multi-line selection (this is different than "block selection") which shouldn't be removed.
Even visual studio doesn't have middle mouse scrolling out of the box (many extensions add this feature).
What I recommend is an option for the middle mouse behavior (multi-select being default).  Since there is a keyboard shortcut for multi-line select, users like myself can get the best of both worlds.

FWIW, I wouldn't call this a bug.  It's definitely a feature request.  The current functionality appears to be modeled after Sublime's multi-line selection (this is different than "block selection") which shouldn't be removed.
Even visual studio doesn't have middle mouse scrolling out of the box (many extensions add this feature).
What I recommend is an option for the middle mouse behavior (multi-select being default).  Since there is a keyboard shortcut for multi-line select, users like myself can get the best of both worlds.

Imagine there is a software which decides to do the click on right button and right click on left button of the mouse. It is not a "bug", it is a decision of the software makers. What would people do? Open bug reports. Mouse does not behave as expected.
A standard mouse has left button for click, right button for right click, and a scroll wheel for scrolling. The scroll wheel when pressed is the middle button. Middle button's standard use is auto scrolling.
We can argue that it is not a bug, it is a decision of developers to hijack the middle button for something else, but in that case the only sensible thing to do is to provide a checkbox to let it work as expected. The middle button was already doing something (auto scroll) before VS Code just hijacked it without notifying users about it.

Imagine there is a software which decides to do the click on right button and right click on left button of the mouse. It is not a "bug", it is a decision of the software makers. What would people do? Open bug reports. Mouse does not behave as expected.
A standard mouse has left button for click, right button for right click, and a scroll wheel for scrolling. The scroll wheel when pressed is the middle button. Middle button's standard use is auto scrolling.
We can argue that it is not a bug, it is a decision of developers to hijack the middle button for something else, but in that case the only sensible thing to do is to provide a checkbox to let it work as expected. The middle button was already doing something (auto scroll) before VS Code just hijacked it without notifying users about it.

Agreed, the point really isn't weather it's a bug or not.  I'm only pointing out that middle mouse scroll is something that isn't always implemented.  It's a feature that originated with web browsers, and many other applications have followed suit (it's not native to the Win32 API and your app doesn't automatically have the functionality).  Many apps don't scroll on middle click:

Visual studio
Many source control IDEs (Perforce P4V, Git extensions, etc.)
Notepad++
Sublime Text
Windows Explorer
etc. - the list is quite large

My main point is that the implementer should consider making it an option, since column select is a useful feature which I use all the time for multi-edit.

Agreed, the point really isn't weather it's a bug or not.  I'm only pointing out that middle mouse scroll is something that isn't always implemented.  It's a feature that originated with web browsers, and many other applications have followed suit (it's not native to the Win32 API and your app doesn't automatically have the functionality).  Many apps don't scroll on middle click:

Visual studio
Many source control IDEs (Perforce P4V, Git extensions, etc.)
Notepad++
Sublime Text
Windows Explorer
etc. - the list is quite large

My main point is that the implementer should consider making it an option, since column select is a useful feature which I use all the time for multi-edit.

With autoscroll, you can click (not hold) middle button and then drag. So it (at least this part) won't be conflicted with column select.
Of course, we still should have (and probably will get) options if it's ever going to be added.

With autoscroll, you can click (not hold) middle button and then drag. So it (at least this part) won't be conflicted with column select.
Of course, we still should have (and probably will get) options if it's ever going to be added.

That's a great point.  Most implementations have both states, but there's no reason VSCode needs to have the drag functionality allowing both functions (though it might feel weird).
I noticed that the extensions browser in VSCode does already have the middle mouse scroll functionality, but I'm unsure if it's because that view is actually some sort of 3rdparty web view or if it's actually implemented that way (I didn't get that far looking into it).

That's a great point.  Most implementations have both states, but there's no reason VSCode needs to have the drag functionality allowing both functions (though it might feel weird).
I noticed that the extensions browser in VSCode does already have the middle mouse scroll functionality, but I'm unsure if it's because that view is actually some sort of 3rdparty web view or if it's actually implemented that way (I didn't get that far looking into it).

Here's an autohotkey workaround:
https://github.com/qooqu/vs-code-mbutton-scroll-ahk

/duplicate #6302

With Lenovo Thinkpads on Windows there is a setting whether the middle mouse button should emulate scroll or do an actual middle mouse button input.
With it set to scrolling vscode scrolls properly with middle mouse button. However that breaks a lot of features in other applications, i.e. closing tabs in a browser with middle mouse click.
With it set to middle click, I cannot scroll in vscode using it.
It's a big problem for my workflow having to decide through a system-wide configuration whether I'd prefer scrolling in vscode or closing tabs in my browser / other applications.

Duplicates also of #129986 from Aug 2, 2021 and if I remember well everything was working fine before the last update of this period... @vscode-triage-bot is there any update on this bug ? I do not really understand why a necessary functionality that used to work take some much time for you to re-activate... please do something @microsoft

Closing as duplicate of #6302, the bot failed.

@hediet now that you closed this, the issue from 2016 will get the proper attention? So that is why this was not fixed until now, too many open tickets :D


Could not locate that visualization (id: BRFSS:-Respondents)

After uploading the data into elasticsearch, I'm unable to see the visualization in the kibana dashboard. For every element in the dashboard I get this error with different id not being located.

@osat Can you confirm the version of Kibana you are using?

I will try and reproduce this on kibana 5.6.3, updating the saved objects if required.

I'm not able to reproduce this in 5.6.3. When importing the dashboards into 5.6.3, i am prompted to select the index pattern - at this point you should select brfss as shown below:

Otherwise no issues. @osat did you see any errors on import of the dashboards? Did you create the index pattern prior to the import?

I've updated the example with this https://github.com/elastic/examples/pull/183 to illustrate this has been tested on 5.6.3

@osat happy to reopen if you can provide reproducible steps on 5.6.3 or later.


Update dependencies

What changed?
Updated some cadence server dependencies to higher minor versions.

Why?
Best practice to keep dependencies up to date.

How did you test it?
Pipeline build.

Potential risks
Build / Functionality issues with new dependencies.

Release notes

Documentation Changes

Pull Request Test Coverage Report for Build 01858736-9181-4c2c-9a07-77c24df52984

0 of 0   changed or added relevant lines in 0 files are covered.
102 unchanged lines in 16 files lost coverage.
Overall coverage increased (+0.02%) to 57.206%

Files with Coverage Reduction
New Missed Lines
%

common/persistence/executionManager.go
2
78.89%

common/persistence/statsComputer.go
2
94.64%

common/task/fifoTaskScheduler.go
2
85.57%

common/util.go
2
52.54%

service/history/execution/mutable_state_util.go
2
36.04%

service/history/task/transfer_active_task_executor.go
2
72.22%

service/matching/matcher.go
2
91.46%

common/persistence/serialization/parser.go
4
62.41%

common/persistence/serialization/thrift_decoder.go
4
53.06%

service/history/task/transfer_standby_task_executor.go
4
85.98%

Totals

Change from base Build 01857a77-c095-4358-b8fe-5a82b9321ebf:
0.02%

Covered Lines:
84886

Relevant Lines:
148387

💛  - Coveralls


Matchers for nested blocks

Extend the matcher mechanism to support matching bodies of structured operations, and blocks in general. Block matchers are similar to operation and value matchers and are rooted at the terminator for efficiency: it is cheaper to traverse from opreand use to its definition.
Restructure the capturing matcher base classes to allow any matcher to point to any other matcher as nested.
Use block body matchers to replace custom predicates for single-op bodies in softmax. The predicate for the terminator-only pass-through body cannot be replaced yet as it requires a "variadic" value matcher that corresponds to the entire list of terminator operands.

Closing stale PR.


Update How-to-use-different-LLM.md

Corrected grammatical errors to remove ambiguity and improve professionalism.

What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
docs update
Why was this change needed? (You can also link to an open issue here)
Some grammatical errors lead to misinterpretations.
Other information:
docs/pages/Guides/How-to-use-different-LLM.md

Thank you, @holopin-bot @Ayush-Prabhu


iot-device-registry credentials hash-function

Describe the bug
following the iot example I noticed that the hash-function property of the credentials doesn't match the hash-function provided when creating the credentials.
I made a POST request to the credentials endpoint of the device-registry indicating sha-512 as  hash-function, but querying the just created credential the hash-function is bcrypt
To Reproduce
[examples](systemtests-iot|+7)$ curl --insecure -X POST -i -H 'Content-Type: application/json' --data-binary '{"device-id": "4711","type": "hashed-password","auth-id": "sensor1","secrets": [{"hash-function" : "sha-512","pwd-plain":"'hono-secret'"}]}' https://$(oc get routes device-registry --template='{{ .spec.host }}')/credentials/myapp.iot
HTTP/1.1 201 Created
location: /credentials/myapp.iot/sensor1/hashed-password
content-length: 0
Set-Cookie: cf4e55db6204a0536329ceeca925c096=9a04f233a8eec5c077aa66bdbe4077b0; path=/; HttpOnly; Secure

[examples](systemtests-iot|+7)$ curl --insecure -X GET -i https://$(oc get routes device-registry --template='{{ .spec.host }}')/credentials/myapp.iot/4711
HTTP/1.1 200 OK
content-type: application/json; charset=utf-8
content-length: 221
Set-Cookie: cf4e55db6204a0536329ceeca925c096=9a04f233a8eec5c077aa66bdbe4077b0; path=/; HttpOnly; Secure
Cache-control: private

{"total":1,"credentials":[{"device-id":"4711","type":"hashed-password","auth-id":"sensor1","enabled":true,"secrets":[{"hash-function":"bcrypt","pwd-hash":"$2a$10$bAL7Zz8QQDk6vcysP7jazedzrf00nMRbHFtRAYY1iAdkypqLrELOm"}]}]}

I'm not sure if this is the expected behaviour or the request is not correct or if there is a bug here.

Yea, I think the whole API of the credentials part of the device registry is … complicated and should be fixed, completely.
When you provide the plain password, then the hash is ignored IIRC. When you provide the hash algorithm, then you need to hash the password yourself. And also do the salt yourself.
You can have a look here:
https://github.com/ctron/hat/blob/5ca0920a9f88c7e387060277bfa4abdf05dc5fcd/src/credentials.rs#L419-L450

Sounds reasonable to me, Thank you @ctron

There is currently a discussion going on removing this altogether: https://github.com/eclipse/hono/pull/1130#issuecomment-479829977


Reviewdog Diagnostic Format (RD Format, rdformat)

This is an umbrella issue of Reviewdog Diagnostic Format
document and proto: https://github.com/reviewdog/reviewdog/tree/master/proto/rdf

[x] RFC: Reviewdog Diagnostic Format #629

Input format support

[x] Support rdjsonl as input format #674
[x] Support rdjson as input format #703

Output format support

[ ] Support rdjsonl as output format
[ ] Support rdjson as output format

[x] Support diagnostic level #684

[x] Improve parsers' RD format support (errorformat,checkstyle) #690 #694

[x] Use Reviewdog Diagnostic Format internally #673
Support multiline diagnostic output

[x] -reporter=github-pr-review #680
[x]  -reporter=github-check (github-pr-check)  #684
[ ] -reporter=gitlab-mr-discussion
[ ] -reporter=gerrit-change-review
[ ] -reporter=local (Unified reporter)

[x] Improve comment output format (support severity, code, source name) #700
[ ] Support Code Suggestion (Tracked by #678)

[x] partially done. supported github-pr-review

[x] Update README and CHANGELOG

[ ] Create a dedicated Reviewdog Diagnostic Format repository
[ ] Support RD format as output of https://github.com/reviewdog/errorformat
[ ] Support conversion between RD Format and SARIF

SARIF references:

https://github.blog/2020-10-05-announcing-third-party-code-scanning-tools-static-analysis-and-developer-security-training/

There is also this one to look at: https://lsif.dev/


Front page: hover on "Advanced search" button should change cursor into button style

Right now hovering on the "Advanced search" button does not show the "click" style cursor, which means that users are not hinted that it is a button to be clicked upon.

This issue is reported by @kesara .

Fixed in v2022.8.8_1


chore: updating typescript to 5, removing ts-auto-mock

ts-auto-mock is been deprecated
https://github.com/Typescript-TDD/ts-auto-mock/
and it was what prevented us to go to typescript 5
ts-auto-mock relies on ttypescript and ttypescript doesn't work with typescript 5
I tried ttsc unsuccesfully
I'm not sure if this is the best way to go forward, this PR adds quite a bit of not-very-useful code, mostly generated by GPT.
but otherwise not been able to update typescript is not ideal either

I think this approach makes sense and will approve once the ts-ignore issue is addressed.


Updating logging, package.json and isVisible

isVisible may need to be rejected,  my changes sets a invalid element request to return the result object, this is against your specifications.


EKF_from_TLV.py import error

"from mmwave.tracking import GTRACK_visualize" in EKF_from_TLV.py is an error,  i revise it to 'gtrack_visualize' ,but i found that there isn't a function named create() in it so that 'gtrack_visualize.create()' error

i hope you forgive my poor English

have solved


How disable log in mongo conteiner?

In mongo version 2.6 have issue with filling disk 1Gb/day. After restart container space is cleaning and again filling disk. I thing need disable log (or redirect to /dev/null for showing in docker logs mongo )

may be mongo-docker have attributes for change path log?

I have a mongo container that was created 6 months ago and I don't see any log files within the container taking space.  I even checked in my mounted volume and it only has the database files.  I do see my logs in docker logs.
$ docker diff mongo
C /tmp
A /tmp/mongodb-27017.sock
C /root
A /root/.dbshell
A /root/.mongorc.js

By default mongod logs to stdout, so running docker run -d --name some-mongo mongo:2.7 will make all logs available in docker logs some-mongo.  If you need to set limits on those logs, check out configuring log drivers. You could also configure it to point to gelf, syslog, or another logging service.
If you just want to change where mongod logs, then you can pass the --logpath option to it: docker run -d --name some-mongo mongo:2.7 --logpath /var/log/mongodb/server1.log --logappend.  You'll probably need to ensure the folder exists with the correct permissions in the container. With this route you would probably want to look in to having mongod open a new file on some sort of schedule https://docs.mongodb.com/v2.6/tutorial/rotate-log-files/, so that you can delete older logs.

Closing old issue. Feel free to comment on further troubleshooting if you feel this was closed in error or on the solution to help users running into the same problem.


LibreELEC addon

Hello,
@shanemeagher and I are trying to create a librespot addon for LibreELEC.
I open this pull request to document this effort and to request help.
This pull request currently includes two commits:

with-audiocache by @mherger
dns-sd

The with-audiocache commit is welcome on LibreELEC, whose storage is mainly flash based.
The dns-sd commit works, although libdns_sd is not linked statically into librespot.
I built librespot with
docker run -v /tmp/librespot-build:/build --env PKG_CONFIG_ALLOW_CROSS=0 --env PKG_CONFIG_ALL_STATIC=1 --env PKG_CONFIG_PATH=/usr/lib/arm-linux-gnueabihf/pkgconfig librespot-cross cargo build --release --target arm-unknown-linux-gnueabihf --no-default-features --features alsa-backend
Then I fetched libdns_sd.so with
docker run -v /tmp/librespot-build:/build --env PKG_CONFIG_ALLOW_CROSS=0 --env PKG_CONFIG_ALL_STATIC=1 --env PKG_CONFIG_PATH=/usr/lib/arm-linux-gnueabihf/pkgconfig librespot-cross cp /usr/lib/arm-linux-gnueabihf/libdns_sd.so.1 /build
After copying librespot and libdns_sd.so.1 to LibreELEC for RPi2, I succesfull ran
LD_LIBRARY_PATH=. ./librespot -b 320 -c ./cache -n test
So here are my questions/requests:

What should I do to statically link libdns_sd into librespot?
Would it be possible to reintroduce avahi (dns-sd) into librespot, as an alternative to mdns?

Thank you in advance for your support and regards.

Thanks,
My main concern with #181 (with-audiocache) is that is should be a runtime setting, not compile time. Sorry @michaelherger / @mherger (I'm guessing that's the same person), I completely forgot to comment back on that PR.
About dns-sd, I originally removed it because

It makes cross-compilation a lot more complicated. Audio backends aside, I've had to remove some features to reach today's point of no dependencies which can't be built by Cargo and cross-compile smoothly.
Some embedded devices don't have avahi running, and it's quite a big dependency to add

If it's a disabled by default dependency then I'm fine adding support for it, but rust-mdns must still exist as a fallback.
One a side note, this might interest you : https://github.com/plietar/python-librespot
It's a very basic python wrapper around librespot. You could use it to run librespot directly in your plugin, and offer tighter integration. But it would need a lot of work (including documentation) first.

Thank you @plietar for your reply
My skills with Rust are however very limited (I discovered Rust around May, 9).
I will leave it at that, in the hope that someone here (@shanemeagher, @joerg-krause, @michaelherger, you?) will be able to split the code in default mdns and optional avahi.

@plietar @awiouy I've created a commit (f2bee4f87138b9cdd62133f4ddf0bd1bdc76f568) for optionally using dns-sd instead of rust-mdns. rust-mdns (--with-rust-mdns) is the default for discovery, while librespot can be built with dns-sd using --with-avahi switch.

Great! I will update this pull request this week-end. Thanks @shanemeagher

Rebased to merely add docker-build-libreelec.sh

Closing this PR, since librespot can now be built with the LibreELEC toolchain (https://github.com/LibreELEC/LibreELEC.tv/pull/1622)


Plot legend: use a fixed width

This will ensure that the plot itself is the same size, regardless of label size.

Linking to @moontrip's #170  PR because I think we agreed that was a good enough legend fix for Phase 1.

On QA, I find that Plot legends do NOT have a fixed width and change in size depending on the length of the label. Screenshots added as examples of short and long label. We need clarification from the developers about what decisions were made regarding fixing this behavior since it is not fixed in QA.

Hi @nkittur-uga, thank you for your review. Actually this is different issue from legend. We have introduced legend ellipsis with tooltip, which longer text (20 characters for now) is changed with, e.g., 'trucatedtext...' format (please see an example screenshot in the following). The issue you have observed is long legend title, not legend, which is different each other. We have not considered legend title's ellipsis with tooltip so if you think it needs to be addressed, then new ticket/issue should be made.

Ah! Thanks for the clarification, @moontrip , I understand that I did not QA the right thing. Let me go QA the legend (the correct issue) and ask my team about this legend label issue, if we need a new ticket for that or not.

Tried this on GEMS1 with x=weight, y=height, overlay=water availability, (and also with overlay= drinking water container) and it worked well. Long values are truncated with ellipses and you can hover to see complete label. This passes QA and can be closed.

@nkittur-uga thanks again for your review 👍 The figure size of plotly is a bit strange and it is affected by legend title and legend as you noticed. Since there are many overlay variables that have relatively lengthy displayName, my feeling is that the legend title also needs to have a fixed width like introducing ellipsis with tooltip as legend was treated.

Needs a ticket then - I will make it :-)

Thanks @bobular for making a ticket (I was about to, but you beat me to it) :)
@moontrip Agreed that legend title would need a fixed width but would request the label (display name) to be wrapped text if possible, instead of ellipsis with tooltip.

@nkittur-uga thank you for your information. I think wrapped text means like multiple lines? Not quite sure if it is doable but will see at first. If not possible, we would need ellipsis with tooltip (for now)

@moontrip Yes, exactly, wrapping the text to cover multiple lines. And yes if that is not easily possible, ellipsis with tooltip will be great. Thanks.

Best to make these comments on the new ticket!


Does not see iOS 11 Simulator

It just doesn't :(

#22 This pull request uses more reliable way to inject dylibs and it should now see any simulator truly available. You can try.

Still having issues, I have the beta XCode and stable installed, but I used xcode-select to select the beta one yet it still can't see them :(

Injecting appropriate dynamic libraries from /opt/simject... Respringing 6E80CF2C-C1E3-4932-BEDD-6DE39D2B0523 (iPhone 7) ... An error was encountered processing the command (domain=NSPOSIXErrorDomain, code=2): The operation couldn’t be completed. No such file or directory No such file or directory Respringing 98DF8D53-E751-4CEF-8683-CF9A02BDA6B8 (iPhone 7) ... An error was encountered processing the command (domain=NSPOSIXErrorDomain, code=2): The operation couldn’t be completed. No such file or directory No such file or directory

@andrewwiik I presume it is by the absence of launchctl in iOS 11+ SDK, causing an error that file is not found. One could copy the aforementioned binary from earlier SDK (iOS 10 is recommended) to /bin of the SDK root.

isn't this something that simject should somehow handle though? @PoomSmart

@andrewwiik It was something I overlooked. There are two ways: (1) Auto-detect iOS 10.x SDK and copy the binary on-the-fly if necessary. (2) Just warn the user that the binary is not there and it must exist in iOS 11 SDK in order to make simject work.

@andrewwiik Please confirm if the solution works for you so maybe this issue can be finally closed. @angelXwind

@PoomSmart I wouldn't be able to consider this issue closed until one of those solutions is actually implemented in the code and a pull request is made, but I will test and get back to you give me a few mins

@PoomSmart maybe I am putting it in the wrong place but I am still getting the error

@andrewwiik Could you check if in ~/Library/Developer/CoreSimulator/Devices contains any folder named UDID of any simulator as indicated in your simject output?

@PoomSmart A folder for the UDID of the simulator that simject outputs is indeed present

@PoomSmart Simject seems the simulator now, that is fixed, but simject is not working on the XCode beta simulators for actual respringing and injecting

@andrewwiik What kind of error you face on Xcode beta at this point, the same one?

@PoomSmart If I run the command manually this is the output:
xcrun simctl spawn 98DF8D53-E751-4CEF-8683-CF9A02BDA6B8 launchctl setenv DYLD_INSERT_LIBRARIES /opt/simject/simject.dylib An error was encountered processing the command (domain=NSPOSIXErrorDomain, code=2): The operation couldn’t be completed. No such file or directory No such file or directory

@andrewwiik Please check if launchctl is actually inside /Applications/Xcode-beta.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/Library/CoreSimulator/Profiles/Runtimes/iOS.simruntime/Contents/Resources/RuntimeRoot/bin.

@PoomSmart OHHHH, you said put it in the SDK above, not the runtime root, these are two different folders haha give me one sec

@PoomSmart worked

I'll close this issue but let's see if we can get a command to copy that file put in the GroupMe @angelXwind @PoomSmart


Format inline code and left-align table headers in README.md

Regarding the alignment of table headers: now it matches the alignment of non-header cells.
I think these changes make the text look better, but feel free to disagree if you have a different taste. 😄

Thanks!


Activity diagram throws error inside needuml directive

There are syntax errors when activity diagram is realized inside a needuml directive. Below is the code and the corresponding error.

.. needuml::

    start
    :Some Action;
    :Some Other Action;
    note
    hello welcome to Note
    these are multi line!!
    endnote
    end

WARNING: error while running plantuml
b'ERROR\r\n3\r\nSyntax Error?\r\nSome diagram description contains errors\r\n'

Hi @MohSam1,
Thanks for reporting this.
The problem is allowmixing. For  directive needuml, it has allowmixing configured by default. But this syntax allowmixing is not allowed for activity diagram.
Will fix it soon.


pre-split files

Hello author, it seems that the pre-split file is not provided in the code. Can you provide it?

Hi, thanks for attention, the pre-split files have been uploaded.
Btw, if you're interested, we highly recommend you try our new work: https://github.com/xmed-lab/GenericSSL, which considers more practical scenarios of semi-supervised segmentation.
Good luck with your research.


use tox-lsr 2.3.0 and enable ansible-test

Upgrade to tox-lsr 2.3.0 which fixes several issues with running
ansible-test sanity from tox.
Add ansible-test to the python 3.6 test list.

Thank you for your approval, @Jakuje! Could you please merge this PR? Thanks!


Eventual Resource Leak

After a few months of research and bug fixes on my end I finally stabilized my environment. After about 11 days of uptime I started getting Page Crashed errors. At first it was here and there and I started seeing them in bulks. Restarting the servers fixed the problem.
My Config:
clusterLauncher.launch({       concurrency: Cluster.CONCURRENCY_BROWSER,       maxConcurrency: 2,       timeout: 300000,       puppeteerOptions: {         args: [DISABLE_CORS, '--no-sandbox', '--disable-dev-shm-usage', '--disable-gpu']       }     });
My Observations:
I noticed that puppeteer cluster starts up 8 chrome instances and these instances stay up the entire time. As time goes by their CPU goes higher and higher every time they are in use.
Question:
Why doesn't puppeteer cluster kill these instances every once in a while and spawn new ones instead?
Is there some config that I missed? My current option, the way I see it, is just to destroy the cluster and reinitialize it myself.
Ideas on something better?

It's currently not implemented: #84


flutter_math_fork-0.7.1 does not support flutter sdk: '>=3.2.0-191.0.dev <4.0.0'

Describe the bug
The package does not compile when used in the flutter beta channel.
To Reproduce
Steps to reproduce the behavior:

Switch to the flutter beta channel
Try to run the app

Additional context
Error (Xcode): ../../.pub-cache/hosted/pub.dev/flutter_math_fork-0.7.1/lib/src/widgets/selection/gesture_detector_builder_selectable.dart:38:22: Error: Type 'TapDragUpDetails' not found.

It is not compiling for me on flutter Channel Stable 3.16.0.
Here is my flutter doctor:
Doctor summary (to see all details, run flutter doctor -v):
[✓] Flutter (Channel stable, 3.16.0, on macOS 13.4 22F66 darwin-arm64, locale en-GB)
[✓] Android toolchain - develop for Android devices (Android SDK version 33.0.0)
[✓] Xcode - develop for iOS and macOS (Xcode 14.3.1)
[✓] Chrome - develop for the web
[✓] Android Studio (version 2021.3)
[✓] VS Code (version 1.84.2)
[✓] Connected device (2 available)
[✓] Network resources

It throws this error:
: Error: Type 'TapDragUpDetails' not found.
gesture_detector_builder_selectable.dart:38
  void onSingleTapUp(TapDragUpDetails details) {
                     ^^^^^^^^^^^^^^^^

: Error: 'TapDragUpDetails' isn't a type.
gesture_detector_builder_selectable.dart:38
  void onSingleTapUp(TapDragUpDetails details) {

                     ^^^^^^^^^^^^^^^^
Failed to compile application.

This should be fixed in https://github.com/simpleclub-extended/flutter_math_fork/pull/87

Fixed #87


Add list method to AggregateCounterReader

This resolves #13

Once the aggregate counter app is ported, we can add the appropriate tests for this as well.

Addressed the review comments.

@ilayaperumalg Please verify that this project is building. I am seeing compilation errors. E.g. in InMemoryAggregateCounterRepository the ArrayList import seemed missing. Also  AggregateCounterTests seems to have errors, e.g. cannot find AggregateCounterSinkApplication. Maybe I am missing something obvious here.

@ghillert No, it was my mistake. Sorry about that. Fixed them now.

Merged: eccd3652f7d8be6abebd2d819a99048073c39809


Question about FileLogger implementation

Do you plan or wish to implement the FileLogger as part of the aspnet/Logging project or it should be a third-party provider? I have interest to contribute to this feature, but I don't know where it should be.

No current plans for this, mostly because there are a lot of great comprehensive solutions that already exist. I think having such a feature built-in would be nice, but I suspect it's a huge amount of work due to what is likely to be a large "minimum viable implementation." Having said that, it's certainly worth a discussion.

I wonder why folks would choose not to use NLog or SeriLog for logging to a file.
Putting in Backlog for further discussion.

NLog project integration is too low ,They don't have a unified style.

Discussion: https://github.com/aspnet/Logging/issues/441
Closing this as a dup


Include trello cli!

It would be great if I could remove the twitter feed and replace it with my trello card info so I could view my sprint progress.
This: https://github.com/mheap/trello-cli does a great job of listing my cards. If only I could embed it!
Node Version: 7.9.0
tiny-core-terminal version: version: '1.0.8'
Shell: zsh
Terminal Program: gnome-terminal
Operating System: Ubuntu Linux
Thank you!

Hmm, I'm not super sure about including trello in this dashboard -- it sounds like it could just be a completely different dashboard altogether. That sounds more like a "what work do i have to do" dashboard (and you could combine it with a list of other todos), rather than a selfcare dashboard, which I'd like this to remain.

Yes good idea ! A button for switch with multiple tab

Hi, in what form would you integree trello? I think working on it ..

Well - I agree with @notwaldorf that it isn't related to the main application, but personally, I'd do something like:

Extract a skeleton from tiny-care-terminal which allows configurable "slots" to be used by whatever you want.
Make the git and trello integration "plugins" which can be slotted into the skeleton (above)

That way, tiny-care could keep on taking care, and yet we could configure it for use at say - stand-up, as a handy way of seeing what we were working on, what was coming up, what was completed etc.
People could then create different plugins, for whatever purposes they wanted. I think it would be a super-handy tool then.
As for the exact trello integration - we use it like a kan-ban board. So I'd want it to list summaries of cards in the columns "upcoming, in development, in qa, and released"

Have you looked at blessed-contrib? That's exactly what it does -- it draws the dashboard for you, and the boxes, and you can put whatever you want in it. I really don't want to maintain a plugin dashboard framework thing :)

I did briefly look at it - but I didn't have time to understand what tiny-care-terminal added on top.
In that case @PrincesseLulu maybe it's worth starting with blessed-contrib and building our own dashboard.

Yes i think to, i'have download the source and i read the documentation.

@PrincesseLulu happy to help where I can - if you want to start a repository and add me as a contributor then please do and we'll take the discussion there!

Yes i do that's now

Going to close this, since it sounds like y'all have a good plan for it. Good luck! <3


Physics: Solve the 'tunnelling' / 'bullet through paper' problem

This is the problem where an object is moving so quickly that it's next move iteration jumps it to the other side of an object that it ought to have collided with.

Notes to self:
On the physics-noodling branch, the engine is now fast enough to show that the tunnelling problem will always exist with the current implementation (seems obvious in hindsight) because fundamentally, we have to assume 60fps as an upper iteration bound, and if the object is moving sufficiently quickly, it will eventually skip over something.
So what to do?
Currently the engine is a sort of crude 'discrete' engine, in that it really just compares complete moves per iteration. That works perfectly ok (or ok enough) for anything doing a "safe" move, by which I'm meaning (possibly wrongly) that the next position is overlapping the previous position because it's moving slowly enough. In that scenario, the likelihood of tunnelling seems acceptably small (and so edge cases seem ignore-able, at least for now), and so I can treat these as the happy path and just use the existing approach for the calculations.
For "unsafe" items, what I need to do, is do "some" iterations from the old to new positions - ideally leaving no gaps but maybe there's an upper bound to attempts? - and estimate a TOI (time of impact) when it hits each thing (including other unsafe items, so that means iterating them together...), and then solve the collision(s) with the earliest TOI(s), and skip anything else. For example, if at the end of it's move (TOI: 1), a ball hits another ball, but half way there it would have hit a wall (TOI: 0.5), then the ball to ball collision never happened, and we just need to do the ball to wall collision.


vstack changing to hstack on medium-sized devices

Prerequisites

[X] I have searched for duplicate or closed feature requests
[X] I have read the contributing guidelines

Proposal
Hello,
I think it would be nice to have a vertical stacking on mobiles changing to a horizontal stacking on PCs.
Pseudocode
<div class="vstack hstack-md gap-2 ...">
    <button ...>
    <button ...>
</div>

Render on small screens

Render on larger screens

Motivation and context
It may be usefull to easily fit buttons next to each others on large screens, but on top of each others on larger screens.

This could likely be best done via utilities on top of the helpers, just to keep things tidier. Try some of our flex utilities for now while we look into it, .flex-md-row on a .vstack for example.

Going to leave this as a won't fix for now since the flex utilities address it for now.


When using 'forwardTo' in route it is not possible to pass params

When using forwardTo in route which as far as i know takes a route name i cant pass paramteres.
Is there any other more powerfull redirecting methods?
Maybe forwardTo  could take a function which passes all the required data in order to proberly handle a redirection with params :-)?

I'm not sure you can do forwardTo with route params, but I agree that a callback similar to canActivate would be a good idea.
Alternatively, you can use canActivate to redirect with params. Although the router will interpret this as a transition error, it does redirect with parameters.
[
  {
    path: '/hello',
    name: 'redirect',
    canActivate: () => (toSate, fromState, done) => done({ redirect: { name: 'route', params: { hello: 'world' } } }),
  },
  {
    path: '/route?hello',
    name: 'route',
  }
]

@aksel Thanks for the tip :-)
I that might be my workaround for now :-) !

@thupi .forwardTo() is a configuration method. When you navigate to A and forward to B, any parameters passed to A are passed to B.


Support SET timezone to non-UTC time zone

Is your feature request related to a problem or challenge? Please describe what you are trying to do.
I'd like to add the support for SET TIMEZONE.
I'd like to have now() and TimestampTz use the timezone in config_options instead of the fixed UTC
Describe the solution you'd like

enable SET TIME TO [SOME_TIMEZONE]
It's currently disabled on purpose

https://github.com/apache/arrow-datafusion/blob/7e944ede86457fe0f43be44e0e5550229ecaf008/datafusion/sql/src/planner.rs#L2484-L2489
i'd like to remove it (probably replaced by some tz verification) and have this as the result
❯ set time zone to '+08:00';
0 rows in set. Query took 0.000 seconds.
❯ show time zone;
+--------------------------------+---------+
| name                           | setting |
+--------------------------------+---------+
| datafusion.execution.time_zone | +08:00  |
+--------------------------------+---------+
1 row in set. Query took 0.007 seconds.

now() returns the Timestamp<TimeUnit::Nanosecond, Some("SOME_TIMEZONE") according to the time zone we have. it's currently fixed as "UTC"
https://github.com/apache/arrow-datafusion/blob/7e944ede86457fe0f43be44e0e5550229ecaf008/datafusion/physical-expr/src/datetime_expressions.rs#L176-L186

Some("UTC".to_owned()) should be modified. we need to pass config_options or time zone into here this function
e.g.
current version
❯ set time zone to '+08:00';
0 rows in set. Query took 0.000 seconds.
❯ select arrow_typeof(now());
+------------------------------------+
| arrowtypeof(now())                 |
+------------------------------------+
| Timestamp(Nanosecond, Some("UTC")) |
+------------------------------------+
1 row in set. Query took 0.003 seconds.

becomes
❯ set time zone to '+08:00';
0 rows in set. Query took 0.000 seconds.
❯ select arrow_typeof(now());
+---------------------------------------+
| arrowtypeof(now())                    |
+---------------------------------------+
| Timestamp(Nanosecond, Some("+08:00")) |
+---------------------------------------+
1 row in set. Query took 0.003 seconds.

TimestampTz should use the timezone from config_options

https://github.com/apache/arrow-datafusion/blob/7e944ede86457fe0f43be44e0e5550229ecaf008/datafusion/sql/src/planner.rs#L2832-L2841
we currently fixed TimestampTz as "UTC" without considering config_options's timezone.
to enable it to consider config_options, we need to
3-1. make convert_simple_data_type as a method of SqlToRel
https://github.com/apache/arrow-datafusion/blob/7e944ede86457fe0f43be44e0e5550229ecaf008/datafusion/sql/src/planner.rs#L2811-L2817
3-2. Add get_config_option in ContextProvider so that we could get the time zone
https://github.com/apache/arrow-datafusion/blob/7e944ede86457fe0f43be44e0e5550229ecaf008/datafusion/sql/src/planner.rs#L2832-L2841
3-3 then we can use the timezone in config_options here to replace fixed UTC
https://github.com/apache/arrow-datafusion/blob/7e944ede86457fe0f43be44e0e5550229ecaf008/datafusion/sql/src/planner.rs#L2832-L2841
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.

@alamb  @liukun4515  @avantgardnerio @tustvold  would you mind helping to check whether this make sense?

i added a POC to showcase some functionalities
#4107
perhaps we should break it to several pc later

@waitingkuo thank you for your clear communication as always! You have the most reviewable PRs and issues I've seen :smile: .
The issue looks good to me, but I would propose tackling in stages:

Allow things like set time zone to '+08:00'; as described
Allow set time zone to 'US/Mountain'; or set time zone to 'US/Denver'; or ``set time zone to 'MT';`

This is due to the extra complication of what to do when someone does a select TO_TIMESTAMP('2022-11-06T01:30:00'); and the server timezone is 'US/Mountain' and there are two distinct 1:30AMs one in MDT and one in MST. Do we know what postgres does here? The only sensible thing I can think to do is fail the query with an error.

You have the most reviewable PRs and issues I've seen 😄 .

@waitingkuo thank you for your clear communication as always! You have the most reviewable PRs and issues I've seen 😄 .

❤

The issue looks good to me, but I would propose tackling in stages:

Allow things like set time zone to '+08:00'; as described
Allow set time zone to 'US/Mountain'; or set time zone to 'US/Denver'; or set time zone to 'MT';

This is due to the extra complication of what to do when someone does a select TO_TIMESTAMP('2022-11-06T01:30:00'); and the server timezone is 'US/Mountain' and there are two distinct 1:30AMs one in MDT and one in MST. Do we know what postgres does here? The only sensible thing I can think to do is fail the query with an error.

PostgreSQL's to_timestamp ouputs timestamp with time zone
https://www.postgresql.org/docs/current/functions-formatting.html
to_timestamp ( text, text ) → timestamp with time zone
Converts string to time stamp according to the given format.

to_timestamp('05 Dec 2000', 'DD Mon YYYY') → 2000-12-05 00:00:00-05

willy=# set timezone to 'America/Denver';
SET
willy=# select to_timestamp('05 Dec 2000', 'DD Mon YYYY');
      to_timestamp
------------------------
 2000-12-05 00:00:00-07
(1 row)

it shows the fixed offset timezone. i think there's no ambiguity in this approach.
The TO_TIMESTAMP for datafusion for now outputs Timestamp<TimeUnit, None>.
https://github.com/apache/arrow-datafusion/blob/6d00bd990ce5644181ad1549a6c70c8406219070/datafusion/expr/src/function.rs#L206-L220
I think it will make more sense if these TO_TIMESTSMP_XX functions change the signatures to Timestamp with Timezone. This is in my backlog as well  . I was working on #2979 to align TO_TIMESTAMP to Postgrseql's but found that we don't have timezone support. So I moved the focus to finish the time zone support (from sqlparser, arrow-rs, and finally datafusion 😃 )

i think we might need to refactor the return_type to support dynamical time zone determine
https://github.com/apache/arrow-datafusion/blob/6d00bd990ce5644181ad1549a6c70c8406219070/datafusion/expr/src/function.rs#L221-L223
now()'s return type is TImestamp<TimeUnt, Some("+08:00")> for now. need to get the timezone from config_options to and return TImestamp<TimeUnt, Some("SOME_TIMEZONE")> instead. I'll prefer move the now() support to another issue/pr.
i.e. 2. now() returns the Timestamp<TimeUnit::Nanosecond, Some("SOME_TIMEZONE") according to the time zone we have. it's currently fixed as "UTC"
will be implemented in this pr. we can do this instead for now
❯ set time zone to '+08:00';
0 rows in set. Query took 0.000 seconds.

❯ select now();
+----------------------------------+
| now()                            |
+----------------------------------+
| 2022-11-05T11:11:51.713660+00:00 |
+----------------------------------+
1 row in set. Query took 0.003 seconds.

❯ select now()::timestamptz;
+----------------------------------+
| now()                            |
+----------------------------------+
| 2022-11-05T19:11:14.245835+08:00 |
+----------------------------------+
1 row in set. Query took 0.003 seconds.

no ambiguity in this approach

I disagree. The problem is that America/Denver is on a statuary (legally constructed) timezone called Mountain Time. Because Mountain Time (presently) observes Daylight Savings Time, it is two "real" timezones: MDT or UTC-6 and MST UTC-7.

Unfortunately, this Sunday (2022-11-06), MT will be switching from UTC-6 to UTC-7 at 02:00 MDT, which will cause the clocks to go to 01:00 MST, and about half an hour later it will be 1:30AM MT for the second time this year.
So while I agree there is no ambiguity for to_timestamp('05 Dec 2000', 'DD Mon YYYY'), I think we need a test case specifically for select TO_TIMESTAMP('2022-11-06T01:30:00');, because given only that the only information known is:

2022-11-06T01:30:00
and America/Denver

There is no way to infer if this means there is no way to know if that corresponds with<PHONE_NUMBER> (UTC-6) or<PHONE_NUMBER> (UTC-7).

https://www.unixtimestamp.com/index.php

@avantgardnerio thank you. I didn't aware this before. never live in the area that has the timezone switch.
I did some research in Postgrseql and Chrono-tz
MST timezone offset: -7
MDT timezone offset: -6
In 2022, MDT
began from  Sunday, 13 March, 02:00 (changed from -7 to -6)
ended at  Sunday, 6 November, 02:00 (changed from -6 to -7)
willy=# set timezone to 'America/Denver';
SET

this is valid (right before the timezone shift):
willy=# select to_timestamp('2022-03-13 01:00', 'YYYY-MM-DD HH24:MI');
      to_timestamp
------------------------
 2022-03-13 01:00:00-07
(1 row)

willy=# select to_timestamp('2022-03-13 01:59', 'YYYY-MM-DD HH24:MI');
      to_timestamp
------------------------
 2022-03-13 01:59:00-07
(1 row)

begin from 2:00, it switches to MDT (-6)
i think the logic behind for this hour is:
parse as it's MST(-7), and then switch to MDT (-6), that's why we have an one hour shift here
willy=# select to_timestamp('2022-03-13 02:00', 'YYYY-MM-DD HH24:MI');
      to_timestamp
------------------------
 2022-03-13 03:00:00-06
(1 row)

willy=# select to_timestamp('2022-03-13 02:30', 'YYYY-MM-DD HH24:MI');
      to_timestamp
------------------------
 2022-03-13 03:30:00-06
(1 row)

willy=# select to_timestamp('2022-03-13 02:59', 'YYYY-MM-DD HH24:MI');
      to_timestamp
------------------------
 2022-03-13 03:59:00-06
(1 row)

and then the next hour it's parsed as MDT
willy=# select to_timestamp('2022-03-13 03:00', 'YYYY-MM-DD HH24:MI');
      to_timestamp
------------------------
 2022-03-13 03:00:00-06
(1 row)

In November 6th 2am MDT, time zone is switched back to MST (1am MST)
let's begin with something unambiguous
willy=# select to_timestamp('2022-11-06 00:59', 'YYYY-MM-DD HH24:MI');
      to_timestamp
------------------------
 2022-11-06 00:59:00-06
(1 row)

for the next 1 hour, it's ambiguous since both MST and MDT has 1 am. and this is what postgresql does, it uses MST even though 1am MDT is valid as well
willy=# select to_timestamp('2022-11-06 01:00', 'YYYY-MM-DD HH24:MI');
      to_timestamp
------------------------
 2022-11-06 01:00:00-07
(1 row)
willy=# select to_timestamp('2022-11-06 01:59', 'YYYY-MM-DD HH24:MI');
      to_timestamp
------------------------
 2022-11-06 01:59:00-07
(1 row)

after that, there's no ambiguity
willy=# select to_timestamp('2022-11-06 02:00', 'YYYY-MM-DD HH24:MI');
      to_timestamp
------------------------
 2022-11-06 02:00:00-07
(1 row)

conclusion for Postgrseql: when it's ambiguous or invalid, it's parsed as MST, and then switches to MDT if needed
now let's see the behavior for chrono-tz
     let tz: Tz = "America/Denver".parse().unwrap();
    let dt = tz.datetime_from_str("2022-03-13T01:59", "%Y-%m-%dT%H:%M");
    println!("2022-03-13T01:59 -> {:?} / {}", dt, dt.unwrap().to_rfc3339());
    let dt = tz.datetime_from_str("2022-03-13T02:00", "%Y-%m-%dT%H:%M");
    println!("2022-03-13T02:00 -> {:?}", dt);
    let dt = tz.datetime_from_str("2022-03-13T02:59", "%Y-%m-%dT%H:%M");
    println!("2022-03-13T02:59 -> {:?}", dt);
    let dt = tz.datetime_from_str("2022-03-13T03:00", "%Y-%m-%dT%H:%M");
    println!("2022-03-13T03:00 -> {:?} / {}", dt, dt.unwrap().to_rfc3339());

2022-03-13T01:59 -> Ok(2022-03-13T01:59:00MST) / 2022-03-13T01:59:00-07:00
2022-03-13T02:00 -> Err(ParseError(Impossible))
2022-03-13T02:59 -> Err(ParseError(Impossible))
2022-03-13T03:00 -> Ok(2022-03-13T03:00:00MDT) / 2022-03-13T03:00:00-06:00

    let dt = tz.datetime_from_str("2022-11-06T00:59", "%Y-%m-%dT%H:%M");
    println!("2022-11-06T00:59 -> {:?} / {}", dt, dt.unwrap().to_rfc3339());
    let dt = tz.datetime_from_str("2022-11-06T01:00", "%Y-%m-%dT%H:%M");
    println!("2022-11-06T01:00 -> {:?}", dt);
    let dt = tz.datetime_from_str("2022-11-06T01:59", "%Y-%m-%dT%H:%M");
    println!("2022-11-06T01:59 -> {:?}", dt);
    let dt = tz.datetime_from_str("2022-11-06T02:00", "%Y-%m-%dT%H:%M");
    println!("2022-11-06T02:00 -> {:?} / {}", dt, dt.unwrap().to_rfc3339());

2022-11-06T00:59 -> Ok(2022-11-06T00:59:00MDT) / 2022-11-06T00:59:00-06:00
2022-11-06T01:00 -> Err(ParseError(NotEnough))
2022-11-06T01:59 -> Err(ParseError(NotEnough))
2022-11-06T02:00 -> Ok(2022-11-06T02:00:00MST) / 2022-11-06T02:00:00-07:00

I think chrono-tz did a good job here.

@waitingkuo thank you for your clear communication as always! You have the most reviewable PRs and issues I've seen 😄 .
The issue looks good to me, but I would propose tackling in stages:

Allow things like set time zone to '+08:00'; as described
Allow set time zone to 'US/Mountain'; or set time zone to 'US/Denver'; or set time zone to 'MT';

This is due to the extra complication of what to do when someone does a select TO_TIMESTAMP('2022-11-06T01:30:00'); and the server timezone is 'US/Mountain' and there are two distinct 1:30AMs one in MDT and one in MST. Do we know what postgres does here? The only sensible thing I can think to do is fail the query with an error.

i'll limit this pr to support fixed offset timezone for now. thank you @avantgardnerio

never live in the area that has the timezone switch

@waitingkuo I think this is good advice :) Hopefully the US ends this nonsense next year.
I find it troubling that postgres happily parses ambiguous timestamps and chooses a default arbitrarily, but it seems like the emerging trend for DataFusion is "just do what postgres does", so perhaps we just copy their flawed implementation.
What's even more troubling than it defaulting an ambiguous timestamp is that it happily parses a non-existent 2:30AM in March!
I guess the only real choice we have is:

do we follow postgres' arguably flawed behavior?
or do we throw errors for ambiguous/invalid timestamps?

 DST didn't always start or end in March/November, so a database is required to keep track of when various legal jurisdictions implement/modify/retract DST. In unix-based OSes I think this is a tzinfo file, but I know of no equivalent on Windows.
If we do embrace US/MT, I think we should account for the historical shifts i.e. we need tests for April < 1986 rather than March.

@avantgardnerio
TLDR:
chrono-tz use

timezone data in https://github.com/eggert/tz
https://github.com/chronotope/parse-zoneinfo as parser

IANA timezone database maintains the offset & leapseconds
https://www.iana.org/time-zones
this repo has the database and parser (written in c)
https://github.com/eggert/tz
here's the sample for North America
https://github.com/eggert/tz/blob/main/northamerica
chrono-tz use
https://github.com/eggert/tz as the timezone database
and https://github.com/chronotope/parse-zoneinfo as parser code

@avantgardnerio
perhaps we could force user to add the timezone offset while casting string to timestamptz
e.g.
correct
2000-01-01T02:00:00+00:00
2000-01-01T02:00:00-06:00
2000-01-01T02:00:00-07:00
2000-01-01T02:00:00Z (this is a special case)
note that if we set time zone as +08:00
2000-01-01T02:00:00-06:00  becomes2000-01-01T16:00:00+08:00
incorrect
2000-03-13T02:30:00 -> this is the one might be illegal in some timezone
2000-03-01T02:30:00 -> this should work for all the timezone but still disallow it

chrono-tz use

Very informative, ty!

perhaps we could force user to add the timezone offset

That would definitely eliminate the ambiguity. I'd love to see if others have opinions about this.


Slybot version number

no objections, @dangra ?

Probably that script isn't necessary anymore and we can leave the default build command, removing slybot/Makefile.buildbot from repo. Default build command adds by default the hash commit into version.
I preferred to just add it there because I wasn't 100% sure if that custom build command (bin/makedeb) is still being used.

no objections except we can try first to remove Makefile.buildbot and rely on default action.


docs: Copy correct directory at vk3d-proton

Signed-off-by: Peter Jung<EMAIL_ADDRESS>

Thanks!


New car docs

[ ] Add dashcam exception

It might be interesting to utilize the "silver" designation as a "grey zone" where cars that would be bronze in stock form, could be promoted via modifications (eg. SDSU, Pedal, ZSS, EPS f/w hack, etc.)... or perhaps have a separate page entirely like docs/CARS_modded.md that incorporates a more flexible interpretation.

The plan right now is to categorize each car based on the "stock" install and perhaps add a column indicating that it can achieve a gold-level experience with modifications. I kind of like your second README idea though.

[ ] Add dashcam exception

@vibhusapra That's because these values aren't in the CarInterface. Feel free to submit PRs for missing metadata like CP.minSteerSpeed and CP.minEnableSpeed

I propose doing this sorting manually. I posted a "score sheet" on discord.
All cars start with 3 points. You lose one for:

low torque (honda accord, nidec civic)
no radar, likely inaccessible without reflash (vw, honda bosch)
non mainline software support (chrysler)

3 = gold, 2 = silver, 0-1 = bronze
Toyota Corolla = Gold
Honda Civic (nidec) = Silver
Honda Accord = Bronze


TypeError: Cannot read property 'step' of undefined

Running the plain vanilla example with Node.js on the command line results in "TypeError: Cannot read property 'step' of undefined"  My webserver is not logging a request/response when I run this example.  What could I be doing wrong?
C:\Users\prowe030215\test16>node traverson.js
C:\Users\prowe030215\test16\node_modules\traverson\lib\transforms\fetch_resource.js:45
log.debug('error while processing step ', t.step);
^
TypeError: Cannot read property 'step' of undefined
at C:\Users\prowe030215\test16\node_modules\traverson\lib\transforms\fetch_resource.js:45:52
at detectContentType (C:\Users\prowe030215\test16\node_modules\traverson\lib\transforms\detect_content_type.js:16:7)
at Request._callback (C:\Users\prowe030215\test16\node_modules\traverson\lib\http_requests.js:60:10)
at Request.self.callback (C:\Users\prowe030215\test16\node_modules\request\request.js:198:22)
at emitTwo (events.js:87:13)
at Request.emit (events.js:172:7)
at Request. (C:\Users\prowe030215\test16\node_modules\request\request.js:1035:10)
at emitOne (events.js:82:20)
at Request.emit (events.js:169:7)
at IncomingMessage. (C:\Users\prowe030215\test16\node_modules\request\request.js:962:12)

http_proxy caused the error - making requests go outside instead of my request going to local webserver.
It would be nice to make the error message a bit more meaningful.

Re-opened, another cryptic error.  Is it because I am using HAL ?
C:\Users\prowe030215\test16>node traverson.js
ENTRY
traverson=[object Object]
REQUEST { uri: 'http://localhost:6060/allocation',
callback: [Function],
method: 'GET' }
EXIT
REQUEST make request http://localhost:6060/allocation
REQUEST onRequestResponse http://localhost:6060/allocation 200 { server: 'Apache-Coyote/1.1',
'content-type': 'application/hal+json;charset=UTF-8',
'transfer-encoding': 'chunked',
date: 'Wed, 20 Jan 2016 09:33:16 GMT',
connection: 'close' }
REQUEST reading response's body
REQUEST finish init function http://localhost:6060/allocation
REQUEST response end http://localhost:6060/allocation 200 { server: 'Apache-Coyote/1.1',
'content-type': 'application/hal+json;charset=UTF-8',
'transfer-encoding': 'chunked',
date: 'Wed, 20 Jan 2016 09:33:16 GMT',
connection: 'close' }
REQUEST end event http://localhost:6060/allocation
REQUEST has body http://localhost:6060/allocation 2219
REQUEST emitting complete http://localhost:6060/allocation
C:\Users\prowe030215\test16\node_modules\traverson\lib\transforms\fetch_resource.js:45
log.debug('error while processing step ', t.step);
^
TypeError: Cannot read property 'step' of undefined
at C:\Users\prowe030215\test16\node_modules\traverson\lib\transforms\fetch_resource.js:45:52
at detectContentType (C:\Users\prowe030215\test16\node_modules\traverson\lib\transforms\detect_content_type.js:16:7)
at Request._callback (C:\Users\prowe030215\test16\node_modules\traverson\lib\http_requests.js:60:10)
at Request.self.callback (C:\Users\prowe030215\test16\node_modules\request\request.js:198:22)
at emitTwo (events.js:87:13)
at Request.emit (events.js:172:7)
at Request. (C:\Users\prowe030215\test16\node_modules\request\request.js:1035:10)
at emitOne (events.js:82:20)
at Request.emit (events.js:169:7)
at IncomingMessage. (C:\Users\prowe030215\test16\node_modules\request\request.js:962:12)

Could you please post the exact code that causes this problem? That would make it easier for me to reproduce it. The line number/file name indicates that the traversal has been aborted - do you abort requests via traversal.abort() (see https://github.com/basti1302/traverson/blob/master/user-guide.markdown#aborting-the-link-traversal)?

Also, I noticed a problem in traverson that would actually explain the cryptic error message you got - a follow up. I fixed it in version 3.1.2 which I just released. Please try again with this release. It might not solve your problem completely, but at least the actual error message should no longer be shadowed by the TypeError you see now and that might help me to investigate further.
Thanks for the report, by the way.

Closing because of missing feedback from the OP. Feel free to reopen when ready to provide the information asked for above.


docker-machine : add new package

Motivation for this change
Docker-machine must exist :-)
Things done

[x] Tested using sandboxing
(nix.useSandbox on NixOS,
or option build-use-sandbox in nix.conf
on non-NixOS)
Built on platform(s)

[x] NixOS
[ ] OS X
[x] Linux

[x] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[x] Fits CONTRIBUTING.md.

@offlinehacker Notify me if it's ok : I add same docker maintainer since I'm not ready right now to maintain package.

I used docker-machine only once, but i do not mind if you keep me as a maintainer, also i'm fine with LGTM.


Add X509 Serialization functions

This PR also includes the functions needed to
serialize a MerkleTreeLeaf for X509 leaf entries.

Assigning to Martin for Go review.
My observations:

The fix to the test & algorithm looks good.
Serialization code looks good.

I'd suggest splitting this CL into two:

First, submit the leaf-building code.
Second, use the leaf-building code in the fix to the inclusion verification code. So rather than hard-coding the leaf in the tests twice, the serialization code will have it hard-coded for comparison, and the inclusion check test will load the SCT and cert from the testdata directory and will use the (now-tested) leaf building code to get the leaf.

Reduced PR to just include X509 Serialization functions.
@taknira @pphaneuf

LGTM, merging.


Recursive parse

No works with complex json example:
const schema = require("schm");
const { validate } = schema;
const userSchema = schema({
    name: String,
    age: Number,
    child: {
        name: String,
        age: Number,
    },
});

validate({ name: "John", age: 17, childs: {name: "Test", age: 1} }, userSchema)
    .then(parsedValues => {
        console.log("Yaay!", parsedValues);
    })
    .catch(errors => {
        console.log("Oops!", errors);
    });

I'm sorry, was that, but should I accuse property that is not being passed right? instead of giving only the error "undefined"

Sorry about the delayed response. It'll return the error if you make the properties required:
const userSchema = schema({
  name: {
    type: String,
    required: true
  }
});


V1alpha2 KFService Spec for predict, explain, transform

What this PR does / why we need it:
v1alpha2 spec to support predict, explain, transform service on KFService graph.
Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes https://github.com/kubeflow/kfserving/issues/301
Special notes for your reviewer:

Please confirm that if this PR changes any image versions, then that's the sole change this PR makes.

Release note:

v1alpha2 is not backwards compatible with v1alpha1, original `ModelSpec` is pushed down a level with predict service, added new services for explain and transform.

This change is

/retest

So cool to see this coming together :) put in a few comments...

I like EndpointSpec :) default endpoint flows well..
On Wed, Aug 21, 2019, 7:19 PM Ellis Bigelow<EMAIL_ADDRESS>wrote:

@ellis-bigelow commented on this pull request.
In pkg/apis/serving/v1alpha2/kfservice_types.go
https://github.com/kubeflow/kfserving/pull/300#discussion_r316472653:

}

-// ModelSpec defines the configuration to route traffic to a predictor.
-type ModelSpec struct {
+type ComponentsSpec struct {
What about something like EndpointSpec or RouteSpec?
Canary and Default are effectively different "endpoints". This maps
somewhat cleanly to AWS's data model of Models and Endpoints. We've just
cleaned it up a bit :).
In pkg/apis/serving/v1alpha2/kfservice_types.go
https://github.com/kubeflow/kfserving/pull/300#discussion_r316472716:

}

-// ModelSpec defines the configuration to route traffic to a predictor.
-type ModelSpec struct {
+type ComponentsSpec struct {

// predict defines the model serving spec
// +required
Predict ModelSpec json:"predict"

+1 to PredictSpec.
In pkg/apis/serving/v1alpha2/kfservice_types.go
https://github.com/kubeflow/kfserving/pull/300#discussion_r316472738:

-// ModelSpec defines the configuration to route traffic to a predictor.
-type ModelSpec struct {
+type ComponentsSpec struct {

// predict defines the model serving spec
// +required
Predict ModelSpec json:"predict"

// explain defines the model explanation service spec
// explain service calls to transform or predict service
// +optional
Explain *ExplainSpec json:"explain,omitempty"

// transform defines the transform service spec for pre/post processing
// transform service calls to predict service
// +optional
Transform *TransformSpec json:"transform,omitempty"

Love it.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/kubeflow/kfserving/pull/300?email_source=notifications&email_token=AA2CTBMKBSXEUJDTGE72J3TQFXZT7A5CNFSM4IOPTXNKYY3PNVWWK3TUL52HS4DFWFIHK3DMKJSXC5LFON2FEZLWNFSXPKTDN5WW2ZLOORPWSZGOCCKGJEI#pullrequestreview-278160529,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AA2CTBK3CLE6ANACVHK6PPDQFXZT7ANCNFSM4IOPTXNA
.

/retest

very cool!
/lgtm

/hold

/unhold
/lgtm

/lgtm

/unhold
ready to merge @yuzisun?

/unhold
ready to merge @yuzisun?

yes, good to merge!

/approve
/unhold

/hold cancel


Reports stopped working, Failed generating dataframe local variable 'response' referenced before assignment

I had set up superset two days ago with compose and the non-dev configuration and set up smtp data and reporting and created a report. everything worked as expected, emails were sent. but since today the reports are not being sent, instead I receive an error message via Email:
Error Message in reports:
Failed generating dataframe local variable 'response' referenced before assignment
How to reproduce the bug
I actually deleted the whole superset instance, removed all containers and volumes and started from scratch. Same thing, it worked for a few hours, then the error comes up and no reports are being sent.

i cloned the repo
used prod settings
config like below
docker compose up

Expected results
reports are being sent
Actual results
reports are not being sent
Screenshots

Environment

browser type and version: firefox
superset version: Superset 0.0.0dev (d5ea537b0eb3e102677d63811b99cf2c4b31a3ab)
python version: Python 3.8.12
node.js version: idk, doesnt say
any feature flags active:  superset_config_docker.py is set with these values:

ENABLE_TEMPLATE_PROCESSING = True
ENABLE_JAVASCRIPT_CONTROLS = True
EMAIL_NOTIFICATIONS = True
ENABLE_SCHEDULED_EMAIL_REPORTS = True
ALERT_REPORTS_NOTIFICATION_DRY_RUN = False
SMTP is set

Checklist
Make sure to follow these steps before submitting your issue - thank you!

[x] I have checked the superset logs for python stacktraces and included it here as text if there are any.
[x] I have reproduced the issue with at least the latest released version of superset.
[x] I have checked the issue tracker for the same issue and I haven't found one similar.

Additional context
Add any other context about the problem here.
superset_app          | <IP_ADDRESS> - - [06/May/2022:13:48:33 +0000] "GET /health HTTP/1.1" 200 2 "-" "curl/7.74.0"
superset_worker_beat  | [2022-05-06 13:49:00,050: INFO/MainProcess] Scheduler: Sending due task reports.scheduler (reports.scheduler)
superset_worker       | [2022-05-06 13:49:00,053: INFO/MainProcess] Task reports.scheduler[0ff76ece-eb1e-4c70-b4ae-55b23cda0f11] received
superset_worker       | Scheduling alert test eta: 2022-05-06 13:49:00
superset_worker       | [2022-05-06 13:49:00,068: INFO/ForkPoolWorker-7] Scheduling alert test eta: 2022-05-06 13:49:00
superset_worker       | [2022-05-06 13:49:00,071: INFO/MainProcess] Task reports.execute[075a2ff2-3463-4728-90d6-c659a8785fb6] received
superset_worker       | [2022-05-06 13:49:00,072: INFO/ForkPoolWorker-7] Task reports.scheduler[0ff76ece-eb1e-4c70-b4ae-55b23cda0f11] succeeded in 0.01864649821072817s: None
superset_worker       | Getting chart from http://superset:8088/api/v1/chart/5/data/?format=json&type=post_processed&force=false
superset_worker       | [2022-05-06 13:49:00,117: INFO/ForkPoolWorker-7] Getting chart from http://superset:8088/api/v1/chart/5/data/?format=json&type=post_processed&force=false
superset_worker       | Report state: Failed generating dataframe local variable 'response' referenced before assignment
superset_worker       | [2022-05-06 13:49:00,143: INFO/ForkPoolWorker-7] Report state: Failed generating dataframe local variable 'response' referenced before assignment
superset_worker       | [2022-05-06 13:49:00,145: INFO/ForkPoolWorker-7] Task reports.execute[075a2ff2-3463-4728-90d6-c659a8785fb6] succeeded in 0.0715110320597887s: None
superset_app          | <IP_ADDRESS> - - [06/May/2022:13:49:03 +0000] "GET /health HTTP/1.1" 200 2 "-" "curl/7.74.0"

The Email looks like this:

Anybody?

Now tried it with v.1.5.0, but still no luck. Anybody getting the same error?

I created a repo to reproduce:
https://github.com/phifa/superset_demo

I'm not sure if this is still an issue in current versions of Superset (3.x). If it is, we can re-open this, or feel free to open a new issue with updated context and a reproducible case using example data. We're no longer supporting Superset 2.x or prior, and it's been a while since this thread saw any activity, so I'm closing this as stale.


Azure Kinect Body tracking SDK crashes on opening

Describe the bug
Azure Kinect Body tracking SDK crashes on opening
To Reproduce
 build 18362.836

SDK Version:  <!-- 1.0.1

Hello, I wanted to perform body tracking for shoulder movement. The Azure kinect viewer opens up on the computer and I can see the depth camera information but the kinect body tracking does not open and crashes as soon as I click on it. I have tried uninstall and reinstall but it is showing a different icon compared to the viewer as can be seen in the picture above. Please advise what other information would you require.

@hpsinghjk Did you solve this issue? Having the same problem and cannot find a solution.

We fixed this with the firmware update. https://docs.microsoft.com/en-us/azure/kinect-dk/update-device-firmware


fix: lock autocomplete version

#148
I currently believe that we need to lock the autocomplete version until loadspecs is compatible.

@microsoft-github-policy-service agree [company="{your company}"]

@microsoft-github-policy-service agree [company="Tencent"]

@alanhg thanks for fixing this


feat(components): make "template" method being optional.

Features for components:

made "template" method being optional
added ability to return DOM node/fragment from "template" method
added tests for component binding

CC: @Leeds-eBooks, @mikeric, @ansman

I did also implement support for dependent component and will pull request it as soon as this is closed (https://github.com/stalniy/rivets/tree/improved-component).
Also plan to add support for rv-content component which will insert existing component content to specified point (aka ng-content)

As I mentioned in #500 I would like agreement from at least another contributor before merging in big changes, and this seems like a big change to me. Can you explain why the template method should be optional? I find coffeescript very hard to read...

@Leeds-eBooks  Template method should be optional because sometimes you will want to proceed with existing template (e.g. tabset)
<tabset>
  <tab title="title #1">Title 1</tab>
</tabset>

PS: That's defenetly not a big change. The biggest amount of work was done on writing tests in JavaScript.
Everything else is removal of code duplication and additional method renderTemplate

IMO, the changes code wise is an improvement.
Regarding the ability of using the elements inside a component i think the way to go is to implement something similar to yield in Riot (http://riotjs.com/api/#yielding-nested-html) or slot in Vue ( http://vuejs.org/guide/components.html#Content_Distribution_with_Slots )
It's a very flexible feature covering the above case and others

@blikblum I've already done this.
Dependent components: https://github.com/stalniy/rivets/tree/improved-component
Transclusion: https://github.com/stalniy/rivets/tree/transclusion
Docs and tests are added as well so waiting for this to be merged and will proceed with other pull-requests

Also I wrote to @mikeric and asked him to provide access to repo for me and @blikblum (don't know your email so couldn't add you to CC)

For those who are interested in I plan currently maintain own fork of rivets. So, today I publish 1.0 version  https://github.com/stalniy/rivets .
Did a lot of changes to components, everything is documented and tested. So, check spec/rivets and docs folders for more info

@stalniy I have been looking into this and it seems ok to me. You are adding features that people come to expect in libraries that have components. None of us can get ahold of @mikeric so, we will just work without him. Can you resolve the conflict in your branch? There were some test added for components in another PR. Yours are conflicting. I attempted to fix them myself but would prefer that you do it since you know your feature better than we do.
I have been looking through the docs on your fork. It looks like you are pushing things forward quite well.  In order to get ALL the changes you have mentioned (transclusion etc) I would love to see more work done on the DOC's for components. There are many statements made that do not have corresponding example / explanation. For example, the statement : 'Controller is accessible inside template by component's name or by custom name specified in as option.' I see no example of this.
If you update your PR to resolve the conflict, I will comb through the docs and fix them where I can / notify you where I am unsure. Once we get the docs in line, I will merge this in.
We really appreciate your work. Please understand that components are one of the most confusing parts of Rivets right now (as evidenced by the amount of Issue's we get around them).  If we can make components and their the docs better, then we can avoid some of that effort.
If @Leeds-eBooks and I had permissions to add more contributors. We probably would.

@Duder-onomy that is a great news! Will solve conflicts today

@Duder-onomy done. Will create new pull request as soon as this one is merged

What about the es6 branch? All this work is going to need redoing, shouldn't we be putting new features into es6 and pushing forward with that?

@Leeds-eBooks I believe we don't have enough tests in order to switch to es6 branch

Also I believe there should be some convertor like coffeescript -> es6

@Leeds-eBooks, @mikeric, @ansman, @Duder-onomy  Are there any reasons that blocks the merge of this pull request?
All the changes here backward compatible. @Leeds-eBooks if you want me to create the same request  for es6 branch just let me know. But I'd like to move components stuff forward.

Sorry for the delay on this, @Duder-onomy was going to review and merge the components stuff you have done as I think he is more confident on this side of things. I'm sure he'll come to it as soon as he can!

@Duder-onomy I know you are currently pretty busy but if you could just take a quick look at this and merge (as there are nothing you haven't seen) we would proceed with components enhancements

@Leeds-eBooks by the way the good example of the component with optional template is form. form component can extend default functionality of the form tag and provide some useful methods like form.isValid, form.errors, etc.


Error: Failed to install CocoaPods dependencies for iOS project, which is required by this template

I posted in detail what the bug is I got at SO.
I am getting this when trying to install React Native for MacOS.
$ npx react-native init myproject
ld: warning: dylib (/usr/local/opt/llvm/lib/libc++.dylib) was built for newer macOS version (10.15) than being linked (10.13)
ld: warning: dylib (/usr/local/opt/llvm/lib/libunwind.dylib) was built for newer macOS version (10.15) than being linked (10.13)
ld: warning: dylib (/usr/local/opt/llvm/lib/libunwind.dylib) was built for newer macOS version (10.15) than being linked (10.13)
ld: warning: dylib (/usr/local/opt/llvm/lib/libc++.dylib) was built for newer macOS version (10.15) than being linked (10.13)
ld: warning: dylib (/usr/local/opt/llvm/lib/libunwind.dylib) was built for newer macOS version (10.15) than being linked (10.13)
ld: warning: dylib (/usr/local/opt/llvm/lib/libunwind.dylib) was built for newer macOS version (10.15) than being linked (10.13)
...
✔ Downloading template
✔ Copying template
✔ Processing template
✖ Installing CocoaPods dependencies (this may take a few minutes)
✖ Installing CocoaPods dependencies (this may take a few minutes)
error Error: Failed to install CocoaPods dependencies for iOS project, which is required by this template.
Please try again manually: "cd ./myproject/ios && pod install".
CocoaPods documentation: https://cocoapods.org/
$ cd ./myproject/ios && pod install
Analyzing dependencies
Fetching podspec for `DoubleConversion` from `../node_modules/react-native/third-party-podspecs/DoubleConversion.podspec`
Fetching podspec for `Folly` from `../node_modules/react-native/third-party-podspecs/Folly.podspec`
Fetching podspec for `glog` from `../node_modules/react-native/third-party-podspecs/glog.podspec`
Downloading dependencies
Installing CocoaAsyncSocket (7.6.5)
Installing CocoaLibEvent (1.0.0)
Installing DoubleConversion (1.1.6)
Installing FBLazyVector (0.63.4)
Installing FBReactNativeSpec (0.63.4)
Installing Flipper (0.54.0)
Installing Flipper-DoubleConversion (1.1.7)
Installing Flipper-Folly (2.3.0)
Installing Flipper-Glog (0.3.6)
[!] /bin/bash -c
set -e
#!/bin/bash
# Copyright (c) Facebook, Inc. and its affiliates.
#
# This source code is licensed under the MIT license found in the
# LICENSE file in the root directory of this source tree.

set -e

PLATFORM_NAME="${PLATFORM_NAME:-iphoneos}"
CURRENT_ARCH="${CURRENT_ARCH}"

if [ -z "$CURRENT_ARCH" ] || [ "$CURRENT_ARCH" == "undefined_arch" ]; then
    # Xcode 10 beta sets CURRENT_ARCH to "undefined_arch", this leads to incorrect linker arg.
    # it's better to rely on platform name as fallback because architecture differs between simulator and device

    if [[ "$PLATFORM_NAME" == *"simulator"* ]]; then
        CURRENT_ARCH="x86_64"
    else
        CURRENT_ARCH="armv7"
    fi
fi

export CC="$(xcrun -find -sdk $PLATFORM_NAME cc) -arch $CURRENT_ARCH -isysroot $(xcrun -sdk $PLATFORM_NAME --show-sdk-path)"
export CXX="$CC"

# Remove automake symlink if it exists
if [ -h "test-driver" ]; then
    rm test-driver
fi

./configure --host arm-apple-darwin

# Fix build for tvOS
cat << EOF >> src/config.h
/* Add in so we have Apple Target Conditionals */
#ifdef __APPLE__
#include <TargetConditionals.h>
#include <Availability.h>
#endif
/* Special configuration for AppleTVOS */
#if TARGET_OS_TV
#undef HAVE_SYSCALL_H
#undef HAVE_SYS_SYSCALL_H
#undef OS_MACOSX
#endif
/* Special configuration for ucontext */
#undef HAVE_UCONTEXT_H
#undef PC_FROM_UCONTEXT
#if defined(__x86_64__)
#define PC_FROM_UCONTEXT uc_mcontext->__ss.__rip
#elif defined(__i386__)
#define PC_FROM_UCONTEXT uc_mcontext->__ss.__eip
#endif
EOF

# Prepare exported header include
EXPORTED_INCLUDE_DIR="exported/glog"
mkdir -p exported/glog
cp -f src/glog/log_severity.h "$EXPORTED_INCLUDE_DIR/"
cp -f src/glog/logging.h "$EXPORTED_INCLUDE_DIR/"
cp -f src/glog/raw_logging.h "$EXPORTED_INCLUDE_DIR/"
cp -f src/glog/stl_logging.h "$EXPORTED_INCLUDE_DIR/"
cp -f src/glog/vlog_is_on.h "$EXPORTED_INCLUDE_DIR/"

checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for arm-apple-darwin-strip... no
checking for strip... strip
checking for a thread-safe mkdir -p... ./install-sh -c -d
checking for gawk... no
checking for mawk... no
checking for nawk... no
checking for awk... awk
checking whether make sets $(MAKE)... yes
checking whether make supports nested variables... yes
checking for arm-apple-darwin-gcc... /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/cc -arch armv7 -isysroot /Applications/Xcode.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/SDKs/iPhoneOS14.3.sdk
checking whether the C compiler works... no
/Users/lancepollard/Library/Caches/CocoaPods/Pods/Release/Flipper-Glog/0.3.6-1dfd6/missing: Unknown `--is-lightweight' option
Try `/Users/lancepollard/Library/Caches/CocoaPods/Pods/Release/Flipper-Glog/0.3.6-1dfd6/missing --help' for more information
configure: WARNING: 'missing' script is too old or missing
configure: error: in `/Users/lancepollard/Library/Caches/CocoaPods/Pods/Release/Flipper-Glog/0.3.6-1dfd6':
configure: error: C compiler cannot create executables
See `config.log' for more details

A snippet from config.log says:
clang: error: argument to '-V' is missing (expected 1 value)
clang: error: no input files
configure:3685: $? = 1
configure:3674: /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/cc -arch armv7 -isysroot /Applications/Xcode.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/SDKs/iPhoneOS14.3.sdk -qversion >&5
clang: error: unknown argument '-qversion'; did you mean '--version'?
clang: error: no input files
configure:3685: $? = 1
configure:3705: checking whether the C compiler works
configure:3727: /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/cc -arch armv7 -isysroot /Applications/Xcode.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/SDKs/iPhoneOS14.3.sdk  -I/usr/local/opt/llvm/include -L/usr/local/opt/llvm/lib conftest.c  >&5
ld: in '/usr/local/opt/llvm/lib/libunwind.dylib', building for iOS-armv7 but attempting to link with file built for macOS-x86_64
clang: error: linker command failed with exit code 1 (use -v to see invocation)
configure:3731: $? = 1
configure:3769: result: no
configure: failed program was:
...
configure: exit 77

My Mac version is Catalina 10.15.7 (19H2). XCode is version 12.

I tried everything from https://stackoverflow.com/questions/58934022/react-native-error-failed-to-install-cocoapods-dependencies-for-ios-project-w, but nothing worked. I invoked brew install cocoapods as well.
Any ideas how to get past this? Could it be something to do with the fact that I have a node_modules folder higher up in the directory structure (above where I am running the commands)? I don't know what this error means.
Here is also output from the missing command:
$ /Users/lancepollard/Library/Caches/CocoaPods/Pods/Release/Flipper-Glog/0.3.6-1dfd6/missing --help
/Users/lancepollard/Library/Caches/CocoaPods/Pods/Release/Flipper-Glog/0.3.6-1dfd6/missing [OPTION]... PROGRAM [ARGUMENT]...

Handle `PROGRAM [ARGUMENT]...' for when PROGRAM is missing, or return an
error status if there is no known handling for PROGRAM.

Options:
  -h, --help      display this help and exit
  -v, --version   output version information and exit
  --run           try to run the given command, and emulate it if it fails

Supported PROGRAM values:
  aclocal      touch file `aclocal.m4'
  autoconf     touch file `configure'
  autoheader   touch file `config.h.in'
  autom4te     touch the output file, or create a stub one
  automake     touch all `Makefile.in' files
  bison        create `y.tab.[ch]', if possible, from existing .[ch]
  flex         create `lex.yy.c', if possible, from existing .c
  help2man     touch the output file
  lex          create `lex.yy.c', if possible, from existing .c
  makeinfo     touch the output file
  tar          try tar, gnutar, gtar, then tar without non-portable flags
  yacc         create `y.tab.[ch]', if possible, from existing .[ch]

Send bug reports to<EMAIL_ADDRESS>

    OS: macOS 10.15.7
    CPU: (8) x64 Intel(R) Core(TM) i5-1030NG7 CPU @ 1.10GHz
    Memory: 611.49 MB / 8.00 GB
    Shell: 5.7.1 - /bin/zsh
  Binaries:
    Node: 14.3.0 - /usr/local/bin/node
    Yarn: Not Found
    npm: 6.14.5 - /usr/local/bin/npm
    Watchman: 4.9.0 - /usr/local/bin/watchman
  Managers:
    CocoaPods: 1.10.1 - /usr/local/bin/pod
  SDKs:
    iOS SDK:
      Platforms: iOS 14.3, DriverKit 20.2, macOS 11.1, tvOS 14.3, watchOS 7.2
    Android SDK: Not Found
  IDEs:
    Android Studio: Not Found
    Xcode: 12.3/12C33 - /usr/bin/xcodebuild
  Languages:
    Java: 14.0.1 - /usr/bin/javac
    Python: 2.7.16 - /usr/bin/python
  npmPackages:
    @react-native-community/cli: Not Found
    react: Not Found
    react-native: Not Found
    react-native-macos: Not Found
  npmGlobalPackages:
    *react-native*: Not Found```

    OS: macOS 10.15.7
    CPU: (8) x64 Intel(R) Core(TM) i5-1030NG7 CPU @ 1.10GHz
    Memory: 611.49 MB / 8.00 GB
    Shell: 5.7.1 - /bin/zsh
  Binaries:
    Node: 14.3.0 - /usr/local/bin/node
    Yarn: Not Found
    npm: 6.14.5 - /usr/local/bin/npm
    Watchman: 4.9.0 - /usr/local/bin/watchman
  Managers:
    CocoaPods: 1.10.1 - /usr/local/bin/pod
  SDKs:
    iOS SDK:
      Platforms: iOS 14.3, DriverKit 20.2, macOS 11.1, tvOS 14.3, watchOS 7.2
    Android SDK: Not Found
  IDEs:
    Android Studio: Not Found
    Xcode: 12.3/12C33 - /usr/bin/xcodebuild
  Languages:
    Java: 14.0.1 - /usr/bin/javac
    Python: 2.7.16 - /usr/bin/python
  npmPackages:
    @react-native-community/cli: Not Found
    react: Not Found
    react-native: Not Found
    react-native-macos: Not Found
  npmGlobalPackages:
    *react-native*: Not Found```

@lancejpollard did you manage to solve this? I'm having the some issue and can't find anything online

@xjord not sure if you found it already but it was because of some compiler flags left in some random file, it's in here in some thread somewhere I just don't remember where! Some LLVM flags.

https://stackoverflow.com/a/65660622/169992

@xjord not sure if you found it already but it was because of some compiler flags left in some random file, it's in here in some thread somewhere I just don't remember where! Some LLVM flags.

Thanks @lancejpollard, I was able to fix it with git config --global core.autocrlf false. I found out that git config core.autocrlf  should be set to false otherwise git checkout will often try to turn LF line endings into CRLF, which can easily break fragile files.

This error happened to me as well. It was because of old CocoaPods version. I used version 1.8.0. After upgrading it to 1.10.1, the error was gone

This error happened to me as well. It was because of old CocoaPods version. I used version 1.8.0. After upgrading it to 1.10.1, the error was gone

I can confirm that @miidx solution works.
On OS X, I updated with
sudo gem install cocoapods

Then ran pod install, which threw this error:
$ pod install
Analyzing dependencies
Fetching podspec for `DoubleConversion` from `../node_modules/react-native/third-party-podspecs/DoubleConversion.podspec`
Fetching podspec for `RCT-Folly` from `../node_modules/react-native/third-party-podspecs/RCT-Folly.podspec`
Fetching podspec for `glog` from `../node_modules/react-native/third-party-podspecs/glog.podspec`
[!] CocoaPods could not find compatible versions for pod "FlipperKit/FlipperKitHighlightOverlay":
  In Podfile:
    FlipperKit/FlipperKitHighlightOverlay (~> 0.75.1)

None of your spec sources contain a spec satisfying the dependency: `FlipperKit/FlipperKitHighlightOverlay (~> 0.75.1)`.

You have either:
 * out-of-date source repos which you can update with `pod repo update` or with `pod install --repo-update`.
 * mistyped the name or version.
 * not added the source repo that hosts the Podspec to your Podfile.

Which got resolved by updating pod repo
$ pod repo update
Updating spec repo `trunk`

brew install cocoapods
worked for me like a charm after try every possible solution, I have a M1 2020, hope it helps

brew install cocoapods
worked for me like a charm after try every possible solution, I have a M1 2020, hope it helps

Thank you, installing with brew worked for me too on my M1.

brew install cocoapods
worked for me like a charm after try every possible solution, I have a M1 2020, hope it helps

Thank you, installing with brew worked for me too on my M1.

After this issue I have a arm4 problem when run npx react-native run-ios.
Solved adding arm64 in excluded architectures of the project and pod in Xcode build settings.

brew install cocoapods
worked for me like a charm after try every possible solution, I have a M1 2020, hope it helps

Thank you, installing with brew worked for me too on my M1.

After this issue I have a arm4 problem when run npx react-native run-ios.
Solved adding arm64 in excluded architectures of the project and pod in Xcode build settings.

Hello! Could you please describe how you did it? ( i'm new to rn )

brew install cocoapods
worked for me like a charm after try every possible solution, I have a M1 2020, hope it helps

Thank you, installing with brew worked for me too on my M1.

After this issue I have a arm4 problem when run npx react-native run-ios.
Solved adding arm64 in excluded architectures of the project and pod in Xcode build settings.

Hello! Could you please describe how you did it? ( i'm new to rn )

I followed this instructions:
https://stackoverflow.com/a/65399525/15801029
If u still have problems, this answer is more complete
https://khushwanttanwar.medium.com/xcode-12-compilation-errors-while-running-with-ios-14-simulators-5731c91326e9

brew install cocoapods
worked for me like a charm after try every possible solution, I have a M1 2020, hope it helps

Thank you, installing with brew worked for me too on my M1.

After this issue I have a arm4 problem when run npx react-native run-ios.
Solved adding arm64 in excluded architectures of the project and pod in Xcode build settings.

Thanks, this worked for me as well on my Mac Pro M1

@xjord not sure if you found it already but it was because of some compiler flags left in some random file, it's in here in some thread somewhere I just don't remember where! Some LLVM flags.

Thanks @lancejpollard, I was able to fix it with git config --global core.autocrlf false. I found out that git config core.autocrlf should be set to false otherwise git checkout will often try to turn LF line endings into CRLF, which can easily break fragile files.

This resolved my issue as well. Thanks so much!

brew install cocoapods
worked for me like a charm after try every possible solution, I have a M1 2020, hope it helps

Worked on M1 Pro 14"

@xjord not sure if you found it already but it was because of some compiler flags left in some random file, it's in here in some thread somewhere I just don't remember where! Some LLVM flags.

Thanks @lancejpollard, I was able to fix it with git config --global core.autocrlf false. I found out that git config core.autocrlf should be set to false otherwise git checkout will often try to turn LF line endings into CRLF, which can easily break fragile files.

Thanks! Fixed for me


Add export cac form submissions option

Issue #: https://github.com/bcgov/met-public/issues/2106
Description of changes:

Add export cac form submissions option in action drop down for superusers and assigned TMs

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of the met-public license (Apache 2.0).

Codecov Report

Merging #2183 (82ba8fa) into main (ef0a68e) will decrease coverage by 0.17%.
Report is 4 commits behind head on main.
The diff coverage is 33.80%.

@@            Coverage Diff             @@
##             main    #2183      +/-   ##
==========================================
- Coverage   68.80%   68.64%   -0.17%
==========================================
  Files         467      467
  Lines       15097    15162      +65
  Branches     1180     1178       -2
==========================================
+ Hits        10388    10408      +20
- Misses       4508     4553      +45
  Partials      201      201

Flag
Coverage Δ

metapi
76.97% <33.80%> (-0.45%)
:arrow_down:

Flags with carried forward coverage won't be shown. Click here to find out more.

Files Changed
Coverage Δ

met-web/src/apiManager/endpoints/index.ts
100.00% <ø> (ø)

.../components/engagement/listing/ActionsDropDown.tsx
60.93% <ø> (-1.75%)
:arrow_down:

met-web/src/services/userService/constants.ts
100.00% <ø> (ø)

...rc/met_api/services/document_generation_service.py
45.61% <3.57%> (-40.60%)
:arrow_down:

met-api/src/met_api/services/cac_form_service.py
45.71% <44.44%> (-1.35%)
:arrow_down:

met-api/src/met_api/resources/cac_form.py
55.81% <52.63%> (-4.19%)
:arrow_down:

met-api/src/met_api/models/cac_form.py
94.44% <66.66%> (-5.56%)
:arrow_down:

met-api/src/met_api/utils/enums.py
100.00% <100.00%> (ø)

met-api/src/met_api/utils/roles.py
100.00% <100.00%> (ø)

... and 1 file with indirect coverage changes


feature-<#5631>-

Description
Creating a spread execution model to execute when spread is desirably small in python.

Related Issue
#5631

Motivation and Context
To provide easy implementation of execution through tight spread to reduce slippage

Requires Documentation Change
Add desciption on this class in "Execution" page

How Has This Been Tested?

Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] Refactor (non-breaking change which improves implementation)
[ ] Performance (non-breaking change which improves performance. Please add associated performance test and results)
[X] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] Non-functional change (xml comments/documentation/etc)

Checklist:

[X] My code follows the code style of this project.
[X] I have read the CONTRIBUTING document.
[ ] I have added tests to cover my changes.
[ ] All new and existing tests passed.
[X] My branch follows the naming convention bug-<issue#>-<description> or feature-<issue#>-<description>

The tests failed by LiveOptionChainFromFuture something like that. It is unrelated to the execution model here itself, I'm confused on passing the tests.


Missing colours in admonitions without JavaScript

Apparently, the light-theme and dark-theme classes are set in JavaScript but the CSS does not have colour variables set without theme being chosen. We should probably define the default colours for just :root.

Thanks. It should be fixed now.