text:
Update docs for textDecorationStyle

This PR fixes the documentation for the textDecorationStyle prop in the Text component documentation.
textDecorationLine and textDecorationStyle were added for Android in https://github.com/facebook/react-native/releases/tag/v0.25.1
Only textDecorationLine was updated at the time https://github.com/facebook/react-native/commit/2039be9d32a52552db02239040bd8e7257bb80f0#diff-8d238dc2c74635b2aaca431551873addL55

By analyzing the blame information on this pull request, we identified @trave7er and @Kudo to be potential reviewers.

Thank you for your pull request and welcome to our community. We require contributors to sign our Contributor License Agreement, and we don't seem to have you on file. In order for us to review and merge your code, please sign up at https://code.facebook.com/cla - and if you have received this in error or have any questions, please drop us a line at cla@fb.com. Thanks!

As far as I can see, textDecorationStyle is still not available on Android. The release notes also no longer mention this.

Hi @javache,
maybe I did not link it but in the 0.27 release it's already in the android examples and in my project using 0.26 it's working :)

Could you link to the native code that implements this?

@javache you are right, I cannot find anything for textDecorationStyle that is like  like the implementation for setTextDecorationLine . And, at the moment,  it's working only the solid value for textDecorationStyle. Sorry about that.


text:
Add post documentation lockdown survey link

We did a survey prior to the doc lockdown to get an idea of what we should focus on. Now we have a yes/no style survey to ensure that we met the user needs when it came to our start of improving the docs.
This diff adds the survey link to the bottom of each page. And we will cherry-pick it into 0.29 as well, which will be the first official release with the new doc content

NOTE: The content via the links in this survey will not be valid until 0.29 is actually released. So I have not enabled the questions for the survey until then.

Test Plan:
http://localhost:8079/react-native/docs/getting-started.html

By analyzing the blame information on this pull request, we identified @Andreyco and @caabernathy to be potential reviewers.

LGTM. Minor nit regarding the use of lockdown but I don't feel too strongly about it.

@hramos Ah - good point. Fixed.

@facebook-github-bot shipit

Something went wrong when importing this pull request. Please cc someone from the team at fb to help with importing this.

@facebook-github-bot shipit

Thanks for importing. If you are an FB employee go to Phabricator to review.

source: gharchive/pull-request

repo: facebook/react-native

license: MIT

license_type: permissive

license_source: github-api


text:
Better syntax error for return foo

Something like "return doesn't exist in Reason; blabla"

What if someone names a function return, as with monads (although that's a terrible name, it's still used)

We could make it a hint, like we’ve done in the past. The hints are 100% accurate but they help give some idea of what caused the problem. Like “did you miss a semicolon” etc

return foo is invalid syntax, not a function

Reason does not need something like this :/

Folks, please read the title. It's to provide better syntax error message when people attempt to do return foo, which is invalid in reason. Right now the error message is <UNKNOWN SYNTAX ERROR>

source: gharchive/issue

authors: bsansouci chenglou mrkaspa ubsan

repo: facebook/reason


text:
Add eval opam config env

I followed the installation instructions, but the rebuild command didn't work - but after running eval opam config env everything worked.

Good catch. One does need to eval opam config env to make new opam configs take effects in the current shell. We should definitely put this instruction in the doc.

The instruction to add opam config env is a few line above (in case you didn't see it)
(Hey again!)

@chenglou I think we need to be explicit that people have to type it in the current shell.

@SanderSpies Could you move the line right below opam switch 4.02.3 ? If someone was using another switch before he switched to 4.02.3, the package pinned below will be pinned to the original switch instead of 4.02.3 unless he types eval opam config env.

@yunxing Will do.
@chenglou (Hey!) Right, my mistake indeed.

authors: SanderSpies chenglou yunxing


text:
Upgrade gh-pages to reflect v1.1.0

This adds an elements screenshot and bumps the version numbers.

looks good (y)

authors: jasta rickbrew

repo: facebook/stetho

license: mit

license_source: bigquery


text:
From React

I am getting this issue:->
ERROR in ./client/index.js
Module build failed: SyntaxError: 'import' and 'export' may only appear at the top level (6:1)
4 |     render components from here
5 | */

6 |  import react from 'react';
|  ^
7 |  import reactDom from 'react-dom';
8 |  import APP from './components/App.js';
9 |  reactDom.render(, document.getElementById('app'));

@ multi main

Please provide the complete code.

I'll close this as it's been a day and it's likely you resolved it.
Effectively, you are not allowed to run any code before an import. They must be first.
Please move any code that is not an import below the imports.

authors: Timer gaearon radhey113

repo: facebookincubator/create-react-app


text:
:art: add first class debugging support

continuation of #1360. re-implemented per code review remarks, and conflicts resolved.  needs 👀 re-review :).
problem statement

react-scripts does not offer ready-to-roll jest debugging.

solution

add it!

closes #594
test

checkout this feature branch
/path/to/this/branch/create-react-app/bin/create-react-app dummy-app
cd dummy-app
modify npm test to add a debug flag ^^
tell your editor to honor source maps
npm test
connect the remote debugger
go.

back at cha

good news!  debugging is working reliably!  good enough where i think we should ship, after any polish requested is applied.
bad news, --inspect* is no bueno.  essentially facebook/jest#1652 prevents us from using JSDom in jest & the inspector protocol simultaneously.  i'm not enough of a jest+JSDOM wizard to figure that out.

the code has been annotated, and --debug-brk still works great :), even in watch mode!

note, jest in watch mode in master is really, painfully slow on OSX for whatever reason.  unrelated to this PR, but woof!

i'm not sure when react-scripts is targeting another release, but i would really like to be able to bump my projects and start debugging asap!  go team ⚽

When can we expect a release including this issue?

BTW, I think the build needs to be kicked started again.  I don't think my pathes are the source of failure. An extra set of :eyes: would be appreciated

@cdaringe I don't want to leave this hanging, but I don't know if we're going to ship this until https://github.com/facebook/jest/issues/1652 is resolved.
I feel very uncomfortable relying on a flag that's already deprecated 😞; are there workarounds we can implement to get inspect working?

I’m going to push this back to 0.11 so we can have the time to figure this out.

@Timer @gaearon,

why is node's flag deprecation a threat?  i don't see any risk here.  we only add value/capability in this PR.  there's zero loss to stakeholders.  we can rev react-scripts later when the jest team gets this sorted out.

i do not think there's a jest hack to make --inspect work in the interim

i'm not sure what more we need to figure out.  there's a known open issue against our dependency stack, but there is a reliable, non-hacky workaround--just limit usage to the older, but well tested & supported protocol.

debug capability, IMHO, is super important, & this is the 2nd time I've implemented it.  i'm not upset, but i do not want to have to do it a 3rd time.  can you speak more to why you feel we shouldn't get this in sooner?

I strongly agree with @cdaringe, this is very important for productivity and one of the worst parts of CRA testing.

I agree, with @cdaringe also.  My team needs this capability as soon as
possible.
On Mon, May 8, 2017, 6:35 PM Caio Balthazar notifications@github.com
wrote:

I strongly agree with @cdaringe https://github.com/cdaringe, this is
very important for productivity and one of the worst parts of CRA testing.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/facebookincubator/create-react-app/pull/2041#issuecomment-300010026,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAgWoPOhKMtJexaWThVfx5D9uuBG-fvlks5r35iUgaJpZM4NLNqS
.

https://github.com/facebook/jest/issues/1652 has been closed with no action taken.

There is nothing Jest can do to fix it. Please express your support for https://github.com/nodejs/node/issues/7593.

At this point we just need somebody to help push this through.
https://github.com/nodejs/node/pull/9272#issuecomment-304365983
Any volunteers?

@cdaringe sorry I didn't respond earlier

why is node's flag deprecation a threat? i don't see any risk here. we only add value/capability in this PR. there's zero loss to stakeholders. we can rev react-scripts later when the jest team gets this sorted out.

It's not so much that it's a threat, but if it becomes something we support, it's turns into our job to maintain that feature going forward.
When Node 8 is released, it is highly likely that --debug will not exist anymore and the only option will be --inspect.
Jest doesn't work with --inspect, so we'd have to tell users to not upgrade their Node versions if they'd like to debug.
This puts us in a bad position because people will expect test debugging to work across all LTS versions of Node (as they should).
IMO, this is plunging us back into the era of JavaScript F***gue where environment matters and tools don't work reliably.
Secondly, Create React App is a toolchain focused at beginners first, but we still consider advanced users and try to accommodate their needs.
Teaching beginners how to debug using a deprecated method and then telling them they have to switch to --inspect (external of our control [based on their environment]) would be painful and cause a potentially poor/confusing experience.

debug capability, IMHO, is super important, & this is the 2nd time I've implemented it. i'm not upset, but i do not want to have to do it a 3rd time.

I'm really sorry that you feel your development efforts are being wasted.
We try really hard to incorporate as many changes as we can and try to ensure developers feel valued. (and we do value your contributions very much, really.)
We will use your work (and not waste it 😄) as a foundation for building out this feature in the future if you are unable to allocate time, but I hope you can understand our position.

I would feel comfortable adding support for --debug if we had a solid timeline and plan for Jest supporting --inspect (which is blocked by Node currently).

I think any effort here should be directed towards unblocking Node. Let's just fix it there.

Just dropping this here, speculation was correct and --debug is dead:
Joes-MacBook-Pro:16s-website joe$ node --debug
(node:70606) [DEP0062] DeprecationWarning: `node --debug` and `node --debug-brk` are invalid. Please use `node --inspect` or `node --inspect-brk` instead.

Really looking forward to https://github.com/nodejs/node/issues/7593 and https://github.com/nodejs/node/pull/9272#issuecomment-304365983 progressing.

Doesn’t seem like anybody wants to take ownership 😞 .

My support hath been cast!

This and various related issues have been open since fall 2016. It seems like debugging is a second class citizen in the react/jest/CRA community? I know some folks think if tests are so complicated you need to debug them, then you are doing it wrong, but I personally think a debugger (with good tests) is one of the most productivity enhancing tools of all times. It would give me great confidence in the react community if debugging was a first-class concern.

We'd really like to implement this feature but Node does not support it. See https://github.com/nodejs/node/issues/7593 and https://github.com/nodejs/node/pull/9272#issuecomment-304365983.
If you can help implement the feature in Node, that'd be great!

@timer can we move forward on this yet now that inspector has been merged in node?

FYI, debugging Jest tests with inspector is now possible as of Node 8.4.0 (https://github.com/nodejs/node/pull/14465).

@jgoz Thank you for mentioning that here! I'll upgrade and try it again. I'm very happy to see this fixed!

This and various related issues have been open since fall 2016. It seems like debugging is a second class citizen in the react/jest/CRA community?

No. We were just as frustrated about this. Unfortunately we lacked the necessary knowledge (knowing C, understanding of how contexts work in Node and V8) to fix this. We are also glad the fix has landed! Sometimes a hard fix is just a hard fix, and not some intentional choice. :-)
I don't understand what you mean about profiles.

Can any provide guidance as to how to debug Jest tests using Node.js 8.4.0? I've so far tried:
npm test -- --inspect-brk

and:
node --inspect-brk node_modules/jest/bin/jest.js -i

with no joy.

Can any provide guidance as to how to debug Jest tests using Node.js 8.4.0? I've so far tried:
npm test -- --inspect-brk

and:
node --inspect-brk node_modules/jest/bin/jest.js -i

with no joy.

@dchambers, see https://github.com/facebookincubator/create-react-app/issues/594#issuecomment-322842515.  make sure you're using version 1.0.11+

Thanks @cdaringe, upgrading 'react-scripts' to 1.0.11 then running ./node_modules/.bin/react-scripts --inspect --inspect-brk test --env=jsdom --runInBand did it for me 🎉

Closing this as support has been added in 1.0.11, thanks for all of your hard work!

Hey all,
I think this is broken.  I'm having issues with debugging my thinks.
Here's repro branch
https://github.com/TheTFo/cria/tree/jest-debug?files=1
Attempt to debug tests from vscode launcher, placing a break point on the line indicated in comment in this file:
https://github.com/TheTFo/cria/blob/jest-debug/src/actions/todoActions.js
Breakpoints don't appear to hit the appropriate lines.  Not sure what's causing it. I don't see transpiled code, just wierd breakpoints hits.

@TheTFo had the same problem. Comment https://github.com/facebookincubator/create-react-app/issues/594#issuecomment-245426594 fixed it for me

authors: TheTFo Timer bgard6977 caiobalthazar cdaringe dchambers gaearon jgoz lifeiscontent valorize


text:
EchoClient and EchoServer unable to establish connection

I can successfully compile the project on Ubuntu. 18.04,but when I run the sample client I get the following error:
vmtest@vmtest-virtual-machine:~/Documents/ietf_quic/mvfst/_build/build/quic/samples$ ./echo -mode=server -host=127.0.0.1 -port=6666 -colorlogtostderr=true -alsologtostderr=true
I0514 08:35:31.092536 28271 EchoServer.h:80] Echo server started at: [::]:6666
vmtest@vmtest-virtual-machine:~/Documents/ietf_quic/mvfst/_build/build/quic/samples$ ./echo -mode=client -host=127.0.0.1 -port=6666 -colorlogtostderr=true -log_dir="/home/vmtest/Documents/ietf_quic/mvfst/_build/build/quic/samples/" -alsologtostderr=true
I0514 08:36:33.769158 28283 EchoClient.h:127] EchoClient connecting to 127.0.0.1:6666
E0514 08:36:33.771145 28283 EchoClient.h:82] EchoClient error: Connect failed
It seems that the handshake method failed. (ClientHandshake::connect() )
What should I do to make the client and server connect successfully?

Can you include the verbose log from both the client and the server?
i.e. ./echo -mode=server -host=127.0.0.1 -port=6666 -colorlogtostderr=true -alsologtostderr=true --v=10

@udippant
vmtest@vmtest-virtual-machine:~/Documents/ietf_quic/mvfst/_build/build/quic/samples$ ./echo -mode=client -host=127.0.0.1 -port=6666 -colorlogtostderr=true -log_dir="/home/vmtest/Documents/ietf_quic/mvfst/_build/build/quic/samples/" -alsologtostderr=true --v=10
I0514 09:01:18.038892 28311 EventBase.cpp:117] EventBase(): Created.
I0514 09:01:18.039906 28312 EventBase.cpp:280] EventBase(): Starting loop.
I0514 09:01:18.040313 28312 QuicClientTransport.cpp:50] client created client CID=b1fbc0e40a8a05dc server CID=None peer address=
I0514 09:01:18.040407 28312 EchoClient.h:127] EchoClient connecting to 127.0.0.1:6666
I0514 09:01:18.041589 28312 StateMachine-inl.h:41] Transition from Uninitialized to ExpectingServerHello
I0514 09:01:18.041658 28312 QuicTransportFunctions.cpp:862] Client writing data using scheduler=CryptoAndAcksScheduler client CID=b1fbc0e40a8a05dc server CID=None peer address=127.0.0.1:6666
I0514 09:01:18.041740 28312 QuicPacketScheduler.cpp:487] Wrote crypto frame offset=0 bytesWritten=234 client CID=b1fbc0e40a8a05dc server CID=None peer address=127.0.0.1:6666
I0514 09:01:18.042423 28312 QuicTransportFunctions.cpp:184] Client sent packetNum=0 in space=InitialSpace size=1255 client CID=b1fbc0e40a8a05dc server CID=None peer address=127.0.0.1:6666
I0514 09:01:18.042490 28312 QuicTransportFunctions.cpp:71] Client sent packetNum=0 space=InitialSpace client CID=b1fbc0e40a8a05dc server CID=None peer address=127.0.0.1:6666
I0514 09:01:18.042683 28312 QuicTransportFunctions.cpp:559] Client written crypto and acks data type=Initial packets=1 client CID=b1fbc0e40a8a05dc server CID=None peer address=127.0.0.1:6666
I0514 09:01:18.042752 28312 QuicLossFunctions.h:189] setLossDetectionAlarm setting transmission alarm=99ms method=Handshake outstanding=1 handshakePackets=1 pureAckPackets=0 Client client CID=b1fbc0e40a8a05dc server CID=None peer address=127.0.0.1:6666
I0514 09:01:18.042807 28312 QuicTransportBase.cpp:1974] schedulePathValidationTimeout cancel timeout client CID=b1fbc0e40a8a05dc server CID=None peer address=127.0.0.1:6666
I0514 09:01:18.042855 28312 QuicTransportBase.cpp:1038] Client stopping write looper client CID=b1fbc0e40a8a05dc server CID=None peer address=127.0.0.1:6666
I0514 09:01:18.042981 28312 AsyncUDPSocket.cpp:491] AsyncSocket::handleErrMessages(): recvmsg returned 1
I0514 09:01:18.043046 28312 AsyncUDPSocket.cpp:491] AsyncSocket::handleErrMessages(): recvmsg returned -1
I0514 09:01:18.043131 28312 QuicTransportBase.cpp:274] Stopping read looper due to immediate close client CID=b1fbc0e40a8a05dc server CID=None peer address=127.0.0.1:6666
I0514 09:01:18.043187 28312 QuicTransportBase.cpp:692] Stopping read looper client CID=b1fbc0e40a8a05dc server CID=None peer address=127.0.0.1:6666
I0514 09:01:18.043282 28312 QuicTransportBase.cpp:1000] Stopping peek looper client CID=b1fbc0e40a8a05dc server CID=None peer address=127.0.0.1:6666
I0514 09:01:18.043331 28312 QuicTransportBase.cpp:1025] Client stopping write looper because conn closed client CID=b1fbc0e40a8a05dc server CID=None peer address=127.0.0.1:6666
E0514 09:01:18.043413 28312 EchoClient.h:82] EchoClient error: Connect failed

I was able to reproduce this as well with the echo client / server examples:
./echo -mode=client -host=127.0.0.1 -port=6666 -colorlogtostderr=true -log_dir="/home/agnosticdev/Documents/code/cpp/mvfast/_build/build/quic/samples/logs" -alsologtostderr=true

./echo -mode=server -host=127.0.0.1 -port=6666 -colorlogtostderr=true -alsologtostderr=true --v=10

I0513 21:20:21.171392 14234 EchoServer.h:80] Echo server started at: [::]:6666
I0513 21:20:21.171388 14241 QuicServerWorker.cpp:69] Registered read on worker=0x55fb000d74f0 thread=139644201064192 processId=0
I0513 21:20:21.171394 14240 QuicServerWorker.cpp:69] Registered read on worker=0x55fb000d7210 thread=139644209456896 processId=0
I0513 21:20:21.171360 14236 QuicServerWorker.cpp:69] Registered read on worker=0x55fb000d6680 thread=139644450768640 processId=0
I0513 21:20:21.171360 14237 QuicServerWorker.cpp:69] Registered read on worker=0x55fb000d6960 thread=139644442375936 processId=0
I0513 21:20:21.171406 14242 QuicServerWorker.cpp:69] Registered read on worker=0x55fb000d77d0 thread=139644192671488 processId=0
I0513 21:20:21.171408 14234 EventBase.cpp:280] EventBase(): Starting loop.
I0513 21:20:21.171394 14238 QuicServerWorker.cpp:69] Registered read on worker=0x55fb000d6c20 thread=139644433983232 processId=0

It looks like after resumeRead() calls out to AsyncUDPSocket and nothing else is recorded after that.
void QuicServerWorker::start() {
  CHECK(socket_);
  if (transportSettings_.pacingEnabled && !pacingTimer_) {
    pacingTimer_ = TimerHighRes::newTimer(
        evb_, transportSettings_.pacingTimerTickInterval);
  }
  socket_->resumeRead(this);
  VLOG(10) << "Registered read on worker=" << this
           << " thread=" << folly::getCurrentThreadID()
           << " processId=" << (int)processId_;
}

void AsyncUDPSocket::resumeRead(ReadCallback* cob) {
  CHECK(!readCallback_) << "Another read callback already installed";
  CHECK_NE(NetworkSocket(), fd_)
      << "UDP server socket not yet bind to an address";

  readCallback_ = CHECK_NOTNULL(cob);
  if (!updateRegistration()) {
    AsyncSocketException ex(
        AsyncSocketException::NOT_OPEN, "failed to register for accept events");

    readCallback_ = nullptr;
    cob->onReadError(ex);
    return;
  }
}

Will keep digging.

there looks to be something off with bind. can you try remove the —client and —server arguments from your commands?

@lnicco

After updating the commands to:
Echo Server: ./echo --v=10
Echo Client: ./echo -mode=client --v=10
I am now able to see data being echoed on the server side:
I0514 05:09:48.316179 25235 QuicTransportBase.cpp:1143] Delivered eof to app for stream=0 client CID=db2ee4d1754f2aa7 server CID=400001db90af82c7 peer address=[::1]:51044
I0514 05:09:48.316190 25235 QuicTransportBase.cpp:717] Stopping read looper client CID=db2ee4d1754f2aa7 server CID=400001db90af82c7 peer address=[::1]:51044
I0514 05:09:48.316202 25235 QuicTransportBase.cpp:1023] Stopping peek looper client CID=db2ee4d1754f2aa7 server CID=400001db90af82c7 peer address=[::1]:51044
I0514 05:09:48.316215 25235 QuicTransportBase.cpp:1043] Server stopping write looper client CID=db2ee4d1754f2aa7 server CID=400001db90af82c7 peer address=[::1]:51044
I0514 05:09:48.316227 25235 EchoHandler.h:73] Got len=5 eof=1 total=5 **data=mvfst**
I0514 05:09:48.316241 25235 QuicTransportBase.cpp:1038] Server running write looper thisIteration=1 client CID=db2ee4d1754f2aa7 server CID=400001db90af82c7 peer address=[::1]:51044
I0514 05:09:48.316254 25235 QuicTransportBase.cpp:717] Stopping read looper client CID=db2ee4d1754f2aa7 server CID=400001db90af82c7 peer address=[::1]:51044
I0514 05:09:48.316267 25235 QuicTransportBase.cpp:1038] Server running write looper thisIteration=1 client CID=db2ee4d1754f2aa7 server CID=400001db90af82c7 peer address=[::1]:51044
I0514 05:09:48.316282 25235 QuicTransportFunctions.cpp:865] Server writing data using scheduler=FrameScheduler client CID=db2ee4d1754f2aa7 server CID=400001db90af82c7 peer address=[::1]:51044
I0514 05:09:48.316308 25235 QuicWriteCodec.cpp:118] writing frame stream=0 offset=0 data=10 fin=1

Client:
b90af82c7 peer address=[::1]:6666
I0514 05:09:41.108058 25237 QuicTransportBase.cpp:1979] schedulePathValidationTimeout cancel timeout client CID=db2ee4d1754f2aa7 server CID=400001db90af82c7 peer address=[::1]:6666
I0514 05:09:41.108064 25237 QuicTransportBase.cpp:717] Stopping read looper client CID=db2ee4d1754f2aa7 server CID=400001db90af82c7 peer address=[::1]:6666
I0514 05:09:41.108070 25237 QuicTransportBase.cpp:1023] Stopping peek looper client CID=db2ee4d1754f2aa7 server CID=400001db90af82c7 peer address=[::1]:6666
I0514 05:09:41.108076 25237 QuicTransportBase.cpp:1043] Client stopping write looper client CID=db2ee4d1754f2aa7 server CID=400001db90af82c7 peer address=[::1]:6666
mvfst
I0514 05:09:48.315528 25237 QuicTransportBase.cpp:581] Setting setReadCallback for stream=0 cb=0x7ffcd4996c48 client CID=db2ee4d1754f2aa7 server CID=400001db90af82c7 peer address=[::1]:6666
I0514 05:09:48.315577 25237 QuicTransportBase.cpp:717] Stopping read looper client CID=db2ee4d1754f2aa7 server CID=400001db90af82c7 peer address=[::1]:6666
I0514 05:09:48.315599 25237 QuicTransportBase.cpp:1038] Client running write looper thisIteration=1 client CID=db2ee4d1754f2aa7 server CID=400001db90af82c7 peer address=[::1]:6666
I0514 05:09:48.315615 25237 **EchoClient.h:167] EchoClient wrote "mvfst", len=5 on stream=0**
I0514 05:09:48.315644 25237 QuicTransportFunctions.cpp:865] Client writing data using scheduler=FrameSchedulerWithoutCrypto client CID=db2ee4d1754f2aa7 server CID=400001db90af82c7 peer address=[::1]:6666
I0514 05:09:48.315671 25237 QuicWriteCodec.cpp:118] writing frame stream=0 offset=0 data=5 fin=1

Do you want me to put a PR up to switch the echo example on the README?

I have a feeling like it’s something wrong with the binding to the v4 interface on the host. By default we bind to the v6 localhost which is ::1.
Ya please feel free to put up a pr to fix it to v6 localhost.

Ahh, yes.  I see it now. It looks like the client() takes the FLAGS_host argument while the server is started with just FLAGS_port and FLAGS_port, so the server is then by default binding to ::1.  Thank you!
if (FLAGS_mode == "server") {
  EchoServer server(FLAGS_port, FLAGS_port);
  server.start();
} else if (FLAGS_mode == "client") {
  if (FLAGS_host.empty() || FLAGS_port == 0) {
    LOG(ERROR) << "EchoClient expected --host and --port";
    return -2;
  }
  EchoClient client(FLAGS_host, FLAGS_port, FLAGS_pr);
  client.start();
} else {
  LOG(ERROR) << "Unknown mode specified: " << FLAGS_mode;
  return -1;
}

The update above does include passing in a IPv4 or IPv6 host argument to the echo server as well as a README fix.

Addressed on https://github.com/facebookincubator/mvfst/pull/13

authors: DavidWangW agnosticdev lnicco siyengar udippant

repo: facebookincubator/mvfst


text:
Remove the BloomFilter classes from dwio/parquet/writer/arrow/tests/

Description
The classes were moved from Arrow Parquet writer to dwio/parquet/common in "Move arrow parquet bloom filter code to velox dwio (#10516)", but there is still another copy in velox/dwio/parquet/writer/arrow/tests/. The references in velox/dwio/parquet/writer/arrow/tests/ shall be updated to the ones in dwio/parquet/common

cc @pedroerp @nmahadevuni

repo: facebookincubator/velox


text:
Update Types documentation

Update Decimal and Interval Day to Second type documentation since they
are now logical types.
Add documentation for Presto Types.

@mbasmanova I addressed your comments. Can you make another pass? Thanks.

I added a note for OPAQUE and UNKNOWN types as well.

@mbasmanova thank you for your feedback. I addressed all of them.


text:
Add ContainerRowSerde::compareWithNulls API for ByteStream compare

Presto aggregate functions that compare values of complex types must detect
cases when complex values contain nulls. The new
ContainerRowSerde::compareWithNulls API allows signaling the case when a complex
type value contains a null when comparing ByteStream with ByteStream.
Similar to https://github.com/facebookincubator/velox/pull/6419.

I'm getting Diff too old error. Would you rebase?

I'm getting Diff too old error. Would you rebase?

@mbasmanova Got it, done.

@duanmeng Thanks.

authors: duanmeng mbasmanova


text:
Train models config directory path

Shouldn't the model config path in the configs table in the README.md Training models section contain model_configs directory as shown below?

Model
Config directory

ANS(rgb)
configs/model_configs/ans_rgb

ANS(depth)
configs/model_configs/ans_depth

OccAnt(rgb)
configs/model_configs/occant_rgb

OccAnt(depth)
configs/model_configs/occant_depth

OccAnt(rgbd)
configs/model_configs/occant_rgbd

OccAnt(GT)
configs/model_configs/occant_ground_truth

The pre-models that are available do not obey this directory structure. The above was just an indication pointing to sample config files for each model. In each case, the paths for the following must be changed based on the user's needs:
TENSORBOARD_DIR
EVAL_CKPT_PATH_DIR
VIDEO_DIR
CHECKPOINT_FOLDER

Got it.
In my humble opinion, it's a bit confusing because we have the configs directory in the project root.
And I initially thought that the path is specified relative to the configs directory.
Maybe it would be better to add some explanation and angle brackets around config like this

Model
Config directory

ANS(rgb)
<configs>/ans_rgb

ANS(depth)
<configs>/ans_depth

OccAnt(rgb)
<configs>/occant_rgb

OccAnt(depth)
<configs>/occant_depth

OccAnt(rgbd)
<configs>/occant_rgbd

OccAnt(GT)
<configs>/occant_ground_truth

where <config> is an indication pointing to sample config files for each model.

All paths in the repo are relative the main directory. So, the paths specified are valid paths for example config files. Is it an issue with the pre-trained models?

No no, I just got confused, because the paths specified in the Config directory column don't exist.
For example, there is a configs directory in the project root, but the path configs/ans_rgb doesn't exist (but the path configs/model_configs/ans_rgb does exist).
That's why I suggested either change it to the correct path or to add an explanation that the config is an indication pointing to sample config files for each model.

Oh, got it. The model_configs was missing. Yes, I will fix this in my next update. Thanks!

repo: facebookresearch/OccupancyAnticipation


text:
Where is fairseq-preprocess

When I run following command in the shell script
for input_index in $(seq 1 2); do
  fairseq-preprocess \
      --only-source \
      --trainpref $processed_data_dir/train.${input_index}.bpe \
      --validpref $processed_data_dir/dev.${input_index}.bpe \
      --testpref $processed_data_dir/test.${input_index}.bpe \
      --destdir $processed_data_dir/Input.${input_index} \
      --workers 4 \
      --srcdict ${roberta_vocab_dir}/dict.txt
done

There is an issue that command not found
fairseq-preprocess: command not found

You need to run “pip install --editable .” to install the fairseq-preprocess executable.

sorry, from which directory shall I run “pip install --editable .” ?

You need to run “pip install --editable .” to install the fairseq-preprocess executable.

@myleott
Even after running this and having fairseq successfully installed the fairseq-preprocess is not found

@Skylixia Were you able to fix this?

authors: Skylixia chengfx myleott nonononanana yarakhater

repo: facebookresearch/fairseq


text:
accessing build/viewer

❓ Questions and Help
How does one access build/viewer code? It does not seem to be on GitHub.

Just pass -DBUILD_GUI_VIEWERS=ON to CMake.

Forgive me, but how is CMake involved? I know it it a dependency, but I have installed it without specifically in invoking it.

How does one access build/viewer code

Is this what you are looking for: https://github.com/facebookresearch/habitat-sim/blob/master/src/utils/viewer/viewer.cpp?

How to build this viewer as it is already not there in build folder?

You'll need to build habitat-sim for a system with display as described here: https://github.com/facebookresearch/habitat-sim/blob/master/BUILD_FROM_SOURCE.md (i.e., do not include the --headless argument).

Hii @aclegg3 thank you for response , I installed habitat-sim using the same .But, still got error as :
./build/viewer no such file or directory exists.

@KenaHemnani then we'll need more info from your build before we can move forward. You should see an alias to viewer in the habitat-sim/build directory and a habitat-sim/utils/viewer/ directory containing the viewer application.

Hii @aclegg3 I reinstalled habitat-sim using conda . The headless version is working fine , but with display I am not able to visualize even with VNC , Yes I do have habitat-viewer inside habitat-sim/utils/viewer/ directory .So, I run following command
./habitat-viewer ~/DIR/habitat-lab/data/scene_datasets/hitat-test-scenes/skokloster-castle.glb
It shows following `error:

Is there any other way to visualize the performance of agents as how it is navigating inside 3D habitat environment? locally on small dataset.
`

repo: facebookresearch/habitat-sim


text:
--[BE][WIP] - Dataset Diagnostics and Attributes Deduplication

Motivation and Context
This PR introduces a transparent dataset diagnostics protocol that can be controlled by setting flags using the optional tag "request_diagnostics" placed in the scene dataset config, followed by either an individual string or a list of strings, each specifying a desired diagnostic to be performed.
As a proof of concept, as well as to address an existing issue with the base hssd scene instances, the following tags are currently supported :

SaveCorrected : save any files that have been tested and corrected. Ignored if no tests specified
TestForSceneInstanceDuplicates : test for duplicate rigid/articulated object instances on scene instance load, not loading duplicates if found.
TestForSemanticRegionDuplicates : test for duplicate semantic region definitions on semantic attributes load, not loading duplicates if found.

This PR will perform conditional de-duplication of any loaded subconfiguration, such as Object Instances from the Scene Instance configuration file, if the appropriate test (TestForSceneInstanceDuplicates) is requested.  If multiple such object instances are loaded that have identical data, then the extra duplicates will not be saved as part of the internal representation of the scene instance.
If SaveCorrected is specified, the scene instance, in this case, minus the extra duplicates, will be saved to disk. Otherwise, it will just be retained in memory for the lifetime of the execution.
This functionality is also available for SemanticAttributes/configs, should identical SemanticRegion definitions exist within the original json config description.
This PR is currently set up to prevent any duplicate SceneObjectInstanceAttributes or SceneAOInstanceAttributes from being saved when a SceneInstanceAttributes is being created for manual save to disk.
This PR also includes a renaming refactor for attributes and attributes manager base classes to fall in line with standard naming protocol and be less confusing.
Still needed :

Actually saving the modified attributes if the diagnostics indicate it and the user requested saving.
Tests

How Has This Been Tested
Locally c++ and python tests pass (currently transparent pass-through)

Types of changes

[x] Docs change / refactoring / dependency upgrade
[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist

[x] My code follows the code style of this project.
[x] My change requires a change to the documentation.
[x] I have updated the documentation accordingly.
[x] I have read the CONTRIBUTING document.
[x] I have completed my CLA (see CONTRIBUTING)
[ ] I have added tests to cover my changes.
[x] All new and existing tests passed.

So currently to request a diagnostic, say on duplicate scene object instances, you would add the following line to the scene dataset config :
"request_diagnostics":"TestForSceneInstanceDuplicates",
or
"request_diagnostics":["TestForSceneInstanceDuplicates"],
if you wanted to save the scene instances that were corrected by the diagnostic process,  you would use
"request_diagnostics":["TestForSceneInstanceDuplicates", "SaveCorrected"],
and when you do not wish for any diagnostics anymore, you would just delete the line from the scene dataset config.
Other mechanisms for performing these diagnostics would be easy to implement, this was just the mechanism I started with.


text:
Problems opening GUI

Does anyone know how to open gui for the ovmm?

Hey this is the script for GUI: https://github.com/facebookresearch/habitat-lab/blob/ovmm_v0.2.5/examples/interactive_play.py.

repo: facebookresearch/home-robot


text:
Reduce the training loss

❓ Questions and Help
Is it necessary to reduce the training losses through multiple processes in trainer.py?
I think current reduction on losses only work for logging instead of backward.
Could anyone explain about which parts of codes average the gradients from all processes when doing distributed training?

The reduction in the losses is indeed only needed for logging purposes, and not for training.
The gradient averaging is handled by DistributedDataParallel, and is done automatically for us when we call .backward.
I'm closing this issue as I believe I have answered your question, but let me know if something isn't clear.

authors: Jiayuan-Gu fmassa

repo: facebookresearch/maskrcnn-benchmark


text:
Where is envs buffers?

I encounter a problem when trying to find the JSON files of all the visdom envs.
First of all, I can not find where the visdom server save all the envs buffer path. I use buffer path" referring to the path where all the unsaved envs  are kept. This buffer seems to be automatically cleared when the visdom server is shut down. However I need to find and use it when the server is still on.
Its path is definitely not "~/.visdom", and I would like to know where it is
The other thing is that I need to save some of the good envs and reload them freely. So far, the save button can save the envs file to "~/.visdom", but I can not find anyway to use these JSON files other than simply reboot the server.
How can I use another server (That say new IP new port) to load all the JSON file I pick(I would get the file from save button and move them elsewhere) from any path I set?

This 'buffer' is entirely in the server's python local memory in self.state[eid], it doesn't exist as a file. Hard saves are the only thing that push data to a file.
For the latter question you can move the files to a different folder and start the server with the -env_path <directory> option to point to that folder.

@JackUrb Thanks~ This is what we are doing now. ^_^

repo: facebookresearch/visdom


text:
Even better upgrades to playground

Allow loading notebook pages
Add spinner to show pyodide is loading and/or working

@gir-bot lgtm

repo: facelessuser/coloraide


text:
🛑 fiscaliadeestado.misiones.gob.ar is down

In 6fc729e, fiscaliadeestado.misiones.gob.ar (https://fiscaliadeestado.misiones.gob.ar/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: fiscaliadeestado.misiones.gob.ar is back up in 3751ec0.


text:
🛑 htc.misiones.gob.ar is down

In 83a7531, htc.misiones.gob.ar (https://htc.misiones.gob.ar/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: htc.misiones.gob.ar is back up in 4bd7cdc.


text:
test: update tests for wasmhooks

Notes
update simapp and tests to be compatible with sdk 50, and make all tests pass
Tests pass

@faddat hey, i'm implementing ibc-hooks for eve, and since there is no completed version of ibc-hooks v8, i will continue working on your branch

@faddat hi sir, tests and lint passed, please review this PR

thank you!

repo: faddat/ibc-apps


text:
Add authorization token to be allowed to access the backend

Change endPoint to Access to platform backend to get dynamic projects list
Proposed Changes

Add endPiont to evirioment
Add header to include valid token to access
Get project list from server

Pull request checklist
Please check if your PR fulfills the following requirements:

[ ] Tests
[x] Build locally
[ ] Code format / lint
[ ] Docs have been reviewed and added

Pull request type
Please check the type of change your PR introduces:

[ ] Bugfix
[x] Feature
[ ] Code style update (formatting, renaming)
[ ] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[ ] Documentation content changes
[ ] Other (please describe):

What is the current behavior?

Issue Number: N/A
The sistem access to backend to get the list of project available using a valid token

Fixes #81
What is the new behavior?

Does this introduce a breaking change?

[ ] Yes
[x] No

Other information

Be careful with the blank spaces in the checkbox of the PR.  Try to put labels, use the issue in the Kanban project and assign the PR to someone

authors: carloscaverobarca miquinti


text:
Issues while fetching data, latest and previous fdp-storage versions

When I'm fetching  / downloading
 // read directory
    const items = await this.fdp.directory.read(
      TODOS_NAMESPACE,
      `/${TODOS_PATH}`
    );

  // only add new todos
    for (const i in items.content) {
      if (!this.todos.find((t) => t.id === i.split(`.`)[1])) {
        const data = await this.fdp.file.downloadData(
          TODOS_NAMESPACE,
          `/${TODOS_PATH}/${(i as any).name}`
        );
      // fails with "Data not found"

        const payload = new TextDecoder().decode(data.buffer);
        const obj = JSON.parse(payload);
        this.todos.push(obj);
      }
    }

I get the following error in Chrome
vue.runtime.esm.js?c320:3020 Error: Data not found
    at t.lookup (index.browser.min.js?fb75:2:1)
    at async t.getRawMetadata (index.browser.min.js?fb75:2:1)
    at async s (index.browser.min.js?fb75:2:1)
    at async t.downloadData (index.browser.min.js?fb75:2:1)
    at async VueComponent.loadItems (App.vue?38a5:107:1)

This is in the supertodos repository

developers should use async/await

authors: molekilla tfius

repo: fairDataSociety/fdp-storage


text:
[sway systemd setup] unable to re-login after exiting sway

Hello,
thank you for making this beautiful display manager!
OS: manjaro with latest linux55 kernel
$ sway --version
sway version 1.4

wlroots version 0.10.1-1

ly version: installed via yay -S ly-git  v0.5.0.r9.gaa25ede-1
When trying to logout and then re-login with sway I see the following errors:

Click to expand!
Apr 28 14:53:59 teutates-laptop ly[657]: gkr-pam: unable to locate daemon control file
Apr 28 14:53:59 teutates-laptop audit[657]: USER_AUTH pid=657 uid=0 auid=1000 ses=1 msg='op=PAM:authentication grantors=pam_securetty,pam_tally2,p>
Apr 28 14:53:59 teutates-laptop ly[657]: gkr-pam: stashed password to try later in open session
Apr 28 14:53:59 teutates-laptop audit[657]: USER_ACCT pid=657 uid=0 auid=1000 ses=1 msg='op=PAM:accounting grantors=pam_tally2,pam_access,pam_unix>
Apr 28 14:53:59 teutates-laptop audit[657]: CRED_ACQ pid=657 uid=0 auid=1000 ses=1 msg='op=PAM:setcred grantors=pam_securetty,pam_tally2,pam_shell>
Apr 28 14:53:59 teutates-laptop ly[657]: pam_unix(ly:session): session opened for user teutates by (uid=0)
Apr 28 14:53:59 teutates-laptop ly[657]: gkr-pam: unable to locate daemon control file
Apr 28 14:53:59 teutates-laptop ly[657]: gkr-pam: gnome-keyring-daemon started properly and unlocked keyring
Apr 28 14:53:59 teutates-laptop audit[657]: USER_START pid=657 uid=0 auid=1000 ses=1 msg='op=PAM:session_open grantors=pam_loginuid,pam_keyinit,pa>
Apr 28 14:53:59 teutates-laptop systemd[1037]: Started sway - SirCmpwn's Wayland window manager.
Apr 28 14:53:59 teutates-laptop sway[63955]: 2020-04-28 14:53:59 - [sway/main.c:152] Linux teutates-laptop 5.5.19-1-MANJARO #1 SMP PREEMPT Tue>
Apr 28 14:53:59 teutates-laptop sway[63955]: 2020-04-28 14:53:59 - [sway/main.c:168] Contents of /etc/lsb-release:
Apr 28 14:53:59 teutates-laptop sway[63955]: 2020-04-28 14:53:59 - [sway/main.c:152] DISTRIB_ID=ManjaroLinux
Apr 28 14:53:59 teutates-laptop sway[63955]: 2020-04-28 14:53:59 - [sway/main.c:152] DISTRIB_RELEASE=20.0
Apr 28 14:53:59 teutates-laptop sway[63955]: 2020-04-28 14:53:59 - [sway/main.c:152] DISTRIB_CODENAME=Lysia
Apr 28 14:53:59 teutates-laptop sway[63955]: 2020-04-28 14:53:59 - [sway/main.c:152] DISTRIB_DESCRIPTION="Manjaro Linux"
Apr 28 14:53:59 teutates-laptop sway[63955]: 2020-04-28 14:53:59 - [sway/main.c:168] Contents of /etc/os-release:
Apr 28 14:53:59 teutates-laptop sway[63955]: 2020-04-28 14:53:59 - [sway/main.c:152] NAME="Manjaro Linux"
Apr 28 14:53:59 teutates-laptop sway[63955]: 2020-04-28 14:53:59 - [sway/main.c:152] ID=manjaro
Apr 28 14:53:59 teutates-laptop sway[63955]: 2020-04-28 14:53:59 - [sway/main.c:152] ID_LIKE=arch
Apr 28 14:53:59 teutates-laptop sway[63955]: 2020-04-28 14:53:59 - [sway/main.c:152] PRETTY_NAME="Manjaro Linux"
Apr 28 14:53:59 teutates-laptop sway[63955]: 2020-04-28 14:53:59 - [sway/main.c:152] ANSI_COLOR="1;32"
Apr 28 14:53:59 teutates-laptop sway[63955]: 2020-04-28 14:53:59 - [sway/main.c:152] HOME_URL="https://www.manjaro.org/"
Apr 28 14:53:59 teutates-laptop sway[63955]: 2020-04-28 14:53:59 - [sway/main.c:152] SUPPORT_URL="https://www.manjaro.org/"
Apr 28 14:53:59 teutates-laptop sway[63955]: 2020-04-28 14:53:59 - [sway/main.c:152] BUG_REPORT_URL="https://bugs.manjaro.org/"
Apr 28 14:53:59 teutates-laptop sway[63955]: 2020-04-28 14:53:59 - [sway/main.c:152] LOGO=manjarolinux
Apr 28 14:53:59 teutates-laptop sway[63955]: 2020-04-28 14:53:59 - [sway/main.c:140] LD_LIBRARY_PATH=(null)
Apr 28 14:53:59 teutates-laptop sway[63955]: 2020-04-28 14:53:59 - [sway/main.c:140] LD_PRELOAD=(null)
Apr 28 14:53:59 teutates-laptop sway[63955]: 2020-04-28 14:53:59 - [sway/main.c:140] PATH=/home/teutates/.local/bin:/sbin:/bin:/usr/local/sbin:/us>
Apr 28 14:53:59 teutates-laptop sway[63955]: 2020-04-28 14:53:59 - [sway/main.c:140] SWAYSOCK=/run/user/1000/sway-ipc.1000.1062.sock
Apr 28 14:53:59 teutates-laptop sway[63955]: 2020-04-28 14:53:59 - [sway/server.c:40] Preparing Wayland server initialization
Apr 28 14:53:59 teutates-laptop sway[63955]: 2020-04-28 14:53:59 - [backend/wayland/backend.c:255] Creating wayland backend
Apr 28 14:53:59 teutates-laptop sway[63955]: 2020-04-28 14:53:59 - [backend/wayland/backend.c:271] Could not connect to remote display: No such fi>
Apr 28 14:53:59 teutates-laptop sway[63955]: 2020-04-28 14:53:59 - [backend/noop/backend.c:51] Creating noop backend
Apr 28 14:53:59 teutates-laptop sway[63955]: 2020-04-28 14:53:59 - [sway/server.c:47] Unable to create backend
Apr 28 14:53:59 teutates-laptop systemd[1037]: sway.service: Main process exited, code=exited, status=1/FAILURE
Apr 28 14:53:59 teutates-laptop systemd[1037]: sway.service: Failed with result 'exit-code'.
Apr 28 14:53:59 teutates-laptop ly[657]: pam_unix(ly:session): session closed for user teutates
Apr 28 14:53:59 teutates-laptop audit[657]: USER_END pid=657 uid=0 auid=1000 ses=1 msg='op=PAM:session_close grantors=pam_loginuid,pam_keyinit,pam>
Apr 28 14:53:59 teutates-laptop audit[657]: CRED_DISP pid=657 uid=0 auid=1000 ses=1 msg='op=PAM:setcred grantors=pam_securetty,pam_tally2,pam_shel

Steps to reproduce:

I have setup sway to start with systemd as described in the sway wiki (follow the whole page, also setup sway itself as a --user service)
setup ly as a systemd service as well
exit sway with swaymsg exit
get logged out and redirected correctly to ly
try to login again: ly seems to refresh itself and does not open sway. in the logs the mentioned error messsages show up

Expected:

ly should start a new sway session successfully.

I am very curious if this is reproducable for others and would be happy to provide more debugging info as needed.

I cannot reproduce with Sway 1.5 on Arch Linux, but I'm not running Sway as a systemd service.

Consider trying the sway-services project instead, available as sway-services-git package in the Arch Linux AUR.
One thing it does is to clean up some environment variables set by Sway upon exit. Perhaps if these are not unset it could cause a problem upon re-login:
https://github.com/xdbob/sway-services/blob/master/bin/sway-user-service
You see the sway.service file also contains code to clean-up environment vars:
https://github.com/xdbob/sway-services/blob/5ccb33b92c78a0b95216b3c3470d0d45e76cea2c/systemd/sway.service

Consider trying the sway-services project instead, available as sway-services-git package in the Arch Linux AUR.
One thing it does is to clean up some environment variables set by Sway upon exit. Perhaps if these are not unset it could cause a problem upon re-login:
https://github.com/xdbob/sway-services/blob/master/bin/sway-user-service
You see the sway.service file also contains code to clean-up environment vars:
https://github.com/xdbob/sway-services/blob/5ccb33b92c78a0b95216b3c3470d0d45e76cea2c/systemd/sway.service

Thank you @markstos, I'll definitely check that out and report back how it goes.

Thank you @markstos, I'll definitely check that out and report back how it goes.

Nice! This little detail in sway.service does the trick:
https://github.com/xdbob/sway-services/blob/eab69fa5253ad494921833e46b6476d7bf675ed4/systemd/sway.service#L19
ExecStopPost=/usr/bin/systemctl --user unset-environment SWAYSOCK DISPLAY I3SOCK WAYLAND_DISPLAY

Nice! This little detail in sway.service does the trick:
https://github.com/xdbob/sway-services/blob/eab69fa5253ad494921833e46b6476d7bf675ed4/systemd/sway.service#L19
ExecStopPost=/usr/bin/systemctl --user unset-environment SWAYSOCK DISPLAY I3SOCK WAYLAND_DISPLAY

There seems to be an similiar issue with River WM

authors: kardwen markstos teutat3s

repo: fairyglade/ly

license: WTFPL


text:
fal installation instructions with dbt 1.0

Trying fal now after a recommendation through Slack. I installed dbt 1.0 by pip install dbt-core, as well as fal by pip install fal.
I ran into a few snags when installing fal in a clean python 3.9 environment, and it might be worth adding a note about dbt 1.0 to the fal readme.

fal currently doesn't install dbt. I assume this is because of the change from dbt to dbt-core.
fal relies on bigquery here, which means that one needs to run pip install dbt-bigquery. This should be explicitly stated on the readme, and preferably not be a requirement.

For the second point, it would be much better to use:
from dbt.adapters.factory import load_plugin
load_plugin("bigquery") # returns dbt.adapters.bigquery.connections.BigQueryCredentials

Hi @thomasaarholt! Thanks for raising this issue. We are actively working on supporting dbt 1.0 (see #69) and should release the new version soon. You're right, we should add a note about dbt 1.0 in README.

Ah! I searched for 1.0 and didn't find the PR (I had to type 1.0.0...) :)

My bigquery fix above works on 0.20 as well, I just checked:

Should I make a PR?

Ah, I see you have a fix as well in the 1.0.0 PR :) I'll leave that to you!

@thomasaarholt, we have just released a version compatible with dbt 1.0.0.
pip install fal==0.1.35

Please let us know how it goes and if anything else comes up!

repo: fal-ai/fal


text:
Driverkit Debian/Ubuntu builder wrong kernel version

Describe the bug
Basically, kernel-crawler kernels list is exporting fields like:
"kernelrelease": "5.10.103-1-amd64",

(https://github.com/falcosecurity/kernel-crawler/blob/main/kernels/x86_64/list.json#L7368),
whose url is http://security.debian.org/pool/updates/main/l/linux/linux-headers-5.10.0-12-amd64_5.10.103-1_amd64.deb
But Driverkit is reading those as 5.10.0-12 kernelversion instead, using a regex that expects:
href="(linux-headers-5\.10\.103-1-(amd64)_.*(amd64|all)\.deb)"

This means that running driverkit with:
driverkit docker --output-module /tmp/falco.ko --kernelversion=1 --kernelrelease=5.10.103-1-amd64 --target=debian
will fail, because it expects 5.10.0-12 kernelrelease.
Fact is, kernel-crawler is right because it is using packages metadata, eg  (notice the Version line):
Package: linux-headers-5.10.0-12-common
Source: linux
Version: 5.10.103-1
Installed-Size: 51854
Maintainer: Debian Kernel Team <debian-kernel@lists.debian.org>
Architecture: all
Description: Common header files for Linux 5.10.0-12
Homepage: https://www.kernel.org/
Description-md5: ab592fb1c299fa53a862c8eecd4486e6
Multi-Arch: foreign
Section: kernel
Priority: optional
Filename: pool/updates/main/l/linux/linux-headers-5.10.0-12-common_5.10.103-1_all.deb
Size: 8940952
SHA256: 9753625d0256066b37dd92d55621ebb5a76c3a9e6c2579607531b0809f6b3552

Of course, changing the way driverkit behaves would break every existing config.
I am not sure whether "breaking" kernel-crawler to match driverkit output would be a good idea.
I can try to add a new parameter to driverkit configs header_urls[], that when set, would force certain headers instead of trying to fetch the correct one programmatically.
Moreover, i could even try to double the matching pattern, trying the current driverkit before, and if it fails, fallbacking at trying the new pattern.
What would you think?
Do you have any idea?
/cc  @zuc @maxgio92

Proposed PR for arm support (https://github.com/falcosecurity/driverkit/pull/143) address this issue using both evaluated options:

adds a kernelurls param
doubled the matching pattern

repo: falcosecurity/driverkit


text:
update(data/en): correct and update gRPC config description

What type of PR is this?
/kind bug
/kind cleanup
/kind content
Any specific area of the project related to this PR?
/area documentation
What this PR does / why we need it:
Which issue(s) this PR fixes:
The gRPC config description was not updated w.r.t the unix socket binding type.
Fixes #
Special notes for your reviewer:

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To complete the pull request process, please assign leogr
You can assign the PR to them by writing /assign @leogr in a comment when ready.
The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

LGTM label has been added.  Git tree hash: 332d7cb66b9919b5415f0854bc947fbf6b345fe8

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: fntlnz
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [fntlnz]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

authors: leogr poiana

repo: falcosecurity/falco-website


text:
wip: new(rules): add rule for detecting fileless execution via memfd_create

What type of PR is this?

Uncomment one (or more) /kind <> lines:

/kind bug

/kind cleanup

/kind design

/kind documentation

/kind failing-test

/kind feature

Any specific area of the project related to this PR?

Uncomment one (or more) /area <> lines:

/area rules

/area registry

/area build

/area documentation

What this PR does / why we need it:
This PR takes advantage of a new incoming Falco feature for detecting fileless execution via memfd_create. This is a very well known defense evasion technique that threat actors might use to execute malware on victim machines. It has been used in the past, but also pretty recently as reported by these two articles:

https://cybersecurity.att.com/blogs/labs-research/malware-using-new-ezuri-memory-loader
https://www.wiz.io/blog/pyloose-first-python-based-fileless-attack-on-cloud-workloads
Putting this on wip until the feature lands in Falco.

Which issue(s) this PR fixes:

Fixes #
Special notes for your reviewer:

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: loresuso
Once this PR has been reviewed and has the lgtm label, please assign andreagit97 for approval. For more information see the Kubernetes Code Review Process.
The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@loresuso we can soon start with merging rules that make the rules file incompatible with the current Falco as the next release is planned for end of Sep.

After merging this rule at maturity_incubating we can bump to maturity_stable in a follow up PR. That way we honor our new guidelines. CC @darryk10 @leogr

After merging this rule at maturity_incubating we can bump to maturity_stable in a follow up PR. That way we honor our new guidelines. CC @darryk10 @leogr

:+1:
Rules files have been split. @loresuso could you rebase this PR and address the above suggestions, please? :pray:

IMO it makes sense to uniformly bump the engine version. In this way, when we graduate rules, we don't need to bother or remember how the version should be bumped, and just move the rule between files, but I'm open to discuss!

/hold
We need to bump the required engine version. @leogr @LucaGuerra do we bump the rules engine uniformly in all rules files? I would vote for that!

What's the benefit of having the same required_engine_version?
The only two consequences I see

We will have to bump the minor version in all rules files https://github.com/falcosecurity/rules/blob/main/RELEASE.md#versioning-a-ruleset
We will make all files not compatible with a previous Falco engine (even if they are)

Moreover, the CI should already be able to check (and inform us) when an engine version bump is required. Indeed, this jobs matrix indicates that falco-incubating_rules.yaml is no longer compatible with 0.35.0 because the missing field

In the end, I don't have a strong opinion and am open to any solution. I just don't see the benefit of doing this (perhaps am I missing something? :thinking: )
In case we decide to bump all files, I still would avoid bumping falco-deprecated_rules.yaml, since it does not make much sense to me.

@leogr will the required engine version be overriden in the order the rules files are loaded? If we don't bump in all files, we at least should make sure the highest required version in any files has the final say?

@leogr will the required engine version be overriden in the order the rules files are loaded? If we don't bump in all files, we at least should make sure the highest required version in any files has the final say?

The required_engine_version applies at the single file level only (@jasondellaluce correct me if I'm wrong). It acts as a validation condition when loading the rules files, so it won't be overridden by other rules files. Basically, files will be validated one by one, the first failure will stop the whole process, regardless of the loading order.

@leogr will the required engine version be overriden in the order the rules files are loaded? If we don't bump in all files, we at least should make sure the highest required version in any files has the final say?

The required_engine_version applies at the single file level only (@jasondellaluce correct me if I'm wrong). It acts as a validation condition when loading the rules files, so it won't be overridden by other rules files. Basically, files will be validated one by one, the first failure will stop the whole process, regardless of the loading order.

ok then let's just bump it in the respective file for now, thanks!

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: incertum, loresuso
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [incertum]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

LGTM label has been added.  Git tree hash: 01650113bdbe0bb5383a3ee06151604fd4526b6b

/unhold

authors: incertum leogr loresuso poiana

repo: falcosecurity/rules


text:
您要的产品目前在中国商店不提供

下载不了，可以提供一个dmg安装包吗

这个软件现在有些小问题，作者还没修改！下了也登录不上！等作者修改吧！

@Noah1991 后续会上架，最近太忙了
#179

authors: Noah1991 fancymax joenil


text:
Nerd font and color scheme used for mac-os preview ?

@fang2hou Thanks for the preset, it looks amazing 🌟
Just one more thing, if you wouldn't mind could you please also share the nerd font and terminal color scheme used in the Mac-OS preview ? as it looks the best among all the previews

I am using alacritty now.
The font is JetBrainsMono Nerd Font, you can download it from here.

My alacrity TOML
[colors.bright]
black = "#4b4b4b"
blue = "#9ac2bb"
cyan = "#aedea0"
green = "#c8c847"
magenta = "#eaa4b7"
red = "#ff5f4f"
white = "#ffffff"
yellow = "#ffc24b"

[colors.normal]
black = "#282828"
blue = "#80aa9e"
cyan = "#8bba7f"
green = "#b0b846"
magenta = "#d3869b"
red = "#f2594b"
white = "#e2cca9"
yellow = "#e9b143"

[colors.primary]
background = "#282828"
foreground = "#e2cca9"

[font]
size = 15.0

[font.bold]
family = "JetBrainsMono Nerd Font"
style = "Bold"

[font.bold_italic]
family = "JetBrainsMono Nerd Font"
style = "Bold Italic"

[font.italic]
family = "JetBrainsMono Nerd Font"
style = "Italic"

[font.normal]
family = "JetBrainsMono Nerd Font"
style = "Light"

[font.offset]
x = 0
y = 1

[window]
decorations = "full"
dynamic_padding = false
option_as_alt = "OnlyLeft"
resize_increments = true

[window.dimensions]
columns = 180
lines = 35

[window.padding]
x = 12
y = 12

Thank you for sharing the color scheme. I figured it out, I was using a regular styled mono version of the JetBrains Mono font, after changing to a non-mono medium styled version it looks similar


text:
feat: support nft urls in reactions and replies

What is the feature you would like to implement?
Allow reactions and cast-replies to point to an NFT as their parent. We will eventually want to expand this to work for generic web URLs as well, though that can be cut if it adds a lot of complexity.
Why is this feature important?
Merkle supports NFT likes in a centralized manner, and NFT comments is one of the most requested features from users. If the protocol doesn't support it, clients will continue doing it in a centralized manner. Doing it in a decentralized way, makes this data more portable and available to other clients.
Will the protocol spec need to be updated??
Yes, we'll need to change the specification for the message fields for cast parents and reaction targets.
How should this feature be built? (optional)
TBD

Closing in favor of existing ticket https://github.com/farcasterxyz/hub/issues/231

authors: pfletcherhill varunsrin

repo: farcasterxyz/hub


text:
Month, Year select

Hi! 👋
Firstly, thanks for your work on this project! 🙂
Today I used patch-package to patch react-native-ui-datepicker@1.0.11 for the project I'm working on.

Here is the diff that solved my problem:
diff --git a/node_modules/react-native-ui-datepicker/src/DateTimePicker.tsx b/node_modules/react-native-ui-datepicker/src/DateTimePicker.tsx
index 5a55cf2..3958bdd 100644
--- a/node_modules/react-native-ui-datepicker/src/DateTimePicker.tsx
+++ b/node_modules/react-native-ui-datepicker/src/DateTimePicker.tsx
@@ -137,7 +137,7 @@ const DateTimePicker = ({
   useEffect(() => {
     dispatch({
       type: CalendarActionKind.SET_CALENDAR_VIEW,
-      payload: mode === 'time' ? CalendarViews.time : CalendarViews.day,
+      payload: mode === 'time' ? CalendarViews.time : mode === 'year' ? CalendarViews.year : mode ==='month' ? CalendarViews.month : CalendarViews.day ,
     });
   }, [mode]);

diff --git a/node_modules/react-native-ui-datepicker/src/types.ts b/node_modules/react-native-ui-datepicker/src/types.ts
index 7783b3f..4229093 100644
--- a/node_modules/react-native-ui-datepicker/src/types.ts
+++ b/node_modules/react-native-ui-datepicker/src/types.ts
@@ -5,7 +5,7 @@ import type { ReactNode } from 'react';

 export type DateType = string | number | Dayjs | Date | null | undefined;

-export type CalendarModes = 'datetime' | 'date' | 'time';
+export type CalendarModes = 'datetime' | 'date' | 'time' | 'month' | 'year';

 export type HeaderButtonPositions = 'around' | 'right' | 'left';

This issue body was partially generated by patch-package.

this is fixed in this commit 653daa8


text:
Fixed and extended Dead ReLU detector callback

Initially 'DeadReLUDetectorCallback was only working for Dense layers and the percentage of dead relu neurons was incorrect.
Corrected the percentage calculations
Extended for all layers with a ReLU activation (tested for conv2d and dense)
Tested on python 3.5 TF and Theano

For testing I had 1 fail, however I'm quite certain it is independent of my additions.
`self = <backend_test.TestBackend object at 0x7f4f68019470>
def test_moments(self):
    input_shape = (10, 10, 10, 10)
    x_0 = np.zeros(input_shape)
    x_1 = np.ones(input_shape)
    x_random = np.random.random(input_shape)

    th_axes = [0, 2, 3]
    tf_axes = [0, 1, 2]

    for ip in [x_0, x_1, x_random]:
        for axes in [th_axes, tf_axes]:
            for keep_dims in [True, False]:
                ip_th = KTH.variable(ip)
                th_mean, th_var = KCTH.moments(ip_th, axes, keep_dims=keep_dims)

                ip_tf = KTF.variable(ip)
                tf_mean, tf_var = KCTF.moments(ip_tf, axes, keep_dims=keep_dims)

                th_mean_val = KTH.eval(th_mean)
                tf_mean_val = KTF.eval(tf_mean)
                th_var_val = KTH.eval(th_var)
                tf_var_val = KTF.eval(tf_var)

                assert_allclose(th_mean_val, tf_mean_val, rtol=1e-4)

              assert_allclose(th_var_val, tf_var_val, rtol=1e-4)

E                   AssertionError:
E                   Not equal to tolerance rtol=0.0001, atol=0
E
E                   (mismatch 100.0%)
E                    x: array([[[[ 0.]],
E
E                           [[ 0.]],...
E                    y: array([[[[  6.938894e-18]],
E
E                           [[  6.938894e-18]],...

If people need a return vallue/callback, the request will come naturally.
Now... My check failed multiple times. For a test that worked on my pc (both py2.7 Tensorflow and py3.5 Tensorflow) an never by the 'ravis CI build'. In the end I just commented that part of the test, but now it gives errors about an other package. I don't know what I can/should do about that

@infelane I took a look at the errors and it seems they aren't related to your changes. Does that seem correct to you?

@ahundt The errors that raised were indeed outside my additions. I checked the code that raised the error and might have found a bug overthere. Do you think the dead_relu_detector can be merged? Maybe reopen the backend_test?

LGTM, merging, thanks for the contribution! 👍

Congrats for getting it merged

authors: ahundt arodiss infelane


text:
Notes

1
For an @-subcard during a local quiz, the prompt sentence will be shown but with a piece of it replaced with the @-subprompt. In order to know which piece of the prompt sentence to hide, the @-subcard's pieces will be examined for cloze marks.

if no cloze marks found, look for the prompt, and if that fails, look for the responses, and if that fails, throw.
if cloze marks found in one item (or more, though that's probably an error), hide that in the sentence.

We can have a "linter" that will warn when no clozes are present in @-subcard and the prompt/response chosen is repeated in the sentence. Also if more than one item has a cloze mark.
2
Two Ebisu models are associated each global card. One global one shared by all instances of it. And one local one personal to it and this sentence. When you do a global review (all by itself), the local ones all get an active update. When you do a local review (with a single sentence), the global get a passive update.
3
Exponential decay and SRS might optimize long-term just-about-to-forget, hard-to-recall recall, but what if you want to optimize rapid recall? You see kanji on the subway, and sure if you've been doing your SRS you'll likely eventually get the answer (with a probability given by Ebisu), but you'll have rolled past it. The only way to do that is regular exposure.

When you do a local review (with a single sentence), the global get a passive update, and all other local reviews get an active update.

repo: fasiha/curtiz-japanese-nlp

license: Unlicense


text:
Is the remotemoe tunnel down?

I have been getting the error message 'This page isn't working' for more than five days 😭. Am I doing something wrong, or is the remotemoe tunnel down?

See https://github.com/fasmide/remotemoe/issues/19

authors: camenduru fasmide

repo: fasmide/remotemoe


text:
fix AWD_LSTM not contiguous bug

Error: rnn: hx is not contiguous
This error happens when

bidir=True
bs decrease
run on gpu

The 1 and 2 cause self.hidden[l][0][:,:bs] be not contiguous, and with 3 the error happens.
Fix it by adding contiguous() after self.hidden[l][0][:,:bs] and add a test that can reproduce this error with cuda flag.

Thanks a lot for fixing!

authors: cwza sgugger


text:
Is there a way to have custom javascript in the rendered HTML for a blog post?

I have a blog post with Altair visualization made from Jupyter Notebook as usual. However, I want to add some custom JavaScript to it.
Inside the Jupyter notebook, you have to run the cell with the JavaScript every time you open it to see its effects, even though the rest of the interactivity of the Altair chart works without executing any cell. Because of this behavior, just publishing the jupyter notebook with the JavaScript code would probably not have any effect (I haven't actually tested it).
Similar to https://github.com/fastai/fastpages/pull/171 I want to have fastpages add a little JavaScript code in the rendered HTML for one of the posts, so that the already existing HTML for the charts are modified a little.
Is there a way to achieve this?

This is example of how custom javascript is injected into fastpages: https://github.com/fastai/fastpages/blob/master/_includes/custom-head.html
This requires you to customize fastpages and learn about how the internals work a bit more.

@hamelsmu That helped a lot and I just got it working. I think it's actually better to have custom scripts enabled via Jekyll.

great!

authors: armsp hamelsmu

repo: fastai/fastpages


text:
Automatically generate a sitemap

I want to add my blog to the Google search engine, I need to generate a sitemap of the blog.
So can you add a feature that automatically generate a sitemap?

thanks.  try this https://github.com/jekyll/jekyll-sitemap

thanks.  try this https://github.com/jekyll/jekyll-sitemap

authors: hamelsmu spiritLHL


text:
fastapi dev runs stuck

Privileged issue

[X] I'm @tiangolo or he asked me directly to create an issue here.

Issue Content
The first time I ran fastapi dev, there was no problem, but I encountered a code error. Then after I modified the code and saved it, a WARNING: WatchFiles detected changes in 'tool/index.py'. Reloading... then got stuck and could not exit.

Any updates on this @kingcwt? facing the same issue!

Could be related to: https://github.com/encode/uvicorn/issues/2000

I currently have a slightly different issue from yours @kingcwt but it's still an issue with fastapi cli (dev and run)
The Code

The Error

do not use the fastapi dev to run your application just use uvicorn  instead, i do not face any issues with uvicorn

I tryied to reproduce it, but without success.
But sometimes I get the same problem running uvicorn with --reload in cmder/windows. I think it is related to uvicorn instead of fastapi

I'm having the same issue here on windows 10.
I think this is related: https://www.reddit.com/r/FastAPI/comments/13oynf6/keeps_old_routes_after_changing_cache_problem/
It is like fastapi keeps an old version of the code cached somewhere. Even if I force kill fastpi and restart it, it loads an old version of my code.
It works (for a while) if I change port.

I think uvicorn dev server is better as of now. As we are not getting any updates about the Fast API cli. Its important to note that this may be fixed in near future. It happens a lot with Fast API server. So you have to kill the terminal and open a new one to re-run the project. Its painful.

@Sarmad426 Yes, you are right i am also facing the same issue I tried with both the commands such as
fast API dev filename
or
if name == "main":
uvicorn.run("main:app", host="127.0.0.1", port=8000, reload=True)
Sometimes it stuck you have to forcefully close the server but still, the port is running on the cache. So you have to run the server again on a different port.

Running into a similar issue.  I can I kill the the process with ctrl+c, but I cannot run on the same port.  Attempting to run on the same port prints out the message like everything is working fine, but trying to access /docs spins forever.  Switching to a new port works fine.

in pycharm if you use the "run" method to run the project then it tends to hand after reloading. if you task manager kill python it reloads again. something definately fishy there.
if you just do uvicorn --reload  in terminal it tends to work better but still a massive PITA on windows :( easier to just not run it with reload
win11, py3.12, pycharm

can confirm. win 11.
issue present at least month.
WARNING:  WatchFiles detected changes in 'config.py'. Reloading... and its stuck. No pycharm, vscode + venv, server command started by hand in terminal (❯ fastapi dev webserver.py --port 8080)

I wonder if this would still happen with uvicorn's --timeout-graceful-shutdown option. Using fastapi dev, you have to set it using an environment variable UVICORN_TIMEOUT_GRACEFUL_SHUTDOWN=5.

I have been getting this same problem whether uvicorn main:app --reload or fastapi dev method launching from powershell. (no pycharm here)

Win11.
VSCode
Python 3.12.6
FastAPI 0.115.0
Uvicorn 0.31.0

Resorting to Task Manager (Ctrl+Shift+Esc) and killing python tasks as Ctrl+C often won't quit server and closing powershell window and launching another doesn't seem to kill it either.
Installed fastapi using "fastapi[standard]" and also removed and tried just installing separately fastapi and uvicorn
Based on this thread #2000 just to test tried downgrading just uvicorn to 0.22 with no difference then to 0.21 (0.21.1) and sure enough it stops being stuck and reloads in a second?
WARNING:  StatReload detected changes in 'api.py'. Reloading...
INFO:     Started server process [9192]
INFO:     Waiting for application startup.
INFO:     Application startup complete.

I am also  facing this issue recently with FastAPI reloading.
When we start the server, it works fine, and the APIs are functioning correctly.
However, when we make changes to the code and save it, the FastAPI server does not respond when the API is hit again, and the FastAPI server page shows the reload icon for a long time.

Windows stuff, I see, using WSL2 never encountered this issue.

For me the problem was avast scanning the app before allowing it to execute thus taking a long time. Disabled avast and suddenly it was working well

I am facing a similar issue using Uvicorn. When I make changes to the code and save it, Uvicorn reloads, showing the message 'Application shutdown completed.' After that, the APIs stop responding, and the terminal becomes unresponsive. Even pressing Ctrl+C doesn't work

I had the same problem with PyCharm FastAPI. When introducing a change, it used to get stuck on reload. (most likely couldn't kill the current process.) But I could resolve it by just using the terminal and running
uvicorn main:app --reload

It then worked like a charm.
I noticed that no matter what I do in Run/Debug Configuration of PyCharm, it wont be fixed there. I.E. if I choose Uvicorn in Run/Debug Config, I would still have the same problem. For me it works only when I lunch the server from terminal using Uvicorn.

I had same problem, fastapi dev got stuck. Then after i killed the terminal and started again, the schemas in the docs got stucks, it won't be updated even i modify the model schemas, it will works again when you start dev server with different port.

how fix it>

backto uvicorn ==0.20.0,  this v can work.

backto uvicorn ==0.20.0, this v can work.

I have tried this method too, but the issue persists.

authors: 3to1null AIdjis AdmWinther Jkrox Omachonu-prosper RasmusN Sarmad426 WilliamStam ankit-brijwasi arslanahmad768 atomicjarrod ceb10n killjoy1221 kingcwt linpan mavic111 pmsmanishchauhan qodzero rutexd thecouchcoder

repo: fastapi/fastapi


text:
Fix ValidationExceptions missing type annotations after v0.100.0

Type information got lost from ValidationExceptions after v0.100.0. This PR brings them back. ErrorDetails is used as is from Pydantic V2. With V1 its compatible with Pydantic V1 .errors().
Related https://github.com/tiangolo/fastapi/discussions/9907

Checking the conversation in the discussion to understand the use case, it seems the use case would be solved by using a custom exception, that would be much simpler and independent of FastAPI internals. :nerd_face:
Given that, I'll pass on this one, but  thanks for the interest! :coffee:

@tiangolo why the errors() can not be properly typed when the class is documented https://fastapi.tiangolo.com/tutorial/handling-errors/#override-request-validation-exceptions ?

authors: MarkusSintonen tiangolo


text:
Connect functionalities from mesher and elements to plotter

This PR will connect functionalities from mesher and elements, and use PyVista to provide visual aid.

For reference, here is my playground script (for now).
import fastfem.mesh as m
import fastfem.plotter as p
import numpy as np

nh = 10
nv = 10
hl = 3
vl = 3
mesh = m.create_a_rectangle_mesh(
    horizontal_length=hl,
    vertical_length=vl,
    nodes_in_horizontal_direction=nh,
    nodes_in_vertical_direction=nv,
    element_type="triangle",
    file_name=None,
)

# Domains:
bottom_boundary = mesh["bottom_boundary"]
right_boundary = mesh["right_boundary"]
top_boundary = mesh["top_boundary"]
left_boundary = mesh["left_boundary"]
rectangle = mesh["surface"]

visualizer = p.VisualMesh(mesh)
visualizer.plot_mesh()

# Time
time_steps = 240
temperatures = np.zeros((time_steps, nv, nh))

# Dummy data
left_right_temp = 15
top_temp = 10
bottom_temp = 25
for t in range(time_steps):
    for i in range(nv):
        for j in range(nh):
            x = j / (nh - 1) * hl
            y = i / (nv - 1) * vl
            if j == 0 or j == nh - 1:
                temperatures[t, i, j] = left_right_temp
            elif i == 0:
                temperatures[t, i, j] = bottom_temp
            elif i == nv - 1:
                temperatures[t, i, j] = top_temp
            else:
                temperatures[t, i, j] = 20 + 20 * np.sin(2 * np.pi * x / hl) * \
                                        np.cos(2 * np.pi * y / vl) * \
                                        np.sin(np.pi * t / time_steps)

visualizer.animate_mesh(30, time_steps, temperatures)

Hi @sacha-escudier, I rebased this branch to main. There is an issue related to our API Reference in docs.
If you run
hatch run docs:serve

you will get this error:
WARNING -  griffe: fastfem/plotter/mesh_visual.py:13: No type or annotation for parameter 'mesh'
WARNING -  griffe: fastfem/plotter/mesh_visual.py:16: No type or annotation for returned value 1

That's why docs workflow fail currently.
Could you add all the type hints until there aren't any error in docs?

@sinaatalay type issue should be fixed now.

authors: sacha-escudier sinaatalay

repo: fastfem/fastfem


text:
Renamed to process-warning

Signed-off-by: Matteo Collina hello@matteocollina.com
Fixes #43

Checklist

[ ] run npm run test and npm run benchmark
[ ] tests and/or benchmarks are included
[ ] documentation is changed or added
[ ] commit message and code follows the Developer's Certification of Origin
and the Code of conduct

I'll bump the major and deprecate the previous module once this lands.

repo: fastify/process-warning


text:
If the bot doesn't have push access, we crash. Maybe we should be friendly?

[2018-04-02 18:20:55] DEBUG GitRepo:  Not setup yet, sleeping (time before timeout: 300.0) https://github.com/fastlane/ci
Thread terminated with exception: git '--git-dir=/Users/liebowitz/.fastlane/ci/fastlane-ci-config/.git' '--work-tree=/Users/liebowitz/.fastlane/ci/fastlane-ci-config' push 'origin' 'master'  2>&1:remote: Permission to fastlane/ci-config-heroku.git denied to fastlanebot.
fatal: unable to access 'https://github.com/fastlane/ci-config-heroku/': The requested URL returned error: 403
[2018-04-02 18:20:55] DEBUG GitRepo:  Starting commit_changes! https://github.com/fastlane/ci-config-heroku for taquitos@gmail.com
/Users/liebowitz/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/gems/git-1.3.0/lib/git/lib.rb:937:in command'   /Users/liebowitz/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/gems/git-1.3.0/lib/git/lib.rb:742:in push'
/Users/liebowitz/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/gems/git-1.3.0/lib/git/base.rb:329:in push'   /Users/liebowitz/dev/ci/app/shared/models/git_repo.rb:396:in block in push'
/Users/liebowitz/dev/ci/app/shared/models/git_repo.rb:320:in perform_block'   /Users/liebowitz/dev/ci/app/shared/models/git_repo.rb:391:in push'
/Users/liebowitz/dev/ci/app/shared/models/git_repo.rb:384:in block in commit_changes!'   /Users/liebowitz/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/bundler/gems/TaskQueue-5b3f459be5c4/lib/queue_worker.rb:82:in block in process'
[2018-04-02 18:20:55] DEBUG GitRepo:  Using Clone User credentials with taquitos@gmail.com as author information on https://github.com/fastlane/ci-config-heroku
bundler: failed to load command: rackup (/Users/liebowitz/.rbenv/versions/2.3.3/bin/rackup)
Git::GitExecuteError: git '--git-dir=/Users/liebowitz/.fastlane/ci/fastlane-ci-config/.git' '--work-tree=/Users/liebowitz/.fastlane/ci/fastlane-ci-config' push 'origin' 'master'  2>&1:remote: Permission to fastlane/ci-config-heroku.git denied to fastlanebot.
fatal: unable to access 'https://github.com/fastlane/ci-config-heroku/': The requested URL returned error: 403
/Users/liebowitz/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/gems/git-1.3.0/lib/git/lib.rb:937:in command'   /Users/liebowitz/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/gems/git-1.3.0/lib/git/lib.rb:742:in push'
/Users/liebowitz/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/gems/git-1.3.0/lib/git/base.rb:329:in push'   /Users/liebowitz/dev/ci/app/shared/models/git_repo.rb:396:in block in push'
/Users/liebowitz/dev/ci/app/shared/models/git_repo.rb:320:in perform_block'   /Users/liebowitz/dev/ci/app/shared/models/git_repo.rb:391:in push'
/Users/liebowitz/dev/ci/app/shared/models/git_repo.rb:384:in block in commit_changes!'   /Users/liebowitz/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/bundler/gems/TaskQueue-5b3f459be5c4/lib/queue_worker.rb:82:in block in process'

We actually now post a notification 🎉

repo: fastlane/ci