text:
Adding Boss Bar for countdowns

Why don't you add a boss bar message while the starting, the cycling and the game countdowns are running ?
This is a missing feature that you can add.

We are going to do this, the plugin is not yet compete. The reason why this hasn't yet been implemented is because we are waiting for translations are complete before adding this feature.

Nice to heard it :)

One cuestion,
The translations will be per client o per server config?
El dia 02/02/2015 16.35, "maestro34" notifications@github.com va escriure:

Nice to heard it :)
—
Reply to this email directly or view it on GitHub
https://github.com/twizmwazin/CardinalPGM/issues/127#issuecomment-72477031
.

@elespawol The actual translations will be done by the server, but it will look at your client's language and then send a message based on what language you are using.

Cool!
El dia 02/02/2015 19.30, "iEli2tyree011" notifications@github.com va
escriure:

@elespawol https://github.com/elespawol The actual translations will be
done by the server, but it will look at your client's language and then
send a message based on what language you are using.
—
Reply to this email directly or view it on GitHub
https://github.com/twizmwazin/CardinalPGM/issues/127#issuecomment-72510289
.

Add this for all countdpwns, like fo gold core, glass core, and in cannon duelthe coundowns of the map

We know that we need to add, this feature is just a complicated one and it will take time.

@twizmwazin Will the countdown use BarAPI? Or something custom coded?

+1
El dia 16/02/2015 8.39, "dentmaged" notifications@github.com va escriure:

@twizmwazin https://github.com/twizmwazin Will the countdown use
BarAPI? Or something custom coded?
—
Reply to this email directly or view it on GitHub
https://github.com/twizmwazin/CardinalPGM/issues/127#issuecomment-74469639
.

@dentmaged I want to minimize use of external dependencies when possible. Bar API has a host of limitations, one being the inability to do localization efficiently. Because it is just sending some packets, I plan on doing this myself.

Mean that you can not add this? It would be great, tried to add BarAPI your plugin? you will think of something.

@Jair07mx The answer to your question is right above your comment:
"I want to minimize use of external dependencies when possible. Bar API has a host of limitations, one being the inability to do localization efficiently. Because it is just sending some packets, I plan on doing this myself."

@twizmwazin You can send boss bars per-client, thus you can do localisation just fine with BarAPI.

@ParaPenguin BarAPI is like 2 classes though, which could both be easily rewritten in Cardinal. Either way, I am waiting until we move to 1.8 to do this. SportBukkit 1.8 is currently mostly ready, it can b e found in this PR. As soon as it hits master, I'm going to update Cardinal to support it. SportBukkit's custom API is not consistent between versions, so I will not be able to have cross version compatibility.

@twizmwazin If SportBukkit doesn't cross per version, it would probably be best to use reflection to achieve the best result across versions.

@ParaPenguin Perhaps, although I'm not too concerned with supporting older Minecraft versions.

@twizmwazin I think most people would at least expect the support of 1.7 until 1.8 is launched

https://github.com/twizmwazin/CardinalPGM/commit/9f9f043486655dab73655d357f84a28382156920

I'll close the issue when the bar is fully implemented

Yeah, i know, GL

Before I go for the night:
:D

Congrats @twizmwazin ! Good night!
Or is this made using cropping O_o

@SungMatt This was 100% legit taken in Cardinal

@twizmwazin Doesn't help that today is April Fools, does it :p
So close to the completing the milestone's objectives!

@SungMatt Still the 31st for me

Congrats!!! When that will be avabile?

@twizmwazin When will this feature be done? I'll implement it on myself if you're too busy.

@dentmaged I ran into a lot of issues and inconsistencies. If you want to take a stab at it, be my guest.

@twizmwazin I have began work on it. How can I tell when a core is about to go into a mode (gold core mode for example)?

GOLD CORE MODE in {0} seconds

@TiTo-418 What colours are used?

Maybe @CaptainElliott know

@dentmaged Just wondering, before you work on all the different possibilities for displaying the boss bar, did you make it reliable?

@dentmaged also do you have compatibility for localisation?

@CaptainElliott Yep!
@iEli2tyree011 What do you mean by "reliable"? I don't think there will be any problems in the future (unless SportBukkit changes)

TiTi-418, pl0x

@dentmaged Did you write your own module then?

Yes. It is a wrapper for the BossBar module.

05/05/15, this is not added.

@Zenzoh Be patient...

is this ready to be implemented yet?

Implemented completely on 857eeab

repo: twizmwazin/CardinalPGM


text:
kadm: Add ErrorSummary() for sharded responses

The kadm client is super handy for administrative tools, especially when working with sharded responses such as fetching many consumer group offsets. The package already offers a func (rs FetchOffsetsResponses) EachError(fn func(FetchOffsetsResponse)) function to log all errors from a response.
Oftentimes I want to bubble up a single descriptive error message in case all shards have failed after checking with res.AllFailed(). I propose adding another method func (rs FetchOffsetsResponses) ErrorSummary() error which would offer that for all sharded responses which may contain more than one error. The returned error message could be something like this: "8 out of 13 total shard requests have failed. The last error is: GROUP_COORDINATOR_NOT_AVAILABLE - the returned error message by the respective broker."
Usage would then be:
res := s.kafkaSvc.ListConsumerGroupOffsetsBulk(ctx, groups)

res.EachError(func(shardRes kadm.FetchOffsetsResponse) {
	s.Logger.Warn("failed to fetch group offset",
		zap.String("group", shardRes.Group),
		zap.Error(shardRes.Err))
})

if res.AllFailed() {
	return nil, res.ErrorSummary()
}

What do you think? Happy to contribute it.

wdyt about instead switching Error to return ShardErrors, which already does the summary you're looking for? And we can improve the ShardErrors.Error function.
So then your example would switch to,
if res.AllFailed() {
        return nil, res.Error()
}

Actually, the sharding aspect is already lost in FetchOffsetResponses. Each error can be from any shard. I'm not sure this is worth providing by default in kadm -- usually Error returns the first encountered error -- I'm leaning to close this without a proposed implementation.

Closed due to prior comment

source: gharchive/issue

authors: twmb weeco

repo: twmb/franz-go

license_type: permissive

license_source: github-api


text:
Quick Install instructions in README.rst are out of date

$ git clone https://github.com/facebook/rocksdb.git
Cloning into 'rocksdb'...
remote: Counting objects: 53785, done.
remote: Compressing objects: 100% (10/10), done.
remote: Total 53785 (delta 0), reused 2 (delta 0), pack-reused 53775
Receiving objects: 100% (53785/53785), 100.79 MiB | 7.72 MiB/s, done.
Resolving deltas: 100% (40041/40041), done.
$ cd rocksdb/
$ make build
Makefile:105: Warning: Compiling in debug mode. Don't use the resulting binary in production
  GEN      util/build_version.cc
Makefile:105: Warning: Compiling in debug mode. Don't use the resulting binary in production
  GEN      util/build_version.cc
make: *** No rule to make target 'build'.  Stop.

As you can see, following them leads to failed build. Additionally, I don't think it should be done in debug mode.

@Srogozins
it's typo.

Seems to be failing on the pip install now for me:
    x86_64-linux-gnu-g++ -pthread -shared -Wl,-O1 -Wl,-Bsymbolic-functions -Wl,-z,relro -fno-strict-aliasing -DNDEBUG -g -fwrapv -O2 -Wall -Wstrict-prototypes -Wdate-time -D_FORTIFY_SOURCE=2 -g -fdebug-prefix-map=/build/python2.7-HVkOs2/python2.7-2.7.13=. -fstack-protector-strong -Wformat -Werror=format-security -Wl,-z,relro -Wdate-time -D_FORTIFY_SOURCE=2 -g -fdebug-prefix-map=/build/python2.7-HVkOs2/python2.7-2.7.13=. -fstack-protector-strong -Wformat -Werror=format-security build/temp.linux-x86_64-2.7/rocksdb/_rocksdb.o -lrocksdb -lsnappy -lbz2 -lz -o build/lib.linux-x86_64-2.7/rocksdb/_rocksdb.so
    /usr/bin/ld: cannot find -lrocksdb
    collect2: error: ld returned 1 exit status
    error: command 'x86_64-linux-gnu-g++' failed with exit status 1

Full install log(a lot of output)
Also, I believe, . bin/active should be . bin/activate

@Srogozins
from the log
/usr/bin/ld: cannot find -lrocksdb

after compiling rocksdb, you should add $BUILD_ROCKSDB_DIR to environment variables.
something like this
export CPLUS_INCLUDE_PATH=${CPLUS_INCLUDE_PATH}:`pwd`/../include
export LD_LIBRARY_PATH=${LD_LIBRARY_PATH}:`pwd`
export LIBRARY_PATH=${LIBRARY_PATH}:`pwd

where pwd is $BUILD_ROCKSDB_DIR.
so that python-rocksdb can locate the rocksdb library and headers.

I believe that's what I did on lines 49-51:
$ export CPLUS_INCLUDE_PATH=${CPLUS_INCLUDE_PATH}:`pwd`/../include
$ export LD_LIBRARY_PATH=${LD_LIBRARY_PATH}:`pwd`
$ export LIBRARY_PATH=${LIBRARY_PATH}:`pwd`

(pyrocks_test) root@a759e1ee669d:/rocksdb/build# printenv
LD_LIBRARY_PATH=:/rocksdb/build
HOSTNAME=a759e1ee669d
OLDPWD=/rocksdb
VIRTUAL_ENV=/rocksdb/pyrocks_test
PWD=/rocksdb/build
HOME=/root
LIBRARY_PATH=:/rocksdb/build
TERM=xterm
SHLVL=1
CPLUS_INCLUDE_PATH=:/rocksdb/build/../include
PATH=/rocksdb/pyrocks_test/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
PS1=(pyrocks_test) ${debian_chroot:+($debian_chroot)}\u@\h:\w\$
_=/usr/bin/printenv

@Srogozins
can you show the content of  /rocksdb/build ?
thanks

$ ls /rocksdb/build
CMakeCache.txt	CTestTestfile.cmake  build_version.cc	  third-party
CMakeFiles	Makefile	     cmake_install.cmake  tools

@Srogozins
I miss the important part in the installation section.
you should make after cmake ...
cmake ..
make

sorry, it's my fault.

Unfortunately, it fails:
$ git clone https://github.com/facebook/rocksdb.git
Cloning into 'rocksdb'...
remote: Counting objects: 54748, done.
remote: Compressing objects: 100% (905/905), done.
remote: Total 54748 (delta 106), reused 202 (delta 48), pack-reused 53775
Receiving objects: 100% (54748/54748), 102.99 MiB | 19.77 MiB/s, done.
Resolving deltas: 100% (40147/40147), done.
$ cd rocksdb
$ mkdir build && cd build
$ cmake ..
-- The C compiler identification is GNU 6.3.0
-- The CXX compiler identification is GNU 6.3.0
-- Check for working C compiler: /usr/bin/cc
-- Check for working C compiler: /usr/bin/cc -- works
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Detecting C compile features
-- Detecting C compile features - done
-- Check for working CXX compiler: /usr/bin/c++
-- Check for working CXX compiler: /usr/bin/c++ -- works
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Detecting CXX compile features
-- Detecting CXX compile features - done
-- Found Git: /usr/bin/git (found version "2.11.0")
-- Performing Test HAVE_SSE42
-- Performing Test HAVE_SSE42 - Success
-- Performing Test HAVE_THREAD_LOCAL
-- Performing Test HAVE_THREAD_LOCAL - Success
-- Performing Test HAVE_OMIT_LEAF_FRAME_POINTER
-- Performing Test HAVE_OMIT_LEAF_FRAME_POINTER - Success
-- Performing Test HAVE_FALLOCATE
-- Performing Test HAVE_FALLOCATE - Success
-- Looking for malloc_usable_size
-- Looking for malloc_usable_size - found
-- Looking for pthread.h
-- Looking for pthread.h - found
-- Looking for pthread_create
-- Looking for pthread_create - not found
-- Looking for pthread_create in pthreads
-- Looking for pthread_create in pthreads - not found
-- Looking for pthread_create in pthread
-- Looking for pthread_create in pthread - found
-- Found Threads: TRUE
-- JNI library is disabled
-- Configuring done
-- Generating done
-- Build files have been written to: /rocksdb/build
$ make
Scanning dependencies of target testutillib
[  1%] Building CXX object CMakeFiles/testutillib.dir/db/db_test_util.cc.o
/rocksdb/db/db_test_util.cc: In destructor 'virtual rocksdb::DBTestBase::~DBTestBase()':
/rocksdb/db/db_test_util.cc:71:12: error: 'rocksdb::SyncPoint' has not been declared
   rocksdb::SyncPoint::GetInstance()->DisableProcessing();
            ^~~~~~~~~
/rocksdb/db/db_test_util.cc:72:12: error: 'rocksdb::SyncPoint' has not been declared
   rocksdb::SyncPoint::GetInstance()->LoadDependency({});
            ^~~~~~~~~
/rocksdb/db/db_test_util.cc:73:12: error: 'rocksdb::SyncPoint' has not been declared
   rocksdb::SyncPoint::GetInstance()->ClearAllCallBacks();
            ^~~~~~~~~
/rocksdb/db/db_test_util.cc: In member function 'rocksdb::Options rocksdb::DBTestBase::GetOptions(int, const rocksdb::Options&, const rocksdb::anon::OptionsOverride&) const':
/rocksdb/db/db_test_util.cc:282:12: error: 'rocksdb::SyncPoint' has not been declared
   rocksdb::SyncPoint::GetInstance()->ClearCallBack(
            ^~~~~~~~~
/rocksdb/db/db_test_util.cc:284:12: error: 'rocksdb::SyncPoint' has not been declared
   rocksdb::SyncPoint::GetInstance()->ClearCallBack(
            ^~~~~~~~~
/rocksdb/db/db_test_util.cc:459:16: error: 'rocksdb::SyncPoint' has not been declared
       rocksdb::SyncPoint::GetInstance()->SetCallBack(
                ^~~~~~~~~
/rocksdb/db/db_test_util.cc:464:16: error: 'rocksdb::SyncPoint' has not been declared
       rocksdb::SyncPoint::GetInstance()->SetCallBack(
                ^~~~~~~~~
/rocksdb/db/db_test_util.cc:469:16: error: 'rocksdb::SyncPoint' has not been declared
       rocksdb::SyncPoint::GetInstance()->EnableProcessing();
                ^~~~~~~~~
/rocksdb/db/db_test_util.cc: In member function 'void rocksdb::DBTestBase::MoveFilesToLevel(int, int)':
/rocksdb/db/db_test_util.cc:972:17: error: 'class rocksdb::DBImpl' has no member named 'TEST_CompactRange'; did you mean 'CompactRange'?
       dbfull()->TEST_CompactRange(l, nullptr, nullptr, handles_[cf]);
                 ^~~~~~~~~~~~~~~~~
/rocksdb/db/db_test_util.cc:974:17: error: 'class rocksdb::DBImpl' has no member named 'TEST_CompactRange'; did you mean 'CompactRange'?
       dbfull()->TEST_CompactRange(l, nullptr, nullptr);
                 ^~~~~~~~~~~~~~~~~
/rocksdb/db/db_test_util.cc: In member function 'void rocksdb::DBTestBase::DumpFileCounts(const char*)':
/rocksdb/db/db_test_util.cc:982:21: error: 'class rocksdb::DBImpl' has no member named 'TEST_MaxNextLevelOverlappingBytes'
           dbfull()->TEST_MaxNextLevelOverlappingBytes());
                     ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
/rocksdb/db/db_test_util.cc: In member function 'void rocksdb::DBTestBase::GenerateNewFile(int, rocksdb::Random*, int*, bool)':
/rocksdb/db/db_test_util.cc:1023:15: error: 'class rocksdb::DBImpl' has no member named 'TEST_WaitForFlushMemTable'; did you mean 'WaitForFlushMemTable'?
     dbfull()->TEST_WaitForFlushMemTable();
               ^~~~~~~~~~~~~~~~~~~~~~~~~
/rocksdb/db/db_test_util.cc:1024:15: error: 'class rocksdb::DBImpl' has no member named 'TEST_WaitForCompact'
     dbfull()->TEST_WaitForCompact();
               ^~~~~~~~~~~~~~~~~~~
/rocksdb/db/db_test_util.cc: In member function 'void rocksdb::DBTestBase::GenerateNewFile(rocksdb::Random*, int*, bool)':
/rocksdb/db/db_test_util.cc:1035:15: error: 'class rocksdb::DBImpl' has no member named 'TEST_WaitForFlushMemTable'; did you mean 'WaitForFlushMemTable'?
     dbfull()->TEST_WaitForFlushMemTable();
               ^~~~~~~~~~~~~~~~~~~~~~~~~
/rocksdb/db/db_test_util.cc:1036:15: error: 'class rocksdb::DBImpl' has no member named 'TEST_WaitForCompact'
     dbfull()->TEST_WaitForCompact();
               ^~~~~~~~~~~~~~~~~~~
/rocksdb/db/db_test_util.cc: In member function 'void rocksdb::DBTestBase::GenerateNewRandomFile(rocksdb::Random*, bool)':
/rocksdb/db/db_test_util.cc:1048:15: error: 'class rocksdb::DBImpl' has no member named 'TEST_WaitForFlushMemTable'; did you mean 'WaitForFlushMemTable'?
     dbfull()->TEST_WaitForFlushMemTable();
               ^~~~~~~~~~~~~~~~~~~~~~~~~
/rocksdb/db/db_test_util.cc:1049:15: error: 'class rocksdb::DBImpl' has no member named 'TEST_WaitForCompact'
     dbfull()->TEST_WaitForCompact();
               ^~~~~~~~~~~~~~~~~~~
CMakeFiles/testutillib.dir/build.make:62: recipe for target 'CMakeFiles/testutillib.dir/db/db_test_util.cc.o' failed
make[2]: *** [CMakeFiles/testutillib.dir/db/db_test_util.cc.o] Error 1
CMakeFiles/Makefile2:3570: recipe for target 'CMakeFiles/testutillib.dir/all' failed
make[1]: *** [CMakeFiles/testutillib.dir/all] Error 2
Makefile:138: recipe for target 'all' failed
make: *** [all] Error 2

@Srogozins
this problem is related to rocksdb (https://github.com/facebook/rocksdb/issues/2445)
you should try to checkout specific branch.
git checkout v5.4.6

OK, looks like I'm finally able to get it working, thanks for the assistance.
If you fix . bin/active to . bin/activate and granted that facebook/rocksdb fix their master soon-ish, I think it will be OK to close this issue, then.

now it works with latest rocksdb.

authors: Srogozins twmht

repo: twmht/python-rocksdb


text:
The ComboBox widget doesn't work

It's problem with JS
utils.js:109 Error: Could not create a view for model id ec623906-2e27-47d2-b738-75d89ebeab62
    at promiseRejection (utils.js:109)
    at <anonymous>
promiseRejection @ utils.js:109
utils.js:109 Error: Could not create view
    at promiseRejection (utils.js:109)
    at <anonymous>
promiseRejection @ utils.js:109
comboBoxWidget.js:39 Uncaught (in promise) TypeError: this.$select.combobox is not a function
    at child.render (comboBoxWidget.js:39)
    at manager-base.js:99
    at <anonymous>
comboBoxWidget.js:39 Uncaught (in promise) TypeError: this.$select.combobox is not a function
    at child.render (comboBoxWidget.js:39)
    at manager-base.js:99
    at <anonymous>

authors: EfimovVladimir michalgce

repo: twosigma/beakerx

license_source: bigquery


text:
taia 1.0 TODOs

@txpjs/qa

[ ] config 层
[ ] lint 层（默认好用的命令，同时支持用户自定义）

[ ] 命令收敛
[ ] 配置文件收敛

[ ] cli 层

[ ] 一键安装配置化
[ ] verifyCommit

认领 config 层

repo: txpjs/taia

license: MIT


text:
ability to skip paid tests on travis-ci

I haven't looked into this, so I don't know if there's an easy solution, but the cost of testing all the API services on every PR/merge is likely to get quite high over time. It's not really a concern for most of the APIs, which are in the $1/1,000 requests ballpark, but some are much more expensive--particularly Indico, which costs $6/1,000 requests. Although our usage will probably come down once we figure out the problem discussed in #272, aggregate costs will continue to rise as we add more APIs.
What we should probably do is add some triggering condition that allows us to only test paid APIs on request, or at least at regular intervals. It would be simple enough to probabilistically trigger the API tests within the travis config (e.g., randomly run them 10% of the time), but it would be nice to have something a little more predictable than that. The best-case scenario would be if there's an easy way to manually trigger only the API tests directly from a GitHub PR.

Note that this is partly independent of the issue raised in #237 (and solution in #270), as we'll still need some way to trigger/skip the API tests using the new py.test markers once #270 is merged.

repo: tyarkoni/pliers


text:
秒杀难以成功

最近秒杀脚本提交不了了，手动买还可以。😂对这个不是很懂。只是有时候返回json信息为空就抛异常了

最近是有点问题，时好时坏的，但是又找不到原因，不知道触发了后台什么拦截规则。

也许他们拜读了您的code，然后加了相应的判别机制👀

authors: liwenfaYoY tychxn

repo: tychxn/jd-assistant


text:
Is it possible to define testString for a google font?

I'm loading one character from one Google Font (character is "&" and the font is "Butterfly Kids"), and it's doing it successfully.
I'm guessing because I'm not loading any of the characters from the default test string, the script is showing the "wf-inactive" class, thinking it failed to load the font.
I've tried forcing the testString to be just "&". I've tried "&", "&", "%26" and "\u0026" and none of them seem to have any effect - but that makes sense as the documentation suggests this testString var is meant to work on custom font faces only. Would it be possible to make it work for other font sources (specially Google, as they're the only ones with a "text" parameter to only download a subset of the font?

Issue #224 looks like the same issue - apologies

repo: typekit/webfontloader


text:
Uniform case analysis for data cons with < 6 fields

Courtesy of @carymrobbins:
% ghci
GHCi, version 8.0.2: http://www.haskell.org/ghc/  :? for help
Loaded GHCi configuration from /Users/crobbins/dotfiles/.ghci
λ data Foo = Bar Int | Baz String deriving Show
λ foos = [Bar 2, Baz "hey"]
λ foos
[Bar 2,Baz "hey"]
λ data Thing = Spam Int | Eggs String deriving Show
λ :m + Unsafe.Coerce
λ things = unsafeCoerce foos :: [Thing]
λ things
[Spam 2,Eggs "hey"]

The above will cause a ClassCastException in the current version of Eta. By adding specialised classes StgConstrN for N = 0,...,6, we can actually make the above code work.

This unfortunately is not possible without breaking the class hierarchy we have setup which is actually quite useful (a class for the type and all the data constructors subclasses from that type). The best we can do if we really need this is using reflection to access the fields.

Yes, I was afraid that this would be a limitation of the JVM itself. Unless some new instruction allows for casting one class to another, we can't really convert a Bar to a Spam, and I don't foresee this being supported anytime soon.

Not exactly a limitation of the JVM, but how we chose to encode
data Greeting = Hello | Hi Int

This is generated as:
public abstract class GreetingT extends Value {}

public class HelloD extends GreetingT {}
public class HiD extends GreetingT {}

(Value is the parent classes of all evaluated data types in Eta, including functions.)
But we just as easily not generate these classes at all and could have just used generic, standard classes like below to instantiate an instance of Hello or Hi:
public class DataCon0 extends Value {}
public class DataCon1 extends Value {}

You can use DataCon0 when instantiating Hello or any nullary data constructor and DataCon1 when instantiating Hi or any data constructor with one boxed argument. You can have a whole range of these standard classes and only use those. And with this code generate style, you can implement this issue.
But the cost? Debugging becomes more painful and we lose type information at runtime. And we lose out on JVM's opportunity to optimise each call-site based on type information.
Right now, I can run VisualVM and know exactly which data types are being allocated frequently, etc., based on the class itself. With the alternative code generation, I lose of all of this.

Right, I actually meant it's a limitation if you use this sort of type hierarchy, which doing otherwise would make not only debugging and profiling more difficult, but interop with other languages would become pretty painful as well.

authors: carymrobbins rahulmutt

repo: typelead/eta


text:
Add ConfigDocument API

This work came out of the discussion in https://github.com/typesafehub/config/issues/272.
These commits add a new grouping of classes, ConfigNode, to the library, which are used to form an AST. This AST contains all the tokens from which it was parsed, so the original text can be reproduced from them.
I'm opening this up for review now as the implementation is complete, so I think that portion is ready for review. The testing code is rough right now, largely because of the difficulty involved with crafting instances of ConfigNodeComplexValue by hand, so I'm still working on improving that, although any feedback on that front is welcome.
This PR adds the ConfigDocument API in its entirety, including its backend representation with ConfigNodes, the ConfigDocument Parser, and the ConfigDocument Interface.

To avoid crafting complex nodes by hand, one approach would be to go ahead and implement the tokens-to-ConfigNode parser. That would also allow implementing a round-trip test that no tokens or formatting are lost in the parsing process and that the ConfigNode type hierarchy is complete. (Round trip test means:  configNodeParser("any valid config stuff here").render().equals("any valid config stuff here") ... this can be tested for the files that are already in src/test/resources perhaps)
I think you could cut-and-paste Parser.java; the changes I see the need to make right away are:

you can drop all that TokenWithComments / attractsLeading/TrailingComments stuff and instead just generate comments nodes
generate nodes for, rather than discarding, tokens such as ignored whitespace and field separators
don't actually process includes, just make nodes for them
might want to split the path expression parsing stuff out of Parser.java into its own file so you can use it too

I think if your new parser doesn't have the TokenWithComments stuff and shares the path expression parsing stuff, it won't be that many lines of code, and the lines it has will be based on the Parser.java lines. Most of the verbosity in Parser.java is about nice error messages (which would indeed be nice to keep). Don't be afraid of cut-and-paste for the bulk of the parser, since we can clean that up later by making the existing Parser.java go from ConfigNode => ConfigValue instead of using tokens.

@havocp Yeah, I was thinking that implementing the parser would make testing easier, but I felt like there was still some value in directly crafting config nodes for tests.
I have some more tests of config nodes that I haven't pushed up yet. Do you want me to push those up? And would you prefer the Parser be added to this PR or a new PR? I was planning to add in the parser in a new PR after this was merged, but I can add it into this PR if you'd like.

@havocp I've added some more tests and will get to work on addressing your feedback, thanks!

I agree that some direct tests for the nodes are good too. I'm thinking it might be worth adding the parser here because I'm having trouble feeling we have the node API right without also having the parser and roundtrip tests.  What do you think?
What I would like to keep separate is the modification of Parser.java - mostly because that's when we risk breaking existing functionality. It would be nice if this PR is only adding new stuff, and then make it a separate step to unify with the old stuff.
(exception: maybe that path expression parser code can move into its own PathParser file, since that's hopefully just a simple move.)

@havocp Hmm, that makes sense to me. This feature isn't really finished without the Parser, so if they get merged separately, we'll have an incomplete, in-progress feature in the repository. I'll address your feedback, then get to work on the new Parser. I'll add it as a commit to this PR once it's ready to be reviewed.

@havocp I've just pushed up a new commit addressing most of your feedback. In regards to the path changes, I'm getting to work on that now, and will push that up in a separate commit.

@havocp I've pushed up a new commit that saves the Tokens in Paths produced by Parser.parsePath. It should be ready for review, so any feedback is much appreciated!

Looking better all the time, I appreciate the work on this. I think it's turning out to be fairly simple, maybe more so than I expected... not a common experience in software development :-) yay!

@havocp we owe you a beer for all your help on this! :)

@havocp I've addressed your comments, and have also extracted the Path Parsing into a new class. Let me know what you think!

@havocp Quick question: for the new Parser, should I be keeping the logic that throws errors if the parsed text does not conform to JSON? Or should we ignore that in the ConfigDocumentParser, and let the current Parser handle it when it grabs config nodes from the ConfigDocumentParser?

I think when loading a document you might want to require it to be JSON-conforming, so maybe the doc parser should be able to check JSON conformance too.

@havocp @cprice404 I've just pushed up my implementation of the parser if either of you want to take a look. It can parse a file into a ComplexConfigNode and render that file back out exactly as it was rendered in.
I don't have a ConfigDocument class implemented yet, that's coming next. Once that's implemented, I'm going to add ConfigDocument tests that test replacement and rendering (since ConfigNodeComplexValue does the lion's share of the work, I doubt a ConfigDocument implementation will take me long at all).
I've put this up now as I feel it's ready for review. Hopefully I'll have the ConfigDocument changes up by some point tomorrow, at which point this PR will have all it needs for final review/merge.

@havocp The Parser is finished, and is now ready for review. Any feedback (especially on test coverage) is welcome!

fantastic! I'm at scala days right now and iPhone-only most of the day, so my review may be lagged as late as next week, but I will try to take a first pass this evening or throw in a few impressions via iPhone.
One thing you can do is run jacoco:cover (do "project config" first I think to enter the config subproject). then look at the generated html report under config/target.
I haven't looked at the code yet but another idea would be to share all applicable tests with the old parser, for example they should probably throw most of the same errors.
you can also run findbugs which may turn up a couple small issues, or not. sometimes it does.

Were there any interesting changes or decisions porting the old parser to generate nodes?

Thanks! I'll look into those approaches, probably once I get the ConfigDocument stuff pushed up.
There weren't a ton of super noteworthy changes, it was pretty easy to modify the Parser to create nodes. Mostly I was able to simplify things quite a bit and cut out a number of methods, which was nice, it was a pretty fun exercise.

Okay, got the ConfigDocument stuff written along with some tests. This is ready for final review, I think.
The only problem I know of now is adding a new path in JSON files. This is tricky because of the way JSON works, as all keys need to be quoted. What's happening with CONF files is the path is just being added at the top level, so if you give it path a.b.c, and it doesn't see that path anywhere in the file, it'll just add a.b.c=[value] to the top level. This is not valid in JSON, as all paths need to be quoted, and we can't just add a quote around the path when adding a new path to a JSON input because if we were replacing a value with a multi-element path, we'd add path "a.b.c" instead of a.b.c, and those are different.
I think the path replacement is going to have to be modified somehow. I can think of three approaches:

We don't support adding a new path in JSON if it's not a single-element path.
We support adding all new paths in JSON, but when we add a multi-element path, we quote the entire thing, turning it into a single-element path.
Instead of adding the path at the top level, we move down through the tree until we find the object where only a single-element path remains, and add the value into that object with the necessary key. I definitely think this is the best approach. So if we had the map

{a: b
 c: {
   d: e
 }

And set value 12 at path c.f, we'd get the following map:
{a: b
  c: {
    d: e
    f: 12
  }

In this case, if there does not exist an object wherein the remaining path is single-element, then we'd add the full path to the top level of the map in the case of parsing a CONF file, or throw an exception in the case of a JSON file. So, if in the above example, we wanted to set value 12 at path c.f.g, an exception would be thrown if the file were JSON, but we'd get the following if it were a CONF file:
{a: b
  c: {
    d: e
  c.f.g: 12
}

I'm thinking the third approach would be best, especially now that I've put it down into writing and can see that it probably won't be very hard to accomplish at all.
@havocp How does this sound to you? Would you prefer a different approach?

I like the third approach. To be clear, we would throw if we try to set a field in a non-object right, but if we try to set a field in a path that doesn't exist we could auto create the parent object I would think?

so right now the public ConfigNode is useless right (there's no way to get one?)
That's fine and even good (would be nice to get this basic document with set value thing done, then look at public nodes later, I don't know if you even want that).
But wanted to clarify.

In terms of the value setting, yeah, I think we could definitely create the parent object if it doesn't exist. I think it will be tricky, though, to figure out which level on which to create the parent object and the indentation for the parent object/new setting.
And yeah, right now there's no way to use the public ConfigNode. I'm thinking we can add that in a subsequent PR.

I would think maybe it'd be alright to not worry about indentation for the first pass at this?

@cprice404 That's a good point, that can probably be added in a subsequent PR. If we're just worrying about adding the parent object, this should be quite a bit easier to implement.
I'll work on modifying the value adding so it creates the parent object if it doesn't exist. I think that'll be pretty easy if we're not worrying about indentation, so hopefully I'll have something ready in the next couple hours.

ignoring indentation seems fine to me as a first cut, go for it.

Okay, I've fixed up the field addition. Now, all non-existent objects along the path will be created, and when the ConfigDocument was parsed from a JSON document, the resultant ConfigDocument will render valid JSON.

I've updated the title, since this is now in a state where I feel it is ready for a full review with the intent of being merged.

I'm currently working on a new PR on top of this current one to refactor the current parser to use the new parser. Some internal implementation details will be changed, but the results of the public API as it stands in this PR will not be changing, so this should still be good for merging.

apologies for being slow here, have been traveling and so on.
I'm thinking there might be some work to make the ConfigNode subtypes a little more "semantic," like have nodes for includes and comments and so on. I'd think the public API has stuff like ConfigNodeComment rather than ConfigNodeSingleToken. The old parser then would do very little (drop purely syntactic nodes, process includes, ...)
Is that part of what you're doing now or does it not make sense ?

@havocp Yeah, that's part of what I'm doing now for the subsequent PR. If you'd like I can merge what I've done (minus the Parser changes) into this PR.

Also, no problem on the response time! We know you've been busy with Scala Days and such. :)

It's fine to keep it separate; I'll get this one merged. I don't think I have any more substantive comments on this PR I just wanted to at least read all the code.

@havocp Great! Let me know if you have any feedback, I'm happy to make any more changes you think are necessary (particularly in regards to test coverage).

@havocp I noticed you had given me some feedback around the ConfigDocument that I hadn't addressed yet, I pushed up a new commit that addresses it.

The test coverage looks reasonable to me, I'm also thinking that once you port the existing parser to use this one, we'll get a ton of coverage "for free" from all the existing tests.

the only outright bug I saw was the !=/equals thing, so unless I'm confused there we should probably fix it. otherwise, I've been through this code and it looks good to merge.

@havocp Great! I'll go through and address your last bits of feedback, hopefully it won't take long

Thanks for the review!

throwing on any kind of stuff (comments, whitespace, concatenation not supported by JSON) around the value in setValue makes sense to me, because otherwise it gets into all kinds of thorny issues where we can have multiple trees possible for the same rendered file.

@havocp Alright, I'll get to work now on making a new simple value class that is multi-node to contain whitespace/comments, which will be used solely in the case of setting a value.

I was trying to say don't do that - I don't think we want the whitespace/comments to be part of the value node sometimes, and part of the parent node sometimes. Also, I don't think we want setting a value to be non-idempotent. Instead, setValue could give up and throw if there's any "extras" around the value. That way we can punt on all the semantics of whitespace/comments.

Ah, sorry, misunderstood what you were saying! That should be a fairly quick fix.

@havocp Alright, I've addressed your last few comments!

Merged, thanks very much!

source: gharchive/pull-request

authors: cprice404 fpringvaldsen havocp

repo: typesafehub/config


text:
add: support for update collections

Change Summary
add: support for update collections
fix: document update returns 200 not 201 code.
PR Checklist

[x] I have read and signed the Contributor License Agreement.

do you want me to regenerate this from the updated spec before merging?

I presumed this was already generated after the changes in https://github.com/typesense/typesense-api-spec/pull/26 -- was it done before?

It was, I didn't see the spec was out of date until after. I'm regenerating now, will squash and rebase

@kishorenc done

repo: typesense/typesense-go


text:
syntree:0.1.0

I am submitting

[x] a new package
[ ] an update for a package

I have read and followed the submission guidelines and, in particular, I

[x] selected a name in conformance with the guidelines
[x] added a typst.toml file with all required keys
[x] added a README.md with documentation for my package
[x] have chosen a license and added a LICENSE file or linked one in my README.md
[x] ensured that my submission does not infringe upon the rights of a third party
[x] tested my package locally on my system and it worked
[x] named this PR as name:version of the submitted package
[x] agree that my package will not be removed without good reason

Description: this package can lay out textual trees, such as syntax/parse trees used by linguists. It also provides a wrapper to generate such trees from a concise DSL.
#tree("NP", tree("Det")[a], tree([N$'$], roof: true)[simple example])
#syntree("[NP [Det a] [^N$'$ simple example]]")

Thank you!

authors: laurmaedje lynn

repo: typst/packages


text:
smooth-tmlr:0.3.0

I am submitting

[x] a new package
[ ] an update for a package

Description: Explain what the package does and why it's useful.

I have read and followed the submission guidelines and, in particular, I

[x] selected a name that isn't the most obvious or canonical name for what the package does
[x] added a typst.toml file with all required keys
[x] added a README.md with documentation for my package
[x] have chosen a license and added a LICENSE file or linked one in my README.md
[x] tested my package locally on my system and it worked
[x] excluded PDFs or README images, if any, but not the LICENSE

[x] ensured that my package is licensed such that users can use and distribute the contents of its template directory without restriction, after modifying them through normal use.

Thanks for another great template!

authors: daskol laurmaedje


text:
Typst not rendering report entry with genre while Hayagriva do

Description
I was unable to get typst to render the following references correctly, and the outcome differs from that of hayagriva.
The good way is to print genre for reports and thesis.
Minimum reproducible example
Here is the refs.yaml:
Awesome_Tech_Report:
  type: report
  title: "My Awesome Tech Report"
  author:
    - First, Author
    - Second, Author
  date: 2023
  genre: Tech. Report
  publisher: My Lab, My University
  serial-number:
    doi: 10.48550/arXiv.2312.xxxxx

Here is the hayagriva code:
use hayagriva::io::from_yaml_str;
use std::fs;
use hayagriva::{
    BibliographyDriver, BibliographyRequest,
    CitationItem, CitationRequest,
};
use hayagriva::citationberg::{LocaleFile, IndependentStyle};

fn main() {
    let yaml = fs::read_to_string("tests/data/refs.yml").unwrap();
    let bib = from_yaml_str(&yaml).unwrap();

    let en_locale = fs::read_to_string("tests/data/locales-en-US.xml").unwrap();
    let locales = [LocaleFile::from_xml(&en_locale).unwrap().into()];

    let style_file = fs::read_to_string("tests/data/ieee.csl").unwrap();
    let style = IndependentStyle::from_xml(&style_file).unwrap();

    let mut driver = BibliographyDriver::new();

    for entry in bib.iter() {
        let items = vec![CitationItem::with_entry(entry)];
        driver.citation(CitationRequest::from_items(items, &style, &locales));
    }

    let result = driver.finish(BibliographyRequest {
        style: &style,
        locale: None,
        locale_files: &locales,
    });

    for bibentry in result.bibliography.unwrap().items {
        println!("{}", bibentry.content)
    }
}

With the following output:
A. First and A. Second, “My Awesome Tech Report,” My Lab, My University, Tech. Report, 2023. doi: 10.48550/arXiv.2312.xxxxx.
And here is my typst code:
#page(width: auto, height: auto, margin: 2em)[
  Here is the cite @Awesome_Tech_Report

  #bibliography("tests/data/refs.yml", title: text("Here is the bibliography"), style: "tests/data/ieee.csl")
]

with the following result :

System
cargo -V: cargo 1.76.0 (c84b36747 2024-01-18)
uname -srvm: Linux ashton-laval 5.14.0-1057-oem #64-Ubuntu SMP Mon Jan 23 17:02:19 UTC 2023 x86_64
hayagriva -V: Hayagriva CLI 0.5.2
typst -V: typst 0.10.0 (70ca0d25)

My current workaround is to put the genre in the publisher because, in ieee style, those two pieces of informations are close together.

Every type doesn't have every field, and even when they do, a style doesn't have print all of them. I doubt this is an actual bug.

I am pretty sure genre is required in these cases.
Here is ieee csl style for report followed by thesis
        <else-if type="report">
          <group delimiter=", " suffix=".">
            <text macro="title"/>
            <text macro="publisher"/>
            <group delimiter=" ">
              <text variable="genre"/>
              <text variable="number"/>
            </group>
            <text macro="issued"/>
          </group>
          <text macro="access"/>
        </else-if>
        <else-if type="thesis">
          <group delimiter=", " suffix=".">
            <text macro="title"/>
            <text variable="genre"/>
            <text macro="publisher"/>
            <text macro="issued"/>
          </group>
          <text macro="access"/>
        </else-if>

Anyway why would hayagriva and typst would have two different outputs for the same reference and style when the latter use the former to render bibliographies ?

I have a similar problem: I can't seem to get the genre's value in CSL in bib file.
...
  <bibliography>
    <layout>
      <text macro="citation-number" />
      <choose>
        <if type="book" match="any">
          <text variable="title" />
          <text variable="genre" />
        </if>
      </choose>
    </layout>
  </bibliography>
...

@book{1,
  title = {Any title},
  genre = {tutorial},
}

I can't use subtitle because it's not defined in CSL, but genre is: https://docs.citationstyles.org/en/stable/specification.html#standard-variables. So is title. And since title is printed and genre isn't, it has to be a bug.
genre.zip

It looks like archive and part-title don't work as well. But abstract and annote do. How much more of them are not usable?

As a "temporary" workaround I added this:
  <macro name="genre">
    <group prefix=": ">
      <choose>
        <if variable="genre">
          <text variable="genre" />
        </if>
        <else>
          <text variable="annote" />
        </else>
      </choose>
    </group>
  </macro>

I can reproduce this in Typst 0.10, but not in Typst 0.11, so looks like it's fixed already.

Can confirm that archive, abstract, annote, title, and genre fields are working in v0.11.0, but part-title still isn't.

authors: Andrew15-5 Enivex halsimov laurmaedje

repo: typst/typst


text:
🛑 (dev) Monitor / services is down

In 36a2d9a, (dev) Monitor / services ($DEVELOPMENT_TYREPHARM/local/api/Monitor/services) was down:

HTTP code: 0
Response time: 0 ms

Resolved: (dev) Monitor / services is back up in d8825ca.

repo: tyrepharm/upptime-test


text:
选中的tab，不能在修改tab样式

tab被选中后，再次点击选中的tab时，虽然有监听，但是并不能再次对选中的tab的文字图形样式在进行修改了，建议添加个监听，可以在SpecialTab中进行自定义已选中的tab样式

确实，对于自定义可能更加方便。我会在下一个小版本中添加这个方法

2.2.5版本添加了一个回调

authors: AlvinQiang tyzlmjj

repo: tyzlmjj/PagerBottomTabStrip


text:
Allow whitelisting languages

Currently the configuration allows settting ignored_file_types. Is it possible to allow a whitelist (could for instance be called allowed_file_types) of languages for which tabnine is only enabled for, and disabled for all other languages?

This would be unelegant. Having both an allow list and a disallowed list is ungainly.
I think a better option would probably be to change it to a callback, such that each user can implement what works for him.

I personally don't agree that having a whitelist and a blacklist is unelegant, but I adding a callback is fine with me too :)

Having both, the logic gets comicates fairly quickly. Also, documenting the
order of preference between the lists would confound new users.
On Thu, 2 Dec 2021, 16:18 Melker Österberg, @.***>
wrote:

I personally don't agree that having a whitelist and a blacklist is
unelegant, but I adding a callback is fine with me too :)
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/tzachar/cmp-tabnine/issues/26#issuecomment-984668393,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABFXXC7BQ4JLOY42Y5MXELDUO552DANCNFSM5JG6DUOA
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

Take a look at this.
You can set up a per buffer configuration, based on anything you want. This is supported upstream.
I think I will also remove the blacklist.

@tzachar Thanks, that worked for me!

authors: Melkster tzachar

repo: tzachar/cmp-tabnine


text:
cmp-tabnine: Cannot find installed TabNine. Please run install.sh

When starting nvim I get this cmp-tabnine: Cannot find installed TabNine. Please run install.sh
Installing plugins through packer
Running:
Nvim: 0.8.0
macOS: 12.6.1
iTerm2: 3.4.16 (this error appears in the default terminal as well)
zsh: 5.8.1

As the message says, try running the install.sh script by hand.

authors: alanmicah tzachar


text:
dlib compiling error round

I tried to compile it using NDK-build but received following error:
jni/../dlib\dlib/image_loader/../image_transforms/random_cropper.hjni/../dlib\dlib/image_loader/../image_transforms/random_cropper.h::178178::6767::  error: noerror : member nonamed  member'round'  namedin  'round'namespace
in       'std'namespace
              const unsigned long min_object_height_absolute = std::round(min_object_height*crop_plan.rows);'std'

                                                         ~~~~~^            const unsigned long min_object_height_absolute = std::round(min_object_height*crop_plan.rows);

                                                         ~~~~~^

Anyone know how can I fix it?

Which OS are you compiling on?

Windows 10

Sorry, I cannot help you... unless you use Ubuntu!
I also have Windows 10 but compiled it on Ubuntu 16.10 Virtual Machine running on Win10

I actually have an Ubuntu Virtual Machine too. I guess I will just do it on there then...

Yes, please close this issue and ask me any questions regarding to compilation to my mail: ezequieladrianm@gmail.com
So we keep this thread clean :)

authors: EzequielAdrianM ethanyuwang

repo: tzutalin/dlib-android

license: mit


text:
🛑 Grafana is down

In 74a1a0f, Grafana (https://g.uvvu.pw) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Grafana is back up in c0ddbb1.

repo: u-v-v-u/status


text:
Remove reliance on nonexistent UDP binding return code.

Good find! bind does at least throw an exception if an error occurs? :$
:+1:

bind is supposed to reject if there's a problem, yes.  This is already true in Chrome, and soon will be in Firefox too: https://github.com/freedomjs/freedom-for-firefox/pull/71

authors: bemasc trevj

repo: uProxy/uproxy-lib


text:
Copy change to contact headers

Change "Trusted uProxy friends" to
"Friends you can get access from" on the Get tab and
"Friends who can get access from you" on the Share tab
@gwpenn – anything else to add?

Looks good! We may also want to change the category below trusted to "Other friends running uProxy."

We're going to go with "Friends you trust" for the get tab because they are moved to that category as soon as you request access. (So it's not automatically true that they are friends you can get access from.)

I'm fine with that for this push, but would really love to the model/headers above when we're under less of a tight deadline.
@lucyhe how much work do you think it would take to make it so that contacts are moved to the sections above after each party has established trust?

It shouldn't take too long at all. The argument for a "Friends you trust" category though, is that as soon as you interact/request access from your friend, they will be bumped to the top of your contact list. @dborkan and I were unsure about keeping your friends in the "other" list if you've already acknowledged you'd like to get access from them and you are waiting for their response; do you think that would be preferable?

I don't think "Friends you trust"/all contacts is a helpful differentiation for users. Users will find it more helpful to be able to easily differentiate who you can get access from and who you can't.

Okay, sounds good to me, but lets also discuss tomorrow!

Izzie to update bug with iconography

See #875 for mocks

Re-pasting collapsed/expanded states below:

When contact is expanded, we will no longer have iconography in the expanded section as it is currently:

authors: gwpenn lucyhe zahoriea

repo: uProxy/uproxy


text:
Fix scoping for chrome notifications event

This also renames trigger to emit for chrome_browser_api
Fixes #1343

:thumbsup: from @iislucas


text:
Updated gruntfile and index.html to build uProxy on ios

Updated cca/app/index.html by uncommenting
Updated Gruntfile by adding correct commands to build ios; now you can use 'grunt build_ios' or 'grunt emulate_ios' to run uproxy on ios

:+1:

authors: bemasc gitlaura


text:
Added Scala 2.12.1 for crossbuilding. Fixed dependencies as necessary.

Addresses issue: https://github.com/ua-parser/uap-scala/issues/13

@humanzz @aoiroaoino @orendain Is this library still maintained?

@vitorsvieira I'm successfully using uap-scala, though don't have enough bandwidth to track down and patch the failed test.  I'm not sure if the project as a whole is still actively maintained (or if it even needs it) - the day I submitted the PR was the first day I stumbled upon this repo.

@orendain @vitorsvieira I've taken a slightly different approach in #18.

Merged https://github.com/ua-parser/uap-scala/pull/18

authors: humanzz orendain travisbrown vitorsvieira

repo: ua-parser/uap-scala

license: WTFPL


text:
🛑 guacamole aules is down

In 031ba6e, guacamole aules (https://aules.sbd.uab.cat) was down:

HTTP code: 0
Response time: 0 ms

Resolved: guacamole aules is back up in 757c2c2.

repo: uab-dtic/sbd-uab-monitoring


text:
Update header with wireless link

Changed the "Connect to wireless" link in header to redirect to OIT's instructions on connecting to wifi.
It looks like a lot of commits, but everything has been reverted that isn't related to the header link change. 👍

I went ahead and ran grunt live-build even though this change only affects WP/PHP files-- just in case-- and we're all good to go.

repo: ualib-deploy/roots-ualib


text:
move static asset to public instead of storage

Problem

s3 does not know  about media asset on storage

use Storage::get() instead

repo: uasoft-indonesia/badaso


text:
sphereElectrostatic_example

the code to run the electrostatic sphere example (https://github.com/simpeg/simpeg/blob/a9c9ce6bc8658317f3ad3e763b44cdc9db884f29/SimPEG/Examples/sphereElectrostatic_example.py) should be included in util_codes and the associated notebook updated to import the necessary code from there.
This replaces the issue ubcgif/em#159

#7

authors: lheagy thast


text:
particle demo

@ibgreen @mikolalysenko
Adds a particle demo for #24
gif: http://i.imgur.com/kMZWjNd.gifv
Screenshot:

For the record this looks really cool.

@Qix- Thanks for the review and kudos. :+1: :grinning:

authors: Qix- wwwtyro


text:
Multilingual support

Hi, is Plato good for multilingual support? Has there been any successful samples/ use cases?
Thanks!

Hi, as Plato is a generic framework, I don't see why it wouldn't work for multilingual applications. Hopefully we can add a tutorial soon!

authors: apapangelis jinmingteo


text:
Security test, please do not approve a wadyrh

Security test, please do not approve a wadyrh

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

authors: CLAassistant magnumfistuk

repo: uber/cadence-idl


text:
Add initial support for custom SQL TLS configuration

This is an attempt to add support for TLS MySQL (we use RDS/Aurora and require TLS support) using the recently added TLS support for Cassandra. In the process it reuses the config in persistence for use in tools and removes ConnectParams.
For the cli you can use env:
SQL_TLS=1 SQL_TLS_CA_FILE=./my-ca-file.pem SQL_CONNECT_ATTRIBUTES="tx_isolation=READ-COMMITTED" ./cadence-sql-tool ...

or command flags:
./cadence-sql-tool ... --tls --tls-ca-file ./my-ca-file.pem --plugin mysql --connect-attributes "tx_isolation=READ-COMMITTED" create ...

And tls: can now be used in config.yaml for running cadence-server
Feedback is welcome!
_Closing previous attempt, which was before major refactor related to postgres support:
https://github.com/uber/cadence/pull/2841_

Coverage decreased (-0.1%) to 67.886% when pulling 0e1689b71235fb8374bc526e325dbe177bedd9fc on bjacobso:ben/enable-mysql-tls into 0325021abd23a73d589587e49650c6d677f4290f on uber:master.

@venkat1109 I believe I addressed all your comments from my last PR
@longquanzheng indeed this was a lot easier after your postgres changes, thanks!

Thoughts this change @venkat1109 and @longquanzheng?

@bjacobso First of all thanks for this PR . I have 2 immediate questions here.

If the certificate is signed and its not same as hostname how the user can configure it.
If the user specifies the reserved config values i.e. one of ["skip-verify", "preferred", "true", "false"] what should be the behaviour?

@PankajWorks

If the certificate is signed and its not same as hostname how the user can configure it.

It looks like my PR doesn't take this into account unfortunately. Are you referring to this:
https://github.com/uber/cadence/pull/2974/files#diff-460ccb997687fa1effc1307704bde981R215-R217
You would need to add a host option to the TLS struct here:
https://github.com/uber/cadence/pull/2913/files#diff-6dc12e8c80a8118bbc5213ff428682c3R38

If the user specifies the reserved config values i.e. one of ["skip-verify", "preferred", "true", "false"] what should be the behaviour?

In this case that value will take precedent and the TLS configuration won't be used. Currently this doesn't return an error or anything it will just be registered but not used.

@bjacobso it will good to have an variable for ServerName to override with.

authors: PankajWorks bjacobso coveralls

repo: uber/cadence


text:
Fix redispatch queue initialization

What changed?
Fix redispatch queue initialization

Coverage decreased (-0.03%) to 67.147% when pulling 04f183ec7e1569832afe5b7fb928e369ab756221 on yycptt:fix-redispatch-init into 9367197688a4a0a4a8fc8495f2ff4a4218a132d2 on uber:master.

authors: coveralls yycptt


text:
Views not contained inside canvas element

Description
When setting up a simple test case for a Deck.gl implementation, the rendered view is not contained inside the canvas.

Repro Steps
My code:
import DeckGL, { MapView } from 'deck.gl';
import React from 'react';
import { _MapContext as MapContext, StaticMap, NavigationControl } from 'react-map-gl';

function AssetMap() {
  const [coordinates, setCoordinates] = React.useState({ longitude: -74.006, latitude: 40.7128 });
  const [zoom, setZoom] = React.useState(12);

  return (
    <DeckGL
      ContextProvider={MapContext.Provider}
      views={[new MapView({ id: 'default-view', width: '100%', height: '100%' })]}
      viewState={{
        ...coordinates,
        zoom,
      }}
      id="asset-map"
      height="90vh"
      width="100%"
      controller={true}
      onViewStateChange={(data: any) => {
        const { latitude, longitude } = data.viewState;

        setCoordinates({ latitude, longitude });
        setZoom(data.viewState.zoom);
      }}
    >

        <NavigationControl />

      <StaticMap
        height="100%"
        width="100%"
        mapStyle="mapbox://styles/mapbox/streets-v11"
        mapboxApiAccessToken="pk.eyJ1IjoiY2FsbGFyaWRlIiwiYSI6ImNqeWlvZ2ljODA0YWgzbm82d2FxM3BoeGIifQ.VgvqmFDyg4joDqMGtQJaDQ"
      />
    </DeckGL>
  );
}

export default AssetMap;

Environment (please complete the following information):

Framework Version: 7.3.2

@reinvanimschoot , it does show the static map in your images correctly (with map box logo), also I don't see you are rendering any layers, i.e. no layers props for DeckGL. And also don't see any issues with DeckGL props. What is expected here?
Another thing, by providing viewState you will not be using deck.gl internal viewState, instead you can provide initialViewState, docs here.

@1chandu The problem is that even though I tried changing the styling of the Deck/View/StaticMap, it still renders an absolute positioned element that is hidden behind the top header and drawer menu on the side. I cannot seem to get rid of that inherent styling.
And I noticed in the elements tab that the two views that are rendered are not children of the canvas element but siblings. Not sure if that should be the case? The canvas element itself is correctly rendered and displayed but the views don't care about that styling and are still rendered in the top left corner.

If the question is , how to position your view at an offset (w.r.t to top-left corner), you can specify x and y (absolute number or %) for your view object
      views={[new MapView({ id: 'default-view', x: 25, y: '10%', width: '100%', height: '100%' })]}

That's not the problem.
The problem is that none of the children of the div with the deckl-wrapper are actually contained inside of it since they are all absolutely positioned.
I want the canvas and the default view to respect the size of the deckgl-wrapper div, not be stuck behind my header with no way of controlling the style.

Mind you, even when I added width and height to the deck-gl wrapper in the browser, I still need to set both the canvas and the view to relative positioning, which is not something I can seem to do through code.

The style of deckgl-wrapper is managed internally. You need to place DeckGL in another div whose style you can control.

I tried to do this in our app and it only by changing the positioning to relative in the wrapping div it seems to be breaking our map and resulting in the warning: luma: Device pixel ratio clamped. When we add the wrapper style the deck component seems to break, a map shows up but with no controls, no viewport and not added layers.

      <DeckGL
        layers={renderLayers({
          data: getRuns(geo),
          selected:props.selection,
          onHover: hover => _onHover(hover)})}
        getCursor={() => hover.hoveredObject ? 'pointer' : 'default'}
        initialViewState={INITIAL_VIEW_STATE}
        controller={true}
        onClick={(click) => _onClick(click)}
      >
        <StaticMap
          mapboxApiAccessToken={MAPBOX_TOKEN}
          mapStyle={MAPBOX_STYLE} />
      </DeckGL>

```

any idea why the wrapping styling would be breaking the deck component?

We can't reproduce this issue from your description. Here are some suggestions:

Report the deck.gl version that you are using
Screenshots
A Code Sandbox example that reproduces your issue

I seemed to fix it in our project by constraining the wrapping div with its own height and width instead of its parents but I have it replicated hear if you wanted to see the assertion error it's causing. Probably just a stupid mistake on my part as I'm still getting the grips on DeckGL.  https://codesandbox.io/s/deckgl-c5lg7

authors: 1chandu Pessimistress aaronsamkennedy reinvanimschoot


text:
Async Props RFC: LayerState class introduction (Stage 1)

This is a slightly simplified version of the layer state class PR that was previously approved for 6.0, now proposing for for 5.2.

Refer to #1418


text:
Rotate EEF over 90 degrees (as the stage name says)

As per subject.
Stage was named "rx +90°" but rotated over 45 degrees.

Great. Thanks!

authors: gavanderhoorn rhaschke


text:
Allow Custom Data attributes

Overview

Allows custom data attributes to be specified
Additional examples specified in Stories.
The props that are not explicit in the component are received together and given to the element together with the spread operator

@8845musign please resolve conflicts 🙏

repo: ubie-oss/ubie-ui


text:
No Linting in the YAML Action File

It looks like the YAML file doesn't lint commits to the repository. Is this correct? If so will we be adding this feature? I only ask so I can write the documentation a little bit and explain the process of linting with actions

I do think so. How can we add this feature?  Any suggestion on this?

I don't understand the question. Can you please explain?

I did the pylint for algorithm and have resolved few issues ( not all).


text:
Update deprecated APIs for Chisel 5 update

Note that this is not compatible with Chisel 3.6.0.

@milovanovic / @jerryz123 are you able to take a look at this MR? Not sure if this project wants to move forward with merging these changes now, but I'd love to know what the path forward is for moving to Chisel 5+. Thanks!

@tymcauley I found this does not break compatibility with chisel3.6 (I'm planning an incremental upgrade to chisel6 right now).

repo: ucb-bar/rocket-dsp-utils


text:
How to add Pod Annotations for redis pods

Hi All,
Actually  we are using distributedRedisCluster object with 3 masters and 3 replicas .As we have single file redis DistributedRedisCluster file. Now we want to add some labels and Annotations to redis pods which are created. How can we do that?

If I add annotations and labels in DRC file . It is applied to DRC object , I want it to be applied to individual redis pods

If I understand the logic of the code correctly, it is currently possible to set the pod label via the label of the drc object, but not the annotation.

repo: ucloud/redis-cluster-operator


text:
Issue 543: Designate ObservablePattern a subclass of Pattern, adding namespace import

This Pull Request resolves all requirements of Issue #543 .
Coordination

[x] Pull Request is against correct branch
[x] Pull Request is in, or reverted to, Draft status before Solutions Approval vote has passed
[x] CI passes in UCO feature branch against develop-2.0.0
[x] CI passes in UCO current unstable-2.0.0 branch (65cc8a8)
[x] CI passes in CASE current unstable-2.0.0 branch tracking UCO's unstable as submodule (6e89872)
[x] Impact on SHACL validation reviewed for CASE-Examples
[x] Impact on SHACL validation remediated for CASE-Examples (N/A)
[x] Impact on SHACL validation reviewed for CASE-Corpora
[x] Impact on SHACL validation remediated for CASE-Corpora (N/A)
[x] Impact on SHACL validation reviewed for casework.github.io
[x] Impact on SHACL validation remediated for casework.github.io (N/A)
[x] Milestone linked
[x] Solutions Approval vote logged on corresponding Issue (N/A) - bugfix proposal

Any member of @ucoProject/maintainers-uco may feel free to merge this PR.  I believe it is bugfix-grade, and if you agree, please merge.

repo: ucoProject/UCO


text:
Menu Export

fichier -> exporter ne mène nulle part.
(1) Une fenêtre s'ouvre pour choisir un répertoire apparemment, mais on ne peut pas saisir de nom de fichier, impossible d'exporter quoi que ce soit (qu'exporte-t-on d'ailleurs ? ce n'est pas clair).
(2) En bas le menu déroulant écrit "tout fichier de compte" et on ne voit pas d'extension de fichier.
Je pense que par défaut la fenêtre devrait s'ouvrir dans le répertoire où cutecoin sauvegarde les données du compte que l'on peut exporter / importer (lequel est-ce !? sous Ubuntu : ~./config/cutecoin)

Ok pour l'amélioration de la fenêtre d'export.
Par contre, le ~/config/cutecoin n'est pas censé être utilisé / connu des utilisateurs standards. A terme il faut que ça soit transparent sans qu'il n'ait besoin de savoir ou se trouvent les données mises en cache.

A voir si ces données son sensibles ou pas. Si elles sont sont sensibles il vaut mieux que l"utilisateur sache où elles sont en cas de besoin de les supprimer (ex : changement de machine pour gérer son compte, nécessité d'effacer les données de l'ancienne machine...).

Disons que je préfère maitriser le processus, l'import/export est là pour ce cas d'usage.
Copier/coller des données y compris celles en cache, je suis pas très fan. Pas de garantie sur le comportement de cutecoin suite à une telle manipulation. Ca peut marcher dans 90% des cas mais je ne sais pas si ça sera 100% !

Clairement l'import - export est une fonctionnalité essentielle sous cette forme. Mais savoir où sont les données ne serait pas un luxe tout de même. Quitte à ce que ce soit dans le help, online ou pas.

Ok pour documenter tout ça. De toute façon il faudrait qu'on enrichisse la doc développeurs pour capitaliser les connaissances sur le long terme.

authors: Insoleet galuel

repo: ucoin-io/cutecoin


text:
PyLinting

Clean up existing code with pylint

I would like to take this.

authors: csaranbalaji nlynn


text:
Paths in example data file don't match when generating your own.

The example file has IMG/center_2017_05_21_19_15_37_960.jpg, but when the recorder is generating files, it has the full path /home/[stuff]/CarND-Behavioral-Cloning-P3/data/train_3/.. combine this with the fact that image = cv2.imread(img_path) silently fails on missing files (Returning a null) and this can cause some headaches. Please just make them all relative to the csv file.

Looks like we've since changed this example to be different than what caused the issue, so closing this one out.

authors: frankcarey mvirgo


text:
#TODO Exercise in Intro To Torch Part 8 is already solved

The notebook "Part 8 - Transfer Learning (Exercises).ipynb" in "into-to-pytorch" folder has the TODO exercise about transformations already solved, even though it is not a "solution" notebook.

Really? Oh dang. I'll look into that.

The issue is valid, I proposed a change in the following pull request:
https://github.com/udacity/deep-learning-v2-pytorch/pull/55

Fixed in this commit: 883eb15a91f80c10064be8e2b6b13527060f4607

authors: cerepos dJani97 mcleonard


text:
Revisión del bug en el modulo de entrada que no carga los elementos cuando se va a realizar una entrada

Se debe revisar y corregir el bug en el modulo de entrada al realizar el proceso de una entrada algunas actas no tiene  elementos para relacionar, se debe revisar si es que el acta no tenia elementos asociados y si es así se debe controlar el error para que ninguna acta pase a estado aceptada sin elementos, la issue debe cumplir con los siguientes requerimientos:

[x] Revisar cual es el bug al momento de generar una entrada que no carga los elementos asociados a esa acta en estado de aceptada
[x] ajustar que las actas que se encuentre en esatdo de aceptadas si tengan elementos asociados

no se encuentra necesario la issue

no se encuentra necesario la issue

Los elementos no se cargan cuando el acta no tiene un proveedor asociado (actas especiales). La carga de elementos se hace a través del mid en la función GetElementos del helper de acta de recibido.

Los elementos no se cargan cuando el acta no tiene un proveedor asociado (actas especiales). La carga de elementos se hace a través del mid en la función GetElementos del helper de acta de recibido.

El mid se actualiza en el PD udistrital/arka_mid#59.

El mid se actualiza en el PD udistrital/arka_mid#59.


text:
Prueba de integridad y consistencia en el modulo de admisiones, ajustes, establecer data en el ambiente de pruebas y comprobación de flujo de cada submódulo

Se requiere realizar la Prueba de integridad y consistencia en el modulo de admisiones, ajustes, establecer data en el ambiente de pruebas y comprobación de flujo de cada submódulo, la issue debe cumplir con los siguientes requerimientos:
Sub Tareas

[x] Crear todo el ambiente de pruebas necesario para la prueba de integración, creación de aspirantes de pruebas, criterios, subcriterios, cupos, evaluación de documentos, evaluación de aspirantes y cambio de estado de aspirantes
[x] Realizar la prueba de integridad e integridad de todos los módulos ajustados en las issue #388, #375 y #358

Criterios de aceptación

[x] Establecer la data de pruebas
[x] Realizar la prueba de integridad y consistencia del modulo de admisiones

Requerimientos
No aplica
Definition of Ready - DoR

[x] Está refinada y estimada en puntos de historia por el equipo.
[x] Incluye la descripción y criterios de aceptación, con el detalle funcional y especificaciones técnicas, de forma entendible por cualquier miembro del equipo.
[x] No tiene bloqueos que impidan su ejecución.
[x] Las dependencias están identificadas y resueltas.
[x] Puede ser probada dentro del Sprint.

Definition of Done - DoD - Desarrollo

[x] Desarrollo en local.
[x] Push en Feature.
[x] Pruebas locales (funcionales).
[x] PR a Develop.
[x] Criterios de aceptación cumplidos.
[x] Documentación de issue realizada.
[x] Aprobada por SM/Líder técnico.

[ ] creación calendario academico.
[ ] creación proyecto curricular.
[ ] creación criterios, subcriterios.

[ ] definir criterios.
[ ] asignar criterios al proyecto curricular.

[ ] creación de aspirantes de pruebas.

[ ] crear usuarios.
[ ] completar el proceso de datos basicos.
[ ] pagar el recibo.
[ ] crear inscripcion a un proyecto academico.
[ ] completar inscripcion.

[ ] comprobación de flujo

[ ] evaluación de documentos.
[ ] evaluación de aspirantes.
[ ] cambio de estado de aspirantes.

Estandar de estilos.

Badge de activo

/* Estilos para el indicador de estado */
.badge {
margin: 0.4em;
width: 0.5em;
height: 0.5em;
border-radius: 100%;
}

Se da por finalizada la issue y se da continiudad en la tarea #434


text:
propuesta de cambios de avances

en base a las historias de usuario , los sistemas actuales y los lineamientos actuales de la oficina proponer un modelo de datos ajustado al presentado y reconstruido en el informe de avances

Modelo de datos
Se propone el siguiente modelo de datos, sujeto a recomendaciones y modificaciones

Link(vertabelo)
https://my.vertabelo.com/doc/GQ4xCb0AGYeTTx7E63gsbgPTlyFIUdIp
Modificaciones
Respecto al anterior se propone los siguientes cambios:

Se adicionan los lineamientos segun La Oas, se adicionan  los campos de fecha_creacion, fecha_modificacion, Activo a todas las tablas y renombra los campos que son llaves foraneas.
Eliminar tablas: etapa_avance, requisito_tipo_avance, solicitud_tipo_avance
Se adiciona campo Link_norma a la tabla tipo_avance
Se adiciona tabla especificaciones_avance
Se adiciona a la tabla solicitud_avance los campos: tipo_documento, documento, area_funcional, cargo, fecha_evento, dependencia, facultad, proyecto curricular
Se elimina tablas cuentas_especial
Se elimina tabla tipo_documento_afectante , pero se adiciona los campos tipo_documento, documento a la tabla avance_legalizacion_tipo
Se adiciona tabla consolidado_retencion
Se adiciona tabla practica_academica
Se adiciona tabla informacion_estudiante

Presento dudas de como hacer la relaciona de las tablas de practica_academica con la tabla de avance_legalizacion_tipo, por el momento se deja asociada a la tabla tipo_avance_legalizacion
Algunas tablas no se quitaron ya que se encuentra que pueden tener relación con el tema de avances pero no se tiene claridad.

Modelo de datos
Se propone el siguiente modelo de datos, sujeto a recomendaciones y modificaciones

Link(vertabelo)
https://my.vertabelo.com/doc/GQ4xCb0AGYeTTx7E63gsbgPTlyFIUdIp
Modificaciones
Respecto al anterior se propone los siguientes cambios:

Se adicionan los lineamientos segun La Oas, se adicionan  los campos de fecha_creacion, fecha_modificacion, Activo a todas las tablas y renombra los campos que son llaves foraneas.
Eliminar tablas: etapa_avance, requisito_tipo_avance, solicitud_tipo_avance
Se adiciona campo Link_norma a la tabla tipo_avance
Se adiciona tabla especificaciones_avance
Se adiciona a la tabla solicitud_avance los campos: tipo_documento, documento, area_funcional, cargo, fecha_evento, dependencia, facultad, proyecto curricular
Se elimina tablas cuentas_especial
Se elimina tabla tipo_documento_afectante , pero se adiciona los campos tipo_documento, documento a la tabla avance_legalizacion_tipo
Se adiciona tabla consolidado_retencion
Se adiciona tabla practica_academica
Se adiciona tabla informacion_estudiante

Presento dudas de como hacer la relaciona de las tablas de practica_academica con la tabla de avance_legalizacion_tipo, por el momento se deja asociada a la tabla tipo_avance_legalizacion
Algunas tablas no se quitaron ya que se encuentra que pueden tener relación con el tema de avances pero no se tiene claridad.

authors: BOTOOM NRDaza


text:
Trouble with Multiplayer

We are using the plugin in our project, where we have 2 teams, one Blue and one Red.
Works fine on BlueTeam with all 8 players, but on RedTeam, characters start to disapper and reappear.
Link here :
https://gyazo.com/36df77f6f0159c0d1ae88022d8c8878e
Though game is working as it should, the only issue we are struggling with is the FogOfWar
So my question is, does FogOfWar actually support network?
Because there is no information in your description neither the documentation.
Cheers

After tweaking it with a bunch of tries, we finally got it to work.

repo: ufna/VaFogOfWar


text:
Add 2020 board

Closes https://github.com/uio-carpentry/governance/issues/12

Will add the roles to the new file in a new pull-request

Forgot to create pull-request and merged directly into master.
Sorry

authors: arockenberger lexnederbragt

repo: uio-carpentry/governance


text:
First wall thermohydraulic model

In GitLab by @mkovari on Nov 26, 2015, 08:43
The first wall calculation (subroutine iterate_fw in hcpb.f90) is very complicated, and causes frequent problems.  I propose to replace it, as described below.
The thickness of the pipe wall sufficient to withstand the pressure is always very small - a fraction of a mm.  In practice thermal stresses, corrosion and manufacturing issues will determine the thickness, so this is now an input. (This is additional to the armour thickness.)
The maximum temperature at the front face is calculated, and a constraint is available to limit this temperature.  The first wall channel length affects this, as it determines the flow speed, so it is available as an iteration variable.  Note it is no longer derived from the size and shape of the blanket module.
Strictly speaking since the first wall temperature is not known to start with, the thermal conductivity and heat transfer coefficient are not known.  To get round this the global variable tpeak (peak first wall temperature) is now initialised to 873 K.  Its value converges as VMCON converges.
The LeClaire formula for circular pipes is NOT used.  It gives an unrealistically small temperature differential, as the wall thickness is the same all the way round, and the surface area is bigger than that of a flat wall.  Instead two simple approximations are used:
See attached file.
It would be good to have an input for the reduction in thermal conductivity due to irradiation.
afwi /0.008/ : inner radius of inboard first wall/blanket coolant channels OBSO LETE (m)
afwo /0.008/ : inner radius of outboard first wall/blanket coolant channels OBS OLETE (m
fwcoolant /helium/ : first wall coolant (can be different from blanket coolant) 'helium' or 'water' (15/11/27)
fw_wall /0.003/ : wall thickness of first wall coolant channels (m) (15/11/27)
afw /0.006/ : radius of first wall cooling channels (m) (27/11/15)
pitch /0.020/ : pitch of first wall cooling channels (m) (27/11/15)
fwinlet /623/ : inlet temperature of first wall coolant (K) (15/11/27)
fwoutlet /823/ : outlet temperature of first wall coolant (K) (15/11/27)
fwpressure /15.5e6/ : first wall coolant pressure (Pa) (secondary_cycle>1)
tpeak : peak first wall temperature (K) (15/11/27)
roughness /1e-6/ : first wall channel roughness epsilon (m) (15/11/27)
fw_channel_length /4.0/ : Length of a single first wall channel (all in paralle l) (m) ( (iteration variable 114, useful for constraint equation 39)
peaking_factor /1.0/ : peaking factor for first wall heat loads (15/11/27) (Applied separately to inboard and outboard loads. Applies to both neutron and surface loads.)
blpressure /15.5e6/ : blanket coolant pressure (Pa) (secondary_cycle>1) (15/11/ 27)
inlet_temp /573.0/ : inlet temperature of blanket coolant (K) (secondary_cycle >1) (15/
outlet_temp /823.0/ : outlet temperature of blanket coolant (K) (15/11/27)
    (secondary_cycle>1);
    input if coolwh=1 (helium), calculated if coolwh=2 (water)

coolp /15.5e6/ : blanket coolant pressure (Pa) stellarator ONLY (15/11/27)

First_wall_geometry_for_PROCESS.docx

authors: jonmaddock mkovari

repo: ukaea/PROCESS


text:
Remove Role metadata model

Issue number: N/A
Description of change
Role was an earlier version of job title and is no longer used (following #15) as job title is free text.
This removes the role model and related constants and fixtures.
Checklist

[x] Have any relevant search models been updated?
[x] Have any relevant fixtures (fixtures/test_data.yaml) been updated?
[x] Have any relevant select-/prefetch-related field lists in the views and search apps been updated?
[x] Has the admin site been updated (for new models, fields etc.)?
[x] Has the README been updated (if needed)?

Codecov Report

Merging #906 into develop will decrease coverage by <.01%.
The diff coverage is n/a.

@@             Coverage Diff             @@
##           develop     #906      +/-   ##
===========================================
- Coverage    96.66%   96.65%   -0.01%
===========================================
  Files          168      168
  Lines         4884     4870      -14
  Branches       470      470
===========================================
- Hits          4721     4707      -14
- Misses          99      100       +1
+ Partials        64       63       -1

Impacted Files
Coverage Δ

datahub/metadata/metadata.py
100% <ø> (ø)
:arrow_up:

datahub/metadata/admin.py
100% <ø> (ø)
:arrow_up:

...ub/core/management/commands/loadinitialmetadata.py
93.93% <ø> (ø)
:arrow_up:

datahub/core/constants.py
100% <ø> (ø)
:arrow_up:

datahub/core/admin.py
82.6% <0%> (ø)
:arrow_up:

Continue to review full report at Codecov.

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

authors: codecov-io reupen

repo: uktrade/data-hub-leeloo


text:
EncryptablePropertySourceConverter should only convert files defined in .include-sources

On startup, I get the following message logged for all of my *.properties:
c.u.j.EncryptablePropertySourceConverter : Converting PropertySource applicationConfig: [classpath:/application.properties] [org.springframework.boot.env.OriginTrackedMapPropertySource] to EncryptableMapPropertySourceWrapper
c.u.j.EncryptablePropertySourceConverter : Converting PropertySource applicationConfig: [classpath:/application-custom.properties] [org.springframework.boot.env.OriginTrackedMapPropertySource] to EncryptableMapPropertySourceWrapper
[classpath:/application-custom2.properties] [org.springframework.boot.env.OriginTrackedMapPropertySource] to EncryptableMapPropertySourceWrapper

But as I set the following property:
jasypt.encryptor.property.filter.include-sources=application.properties

It would be great if the EncryptablePropertySourceConverter could simply skip the files not mentioned there. Because I already told him with the property that the other files don't contain encrypted values, thus these files could be skipped entirely.

You’re right. I will take a look but I think that all property sources get converted regardless. The filter logic is then applied when properties are looked up, so semantically, it should work as you expect

closing this since the behavior is as expected. One caveat though, the include-sources is based on the property source name, and application.properties is not the property source name of the application.properties file, the actual name is applicationConfig

So your advise is to set jasypt.encryptor.property.filter.include-sources=applicationConfig??

yes, you can either use include-sources=applicationConfig or include-names="some\.property\.prefix\..*"

Just as a sidenote: I never got it working with include-sources even though I'm only having a simple application.properties file, and using jasypt.encryptor.property.filter.include-sources=applicationConfig. The password is never decoded.
Inspite, I could get it working with jasypt.encryptor.property.filter.include-names=spring.datasource..*
Maybe you could have a look again on the include-sources property? This seem not to be working correctly...

thanks for the heads up, I'll take a look

should work as expected: https://github.com/ulisesbocchio/jasypt-spring-boot/blob/master/jasypt-spring-boot/src/test/java/com/ulisesbocchio/jasyptspringboot/filter/DefaultPropertyFilterTest.java

authors: membersound sddakoty ulisesbocchio

repo: ulisesbocchio/jasypt-spring-boot


text:
Docs: Umami API documentation is very poor

I have to guess to know what queries are required for each endpoint. Some endpoints throw 500 errors too.
For example
https://api.umami.is/v1/websites/<id>/pageviews - request
Invalid unit - response
or
https://api.umami.is/v1/websites/<id>/events - request
500: Internal Server error - response
Originally posted by @sonysn in https://github.com/umami-software/umami/discussions/2883

API documentation is here, https://umami.is/docs/api/website-stats

authors: mikecao sonysn

repo: umami-software/umami


text:
Add Sovryn multiprocessor

Context
This PR represents the same as #364
To-do list

[ ] Added tests
[ ] Tested on dev/sbx
[ ] Changelog was updated with current changes
[ ] Documentation or guides were updated (slab, readme)
[ ] Version was updated on package.json (releases/hotfixes)

Checklist before merge

[ ] there are no errors in logs in any workers
[ ] new blocks are being discovered and marked as finalized
[ ] foreign blocks are being dispatched
[ ] squash all commits before merging

Looks good to me! Just not sure if it will cause conflicts on that PR

Looks good to me! Just not sure if it will cause conflicts on that PR

@matheushahnn, thanks. I will close the old one, for whatever reason github didn't allow me to force push after rebasing develop. That is why I opened this new one including your suggestions.

repo: umbrella-network/pegasus


text:
Verify encoder rotation direction

The encoders might associate positive rotation with clockwise rotation, which is counter to the ROS specifications. Take the time to rotate each wheel and verify that the associated JointState is updated as expected. Should the rotation be incorrect, modify phidgets_encoder to reflect the proper behavior.

Encoder output does indeed turn the wrong direction. Updated launchfile in goat_launch to change parameter reflecting this flip.

repo: umigv/atlas


text:
Command line debugging tests fail when compiling multiple umple files for one test

Brief Description
Refer to Issue #882 to see changes made for command line debugging. (See all ignored tests in testbed/test/cruise.compiler.CompilerErrorOutputTests)
The command line debugging tool seems to be functioning correctly for the issues these tests test for, but for some reason the tests themselves fail to execute correctly. When Umple compiles multiple files in order to generate one or more Java files, it claims that it cannot find a symbol from a file that is used by the main file being compiled.
Minimum Steps to Reproduce
There are already 3 tests created in cruise.compiler.CompilerErrorOutputTests, simply removing the @ ignore annotation and running the JUnit test will show you the error

Navigate to the following file: testbed/cruise.compiler.CompilerErrorOutputTests
Find "MultipleClassesTest" and remove the @ ignore annotation above it
Run the JUnit test for the file and observe the failure message

Expected Result
You can view the expected results for the three tests in testbed/test/cruise.compiler.expected

I am raising the priority on this, since this is an important problem.

In particular, the build of Umple itself, which operates on multiple files has this problem

See also #1173

authors: AlexJoshuaMcManus TimLethbridge

repo: umple/umple


text:
Extração de dados

Extração de dados
Descrição
Nesta issue, vamos discutir e explorar diferentes métodos e ferramentas para extrair dados de PDFs do Diário Oficial. A extração de dados dos PDFs é fundamental para automatizar a coleta de informações importantes.
Tarefas Planejadas

[x] Verificar o local onde o diário oficial de Sergipe é disponibilizado
[x] Explorar formas de baixar os pdf's do diário oficial de forma automatizada
[x] Criar um script em python para realizar a extração desses pdf's

Após avaliar diversas bibliotecas para a realização de downloads de arquivos, concluí que o Selenium é a solução mais eficaz. Desenvolvi um script utilizando esta biblioteca para facilitar o processo de download.
Script disponível em: https://github.com/unb-mds/2023-2-Squad04/blob/main/Code/pdf_download.py


text:
Publicação da Página do Miro

Tarefa: Publicação da Página do Miro
Descrição: A tarefa consiste em preparar, revisar e publicar uma página no Miro contendo o Story Map, documentação do projeto, backlog e outras informações relevantes. O objetivo é centralizar todos os dados importantes do projeto em uma única página, facilitando o acesso e a colaboração entre a equipe. A página do Miro deve ser clara, organizada e acessível para todos os membros da equipe.
Detalhes

Responsável: João Pedro
Prazo: 01/12/2024

Critérios de Conclusão

[ ] Página completa e organizada: A página do Miro deve conter o Story Map, backlog, documentação e outras informações relevantes, todas bem organizadas e facilmente acessíveis.
[ ] Revisão realizada: A página foi revisada e validada pela equipe, garantindo que todas as informações estão corretas, claras e atualizadas.
[ ] Publicação e acesso realizados: A página foi publicada e está acessível a todos os relevantes, com permissões de acesso configuradas corretamente.
[ ] Comunicação enviada: Todos os membros da equipe foram informados sobre a publicação da página e como acessá-la.

Link da pagina do miro: Miro

A analise foi feita e a pagina está pronta para ser postada na documentação do projeto.


text:
Move healthcheck outside domain constraints

The AWS ECS healthcheck uses an internal hostname which fails to route and causes the cycling of tasks due to healthcheck failures.

Thanks 👍🏻

repo: unboxed/bops


text:
Scope log path fix

Closes #150

Ready for review @fermayo

repo: undefinedlabs/scope-go-agent


text:
🛑 Piped API is down

In 1f854d1, Piped API (https://pipedapi.unforest.net) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Piped API is back up in a9c41fe after 31 minutes.

repo: unforest/uptime


text:
🛑 Piped API is down

In c94bdd9, Piped API (https://pipedapi.unforest.net) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Piped API is back up in 84c4393 after 38 minutes.


text:
🛑 Nitter is down

In 4d835e3, Nitter (https://nitter.unforest.net) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Nitter is back up in df1d9ff after 17 minutes.


text:
🛑 Libreddit is down

In 788b099, Libreddit (https://libreddit.unforest.net) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Libreddit is back up in d3b2b52 after 12 minutes.


text:
Upstream extension-search-path.patch

Upstreams the extension search path patch from https://github.com/NixOS/nixpkgs/pull/188086

I avoided the nixpkgs issue largely because of its slightly convoluted history.
Given that I both maintain ungoogled-chromium and it's nixpkgs packaging (CC @emilylange), I'll try to take a closer look (can't promise when) at declarative extensions and whether ungoogled-chromium should put patches for it into its patchset

Besides, this patch does not apply.

One of the stated goals of the ungoogled-chromium project is:

ungoogled-chromium features tweaks to enhance privacy, control, and transparency. However, almost all of these features must be manually activated or enabled. For more details, see Feature Overview.

As this is a patch that enhances control, I'd argue this patch does apply.

Besides, this patch does not apply.

that is a technical observation:
WARNING: Patch failed validation: extra/ungoogled-chromium/extension-search-path.patch
DEBUG: Specifically, file "chrome/common/chrome_paths.cc" failed validation: Line '#include "base/files/file_path.h"' does not match context line '#include "base/files/file_util.h"' from patch
DEBUG: PATCH_BIN env variable is not set
DEBUG: Output of "patch --dry-run" for this patch on this file:
checking file chrome/common/chrome_paths.cc
Hunk #1 FAILED at 4.
Hunk #2 FAILED at 511.
2 out of 2 hunks FAILED

Sorry! Misinterpreted your statement.

The patch should apply now.

I'll try to take a closer look (can't promise when) at declarative extensions and whether ungoogled-chromium should put patches for it into its patchset

@networkException Have you had a chance to glance through? What's your opinion?

with my nixpkgs chromium maintainer hat on I don't see the patch as useful here or in packaging as there are ways not needing modifications which I would prefer anyways

I would love to see this in UC. It's not just for including extensions from chromestore, but also for developing your own.

Carrying this patch in nixpkgs doesn't make sense, because it enables a substantial use case, which would then differ from other distros.
While there are workarounds, like managing the user's extention dir, this is substantially different and valuable in it's own right, because a system level extension also can't be messed up by a user messing up their browser profile.

Just fixed a merge conflict. Would anyone from UC be willing to review this?

No, this is not happening until it gets decided in nixpkgs upstream.

In what way is nixpkgs to be considered upstream to this?
What decision should be taken by nixpkgs and how would it influence UC?

I have also sent this patch to chromium upstream. It can be tracked here: https://chromium-review.googlesource.com/c/chromium/+/5650013

I think this has been discussed enough, solutions have been pointed out. This is definitely not a fit for us and very likely not for nixpkgs either.
Closeing as per https://github.com/ungoogled-software/ungoogled-chromium/issues/2932#issuecomment-2212516130

repo: ungoogled-software/ungoogled-chromium


text:
Upgrade to new scalismo version

This PR upgrades the library to work with the new version of Scalismo v0.90-RC1.
This PR might cause some changes also in the user code of people using this library. Given that the usability and clarity of a lot of concepts within scalismo improved, we think it justifies the investment switching to the newer version.

Thank you for your feedback. I resorted now in most cases to solutions that work in scala pre and post 2.13. Only a helper function to zipping three sequences now remained in the specialized code.
I combined the last four commits to one such that the changes are cleaner and the splitting and merging of the code are removed.

repo: unibas-gravis/scalismo-faces


text:
Wrong error received when trying to run a binary

Describe the bug
Wrong error received when trying to run a binary: a more suggestive error should be received, as example "Cannot run the binary" instead of unknown runner: linuxu
Steps to reproduce
kraft version 0.6.4-32-gc5105c9 (c5105c9c7951ed2e0104663d257cfb255c7b08e4) go1.20.2 2023-07-16T12:59:01Z
unikraft@firefly:~/unikraft/static-pie-apps/lang/c$ sudo kraft run --as linuxu /lib/x86_64-linux-gnu/ld-linux-x86-64.so.2
unknown runner: linuxu
Expected behavior
unikraft@firefly:~/unikraft/static-pie-apps/lang/c$ /lib/x86_64-linux-gnu/ld-linux-x86-64.so.2
/lib/x86_64-linux-gnu/ld-linux-x86-64.so.2: missing program name
Try '/lib/x86_64-linux-gnu/ld-linux-x86-64.so.2 --help' for more information.
unikraft@firefly:/lib64$ ./ld-linux-x86-64.so.2 --help
Usage: ./ld-linux-x86-64.so.2 [OPTION]... EXECUTABLE-FILE [ARGS-FOR-PROGRAM...]
You have invoked 'ld.so', the program interpreter for dynamically-linked
ELF programs.  Usually, the program interpreter is invoked automatically
when a dynamically-linked executable is started.
Which architectures were you using or does this bug affect?
x86_64
Which operating system were you using or does this bug affect?
linux/debian
Relevant log output
No response

It seems that the bug is fixed. New error received is:
could not determine how to run provided input: file is not ELF executable
provided file is not a Unikraft unikernel
path is not project: /media/stefan/projects/unikraft/kraftkit
incompatible source

The issue can be closed with resolution Fixed.

repo: unikraft/kraftkit


text:
Fix QOSF project page rendering.

I'm relying on the CI to test deployment, so please hold off on review for a few minutes while I diagnose what will or won't work.

That works! Let's see if it's the permalink field's mime-type, or if the id field will still work, at least.

That doesn't work, and the problem does genuinely seem to be mime-type served with a permalink field. Let's try to restore the id field, now.

This is ready to review, unless we have a pressing requirement to diagnose the problem with mime-type in the framework or app internals, for the permalink field.

I'm getting a 404 when navigating to the QOSF page from /bounties.
https://deploy-preview-19--unitaryhack2024.netlify.app/projects/quantum-open-source-foundation-qosf

Closing in favor of 9f40380

authors: WrathfulSpatula natestemen


text:
When will be new release?

Hi everybody.
When will be new release?

Seems that never.

authors: AndreyNag Shekelme

repo: unitcurrency/unitcurrency


text:
factoryinput

See also https://github.com/united-manufacturing-hub/united-manufacturing-hub/pull/489

@Scarjit

Please add docs
Please work on warnings (no customers, JAEGER_HOST, etc.)


text:
Add serializer type attribute for collection

Add attribute to define type id for type provider.

Create branch from main
issue-13-add-serializer-type-attribute-for-collection


text:
Regression in 5.2.1 while using InjectionFactory

this worked fine in 5.2.0 (as well as previous versions) and not anymore in 5.2.1.
 class Program
    {
        static void Main(string[] args)
        {
            WorksOnUnityContainer520(new UnityContainer());

            Console.ReadLine();
        }

        static void WorksOnUnityContainer520(IUnityContainer container)
        {
            container.RegisterType<ITestService, TestService>(new InjectionFactory(c => new TestService(new ModelA())));

            var testService = container.Resolve<ITestService>();

        }

        #region Model

        public interface ITestService
        {

        }

        public interface IModelA
        {

        }

        internal sealed class TestService : ITestService
        {
            private readonly IModelA _a;

            public TestService(IModelA a)
            {
                _a = a;
            }
        }

        internal sealed class ModelA : IModelA
        {

        }

        #endregion
    }

I switched to using InjectionConstructor which still works as expected.

Think about this line of code:
RegisterType<ITestService, TestService>(new InjectionFactory(c => new Tes...));

Are you registering a map between ITestService and TestService?
Or perhaps you are registering map between ''ITestService'' and InjectionFactory(c => new TestService(new ModelA())?
If you think about these two, they are mutually exclusive.

Viewed that way you are absolutely right. Still, this did work in older versions, but I guess it can be viewed as a bugfix then. I switched all my cases to InjectionConstructor, which is the correct (and shorter/better) solution anyway. Thanks for the clarification.

I've added note to Release with explanation

authors: ENikS MarcMenghin

repo: unitycontainer/container


text:
chore!: update deps

I updated dependencies.
Since this PR major update (i.e. TypeScript v4 to v5), I set ! mark in the commit message.
Should we keep using TypeScript v4?
By the way, this PR includes https://github.com/unjs/eslint-config/pull/8 so CI pipeline will pass on initial commit.

The content of this PR has been become same as #70 and #73, so I will close it for now.

repo: unjs/template


text:
download template and has an error

Environment
node: v20.10.0
Reproduction

pnpm dlx giget gh:unjs/undocs/template docs --install
pnpm dev

Describe the bug

When i use command to dev the project, has this error.

I install nuxt, other command has resolve this error, but pnpm to dev the project, also has error.

Additional context

Logs
No response

please use bun

Thank you for your quick reply. But i use bun also need nuxt. Its something i forgot for？

Thanks for confirming. From reproduction above, i saw pnpm dev

Thanks for confirming. From reproduction above, i saw pnpm dev did you remove node_modules and use bun install to install dependencies? (bun is not strict about dependency hoisting)

Oh, i confirm that. Use bun is correct. Is  my fault, i think first i use pnpm install, then use bun has same error. But in docs guide, has these command too, i think its should to be solve? Thank you very much.

@pi0 We could add within the post install script as an option, if not we can make it more clear in the docs.
{
  "scripts": {
    "preinstall": "npx only-allow bun"
  }
}

before marking undocs as general purpose will will certainly solve this for supporting other package managers but using hooks only makes install time less reliable / slower.

repo: unjs/undocs