Why do you have to train Cifar10 two times?

Notice: The code should be find in cifar10_test.py in line around 190.
In file cifar10_test.py you use code
if TRAIN_SMALLER_MODEL:
        for _ in range(2):

to train the model twice.
But as I can see, the first get a higher performance for small model 0, with no quantization or distill.
smallerModelSpec0 = {'spec_conv_layers': [(75, 5, 5), (50, 5, 5), (50, 5, 5), (25, 5, 5)],
                    'spec_max_pooling': [(1, 2, 2), (3, 2, 2)],
                    'spec_dropout_rates': [(1, 0.2), (3, 0.3), (4, 0.4)],
                    'spec_linear': [500], 'width': 32, 'height': 32}

So Why?

Hi,
I believe this was just a residue of some experiments we were running which I forgot to clean up. There is no particular reason to train it twice.


Add parent post to related

Would be super handy. How often do you need to know parent post name etc...

Like this:
/**
 *  Serialize page parent
 *
 * @param array $input The post currently being processed by Rest-Easy
 */
    function add_page_parent($related){
        $target = get_post($related['id']);
        $parent = get_post($target->post_parent);

        $related['parent'] = apply_filters('rez_serialize_object', $parent);

        return $related;
    }
    add_filter('rez_gather_related', 'add_page_parent');

@drewbaker Definitely useful! I'm going to close this and move this to Rest-Easy, that's something we should have on the plugin from the start.

Added here


Fails to rename dead symlink movie

Version: 2.9.14-SNAPSHOT_1270b65_linux
Build: 2018-10-18 18:56
OS: Debian Stretch, Linux 4.9.0-8-amd64
JDK: openjdk version "1.8.0_181"
What is the actual behaviour?
The dead symlinks is not renamed but a new nfo file is created.
ls -lR /tmp/dead_symlinks
/tmp/dead_symlinks:
total 4
drwxr-xr-x 1 nxxxse nxxxse 82 Oct 21 21:39 Star Trek - The Motion Picture (1979)
lrwxrwxrwx 1 nxxxse nxxxse  4 Oct 21 21:27 Star Trek - The Motion Picture (1979).mkv -> dead

/tmp/dead_symlinks/Star Trek - The Motion Picture (1979):
total 8
-rw-r--r-- 1 nxxxse nxxxse 5810 Oct 21 21:39 Star Trek - The Motion Picture (1979).nfo

What is the expected behaviour?
Rename/move the dead symlink to 'Star Trek - The Motion Picture (1979)/Star Trek - The Motion Picture (1979).mkv'. In case of a relative symlink, it does not matter if this move breaks the symlink.
Steps to reproduce:

Prepare test movie source:
# In a GNU/Linux shell
mkdir /tmp/dead_symlinks && cd /tmp/dead_symlinks
ln -s dead 'Star Trek - The Motion Picture (1979).mkv'

Point tmm to the test source.

Update source and scrape.

Run "Rename/Cleanup selected movie(s)"

Additional
Have you attached the Logfile from the day it happened?

Failed to rename: Source '/tmp/dead_symlinks/Star Trek - The Motion Picture (1979).mkv' does not exist

Context
git-annex uses (dead) symlinks versioned in git for file management and syncing. This allows to have a full index of a big movie library on every device and make changes to the file names which get later synced. Thus it would come in handy if tmm would allow to rename dead symlinks. Access to movie/file content is not required for my use case. I expect that tmm checks if the source file exists before trying to rename it.

Nice approach you have; never heard of that ^^
Looks interesting.
Tried to replicate your setup on my NAS (shared via samba), but this does not work here.
No links are shared (for a good reason), so this only applies to linux clients directly.
Nevertheless, our "move" file method does always an "exists" check (as you already expected)
I've changed that to additionally check for symlinks and ignore the (non)existence (of the target).
So it should move the symlink 1:1 into that directory / rename it, without altering it.
Unfortunately, i cannot test this.
Would be cool, if you clould test latest nightly build and report back :)


feat: gleam

Not working as of now
Built live with gemini (preview: Interactive Chat) in IDX with @kirupa and @cpsloal

Thank you @Malix-Labs! Do you have a personal fork URL to test?

Nope, but I probably won't know how to fix it myself for now


New pull request template

Pull request information

Status: Ready to merge
Kind of changes: Better Github workflow
Code affected: None
Related PR or issue: None

Description

A new pull request template that will be active for all futures PRs.

Pull Request Test Coverage Report for Build 3366

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 89.319%

Totals

Change from base Build 3352:
0.0%

Covered Lines:
8011

Relevant Lines:
8969

💛  - Coveralls

@nathanlct I really love this! One question (just as a discussion point), how to we deal with the todo's? Are they meant to resolve them before we can merge it or is it a matter of creating an issue about it and leaving it for a later date?

@AboudyKreidieh Thanks! Imo the todos should only be used when the status of the PR is still in development, and further suggestions or issues should be opened as issues.
However now that I think of it, we're not really supposed to have In development PRs since the development should be done in a branch until all tests pass, and then a Ready to merge PR should be created (then Todos would directly be the reviewers comments and PRs would be in development only when fixing stuff mentioned in reviews, lmk if you agree). I actually added the Todos/In development thing because of the - do not merge PRs, so are these justified or could they stay in a branch during development until they are ready to be merged?
As a side note, it would be nice to remove the inactive PRs from 2018 to have a cleaner view of what needs to be reviewed (then maybe assign people to review the current PRs).

All sounds good. So we can use these then as a means of determining what still needs to be done before a PR can be merged. LGTM then


main to alpha

:tada: This PR is included in version 1.7.1 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Fix outdated link in 0395-observability.md

The link about attached macros was outdated and has been corrected.

Thanks!


Remove unnecessary length check in LengthPatternFilter

What the title says

Codecov Report

Merging #81 into master will decrease coverage by 0.02%.
The diff coverage is n/a.

@@             Coverage Diff              @@
##             master      #81      +/-   ##
============================================
- Coverage     86.29%   86.26%   -0.03%
+ Complexity      235      233       -2
============================================
  Files            21       21
  Lines           518      517       -1
  Branches        111      110       -1
============================================
- Hits            447      446       -1
  Misses           24       24
  Partials         47       47

Impacted Files
Coverage Δ
Complexity Δ

...chaapi/patternfilter/jimple/LengthPatternFilter.kt
100% <ø> (ø)
3 <0> (-2)
:arrow_down:

Continue to review full report at Codecov.

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


Component consolidation between Builder and DeepInsights

As we are thinking about merging Builder and DeepInsights into the same codebase, there is some room for improvements here related to components, like component consolidation.
As of now, we have detected two main differences between components in Builder and DI:

Tipsy Tooltips (https://github.com/CartoDB/cartodb/issues/13194)
Dropdown Overlay (https://github.com/CartoDB/cartodb/issues/13132)

Not available in DI widgets yet
Check if we can use ContextMenuView in ColorPicker

Please feel free to add anything else to this list if needed.

awesome! thanks @jesusbotella


HTTPS proxy support

Description
Hi, I tried using the client with a proxy by using the proxy parameter in the client, and it worked with an HTTP proxy, but with an HTTPS proxy I get this error:
Only http proxies are supported
Is it supposed to be supported (both in the web and RTM clients)?
What type of issue is this? (place an x in one of the [ ])

[ ] bug
[ ] enhancement (feature request)
[x] question
[ ] documentation related
[ ] testing related
[ ] discussion

Requirements (place an x in each of the [ ])

[X] I've read and understood the Contributing guidelines and have done my best effort to follow them.
[X] I've read and agree to the Code of Conduct.
[X] I've searched for any related issues and avoided creating a duplicate issue.

Hi @liorblob and @Allexio-bot, this error comes from AIOHTTP our client dependency. (Specifically this line of code)
This thread may shed some light on this: https://github.com/aio-libs/aiohttp/issues/2722#issuecomment-453963275

Thanks.


Hiding chunks mechanisms

The ability to prevent players from seeing chunks would be a really cool addition, similarly to the entity hiding mechanisms. If possible to use in the same way:
ChunkTag.hide_from_players
ChunkTag.show_to_players
PlayerTag.hide_chunk
PlayerTag.show_chunk

You can technically do this with the player receives packet event now


Bring in the API utilities from pkg/apis/serving/v1alpha1 used for …

…validation and defaulting in the webhook.
Fixes: https://github.com/knative/pkg/issues/12

/lgtm

/retest


[Bug] consumer listener does not respect receiver queue size

Search before asking

[X] I searched in the issues and found nothing similar.

Version
Pulsar Version: 2.11.0
Pulsar C++ Client Version: 3.1.0 (This is version used by Nodejs 1.8.0 but I do see newer C++ version 3.1.1 available)
Pulsar Nodejs Client Version: 1.8.0
We are using Pulsar Nodejs Client that depends on Pulsar C++ client version (details above)

When using Consumers with Listener approach, setting "ReceiverQueueSize" is not honored by Consumer
Receiver Queue Size works when using Receive approach with Consumer

This issue already addressed in Pulsar Java Client:

We tested using Java Client and noticed that both Listener and Receive honor ReceiverMessageQueue
Reference of this fix in Java Client: https://github.com/apache/pulsar/issues/11008
Related PR: https://github.com/apache/pulsar/pull/11455

Minimal reproduce step

Use Shared subscription that has two below consumers:
Start 1st  Consumer with listener callback approach
Start 2nd Consumer with Receive option to receive messages
Set ReceiverQueueSize for both consumers to: 50
Send 1000 messages to topic that Shared Subscription above is subscribed to

For this test Implement Message processing function as below and call the same from both Listener callback and Receive:
ReceiveMessages(msg: any, consumer: any) {
await delay(500); // 500 ms delay
}
Its same method used by Listener Consumer or Receive Consumer.
What did you expect to see?

Listener Consumer: You will notice that almost all 1000 or at least more than 900 messages go to Listener
Receive Consumer: Consumer will pick up at most nothing to < 50
Anything else?
In C++ implementation, it looks like listener callbacks are posted as messages are processed from queue using Boost Async IO library. Once caller posts all messages, new messages are retrieved.
If any receive callback does CPU intensive work, there is delay imposed but if we are doing async/await option in NodeJS - example: waiting for DB call to complete, caller assumes we are done processing with all messages in Receiver Queue and request more. This will look like very fast consumer to broker and all messages are pushed, and Listener Consumer will end up taking up a lot before actually getting any finished.
Due to this 2nd Consumer with Receive approach barely get any messages.
This issue is well document and addressed in Pulsar Java Client already but similar fix did not make it C++ client?
https://github.com/apache/pulsar/issues/11008
Is this to be considered as behavior by design for C++ client OR this needs to be flagged as bug and needs fix?
Any thoughts, feedback and responses are appreciated.
Thanks again for your help
Are you willing to submit a PR?

[ ] I'm willing to submit a PR!

Actually, it's a bug from the nodejs client. I will push a PR to fix it.

Thank you very much @RobertIndie


8322 update help content for R32 - update contract periods

New PR to be opened on project branch.


HDDS-4741. Modularize upgrade test

What changes were proposed in this pull request?
As of now, upgrade acceptance test verifies upgrade from Ozone 0.5.0 to "current", ie. the commit being built.  It has an OZONE_UPGRADE_TO variable, but its value is not really relevant to which version is run after the "upgrade".
This PR introduces the following changes:

Test upgrade from multiple earlier versions, eg. from 0.5.0 or 1.0.0.
Extract parts of the upgrade test script to two libraries (the existing main lib and an upgrade-specific one).
Split upgrade test script:

upgrade_to_current: test upgrade from a release to the current binaries,
upgrade_to_release: test upgrade from one release to a later one.

Improve the scripts which define version-specific behavior: instead of just declaring variables, define functions to activate/deactivate behavior of a specific version.
Introduce "logical version" to be able to upgrade across multiple versions (eg. from 0.5.0 to 1.1.0).

https://issues.apache.org/jira/browse/HDDS-4741
How was this patch tested?
Regular CI now runs upgrade_to_current.sh from both 0.5.0 and 1.0.0:
https://github.com/adoroszlai/hadoop-ozone/runs/1912441301
Also tested upgrade_to_release.sh manually.

cc @errose28 for review.

Also it looks like there is an extra robot log and report getting placed in the upgrade directory (outside the results folder). Looks like log and report for 0.5.0 first gets put there, and then log and report for 1.0.0 overwrites it. Is this supposed to happen?

Thanks for pointing this out.  It turns out not specific to the upgrade test or this change.  It happens for each "subtest" on master, too.  Example (from here):
Log:     /mnt/ozone/hadoop-ozone/dist/target/ozone-1.1.0-SNAPSHOT/compose/compatibility/result/log.html
Report:  /mnt/ozone/hadoop-ozone/dist/target/ozone-1.1.0-SNAPSHOT/compose/compatibility/result/report.html
Output:  /mnt/ozone/hadoop-ozone/dist/target/ozone-1.1.0-SNAPSHOT/compose/result/compatibility.xml
Log:     /mnt/ozone/hadoop-ozone/dist/target/ozone-1.1.0-SNAPSHOT/compose/log.html
Report:  /mnt/ozone/hadoop-ozone/dist/target/ozone-1.1.0-SNAPSHOT/compose/report.html

(The second log and report are the ones created in the same way as you described.)
Since the fix is pretty simple, I incuded it here, instead of creating a separate issue.

Thanks for working on this @adoroszlai. Changes LGTM +1.

@avijayanhwx @elek @fapifta can you please review?  @errose28 is OK with it and would like to work on top of it in the upgrade branch.

Thanks for the patch @adoroszlai, and the reviews @errose28 & @elek. I am merging this.


Fix a formatError exception when parsing some Linux traces.

This was caused by a trace with an empty process name.   Fixed to be resilient to that.
Also made the code clearer while I was in there.

Codecov Report

Merging #890 into master will decrease coverage by <.01%.
The diff coverage is 33.33%.

@@            Coverage Diff             @@
##           master     #890      +/-   ##
==========================================
- Coverage   17.48%   17.47%   -0.01%
==========================================
  Files         228      228
  Lines      139263   139271       +8
  Branches    12334    12336       +2
==========================================
- Hits        24353    24341      -12
- Misses     113967   113985      +18
- Partials      943      945       +2

Flag
Coverage Δ

#2017
17.47% <33.33%> (-0.01%)
:arrow_down:

#Debug
17.47% <33.33%> (-0.01%)
:arrow_down:

Impacted Files
Coverage Δ

...w/OtherSources/Linux/LinuxPerfScriptEventParser.cs
75.85% <33.33%> (-1.17%)
:arrow_down:

src/PerfView/Utilities/FastStream.cs
45.85% <0%> (-2.54%)
:arrow_down:

Continue to review full report at Codecov.

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


Query String / Hash Support

Does universal-router plan to support query strings and hashes? From my tests, it appears that these are not currently supported.
For example:
myapp/test?foo=1&bar=5#hash

Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

Parsing hashes would work only on the client-side (in the browser). Are you using Universal Router in an isomorphic (universal) app or regular SPA?

The short answer is SPA.
I'm actually evaluating it to potentially propose to the author of a Vue mobile web UI framework. It currently has its own router implementation designed primarily for SPAs, but with a router implementation that worked on the server, it could potentially support server rendering as well. The router implementation supports query strings and hashes, so I was curious about support for these features in universal-router.

@bencompton in the current version of the router, there is just a single UniversalRouter.resolve(routes, context) method. The second parameter can be customized to pass a query/hash strings as objects, for example:
import Router from 'universal-router';
import qs from 'query-string';
import routes from './routes';

Router.resolve(routes, {
  path: window.location.pathname,
  query: qs.parse(window.location.search),
  hash: qs.parse(window.location.hash),
}).then(render);

All this info is passed down to route handler functions, e.g.:
// some-route.js
export default {
  path: '/some-route',
  action({ query, hash }) {
    console.log(query, hash);
    return ...;
  }
}

Do you think this will work for your use case, or you have a better idea how to support hashes?

@koistya thanks for the quick response! The current router accepts a string like /user/45/posts/28/?sort=first#opened and parses it. universal-router would be wrapped with the API of the current router implementation anyways, so it could certainly pre-parse the strings to separate the path from "other stuff" before passing it all onto universal-router for resolution.
So, universal-router should be perfectly usable as-is for this use case. In an ideal world, though, universal-router might support more generic syntax like this:
// some-route.js
export default {
  path: '/user/:userId/posts/:postId/?sort=:sortBy#:hash',
  action({ userId, postId, sortBy, hash }) {
    ...
    return ...;
  }
}

``

import Router from 'universal-router';
import queryString from 'query-string';
import routes from './routes';

// location = '/user/45/posts/28/?sort=first#opened'
Router.resolve(routes, {
  path: location.pathname,
  query: queryString.parse(location.search),
  hash: location.hash,
}).then(render);

const route = {
  path: '/user/:userId/posts/:postId',
  action({ path, params: { userId, postId }, query: { sort }, hash }) {
    console.log(path);   // => '/user/45/posts/28/?sort=first#opened'
    console.log(userId); // => '45'
    console.log(postId); // => '28'
    console.log(sort);   // => 'first'
    console.log(hash);   // => '#opened'
    return /*...*/;
  }
}

Playground: https://jsfiddle.net/frenzzy/1gk5mh1d/

@frenzzy, using the URL object looks like a really simple way to pre-parse a URL string and querystring is a nice, small library. That's perfect--thanks!


Feature request: command line option to print the version & build info

Ability to execute DiscImageCreator with something like --version where it simply prints out the version, build information, and potentially the git commit identifier (and does not beep).
Also, if I execute DiscImageCreator.exe with just /q and no other arguments, it prints "Invalid argument" and it still beeps even though I provided the /q argument that is supposed to disable beep.

That prints several pages of Usage info after printing the AppVersion & AnsiBuild, can there be a command line argument to only print the AppVersion & AnsiBuild?

DiscImageCreator_test.zip

added: /v for printing only version

DiscImageCreator.exe /v


Patch updates

About this PR
Updates:

📦 org.scalatest:scalatest from 3.2.17 to 3.2.18

📜 GitHub Release Notes - Version Diff

Usage
✅ Please merge!
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

⚙ Adjust future updates
Add these to your .scala-steward.conf file to ignore future updates of these dependencies:
updates.ignore = [
  { groupId = "org.scalatest", artifactId = "scalatest" }
]

Or, add these to slow down future updates of these dependencies:
dependencyOverrides = [
  {
    pullRequests = { frequency = "30 days" },
    dependency = { groupId = "org.scalatest", artifactId = "scalatest" }
  }
]

labels: library-update, early-semver-patch, semver-spec-patch, commit-count:1

Can't upgrade currently because bad combination with selenium version used, see

https://repo1.maven.org/maven2/org/scalatestplus/selenium-4-12_2.13/ (only published for scalatest <IP_ADDRESS>).
Next available version https://repo1.maven.org/maven2/org/scalatestplus/selenium-4-17_2.13/, however selenium 4.17 does not work for us currently, see

https://github.com/FluentLenium/FluentLenium/issues/1399#issuecomment-1866234405
https://github.com/playframework/playframework/pull/12371#issuecomment-1970655278

[error] (scalatestplus-play / update) sbt.librarymanagement.ResolveException: Error downloading org.scalatestplus:selenium-4-12_2.13:<IP_ADDRESS>
...
[error]   not found: https://repo1.maven.org/maven2/org/scalatestplus/selenium-4-12_2.13/<IP_ADDRESS>/selenium-4-12_2.13-<IP_ADDRESS>.pom
...
[error] Total time: 4 s, completed Apr 28, 2024, 8:07:08 AM


🐛 fix(i18n): fix arrows in RTL languages

Fix https://github.com/welpo/tabi/issues/271

Thank you!
I've added an EOL and a couple of non-breaking spaces so the arrows are not too close to the text (consistent with LTR languages).


Visualization Qesition

hello, I would like to ask, what method did you use to visualize the result in the end?
Do you mind sharing the source code of the visualization? thank you a lot
Looking forward to your reply

Hi, I think you should ask the question on the official repo of the paper. This is not an official implementation and I am not affiliated with the authors.
Cheers

ok, any way, thank you for your reply


Update Select to 0.41.0

Since Select added the new enhanced look, we have frozen select at v0.40.1 until we have time to update.

https://github.com/material-components/material-components-web-react/issues/213 should be fixed with this as well.

duplicated of #242


entries datastruct

now, the datadtruct is slice, in run function, always sort, why not use heap or wheel,

hi, author, i implement cron with heap, and commit a PR, but not pass TestJob function, but it is not a bug, beacues the heap is dynamically adjusted, so failed to TestJob.

I don't believe that the extra complexity is necessary. It's hard to imagine a system with so many scheduled tasks that sorting them takes a measurable amount of time. Tasks can not be activated more often than once a second at the most, so I don't see any reason to optimize this case. Thanks for your interest


Add animations where possible

Background and context
The app is quite static and transitions abruptly from screen to screen. Some animations would help it make it more fluid and feel more polished.
This is a tracking issue for a very far into the future feature, which will not be started any time soon.
Describe the solution you'd like

[ ] Make the background spheres move around (maybe change their gradient as time goes on)
[ ] Make the spheres animate when they change position from screen to screen.
[ ] Figure out some arcane magic to make the player select animated somehow.
[ ] Come up with other ideas.

Work was started in #166 - spheres now rotate slowly.


Using Visual Studio Code wth WSLackware

The normal import methods for using Visual Studio Code with a distribution on WSL do not seem to work. I followed the site's directions for doing so, by entering at the root prompt, "code ." and without the quotes, and instead I am getting a complaint that the command is unknown to the distribution. Is this because I've installed the VHD to a location that's not the usual one, whatever that is, for a location for WSL to work? And how can we fix this.

Did you use Package installation method? I believe if you use that you won't have any problems running the distro and integrating it with other tools.
Allonzy!

VScode on windows is absolutely fine with importing from WSL directories!
By any chance, are you running #code and expect it to work? Am I getting it wrong!? I hope so.
If you're doing so, you're in absolute wrong way!!
1- it's not installed by default
2- I have plan to deploy X dir for WSLg on WSLackware but I wanna avoid make binary heavy to at same time.
You can also ask in my server if you have further questions since I mostly use git and not github interface itself.

@DoctorWho8 VSCode on windows is absolutely fine with importing from WSL directories!
By any chance, are you running #code and expect it to work? Am I getting it wrong!? I hope so.
If you're doing so, you're in absolute wrong way!!
1- it's not installed by default
2- I have plan to deploy X dir for WSLg on WSLackware but I wanna avoid make binary heavy to at same time.
You can also ask in my server if you have further questions since I mostly use git and not github interface itself.

@DoctorWho8 VSCode on windows is absolutely fine with importing from WSL directories!
By any chance, are you running #code and expect it to work? Am I getting it wrong!? I hope so.
If you're doing so, you're in absolute wrong way!!
1- it's not installed by default.
2- I have plan to deploy X dir for WSLg on WSLackware but I wanna avoid making binary heavy too at same time.
You can also ask in my server if you have further questions.


Buffer ub

Issue #, if available:
Description of changes:
fix buffer null arithmetic ub
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Codecov Report
Patch coverage: 100.00% and no project coverage change.

Comparison is base (f9adeff) 80.47% compared to head (cf56d19) 80.47%.

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #999   +/-   ##
=======================================
  Coverage   80.47%   80.47%
=======================================
  Files          52       52
  Lines        5470     5470
=======================================
  Hits         4402     4402
  Misses       1068     1068

Impacted Files
Coverage Δ

source/byte_buf.c
87.63% <100.00%> (ø)

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


Hotfix/rebase off master

What are your changes?
What is the urgency level of this change?

[ ] Blocker
[ ] High
[ ] Medium

I have completed these items:

[ ] I have built locally and tested for broken links and formatting.
[ ] If appropriate, I have added redirects.

If you included a comment with your commit, it appears here:

retest this please

This does not need to be done. The opposite was done instead (develop -> master). See https://github.com/dcos/dcos-website/pull/941


npm not installing jest resulting in npm test failing

My team's project in VSO is using the NPM vsts-task and it handles most dependencies with no issue.
We recently started working with jest as a testing framework and have included its dependencies in our package.json (and thus package-lock.json) files. Our package.json script was updated so that "test" : "jest" and will trigger jest off of command line: "npm test"
When building on our local dev machine, we can type npm test from the command line and it runs jest with no issues.
When I inject the same custom command into the npm task, it attempts to run jest but returns an error:
2017-08-29T23:09:21.3646344Z [command]C:\Program Files\nodejs\npm.cmd run test
2017-08-29T23:09:22.5258012Z
2017-08-29T23:09:22.5258012Z ><EMAIL_ADDRESS>test d:\a\1\s\*******
2017-08-29T23:09:22.5258012Z > jest
2017-08-29T23:09:22.5258012Z
2017-08-29T23:09:22.5388025Z 'jest' is not recognized as an internal or external command,
2017-08-29T23:09:22.5388025Z operable program or batch file.
2017-08-29T23:09:22.5587825Z npm ERR! code ELIFECYCLE
2017-08-29T23:09:22.5587825Z npm ERR! errno 1
2017-08-29T23:09:22.5587825Z npm ERR<EMAIL_ADDRESS>test: `jest`
2017-08-29T23:09:22.5587825Z npm ERR! Exit status 1
2017-08-29T23:09:22.5597810Z npm ERR!
2017-08-29T23:09:22.5597810Z npm ERR! Failed at the<EMAIL_ADDRESS>test script.
2017-08-29T23:09:22.5597810Z npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
2017-08-29T23:09:22.5597810Z npm WARN Local package.json exists, but node_modules missing, did you mean to install?
2017-08-29T23:09:22.5597810Z
2017-08-29T23:09:22.5597810Z npm ERR! A complete log of this run can be found in:
2017-08-29T23:09:22.5597810Z npm ERR!     C:\NPM\Cache\_logs\2017-08-29T23_09_22_544Z-debug.log
2017-08-29T23:09:22.5767818Z ##[error]npm failed with error: C:\Program Files\nodejs\npm.cmd failed with return code: 1
2017-08-29T23:09:22.5777832Z ##[section]Finishing: npm run (test)

The warning unhelpfully suggests that node_modules is missing but npm install was already run earlier.
Additionally, to help with debugging I added another custom npm task for "npm list jest" and it returned the following:
2017-08-30T00:52:12.0598767Z [command]C:\Program Files\nodejs\npm.cmd list jest
2017-08-30T00:52:15.1108825Z<EMAIL_ADDRESS>d:\a\1\s\*******
2017-08-30T00:52:15.1108825Z `-- UNMET DEPENDENCY<EMAIL_ADDRESS>2017-08-30T00:52:15.1108825Z
2017-08-30T00:52:15.1128578Z npm ERR! missing<EMAIL_ADDRESS>required by<EMAIL_ADDRESS>
Is there a limitation that prevents npm from installing jest or is there something else about the npm task that is causing this issue?

I have a couple of suggestions:

Are you certain that npm install is occurring in the same directory as the task which runs "npm run test"?  Validate this by inspecting the "Working folder with package.json" and by inserting a shell task between "npm install" and "npm run test" that does a "dir".  You should see node_modules

I'm not sure how you're calling 'jest' from your npm run script; however, if it isn't installed globally you may need to add a path (".\node_modules.bin\jest"

Have your "test" command do a "dir" and a "pwd" to see where it thinks it is running from.  Correlate, that with 1.

It appears my npm run test was in fact not in the correct directory. Once I fixed that, it was able to locate and run jest just fine.
Thanks for encouraging me to double check my directory variables. I hadn't noticed they were more complex within this team environment than I expected.


Bundle .env and .env.<stage> with function assets.

I'd like to have a way of loading environment variables from my functions. Simple things like setting a LOG_LEVEL variable without having to go through sst.config.ts via the environment option.
Simply including .env and .env.<stage> to the function's final bundle would enable me to use dotenv to load them.
Related: During discussions in #507 a point was brought up that the current behaviour is incompatible with Nextjs documented behaviour: https://github.com/sst/ion/issues/507#issuecomment-2241047646
As a side note, the behaviour of sst.config.ts file giving .env precedence over .env.<stage> is counter intuitive. This is again contrary to Nextjs behaviour, which I think is more reasonable.

Just to add some details of how I personally think this should work.
.env.* files that should be supported
.env                     # loaded in all cases
.env.local               # loaded in all cases, ignored by git
.env.<stage>             # only loaded in specified stage
.env.<stage>.local       # only loaded in specified stage, ignored by git

Where to look for .env.* files
I believe sst should look for .env.* files next to the closest package.json file. This would be the workspace root in a monorepo.
For example:
.
├── package.json
├── .env  // <- Loaded by the sst.config.ts script only, not bundled with the handler
├── sst.config.ts
└── function
    ├── package.json
    ├── .env  // <- Should be bundled
    └── src
        ├── .env  // <-- Ignored
        └── handler.ts

bundling env files into the deployment isn't something we're likely going to do. we have sst.Secret which is a entire system for managing these values without juggling env files with your team and through CIif they're non-secret values you can put them in your sst.config.ts or in another ts file that you import or you can drill that through a .env you load yourself if you really want to use themalso you can use copyFiles https://sst.dev/docs/component/aws/function/#copyfiles to put whatever stuff you want in the final bundleour system giving .env precedence over .env. is probably wrong - we should look into that

I can just use copyFiles in all my functions, no problem. But I would ask to reconsider adding this to the Nextjs construct at least. This is how people would usually expect a nextjs deployment to work. I spent quite a bit of time trying to figure this out. The only thing I could find talking about this is the issue that I linked. And that discussion is super confusing, the current behaviour is really not clear, even in the docs it can be kind of ambiguous. I read the docs and had hard time figuring out that the .env files are only applied to the sst.config.ts file, not the constructs themselves, but maybe that's my fault.

Added a new doc on this https://sst.dev/docs/environment-variables


Duskweave 2 and 3 have the wrong ID

I saw the Duskweave 2 was not in Cloth category and found out the following items had the wrong ID.
https://github.com/N6REJ/BetterBags_Bears_Ultimate/blob/54f4b2efe3753c880996ca746b61d10833343b3b/Databases/TWW/TWW_Tailoring.lua#L61
Should be changed to -> Duskweave 2: 228233
https://github.com/N6REJ/BetterBags_Bears_Ultimate/blob/54f4b2efe3753c880996ca746b61d10833343b3b/Databases/TWW/TWW_Tailoring.lua#L62
Should be changed to -> Duskweave 3: 228234

https://github.com/N6REJ/BetterBags_Bears_Ultimate/pull/7 fixed this.


bash: ./bbb-mp4-bulk-parallel-input-file.sh: No such file or directory

root@live:~/bbb-mp4# ./bbb-mp4-bulk-parallel-input-file.sh
bash: ./bbb-mp4-bulk-parallel-input-file.sh: No such file or directory

Above script expects list of recordings that you want to convert into MP4. Looks like you have not created such a file.
You may want to use the simpler version: node bbb-mp4.js
Above will convert the given recording into MP4.

Above script expects list of recordings that you want to convert into MP4. Looks like you have not created such a file.
You may want to use the simpler version: node bbb-mp4.js
Above will convert the given recording into MP4.


Add type-alias feature to make it more of a drop in replacement for std Hash[Set|Map]

Should fix https://github.com/tkaitchuck/aHash/issues/103
Adds a new feature which is mutually exclusive to the default "std" feature which adds a type-alias instead of a new type for the AHashMap and AHashSet types. This makes it possible to use AHashMap::with_capacity_and_hasher(123, Default::default()) and pass it to
fn foo<K, V, S>(map: &HashMap<K, V, S>);

The only issue I see with this is how to handle precedence. Cargo doesn't handle mutually exclusive features well. So if for example an application adds an unrelated dependency it could in turn depend on aHash with the default-on std feature. Cargo would then unify the two dependencies and compile aHash with both features. (This would introduce an error.)
One alternative would be to have one feature take precedence over the other. However regardless of which took precedence this could cause a compile error for an application which was written to one or the other.
It might be better to allow both to exist at the same time, for example by naming the alias something different from the struct. (Or perhaps differentiating by path.) For example we could have ahash::HashMap and ahash::AHashMap. This would avoid any conflict at the cost of some confusion for users as to which one to use.

Good point, I can change it to the ahash::Hashmap and see if I can update some docs as well

Please add annotations to allow tests to pass with no-std.

Fixed!

@tkaitchuck looks like the nightly failures are unrelated to my changes?


Update Battle2json.cs - fix reading from wrong JToken

Fix error message being read from the wrong JToken when the json file has error.

Hi, I am just going to merge this without checking it - I have no available time these days and I have trust in you. :-)


Unable to create job if "Estimated time" is too big

Describe the bug
When create a job, if the amount of "Estimated time" is too big,
To Reproduce
Steps to reproduce the behavior:

Login as Client
Create a job
In the "Estimated Time" input, put a super large number, like<PHONE_NUMBER>9999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999. Since the input does not validate the amount, we can still submit this job

Expected behavior
It should have a maximum duration, like it cannot larger than 1 year.
Screenshots

kudos to https://github.com/CQBinh for reported this bug

Resolved in commit https://github.com/bigbomio/bigbom-marketplace/commit/d9e2fd2803c8e29fe715f7b219e646033b0fc0c0


Enable graphite-webapp to read local_settings.py to get its configuration

In 'chef vault mysql graphite password', the permissions on /opt/graphite/webapp/graphite/local_settings.py were changed from 00644 to 00640. This was done so only the owner of the file can read the config and protect the graphite-mysql password from general browsing. The file was owned by root:root. Graphite webapp is run as user www-data which reads the local_settings.py file to get its configuration, which after this commit it couldn't do.
This PR makes www-data owner of /opt/graphite/webapp/graphite/local_settings.py; group is still root and changes permissions to 00440 so only root can change the file. This fixes issue #303

Looks as I'd expect

LGTM.


[FX] Update README.md

Update readme.md to add some FX contents.

Looks like rebase does not help. The bot is flaky.


Database Migrations - How does it work?

Will the db:migrate runs on all the instances?
Is there a way to specify migrations to run only on one instance than on all the instances?

That's really a question to be answered by the aws documentation, but look for 'lead' instance,  I think that option is what you are looking for.

Found the related bit in the sample
  03-rake.config:
    container_commands:
      01seed:
        command: rake db:seed
        leader_only: true

Thank you Kevin.


Load scrape configs from multiple files

This issue is about providing the ability to split Prometheus scrape configs into multiple files.
Design doc: https://docs.google.com/document/d/1bSehbL_Rzx9_guVgISmara-Ft_FB57q_YxEZtwxE3C8/edit#heading=h.bupciudrwmna
Add a new parameter scrape_config_files: [ - <filepath_glob> ... ].
The files in the scrape_config_files are read, and may contain one or multiple files. The filenames can contain globs (scrape_configs.d/*.yml). Relative paths are relative to the main config file.
The files are re-read on every reload. Wrong scrape configs make the reload fail, and scrape configs as applied before apply. Errors reading scrape configs prevent Prometheus to start.
Scrape config names must be unique between prometheus.yml and imported files, otherwise reload/start fail.
Scrape configs are never merged together.
Exemple scrape config file:
Prometheus.yml
global:
   scrape_interval: 10s
scrape_configs:
  - job_name: 'prometheus'
    static_configs:
    - targets: ['localhost:9090']
scrape_config_files:
  - blackbox.yml

blackbox.yml
scrape_configs:
 - job_name: 'blackbox'
    metrics_path: /probe
    params:
      module: [http_2xx]
    static_configs:
      - targets:
        - http://prometheus.io
        - https://prometheus.io
        - http://example.com:8080
    relabel_configs:
      - source_labels: [__address__]
        target_label: __param_target
      - source_labels: [__param_target]
        target_label: instance
      - target_label: __address__
        replacement: <IP_ADDRESS>:9115  # The blackbox exporter's real hostname:port.

@roidelapluie I would like to pick this up.

Welcome! Right, I will assign it to you. If you seek help, please reach out to https://prometheus.io/community/ ; we have  multiple channels / mailing list, and also contributors office hours accross multiple timezones. Also happy to help here on github.

We are exploring similar in prometheus/snmp_exporter and would like to keep the approaches aligned. Ben and my current thinking there was to go through CLI parameters. We will think about this and update.
For reference, see

https://github.com/prometheus/snmp_exporter/issues/628
https://github.com/prometheus/snmp_exporter/issues/625
https://docs.google.com/document/d/1McJJIiJfHgoecVrVNXx4ABJmI5M21e-6O9IgMNbVnvw/edit

I have added the "flag" alternative to the considered options in our design doc.

One question, do we need a top-level scrape_configs: key in the example of the blackbox.yml? The top-level of the file could simply be a list.

One question, do we need a top-level scrape_configs: key in the example of the blackbox.yml? The top-level of the file could simply be a list.

We have a top level groups in the rules, that is why I ketps the top level scrape_configs, for consistency.

Maybe it would be simpler to make this a much more generic include_files: directive, then included files could contain scrape_configs and/or rules.
We would need a recursive depth handler, but it would be much more generic.

Julien, look into IRC, we shared a Meet URL :p

Our current thinking is at https://docs.google.com/document/d/1BK_Gc3ixoWyxr9F5qGC07HEcfDPtb6z96mfqoGyz52Y and I will open a thread on prometheus-developers to make people aware of it, as well.

VictoriaMetrics' vmagent does this perfectly:
https://github.com/VictoriaMetrics/VictoriaMetrics/blob/master/docs/vmagent.md#loading-scrape-configs-from-multiple-files
Can this please be supported in the native prometheus client as well?

I'm just getting started with Prometheus, but we use a lot of Ansible for provisioning. I'd like to have an Ansible role (Ansible's concept of libraries) that sets up the prometheus server and base config. Then have roles for exporters that can just drop a file with their job/target/labels and that prometheus base config would be configured with a wildcard to slurp up any new configs dropped there. I feel like the implementation discussed here would fit this use case well.

If I made a PR with the scrape_config_files option, is there inclination to accept it?

I have a usecase for it: I maintain a public repo with my ansible playbooks. I want to share some jobs, but keep others private, so it'd be extra handy if I can split it into multiple files and commit some files but put others into .gitignore. Guess it would be helpful for others who are trying to automate provisioning their Prometheus configs as well.

Has anyone devised a workaround for this at all? I have a tricky automation scenario that I'm unable to find a viable solution to right now with the singular config file. I am going to have to template out different parts of the file and it's going to get messy. Would really appreciate this functionality or even an alternative method to get a similar effect of modular config.

If I may chime in ;)
Rather than list each file you wanat to load, it would be much more efficient to point to a directory and have it auto load anything that ends in *.yml.
For example, you could have /usr/local/etc/prometheus/scrapes.yml.d/  and inside that folder have blackbox.yml, another.yml, and so on.

Any update on this ? I don't want to switch to VictoriaMetrics just for this feature ! 😅

See #12019

This topic of importing multiple scrape configs has been a frequent request for the past two years. It is important to note that users are not simply asking to include any files, but rather to import multiple scrape configs.
My design document was marked as deprecated, however, I disagree with this. I strongly believe that we should uphold the original principle of Prometheus, which is to not do configuration management. Merging YAML, keys, lists, etc., can be complex, difficult to implement, and can lead to various expectations about how merging works. Additionally, this can create problems for system administrators and those who support Prometheus users on a daily basis.
Therefore, I have implemented my original design document, which is an include mechanism similar to the one we have for rule files. We simply include scrape_configs in the same way we include rule groups. Overall, this meets the needs of the vast majority of users, and I believe that this is a necessary feature.
As for the YAML include issue, I do not believe it is worth implementing and supporting. Instead, we should allow config management tools to handle their job and let each user choose their own way to recompose the YAML files with the rules they prefer.
To conclude this specific issue, I have implemented scrape config includes in #12019, and I hope that we can reach lazy consensus to implement this feature over the next few days.

If I may chime in ;)
Rather than list each file you want to load, it would be much more efficient to point to a directory and have it auto load anything that ends in *.yml.
For example, you could have /usr/local/etc/prometheus/scrapes.yml.d/ and inside that folder have blackbox.yml, another.yml, and so on.

This is possible with the PR: /usr/local/etc/prometheus/scrapes.yml.d/*.yml`

When could this be implemented ?

Is this already implemented? I tried the last version of docoker image and I could not use the feature.
Example:
global:
  scrape_interval: 5s
  evaluation_interval: 15s

scrape_config_files:
  - /etc/prometheus/scrape_configs/*.yml

scrape_configs:
  - job_name: prometheus
    static_configs:
      - targets: ['prometheus:9090']

Error loading config (--config.file=/etc/prometheus/prometheus-global.yml)" file=/etc/prometheus/prometheus-global.yml err="parsing YAML file /etc/prometheus/prometheus-global.yml: yaml: unmarshal errors:\n  line 5: field scrape_config_files not found in type config.plain"

Implemented in #12019

@roidelapluie which Prometheus version should we expect this at? or was it released already?

You can test 2.43.0-rc.0. 2.43.0 will be out soon.


Add ABOUT files for JSON schemas

https://github.com/nexB/scancode.io/tree/main/scanpipe/pipes/schemas should have some ABOUT file imho

We have now ABOUT file for the schemas.


Added Blogs Folder

Related Issue

Issue number goes here:
#23

Proposed Changes

Added Blogs folder to the main directory
Created a universal blog post page(dummy)

Checklist

[X] Documentation of the code
[X] Add your name to the CONTRIBUTORS file
[X] Testing your code in the local machine

Screenshots

For seeing the Changes you can headover to https://tinyurl.com/GSAsansol-Blog

@modiniraj09 Looks amazing. Thanks for your valuable contribution.


Need help using lime test linux -debug

Describe your problem here.
I put it and then it uses neko, does it need that? I need help solving this
Are you modding a build from source or with Lua?
Source
What is your build target?
Mac
Did you edit anything in this build? If so, mention or summarize your changes.
No

this guy literally make issue every 1-6 hour

this guy literally make issue every 1-6 hour

Lol I do need help bro

Yeah Mac needs neko

Yeah Mac needs neko

Thx bro it worked Shadow


If seconds pick less than 10 - zero is fade (09 => 9)

https://jsfiddle.net/myobxe13/
Your Environment

flatpickr version used: 4.6.3
Browser name and version: Google Chrome Version 80.0.3987.116 (Official build), (64 бит)
OS and version: Windows 10 Pro x64

Hi,
In your dateFormat configuration, you can use: dateFormat: 'Y-m-d H:i:S' (notice uppercase "S")
This give leading 0, as doc says: https://flatpickr.js.org/formatting/


Client and master wireless interfaces need to be on the same channel on Slate and Flint routers

Master interface needs to be explicitly configured to the same channel as the AP the client is trying to connect to otherwise it is not reachable.
This seems like it could be a problem when trying to connect to networks with the client interface that have varying channels.
I'm not sure if this is a bug or a limitation but I'm curious your thoughts as to a work around.
Thanks!!

Honestly, I don't understand how to use both client and master at the same time with these routers without just losing the connection and having to reset the whole router (I can't find my ethernet dong lol)

Hi, the AP should follow the client frequency. It's usually not set in the configuration, does auto work? Bear in mind that it make take a minute or two due to DFS scan.

I’ll try again with auto… any logging I can help with?

To download the system log, head to Speedify top bar -> Generate Logs.
Extract the archive, it should be tmp/logreadfile.


Wildcard Domain in KubernetesIngress get no rule in Router

Bug

Configured an wildcard domain (http) within Kubernetes Ingress.
In Traefik1.7 it works as well as it should.
In Traefik2.1.3 there is no rule shown at dashboard.

What did you expect to see?
In Traefik1.7 a wildcard domain was mapped into a regex route rule:

What did you see instead?
In Traefik2.1.3 this list keeps empty

But i see an entry under HTTP Services that say the right generated rule will be used by a router.

Please ignore the fact that the name includes "ssl". This is just the deployment name. Service and ingress are tested on port 80.
Output of traefik version: (What version of Traefik are you using?)

2.1.3

What is your environment & configuration (arguments, toml, provider, platform, ...)?
...
 containers:
  - args:
    - --log=true
    - --log.level=INFO
    - --providers.kubernetesIngress.ingressEndpoint.ip=<IP_ADDRESS>
    - --entryPoints.http.address=:80
    - --entryPoints.https.address=:443
    - --providers.kubernetesingress=true
    - --providers.kubernetescrd=false
    - --api=true
    - --api.dashboard=true
    - --api.insecure=true
    - --ping=true
    - --log.level=DEBUG
    - --accesslog=true

ingress.yaml
apiVersion: extensions/v1beta1
kind: Ingress
metadata:
  annotations:
    field.cattle.io/publicEndpoints: '[{"addresses":["<IP_ADDRESS>"],"port":80,"protocol":"HTTP","serviceName":"default:demo-ssl-demo-ssl-wildcard","ingressName":"default:demo-ssl-demo-ssl-wildcard","hostname":"*.somedomain.tld","path":"/","allNodes":true}]'
    kubernetes.io/ingress.class: traefik
    traefik.ingress.kubernetes.io/priority: "1"
  creationTimestamp: "2020-01-27T13:19:26Z"
  generation: 3
  labels:
    app.kubernetes.io/instance: demo-ssl
    app.kubernetes.io/managed-by: Tiller
    app.kubernetes.io/name: demo-ssl-wildcard
    app.kubernetes.io/version: "1.0"
    helm.sh/chart: demo-ssl-wildcard-0.1.0
  name: demo-ssl-demo-ssl-wildcard
  namespace: default
  resourceVersion: "56777724"
  selfLink: /apis/extensions/v1beta1/namespaces/default/ingresses/demo-ssl-demo-ssl-wildcard
  uid: 524e0a63-09cc-4886-a013-e387834680d0
spec:
  rules:
  - host: '*.somedomain.tld'
    http:
      paths:
      - backend:
          serviceName: demo-ssl-demo-ssl-wildcard
          servicePort: 80
        path: /

Closed by #6251.

@dtomcej Thank you for that incredible fast response and solution! Cheers ...


GStreamer-CRITICAL Error with youtube live video

Hello,
I test the resin-wpe with a live video from youtube 👍
WPE_URL = https://www.youtube.com/embed/hL0sEdVJs3U?autoplay=1&vq=hd720
But the video won't start and I get this error :
(WPEWebProcess:39): GStreamer-CRITICAL **: _gst_util_uint64_scale: assertion 'denom != 0' failed

Any idea ?
Thanks.

From https://forums.resin.io/t/resin-wpe-gstreamer-critical-error-with-youtube-live-video/2171/4

Hello,
I get this response from WPEWebKit team : https://github.com/WebPlatformForEmbedded/WPEWebKit/issues/411#issuecomment-346425899

You need a patched GStreamer to solve this issue. It's solved in WebKit upstream here:
https://bugs.webkit.org/show_bug.cgi?id=176804
I've just backported the patch to gst1-plugins-good in buildroot here:
WebPlatformForEmbedded/buildroot@85e8095

@samouds I updated WPE to the latest version that includes the fix for this problem. I tested with the link you provided and it seems to be working. Feel free to re-open if you still experience issues

Thanks @petrosagg I get this fixed this morning too :) and checked with a live stream from youtube and it's working perfectly !
Big thanks to the resin team and to you.


Scraping failure (JS): globalrelay.com/company/careers/jobs

Jina Reader does not extract the job postings from this website:
https://r.jina.ai/https://www.globalrelay.com/company/careers/jobs/?gh_jid=5117891004

Never mind. I found a way to scrape it.

Never mind. I found a way to scrape it.

How did you achieve this? I have encountered the same problem.


Add support for separate voting.yml

We're evaluating using git-democracy to collaboratively make internal company decisions, but our problem is that we have different types of decisions that require different thresholds, and so we'll need many different voting.ymls and voters.ymls.
The way we're approaching organizing our documents, we could do it by directory - if a pull request has changes that modify the contents of a directory, the voting rules for that directory's voting.yml (or a parent directory, recursively) are used. For standard code applications, this may also work well for monorepos, etc.
If only one root voting.yml is present, that's what's used.
If the pull request has multiple changes in different folders which include different voting.ymls, we go up to the next highest and maybe root voting.yml.
A solution that would also work for us is to have multiple voting.ymls, like:
bylaws-change.voting.yml
new-project.voting.yml
...

and have some way of indicating which process was appropriate in a metadata convention on the PR.
If you're interested in having one of both of these as part of git-democracy, that'd be awesome!
If not, no worries - we'll fork and implement ourselves. Just wanted to check to see if you wanted :)

I'm definitely interested in being able to support monorepos with this projects. I think the way I would intuitively think of the config working is a little different though. I'm wondering if this might work for you too.
Alternative solution: The deepest voting.yml found would be the one used for that section of code. Also if there's no voting.yml covering a section of code, it won't use one. (I can draw out an example later if that idea isn't clear.)
If one of these approaches were added, then it would potentially need to present multiple voting comments or a multi-vote single-comment. This might be pretty confusing if not done well. What do you think this experience should look like?
Another option that might work would be to add a configuration for this action that lets you specify where the config is, then for the user if they have a workflows per action, they can just ignore the action if there's no changes in that directory or use the action on the directory. (I think this would still need an answer for multi-votes though.) This usage would more closely match how my company configures other github actions in their monorepo.

If you're interested in having one of both of these as part of git-democracy, that'd be awesome!

I'm interested, just not sure how to solve it in an intuitive to use way.

This idea sounds good to me. I'm going to say this proposal is accepted. I think that's a reasonable approach to take. If you made a PR that supports this with some documentation and an example of a branch using the change, I would accept it.
It would be a good addition. The idea of two transactionally accepted changes together is an interesting voting concept too. I like that this supports that.

With the now released v2 and the comment by bchrobot above, I think multi-config repos are now a thing. This is untested, if anyone want so write an example, that would be great. Would love to add this to the README.md as well.

I'm going to close this as I think it's implemented.


Example 2

Example 2 returns an empty list.
GET https://graph.microsoft.com/v1.0/sites
It will return a list with this query instead:
GET https://graph.microsoft.com/v1.0/sites?search=

Document Details
⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.

ID: b05ccb12-48fb-7f65-a695-0846564d2bc2
Version Independent ID: 769c63c0-4981-7506-8320-56beafaa8770
Content: List sites - Microsoft Graph v1.0
Content Source: api-reference/v1.0/api/site-list.md
Product: sharepoint
Technology: microsoft-graph
GitHub Login: @spgraph-docs-team
Microsoft Alias: MSGraphDocsVteam

Hi,
Thanks for your feedback. We are currently working on improving docs and we'll do our best to keep your feedback into account while doing that. In the meantime, I'm going to close this item. Thanks for your understanding.


Upgrade of AccessTokenClient

Upgrade of AccessTokenClient
Description
Upgrade of AccessTokenClient
Related Issue(s)

https://github.com/Altinn/altinn-accesstoken/issues/50

Verification

[ ] Your code builds clean without any errors or warnings
[ ] Manual testing done (required)
[ ] Relevant automated test added (if you find this hard, leave it and we'll help out)
[ ] All tests run green

Let's merge this and see how it goes. Don't wait too long. We need to have time to revert the changes.


Home page Animated Icon

to improve UI I think will be nice to have an home page animated icon gif

Please assign me this issue . I am interested to work on this issue.Looking for positive response.
thank you .

Hi @youtanimstar
This is issue is related to below PR
animated icon added in index #36


Fix 0% coverage problem caused after static libraries were introduced.

Issue seems to have gone away without much a direct change to the code base.


Mod crashes on a server when a boat is broken

I don't think we've done any server side testing. It's possible that there are other bugs as well. We should setup and run a server and fix any bugs we find with the mod.

AnnoyanceFix currently has not plans to support multiplayer, unfortunately

This mod now has multiplayer support and should no longer crash. Report/reopen this ticket if you are still having issues 👍


Mark 'csr' field as required in CertificateRequest

What this PR does / why we need it:
This field is currently marked as required by our validating webhook, but not by our CRD schema.
This should be safe to do, as:

it was required anyway
very few users manually create CertificateRequest resources

Release note:
Mark `certificaterequest.spec.csr` field as required in OpenAPI schema

/lgtm


Fix failing build w/ android platform and broken mobile HCP

This fixes this buildpack for apps that have the android platform installed. It also fixes hot code push for all mobile apps that have BUILDPACK_PRELAUNCH_METEOR set.
What this does:

Remove the Android platform because it fails due to the Android tools not being installed
Leave iOS, even when BUILDPACK_PRELAUNCH_METEOR is set, because otherwise mobile hot code push doesn't work (/__cordova/manifest.json is not generated if there are no mobile platforms)
NOTE that this means HCP is broken for android-only apps! I can't think of a solution for that.

Update: I had forgotten to add || true so it would fail if the android platform wasn't installed. Fixed now.


Rename "enter" named range to "entry" to conform to the latest spec

TL;DR
Update "enter" to "entry" to bring polyfill closer to the latest spec
Details
According to this comment, "enter" was renamed to "entry" so this PR updates the polyfill accordingly.

Please run "npm run dev" to rebuild the binaries.  These should be part of the pull request.

Please run "npm run dev" to rebuild the binaries. These should be part of the pull request.

@kevers-google done

Merged PR#108, which has created a merge conflict for the binaries.  You'll need to merge master and rebuild the binaries so that the id Fix in #108 is reflected in the updated binaries for this PR.  When resolving the merge conflict it might be simplest to stomp your local changed with the version in master and then rebuild to create fresh local binaries.

Please run "npm run dev" to rebuild the binaries. These should be part of the pull request.

I just finished automating this step in an action script so the repo no longer needs the dist folder.

The dist directory has been removed from the build, as the build/deploy has been automated.  Kindly cleanup to remove updating the dist files, and we should be good to go.


[Question] How is hm-panelizer different from kikit (the GUI kicad plugin)?

While I realize this project is quite old; I wonder how it is different then the KiKit GUI version. I was hoping to find a tool that would panelize 'random' boards by allowing for manual layout, but it seems this tool just panelizes the same board. If that is the case, I suppose this is now obsolete and no longer needed :(

for different board shapes use this,
https://github.com/ThisIsNotRocketScience/GerberTools
https://www.youtube.com/watch?v=UNSda6lv4cM&t=1091s


flow: Cut workaround for facebook/flow#8833

This issue was fixed in Flow v0.173.0, after I reported it:
https://github.com/facebook/flow/issues/8833
https://github.com/facebook/flow/blob/main/Changelog.md#01730
Now that we've upgraded past that (in #5700), we get to drop the workaround.

Oh, nice! From some grepping, I see some things that might be workarounds for the same bug? What do you think:
src/streams/streamsReducer.js
export function updateStreamProperties<S: Stream | Subscription>(
  stream: S,
  event: StreamUpdateEvent,
): S {
  switch (event.property) {
    case ('name': 'name'):
      return { ...stream, [event.property]: event.value };
    case ('description': 'description'):
      return {
        ...stream,
        [event.property]: event.value,
        rendered_description: event.rendered_description,
      };
    case ('date_created': 'date_created'):
      return { ...stream, [event.property]: event.value };
    case ('invite_only': 'invite_only'):
      return {
        ...stream,
        [event.property]: event.value,
        history_public_to_subscribers: event.history_public_to_subscribers,
        is_web_public: event.is_web_public,
      };
    case ('rendered_description': 'rendered_description'):
      return { ...stream, [event.property]: event.value };
    case ('is_web_public': 'is_web_public'):
      return { ...stream, [event.property]: event.value };
    case ('stream_post_policy': 'stream_post_policy'):
      return { ...stream, [event.property]: event.value };
    case ('message_retention_days': 'message_retention_days'):
      return { ...stream, [event.property]: event.value };
    case ('history_public_to_subscribers': 'history_public_to_subscribers'):
      return { ...stream, [event.property]: event.value };
    case ('first_message_id': 'first_message_id'):
      return { ...stream, [event.property]: event.value };
    case ('is_announcement_only': 'is_announcement_only'):
      return { ...stream, [event.property]: event.value };
    default:
      ensureUnreachable(event.property);
      return stream;
  }
}

Looks like that's a different issue. When I remove those, I get a bunch of errors starting with:
$ npx flow --color=never
Error ┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈ src/streams/streamsReducer.js:18:19

Computing object literal [1] may lead to an exponentially large number of cases
to reason about because inferred union from object literal [1] | object
literal [1] and union type [2] are both unions. Please use at most one union type
per spread to simplify reasoning about the spread result. You may be able to get
rid of a union by specifying a more general type that captures all of the
branches of the union. [exponential-spread]

   src/streams/streamsReducer.js:18:19
   18│       return { ...stream, [event.property]: event.value };
                         ^^^^^^

References:
   src/streams/streamsReducer.js:18:14
   18│       return { ...stream, [event.property]: event.value };
                    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [1]
   src/streams/streamsReducer.js:13:11
   13│   stream: S,
                 ^ [2]

It does seem related, as there's a generic bound involved, and string literals, and the workaround is much the same.


Portuguese (Brazil)

First time doing this, so please forgive if i'm doing it wrong. Here is the translation for Portuguese (Brazil)
Portuguese (Brazil).zip

Hi, i use your plugin in Windows kodi and its perfect. Also I have a receiver vu+ SOLO2 based on Linux , but does not work any press plugin. Mipsel can be implemented in git , then to compile the addon? It would be great

I would change "Ativar (use à sua responsabilidade)" por "Ativar (use por sua conta e risco)".
But this is not wrong, I just think it would sound more natural.
Excellent translation!

Hi. I tested the plugin on a vu + decoder with enigma2, and it seems that it is not supported. Is it possible to add mipsel support to run Quasar in enigma2 decoder? Best regards.


Fix typo and use double quotes for consistency

A small fix for highlight group names.
Most of the codebase use double quotes so I changed some of the single quotes to double quotes for consistency.

Thank you!


NEW Adding controller to expose form schema endpoint for elemental blocks

This PR is heavily influenced by asset-admin. First time I've messed around with form schema endpoints. I'm possibly missing something. But in my testing this will drive a FormBuilderLoader for the most part

Resolved #326


TypeError cancelled

It looks like bot Safari 14 and iOS Safari 14 can throw a TypeError with a message of cancelled when a fetch request is cancelled. Would it make sense to include here?
See also https://github.com/shuding/request-cancellation-test 👀

Cancellation is not a network error, so I don't think it makes sense in this package.

That's fair.. I guess I'm trying to achieve something more specific where I am using is-network-error to detect if an error was the result of a network error or not. Due to the multiple ways that different browsers report network errors, it's difficult to determine the cause of a particular network error.
For instance, Chrome appears to use the same error TypeError: Failed to fetch for both network errors and fetch requests that have been aborted, either using AbortSignal or from the browser itself. So in that instance it's difficult to differentiate them.
In this instance it looks like the error message produced by Safari might distinguish between a network error and aborted fetch request? If that's the case, I'll just handle the TypeError: cancelled error myself.

In this instance it looks like the error message produced by Safari might distinguish between a network error and aborted fetch request?

Seems like that, yes.


Add multiple matching strategies

The default matching algorithm that allows overlaps is not the original algorithm described in the scientific paper. Several matching strategies are possible, it is necessary to declare an interface and let the user choose the strategy.

done in release 0.4.0 https://github.com/scossin/iamsystem_python/pull/17


Cannot install cloned repo

Trying to do some work on this. Hope someone doesn't mind giving me a little help.
When I try to npm install the cloned repo I get:
npm ERR! 404 Registry returned 404 for GET on https://registry.npmjs.org/angular2-seed-advanced
So I changed my package.json file to read:
"angular2-seed-advanced":"NathanWalker/angular2-seed-advanced",
This should load the dependency from the correct repo as far as I know and seem to work but now I get an error on the angular2-seed-advanced postinstall:
npm ERR! Failed at the<EMAIL_ADDRESS>postinstall script 'typings install && gulp check.versions && npm prune && gulp webdriver && node tools/install.js'.
If I just try to 'typings install' I get an error about a missing typings.json file so I think that's the cause.
Am I doing this right and what do I need to do to make it work?

yes because I don't have angular2-seed-advanced or peoplewareDo/angular2-seed-advanced yet in the npm repo yet, give some time to fix that.
Don't point to NathanWalker/angular2-seed-advanced, please use https://github.com/peoplewareDo/angular2-seed-advanced (some changes goes there)
Workaround:

download https://github.com/peoplewareDo/angular2-seed-advanced
use npm link in a package folder will create a globally-installed symbolic link
download this https://github.com/peoplewareDo/generator-ng2-seed-advanced
inside the generator-ng2-seed-advanced run npm link angular2-seed-advanced to complete the dependency.

GOOD to go.

I'll do this. Thank youuu!

remember that when I publish the project on npm then you need to redownload the projects

Ok. Should be easy at that point. Thanks again!


null values in conversation

hey, great tutorial..Im facing an error when i hit
[Get] Get recent convesation
http://localhost:3000/room/565241728497455b966fbc45dc2fa7bd
same issue in
http://localhost:3000/room/565241728497455b966fbc45dc2fa7bd?limit=15&page=0
i get empty data in conversation

{
    "success": true,
    "conversation": [],
    "users": [
        {
            "_id": "5e221be2bbff463cb239ce14278b11b1",
            "firstName": "user1",
            "lastName": "user1",
            "type": "consumer",
            "createdAt": "2021-03-31T22:27:53.203Z",
            "updatedAt": "2021-03-31T22:27:53.203Z",
            "__v": 0
        },
        {
            "_id": "6736f6c9698549da8c77e75f2a784c06",
            "firstName": "user2",
            "lastName": "user2",
            "type": "consumer",
            "createdAt": "2021-03-31T22:28:03.360Z",
            "updatedAt": "2021-03-31T22:28:03.360Z",
            "__v": 0
        }
    ]
}

@ggichure
Try Url: http://localhost:3000/room/565241728497455b966fbc45dc2fa7bd?limit=1&page=0
Where limit will be set to 1.
May be you didn't post a message to that chat room or may be there was an error while posting a message to a chatroom.

thank you @Harshitchourasiya for responding to the OP's query.


Change logging config

This is to resolve Issue 7 https://github.com/SolaceSamples/solace-samples-java-jcsmp/issues/7
Have modified the build.gradle file and the directory structure to include the log4j2.xml properties file outside of the compiled JAR file in a config directory, and have updated the build.gradle file to modify the start scripts' classpaths to include the config.

Confirmed.


Cannot deploy from private docker hub repository

Trying to deploy from a private repository I own. I've authenticated with docker and I can push/pull from it. However when running a commander deploy, I get:
root@power-nine:~/code/PowerNine-Delivery# commander app:deploy power-nine zombor/power-nine
Pulling image zombor/power-nine...
ERROR: error pulling image zombor/power-nine. Attempt 1: Error: image zombor/power-nine: not found
ERROR: error pulling image zombor/power-nine. Attempt 2: Error: image zombor/power-nine: not found
ERROR: error pulling image zombor/power-nine. Attempt 3: Error: image zombor/power-nine: not found
ERROR: unable to pull zombor/power-nine. Has it been released yet?

If I make this repository public, I'm able to deploy. I'm using Docker 1.7.0 with galaxy 0.6.0.

@zombor Thanks for the report.  Is this with the main docker hub registry?  We deploy from our own private registry but I don't think we've tested against a private repository on the main registry before.

Yes, from https://registry.hub.docker.com.
My docker auth is stored in ~/.docker/config.json.

The auth path needed some work anyway. I have a patch incoming for this...

The above commit seems to have resolved the problem:
root@power-nine:~/go/src/github.com/litl/galaxy# commander app:deploy power-nine zombor/power-nine
Pulling image zombor/power-nine...
Deployed zombor/power-nine.

I'm getting this same error again. I'm not sure what changed. If I make the repo public, it works fine. I still have my ~/.docker/config.json with the auth data in it.

Looks like the locked version of go-dockerclient didn't support ~/.docker/config.json. The above referenced PR fixes that.


Respect and enable uninstalls of existing .egg-info packages

Summary
Users often find themselves dropped into environments that contain .egg-info packages. While we won't support installing these, it's not hard to support identifying them (e.g., in pip freeze) and uninstalling them.
Closes #2928.
Closes #3341.
Test Plan
Ran cargo run pip freeze --python /opt/homebrew/Caskroom/miniforge/base/envs/TEST/bin/python, with an environment that includes pip as an .egg-info (/opt/homebrew/Caskroom/miniforge/base/envs/TEST/lib/python3.12/site-packages/pip-24.0-py3.12.egg-info):
cffi @ file:///Users/runner/miniforge3/conda-bld/cffi_1696001825047/work
pip==24.0
pycparser @ file:///home/conda/feedstock_root/build_artifacts/pycparser_1711811537435/work
setuptools==69.5.1
wheel==0.43.0

Then ran cargo run pip uninstall, verified that pip was uninstalled, and no longer listed in pip freeze.

Also closes #2841

Thanks! Added.

Yes good call, thanks.


[Feature Req] input volume based audio capture stop for voice rec

Hi Edin,
First off, awesome contribution to the Cordova world of plugins & sample code here.
A key feature for voice recognition and probably other use cases would be volume based stopping of audio capture to automatically kick off further processing/NLP.
How would I need to go about this, using your cordova plugin & given the sample code for events here?
...or even better yet, is your (older) speech rec project still available / compatible to the current version of your plugin?
Thanks!
Oliver
PS: Commodore64 was a fantastic way to get started - same here :)

Thank you, Oliver!
I agree, being able to get audio chunks of speech is very useful in many scenarios, which is the reason why I created the project you mention. As I mentioned in the other issue, that project has since then been purchased by a  company for commercial use, so it is sadly not available as open-source any longer, but a man needs to eat 😀
The audioinput plugin can be used in many ways, so that type of feature is not something that will be implemented in the plugin, since I believe that Cordova plugins should focus on doing one thing, and doing that well. Basically keeping it clean and simple.
But with that said, it is of course still possible to implement similar functionality outside the audioinput plugin, using for example Web Audio by continuously analyzing the captured audio and creating chunks of audio above a certain audio level.
C64 was indeed a really an amazing machine. Later on, after transitioning to C128, I started using Amiga and only reluctantly had to give that up in pretty late, in 1999. But still we can both be proud of being part of the Generation C64 ☺
Are you on LinkedIn?

Yes, Edin, I'm also on linkedIn :-) ..again apologies for the level of persistence, time is currently not on my side. But I think I managed to find a usable implementation of volume based silence recognition. Probably neither fully accurate nor elegant, but it will do.
I fully appreciate the license constraint, and equally agree that one has got to make a living! I think you were quite ahead of the major voice processing/rec players that now refocus on the topic in combination with NLP and other cool tech.
Re: where such a "volume"-feature could or should sit, I also agree with your statement, with the only exception that especially in hybrid apps performance is always an issue and if some of the background processing can be kept at a stack lower level, I wouldn't say no :)
PS: The C64 got me straight to the Atari corner - yep, the other "side", lol. Those were all great times, including Assembly language, floppy discs and what not.


Add an example migration policy to /examples directory

What this PR does / why we need it:
This PR adds a migration policy manifest example to our /examples directory.
This will ease playing with policies for either testing or exploration.
Release note:

NONE

/cc @enp0s3 @Barakmor1
Mind having a quick look?

/approve
/hold
Please unhold upon addressing @xpivarc comments

@iholder101 As a follow-up work, Maybe it even worth to extend the virtctl create to create migration policy manifests.

/unhold

@iholder101 As a follow-up work, Maybe it even worth to extend the virtctl create to create migration policy manifests.

For sure!
This is definitely on my check-list (also for VM clones).

/lgtm

/test pull-kubevirt-e2e-k8s-1.25-sig-compute-migrations


[Unity][Frontend] Translate StableHLO to Relax

Add a converter to convert the StableHLO to Relax, the source StableHLO IR  could be lowered from JAX, or TensorFlow.

It depends on StableHLO Python Bindings maintained in jaxlib
It only supports one-way conversion, and no MLIR Relax is introduced
Use JAX to generate reference inference result for accuracy verification, and an e2e (JAX ResNet -> StableHLO -> Relax) works

@tvm-bot rerun

CI is green, pls take a look. cc: @psrivas2  @Hzfengsy  @tqchen

Note on unittests: in the future, we want to migrate check_correctness-based numerical tests to IR structural equality test, which is much more accurate and to-the-point


Loading Please Wait took forever, not loading.

As the title says (win 10)
mac works fine

@CptJackieSparrow please follow #545


Remove log for sia lib to fix athenz cert check

There are unnecessary 2 lines output for athenz cert check, eg:
2023/02/01 18:08:29 Group athenz id: 10952

2023/02/01 18:08:29 Group athenz id: 10952

{"application":"athenz-cert-check","status_code":0,"status_msg":"All Certificates are valid"}

Remove the log in sia lib to fix this issue
Signed-off-by: dma<EMAIL_ADDRESS>

this is already included in #2057


Support for jobs.getQueryResults and creating a Client with a yup-oauth2 ServiceAccountKey

Made a couple of additions that I required and thought push them to the repository. This PR:

Adds support for the jobs.getQueryResults API and for the results to be used with ResultSet.
Adds the ability to create a Client from a yup-oauth2 ServiceAccountKey so that a client can be created without a JSON key file.

LGTM. Thanks for this contribution. I will merge to the main branch although the tests are not passing. Will fix that today.

Published version 0.4.0 on crates.io. Thanks!


Can't skip or jump

When I try to skip to 10 minutes from 0 minute.
It doesn't work

Okay guys ;) Long awaited update is hereee! cheers 👍

can skip now but range not correct
when you jump to the end of video, it start redownload the whole video start from range bytes 0

@hklcf working on it

@hklcf done! any problems after this patch?

loop at bytes 0...

Have you found a solution to the problem?

Maybe this will work if you make curl combine with fwrite so you can catch the buffer range. It just my opinion. :D

@japnimedev have you try CURLOPT_FILE?

Closed, issue will be added for the new updates.


[BREAKING] Make JSX middleware import more simple

Currently, to use JSX middleware, we have to do:

import h and jsx
app.use with jsx()
c.render to return HTML.

import { Hono } from 'hono'
import { h, jsx } from 'hono/jsx'

const app = new Hono()

app.use('*', jsx())

app.get('/', (c) => {
  const Layout = (props) => (

      {props.children}

  )

  return c.render(
    <Layout>

foo

    </Layout>
  ) // Add <!doctype html>  automatically
})

I think it's not so simple.

We don't need to use app.use. When h is imported, JSX will be enabled.
We don't need to use c.render. We can use c.html with writing <!doctype html> instead of it. It's not a bad idea to explicitly declare <!doctype html>.
h may be the initial character of a hyperscript. I think it's not suitable for SSR.

How about writing like below with html template literal tag #312
import { Hono } from 'hono'
import { jsx, html } from 'hono/jsx' // `html` is alias of `utils/html`

const app = new Hono()

app.get('/', (c) => {
  const Layout = (props) =>
    html`<!DOCTYPE html>

          ${props.children}

      `

  return c.html(
    <Layout>

foo

    </Layout>
  )
})

These are breaking changes. But, JSX middleware has only just been released, so not many people are using it.

I think it is a good specification. 👍
It looks concise, easy to understand, and performs well enough, so I think being able to write in this way will be one of Hono's most attractive features.

I feel that this pattern... could be a good option with both well DX and well performance, even when considered as a template engine for JavaScript in general.

Okay, I'll implement it later.


sosreport: add GitHub action to test the role

Add a GitHub action to test the role with molecule.
This closes osism/ansible-collection-commons#331

Signed-off-by: Ramona Rautenberg<EMAIL_ADDRESS>

Wrong repository


Fix update expressions

Features

Bump version to 1.0.11
Bump js-slang dependency, fixing update expressions

Pull Request Test Coverage Report for Build 887

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 25.761%

Totals

Change from base Build 884:
0.0%

Covered Lines:
903

Relevant Lines:
2965

💛  - Coveralls


Participate in Connectathon 28

Connectathon 28 is happening Sep 13-15
Goal is to participate in the CDS Hooks WG and be able to say that Epic or Cerner or some other large company successfully consumed our service

[x] @TH33765 to register 2 tickets
[x] Sign up (and also use as a way to anticipate participation) for the CDS Hooks WG at https://bit.ly/cds-hooks-connectathon-tracking
[x] Subscribe to the Zulip stream https://chat.fhir.org/#narrow/stream/179159-cds-hooks
[x] Participate in any CDS Hooks WG specific kickoff calls (happening Sep 9 now)
[x] Plan to have a CDS Service live during the connectathon that we test according to the track details @mseckykoebel - broadly something to do (#77)
[ ] Update docs.sero.run with any documentation changes to existing docs from changes to the lib created by participation @mseckykoebel
[ ] We will need to finish to participate successfully https://github.com/Automate-Medical/sero/issues/7 (this is assigned to me)

Separately, we should treat this Connectathon as an opportunity to launch Sero

[ ] Have a Substack post ready to go about it
[ ] Say that we are participating with Epic, Cerner, etc on different plaforms
[ ] Maybe a video we try to push
[ ] Do a version 0.1.0 release and complete the 0.1.0 Launch milestone

Additionally, there are other working group tracks that use CDS Hooks, and poking around the material might reveal some interesting opportunities. For example: https://confluence.hl7.org/display/FHIR/2021-09+Da+Vinci+Provider+Access+and+Burden+Reduction

Kickoff is scheduled:

Track Kick-off/Orientation on Thursday, Sep 9th @ 12pm Eastern

Made a note about point number 6 in slack, but holding off on updating the goodRx documentation until after the connectathon, as it involves re-recording Josh's demo video and a lot of other changes that we might find easier to revert back.


Sending 'HTTP/1.1 200 OK' instead of 'HTTP/1.1 200'

I have device that requires 'HTTP/1.1 200 OK', 'HTTP/1.1 200' is not accepted.

This does not look correct to me ... OK in this could be defined by _reasonPhase: (now I see it missing "r")
        HeaderAppendHttpStatus(status);
        if (_reasonPhase != null)
        {
            HeaderAppend(" ");
            HeaderAppend(_reasonPhase);
        }

Great,
I did not found the 'owin.ResponseReasonPhrase' which does this. Thanks.


Clean cached handlers (and fns) after HMR/rebuild

Describe the feature
Hey!
I'd like to propose to clean up Nitro's cached functions and handlers after HMR triggers or a rebuild takes place.
While they already change when their code changes (due to how the cache hashes are being created), external factors like new data from API or simply imported deps could change and the cache is not invalidated.
Example

Visit /
See 1-4
Edit arr.ts
Refresh
See no changes

Additional information

[ ] Would you be willing to help implement this feature?

Closing in favor of https://github.com/unjs/nitro/issues/2081


MINOR: Add .jar and vendor paths to gitignore

Trivial, but makes working with this plugin more fun :)

LGTM


typing: ref of type A | undefined do not unwrap refs in A

Version
3.0.4
Reproduction link
https://codesandbox.io/s/goofy-sinoussi-gojxu?file=/src/index.ts
Steps to reproduce
const r = ref<{ a: Ref<number> } | undefined>({ a: ref(3) });
r.value.a // should be type `number`, but shown as `Ref<number>`

What is expected?
r.value.a should be type number
What is actually happening?
r.value.a is shown as Ref<number> instead.

No, please see the RFC of composition-api.

If an object is assigned as a ref's value, the object is made deeply reactive by the reactive method.
So that, the Ref<{a: Ref<number>}> will be Ref<{a: number}>.

It is because of the override function.
export function ref<T extends object>(value: T): ToRef<T>
export function ref<T>(value: T): Ref<UnwrapRef<T>>
export function ref<T = any>(): Ref<T | undefined>

your code const x = ref<{ a: Ref<number> } | undefined>(); will run as ref<T = any>(): Ref<T | undefined>, The T type doesn't include in the UnwrapRef.
So, the export function ref<T = any>(): Ref<T | undefined>  should be export function ref<T = any>(): Ref<UnwrapRef<T> | undefined>.

But while changing export function ref<T = any>(): Ref<T | undefined> to export function ref<T = any>(): Ref<UnwrapRef<T> | undefined>, ref's setter shows the error setting type.
const x = ref<{ a: Ref<number> } | undefined>();
// ERROR Type 'Ref<number>' is not assignable to type 'number'.ts(2322)
x.value = { a: ref(1) };

Make sense. Thanks you @Zcating.
I find it slightly hard to work with the typing when we have nested refs.
For example, this will cause the type go wrong badly
const useA = () => ({
  a: ref(3),
});
const x = ref(useA());
x.value = useA(); // you can't do this coz x is not `Ref<{ a: number }>`

It is because the getting & setting type must be the same type. If change ref.value to ref.setValue & ref.getValue, you can do this:
setValue(value: T);
getValue(value: UnwarpRef<T>);

The typing is correct. If you want it to be a number, you should do
const r = ref<{ a: number } | undefined>({ a: ref(3) });


Update add-your-organization-brand-to-encrypted-messages.md

Added prerequisites for new-omeconfiguration (advanced message encyption)

@JohanFreelancer9 Please copy review

Issue#https://github.com/MicrosoftDocs/microsoft-365-docs/issues/7133

@KCCross Please merge this PR. Thanks.

@KCCross Gentle reminder.

@KCCross Kindly merge this PR. Thanks


WIP experiment: attempt to use only a single instance of AvmSimulator

#8888  👈
master

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @dbanks12 and the rest of your teammates on  Graphite


fix(test): windows tests are failing

Which problem is this PR solving?
This issue is occurring because the underlying v8 engine used by node is consuming more memory on windows, while #3628 is about the tests failing on WIndows build, it also fails on a windows machine.
Fixes #3628
Short description of the changes
This is a targeted fix for the current project that is failing to build, this could also be applied in the unit-test.yml, but that would not address (fix) for anyone cloning and running tests in the repo on a Windows machine.
For reference the --max-old-space-size= is actually a v8 configuration option (not specifically node)
https://github.com/nodejs/node/issues/7937
Type of change
Please delete options that are not relevant.

[X] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update

How Has This Been Tested?
Tested locally on a Windows development machine with the following repo steps (the only way locally I found to repo), the clean is required because lerna was caching the result once a successful build occurred.
git clean -xdf
npm install
npm run compile
npm run test

And also in the GitHub pipeline

Hmm, while this is fixing the out of memory issue the @opentelemetry/shim-opentracing:test is failing, I don't have a local repo for this failure...

Restarted windows build and it reports OOM for shim-opentracing too:

> @opentelemetry/shim-opentracing:test

><EMAIL_ADDRESS>test
> nyc ts-mocha -p tsconfig.json test/**/*.test.ts

<--- Last few GCs --->

[2568:000001E238B2A740]     8985 ms: Mark-sweep (reduce) 15.9 (30.1) -> 13.4 (16.3) MB, 13.3 / 0.0 ms  (+ 0.2 ms in 2 steps since start of marking, biggest step 0.2 ms, walltime since start of marking 37 ms) (average mu = 0.998, current mu = 0.998) finali

<--- JS stacktrace --->

FATAL ERROR: Committing semi space failed. Allocation failed - JavaScript heap out of memory
 1: 00007FF6256E168F v8::internal::CodeObjectRegistry::~CodeObjectRegistry+122159
 2: 00007FF62566B456 DSA_meth_get_flags+64118
 3: 00007FF62566C4D2 DSA_meth_get_flags+68338
 4: 00007FF625FA3CB4 v8::Isolate::ReportExternalAllocationLimitReached+116
 5: 00007FF625F8E27D v8::SharedArrayBuffer::Externalize+781
 6: 00007FF625E3183C v8::internal::Heap::EphemeronKeyWriteBarrierFromCode+1468
 7: 00007FF625E3B55F v8::internal::Heap::PageFlagsAreConsistent+3007
 8: 00007FF625E2E119 v8::internal::Heap::CollectGarbage+2137
 9: 00007FF625E3194B v8::internal::Heap::FinalizeIncrementalMarkingAtomically+267
10: 00007FF625E2640F v8::base::CPU::is_fp64_mode+415
11: 00007FF62560007D node::TriggerNodeReport+53341
12: 00007FF6255FE876 node::TriggerNodeReport+47190
13: 00007FF62573F3DB uv_async_send+331
14: 00007FF62573EB6C uv_loop_init+1292
15: 00007FF62573ED0A uv_run+202
16: 00007FF62570DDF5 node::SpinEventLoop+325
17: 00007FF625624271 cppgc::internal::Marker::visitor+57937
18: 00007FF6256A33FA node::Start+202
19: 00007FF6254C86EC RC4_options+347628
20: 00007FF62652A228 v8::internal::compiler::RepresentationChanger::Uint32OverflowOperatorFor+14520
21: 00007FFEF1A84DE0 BaseThreadInitThunk+16
22: 00007FFEF21DE40B RtlUserThreadStart+43

Looks like #3642 addresses the underlying issue causing the high memory so that might be a better way to go


Gitignore, README.md, label templates

Gitea version (or commit ref): 4a3f404
Git version: 2.7.4
Operating system: Ubuntu 16.04 LTS
Database (use [x]):

[x] PostgreSQL
[ ] MySQL
[ ] MSSQL
[ ] SQLite

Can you reproduce the bug at https://try.gitea.io:

[ ] Yes (provide example URL)
[ ] No
[x] Not relevant

Log gist:

Description
Please provide instructions how to use templates for issue label sets, gitignores and readmes.
I tried to place them into relevant subdirectories under custom/conf/, later just conf/, but they don't show up on the webui either way. This was the place where I used them with Gogs.
I think the issue label sets must be working, since it has a list on the webui with just one (Default) option.
I also think, that I'm doing nothing wrong here, and this is actually a bug, and not the lack of instructions.
Thanks.

Place in folders under custom/options/ eg. labels in custom/options/label/

Very well, it works. I had no idea about the /options/ part, and didn't find it anywhere.

Is there a way to make a default for each of these that is automatically selected and make the:

[ ] Initialize Repository (Adds .gitignore, License and README)

checked by default?


Trying to use with React Typescript

./src/index.tsx
Error: Argument at `2` is not JsBuffer

Caused by:
    unknown field `jsx`, expected one of `tsx`, `decorators`, `dynamicImport`, `importAssertions` at line 1 column 318
    at Generator.next (<anonymous>)
    at new Promise (<anonymous>)

What's your craco config?

I try to run directly from your example.
const cracoSwcPlugin = require('craco-swc');

module.exports = {
  plugins: [
    {
      plugin: cracoSwcPlugin,
    },
  ],
};

Do you have a .swcrc file? Also do you have a tsconfig.json file at the root of your repo?

The example is missing this .srwcrc now i am pull requesting


[8.x] fix #37483 (aggregates with having)

Fixes #37483
Havings should behave exactly the same way as unions when aggregating the data

I'll do some writing then ;)


fixed timing error in 2/3 tests

[Current coverage][cc-pull] is 78.00%

Merging [#230][cc-pull] into [develop][cc-base-branch] will not change coverage

@@            develop       #230   diff @@
==========================================
  Files            24         24
  Lines          3660       3660
  Methods           0          0
  Messages          0          0
  Branches          0          0
==========================================
  Hits           2855       2855
  Misses          805        805
  Partials          0          0

Powered by Codecov. Last updated by [1487b6a...87fc5b4][cc-compare]
[cc-base-branch]: https://codecov.io/gh/kbase/data_api/branch/develop?src=pr
[cc-compare]: https://codecov.io/gh/kbase/data_api/compare/1487b6a813895fc0d7d4810149e88946da194c1d...87fc5b4fdfa1a3ed1cbb823dc5e9e128726ab383?src=pr
[cc-pull]: https://codecov.io/gh/kbase/data_api/pull/230?src=pr

The data-api is defunct at this point


[CI] Add CI tests on transformers main to catch early bugs

As per title and as discussed offline, let's run CIs on transformers main, only on push PEFT main branch in order to check bugs such as https://github.com/huggingface/peft/pull/1459 early.
IMO for that workflow, no need to make things complicated, let's just test it on a speciifc python / OS version
cc @BenjaminBossan @pacman100

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint. The docs are available until 30 days after the last update.

Thanks everyone!
@BenjaminBossan hmm not sure, as disucssed offline, maybe that has somehow to be enabled from your GH account but not sure


toggle-preview hides header info

Category

[x] fzf binary
[ ] fzf-tmux script
[ ] Key bindings
[ ] Completion
[ ] Vim
[ ] Neovim
[ ] Etc.

OS

[x] Linux
[ ] Mac OS X
[ ] Windows
[ ] Etc.

Shell

[ ] bash
[x] zsh
[ ] fish

fzf --header='foo bar baz' --preview='< {}' --bind='space:toggle-preview'

when the preview pane is toggled the header info disappears

Good catch, thanks. Fixed it.
(A workaround for the old binaries is to hit CTRL-L to redraw the screen.)


Added a GitHub Workflow to Build and Test

Issue #, if available:
Description of changes:
Added a GitHub Workflow to Build and Test
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Curious, why the need to setup node.js and .net core 3.1 setps?

There was a failing test that needed Node.JS. I retested again and didn't see the failure I did so removed that dependency.
For .net core 3.1, the test project is failing because it wants 3.1. I guess there's a dependency in there that needs it.

I only have .NET 5 installed in my WSL and I can build and test without needing .NET SDK 3.1. There is something wrong with setup.


Cannot find script list file. Please check the game folder. try to reset the game folder.

Cannot find script list file. Please check the game folder. try to reset the game folder.
what is script list file?

Is it resoved?


Deprecation fix: mktemp is deprecated

https://docs.python.org/3/library/tempfile.html#deprecated-functions-and-variables

Codecov Report

Merging #789 (5b3ad61) into master (7452dce) will not change coverage.
The diff coverage is 0.00%.

@@           Coverage Diff           @@
##           master     #789   +/-   ##
=======================================
  Coverage   77.90%   77.90%
=======================================
  Files          24       24
  Lines        5826     5826
=======================================
  Hits         4539     4539
  Misses       1287     1287

Impacted Files
Coverage Δ

spectral_cube/dask_spectral_cube.py
85.64% <0.00%> (ø)

Continue to review full report at Codecov.

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

Marked as 'draft' and may be a 'do-not-merge' b/c it appears the deprecated mktemp does something qualitatively different from mkstemp that will be hard to reproduce


Is LOG_AGGREGATOR_MISSES configuration directive used anywhere in code?

Hi,
I've just started to use carbon-aggregator and it logs huge amount of metrics not matching aggregation rules. I'd like to switch this extensive logging off but LOG_AGGREGATOR_MISSES directive does not work apparently.
After simple search through code, it looks there is only assignment of default value but there is not any code block to process this setting.
Is it intentional? Thank you, .zp.

It was introduced here but then receiver.py was removed as part of this megacarbon refactor back in January. It looks like the logging bits were never recreated.
@mleinart was this intentional and we just need to clear out the remaining references to LOG_AGGREGATOR_MISSES or should that log be added back?