text:
Base64 Slow?

Today i was trying some PHP vs Crystal tests. And there was something that did not add up.
System: Debian, Ryzen 1600, 8GB ECC
PHP 7.0:
encode: 1333333600, 0.82
decode: 1000000000, 2.94
Crystal 23.1
encode: 1333333600, 00:00:13.5935260
decode: 1000000000, 00:00:26.8058000
Yes, the results ended up being 13 times slower then PHP.
Both Crystal Run and Build && run ended up being slow.
One core running 100% during the both tests ...
require "base64"

STR_SIZE = 10_000_000
TRIES    =        100

str = "a" * STR_SIZE
str2 = ""

print "encode: "
t, s = Time.now, 0
TRIES.times do |i|
  str2 = Base64.strict_encode(str)
  s += str2.bytesize
end
puts "#{s}, #{Time.now - t}"

print "decode: "
t, s = Time.now, 0
TRIES.times do |i|
  s += Base64.decode(str2).bytesize
end
puts "#{s}, #{Time.now - t}"

<?php
$STR_SIZE = 10000000;
$TRIES = 100;
$str = "";
for ($i = 0; $i < $STR_SIZE; $i++) $str .= "a";
$str2 = "";
$s = 0;
$start = microtime(true);
for ($i = 0; $i < $TRIES; $i++) {
    $str2 = base64_encode($str);
    $s += strlen($str2);
}
printf("encode: %d, %.2f\n", $s, microtime(true) - $start);
$s = 0;
$start = microtime(true);
for ($i = 0; $i < $TRIES; $i++) {
    $str3 = base64_decode($str2);
    $s += strlen($str3);
}
printf("decode: %d, %.2f\n", $s, microtime(true) - $start);

Done the benchmarks several times and each time the results ended up being the same.
When checking the original site where i got the code from:
https://github.com/kostya/benchmarks
PHP is supposed to be 3 times slower then Crystal... Are we looking at a issue with Crystal and Ryzen CPUs? Other tests show Crystal winning against PHP or on equal level ( when PHP is accessing C based extentions ).

run it with --release option:
php test.php
encode: 1333333600, 1.52
decode: 1000000000, 9.28
crystal test.cr
encode: 1333333600, 00:00:20.4281690
decode: 1000000000, 00:00:30.6223340
crystal test.cr --release
encode: 1333333600, 00:00:01.1803430
decode: 1000000000, 00:00:02.7188520

Good to know but running with the --release results in the following error
crystal build base64.cr --release
crystal: /var/cache/omnibus/src/llvm/llvm-3.8.1.src/lib/CodeGen/LexicalScopes.cpp:160: llvm::LexicalScope* llvm::LexicalScopes::getOrCreateRegularScope(const llvm::DILocalScope*): Assertion `cast<DISubprogram>(Scope)->describes(MF->getFunction())' failed.
/usr/bin/crystal: line 102: 26729 Aborted                 "$INSTALL_DIR/embedded/bin/crystal" "$@"

PHP 7:
encode: 1333333600, 0.82
decode: 1000000000, 3.25
Crystal:
encode: 1333333600, 00:00:12.8882330
decode: 1000000000, 00:00:26.9714920
Crystal ( --release --no-debug ):
encode: 1333333600, 00:00:00.7490210
decode: 1000000000, 00:00:01.1458920
Those results are much better. Thanks ;)

Duplicate of #4719
FYI, @Wulfklaue if you get to use a newer llvm, the bug should go away.

authors: Wulfklaue bcardiff kostya


text:
Fix race condition in chown

Described in #9174

I know this is extreme micro optimizing, but if's are assumed to be true by the CPU without additional hinting correct? So if x should contain the more likely branch making the current if better because follow_symlinks defaults to false.
If only there was a way to give hints to the compiler LIKELY/UNLIKELY, or possibly use unless as a CPU hinted not likely branch.

I believe branch prediction is pretty useless at this point. On the odd chance this code ends up in a hot path, it won't make a difference when the next instruction is a costly syscall anyways.

source: gharchive/pull-request

authors: didactic-drunk straight-shoota

repo: crystal-lang/crystal

license_type: permissive

license_source: github-api


text:
Allow deleting elements from NamedTuple/Hash literals

Resolves #8849

This is good for another review.

This is good for another review.

@asterite Done.  Also rebased on master to fix that CI issue.

@asterite Done.  Also rebased on master to fix that CI issue.

This is good for another review.

Bump.

@oprypin Bump :)

Does https://github.com/crystal-lang/crystal/pull/7109#issuecomment-441625418 not apply here?

@HertzDevil I'm not sure.  IMO it makes sense to have this given you can construct a hash entirely within macro land, but then if you want to remove a key from it, you can't and would have rebuild the whole hash.
That's my usecase at least, copying the named arguments from an annotation, processing it (i.e. using the provided values to add/remove arguments), then double splat it into the constructor of a struct.

@Blacksmoke16 I'm not sure what you mean. Maybe it makes sense, but the argument against deleting from a Hash is exactly the same as about deleting from an Array (the linked comment)

@oprypin I don't see it that way.  The way I took it the linked comment's argument is against mutations because it makes tracking dependency order harder.  I.e. using the old mutable constant DSL pattern before annotations became more prevalent.
However after working a lot more with macros since that original issue; I don't think that argument is entirely correct mainly because there are use cases for mutating data structures other than as a means of "registering" things.  This is even more important if/when #8835 is ever implemented, as it's easy to see hashes/arrays being passed that you'd expect to be able to modify.
I also don't really see the benefit of removing mutating methods from these macro literals anyway.  It just seems like it's making them less useful for no reason.

Bump, ran into this again.
I have an annotation like @[ADI::Register(tags: [{name: "baz", value: 123, tag_type: CustomTag}])].  Each tag can have an optional tag_type that maps this tag to a specific struct. E.g:
struct CustomTag < ADI::AbstractTag
  getter value : Int32

  def initialize(@value : Int32, name : String, priority : Int32? = nil, *, tag_type = nil)
    super name, priority
  end
end

Of which I'm creating it via "#{tag[:tag_type]}.new(#{tag.double_splat})".id, but since I can't delete tag_type from the annotation's named args, I have to include tag_type in the initializer of the struct so that it doesn't error due to no matching overload.

IMO it makes more sense to have HashLiteral#select, which ArrayLiteral also has, and then we could write tag.select { |k, v| k != :tag_type }.double_splat, without introducing a new source of mutability.
(I would personally avoid this call and double_splat altogether, manually iterate over tag, and interpolate each element separately.)

@HertzDevil Not as elegant but that would work too I suppose.  Better than nothing.

manually iterate over tag, and interpolate each element separately.

That's a bit easier said than done I think because the instantiation of the struct is still in the macro context.  If it wasn't then you could easily use a for in loop to do it.

authors: Blacksmoke16 HertzDevil oprypin


text:
RU - некоторые автоэмоции из текста не работают корректно

хд -> смеётся
не работает как эмоция, звуков смеха не издается.
Так же нужно проверить остальные эмоции.

убейте

source: gharchive/issue

license: MIT


text:
Fuzzy search

Not fine tuned or anything but adds the similar classes feature. #374
Note: requires a npm install

fixes #374

While we are at it, we can do it for unregister too

Whats the progress on this?

Whats the progress on this?

haven't touched it till 5 minutes into the future

authors: CallumCoy tanndlin

repo: cs-discord-at-ucf/lion


text:
[BUG] - Wrong behavior when solution fails to compile

Description
When the frontend passes a solution that fails to compile, the frontend will correctly state that the solution fails to compile. However, the lobby will then say that this solution passed all cases, and the race is over.
Steps to Reproduce
Steps to reproduce the bug:

[ ] Start new race
[ ] Submit a solution that won't compile

Expected Behavior
The frontend should state that the solution doesn't compile, but should not end the race.
Additional Context
This is reproducible using the main branch of the backend and the issue-11 branch of the frontend.
Relevant screenshots

Closed via #24


text:
Code blocks lock the Preview Pane while scrolling

Sometimes when scrolling past code blocks in the Markdown Pane, the Preview Pane will temporarily lock in a fixed position, while I continue to scroll in the Markdown Pane.
Once I scroll past the code block, the Preview Pane resumes scrolling.
This seems to be particularly common with longer code blocks, but I've had it happen for smaller code blocks too. I'm not sure what exactly causes it – if it's a character or something else in the code block, or if it affects all code blocks. I think it is the latter.

Well, the short story is that the whole synchronized scrolling thing is written quite poorly so it doesn't surprise me it turns out glitchy... I might re-write the part at some point, if I have time. (That's not a promise!)
If there are somebody out there interested, they might also want to check out the package https://github.com/mark-hahn/markdown-scroll-sync (I haven't done that myself, but it looks promising).

license: mit

license_source: bigquery


text:
Switch to Maven + Metrics + SimpleSpec

This pull isn't quite ready because I haven't tested metrics yet, and there are some potential perf improvements in metrics usage, but just wanted to get it out there for some feedback.
We also need to get the Java beanstalk API out into a public Maven repo. To get this to build as-is you need to install it locally. Anyone care to tackle that?

A port of the test suite to SimpleSpec, mavenizing the project, and moving to Metrics? The skies have parted.
There are actually a few things that I really liked about the old Introspector setup that I'd like to find a way to preserve (perhaps a servlet endpoint that would return just the subset of explicitly instrumented stuff rather than the whole metrics JVM shebang, but I can look into that later).
Thanks so much man. Mavenizing the Beanstalk lib should be straightforward -- if someone else hasn't yet (or if it hasn't already been mavenized and pushed to Central in the year or so since I've looked at it), I'm happy to.
Will read over in more detail later, but thanks a ton.
– Scott

I'll check this out in detail this evening -- imagine everything in here's good. If things seem fine, I'll bump the pom to -SNAPSHOT, we can merge it, and keep moving from there.

authors: cscotta jarreds

repo: cscotta/Octobot


text:
support postcss 8 plugins, closes #5

This PR adds support for postcss 8 while maintaining support for postcss 7. In postcss 8 plugins no longer provide their own .process() method, so this package has to depend on postcss itself to test plugins.

@jonathantneal Hi! How about merge and publish new release?
Or add somebody to csstools if you haven't enough time.

@Semigradsky, yes, I’ll merge now and do an immediate release. I also want to talk about getting other maintainers on board. Like yourself, immediately. I have started up a monorepo a couple times. I need partners on this project. It can be done fast. Would you have time today or this weekend to team up?

@jonathantneal I can't now, but I will be available after this weekend.

authors: Semigradsky goto-bus-stop jonathantneal

repo: csstools/postcss-tape


text:
better installation check

I had some problems because of missing curl in my fresh kali light install and also node did not installed out of the box, but the installscript finished with the message "ready".
I added some checks before install and set bash in error-mode to stop if one command produced and error.

We're actually moving away from using Node JS / NPM in favor of an all Python approach; though this could help people in the interim! Thanks for taking the time to do a PR.

Looks good to me! Thanks for your contribution!

authors: frankstolle kueblc merlinschumacher

repo: ct-Open-Source/tuya-convert


text:
Why Factories?

At the moment, to get a correct analysis, one has to specify the product of Factories:
event_source = EventSourceFactory.produce(
        input_url=input_file,
        max_events=n_events if n_events > 1 else None,
        product='HESSIOEventSource',
)

What then is the difference to directly using HessioEventSource?

This surprises me... the whole point of the factory is that it finds the correct EventSource based on the input_url. The product traitlet exists only to force a particular return object.

If the EventSourceFactory is not correctly returning HESSIOEventSource for the simtelarray file (without specifying the product), then the is_compatible function needs revisiting. Something may have changed to the simtelarray file definition....

Ok, seems to have been false alarm. Sorry.
@mackaiver always put the keys there and I remember there was an issue at least with CameraCalibrator doing something wrong if not provided with the products.
On the current master, it seems to work.

Should we close this issue, since it seems to be a misunderstanding? I thikn the use case for Factories is quite clear and reasonable (since we have now 4+ data formats to support)

You can always use the shortcut event_source() helper function as well to avoid thinking about factories and products, though it's less flexible when used in a Tool since the Config doesn't propegate.

I should like another Interface.
I think it would be great if EventSource(path) would return the correct subclass.

I considered such a functionality when designing the factories. But I found it important to separate the base class from the factory class. One reason was to avoid the subclasses of EventSource and ChargeExtractor from inheriting the factory behaviour.
Personally, I don't see what is gained over the event_source() helper function. But I look forward to seeing your proposed implementation.

Hiding the Factory design pattern in the base class would be very confusing - that's not how most python classes work, and almost certainly would create circular dependencies, since the base class would need to know about all sub-classes (but sub-classes, which are plug-ins can be in different files, that require the base class to be loaded first), so I'm not sure how easy it would be to make something like that.

In any case, this may be connected to #844

closed by #916

authors: MaxNoe kosack watsonjj

repo: cta-observatory/ctapipe


text:
Generate a content using mezzanine with black background area

A new test mezzanine is created here https://github.com/cta-wave/mezzanine/issues/36#issuecomment-882644468
Can you generate a test content with this mezzanine which has a black background area for QR codes please?

Yes. Where is the full mezzanine content folder? https://dash-large-files.akamaized.net/WAVE/Mezzanine/under_review/2021-07-19/ is incomplete.

That is intended. It's just an experiment to see how much of a difference it makes. There's no need for all the streams.

Generated here: https://dash-large-files.akamaized.net/WAVE/vectors/2021-07-26/avc_sets/15_30_60/

@yanj-github Do you understand the process for connecting HTML+JS and test content sufficiently well to use this directly or do you need help from @louaybassbouss ?

We need to add new combination to the tests.csv. I can do it if you tell me which combination you need. is sequencial-track-playback with t33 ok for you?

Thanks all. Yes @louaybassbouss I just need it as 8.2 test. I would like to have the old t33 as well, if you can keep the old one but add the new one please?

Thanks all. Yes @louaybassbouss I just need it as 8.2 test. I would like to have the old t33 as well, if you can keep the old one but add the new one please?

Yes I will not touch the existing tests I will add a new folder  avc_15_30_60-2021-07-26-online (and one for avc_15_30_60-2021-07-26-local) with one test combination sequential-track-playbackxt33. I will do it tomorrow and let you know.

Thanks all. Yes @louaybassbouss I just need it as 8.2 test. I would like to have the old t33 as well, if you can keep the old one but add the new one please?

@yanj-github a new test sequential-track-playbackxt33 is generated in the new folder avc_15_30_60-2021-07-26-online. Please let me know if you have questions.

The new test is not working, I am not sure if this is issue on test or the contents but I tried the following mpd on dash player it didnt work. Can anyone help to investigate please? Not sure why we used dash-large-files.akamaized.net?
https://dash-large-files.akamaized.net/WAVE/vectors/2021-07-26/avc_sets/15_30_60/t33/stream.mpd

I tried the following mpd on dash player it didnt work. Can anyone help to investigate please?

The following works for me, how is it for you?
https://reference.dashif.org/dash.js/latest/samples/dash-if-reference-player/index.html?mpd=https://dash-large-files.akamaized.net/WAVE/vectors/2021-07-26/avc_sets/15_30_60/t33/stream.mpd

Not sure why we used dash-large-files.akamaized.net?

Because people explicitly complained about CORS when using the www.gpac-licensing.com server. Would you have expected another server or URL?

I tried the following mpd on dash player it didnt work. Can anyone help to investigate please?

The following works for me, how is it for you?
https://reference.dashif.org/dash.js/latest/samples/dash-if-reference-player/index.html?mpd=https://dash-large-files.akamaized.net/WAVE/vectors/2021-07-26/avc_sets/15_30_60/t33/stream.mpd

Not sure why we used dash-large-files.akamaized.net?

Because people explicitly complained about CORS when using the www.gpac-licensing.com server. Would you have expected another server or URL?

I have following error. Is this might be a permission issue please?
Error Dash.js :25
https://dash-large-files.akamaized.net/WAVE/vectors/2021-07-26/avc_sets/15_30_60/t33/stream.mpd is not available

Could someone else give a try please? Can you read:

https://dash-large-files.akamaized.net/WAVE/vectors/2021-07-26/avc_sets/15_30_60/t33/stream.mpd
https://reference.dashif.org/dash.js/latest/samples/dash-if-reference-player/index.html?mpd=https://dash-large-files.akamaized.net/WAVE/vectors/2021-07-26/avc_sets/15_30_60/t33/stream.mpd
?

Could someone else give a try please? Can you read:
* https://dash-large-files.akamaized.net/WAVE/vectors/2021-07-26/avc_sets/15_30_60/t33/stream.mpd

I can see this.

* https://reference.dashif.org/dash.js/latest/samples/dash-if-reference-player/index.html?mpd=https://dash-large-files.akamaized.net/WAVE/vectors/2021-07-26/avc_sets/15_30_60/t33/stream.mpd

But not this one.
@louaybassbouss  can you kindly help to check please?

Directly accessing https://dash-large-files.akamaized.net/WAVE/vectors/2021-07-26/avc_sets/15_30_60/t33/stream.mpd in Chrome works, I can read the MPD file.
With the dash.js link below, I got Error 25 also:
“https://dash-large-files.akamaized.net/WAVE/vectors/2021-07-26/avc_sets/15_30_60/t33/stream.mpd is not available”
Mike Bergman
Consumer Technology Association, producer of CES®
d: +1(703) 907-4366
m: +1(609) 865-4402
From: yanj-github @.>
Sent: Thursday, July 29, 2021 10:41 AM
To: cta-wave/Test-Content-Generation @.>
Cc: Subscribed @.***>
Subject: Re: [cta-wave/Test-Content-Generation] Generate a content using mezzanine with black background area (#42)
Could someone else give a try please? Can you read:

https://dash-large-files.akamaized.net/WAVE/vectors/2021-07-26/avc_sets/15_30_60/t33/stream.mpdhttps://dash-large-files.akamaized.net/WAVE/vectors/2021-07-26/avc_sets/15_30_60/t33/stream.mpd

I can see this.

https://reference.dashif.org/dash.js/latest/samples/dash-if-reference-player/index.html?mpd=https://dash-large-files.akamaized.net/WAVE/vectors/2021-07-26/avc_sets/15_30_60/t33/stream.mpdhttps://reference.dashif.org/dash.js/latest/samples/dash-if-reference-player/index.html?mpd=https://dash-large-files.akamaized.net/WAVE/vectors/2021-07-26/avc_sets/15_30_60/t33/stream.mpd

But not this one.
@louaybassbousshttps://github.com/louaybassbouss can you kindly help to check please?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHubhttps://github.com/cta-wave/Test-Content-Generation/issues/42#issuecomment-889203855, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AFLKEDEF74VS5MNCMFWTPOTT2FSAVANCNFSM5A7UUOOA.
Disclaimer
The information contained in this communication from the sender is confidential. It is intended solely for use by the recipient and others authorized to receive it. If you are not the recipient, you are hereby notified that any disclosure, copying, distribution or taking action in relation of the contents of this information is strictly prohibited and may be unlawful.
This email has been scanned for viruses and malware, and may have been automatically archived by Mimecast Ltd, an innovator in Software as a Service (SaaS) for business. Providing a safer and more useful place for your human generated data. Specializing in; Security, archiving and compliance. To find out more visit the Mimecast website.

Thanks. What about https://reference.dashif.org/dash.js/latest/samples/dash-if-reference-player/index.html?mpd=https://dash.akamaized.net/WAVE/vectors/2021-07-26/avc_sets/15_30_60/t33/stream.mpd ?

Thanks. What about https://reference.dashif.org/dash.js/latest/samples/dash-if-reference-player/index.html?mpd=https://dash.akamaized.net/WAVE/vectors/2021-07-26/avc_sets/15_30_60/t33/stream.mpd ?

Thank you very much. this is working.
@louaybassbouss Can you kinldy help to change the mpd link please?

Thanks. What about https://reference.dashif.org/dash.js/latest/samples/dash-if-reference-player/index.html?mpd=https://dash.akamaized.net/WAVE/vectors/2021-07-26/avc_sets/15_30_60/t33/stream.mpd ?

Thank you very much. this is working.
@louaybassbouss Can you kinldy help to change the mpd link please?

@yanj-github  done :)

authors: cta-source jpiesing louaybassbouss rbouqueau yanj-github

repo: cta-wave/Test-Content-Generation


text:
Create a new release for the latest commit

The latest commit fixed a backwards compatibility issue with gonum. Can you please make a new release with a new tag so that go mod uses the latest version ?

thanks, updating dependencies no longer breaks the build 👍

repo: ctessum/geom


text:
Unable to determine jdbc url from datasource

哪位大神帮忙看看，为啥我修改的数据库地址是105，然后日志中显示的是106连不上哩。。。配置文件及日志请见附件。
[root@localhost apollo]# ./demo.sh start
==== starting service ====
Service logging file is ./service/apollo-service.log
jdbc:mysql://192.168.1.105:3306/ApolloConfigDB?characterEncoding=utf8
Started [8715]
Waiting for config service startup........................
Config service failed to start in 120 seconds! Please check ./service/apollo-service.log for more information.
apollo-service.log
demo.sh.txt

看样子你对jdbc报错的信息没有理解，192.168.1.106是访问数据库的机器IP，不是数据库自己的IP
java.sql.SQLException: Access denied for user 'root'@'192.168.1.106' (using password: YES)

了解了，多谢指正。

repo: ctripcorp/apollo


text:
apllo 为什么不支持实时刷新端口

[ ] I have searched the issues of this repository and believe that this is not a duplicate.
[ ] I have checked the FAQ of this repository and believe that this is not a duplicate.

Describe the bug
A clear and concise description of what the bug is.
To Reproduce
Steps to reproduce the behavior:
1.
2.
3.
4.
Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
Additional Details & Logs

Version
Error logs
Configuration
Platform and Operating System

请详细描述下你的问题

我每次修改配置文件，springboot 应用都要重启，不然不生效，比如我server.port=8080改成8081 ，应用程序端口号没改过来。必须重启服务。感觉apollo热更新是假的

建议参考一下 https://github.com/ctripcorp/apollo-use-cases
apollo能确保配置的值实时更新，对于一些有初始化逻辑的场景是需要程序自己监听配置变化事件并做处理的，比如server.port。

请问参数热更新，是否支持更新为null。
比如：  策略的配置，仅仅在A、Btest或指定的时间内需要。如果不要改配置了，是否支持删除apollo中对应的配置项，然后对应Bean中的属性都变成null？
目标测试下来结果不支持。即使通过 ConfigChangeEvent 的方式也不行

apollo是支持删除配置的，你指的bean中的属性是通过spring注入的吧，这个要看你spring注入的placeholder怎么写了

authors: chenchenggen007 liquanjin nobodyiam


text:
答疑群无法加入

已经申请答疑群3天了，还未得到批准加入

刚刚通过了一批，你看看呢～

可以了~谢谢


text:
Server: move source-map-support/register into the config factory

I suggest to remove the import 'source-map-support/register'; instruction from src/server/index.js and :

add it as multi entry index in the config factory ;
add it in webpack-node-externals whitelist.

The main purpose is to always include the source-map-support package into the server bundle even if the instruction isn't in the source.
In addition, we can move source-map-support into devDependencies properties.
// tools/webpack/configFactory.js
// ...
export default function webpackConfigFactory(buildOptions: BuildOptions) {
  // ...
  const webpackConfig = {
  // ...
    externals: removeEmpty([
      ifNode(
        () => nodeExternals({
          whitelist: [].concat(
            config.nodeBundlesIncludeNodeModuleFileTypes || [],
            'source-map-support/register'
          )
        }),
      ),
    ]),
    // ...
    entry: {
      index: removeEmpty([
        isNode('source-map-support/register'),
        // ...
      ])
    }
    // ...
  }
// ...

Thanks @enten I agree with this. :)
Although, I am not sure that we can move it from devDependencies.  Surely it needs to be installed as a production dependency?

Great idea @enten. @ctrlplusb, I would say with 99.9% certainty, needs to be in the production deps

Below a compilation result (which is configured such as described).
Hash: b4581871dba03e1aff31
Version: webpack 2.1.0-beta.28
Time: 436ms
       Asset    Size  Chunks             Chunk Names
    index.js  118 kB       0  [emitted]  index
index.js.map  140 kB       0  [emitted]  index
chunk    {0} index.js, index.js.map (index) 113 kB [entry] [rendered]
    [0] ../~/source-map/lib/util.js 10.5 kB {0} [built]
    [1] ../~/source-map/lib/array-set.js 2.76 kB {0} [built]
    [2] ../~/source-map/lib/base64-vlq.js 4.71 kB {0} [built]
    [3] ../~/source-map/lib/source-map-generator.js 13.4 kB {0} [built]
    [4] external "fs" 42 bytes {0} [not cacheable]
    [5] ./src/server/index.js 1.22 kB {0} [built]
    [6] ../~/source-map-support/register.js 25 bytes {0} [built]
    [7] ./src/file.json 35 bytes {0} [built]
    [8] ./src/server/foo.js 150 bytes {0} [built]
    [9] ./src/test.js 45 bytes {0} [built]
   [10] ../~/source-map-support/source-map-support.js 16.1 kB {0} [built]
   [11] ../~/source-map/lib/base64.js 1.54 kB {0} [built]
   [12] ../~/source-map/lib/binary-search.js 4.25 kB {0} [built]
   [13] ../~/source-map/lib/mapping-list.js 2.34 kB {0} [built]
   [14] ../~/source-map/lib/quick-sort.js 3.62 kB {0} [built]
   [15] ../~/source-map/lib/source-map-consumer.js 38.4 kB {0} [built]
   [16] ../~/source-map/lib/source-node.js 13.5 kB {0} [built]
   [17] ../~/source-map/source-map.js 405 bytes {0} [built]
   [18] external "express" 42 bytes {0} [not cacheable]
   [19] external "module" 42 bytes {0} [not cacheable]
   [20] external "path" 42 bytes {0} [not cacheable]
   [21] multi index 40 bytes {0} [built]

We can see that source-map-support dependencies (locales and the external source-map) are included in the bundle.
So I think that we don't need this dependency.
Please try to:

make a build with this configuration adjustments
remove node_modules/source-map-support
and start the built server

@strues: I would say with 99.9% certainty, needs to be in the production deps

I'm note a webpack expert. Sir, can you explain please?

@enten You're 100% right. It works flawlessly

@enten awesome, thanks for that breakdown!
I am happy for us to move forward with this. 👍 💖

authors: ctrlplusb enten strues

repo: ctrlplusb/react-universally


text:
Docker container does not respond to SIGTERM signal

When calling docker stop snitch the container does not shutdown the services and exits. So it does not respond to SIGTERM signals. Docker will wait some time, by default 10 seconds, and then send SIGKILL to kill the process. Always waiting 10 seconds is kind of annoying. As a consequence your app won't shutdown gracefully at all in case that is important.
The issue is that you are calling bash entrypoint.sh to start 3 processes and bash ignores signals and does not forward them to processes. As a workaround I have to use docker run --init to let docker insert a small init process as PID 1 which then manages your bash entrypoint.sh process. That way I don't have to wait 10 seconds, but signals still won't be forwarded to your processes for graceful shutdown.
So at least add --init to your tutorial and/or make your PID 1 process more compliant.

Got to admit that Docker isn't my strongest suit, I'll do some reading and fix it - thanks for the tips!

A common work around for providing signal handling without implementing it, is to wrap tini around the entrypoint, and it will take care of the rest.

krallin/tini: A tiny but valid `init` for containers

It's a low effort solution.

authors: almereyda jnehlmeier sadreck

repo: ctxis/SnitchDNS


text:
Move License

Attempting to demostrate how CODEOWNERS works

Hey @natashaarmbrust. If you make @cuappdev/podcast-ios a child team of @cuappdev/developers this should work. Basically @cuappdev/podcast-ios doesn't "own" this repo because @cuappdev/developers does and @cuappdev/podcast-ios is NOT a child team.

done

repo: cuappdev/podcast-ios


text:
能不能写个脚本直接执行安装?

作为一个小白不懂ngnix的使用，看着你的教程晕头转向，要是你能弄个脚本，像shadowsocks一样支持一键简易配置安装的话。我想应该会得很好的推广的

这是我centos7上的安装脚本，不过nginx的配置文件仍然要自己写
#!/usr/bin/sh

# push pwd
pushd

cd /tmp

yum -y install wget build-essential git gcc g++ gcc-c++ make autoconf

# nginx
wget http://nginx.org/download/nginx-1.9.3.tar.gz \
    && tar xzvf nginx-1.9.3.tar.gz

# pcre1
wget ftp://ftp.csx.cam.ac.uk/pub/software/programming/pcre/pcre-8.36.tar.gz \
    && tar xzvf pcre-8.36.tar.gz

# opnssl
wget https://www.openssl.org/source/openssl-1.0.2d.tar.gz \
    && tar xzvf openssl-1.0.2d.tar.gz

# zlib
wget http://zlib.net/zlib-1.2.8.tar.gz \
    && tar xzvf zlib-1.2.8.tar.gz

# extention
git clone https://github.com/cuber/ngx_http_google_filter_module
git clone https://github.com/yaoweibin/ngx_http_substitutions_filter_module

cd nginx-1.9.3

./configure \
    --prefix=/usr/share/nginx \
    --sbin-path=/usr/sbin/nginx \
    --conf-path=/etc/nginx/nginx.conf \
    --user=nginx \
    --group=nginx \
    --with-ipv6 \
    --with-http_ssl_module \
    --with-http_spdy_module \
    --with-http_secure_link_module \
    --with-http_sub_module \
    --with-pcre=../pcre-8.36 \
    --with-zlib=../zlib-1.2.8 \
    --with-openssl=../openssl-1.0.2d \
    --add-module=../ngx_http_google_filter_module \
    --add-module=../ngx_http_substitutions_filter_module \

# build && install
make && make install

popd

# --------------------------------------------
#追加一个nginx组
groupadd -f nginx
#追加一个nginx用户
useradd -s /sbin/nologin -g nginx nginx

#建立nginx日志目录
mkdir /var/log/nginx
#赋予访问权限
chown nginx:nginx /var/log/nginx

echo "
[Unit]
Description=nginx
After=network.target syslog.target

[Service]
Type=forking
ExecStart=/usr/sbin/nginx
ExecStop=/usr/sbin/nginx -s quit
ExecReload=/usr/sbin/nginx -s reload

[Install]
WantedBy=multi-user.target
" > /lib/systemd/system/nginx.service

systemctl enable nginx.service

systemctl start nginx.service

systemctl status nginx.service

这个脚本我收藏了

authors: 2Dou knight-zhou mountainguan


text:
Separate out IR from the passes

Currently, the calyx crate pulls in all the dependencies for the IR and the passes. For Rust consumers, it makes more sense to separately include the crates for the just the IR or the passes to reduce dependencies

This also has the knock-on effect of speeding up compilation in some cases

authors: EclecticGriffin rachitnigam

repo: cucapra/calyx


text:
Idempotent cue/spec cue/format intention of spec, impl expectations

Cue Idempotence
Theoretical
Are the following interpretations of cue spec correct  (in a theoretical sense)?

Unification of a set of cuelang expressions in the same order-one time will yield the same result.

Unification of a set of cuelang expressions in any order-one time will yield the same result.

Unification of a set of cuelang expressions in the same order-any number of times will yield the same result.

Unification of a set of cuelang expressions in any order-any number of times will yield the same result.

Disjunction of a set of cuelang expressions in the same order-one time will yield the same result.

Disjunction of a set of cuelang expressions in any order-one time will yield the same result.

Disjunction of a set of cuelang expressions in the same order-any number of times will yield the same result.

Disjunction of a set of cuelang expressions in any order-any number of times will yield the same result.

Actual Impl

Is it reasonable to expect: Given []byte, an Instance produced by passing []byte to Unmarshal, then a the []byte produced by calling Marshal the produced Instance will return an identical []byte array to the original.
What is considered an operation?  Runtime has a note that states "Any operation that involves two Values or Instances should originate from the same Runtime.".
Does this include Merge on two instances.
Suppose two instances were Marshaled then Unmarshaled does the marshal need to be from the same Runtime to Unmarshal and merge together?
Is accurate to think of Merge as the Unification of the emit value (both in the explicit case and implicit case of all top-level values)?
Is it accurate to think of a Value as what the spec refers to as a expression ?
Could you help me understand how Value and ast.Expr relate to one another, as far as I understand ast.Expr is the position in the file where what the spec refers to as expression is written and Value is the evaluated result but I feel like I'm missing something.
Given a set of []byte, the set of Instances produced by passing []byte to Unmarshal, would you expect Merge and subsequent call to Marshal always to return the same []byte:

Given the set of []byte the same order-one time.
Given the set of []byte any order-one time.
Given the set of []byte the same order-any number of times.
Given the set of []byte any order-any number of times.

Theoretical
Yes, unification and disjunction are associative, commutative and idempotent, at least w.r.t. the theoretical outcome. So, the order of fields in structs may differ for different orders, as the order of fields in structs is semantically irrelevant (there is a proposal to at least guarantee topological consistency). There is a bug currently, though, where certain builtin constraints break commutativity as they are not monotonic and CUE doesn't handle this yet (this is certainly possible, though).
Actual Impl:

No, not in general. I assume with []byte, you mean CUE program. There are all kind of reasons why this may not be the same on a round trip. For instance, CUE is not required to preserve the order of fields (although implementing a best-effort topological sort would be nice).
Anything. So even when merging two Instances they should originate from the same Runtime. This restriction is an implementation detail and may be lifted.
3)Yes
No, Instances do not have to originate from the same runtime for them to be Unmarshaled by a a single one.
Sort of. Merge is like Unify, but with templates pre-expanded. IOW, it unifies the fully evaluated values (semantically, the implementation is more lazy).
A reasonable description. I would describe a Value as the value associated with a path in the configuration tree. It is true, though, that Value gives access to both the evaluated value as well as the raw expression.
ast.Expr is the result of a parse tree. It represents syntax. Value represents semantics: the value at the position in the configuration tree and is the result of partial or full evaluation.
Note that this is often not true for ast.Expr. The expressions related a particular point in the configuration tree may be scattered across multiple locations in the source and may be the result of more general constraint being applied (e.g. foo <Name>: constraint.
Evaluation computes the expression for a Value. The consumer of Value may analyze this as is or request the completion of the evaluation.
Not sure under which conditions you mean that, but generally no. But given the exact same bytes and same order, using the same binary, yes, although even then no guarantee of that can be given. I'm assuming that the bytes you are referring here are the binary encodings of a marshaled CUE representation, which (currently) are CUE programs with additional information. The data format is currently proprietary and may change over time. Even CUE programs itself may change. Even with order guarantee of fields, CUE will still have to invent variable names for variables that become shadowed as a result of computation, the algorithm of which may change over time.
But the semantics of the data, at least, should not change.

There is a bug currently, though, where certain builtin constraints break commutativity as they are not monotonic and CUE doesn't handle this yet (this is certainly possible, though).

Is there there a ticket for this bug?  Or, could you provide me an example of when this bug occurs?

Addressed by #78, for instance.
Closing, as there seems no action left associated with this.

This issue has been migrated to https://github.com/cue-lang/cue/issues/161.
For more details about CUE's migration to a new home, please see https://github.com/cue-lang/cue/issues/1078.

authors: cueckoo mpvl rudolph9

repo: cuelang/cue


text:
Can you please add this DFIR tool to the list ?

Hello !
Can you please add this DFIR tool to the list ?
https://github.com/YosfanEilay/ForensicMiner
Thank you !

Done!

Thank you !

authors: YosfanEilay cugu

repo: cugu/awesome-forensics


text:
点击【更多设置】后，程序自动退出了

作者君，可以看看这个问题吗，感谢您！

ClickShow1_4_1的包

可能少拷贝了文件？

repo: cuiliang/ClickShow


text:
Establish a schedule for developing and offering FOLIO training

We need to plan training and documentation, and publish that plan. We have gotten the following questions related to training:

[x] Are there public timelines for migration/training opportunities, etc.?
[x] Will in people on the pods be required to train everyone else?

People have also expressed concern that Libraries faculty/staff aren't absorbing the scope and depth of impacts on workflows and day-to-day processes. Hopefully creating a clear and public plan for the scope of the training and documentation will do some "show rather than tell".

Timelines show that we plan to create training from May through August and then deliver it from September to Jan 2023 and through go-live. We have considered a few models for training and may get some help from a vendor.

authors: CUSeif jwfuller

repo: culibraries/folio


text:
is it possible to speed up logistic regression with regularization ?

for example for very big sparse data  for binary target/labels
is it possible to speed up logistic regression with regularization?

CuPy does not have Scikit-Learn compatible functions.
I hope that NumPy implement NEP18.
Maybe we can support Scikit-Learn feature easily.

repo: cupy/cupy


text:
Fix scatter_add docs

cupy.scatter_add is deprecated. #894
This PR fixes to use cupyx.scatter_add.

Thanks
LGTM!


text:
Fix tests that have side effects

Rel #4138.
Currently, NotificationTestBase keeps the value of _ufunc_config._config and restores it on tearing down. However, the value of _config is an instance that is destructively changed and we need to have another object to properly restore its original contents.

pfnCI, test this please.

Jenkins CI test (for commit 792a5e196a994a091b2499a5ff8f8ea5aecffcc9, target branch master) succeeded!

authors: chainer-ci kmaehashi takagi


text:
[WIP] Fix random docstring

Fix docstrings of some Generator distributions.

Not draft for readthedocs preview.

Jenkins, test this please

Let me clean the commit log after being ready to merge.

Jenkins CI test (for commit b45eb6ec6548b207d3e9048fc82878b349be53a4, target branch master) succeeded!

I checked RTD preview to see the fix is okay. PTAL!

pfnCI, test this please.

Jenkins CI test (for commit 0ee1fff3f4748dae7f89b665a6117aa758dc0faf, target branch master) succeeded!

standard_exponential is in v9

@emcastillo Failed to backport automatically.

Not cleanly cherry-picked

@emcastillo This pull-request is marked as to-be-backported, but the corresponding backport PR could not be found. Could you check?

will backport manually

@emcastillo This pull-request is marked as to-be-backported, but the corresponding backport PR could not be found. Could you check?

@emcastillo This pull-request is marked as to-be-backported, but the corresponding backport PR could not be found. Could you check?

authors: chainer-ci emcastillo kmaehashi takagi toslunar


text:
Higher reported crashes on devices 1.5 - 2 GB of RAM / ARM Cortex-A53 CPU

Private Zenhub Image

We were unable to get any errors or warnings regarding this issue.

repo: curiouslearning/FeedTheMonsterJS


text:
error after HA restart increasing

Describe the bug
After HA restart the following error is in the log
System details

Home-assistant (version): 2021.3.4

Hassio (Yes/No): yes

alexa_media  (version from const.py or HA startup): latest

alexapy (version from pip show alexapy or HA startup):

Amazon 2FA is enabled (y/n). yes

Logs
Logger: homeassistant.config_entries
Source: custom_components/alexa_media/__init__.py:305
First occurred: 15:03:49 (1 occurrences)
Last logged: 15:03:49

Error setting up entry post@joerg-nauen.de - amazon.de for alexa_media
Traceback (most recent call last):
  File "/usr/local/lib/python3.8/site-packages/alexapy/helpers.py", line 144, in wrapper
    return await func(*args, **kwargs)
  File "/usr/local/lib/python3.8/site-packages/alexapy/alexalogin.py", line 574, in login
    if await self.test_loggedin(cookies):
  File "/usr/local/lib/python3.8/site-packages/alexapy/alexalogin.py", line 452, in test_loggedin
    await self.get_tokens()
  File "/usr/local/lib/python3.8/site-packages/alexapy/alexalogin.py", line 755, in get_tokens
    response = await self._session.post(
  File "/usr/local/lib/python3.8/site-packages/alexapy/aiohttp/client.py", line 544, in _request
    await resp.start(conn)
  File "/usr/local/lib/python3.8/site-packages/alexapy/aiohttp/client_reqrep.py", line 890, in start
    message, payload = await self._protocol.read()  # type: ignore
  File "/usr/local/lib/python3.8/site-packages/alexapy/aiohttp/streams.py", line 604, in read
    await self._waiter
alexapy.aiohttp.client_exceptions.ServerDisconnectedError: Server disconnected

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/config_entries.py", line 248, in async_setup
    result = await component.async_setup_entry(hass, self)  # type: ignore
  File "/config/custom_components/alexa_media/__init__.py", line 305, in async_setup_entry
    await login.login(cookies=await login.load_cookie())
  File "/usr/local/lib/python3.8/site-packages/alexapy/helpers.py", line 154, in wrapper
    raise AlexapyConnectionError from ex
alexapy.errors.AlexapyConnectionError

Additional context
I have to restart 3 to 4 times before it loads without issues

Amazon is disconnecting you. Not much we can do about it. Try relogging in.

OK, understood. What causes Amazon to throw me out?
Interesting thing is, that after the 3rd or 4th try it works.
Is there something which initiates this behavior?
I executed a Host restart yesterday which led to trouble with deConz. During the try to update, I restarted quite often. Could it be that this forced Amazon to thew me out?

It's all a guess on what would trigger a server disconnect. It could be the multiple connections but only amazon knows for certain.

OK thanks. I close this.


text:
A lot of "raw_decode raise JSONDecodeError" errors

Describe the bug
I have a lot this errors in log:
2019-11-11 21:31:35 ERROR (MainThread) [homeassistant.core] Error doing job: Task exception was never retrieved
Traceback (most recent call last):
  File "/home/homeassistant/.homeassistant/custom_components/alexa_media/media_player.py", line 278, in _handle_event
    await _refresh_if_no_audiopush(already_refreshed)
  File "/home/homeassistant/.homeassistant/custom_components/alexa_media/media_player.py", line 194, in _refresh_if_no_audiopush
    await self.async_update()
  File "/home/homeassistant/.homeassistant/custom_components/alexa_media/media_player.py", line 565, in async_update
    no_throttle=True)
  File "/home/homeassistant/.homeassistant/custom_components/alexa_media/helpers.py", line 143, in wrapper
    result = await func(*args, **kwargs)
  File "/home/homeassistant/.homeassistant/custom_components/alexa_media/media_player.py", line 362, in refresh
    session = await self.alexa_api.get_state()
  File "/srv/homeassistant/lib/python3.7/site-packages/alexapy/alexaapi.py", line 457, in get_state
    return await response.json(content_type=None)
  File "/srv/homeassistant/lib/python3.7/site-packages/aiohttp/client_reqrep.py", line 1040, in json
    return loads(stripped.decode(encoding))
  File "/usr/local/lib/python3.7/json/__init__.py", line 348, in loads
    return _default_decoder.decode(s)
  File "/usr/local/lib/python3.7/json/decoder.py", line 337, in decode
    obj, end = self.raw_decode(s, idx=_w(s, 0).end())
  File "/usr/local/lib/python3.7/json/decoder.py", line 355, in raw_decode
    raise JSONDecodeError("Expecting value", s, err.value) from None
json.decoder.JSONDecodeError: Expecting value: line 1 column 1 (char 0)

Expected behavior
No errors
System details

Home-assistant (version): 0.101.3
Hassio (Yes/No): No
alexa_media  (version from const.py or HA startup): 2.3.4
alexapy (version from pip show alexapy or HA startup): 1.3.2

This looks like your cookie file has expired. Delete and relogin. If you are using config flow, you can just remove and readd the integration with no need to restart.
I'll separately figure out why it's not properly forcing a relogin when it sees this.

After restart HA there are no errors in log and component works without relogin or any other action.

authors: alandtse bieniu


text:
Slug value doest not save in database in Lumen Framework.

Hi,
Hope you are doing great. I am using your package for Slug but I can not save slug value in databse .
I am using Lumen Framework.
$post = $this->create([
'title' => 'M ddddy Awesome Blog Hello Post piyush',
'tbl_user_login_id' => '1'
]);
        $post->save();

This code is not working in Lumen Framework.
Can you help me how this problem solve.

Can you provide some more information? Is it throwing errors, or just not saving data?
Also, if you can try the 4.0.0-beta release, I'm only likely supporting that version going forward.

Try again with the 4.0.1 release and re-open this ticket if the problem persists.

repo: cviebrock/eloquent-sluggable


text:
Compilation breaks for problems with no constraints

In the example, when I replace
problem = cp.Problem(cp.Minimize(cp.sum_squares(A @ x - b)), [x >= 0])
with
problem = cp.Problem(cp.Minimize(cp.sum_squares(A @ x - b)))
I get
>>> cpg.generate_code(problem, code_dir='nonneg_LS', solver='SCS')
Generating code with CVXPYgen ...
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/opt/homebrew/Caskroom/miniforge/base/envs/veclib/lib/python3.10/site-packages/cvxpygen/cpg.py", line 672, in generate_code
    utils.write_module_def(f, info_opt, info_usr, info_can)
  File "/opt/homebrew/Caskroom/miniforge/base/envs/veclib/lib/python3.10/site-packages/cvxpygen/utils.py", line 1227, in write_module_def
    max(info_usr[C.D_NAME_TO_SIZE].values())
ValueError: max() arg is an empty sequence

Replacing line 1227 with
max(info_usr[C.D_NAME_TO_SIZE].values(), default=0)
seems to fix the issue.

Fixed on master.

authors: SteveDiamond syanga

repo: cvxgrp/cvxpygen


text:
Actualize cyber-markets Gitcoin tasks

We need to formalize tasks for community

@vstavetski please, create one task)

repo: cybercongress/cyber-markets


text:
Support by-hash index acquisition

This PR implements by-hash index acquisition for go-apt-mirror.
As a side effect, this fixes #15.

@nojima
Please take a look but do not merge it now.
I am testing the changes with the real world repos.

@nojima
I have tested it with official ubuntu repos, dell OMSA, and zabbix.
One bug was found and fixed.  You can merge it if it looks OK.

I'll take a look

レビュー終わり。コメントの部分だけお願いします。

@nojima
Thank you. mirror.go のリファクタは別にやるとすると、storage のハッシュ問題だけで OK?

はい。

LGTM
CI が通ったらマージします。

Thank you!

repo: cybozu-go/aptutil


text:
Add default file associations

For Atom and the tmBundle editors.
VScode ignores this and has its own rules

@oliver-sanders Can you test this in TextMate or one of the others when you have a spare minute?

Sure, I don't think this can do any harm so perhaps just merge it and let the TM bundle rebuild (I think the GH action is broken again).

authors: MetRonnie oliver-sanders

repo: cylc/cylc-textmate-grammar


text:
Updated GPS initialization and parsing

Multiple changes to GPS handling.

Configure GNSS and NMEA messages at cold startup
Fixed byte-order bug on UART configuration
Set UART bit rate to 38400 bps. (Prevents message drops at 9600 bps / 10Hz; more reliable than higher rates)
Add validation of NMEA message checksums
Add support for u-blox 'PUBX' NMEA messages to reduce bandwidth requirement and simplify future satellite constellation parsing
Improved horizontal accuracy calculation
Add vertical velocity and vertical accuracy; update UI 'GPS/AHRS' page
Add satellites tracked and satellites seen; update UI 'Status' page

Changes tested on u-blox M8 (RY835AI UART) and u-blox 7 (VK-172 USB). Should be compatible with all u-blox 6, 7, and 8 series GPS.

Lots of errors on the first two or three starts:
2015/12/28 06:17:53 Using /dev/ttyAMA0 for GPS
2015/12/28 06:17:53 GPS configuration complete
2015/12/28 06:17:54 GPS error. Invalid NMEA string: Invalid NMEA message
2015/12/28 06:17:54 GPS error. Invalid NMEA string: Checksum failed. Calculated 0X9F; expected 0X1F
2015/12/28 06:17:54 GPS error. Invalid NMEA string: Checksum failed. Calculated 0XB4; expected 0X34
2015/12/28 06:17:54 GPS error. Invalid NMEA string: Checksum failed. Calculated 0XB5; expected 0X35
2015/12/28 06:17:54 GPS error. Invalid NMEA string: Checksum failed. Calculated 0XB2; expected 0X32
2015/12/28 06:17:54 GPS error. Invalid NMEA string: Checksum failed. Calculated 0XB3; expected 0X33
2015/12/28 06:17:54 count == 0, doing cleanup if necessary...
2015/12/28 06:17:54 GPS error. Invalid NMEA string: Checksum failed. Calculated 0XB0; expected 0X30
2015/12/28 06:17:54 GPS error. Invalid NMEA string: Checksum failed. Calculated 0XBF; expected 0X3F
2015/12/28 06:17:54 GPS error. Invalid NMEA string: Checksum failed. Calculated 0XB7; expected 0X37
2015/12/28 06:17:55 GPS error. Invalid NMEA string: Checksum failed. Calculated 0XB6; expected 0X36
2015/12/28 06:17:55 GPS error. Invalid NMEA string: Checksum failed. Calculated 0X9F; expected 0X1F
2015/12/28 06:17:55 GPS error. Invalid NMEA string: Checksum failed. Calculated 0XA1; expected 0X21
2015/12/28 06:17:55 GPS error. Invalid NMEA string: Checksum failed. Calculated 0XB5; expected 0X35
2015/12/28 06:17:55 GPS error. Invalid NMEA string: Checksum failed. Calculated 0XB3; expected 0X33
2015/12/28 06:17:55 GPS error. Invalid NMEA string: Checksum failed. Calculated 0XB2; expected 0X32
2015/12/28 06:17:55 count == 0, doing cleanup if necessary...
2015/12/28 06:17:55 GPS error. Invalid NMEA string: Checksum failed. Calculated 0XBB; expected 0X3B
2015/12/28 06:17:55 GPS error. Invalid NMEA string: Invalid checksum
2015/12/28 06:17:55 GPS error. Invalid NMEA string: Checksum failed. Calculated 0XEB; expected 0X6B

It seems like they subsided after running it a few times? Something with the config?

$G�GG�,073749.90,,,,,0,00,99.99,,,,,,*61
$�UB�,00,073749.90,4228.62405,N,08339.66695,W,239.599,NF,9466308,6693691,0.000,0.00,0.000,,99.99,99.99,99.99,0,0,0*34

Some messages coming through like this - checksum is OK but message is garbled.

Your checksums suggest a single bit error on the MSB, where a "0" is being flipped to "1". I saw something similar once during testing; the GPS log on that stat showed multiple single-bit errors on the NMEA messages (anonymized example below).
The top row is what was received by the RPi; the bottom is what actually would have been sent. The extended ASCII characters in the top row (Â, Ø, Î, ×, Ä) are 0x80 offsets from the "correct" characters on the bottom row.
$PUÂØ,00,052918.10,44nn.nnnnn,Î,093nn.nnnnn,×,258.000,Ä3,1.5,2.2,0.175,23.89,0.015,,1.03,1.51,1.05,10,0,0*78
$PUBX,00,052918.10,44nn.nnnnn,N,093nn.nnnnn,W,258.000,D3,1.5,2.2,0.175,23.89,0.015,,1.03,1.51,1.05,10,0,0*78

I'd guess that this could be a sync / timing error on the port; I reset the RPi bit rate from / to 38400 (stty -F /dev/ttyAMA0 9600; stty -F /dev/ttyAMA0 38400) and the problem cleared itself in real time. itself. It didn't come back on the next reset, and I haven't seen it since.
As far as a fix / prevention, a lower bit rate might help. The new code only needs about 12 kbps to feed messages at 10 Hz (including the 1 Hz status messages), so I don't see any reason this couldn't be dropped down to 19.2 kbps.

Turned off AHRS and it cleared up after restarting gen_gdl90, not sure if coincidence or not.

Try https://github.com/AvSquirrel/stratux/commit/48f3170df9190b168f00bba2f14d07c15ca5391e .
This adds a 250 ms delay after GPS initialization completes, before the port is reopened at 38.4k.
I noticed at the beginning of the GPS logs that I was picking up the ACKs from UBX configuration messages. Could be that the GPS is slower than the RPi to respond. This should give the GPS a chance to "settle in" before reading at the higher rate.

authors: AvSquirrel cyoung

repo: cyoung/stratux


text:
not fitted for windows?

Hi,
After pip install, simple "python -m keepasshttp www.amazon.com" fails, see traces below.
I noticed that no ~/.keepasshttp_key was created, as working on Windows.
Workaround "kph = KeePassHTTP(storage="./keepasshttp_key", url="http://localhost:19455/")" didn't fix anything.
any help?
Christophe
full trace:
(base) c:\Utilisateurs\FR20340\OneDrive\Personnel\hacking\keepass-over-http>python -m keepasshttp www.amazon.com
Traceback (most recent call last):
File "C:\Anaconda3\lib\runpy.py", line 193, in run_module_as_main
"main", mod_spec)
File "C:\Anaconda3\lib\runpy.py", line 85, in run_code
exec(code, run_globals)
File "C:\Anaconda3\lib\site-packages\keepasshttp_main.py", line 139, in
print(cmd_line())
File "C:\Anaconda3\lib\site-packages\keepasshttp_main.py", line 133, in cmd_line
credentials[credential] = kph.get(credential)
File "C:\Anaconda3\lib\site-packages\keepasshttp\keepass_http.py", line 130, in get
entries = self.search(key)
File "C:\Anaconda3\lib\site-packages\keepasshttp\keepass_http.py", line 113, in search
data = self._request("get-logins", Url=key, SortSelection=sort_keys)
File "C:\Anaconda3\lib\site-packages\keepasshttp\keepass_http.py", line 189, in _request
self._load()
File "C:\Anaconda3\lib\site-packages\keepasshttp\keepass_http.py", line 152, in _load
self.uid, self.db_hash = self._register()
File "C:\Anaconda3\lib\site-packages\keepasshttp\keepass_http.py", line 171, in _register
data = self._request("associate", Key=base64.b64encode(self.key))
File "C:\Anaconda3\lib\site-packages\keepasshttp\keepass_http.py", line 203, in _request
raise KeePassHTTPException("KeePassHTTP returned an error")  # pragma: no cover
keepasshttp.keepass_http.KeePassHTTPException: KeePassHTTP returned an error
(base) c:\Utilisateurs\FR20340\OneDrive\Personnel\hacking\keepass-over-http>

Apologies, the issue is related to my proxy.
On line 203, requests module fails to connect to local:19455 because of the environment variable declaring a proxy. by unsetting the env variables (del os.environ['HTTP_PROXY']) I managed to fix the issue, which is definitely not at your side.
so I'm happy with your module, finally. thank you for it !


text:
Not an issue. I just want to thank you

It just works, thank you so much. I tried all the other libraries for python and nodejs. This is the one <3

Hey, thank you! Thanks for taking the time to write such kind words... :)

repo: cyrus-and/chrome-remote-interface


text:
Fix #3057: Implement include_once statement.

Implement include_once statement. (#3057)
The include_once statement behaves like the include statement, with the only difference being that if the file has already been included in the module, it will not be included again.

Thanks, but I do not think this use case merits a new keyword (and the resulting breakage of user code).

authors: nicopauss scoder

repo: cython/cython


text:
Fix loop var declaration

https://github.com/cython/cython/commit/584078a371ef412554a2cd0b96fcc20fb3b9c476 looks like it introduced a minor typo.

CC @scoder

Thanks

authors: scoder vyasr


text:
Add option to silence IF deprecation warning

Over in https://github.com/h5py/h5py/pull/2444 the GitHub actions logs get clogged with hundreds/thousands of:
  warning: h5py/api_types_hdf5.pxd:710:2: The 'IF' statement is deprecated and will be removed in a future Cython version. Consider using runtime conditions or C macros instead. See https://github.com/cython/cython/issues/4310

The proper solution is to fix these. But in the meantime, it would be nice if I could:

Open a GitHub issue about it for h5py to keep track of it with milestones etc., and
Silence the warnings in the meantime so the build logs are more readable

This PR moves toward (2). Consider it a proposal-as-PR so feel free to close if it's not the way to go -- I wanted to see if it was doable at all and it turned out not to be too bad to get something that worked for h5py at least, where we could with this PR do cythonize(..., compiler_directives={'warn.deprecated_if': False}).

... and if this does seem worthwhile, I'm happy to look into the Cython contributing guide on how to clean this up / what else needs to be added.

Thanks

authors: da-woods larsoner


text:
Upgrade webpack to 4.32.2

I import cytoscape-dagre in ember.js and cannot work after the build. The error is Not possible to find intersection inside of the rectangle.
After upgrade webpack to 4.32.2 version. cytoscape-dagre works well.
So I suggest to  Upgrade webpack to 4.32.2.

That looks like an issue with Dagre and/or your data, not the build process.
Please demonstrate that there is a precise issue with the build process and that upgrading webpack would solve it.


text:
Wrong Values of the 'Etched Sigil'

In the Game the Offhand 'Etched Sigil' has an 150% damage boost, but here it don't

Items normally have the original value, but if you search and implement a build you get items with wrong values.
Here with the Etched Sigil : https://www.d3planner.com/726248047
And here with the Bracers of the First Man: https://www.d3planner.com/116877321
Both builds are just loaded and not altered, both are from Rhykker.

They're using legacy versions of the items. You can see that by clicking the item and the box in the middle section will say (Legacy).
I noticed that some of the featured builds use wrong versions of items, I'm guessing the authors modified old builds and forgot to replace the items. Not much I can help with here.


text:
🛑 Staging Webhook Public Api is down

In 4ee497b, Staging Webhook Public Api ($STAGING_WEBHOOK) was down:

HTTP code: 503
Response time: 346 ms

Resolved: Staging Webhook Public Api is back up in bd10149.


text:
Infinite loop in ticks function

In the ticks function, there is a way to create an infinite loop.
d3.axisBottom(x)
                .tickFormat(d3.timeFormat("%m/%y")).ticks(d3.timeMonth)
                .ticks(d3.timeDay.filter(function(d) {
                    console.log(d.getFullYear(), d.getMonth, d.getDate())l
                    return d.getMonth() === 10;
                }))

Here, I wanted to show ticks only for data points in November. This condition happened to always be false.
Despite the x.domain() begin from 2002 to 2023 in my data, the loop runs from the year 2023 backwards in time, to negative infinity. At least I think - the last time, I interrupted the loop at around 400 B.C.
To recreate the issue:
d3.axisBottom(x)
                .tickFormat(d3.timeFormat("%m/%y")).ticks(d3.timeMonth)
                .ticks(d3.timeDay.filter(function(d) {
                    return false;
                }))

This isn’t related to d3.ticks; the loop occurs within your faulty filtered time interval because the filter never returns true. You can see the loop here:
https://github.com/d3/d3-time/blob/08cdaa68cdfbd44342342d99ea133979d599c01d/src/interval.js#L38-L50
You can reproduce the problem here:
const filter = d3.utcDay.filter(() => false);
filter(new Date);

It's not faulty, I just don't want to show any ticks unless there is data in November. The data is otherwise fine. If I don't try to create ticks, the chart works fine otherwise.
An infinite loop should never be expected behavior; in this case, the reasonable behavior would be to return no ticks and let the chart render normally.

authors: Monsignor mbostock

license: isc


text:
zoomoutLimit缩放bug

@dabeng
$('#chart-container').orgchart({
'data': this.datascource,
'nodeContent': 'title',
'pan': true,
'zoom': true,
'toggleSiblingsResp': true
});
使用jquery方式初始化orgchart，缩放功能正常，但是如果在不刷新页面的情况下，将$('#chart-container').html('')清空后再次使用orgchart重新初始化，会提示Uncaught TypeError: Cannot read property 'zoomoutLimit' of undefined

to redraw chart, dont empty chart container div using: $('#chart-container').html('')
use this solution:
make chart with empty datasource when your page is ready for first time:
diagram = $('#OrgChartDiagram__chartContainer').orgchart({
'data': null,
'nodeContent': 'title',
'zoom': true
});
( digram is a global variable)
then, for further usage just use:  diagram.init({ 'data': datascource });
this will refresh your diagram.


text:
perf: only allocate vector for inner_get_car_positions when necessary

inner_get_car_positions is a hot function, and it recurses.  In its hottest invocation (including it's own recursion) we only care about the position of the last car, so we can avoid allocating all the intermediate positions. This complicates the method a a bit, but it's a pretty hefty performance gain: 12-13% less runtime for me.
Command ran:
$ cargo flamegraph --bin run_scenario -- --disable_turn_conflicts --infinite_parking --disable_block_the_box --alerts=silence --disable_recalc_lc data/system/scenarios/downtown/weekday.bin --hours=8

before
- After 3m26.7s, the sim is at 08:00:00.0. 19,606 live agents
Advance sim to 08:00:00.0 took 206.7296s
run simulation... plus 0.0000s
run simulation took 206.7296s

(search highlight is for "malloc" which accounts for most of the improvement)
after
- After 2m59.9s, the sim is at  07:59:53.4. 18,968 live agents
Advance sim to 08:00:00.0 took 180.3246s
run simulation... plus 0.0000s
run simulation took 180.3246s

Awesome, thank you! I saw get_car_positions was a clear hot-spot, but thought that's fundamental to what it does, and didn't dig in and see the malloc. I don't think the new code is much more complicated.

authors: dabreegster michaelkirk

repo: dabreegster/abstreet


text:
Views compile issue

I compile my views with this
 cancompile: {
      options: {
        version: '2.1.1'
      },
      dist: {
        src: ['**/*.mustache'],
        dest: 'production/views.production.js'
      }
    },

and concat it with this
concat: {
      dist: {
          src: [
          'bower_components/jquery/dist/jquery.js',
          'bower_components/canjs/can.jquery.js',
          'bower_components/bootstrap/dist/js/bootstrap.js',
          //'js/**/*.js'
              'js/models/placetype.js',
              'js/models/place.js',
              'js/components/place/filter/filter.js',
              'js/components/place/list/list.js',
              'js/components/place/item/item.js',
              'js/components/placetype/filter/filter.js',
              'js/components/place/map/map.js',
              'js/pages/test/home/home.js',
              'js/pages/test/place/place.js',
              'js/pages/home/home.js',
              'js/pages/about/about.js',
              'js/pages/place/place.js',
          'js/app.js', // You app
          '<%= cancompile.dist.dest %>' // The compiled views
        ],
        dest: 'production/production.js'
      }

But if i run my app with the created production.js it tell's me "can.view: No template or empty template"
Here an example of a controller:
    can.Component.extend({
        tag: 'placetypefilter',
        template: can.view('js/components/placetype/filter/views/filter.mustache'),

In the views.production.js i have code like this:
can.view.preloadStringRenderer('\js\components\place\filter\views\filter_mustache', .....

I'd be this is a windows path separator problem. Your view preload function should convert the name into something like
can.view.preloadStringRenderer('js_components_place_filter_views_filter_mustache',

It is using can.view.toId at https://github.com/daffl/can-compile/blob/master/lib/compile.js#L59.

This should be solvable by providing a custom normalizer though:
var path = require('path');

cancompile: {
  options: {
    version: '2.1.1',
    normalizer: function(filename) {
      return filename.replace(new RegExp(path.sep, 'g'), '/');
    }
  }
}

Warning: Object function (filename) {
return filename.replace(new RegExp(path.sep, 'g'), '/');
} has no method 'indexOf' Use --force to continue.

Well what does filename look like? I guess filename.toString().replace(new RegExp(path.sep, 'g'), '/').substr(1); is an option, too.

i created this
cancompile: {
options: {
version: '2.1.1'
},
dist: {
src: ['**/*.mustache'],
dest: 'production/views.production.js'
},
normalizer: function (filename) {
return filename.replace(new RegExp(path.sep, 'g'), '/');
},
},
was filename only a placeholder? sorry i'am a grunt newbie :-)

oh i think i found the problem. :-)
the normalizer was in the wrong place
cancompile: {
options: {
version: '2.1.1',
normalizer: function (filename) {
return filename.replace(new RegExp(path.sep, 'g'), '/');
},
},
dist: {
src: ['**/*.mustache'],
dest: 'production/views.production.js'
}
},

Cool. If that works I'll probably make a new patch release that takes this into consideration so you should be able to remove the normalizer (but don't have to). This hasn't been tested on Windows a lot (in fact I think you're the first one that got it working ;).

if it works i will tell you. now it fails on the first  view. i think the regex has a problem i will check this. it should replace "/" with "_". right?

can you explain me this: new RegExp(path.sep, 'g')
Path.sep = '_' o '/'
what does g mean?

It looks for all instances of the match.
http://stackoverflow.com/questions/12993629/the-g-flag-in-regular-expressions
https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/RegExp

Also path.sep should be \ in Windows. Basically we want to replace every \ with / so that can.view.toId works right.

ok changed the normalizer to this
normalizer: function (filename) {
return filename.replace(new RegExp('\\', 'g'), '/');
},
Know it compiles my views and i the views.production.js i have this:
can.view.preloadStringRenderer('js_components_place_filter_views_filter_mustache'
But my production.js doesn't work.
GET http://localhost:57253/frontend/production/js/components/place/item/views/view.mustache 404

Can you send a views.production.js and the can.view call that doesn't work?

Here my can view call:
template: can.view('js/components/placetype/filter/views/filter.mustache'),
the views.production.js i send to your email. every can.view call fails with 404

It turned out that the Component tags were not dash-separated. Unfortunately Mustache allows component names without a separating dash but they do not seem to work in production.

authors: cpiock daffl marshallswain

repo: daffl/can-compile


text:
Error: unknown command "project" for "dagger"

Env:
dagger version
dagger v0.9.4 (registry.dagger.io/engine) darwin/arm64
From documentation
https://archive.docs.dagger.io/0.2/1200/local-dev
it says:
git clone https://github.com/dagger/todoapp
cd todoapp
dagger project update
dagger do build

But  get error:
dagger project update
Error: unknown command "project" for "dagger"
Run 'dagger --help' for usage.

You're seeing documentation for the archived 0.2 version (notice URL: https://archive.docs.dagger.io/0.2/1200/local-dev), but you're using version 0.9.4. See notice on top of page:

You can find the updated getting started guide at:
https://docs.dagger.io/quickstart/120918/setup
@vikram @jf, the notice at the top should probably be in a red tone, right? At first glance my eyes skipped it, only looked more closely because I knew it was an outdated doc and there had to be a notice somewhere.

@JCzz Let us know if you have any more issues 🙂

Thanks, that worked. Looking forward to play around :-)

@vikram-dagger @slumbering, the notice at the top should probably be in a red tone, right? At first glance my eyes skipped it, only looked more closely because I knew it was an outdated doc and there had to be a notice somewhere.

Correct, the banner should not be blue 👍 ! I would go for orange (a warning color).

Updated on archive.docs.dagger.io and https://archive.docs.dagger.io/0.2/

authors: JCzz helderco vikram-dagger

repo: dagger/dagger


text:
✨ Allow cache volumes as CLI parameters

What are you trying to do?
I have a module with the following constructor:
func New(
	// ...

	// Disable mounting cache volumes.
	disableCache Optional[bool],

	// Module cache volume to mount at /go/pkg/mod.
	modCache Optional[*CacheVolume],

	// Build cache volume to mount at ~/.cache/go-build.
	buildCache Optional[*CacheVolume],
) *Go {
	// ...
}

Currently, running this module in the CLI fails due to CacheVolume being an unsupported CLI argument:
❯ dagger call -m "github.com/sagikazarmark/daggerverse/go@main" --help
✘ load call ERROR [1.21s]
├ [0.56s] loading module
├ [0.65s] loading objects
┃ Error: unsupported object type "CacheVolume" for flag: mod-cache

Given cache volumes are created by their names (and that other types of objects, like files, are also referenced simply by their path or ID), I think it would be useful to do the same for cache volumes. In this instance:
❯ dagger call -m "github.com/sagikazarmark/daggerverse/go@main" --mod-cache go-build

An alternative I can imagine is adding a pragma comment for ignoring certain arguments from the CLI, but including them in the generated code. That's a temporary measure, but would still be easier for module developers, so they can utilize constructors instead of falling back to method chaining for tasks like setting cache.
Why is this important to you?
No response
How are you currently working around this?
I will probably remove those arguments from the constructor for now.
I might add them to the module API, but honestly, I'd rather not.

I usually author the module to manage the cache volumes. Curious about the use cases for wanting to provide the cache volume's name in the CLI.

I had some trouble with pipelines running in parallel using the same cache: https://github.com/dagger/dagger/issues/3345#issuecomment-1862711990

authors: helderco sagikazarmark


text:
No events in TaskEventWatcher

Currently im unable to track events with the TaskEventWatcher. Even the sample TestTaskWatcher.zip does not deliver any event entries for my system.
Im working on a Win10 machine. Ver: 1803 (Build 17234.829)
Im using TaskSheduler .NuGet package in Version 2.8.11.
Maybe i have to activate something to be able to track events (Task History)?
I tried it with differend approaches:
Only watching folder, only watching task.
Filtering events, removing filter. etc:
current implementation:
  using (TaskService ts = new TaskService())
        {
            TaskFolder folder;
            folder = ts.GetFolder(@"\" + ScheduledTaskConstants.TaskFolder);
            watcher = new TaskEventWatcher(folder);
            //watcher.Filter.EventLevels = new int[] {0};

            //watcher.Filter.TaskName = t.Name;
            watcher.EventRecorded += Watcher_EventRecorded;
            watcher.IncludeSubfolders = true;
            watcher.SynchronizingObject = ui;
            watcher.Enabled = true;
        }

The eventrecorded method gets never triggered. As it is not triggered in the TestTaskWatcher.zip
Any ideas?

The code for the TestTaskWatcher was out of date, so that .zip file is now updated. The code you're running disposes the TaskService instance after the watcher is instantiated thereby rendering it useless. Instead of creating a new instance of TaskService, use the TaskService.Instance. (In your code above, just replace the ts variable with TaskService.Instance. Are you using the code provided at https://github.com/dahall/TaskScheduler/wiki/EventSamples#task-event-watching?

Thx for updating the TestTaskWatcher.zip!
Before adapting my code, i would like to see the sample work.
Currently it does not deliver any entries.
I have activated the Task History on my machine, to check if the tasks that im watching are generating events.
That is the case:

But no event is shown in TestTaskWatcher.zip.
How i am configuring it (Watch folder with Include subfolders, or watch the task directly) seems to have no effect at all.
Is there something special regarding the generated tasks that i have to be aware of?
Are you receiving entries with the current zip?

Telling my instance to watch the root and subfolders, it works every time.

That is realy crazy. Not sure what is wrong on my site...
I just close it for now and check on other machines, if this behaviour still exists.
Thx!

authors: Weltraumputze dahall

repo: dahall/TaskScheduler


text:
Exception: Cannot find module '@umijs/fabric'

Code snippet triggering the exception
// INSERT CODE HERE

Logs
(Please select ALL logs in "JS/TS Import/Export Sorter" Output window and copy/paste here)
INSERT LOG HERE

Edit:
Exception: Cannot find module '@umijs/fabric'
Require stack:-
/Users/wangqi/ecs/myapp/.prettierrc.js-
/Users/wangqi/.vscode/extensions/dozerg.tsimportsorter-3.0.4/node_modules/prettier/third-party.js-
/Users/wangqi/.vscode/extensions/dozerg.tsimportsorter-3.0.4/node_modules/prettier/index.js-
/Users/wangqi/.vscode/extensions/dozerg.tsimportsorter-3.0.4/out/config/prettier.js-
/Users/wangqi/.vscode/extensions/dozerg.tsimportsorter-3.0.4/out/config/importSorter.js-
/Users/wangqi/.vscode/extensions/dozerg.tsimportsorter-3.0.4/out/config/index.js-
/Users/wangqi/.vscode/extensions/dozerg.tsimportsorter-3.0.4/out/extension.js-
/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/loader.js-
/Applications/Visual Studio Code.app/Contents/Resources/app/out/bootstrap-amd.js-
/Applications/Visual Studio Code.app/Contents/Resources/app/out/bootstrap-fork.js

@1414551889
Thanks for the feedback!
Could you provide your logs and the code snippet triggering the exception?

Hi @1414551889,
I believe the issue was related to bad configuration of prettier, so I suppressed the error in release v4.1.0.
Please check out and tell me if there are still issues.
I'll close the issue for now.
Thanks!

repo: daidodo/tsimportsorter


text:
TagBot trigger issue

This issue is used to trigger TagBot; feel free to unsubscribe.
If you haven't already, you should update your TagBot.yml to include issue comment triggers.
Please see this post on Discourse for instructions and more details.
If you'd like for me to do this for you, comment TagBot fix on this issue.
I'll open a PR within a few hours, please be patient!

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/97317

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/97598

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/97613

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/97651

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/110199


text:
Installation in Offline Mode

Thank you for your work.
It's possible to add documentation on the readme for an installation in offline mode ?
When I install the ModernAD.psm1 on my offline server the ReportHTML module is not present so I must install it manually with a nupkg file...
https://www.powershellgallery.com/packages/ReportHTML/1.4.1.2

Hello,
No, there is two way to offline installation, get the last package using the powershell command from a machine who have internet  :
Save-Module -Name ModernActiveDirectory -Path “FilePath”
Then copy the folder on your server directory :
C:\Program Files\WindowsPowerShell\Modules
and from powershell run :
Import-Module -Name ModernActiveDirectory

I add a Offline version,
Download the file from release (v1.0.9.zip)
and place the three folder (ModernAD, PSWriteHTML, PSWriteEXECl) on your folder :
For All users this path :
C:\Program Files\WindowsPowerShell\Modules
For current user (no require privilege)
Document\WindowsPowerShell\Modules
and Run :
Import-Module -Name ModernActiveDirectory -force

hello, what command do you use to modify the logo? normally it is possible to add the logo in .bmp format with the -logo argument.
can i see an picture of error ?


text:
Allow for specifying the preferred auth schemes in http requests.

In my specific case that patch allowed me to work around an annoying warning at each and every http request that crowded the log file:
[2019-06-05T12:40:01,590][WARN ][o.a.h.i.a.HttpAuthenticator] NEGOTIATE authentication error: Invalid name provided (Mechanism level: KrbException: Cannot locate default realm)

The server accepts NEGOTIATE and NTLM but NEGOTIATE fails.
The patch lets me do requests like this:
(get "http://whatever-ms-server.com/some/page.aspx"
     {:ntlm-auth ["user" "password"]
      :auth-schemes ["NTLM"]})

The :auth-schemes parameter avoids the NEGOTIATE attempt.

@fourtytoo would you mind adding a blurb to the README including this option? Otherwise I think it'd probably get lost without documentation.

authors: dakrone fourtytoo

repo: dakrone/clj-http


text:
Missing bower.json

Isn't now, with release 0.4.0, possible to include automatically lib with grunt wiredep?

Perhaps, but maintenance of the bower.json isn't so much the issue.
This project will be moving to semantic-release soon and I don't see bower fitting into that model.
If your using grunt, you are likely installing grunt with npm, right?  Is it Okay to also resolve this component with npm?
Perhaps I should have left #238 up a bit longer. =)

Removing bower.json has broken my build process.  We rely on wiredep in our build process and without the bower.json this library is completely missed as a result.
Any chance this decision can be reconsidered.

You can stay on 0.3.15 for now, that way your build will continue to work. If you need a later version you have a couple of options.

Use overrides or [pluggable-resolvers] (http://bower.io/docs/pluggable-resolvers/) to get the later version in a way that doesn't cause bower to complain about the missing bower.json.
Move to Browserify or Webpack
Probably something else that I don't know about. =)

I'll work on accepting a PR to keep bower support I get semantic-release working for a few minor revisions.

Does this help? https://roots.io/using-bootstrap-with-bower-how-to-override-bower-packages/

:-1:

:-1:

@zhouguangming and @martinsznapka  if you want bower support, you can do it yourself (probably in the same amount of time needed to post thumbs down)

@dalelotts
I like this project,
I appreciate your work.
I don't like your decision to drop bower support.
I don't have time to search for workarounds and implement them somehow in our grunt/wiredep/bower project.
I am still using 0.X.X bower version.
So that's the status.
If you have any solution for us "bower users" how to use 1.X.X, please put it into README.
Thank you.

@martinsznapka Not sure what you're having trouble with - there are multiple solutions posted earlier in this issue - all of them work just fine.
The easiest are to stay on 0.3.15 for now, that way your build will continue to work. If you need a later version you have a couple of options.
Otherwise, use overrides so bower doesn't  complain about the missing bower.json - this only takes a minute but you will have to read the bower documentation to understand it.
http://image.slidesharecdn.com/onlineforumapril9th4apr14-140410062527-phpapp01/95/are-you-too-busy-to-improve-part-1-1-638.jpg?cb=1397111234

authors: dalelotts martinsznapka portus84 talvor zhouguangming


text:
Is there anyway to build with 7.1?

Module file's minimum deployment target is ios8.0 v8.0: /Users/xx/Library/Developer/Xcode/DerivedData/xx-hecyatfhzkoghledmajwnqforwij/Build/Products/Debug-iphoneos/Pods/SwiftHTTP.framework/Modules/SwiftHTTP.swiftmodule/arm.swiftmodule

my bad,

repo: daltoniam/SwiftHTTP


text:
What should NoConns be able to do?

"Policy" questions on what the no-connect Signal-type should and should not allow.
The initial implementation from #7 has:

(a) "Strict" single-port, no other connection to anything requirements
(b) Connects to Signals, not Bundles

Questions and proposals:

Should they be allowed to connect non-unity-width ports?

Propose yes. This is part of #33.

Should they be allowed to connect to Bundle valued ports?

Propose yes. This is part of #33.

Should they be allowed in Concat?

Propose yes
I suppose the weird part would be the inference of widths, given the answers above. The most clear, I guess, would be inferring each NoConn as unit-width(?).
This may be a "no for now", just make a Signal instead, especially for non-unit widths.

Should they be allowed in AnonymousBundle?

Propose yes

Should they be Slice-able?

Propose no

Should stuff like the test in #7 work, or fail:

@h.module
class Inner:
  p = h.Port()

@h.module
class Bad:
  # Create two instances of `Inner`
  i1 = Inner()
  i2 = Inner()

  # Connect the first to a `NoConn`
  i1.p = h.NoConn()
  # And then connect the second to the first.
  # Herein lies the "problem"
  i2.p = i1.p

Currently this fails.
The rationale: NoConn as compared to an otherwise unconnected Signal is really just a marker, saying "I intend for this to connect nowhere". Hdl21's port-to-port connection semantics can then override this intent.
I think this should continue to fail.

I agree. Perhaps also create a NoConn that always acts as a single-width, and a NoConns that conveniently expands to connect however many wires as there are to NoConns? There would be ambiguity in some concatenations, but then the user can fallback to the single-width:
:heavy_check_mark:  some_concat = h.Concat(some_sig, h.NoConns(), pwr, gnd, another_bus)
:x: some_concat = h.Concat(some_sig, h.NoConns(), pwr, gnd, h.NoConns()
:heavy_check_mark: some_concat = h.Concat(some_sign, 3 * h.NoConn(), pwr, gnd, h.NoConns())

Agree the Concats are probably the diciest part.
And a very good point - the Signal-multiplication change proposed in #37 would also be a nice play to specify the "width" of NoConns in such concatenations. (Really by just creating several of them.)

I've taken a look at the NoConn problem using the example test:
def test_elab_noconn3():
    """Test bundle-valued noconn"""

    @h.module
    class M2:
        p = h.Diff()

    @h.module
    class M1:
        m = M2()
        m.p = h.NoConn()

    h.elaborate(M1)

    assert len(M1.signals) == 1

The error occurs in PortRefs, with some debugging, I'm noticing that before this ElabPass begins that the Module has an empty Bundle dict. So I'm beginning to think that a Bundle-valued NoConn solution without the rest of the Bundle elaboration plumbing is going to be hacky one.
So, good first step, could be to start by making the Bundles attached to Modules available throughout the elaboration process and then figure out where NoConns feature around that?

The error occurs in PortRefs, with some debugging, I'm noticing that before this ElabPass begins that the Module has an empty Bundle dict.

Not sure I totally follow what you mean here.
Expanding on that example:
import hdl21 as h

@h.module
class M2:
    p = h.Diff()

@h.module
class M1:
    m = M2()
    m.p = h.NoConn()

# Expansion here!
print("M2.bundles:")
print(M2.bundles)
print("M1.bundles:")
print(M1.bundles)

Yields:
M2.bundles:
{'p': BundleInstance(name=p of=Bundle(name=Diff))}
M1.bundles:
{}

Which is right - M2 has a bundle-instance, and M1 does not.
If we do this again after elaborating up to the RESOLVE_PORT_REFS pass, which handles NoConns:
from hdl21.elab.elabpass import ElabPass

h.elaborate(
    M1,
    passes=[
        ElabPass.RUN_GENERATORS,
        ElabPass.ORPHANAGE,
        ElabPass.INSTANCE_BUNDLES,
        ## ElabPass.RESOLVE_PORT_REFS ## This would be next, stop right before it
    ],
)

print("M2.bundles:")
print(M2.bundles)
print("M1.bundles:")
print(M1.bundles)

We get the same thing:
M2.bundles:
{'p': BundleInstance(name=p of=Bundle(name=Diff))}
M1.bundles:
{}

More specifically -
I think the logic to replace a “Bundle-valued NoConn”, such as m.p in that example, would all live in replace_noconn here:
https://github.com/dan-fritchman/Hdl21/blob/09668d735cf692f6deb3de2d1ecd8324ec45db30/hdl21/elab/elaborators/portrefs.py#L260
That would require checking the bundle_ports as well as just ports of the target module mod here:
        # Get the target Module's port-object corresponding to `portref`
        mod = portref.inst._resolved
        port = mod.ports.get(portref.portname, None) ## <- searching `mod.ports` here; also needs to search `bundle_ports`

From there, it looks like the copy_port function knows how to copy Bundle-valued ports. (And if it doesn’t, it’ll need to!)
https://github.com/dan-fritchman/Hdl21/blob/09668d735cf692f6deb3de2d1ecd8324ec45db30/hdl21/elab/elaborators/portrefs.py#L243

Yes, but bundle_ports aren't automatically populated the same way that ports are for modules.

Yes, but bundle_ports aren't automatically populated the same way that ports are for modules.

Sure they are!
Maybe this is a bit of confusion about what makes a Bundle port-visible.
E.g.:
import hdl21 as h

@h.module
class M2a:
    p = h.Diff()

@h.module
class M2b:
    p = h.Diff(port=True)

print(M2a.bundle_ports)
print(M2b.bundle_ports)

Yields:
{}
{'p': BundleInstance(name=p of=Bundle(name=Diff))}

Having port-visibility is an attribute of a BundleInstance. Particularly a boolean-valued one, named port.
This mirrors the difference between the Port and Signal "types" - which is, there really is only one type. All of Port, Input, Output, etc are convenience functions which return Signals, with an appropriate SignalVisibility attribute.
Related: https://github.com/dan-fritchman/Hdl21/issues/39

Should bundle_ports presentation be default (ie. no args required) - given that this is the desired cue that leads to a simple replace_noconn solution?

OK I think we've just been misunderstanding each other a bit here.
6da279e has the changes to enable NoConns to connect to Bundle-valued ports. The "fix" is really all this line:
https://github.com/dan-fritchman/Hdl21/blob/6da279eae510fd598565eb7d956a1f5061683629/hdl21/elab/elaborators/portrefs.py#L265
The rest is testing and the like. If you've got other test cases - let's roll them in!
That change is layered atop some other things I'd done of late on #35, but I think should work stand-alone.

Said change is really only one part of the issue scope here.
Reaching back to the original bullet list:

Should they be allowed to connect non-unity-width ports?

Done. This... already appeared to work actually? This change tests it and succeeds.

Should they be allowed to connect to Bundle valued ports?

Done as of this change

Should they be allowed in Concat?

Intent is "yes", implementation pending

Should they be allowed in AnonymousBundle?

Intent is "yes", implementation pending

Should they be Slice-able?

Intent is "no", and that intent is being met

So of those, there are two "pending":

NoConn in Concat
NoConn in AnonymousBundle

We can make those separate issues, or continue keeping tabs on them here. I'd probably recommend the latter.

authors: ThomasPluck dan-fritchman growly


text:
Confidence

Naive implementation of confidence over 2*sigma pixels. On edges, it will repeat edge values rather than exceed image limits.

Leaving the old method for confidence commented out for now

Does this logic make sense?

I think my formatter kicked in.. sorry

repo: danbider/lightning-pose


text:
Old ownership panel was better

The new ownership panel feels clunkier and less intuitive than the old one. Can we do a bit of design work to re-evaluate it?
attn: @jtomeck

Closed by #942

repo: dandi/dandiarchive


text:
animate css stopped working

Hi, does anyone know why animate css stopped working, at https://daneden.github.io/animate.css/ it also stopped working, I'm using chrome as a browser.

It works fine for me. I am also using Chrome.

Hi, thanks for the answer, the problem was a windows configuration. Now it is working 👍  💯


text:
Nuget packages is working only with serviceStack.Text = 3.9.71

This means we can't use other packages with a later version of serviceStack.

Correct.  This is the last version of ServiceStack.Text with an open source license.  4.x introduced a different license scheme.  I'm open to other suggestions.

See https://servicestack.net/download#free-quotas for more information

Didn't knew that. Sorry!  If ServiceStack.Text is only used for json serialization, move to newtonsoft ?

Or leave it up to the developer to upgrade, but keep the library on 3.9.x.
Currently I need to decide, start messing around with bindings or move to other mailchimp library.  I NEED another package which depends on servicestack (v4).

Would you consider a pull request with a change to NewtonSoft?

Someone is already trying: https://github.com/jphellemons/MailChimp.NET

I've added the Servicestack -> Newtonsoft request to the wishlist page on the wiki.
For the current version of Mailchimp.NET I think we should focus first on have a complete implementation of the Mailchimp API. Then we can start working on version 2 of this library.

@dampee - You're welcome to clone and change over to NewtonSoft in your own repo.  I've tried to isolate much of the code required for that change in the MakeAPICall method.
@SteveVaneeckhout I agree with your sentiment of adding the item to the wishlist and trying to finish up the API client implementation.
Thanks to both of you for getting involved!

authors: SteveVaneeckhout dampee danesparza


text:
Utilizing --verbose flag from bundle

Report
Quick Note:
This less of a bug report and more of a feature request for more output if the --verbose flag is passed to bundler. Danger was working on some of our PRs, but not others, so I assume it might be something in our own configuration. I was hoping to be able to see what the out put to Github would have been so I could maybe identify the UnprocessableEntity it was complaining about.
Either way, thanks! Danger has been a very helpful tool. 👍
What did you do?
Ran bundle exec danger / bundle exec danger --verbose from Travis.
What did you expect to happen?
ℹ Please replace this with what you expected to happen.
Expected it to run danger and report back to the Github PR.
What happened instead?
ℹ Please replace this with of what happened instead.
Received an UnprocessableEntity error from Octokit:
2.56s$ bundle exec danger --verbose
/home/travis/.rvm/gems/ruby-2.3.1/gems/octokit-4.6.2/lib/octokit/response/raise_error.rb:16:in `on_complete': POST https://api.github.com/repos/localmotors/forth/pulls/340/comments: 422 - Validation Failed (Octokit::UnprocessableEntity)
Error summary:
  resource: PullRequestReviewComment
  code: invalid
  field: position // See: https://developer.github.com/v3/pulls/comments/#create-a-comment
	from /home/travis/.rvm/gems/ruby-2.3.1/gems/faraday-0.12.0.1/lib/faraday/response.rb:9:in `block in call'
	from /home/travis/.rvm/gems/ruby-2.3.1/gems/faraday-0.12.0.1/lib/faraday/response.rb:61:in `on_complete'
	from /home/travis/.rvm/gems/ruby-2.3.1/gems/faraday-0.12.0.1/lib/faraday/response.rb:8:in `call'
	from /home/travis/.rvm/gems/ruby-2.3.1/gems/octokit-4.6.2/lib/octokit/middleware/follow_redirects.rb:73:in `perform_with_redirection'
	from /home/travis/.rvm/gems/ruby-2.3.1/gems/octokit-4.6.2/lib/octokit/middleware/follow_redirects.rb:61:in `call'
	from /home/travis/.rvm/gems/ruby-2.3.1/gems/faraday-0.12.0.1/lib/faraday/rack_builder.rb:139:in `build_response'
	from /home/travis/.rvm/gems/ruby-2.3.1/gems/faraday-0.12.0.1/lib/faraday/connection.rb:386:in `run_request'
	from /home/travis/.rvm/gems/ruby-2.3.1/gems/faraday-0.12.0.1/lib/faraday/connection.rb:186:in `post'
	from /home/travis/.rvm/gems/ruby-2.3.1/gems/sawyer-0.8.1/lib/sawyer/agent.rb:94:in `call'
	from /home/travis/.rvm/gems/ruby-2.3.1/gems/octokit-4.6.2/lib/octokit/connection.rb:154:in `request'
	from /home/travis/.rvm/gems/ruby-2.3.1/gems/octokit-4.6.2/lib/octokit/connection.rb:28:in `post'
	from /home/travis/.rvm/gems/ruby-2.3.1/gems/octokit-4.6.2/lib/octokit/client/pull_requests.rb:211:in `create_pull_request_comment'
	from /home/travis/.rvm/gems/ruby-2.3.1/gems/danger-4.3.1/lib/danger/request_sources/github/github.rb:316:in `block in submit_inline_comments_for_kind!'
	from /home/travis/.rvm/gems/ruby-2.3.1/gems/danger-4.3.1/lib/danger/request_sources/github/github.rb:331:in `reject!'
	from /home/travis/.rvm/gems/ruby-2.3.1/gems/danger-4.3.1/lib/danger/request_sources/github/github.rb:331:in `submit_inline_comments_for_kind!'
	from /home/travis/.rvm/gems/ruby-2.3.1/gems/danger-4.3.1/lib/danger/request_sources/github/github.rb:243:in `submit_inline_comments!'
	from /home/travis/.rvm/gems/ruby-2.3.1/gems/danger-4.3.1/lib/danger/request_sources/github/github.rb:153:in `update_pull_request!'
	from /home/travis/.rvm/gems/ruby-2.3.1/gems/danger-4.3.1/lib/danger/danger_core/dangerfile.rb:247:in `post_results'
	from /home/travis/.rvm/gems/ruby-2.3.1/gems/danger-4.3.1/lib/danger/danger_core/dangerfile.rb:277:in `run'
	from /home/travis/.rvm/gems/ruby-2.3.1/gems/danger-4.3.1/lib/danger/danger_core/executor.rb:27:in `run'
	from /home/travis/.rvm/gems/ruby-2.3.1/gems/danger-4.3.1/lib/danger/commands/runner.rb:66:in `run'
	from /home/travis/.rvm/gems/ruby-2.3.1/gems/claide-1.0.1/lib/claide/command.rb:334:in `run'
	from /home/travis/.rvm/gems/ruby-2.3.1/gems/danger-4.3.1/bin/danger:5:in `<top (required)>'
	from /home/travis/.rvm/gems/ruby-2.3.1/bin/danger:23:in `load'
	from /home/travis/.rvm/gems/ruby-2.3.1/bin/danger:23:in `'
	from /home/travis/.rvm/gems/ruby-2.3.1/bin/ruby_executable_hooks:15:in `eval'
	from /home/travis/.rvm/gems/ruby-2.3.1/bin/ruby_executable_hooks:15:in `'
The command "bundle exec danger --verbose" exited with 1.
Done. Your build exited with 1.

Your Environment

Which CI are you running on: Travis
Are you running the latest version of Danger? Yes, 4.3.1
What is your Dangerfile?

require 'open3'

# Add lm-dev link
message "View this on LM-Dev at https://#{github.branch_for_head}.lm-dev.com"

# Check for PR status labels
has_status_label = false
github.pr_labels.each do |label|
  has_status_label = true if label.start_with?('STATUS:')
end
warn "Please use a STATUS label on this PR to reflect its status" if !has_status_label

# Does pull add migrations?
are_migrations_added = false
git.added_files.each { |fn| are_migrations_added = true if fn.include?('/migrations/') }

# Any model changes that don't have migrations?
Open3.popen3('git status --porcelain') do |stdin, stdout, stderr, wait_thr|
  exit_status = wait_thr.value
  unmade_migrations = false
  stdout.readlines.each do |line|
    unmade_migrations = true if line =~ /\?\? .*\/migrations\//
  end

  fail "There are model changes without committed migrations. Run `makemigrations`" if unmade_migrations
end

# package.json updated without yarn.lock?
if git.modified_files.include?('forth/package.json') && !git.modified_files.include?('forth/yarn.lock')
  fail "package.json modified without Yarn lockfile regenerated. Run `yarn`"
end

# Python linter
python_files = (git.added_files + git.modified_files).select{ |file| file.end_with? 'py' }.uniq
python_files.reject! { |file| file.match(/migrations\/\d+_auto_/) != nil }   # Don't lint auto migrations
if !python_files.empty?
  flake8 = "flake8 --ignore=E501,E221,E241 #{python_files.join(' ')}"
  Open3.popen3(flake8) do |stdin, stdout, stderr, wait_thr|
    exit_status = wait_thr.value

    stdout.readlines.each do |line|
      filename, lineno, pos, lint = line.split(':', 4)
      lint.strip!
      if lint =~ /^F\d\d\d /
        fail "(flake8) #{lint}", file: filename, line: lineno
      else
        warn "(flake8) #{lint}", file: filename, line: lineno
      end
    end
  end
end

This sounds like a good idea, I wonder if we can wrap the parts of commenting on an issue with our own error handler that provides more info.

It error caused me too.
I tried to find the cause, but I could not found because of no more information.
I want to be able to see the error detail, and also I want to not fail to the CI job.
I propose the solution, the code will change like below. How about this? @orta
if matching_comments.empty?
- client.create_pull_request_comment(ci_source.repo_slug, ci_source.pull_request_id,
-     body, head_ref, m.file, position)
+ begin
+   client.create_pull_request_comment(ci_source.repo_slug, ci_source.pull_request_id,
+       body, head_ref, m.file, position)
+ rescue Octokit::UnprocessableEntity => e
+   // TODO show some error detail. ex. body, file, head_ref, and position
+   // sorry I don't know how to ouput logs in Danger project...
+
+   next false // next false(=not reject) because this comment has not completed
+ end
else
  # Remove the surviving comment so we don't strike it out

That does sound good - I think in Danger we just use puts ( or maybe Cork ) - that is fine. Yeah, this seems like a good idea to me @litmon 👍

Thanks😄 I will make the Pull Request.

authors: Tristan-zimmerman litmon orta

repo: danger/danger


text:
GitHub API dataCorrupted error

Trying to get the comments on a PR.
Code:
let group = DispatchGroup()
group.enter()
_ = danger.github.api.issueComments(
    owner: "foo",
    repository: "bar",
    number: danger.github.issue.number) { (response: Response<[Comment]>) in
    switch response {
    case .success(let comments):
            // do stuff
    case .failure(let error):
            print("[ERROR]: ", error)
    }
    group.leave()
)
group.wait()

Issues:

I needed to add the DispatchGroup logic otherwise it seemed to end before getting the response back from the Octokit
I get: [ERROR]: dataCorrupted(Swift.DecodingError.Context(codingPath: [], debugDescription: "The given data was not valid JSON.", underlyingError: Optional(Error Domain=NSCocoaErrorDomain Code=3840 "Invalid value around character 1." UserInfo={NSDebugDescription=Invalid value around character 1.})))

Not really sure how to even debug. Any idea why this is happening/how to fix?

The issue comment function comes from https://github.com/nerdishbynature/octokit.swift so that is probably a good starting point.
The dependency was recently updated https://github.com/danger/swift/pull/417, but to doesn't seem that this change is related to the issue.

authors: Huddie f-meloni

repo: danger/swift