Allow to run as root / different user

Is there a compelling reason not to run Logstash in the container as root?
The problem is that the logstash user 999 will not be able to run most logs (like /log/syslog). I think it's better to run root in a Docker container and mount the volume as read-only as to change file permission in the host to allow a non-root docker user to read the logs.
I would suggest just skipping the gosu or add the functionality to specify a user ID to run as when starting the container (through an env variable)...

The reasoning is security.  Root in a container is equal to root on the host.  If there was a vulnerability that allowed a breakout from the docker "container" that would give an attacker root access to the host.  There is a similar discussion to adding a way to specify the running user for elasticsearch (https://github.com/docker-library/elasticsearch/pull/14).

Hm, seems partially contradictory: "root in a container is equal to root on the host" and "if there WAS a vulnerability..." ;-) I guess if that vulneratiblity isn't there, it's not at all equal, is it?
Anyway, would you be willing to support a RUN_AS_ROOT or RUN_AS env variable for those willing to accept the security risk and opt in to run as root (or another user/group)?

Isn't the docker run --user option made for this?..

"Useless" is a bit far :wink:.  We use gosu so that we can fix permissions
before we drop privileges, which is impossible with just "-u".

Is there currently a workaround or a best practice to actually just read logs on a volume that do not have read permissions set for everybody? If not, I think we definitely need a way to change the user logstash runs with, otherwise we lose the ability to perform a lot of file based use-cases without making changes to permissions on the host which is not really desirable.

@pazoozooCH, how are file permissions for logstash handled normally outside docker?  Does logstash just run as root to see all the logs?
And, yes container root does equal host root: alias sudo='docker run -it --rm -v /:/host --privileged --net=host --pid=host debian chroot /host /bin/bash'.

so that we can fix permissions

That is even more awful, btw.

@yosifkit, in this case, I'd probably add the logstash user to the adm so it could read the system logs without me having to change default permissions of Ubuntu. In this case, I'd require an option to specify a "run-as group".
Well, your example is not really that realistic. Obviously, I wouldn't just mount / into my container and run it as root. I would mount /var/log as readonly into the container and trust docker to actually run it in a container/sandbox that is not escapable...

btw, as I've indicated in https://github.com/docker-library/logstash/issues/10, $HOME for the logstash user currently stays /root, causing problems with Logstash's default settings INSIDE the container. I think the whole user management should be improved on anyway...

I found a workaround after reading the entrypoint script: give anything other than logstash as first argument to the docker run command, e.g. full path to it :)
Run as root:
$ docker run -d --name logstash logstash /opt/logstash/bin/logstash agent -e 'input { stdin { } } output { stdout { } }'
$ docker exec logstash ps aux
USER     PID
root     1

Run as user foo:
docker run -d --name logstash --user foo logstash /opt/logstash/bin/logstash agent -e 'input { stdin { } } output { stdout { } }'

Would something like https://github.com/docker-library/elasticsearch/pull/77 be helpful to allow you to specify any non-root user and group to run as, using the --user flag on docker run?  It seems like @viranch's trick would allow you to run as root.

Hi , how to run , with user logstash
input {
file{ path => "/var/log/nginx/access.log" }
}
,
even chmod 777 access.log
Thanks.

@EamonZhang, what about the permissions on the directory /var/log/nginx/?

@yosifkit  drw-rw-rw-
It say  no permissions at first, then I  change it to  drw-rw-rw- with command chmod 666 /var/log/nginx -R
It does not show permissions problem.
but can use , echo "some thing " >  /var/log/nginx/access.log . logstash is not responding.
I notice docker-entrypoint.sh change the user.
I start logstash bypass  docker-entrypoint.sh, use root user. It seems ok.

One side effect of this is that the S3 output plugin will cause the Logstash process to fail to start because during the plugin's registration phase it attempts to write a temporary file to /tmp/logstash/s3/logstash-programmatic-access-test-object-<a short uid> and the logstash user does not have permission to write to this location.  As a result one can't run a container with this image without overriding the entrypoint.

according to the 5.0/docker-entrypoint.sh, to run as root:
docker run  \
 -it --rm -v "$PWD":/config-dir \
 -v /var/log/apache2/:/var/log/apache2/ \
 logstash:5 \
+ /usr/share/logstash/bin/logstash -f /config-dir/logstash.conf
- logstash -f /config-dir/logstash.conf

@pazoozooCH @tianon looks like this could be closed too, right?

@mi-hol , didn't have time to look at it recently - I guess yes...

Right now, the easiest way to run as non-root is to use --entrypoint -- I've filed a PR to simplify this a little further (#70):
$ docker run --name logstash --user 1000:1000 --entrypoint logstash logstash:5.0 -e '...'

As noted in #70, I had to also specify --tmpfs /var/lib/logstash so that user 1000 could write to that directory in the container, but it was successful. :+1:


History of search patterns doesn't work

When searching in vim/nvim you can use <Up>/Down to select patterns from history. Looks like this functionality doesn't work in vscode-neovim.

Duplicate of #514.

Nice! Thank you!


remove two folder/path approach details from SS3 getting started guide?

From the AFS course Rick and I taught in Nov 2021, I think having different ways to run SS3 right away was too much detail for the participants. This makes me think that details about different ways to run SS3 should instead be added to the manual instead of the getting started guide. We can link to these details in the getting started guide for folks who are interested, without distracting from the goal of getting SS3 up and running using 1 workflow.
@Rick-Methot-NOAA , what do you think about this?  I can modify the ppt, too, if you think that is appropriate.

Ok.  I agree that it gets too much attention on the getting started material.
But I do not want to encourage new users to put the exe in every working folder.  Path approach seems best; and functionally equivalent to the 2 folder approach.

Yeah, that is the reason I also felt it important to include all the options for using SS3. I agree it is much better to use a two folder or path approach.
I am changing my tune, though, given how confusing it is to new users (many who are not familiar with the command line).

suggests that we may want to consider an installer for SS3.  Similar to what Neal has for SSI.

I don't think there is an installer for SSI? What would be the advantage of an installer?  (esp. if this means you need admin privileges to install?)

Yeah. You are right about that.
What I am looking for is a zip file that puts the exe into a specific folder and has a script that can be run to modify PATH to refer to that folder.

Got it, yes, I see how that could be helpful! I do like this idea. Probably worth looking into.


Use git_username, git_password arguments when running projects locally.

Codecov Report

Merging #44 into master will decrease coverage by 0.08%.
The diff coverage is 73.33%.

@@            Coverage Diff             @@
##           master      #44      +/-   ##
==========================================
- Coverage   77.04%   76.96%   -0.09%
==========================================
  Files          44       44
  Lines        2540     2548       +8
==========================================
+ Hits         1957     1961       +4
- Misses        583      587       +4

Impacted Files
Coverage Δ

mlflow/cli.py
83.33% <ø> (ø)
:arrow_up:

mlflow/utils/process.py
90.47% <100%> (+0.47%)
:arrow_up:

mlflow/projects.py
81.09% <63.63%> (-1.16%)
: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 5ad2229...81e7d5a. Read the comment docs.

LGTM

Thanks @mateiz! Merging


Fix risky unit tests

Migration to PHP Unit 5.4 and more by fixing Risky unit tests.
Possibility to use the loader defined by Zephir without any warning.
Activation of PHP Unit Coverage by adding filter section in phpunit.xml.dist
Possiblity to use phpdbg to have the coverage
Add some unit tests on ConfigException / Utils

Looks good to me

@hervems Could you please fix build?

@steffengy Could you please sort out with appveyor issue?

For appveyor build, I think the problem is that PHP_EOL is not \r\n
while the var_dump uses a correct end of line ("\r\n").
I can try to do a hack, but I can't test the result because I don't have Microsoft Visual Studio Compiler (cl.exe). Do you have any idea to have a environment in local?

@hervems How about something like this https://hub.docker.com/r/ambakshi/wine-x11-vcpython27/

You actually do not need a full visual studio since quite a while, but only a rather small part of it available here:
http://landinghub.visualstudio.com/visual-cpp-build-tools

@steffengy Could you please take a look?

All builds are ok (travis + appveyor).
By my side, I tested on Windows 7 with Visual Studio 11.

Thanks


docs: Document how URL Readers work and how to write a new one

Closes https://github.com/backstage/backstage/issues/6251
This is more of a developer documentation useful for Backstage developers.

The integrations section is intended to be basically a list of products, and how and at what levels we integrate with them. Your content should definitely not be here I'd say, but I'm not entirely sure where else.
It's kinda in the ballpark of this https://backstage.io/docs/getting-started/configure-app-with-plugins
We lack a section that's focused on "Ways that you can extend and customize your Backstage instance". It would have subsections on "Setting app icons", "Tweaking the sign-in page", "Adding URL readers",...possibly even core feature things like "Extending the set of catalog processors", "Tweaking the entity field validation rules", "Creating custom template Actions"... But sure, the latter could also go under the feature sections themselves too

I originally noticed that this content was missing after reading the External Integrations page - https://backstage.io/docs/features/software-catalog/external-integrations
That page should link to this page but as @freben  mentioned it’s not clear where it should be.

A section like the one you're suggesting @freben would be great.
Throwing "Extending Backstage" into the mix

Thanks all for suggesting where this document should be. "Integrations" does not make sense. Adding this to "Getting started" also doesn't make sense since it's "too top level" for an article like this.
I see some relevance of putting this into Plugins -> Backends and APIs for now. And +1 to the idea of "Extending and customizing Backstage" as top level section.


Shrink ScottPluts without memory overflow/Upgrading typeclasses.

sample/zip-test/Main.hs:136:32: error:
    • Return type does not match:
      	Expected "PBool" but given function returns "PInteger"
    • In the second argument of ‘($)’, namely ‘fromPFun test’
      In the expression: forAll arbitrary $ fromPFun test
      In an equation for ‘testProp7’:
          testProp7
            = forAll arbitrary $ fromPFun test
            where
                test :: Term s (PInteger :--> PInteger)
                test = plam $ id
    |
136 | testProp7 = forAll arbitrary $ fromPFun test

These type errors are sweet!


Finalisation of the data structure

The current structure can change at any time. Before merging our changes back to master, we should stabilise the data structure to prevent future changes unless it is required. It is also a good idea to keep track of the current structure in a README or somewhere. It is always fine to add new entries. However, modifying an entry will require lots of changes in the app layer. We should keep that in mind especially when app gets more complex.

[ ] #14
[ ] #12

The structure is still not finalised. I will spend some time this weekend to possibly finish this.


Enable config server to reach repository via proxy server

Ran into this while teaching a Spring Cloud class on-site with a customer that required a proxy to access the web. JGit does not support the "standard" mechanisms for this.
Reference http://stackoverflow.com/questions/16921374/jgit-proxy-configuration-in-code/17071687#17071687 for an example of how this is done. I figure we can wrap this in some nice configuration that would allow snippets in bootstrap.yml like the following:
spring.cloud.config.server.git.http.proxy.host=blah
spring.cloud.config.server.git.http.proxy.port=1234
spring.cloud.config.server.git.https.proxy.host=blah
spring.cloud.config.server.git.https.proxy.port=5678

That SO link just shows someone making a special case for github. The normal JVM convention for System properties should work unless we need special cases like this (e.g. "-DproxyHost=myproxy.com" etc.). What was the use case exactly at the customer site?

For the record I tried the config server with a proxy and it worked fine with -Dhttps.proxyHost and -Dhttps.proxyPort set (I was using squid so localhost:3128). It also works with ~/.git/config with http.proxy=localhost:3128.
I have seen people on SO having issues with NTLM but I don't really know if we can do anything about that (maybe look at Spring Kerberos for the config server somewhere). This might be helpful (a proxy proxy with NTLM): http://stackoverflow.com/questions/7734518/how-to-set-up-git-to-get-through-a-proxy

I'm considering a PR for this. Cc: @spencergibb

What does your PR do (go ahead and submit it)? Is it to do with the NTLM case?

No, it's not the NTLM case. We need to set proxy host to access a Git repository.

Can you do that with a patch to Spring Cloud? You need to set a System property?

I don't know if we can do this with a patch. I just starting thinking about it and saw this open story. But yes, it appears we'll have to set System properties.

For PCF would it be better to set the system property when you push the app? I suppose we could set a System property based on a config file (Spring environment entry), but it seems upside down.

I agree that having Spring Cloud set system properties feels awkward, if that's the only requirement for going through a proxy. My initial impression was there was something else needed, but I guess not. Your notes above said the system properties worked as desired in your tests.

Yeah. I guess it's an important enough use case that we might be able to support it via System.setProperty(), but I'm not 100% convinced yet.

I'll explore a solution in the context of pushing a PCF app. If anything obvious reveals itself as a candidate for spring cloud, then I'll follow up here. Thanks for the feedback!

This seems to be resolved meanwhile.
See http://cloud.spring.io/spring-cloud-static/Finchley.RELEASE/single/spring-cloud.html#_accessing_backends_through_a_proxy


i18n(ko-KR): update integrations-reference.mdx

Description (required)

update integrations-reference.mdx
#9240

Related issues & labels (optional)

Closes #
Suggested label:

Lunaria Status Overview
🌕 This pull request will trigger status changes.

Learn more
By default, every PR changing files present in the Lunaria configuration's files property will be considered and trigger status changes accordingly.
You can change this by adding one of the keywords present in the ignoreKeywords property in your Lunaria configuration file in the PR's title (ignoring all files) or by including a tracker directive in the merged commit's description.

Tracked Files

File
Note

ko/reference/integrations-reference.mdx
Localization changed, will be marked as complete.

Warnings reference

Icon
Description

🔄
The source for this localization has been updated since the creation of this pull request, make sure all changes in the source have been applied.

Once #10201, #10217, #10231 are merged, I expect to be able to merge this PR successfully.


Trying to filter the list causes a panic

Using F3 or F4 and trying to type any key crashes the application.

Does your list contain an instance without a name (tag)?

Should be fixed in release 0.1.4. Currently building.

Yes I had instances without names. Thanks!


Add gometalinter support

Hi @joehandzik @roclark,
I am creating this PR adding gometalinter support. There is a bunch of different Linters that you can list with gometalinter -h, and you can disable some that are maybe not relevant to you.
Travis is failing of course, but you can just analyze what you want to fix and what you would simply want to disable.
I personally think this tool is much more powerful, and offer editor integration too!

@mjtrangoni Robet and I have discussed this a few times since you submitted this PR, and we're not sure that we want to jump to this level of complexity yet. Are there particular things that any of these other linters catch that you think we're missing out on?

@joehandzik I think the default checks make sense (link), and I took the time to fix the trivial ones for you (I can rebase them all in one commit if you like it that way).
Another thing was to make gometalinter running well with TravisCI, which was not really easy, but it works like a charm now! I just had to disable two checks that took too long at Travis.
The main two things that I leave to you is to fix or disable the following ones,
>> linting code
sources/procfs.go:289::warning: cyclomatic complexity 18 of function (*lustreProcfsSource).Update() is high (> 10) (gocyclo)
sources/procfs_test.go:44::warning: cyclomatic complexity 14 of function TestGetJobStats() is high (> 10) (gocyclo)
sources/procfs.go:709::warning: cyclomatic complexity 11 of function (*lustreProcfsSource).parseFile() is high (> 10) (gocyclo)
sources/procfs.go:280:30:warning: error return value not checked (l.generateOSTMetricTemplates()) (errcheck)
sources/procfs.go:281:30:warning: error return value not checked (l.generateMDTMetricTemplates()) (errcheck)
sources/procfs.go:282:30:warning: error return value not checked (l.generateMGSMetricTemplates()) (errcheck)
sources/procfs.go:283:30:warning: error return value not checked (l.generateMDSMetricTemplates()) (errcheck)
sources/procfs.go:284:33:warning: error return value not checked (l.generateClientMetricTemplates()) (errcheck)
sources/procfs.go:285:34:warning: error return value not checked (l.generateGenericMetricTemplates()) (errcheck)
sources/procsys.go:91:25:warning: error return value not checked (l.generateLNETTemplates()) (errcheck)

gocyclo checks the Cyclomatic_complexity, and I think that this should be improved. @knweiss, do you agree with that?

errcheck shouldn`t be really important but would be also a pity to disable it.

I would guess that we would disable gocyclo for now, I don't think builds should fail because of the complexity numbers it is checking against. We can make a quick fix for all of those errcheck issues, so I'm fine with leaving that enabled (we really should check all errors).
Thank you for taking the time to make these changes! We'll figure out a merge plan today between myself and @roclark.

@joehandzik Perfect! About gocyclo, there is an option that you can increase,
--cyclo-over=10       Report functions with cyclomatic complexity over N (using gocyclo).

@mjtrangoni I believe I have fixed the errcheck issues with PR #99. Can you add the --cycle-over flag to your commit where you change the flags in the Makefile, and set it to 19 (basically, make sure we don't regress with regard to cyclomatic complexity for now)?

@joehandzik TravisCI seems to be happy now, but local is not the same for me. Look,
$ make
>> formatting code
>> linting code
lustre_exporter.go:88:8:error: assignment count mismatch (1 vs 2) (gotype)
Makefile:37: recipe for target 'gometalinter' failed
make: *** [gometalinter] Error 1

Hmm, I saw an issue like that, looks like you still have the error defined somewhere in either sources/source.go or lustre_exporter.go. Not sure why the rebase didn't completely take care of your local code...

@mjtrangoni Your code looks fine in your branch...are you sure you aren't running against something old, or maybe against your fork's master instead of the branch you rebased?

Gonna merge, if we actually have problems after this we'll resolve.

Ok, Thanks! I will be checking this later directly from master

A build worked for me without issue just now from master, so I expect everything to work fine on your end too.

@joehandzik Just for the records, and as I had to do with Travis, this is a gotype issue.
You have to do go test -i, and gotype works again.


Requested frame rate(30) is not supported: 5,10,15,24 start failed - 19

Requested frame rate(30) is not supported: 5,10,15,24
start failed - 19
samsung i9104 Galaxy S II Plus
Os: Android 4.2.2
api level: 17
screen: 480 x 800 px |hdpi|4.3"
I got this error when testing on this device. The back camera worked fine but the front camera
crashes with this error. Can this be resolved by setting a lower standard frame rate? Or wil give this errors on other devices.
Yilzer

You can pretty easily change that setting, but I changed the default.

https://github.com/afollestad/material-camera/releases/tag/0.2.4


Softcasting no annotation

:round_pushpin: Add acceptance test 106 showing issue with if/is implicit casting.

:round_pushpin: Thread down if/is pattern assignment type down to code-generation.
This isn't sufficient however, as the 'assignment' helper handling
code generation doesn't perform any check when patterns are vars. This
is curious, and need to be investigated further.

no annotation is not neccessarily the correct phrasing I think. You must always provide an annotation but you can optionally provide a pattern. Unless I misunderstand what this refers to :)

No pattern* I meant, the issue is actually happening when there's only an annotation


add event bus example to help v1 expectations

This adds an example of how to use similar behavior like with
$broadcast / $dispatch in v1. The motivation comes from not using
vuex immediately for shared state components.
Not sure whether this would need to go rather into a guide, but I wanted to start a discussion about this globally, as I am not the biggest fan of the vuex pattern. This would ease my expectations as a developer coming from v1

@eljefedelrodeodeljefe Have you seen this section in the migration guide? Is that the kind of thing you're looking for?

Yes. And I found it a little confusing, because of this eventhub object. In a template file and browserify based workflow I wouldn't really know how to get a reference to the object. I think deprecating dispatch and broadcast was a right decision, but there should be an equal alternative that is evented - speaking as a backend developer.

Of course one could just require the eventhub everywhere, but that seems a little steep and not so lightweight, no?

If you're using a module system, you don't actually have to do anything special to get a reference to the object - just export it from a file just as with any other module:
module.exports = new Vue()
// OR
export default new Vue()

Doing this isn't really "heavy" unless you consider module systems themselves heavy. If you prefer to access the event hub globally on any component instance though, you can also do this:
Vue.prototype.$eventHub = new Vue()

Then you can access
this.$eventHub.on

No, sure, but I meant that the Vue instance just for being an event hub is heavy, considering that the instance you are using has this functionality already built-in. It's just extremely bad style.

Vue instances are actually very cheap if you're worried about performance.

No, I am worried about style and what documentation suggests and what it not suggests. As is it's promoting vuex for shared state management with a very bad style alternative of using an event hub via an object that doesn't have this as sole purpose.

What specifically are you worried about with the alternative mentioned in the guide? Having a separate event hub has distinct advantages, most notably that you can use it across many root Vue instances or even it outside of components.

It's not really modular. When I wanted to do something like that in backend development, I would either require a global EE or extend from an EE.
It doesn't follow do one thing and do it well, as Vue for sure is no EventEmitter and can easily see API changes, when the global dev scope requires it, as just done with Vue 2.
it's just plain bad bad style.

Not here to argue about good coding practices, especially since I find fronted dev and frameworks peculiar. Closing.

Just to say I too would be really glad about a clear best practice on this. Find it hard to transition from $dispatch and $broadcast to this new system.

@alberto2000 The best practice is laid out here: use Vuex. In cases where that's too difficult a transition, the global event bus example should a fairly painless process, since the migration helper catches 100% of instances and much of it can be handled with find-and-replace.

@chrisvfritz thanks. only problem I have is I have multiple instances of the parent component and when I emit a notification from a child, all those instances register it - instead of just the one that's parent to the child - earlier $dispatch would be perfect here

@alberto2000 Component's custom events allow you to do the same thing, but more explicitly.

@chrisvfritz how can I communicate from a child only to its own parent but not to all other instances of that same parent component? They all are listening to the same event and will catch it too, right?

Nope. 🙂  Try it.

@chrisvfritz I did and that's what happened. I have four parent components, each has a child. Now, one child component emits an event and I'd like it to be only heard by its own parent - the problem though is, that all other parents hear the event as well. $dispatch would only send the event up the tree along to the "real" parent...

Let's open a thread on the forum then. Post a code example and ping me, then it should be easier to see what's going wrong in your case.


Integrate into bids-validator

BrainVision files are part of the EEG extension for the Brain Imaging Data Structure (BIDS).
To Do before integration:

[ ] #6
[ ] #9
[ ] #14

It would be good to use this tool as a validation for BV files, see: https://github.com/bids-standard/bids-validator/issues/475

see: https://github.com/bids-standard/bids-validator/pull/701

it's done! ... has been merged. in PR 701 as linked above.


A simple app for real-time chat

A simple app for real time chat with a group of users and single users
With caching and realtime features to well learn that supabase can help us.

There is an official quickstart guide: https://supabase.io/docs/guides/with-flutter

Posting a recent article on how to create a simple chat application using Flutter and Supabase. It does not have any caching mechanisms though.
https://supabase.com/blog/2022/06/30/flutter-tutorial-building-a-chat-app

Caching is a flutter-specific thing that the dev would need to implement himself. I don't see a reason to implement cache in realtime.
Can this be closed?

Yup, makes sense! Let's close this one!


Better code coverage for PID optimizer

Codecov Report

Merging #68 into master will increase coverage by 0.77%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master      #68      +/-   ##
==========================================
+ Coverage   89.14%   89.92%   +0.77%
==========================================
  Files          13       13
  Lines         645      645
  Branches      147      147
==========================================
+ Hits          575      580       +5
+ Misses         36       34       -2
+ Partials       34       31       -3

Impacted Files
Coverage Δ

torch_optimizer/pid.py
89.58% <100%> (+8.33%)
:arrow_up:

torch_optimizer/sgdw.py
77.55% <0%> (-6.13%)
:arrow_down:

torch_optimizer/accsgd.py
95% <0%> (+10%)
:arrow_up:

Continue to review full report at Codecov.

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


patch vulnerable dependencies

I am not sure if this by design. I found 61 low vulnerabilities with npm audit. All tests passed please see below.
found 61 low severity vulnerabilities in 869 scanned packages
  run `npm audit fix` to fix 61 of them.
➜  juice-shop-ctf git:(master) npm audit fix
added 869 packages from 538 contributors in 10.386s

44 packages are looking for funding
  run `npm fund` for details

fixed 61 of 61 vulnerabilities in 869 scanned packages

Test results
 72 passing (3s)

-------------------------|---------|----------|---------|---------|-------------------
File                     | % Stmts | % Branch | % Funcs | % Lines | Uncovered Line #s
-------------------------|---------|----------|---------|---------|-------------------
All files                |    99.3 |    88.57 |     100 |   99.29 |
 lib                     |     100 |       95 |     100 |     100 |
  calculateHintCost.js   |     100 |      100 |     100 |     100 |
  calculateScore.js      |     100 |      100 |     100 |     100 |
  fetchChallenges.js     |     100 |      100 |     100 |     100 |
  fetchCountryMapping.js |     100 |      100 |     100 |     100 |
  fetchSecretKey.js      |     100 |      100 |     100 |     100 |
  hmac.js                |     100 |      100 |     100 |     100 |
  options.js             |     100 |      100 |     100 |     100 |
  readConfigStream.js    |     100 |       75 |     100 |     100 | 30
  url.js                 |     100 |      100 |     100 |     100 |
  writeToCtfdZip.js      |     100 |      100 |     100 |     100 |
  writeToFbctfJson.js    |     100 |      100 |     100 |     100 |
  writeToRtbXml.js       |     100 |      100 |     100 |     100 |
 lib/generators          |   98.87 |       86 |     100 |   98.84 |
  ctfd.js                |     100 |       90 |     100 |     100 | 69
  fbctf.js               |   97.37 |     87.5 |     100 |   97.22 | 27
  rtb.js                 |   99.12 |    84.38 |     100 |    99.1 | 26
-------------------------|---------|----------|---------|---------|-------------------

Coverage remained the same at 95.442% when pulling dba99a7bcd46ec89f00a2cbc17d8575f776f65eb on Youssef-kaiboussi:patch_vulnerable_dependencies into f10daf969965b670b23cd905e413cd3dd55d2325 on bkimminich:master.

Thanks, but a general update of all dependencies already addressed this. Will be released as v8.1.1 shortly.


Getting error while compiling

I get this error while building:
   Compiling xtensa-lx-rt v0.15.0
error: invalid register name
   --> /Users/shiv/.cargo/git/checkouts/esp-wifi-836f3b2af57fa847/c792679/esp-wifi/src/timer_esp32.rs:209:27
    |
209 |         core::arch::asm!("wsr.226  {0}", in(reg) intr, options(nostack)); // 226 = "intset"
    |                           ^
    |
note: instantiated into assembly here
   --> <inline asm>:1:2
    |
1   |     wsr.226  a8
    |     ^

error: could not compile `esp-wifi` (lib) due to 1 previous error

@kokroo I have upgraded all dependencies to latest, could you try compiling from the latest version of the main branch?


set the log is applied when the exception occurred during applying

if an exception occurred during applying, the log would not be applied forever, and the server would be blocked.
this pr is to try to fix the problem.

log.setApplied(true); is always invoked after log.setException(e); except

maybe it is better to add log.setApplied(true); there instead of adding unnecessary synchronized.

log.setApplied(true); is always invoked after log.setException(e); except

maybe it is better to add log.setApplied(true); there instead of adding unnecessary synchronized.

log.setApplied(true); is always invoked after log.setException(e); except

maybe it is better to add log.setApplied(true); there instead of adding unnecessary synchronized.

ok, I will add log.setApplied(true) here

log.setApplied(true); is always invoked after log.setException(e); except

maybe it is better to add log.setApplied(true); there instead of adding unnecessary synchronized.

ok, I will add log.setApplied(true) here

There are failing tests, please take a look.

There are failing tests, please take a look.

There are failing tests, please take a look.

have fixed

There are failing tests, please take a look.

have fixed


[Applications] SP does not receive new applications

Environment: macOS Big Sur 11.5.1; Chrome version 99.0.4844.51.
Reproducible: always.
Build found: gcp-0.0.94
Preconditions

Log in as parent
Log in as SP with workshop

Steps to reproduce

Click on "Детальніше" link of workshop
Click on "Подати заяву"
Choose child and tick checkboxes
Click on Apply button
Log in as SP with chosen workshop
Click on received notification
Observe that new application is not received
Log in as parent
Click on "Детальніше" link of the same workshop
Choose the same child and make sure that application was send because user can't apply twice on the same workshop

Actual result
Application is send. SP received the notification but doesn't get new application
https://user-images.githubusercontent.com/97882565/177154463-ae9219a7-01be-4d94-8e8d-33ba1d4b88d2.mov
In the Parent cabinet application is also not displayed

Expected result
SP and Parent should see all received applications
User story and test case links
User story https://github.com/ita-social-projects/OoS-Backend/issues/193
Test case
Labels to be added
"Bug", Priority ("pri: High"), Severity ("severity: Critical").

fixed!


skhd -o doesn't print keycodes

When I type skhd -o Terminal return the char pressed on the keyboard as it is. E.g. If you hit 'c', it return 'c' again instead of 0x... something.
My setup: latest Ventura OS, latest brew, Macbook M2

...wow. Thats super odd. I'm on close enough of the same system to you and it works for me.
Can you post a screen shot(s)?

Here they are. It continuously prints the key in latin.

Yes! exactly it is :)
I've given all permissions and been using with Yabai for months. It's functioning as expected, btw. I can use my custom scripts and automation stuff using shortcuts via skhd. But the skhd -o it stopped working suddenly.
...out.log is empty and ...err.log says "could not locate the window to act on!" I guess it is related to Yabai.
I have tried skhd --stop-service & skhd --start-service. No success.

Hmm, would yabai output to skhd log?
Can you post your skhdrc?

Last night I executed brew update; brew upgrade. I was going to cat the skhdrc to post here. I've checked skhd -o one last time whether it works or not! Well, good news. It is working now.

I don't know why, but after the brew stuff Yabai and skhd asked for permission. I have two Yabai app seems running. But everything is working as expected right now.

In short, I guess updating brew, restart computer and enable-disable skhd steps fix the issue. Thanks for your support @tjex, btw


Added wrapper class name to documentation

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


Added support for getting email & more

I added support to get the user email if you have the right permissions with include_email  parameter.
Also added support for a custom SFSafariViewControllerDelegate  in case you don't what your view controller to handle it if this is not set it uses the view controller as it was before.
Removed the #available(iOS 9.0, *) because the minimum deploy target is already iOS9 so I don't think there is a need to check for it.
Updated the prevent animation to match the one used by other social logins (Facebook and Google)
If you think that some of these do not make sense I can remove them.

LGTM 👍


Bug? in url.class.php - checkfilters() - filterFullwoSlash

Describe your problem
I did some code review to learn what happens and found an issue I think, what may cause errors.
I'm no pro php developer, so may be I'm false with that.
Please check the code.
Actual behavior
url.class.php
in checkfilters()
		// $filterFullwoSlash = '/base_url/category'
		$filterFullwoSlash = ltrim($filterURIwoSlash, '/');
		$filterFullwoSlash = HTML_PATH_ROOT.$filterURIwoSlash;

The third line overwrites filterFullwoSlash from second without the reuse of the trimmed var.
Shouldn't it be so: (last line)
// $filterFullwoSlash = '/base_url/category'
$filterFullwoSlash = ltrim($filterURIwoSlash, '/');
$filterFullwoSlash = HTML_PATH_ROOT.$filterFullwoSlash;
Steps to reproduce the problem
Look at the code above.
Bludit version
3.7.1

Hi,
even worst, the variable is defined and is not used.
Sometime I check my code and I don't understand what I did, maybe I was drunk :P
Regards

I know the feeling, although I'm hoping you'll steer clear of Bludit development when drunk ;-)

I removed the lines.
Regards


Custom Debilities

In GitLab by @1augustbebel3 on Mar 15, 2021, 21:42
An option to change both debility names and the effects they take on their respective abilities scores (this also includes applying Advantage/Disadvantage from another Issue).

In GitLab by @julien1205 on Apr 30, 2023, 15:33
Custom debilities are available in the system options.
You can also toggle advantage/disadvantage on debilities there.
I think the ticket can be closed.


Deployment and hosting of V2 as a separate Beta (standalone) application

URL: play.beta.onflow.org

@sideninja if we decide to use the staging env, what do we need to change the domain from play.staging.onflow.org to play.beta.onflow.org ?

@fotescodev I think we would just have to add this domain to the FE in Vercel and also add it to the allowed origins on the BE deployment.

@DylanTinianov sounds like a plan! Let's do it earlier than later.

Added play.beta.onflow.org to allowed origins for staging backend

Created SRE ticket to create a new namespace, node pool, domain, and postgres database for the new beta deployment. We can then target this deployment in the k8 manifests and deploy our v2 beta to it.

Released https://beta.play.flow.com


SDK: Make import errors more clear for scene developers

Currently the DCL SDK is quite picky with imports. They have to be in a certain way for the scene to work as expected.
We are having many issues where VS Code and other IDEs will say that everything is alright, and the scene will compile, but then we will have missing modules while running:

Solving this requires profound changes in SDK compiler and module system. But since there are workarounds, we believe it is better to tackle the issue later when we revamp the whole SDK.
As a temporary solution, we should improve errors in the console when these happen. We have the information to detect which of the dependencies are truly missing (have not been compiled correctly). Instead of showing all the modules that couldn't be loaded, we should only show the ones that where required but couldn't be found, and then suggest possible fixes (change to /index import, ensure external dependency is esm compatible, etc)

Yes!
I can't count how many times I ran into this, and how much time it made me waste each time till I found the root of the problem.
It doesn't happen only with external libraries, also with imports of files in your own scenes, and it also reports it just as cryptically, listing a long bunch of files instead of being specific to where the problem is.


InstagramRipper now send ig_pr=1 cookie when getting next page

Category
This change is exactly one of the following (please change [ ] to [x]) to indicate which:

[X] a bug fix (Fix #500)

Description
The ripper now send the cookie ig_pr=1 when getting the next page
Testing
Required verification:

[x] I've verified that there are no regressions in mvn test (there are no new failures or errors).
[x] I've verified that this change works as intended.

[x] Downloads all relevant content.
[x] Downloads content from multiple pages (as necessary or appropriate).
[x] Saves content at reasonable file names (e.g. page titles or content IDs) to help easily browse downloaded content.

[x] I've verified that this change did not break existing functionality (especially in the Ripper I modified).

Optional but recommended:

[ ] I've added a unit test to cover my change.

Coverage decreased (-0.008%) to 32.325% when pulling 7a1d6263b175b70fa53fa525a21de6077b2c38d8 on cyian-1756:ig-nextpage into 24f07523086414256400f6b41af7f58350ed996b on RipMeApp:master.

Does this still work?
I just got this running with my NodeJS library and while I was testing it, Instagram seemed to have changed things. The cookie trick worked for a few minutes but now it doesn't seem to work. In fact, the graphql endpoint doesn't even open in a browser for me. Any one else getting the same?


olive-editor: 0.1.0 -> 0.1.1

@GrahamcOfBorg build olive-editor

@GrahamcOfBorg build olive-editor

@GrahamcOfBorg build olive-editor

@luzpaz I'm thinking this should be updated according to https://github.com/NixOS/nixpkgs/issues/65399.

@aanderse that's out of my scope, mate.

@luzpaz like so.

@aanderse thanks, done in aaad52b

@GrahamcOfBorg build olive-editor

Thanks @luzpaz :taco:


Training Problems, Pre-trained Models

Hello, could you please give me a centerpoint-based camera, lidar and fusion training model? When I train the image branch, mAP==0. How should I train the image branch?

Same here with the camera stream training using pointpillars.

@rwang5203  Same here with the camera steam training using bevf_tf_xxxx.py,can you provide the pretrained? please. I can't reproduce the results.


hipchat adapter is too coupled with heroku

Suppose I want hubot to work with my existing digital ocean - I don't need a lot of the heroku specific stuff. In fact with heroku's new every free app must sleep 6 hours, deploying to heroku becomes more trouble than it is worth.

I agree that I would rather have alternate instructions on how to install it to my own server so I am not dependent on another 3rd party. Any one have any tips for installing Hubot on a local machine instead of Heroku?

You can install easily on mac with yo. There aren't really any permission issues to worry about like on linux. The only Heroku specific item I have seen is a keepalive script that you can easily uninstall with npm npm uninstall hubot-heroku-keepalive --save


Children of Event/Category should have extensionAllowed rather than # child

The Event/Category is one of the most important tags from the perspective of analysis.  I don't think we should allow extension of Event/Category itself, but rather force taggers to extend within one of the existing subcategories.
Right now each subcategory has a # {takesValue} child.  Some of them have no restrictions on what the values can be.  This makes parsing almost impossible.  A better approach is for taggers to choose to qualify by extending  (following rules for tags, making parsing possible) or grouping with an ID tag.
Example
Instead of Event/Category/Environmental/# use Event/Category/Environmental/Dirt changes to Sidewalk
This makes the tag hierarchy shorter and clearer and forces taggers to follow tag rules.

We no longer have Event/Category.  This problem has been addressed by the new design.

We no longer have Event/Category.  This problem has been addressed by the new design.


[WIP] Aether merge

Working progress of integrating Aether into our codebase and upgrading esper to use esper language plugins.
Completed:

Aether merge working

JavaScript language working in verifier.

Esper plugins loading via script tag.

Incomplete:

Esper python plugin throwing error for python, Dungeons of Kithgard: TypeError: class constructors must be invoked with |new|.
Aether tests must run through karma.

Slowly trying to move in tests and fix errors as they present themselves.
Moved aether_spec into the test folder. Needed to include esper.moden.js in the karma config to fix esper.plugin is not a function errors.
Now I started working on moving constructor_spec.coffee into the test folder. When running via localhost:3000/test there is this concerning error:
JSHint died with error TypeError: "_.includes is not a function"
_.includes is a lodash 4 method. I think this may be the inverse of the lodash silently upgrading to version 4 when we require aether.coffee instead of the build artifact.

Progress update.
JsHint has been disabled as it breaks everything and isn't critical.
There is a cryptic error that is caused in the python plugin for the python tests. This error is a mismatch of the plugin modern version to the engine modern version.
It can be fixed when python-modern plugin is loaded with esper.modern. By default the python plugin was not the modern version.
TODO:
Thus the esper language loading system has to be updated to load the language plugins based on what esper is loaded.

Language plugins load correctly based on the browser.
I tested intro:37 and course-2:72 in the verifier for both python and javascript and they passed.
The tests that came with the merge are still partially broken. The errors that esper provides is overwriting some of our aether hacked errors and thus breaking tests.
Next steps:
Find out why game dev is throwing this error:
|Poseidon's Lana| Non-UserCodeError: TypeError: match.score is not a function
TypeError: match.score is not a function
    at Thang.PropertyErrorHelper.getScoreMatch (eval at module.exports.World.loadClassFromCode (webpack-internal:///48), <anonymous>:122:26)
    at Thang.PropertyErrorHelper.checkForProbableError (eval at module.exports.World.loadClassFromCode (webpack-internal:///48), <anonymous>:79:19)
    at Object.set (eval at module.exports.World.loadClassFromCode (webpack-internal:///48), <anonymous>:24:26)
    at Proxy.Moves.calculateRollingResistance (eval at module.exports.World.loadClassFromCode (webpack-internal:///48), <anonymous>:324:42)
    at Movement.updateMotion (eval at module.exports.World.loadClassFromCode (webpack-internal:///48), <anonymous>:77:17)
    at Movement.update (eval at module.exports.World.loadClassFromCode (webpack-internal:///48), <anonymous>:36:14)
    at WorldFrame.module.exports.WorldFrame.getNextFrame (webpack-internal:///39:28:27)
    at World.module.exports.World.getFrame (webpack-internal:///48:125:38)
    at World.module.exports.World.loadFrames (webpack-internal:///48:256:14)
    at runWorld (http://localhost:3000/javascripts/workers/worker_world.js:422:14)
    at http://localhost:3000/javascripts/workers/worker_world.js:577:24

Found out that match.score was an error due to a library that we expected to mutate the string prototype.
This was resolved in this commit c8c0f3c.


Extend TimeSeriesImputer to handle multiple series

Pull Request Description
Extend TimeSeriesImputer to handle multiple series

After creating the pull request: in order to pass the release_notes_updated check you will need to update the "Future Release" section of docs/source/release_notes.rst to include this pull request by adding :pr:123.

No linked issues found. Please add the corresponding issues in the pull request description.  Use GitHub automation to close the issue when a PR is merged


Add NIF to ClientInfo

This is specifically for one of our Portugese clients, I don't know
enough about tax systems to generalise this addition to commit back
upstream.

Thanks for your PR. Adding a new parameter to ClientInfo seems not a good solution . I am planning to refactor this package make it accept user custom fields, so we can add any custom fields we like next time.

Apologies @zhangshine, I did not mean to create this PR here.    It would be great if we could specify custom fields as some clients have different requirements that need to exist on the invoice.
Anyway, thank you for your great work -- this tool works really well for me and saved me having to understand how ReportLab works!  :)
--Matt


Scene/level2

ground hole filling
added enemy
added house
added vertical wooden platform

cc: @CookieJari
thanks

Thanks Asher!


YT-DLG Information Display Issue

[x] I think my problem is NOT with youtube-dlp
[x] I've verified and i assure that I'm running yt-dlg 1.8.3
[x] I assure that i am using the latest version of youtube-dlp
[x] Searched bugtracker
[x] I've read the FAQs file

What is the purpose of your issue?

[x] Bug report
[ ] Feature request (request for a new functionality)
[ ] Question
[ ] Other

Please remove any sections between (---) if they are not related to your issue

Bug report
If the problem occurs when downloading a URL please provide the full verbose output as follows:

Restart yt-dlg
Go to Options > Extra tab
Enable Debug youtube-dl
Go to Options > Advanced tab and Clear your log content
Try to download the URL
Copy the whole log content and insert it between the ``` part below

I edited my account name out of the logs, hope that's alright
Youtube Link Log (yt-dlp 2022.10.04)
2022-10-05 12:54:29,943-DEBUG-Worker_1-[debug] Command-line config: ['--newline', '-i', '-o', 'C:\\Users\\ACCOUNT\\Desktop\\Youtube-DL\\#\\%(title)s.%(ext)s', '-v', '--ignore-config', '--hls-prefer-native', '--all-subs', '--embed-subs', 'https://youtu.be/u7NQ8g0JLXk']
2022-10-05 12:54:29,943-DEBUG-Worker_1-[debug] Encodings: locale cp1252, fs utf-8, pref cp1252, out cp1252 (No ANSI), error cp1252 (No ANSI), screen cp1252 (No ANSI)
2022-10-05 12:54:29,943-DEBUG-Worker_1-[debug] yt-dlp version 2022.10.04 [4e0511f] (win32_exe)
2022-10-05 12:54:29,943-DEBUG-Worker_1-[debug] Python 3.8.10 (CPython 64bit) - Windows-10-10.0.19044-SP0
2022-10-05 12:54:29,943-DEBUG-Worker_1-[debug] Checking exe version: ffmpeg -bsfs
2022-10-05 12:54:29,943-DEBUG-Worker_1-[debug] Checking exe version: ffprobe -bsfs
2022-10-05 12:54:29,943-DEBUG-Worker_1-[debug] exe versions: ffmpeg N-108492-gb92e14147f-20221004 (setts), ffprobe N-108492-gb92e14147f-20221004
2022-10-05 12:54:29,943-DEBUG-Worker_1-[debug] Optional libraries: Cryptodome-3.15.0, brotli-1.0.9, certifi-2022.09.24, mutagen-1.45.1, sqlite3-2.6.0, websockets-10.3
2022-10-05 12:54:29,944-DEBUG-Worker_1-[debug] Proxy map: {}
2022-10-05 12:54:29,944-DEBUG-Worker_1-[debug] Loaded 1690 extractors
2022-10-05 12:54:29,944-DEBUG-Worker_1-[debug] [youtube] Extracting URL: https://youtu.be/u7NQ8g0JLXk
2022-10-05 12:54:29,944-DEBUG-Worker_1-[debug] Sort order given by extractor: quality, res, fps, hdr:12, source, vcodec:vp9.2, channels, acodec, lang, proto
2022-10-05 12:54:29,944-DEBUG-Worker_1-[debug] Formats sorted by: hasvid, ie_pref, quality, res, fps, hdr:12(7), source, vcodec:vp9.2(10), channels, acodec, lang, proto, filesize, fs_approx, tbr, vbr, abr, asr, vext, aext, hasaud, id
2022-10-05 12:54:29,944-DEBUG-Worker_1-[debug] Default format spec: bestvideo*+bestaudio/best
2022-10-05 12:54:29,944-DEBUG-Worker_1-[debug] Invoking dashsegments downloader on "https://manifest.googlevideo.com/api/manifest/dash/expire/1665010112/ei/YLU9Y7C_Ao3JhgaJp4SgAg/ip/<IP_ADDRESS>/id/bbb350f20d092d79/source/youtube/requiressl/yes/playback_host/rr1---sn-ab5sznz6.googlevideo.com/mh/lu/mm/31%2C29/mn/sn-ab5sznz6%2Csn-ab5l6nrd/ms/au%2Crdu/mv/m/mvi/1/pl/24/hfr/all/as/fmp4_audio_clear%2Cwebm_audio_clear%2Cwebm2_audio_clear%2Cfmp4_sd_hd_clear%2Cwebm2_sd_hd_clear/initcwndbps/213750/vprv/1/mt/1664988067/fvip/2/keepalive/yes/fexp/24001373%2C24007246/itag/0/sparams/expire%2Cei%2Cip%2Cid%2Csource%2Crequiressl%2Chfr%2Cas%2Cvprv%2Citag/sig/AOq0QJ8wRAIgAKWuk_0EFEjPyqQBltuzV4lt9l607qghAYjScxKC0B0CIAcwkmgs-e-U5mXqHmjQh_99HAycxeRg57THAiRnq6uU/lsparams/playback_host%2Cmh%2Cmm%2Cmn%2Cms%2Cmv%2Cmvi%2Cpl%2Cinitcwndbps/lsig/AG3C_xAwRQIhAIbbeuF_MwsTCA-MmJAWnYA5Zpo0sO0pGYPN35Sy8gsjAiAn11F4HKswU6xqurP3yT8msw_TM0G0K2Vvg4kRRJaXSw%3D%3D"
2022-10-05 12:54:29,944-DEBUG-Worker_1-[debug] File locking is not supported. Proceeding without locking
2022-10-05 12:54:29,944-DEBUG-Worker_1-[debug] Invoking http downloader on "https://rr1---sn-ab5sznz6.googlevideo.com/videoplayback?expire=1665010112&ei=YLU9Y5_rI8iL_9EPoMGqmA8&ip=<IP_ADDRESS>&id=o-ACPJTfeBj4XnFKqh_y3_JExX5sMxnKdb9izLgDxV2ABm&itag=251&source=youtube&requiressl=yes&mh=lu&mm=31%2C29&mn=sn-ab5sznz6%2Csn-ab5l6nrd&ms=au%2Crdu&mv=m&mvi=1&pl=24&initcwndbps=213750&spc=yR2vpw9ATvQg4TPiYY6EDGGTZxmz_Oc&vprv=1&svpuc=1&mime=audio%2Fwebm&gir=yes&clen=28308010&otfp=1&dur=1950.501&lmt=1596654620832365&mt=1664988067&fvip=2&keepalive=yes&fexp=24001373%2C24007246&c=ANDROID&txp=6211222&sparams=expire%2Cei%2Cip%2Cid%2Citag%2Csource%2Crequiressl%2Cspc%2Cvprv%2Csvpuc%2Cmime%2Cgir%2Cclen%2Cotfp%2Cdur%2Clmt&sig=AOq0QJ8wRQIhAMl4i2RnH11E3Ws7DPmtnEYh89MR1d2XAN2WERgLBenbAiBv9Fkb6_YUsGFEoM9bBvur0tjmTpIpmXA8363X4SrHVw%3D%3D&lsparams=mh%2Cmm%2Cmn%2Cms%2Cmv%2Cmvi%2Cpl%2Cinitcwndbps&lsig=AG3C_xAwRgIhAJ3vpRIPiy6sFgDGMK2HAlJNIwuDfsNnnjdh2MW7Po1DAiEA9VtrH478aPNYQn9ghqKvPvFRKRb7X3ZflUijZxx9zWs%3D"
2022-10-05 12:54:29,944-DEBUG-Worker_1-[debug] ffmpeg command line: ffmpeg -y -loglevel "repeat+info" -i "file:C:\Users\ACCOUNT\Desktop\Youtube-DL\#\Review Dragon Age Awakening Part 4.f247.webm" -i "file:C:\Users\ACCOUNT\Desktop\Youtube-DL\#\Review Dragon Age Awakening Part 4.f251.webm" -c copy -map "0:v:0" -map "1:a:0" -movflags "+faststart" "file:C:\Users\ACCOUNT\Desktop\Youtube-DL\#\Review Dragon Age Awakening Part 4.temp.webm"

Dailymotion Link log (yt-dlp 2022.10.04)
2022-10-05 14:11:28,566-DEBUG-Worker_1-[debug] Command-line config: ['--newline', '-i', '-o', 'C:\\Users\\ACCOUNT\\Desktop\\Youtube-DL\\#\\%(title)s.%(ext)s', '-v', '--ignore-config', '--hls-prefer-native', '--all-subs', '--embed-subs', 'https://www.dailymotion.com/video/x8bp4ei']
2022-10-05 14:11:28,567-DEBUG-Worker_1-[debug] Encodings: locale cp1252, fs utf-8, pref cp1252, out cp1252 (No ANSI), error cp1252 (No ANSI), screen cp1252 (No ANSI)
2022-10-05 14:11:28,567-DEBUG-Worker_1-[debug] yt-dlp version 2022.10.04 [4e0511f] (win32_exe)
2022-10-05 14:11:28,567-DEBUG-Worker_1-[debug] Python 3.8.10 (CPython 64bit) - Windows-10-10.0.19044-SP0
2022-10-05 14:11:28,567-DEBUG-Worker_1-[debug] Checking exe version: ffmpeg -bsfs
2022-10-05 14:11:28,567-DEBUG-Worker_1-[debug] Checking exe version: ffprobe -bsfs
2022-10-05 14:11:28,567-DEBUG-Worker_1-[debug] exe versions: ffmpeg N-108492-gb92e14147f-20221004 (setts), ffprobe N-108492-gb92e14147f-20221004
2022-10-05 14:11:28,567-DEBUG-Worker_1-[debug] Optional libraries: Cryptodome-3.15.0, brotli-1.0.9, certifi-2022.09.24, mutagen-1.45.1, sqlite3-2.6.0, websockets-10.3
2022-10-05 14:11:28,567-DEBUG-Worker_1-[debug] Proxy map: {}
2022-10-05 14:11:28,567-DEBUG-Worker_1-[debug] Loaded 1690 extractors
2022-10-05 14:11:28,567-DEBUG-Worker_1-[debug] [dailymotion] Extracting URL: https://www.dailymotion.com/video/x8bp4ei
2022-10-05 14:11:28,567-DEBUG-Worker_1-[debug] Formats sorted by: hasvid, ie_pref, lang, quality, res, fps, hdr:12(7), vcodec:vp9.2(10), channels, acodec, filesize, fs_approx, tbr, vbr, abr, asr, proto, vext, aext, hasaud, source, id
2022-10-05 14:11:28,567-DEBUG-Worker_1-[debug] Default format spec: bestvideo*+bestaudio/best
2022-10-05 14:11:28,568-DEBUG-Worker_1-[debug] Invoking http downloader on "https://proxy-34.sv4.dailymotion.com/sec(NxIh-Zt7tjvlaP5FijOgbHzuLQLMyvcCe9GXMrLy8ajsGURvzvICcd5aTv88bupXxB3gw3ZGiH337_BDIYIl3g)/video/092/773/503377290_mp4_h264_aac_fhd.mp4"
2022-10-05 14:11:28,568-DEBUG-Worker_1-[debug] File locking is not supported. Proceeding without locking

What operating system do you use ?
Windows 10 Home
List of actions to perform to reproduce the problem:

Make sure to download and use the edited FFMPEG version that YT-DLP recommends using with its program (https://github.com/yt-dlp/FFmpeg-Builds) The one I used was (2022-10-04 13:16)
Open up YT-DLG
Add a Youtube link to the program
Proceed to download the videos as normal and view the "Size", "ETA", and "Speed" sections of the program

What is the expected behaviour ?
YT-DLG gives an estimate for the "Size", "ETA", and "Speed" sections during the whole download process.
What happens instead ?
YT_DLG only gives a proper estimate for the "Size", "ETA", and "Speed" sections when it reaches the final portion of the download, namely the audio sections.
While downloading the rest, the sections show these indicators:
"Size" = ~
"ETA" = ETA
"Speed" = at

I have recently updated to the newest YT-DLP (yt-dlp 2022.10.04) and began downloading some videos. I noticed after a little bit that the "Size", "ETA", and "Speed" sections were, for some reason, giving strange indicators for their respective outputs. "Size" was just a ~, "ETA" just showed ETA, and "Speed" gave a at. This lasted until the video was almost done and going through the process of downloading the audio for the video.
Given this wasn't the correct output, I decided to go and download the same video with the newest and previously newest version of YT-DLP ( yt-dlp 2022.09.01) to check if this was an issue I didn't notice with the older version. I think discovered that this was an issue with that version as well. Then I figured I'd try to find a version that didn't have the issue, but each older version (some of which I know for 100% fact didn't have this issue) also had the same problem. Due to this I ruled out the possibility it was simply the newer version of the program causing these issues. This became even more complicated when I then decided to test the newest YT-DLP on a Dailymotion video just to make sure every link had the same issue. I figured it would give the same error, but instead all the numbers appeared fine from start to finish.
After all this testing, I believe the issue may in fact be the edited FFMPEG version that YT-DLP suggests to use with the program. My hypothesis is that when the FFMPEG program is called upon to do more complicated process, like downloading .webm, it doesn't properly send the info that YT-DLG is looking for and causes issues with the displayed values as a result. However, when doing something less complicated, such a .mp4 video or audio sections of a .webm video, it is able to properly display the values YT-DLG wants because it isn't getting confused. That's probably not at all what is occurring, but it's the best guess I have given that nothing else really makes sense as older versions of YT-DLP shouldn't be having this issue suddenly and the only other thing I updated was the FFMPEG version they autobuild.
I've attached a RAR with a few images that should help clarify what I'm experiencing just in case the descriptions and logs don't make it clear.
YT-DLG Downloading Info.zip

Thanks for share the Logs and the feedbacks

Welcome, hope it helps!

You can check the commit https://github.com/oleksis/youtube-dl-gui/commit/0c7475d482e0243a2588d966f9b0645e75435d91

Sorry I didn't see your message earlier. By check, do you mean you want me to close this or test it out? If the latter, is it included with the exe now?

Please try the Last release yt-dlg v.1.8.4 the exe or msi and if all work as expected close the issue

Updated to the latest version (alongside updating YT-DLP and its custom FFMPEG to their latest versions) and it seems the videos it had a problem with before display properly now! Very good work!


Character that grows the string when lowercased.

Unicode has special rules about lowercasing characters http://www.unicode.org/Public/UNIDATA/SpecialCasing.txt and this can result in a string growing. When doing the reverse the strings don't appear to shrink (Java/Python). You can see python 3 growing the strings when lowercasing:
>>> len("İ")
1
>>> len("İ".lower())
2

Shout out to @davbo for starting this with #127


C# code clean-up

code formatting
small code optimisations

This issue can be assigned to me.

Where exactly and what exactly needs to be optimized? And in which place exactly is the formatting not satisfied? Specific items will be considered.

Let's consider one specific file (DeOldify.cs):

there are several empty lines (13 line for instance)
many xml-comments missing  keyword  (21 line for instance)
no one naming convention for methods, their parameters, variables and consts
Initialize method is very long and unreadable

there are several empty lines (13 line for instance)

If you are a little more careful, you will notice that there is one empty line between the declarations of methods, classes, structures, etc.
using System;

namespace Sample
{

  public static class Program
  {

    public static void Main()
    {
      Console.WriteLine("Hello, World!");
    }

  }

}

many xml-comments missing <return> keyword  (21 line for instance)

Is it so critical in the APP? This is an APPLICATION, not a class library.

Initialize method is very long and unreadable

This is an automatically generated method. It doesn't need to be read.

many magic numbers exist

I understand that we are talking about the same Initialize method. So these "magic" numbers are the sizes of tensors that need to be loaded from the stream. What kind of demystification do you want to see here? The same applies to the Colorize method. There, the numbers denote convolution parameters, such as stride, dilation, padding, and the number of groups. These numbers are determined by the architecture of the neural network and it is impossible in most cases to give a clear mathematical justification for why there is exactly 1 and not 2, for example. So the author of the architecture decided and it works.
I would like to emphasize, however, that we are talking about neural network code, and not about database or user interface code. There's a lot of magic here and that's fine.

Is it so critical in the APP? This is an APPLICATION, not a class library.

So why to use xml comments at all if you don't use intellisence that can help you to discover your types and type member descriptions? If you use them it's a bad practise to miss some tags.

This is an automatically generated method.

Where it is generated?


Additional '_' in protocol-spec.md

Find a additional underscore character when section Discovery Messages in protocol-spec.md

Closed via PR #1065


Add more docker compose aliases

Adds the following aliases:
alias dco='docker-compose'
alias dcr='docker-compose run'
alias dce='docker-compose exec'

And sorts the aliases similar to docker-compose help order

+1 Tested and working. @robbyrussell Could you take a look on this PR, please?

Thanks!


Test CLIs

Likely using whatever click suggests.

I am working on this. The plan is to write the tests in qiita/scripts/test/, but the problem is that there seems no easy way to import the command functions from qiita/scripts/qiita and qiita/scripts/qiita-env, unless we set qiita/scripts as a submodule instead. @ElDeveloper @antgonza @squirrelo @josenavas , do you have any ideas?

I don't think there is a big problem of setting it as a submodule. @ElDeveloper @antgonza ?

I think submodules is not a big deal but could you explain why this is the best option? BTW what about setting another job to test this https://travis-ci.org/biocore/qiita ...

another job is certainly an option, but isn't it nicer to take advantage of
click's testing facility and to avoid writing boiler plate code ourselves?
To do that, I have to do imports. I am not sure alternative way for that
besides submodules...
On Sun, Aug 23, 2015 at 6:01 PM, Antonio Gonzalez<EMAIL_ADDRESS>wrote:

I think submodules is not a big deal but could you explain why this is the
best option? BTW what about setting another job to test this
https://travis-ci.org/biocore/qiita ...
—
Reply to this email directly or view it on GitHub
https://github.com/biocore/qiita/issues/120#issuecomment-133977254.

Good point! However, I'm not sure what's the import issue (looking at http://click.pocoo.org/3/testing/), could you give an example? Thanks.

What if we put the tests in the same file than the functions are? We will not have the imports problem

The click doc examples defines interface inside test function. that's why
no imports is needed. My example is here:
https://github.com/RNAer/qiita/blob/clitest/scripts/test/test_qiita.py
On Sun, Aug 23, 2015 at 8:37 PM, Antonio Gonzalez<EMAIL_ADDRESS>wrote:

Good point! However, I'm not sure what's the import issue (looking at
http://click.pocoo.org/3/testing/), could you give an example? Thanks.
—
Reply to this email directly or view it on GitHub
https://github.com/biocore/qiita/issues/120#issuecomment-134006762.

Got it, thanks! What about following @josenavas suggestion? Have tests within scripts?

In the long since forgotten rewrite of split_libraries.py, what we did was
had the command line logic part of an API module. This worked extremely
well and easily testable. The script would just import the relevant
methods. The test harness would import the API methods cleanly since
they're already importable. This has the added advantage that the scripts
code becomes very tiny.
On Mon, Aug 24, 2015 at 7:16 AM, Antonio Gonzalez<EMAIL_ADDRESS>wrote:

Got it, thanks! What about following @josenavas
https://github.com/josenavas suggestion? Have tests within scripts?
—
Reply to this email directly or view it on GitHub
https://github.com/biocore/qiita/issues/120#issuecomment-134198144.

Relevant links below:
qiime, this is the actual "script"
cli
click_commands
test_click_commands

Thanks @wasade !
I really like that idea. @RNAer could you follow that approach?

Yeah, that's the same thing we did for Platypus:
https://github.com/biocore/Platypus-Conquistador/blob/master/scripts/platypus
As a side note, a while ago I saw that Click's documentation suggests
that scripts be "deployed" in a different way compared to the approach
we are using:
http://click.pocoo.org/5/setuptools/#scripts-in-packages
On (Aug-24-15| 8:31), Daniel McDonald wrote:

In the long since forgotten rewrite of split_libraries.py, what we did was
had the command line logic part of an API module. This worked extremely
well and easily testable. The script would just import the relevant
methods. The test harness would import the API methods cleanly since
they're already importable. This has the added advantage that the scripts
code becomes very tiny.
On Mon, Aug 24, 2015 at 7:16 AM, Antonio Gonzalez<EMAIL_ADDRESS>wrote:

Got it, thanks! What about following @josenavas
https://github.com/josenavas suggestion? Have tests within scripts?
—
Reply to this email directly or view it on GitHub
https://github.com/biocore/qiita/issues/120#issuecomment-134198144.

Reply to this email directly or view it on GitHub:
https://github.com/biocore/qiita/issues/120#issuecomment-134252232

@wasade , doesn't that still add an extra layer of code? You have a function doing real work, and then the click decorated cli, and another function in scripts dir call that cli. The last layer is not necessary if we make scripts a submodule.

What I had thought is essentially the same thing as described in the link that Yoshiki listed out.

It may well add some extra code -- it was designed to fit into the existing
approach that qiime was doing
On Mon, Aug 24, 2015 at 8:30 PM, Zech Xu<EMAIL_ADDRESS>wrote:

What I had thought is essentially the same thing as described in the link
that Yoshiki listed out.
—
Reply to this email directly or view it on GitHub
https://github.com/biocore/qiita/issues/120#issuecomment-134454531.

Closing as we are making the CLI qiita interaction bare minimum.


Remove Edit button if there is no permission

Fixes #2566
Add description here.

Codecov Report

Merging #2598 (9057690) into main (e97d7ea) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main    #2598   +/-   ##
=======================================
  Coverage   81.12%   81.12%
=======================================
  Files         640      640
  Lines       23291    23291
=======================================
  Hits        18895    18895
  Misses       4396     4396

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 e97d7ea...9057690. Read the comment docs.


Emmet work slowly with longer SASS files

Hello!
I've looking for the solution, but some of them are old and won't work.
I've try to change from Sublime Text to VS Code.
When I'm working with my project, for example Wordpress theme and I'm editing CSS file - no matter how long it is - Emmet abbrevation show and work in lightspeed.
When I'm typing m0 and hit TAB - I've got margin:0; in blink eye.
But when I'm working with SCSS file longer that 150-200 lines it's gonna be really slow.
When I type m0 or p10 I need to wait 2-3 seconds before TAB hit to work it.
Popur with suggestions show really slow. I've try to disable it - not showing of them, but it's not help with working speed.
In long HTML/PHP/JS files it's work perfectly - only problem is with SASS/LESS files.
Version: 1.41.1 (user setup)
Chrome: 76.0.3809.146
Node.js: 12.4.0
V8: 7.6.303.31-electron.0
OS: Windows_NT x64 10.0.18362
I've try to disable all extensions, I've try disable emmet new version - nothing can help.
I know I'm new in this, but SM3 work so much better, especially in this matter, but I really would like to work with VS.

Please try to profile emmet and attach it here, so we can analyze the issue, thanks.
https://github.com/Microsoft/vscode/wiki/Performance-Issues#profile-the-running-extensions.

Please try to profile emmet and attach it here, so we can analyze the issue, thanks.
https://github.com/Microsoft/vscode/wiki/Performance-Issues#profile-the-running-extensions.

Don't worry, I found solution - I just back to Sublime Text 3 and it's works great.


ValuesFrom optional field not working for a particular key

While using ValuesFrom from configmap and keeping optional: true as config, it is showing the following error:
missing key '' in ConfigMap ''

Is this expected behaviour, I am using same configmap for multiple keys. I think the optional field is working only when the configmap is not present altogether. Instead if configmap is present and the key is also not present, the optional field should be respected.
I am talking about the following piece of code
https://github.com/fluxcd/helm-controller/blob/6f0b7cdc76923e79f9472dc49c13842ef3c2c109/controllers/helmrelease_controller.go#L544-L548
Why is the optional not handled in this case?

@hiddeco @stefanprodan can you help out here? I would be happy to raise the PR, if this is how it should be. Thanks

#589

Hey @hiddeco my usecase is that, I would want to render this in GitOps rep but if this field is not present it will take the default value, but this error fails it.


onChange event

It should provide an onChange event when the user changes the page index

Any news about this?

why not use onMomentumScrollEnd?

onMomentumScrollEnd is not reliable. I've got different values for current page index.

@getnashty I wanna second @itinance ... onMomentumScrollEnd is not reliable I get several calls with random indexes by just moving normal without any weird swipes.

@getnashty @itinance so I have found the problem .. is the loadMinimal prop, if is true onMomentumScrollEnd does crazy stuff.
So I'm gonna check if I have some time these days to checkout the source if I can find the problem

Any news on this?

@pjnovas loadMinimal is only causing an issue on Android for me. iOS works fine.

I would find this useful also. I have a slideshow with pictures + video and I would like the videos to play only when one becomes active, and pause if it leaves. Currently, the videos are always playing, and if one has sound you hear it multiple times.
An event that gets fired when the swipe animation starts and ends is necessary, i think. Just like how the ListView component dispatches an onChangeVisibleRows events while you scroll
I'm not sure if I can support slideshows of videos with audio in my application. Any help?

This should definitely be a feature, any technical reason it isn't?


to_nextpoi_kqt.py

Is it here 'traj_id' should be str(traj_id)?

Yes. Thanks for pointing out the bug. And I've updated the traj_sim.py with the correct logic along with the files for NYC. You should be able to get the result with them.

I still cannot get your answer with your updated traj_sim.py file, can you provide your results for traj_sim.py for all three datasets?


DEBUG conflicts with commonly-defined macro

This: https://github.com/morganstanley/modern-cpp-kafka/blob/71c6a9e9d80efda50d935186f15cd08f5939deee/include/kafka/ClientConfig.h#L77
causes:
: error: expected unqualified-id before numeric constant
kafka/ClientConfig.h:77:34: note: in expansion of macro ‘DEBUG’
77 | static const constexpr char *DEBUG = "debug";

While, even the macro (might be from windows?) is "comonly-defined", doesn't mean it's not guilty. 😅
A workaround would be usingundef before including the ClientConfig.h.
E.g.
#ifdef DEBUG
#undef DEBUG
#endif

#include <kafka/ClientConfig.h>
...

It's not so easy - our project actually relies on this macro. This also why UPPERCASE_IDENTIFIERS should be reserved to macros only - there are just too many possible conflicts.
BTW: This is not the first time this has been reported. See: https://github.com/morganstanley/modern-cpp-kafka/issues/127

BTW: This is not the first time this has been reported. See: #127

OH, yes, it comes back to KafkaClient.h via the included headers, -- so anyway you can't get rid of the ClientConfig.h.
Maybe we should just remove the DEBUG from kafka::clients::Config.


⚠ GitLab Server has degraded performance

In a93b22c, GitLab Server (https://gitlab01.its-telekom.eu) experienced degraded performance:

HTTP code: 200
Response time: 7106 ms

Resolved: GitLab Server performance has improved in 3bd82b9.


Migrating Org-level GitHub Projects between GitHub products

Description
GEI cannot migrate Project (classic) at an organization level or ProjectV2, even with organization-wide migrations. It would be great if such migration is supported.

This is a gap that we're aware of, and it is definitely on our radar ❤ Watch this space.
For Projects V2, I have an open source project, gh migrate-project, but it is not an official GitHub-owned tool.

Hi Tim, thanks for the quick response as always! 😄

For Projects V2, I have an open source project, gh migrate-project, but it is not an official GitHub-owned tool.

Great, wasn't aware of this one. I'll try this out!


clean: true = clean: all?

You write in the section on workspaces:

When the Clean setting is true it is equivalent to specifying clean: true for every checkout step in your pipeline.

But what is clean: true ? Before, you defined clean: outputs | resources | all. Is it one of those? (maybe a predecessor?)

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

ID: 95227592-b2a9-62be-59d1-fe8c7f4eae8e
Version Independent ID: abf0c659-ce8c-b187-2784-22ddc061d69f
Content: Jobs in Azure Pipelines and TFS - Azure Pipelines
Content Source: docs/pipelines/process/phases.md
Product: devops
Technology: devops-cicd-process
GitHub Login: @juliakm
Microsoft Alias: jukullam

@ynux -- Suny, thank you for your questions.  Please consider these resources:

Azure DevOps Services
Azure DevOps on Stack Overflow

@juliakm -- Julia, please look into this issue.

@ynux My understanding is that clean: true is the equivalent of running git clean. In contrast, clean:all for a workspace deletes the Pipeline.Workspace directory before running a new job. I'll try to clarify this in our article.


Fail to get repository's package.json when default branch is neither main nor master

📌 Describe Issue
Fail to get repository's package.json when default branch is neither main nor master.
🐠 Checklists

[ ] https://github.com/Tech-Squad-Community/techsquad-community-website/tree/react/tscomm (react)
[ ] https://github.com/evollhhan/mobxplus (dev-v1)
[ ] https://github.com/msdio/stackticon (main)
[ ] https://github.com/52org/garden-of-the-heart (master)
[ ] https://github.com/g2hhh2ee/jihee-image-search-engine-project (develop)

🚴 Possible(or Suggest) solutions
Get default branch with github API, somehow

resolved through https://github.com/msdio/stackticon/pull/126


Inject errors in topology

What does this PR do?
This PR injects errors in the resource handle by the topology.
Fixes #522

Investigating strange behavior, please don't merge right now

(There is a conflict on the provider due to the UDP PR I think)

The PR has been rebased and the weird bug fixed, it's ready for a final review :ship:


Serve-dynamic Modules Middleware

One feature that separates typical Server-Side JS apps from classical scripting languages like PHP is to have a "filesystem based static file server" that can use a simple script language to create assets and documents on demand.
Therefore I would like to propose to create a "serve-dynamic" Middleware that works like "serve-static", but renders resources with JS.
This in combination with hono html Middleware can be a powerful combination to build websites and apps without the need of heavy JS frameworks (React, ...).
To avoid MIME type issues I would suggest to use a class naming convention that holds the final extension name appended by .js.
Example:

Dev registers a serve-dynamic Middleware to serve /routes/ dynamically.
User requests the file `/routes/theme.css
The server has a file /routes/theme.css.js that exports a function so render and respond /routes/theme.css
For this the server uses dynamic import() to load the JS file.

The Middleware should accept ts and js script and therefore needs to look for both files in the example above:

routes/theme.css.js
routes/theme.css.ts

For html files sometimes a folder with an /index.html file is used. Therefore requested html files need to look for following script files:

filename.html.js
filename/index.html.js
filiname.html.js
filename/index.html.ts

Currently dynamic imports are not supported by many Edge hosting platforms. I considered using a manifest.js file that contains all routes to solve it, but this has little value of creating all routes with hono router directly.
Following is an example implementations of the middleware with deno (requires a import_map.json:
import type { Context } from 'hono/context.ts'
import type { Next, MiddlewareHandler } from 'hono/hono.ts'
import { getFilePath } from 'hono/utils/filepath.ts'
import { getMimeType } from 'hono/utils/mime.ts'

export type ServeDynamicOptions = {
    root?: string
    path?: string
  }

const DEFAULT_DOCUMENT = 'index.html'

export const serveDynamic = (options: ServeDynamicOptions = { root: '' }): MiddlewareHandler => {
    return async (c: Context, next: Next) => {

        if (c.finalized) {
            await next()
            return
        }

        const url = new URL(c.req.url)

        const path = getFilePath({
            filename: options.path ?? url.pathname,
            root: options.root,
            defaultDocument: DEFAULT_DOCUMENT,
        })

        const staticPath = `../${path}`
        const dynamicPaths = [
            `../${path}.ts`,
            `../${path}.js`,
        ]

        if (path.endsWith('.html')) {
            dynamicPaths.push(
                `../${path.replace('/index.html', '.html')}.ts`,
                `../${path.replace('/index.html', '.html')}.js`,
            )
        }

        let content

        for (const dynamicPath of dynamicPaths) {
            try {
                const { default: module } = await import(dynamicPath)
                content = module(c)
            } catch (_ignore) { /* NA */ }
        }

        if (content) {
            const mimeType = getMimeType(staticPath)
            if (mimeType) {
                c.header('Content-Type', mimeType)
            }
            return c.body(content)
        } else {
            console.warn(`Dynamic file: Not found for requested ressource ${staticPath}.`)
            await next()
        }
        return
    }
}

Hi @tobiasschmidt89 !
I would also like to have "filesystem-based routing". I think it's not suitable for building Web API, but it's good for building a "Web Site" including HTML. You are right, I am interested in being able to do SSR without heavy JS frameworks. But, I did not make it for the following reasons.

Cloudflare Workers or Fastly Compute@Edge does not have a filesystem.
They also do not support "dynamic import".
We could bundle everything, but we'd have to create a build system for that.

However, you are right, we may soon be able to achieve this with Deno, Bun, and maybe Node.js. Besides, Cloudflare Workers might also support dynamic import, and Compute@Edge has a library that bundles static files. Then Fresh works on Deno Deploy (I have to investigate how it works!).

https://twitter.com/jasnell/status/1546498745054814209
fastly/compute-js-static-publish: Static Publisher for Compute@Edge JavaScript
fresh - The next-gen web framework.

So, maybe it's time to try.

First, we would like to see working examples using your middleware. If possible, could you create your own repository, create the mock-up of middleware and examples, and put them into it? Then I will try it too.
If it looks good, we can host the code at github.com/honojs/middleware.

Hi @tobiasschmidt89  been working on something to that end, you can check it out here


[Monitoring V2] Switch from using rancher/busybox to rancher/library-busybox

As documented in https://github.com/rancher/image-mirror/pull/35#discussion_r490596648, the name for the image has changed and needs to be updated in the charts.
This image is used by both the grafana subchart and rancher-pushprox chart.

This is validated on Rancher:master-db8a864f4acf6f7e70727a8ab9bed029b1c20220-head with the lastest chart.
The image rancher/library-busybox:1.31.1 is used.


Embedded Slideshare Viewer

Is your feature request related to a problem? Please describe.
When putting in a link to a Slideshare presentation, it embeds the link, but clicking takes you away from the tweet to the slideshare website. Instead, a slideshare viewer should be embedded in the post
Describe the solution you'd like
An embedded Slideshare viewer as in X, the former Twitter. The player should open the slideshow on the specified slide.
Describe alternatives you've considered
The alternative is what exists today, taking you away from bsky to the slideshare website to see the slides. This is unacceptable, because it reduces the chances of a member engaging with the post, and reduces the dissemination of the information
Additional context
An example of the url is below
https://www.slideshare.net/SRI.CORNELL/1709-oopportunities-to-raise-agricultural-production-with-watersaving-and-with-climatechange-resilience#6
A link to the slide viewer on twitter is below. The player should have opened on slide #6, and it used to until it broke during the transition from Twitter to X
https://twitter.com/ClonalAntibody/status/1643608852812943361
The code for the viewer should be available from folks at scribd/slideshare, and should hopefully not be a complex transition to bsky
likely scribd contact Mailto<EMAIL_ADDRESS>

The jump to slide functioned extremely well, until it got broken around the time Elon Musk started with his shenanigans on twitter. I had a long dialogue with slideshare about it, and they said that the problem is on the twitter side.
You may have to approach slideshare in order to implement the viewer. The key probably comes from a  request made to slideshare server would be my guess
Having the embedded viewer makes for much more cogent threads.

The jump to slide functioned extremely well, until it got broken around the
time Elon Musk started with his shenanigans on twitter. I had a long
dialogue with slideshare about it, and they said that the problem is on the
twitter side.
You may have to approach slideshare in order to implement the viewer. The
key probably comes from a request made to slideshare server would be my
guess
Having the embedded viewer makes for much more cogent threads.
On Wed, Jan 10, 2024 at 3:56 AM Mary @.***> wrote:

Twitter didn't break it, either it's that Slideshare never actually
implemented said functionality to begin with (my assumption given how the
jump-to-slide functionality is implemented within the URL), or Slideshare
did break it.
Either way it doesn't seem like the URL on this part of HTML changes if
the jump to slide URL is used.
image.png (view on web)
https://github.com/bluesky-social/social-app/assets/148872143/e72f00b9-b1db-48d4-b1b9-17179bf89f37
—
Reply to this email directly, view it on GitHub
https://github.com/bluesky-social/social-app/issues/2466#issuecomment-1884710735,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/BFHL6SU7RZQ4PMXGRDKKKU3YNZ6VJAVCNFSM6AAAAABBUDPIE6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQOBUG4YTANZTGU
.
You are receiving this because you authored the thread.Message ID:
@.***>


chore: restore 2 #aligns

This prevents some false positives in the mathport "dubious
translation" linter.

Did I remove these when re-porting the ad-hoc port?

Yes.

bors merge


[math example] Expected precedence not matching

Hi, I'm trying to use the math parser in a project and I noticed that some examples don't work as expected (or am I'm using incorrectly maybe). I'm trying to fix the issue myself but I could use some help.
minimum example:
initial expression: 1 + (2) / 2
expected expression: +(/(2, 2), 1)
current result: /(+(1, 2), 2)
This also happens with the one written in the documentation: ( 1 + 2 ) * 2 * 2+( 3 * 5   ) / 2 / 2 + 0.25
Let me know if is something wrong on my side or if I can help in somehow (and thanks a lot for the library)

Thank you! I think one of the changes I made in the library broke the example and I hadn't noticed.
I don't like how it's written so I just removed it for now. I'll write another math example in the future.


Sales Copilot for Outlook add-in v. 10 not available

Is version <IP_ADDRESS> or newer of the Sales Copilot for Outlook add-in available on all regions?
Our users see the 'Copy content button' instead of the 'Add to email button' in the suggested email content feature - but we cannot see any available updates in the Microsoft 365 admin center referenced in the documentation.

If version 10 of the Sales Copilot for Outlook add-in is not rolled out in all regions, is there an overview of that somewhere?
Kind regards,
Niels

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

ID: 2e673988-d511-5d36-f6bc-9c2fd3394124
Version Independent ID: 2e673988-d511-5d36-f6bc-9c2fd3394124
Content: Turn on Copilot AI features
Content Source: articles/suggested-replies.md
Service: microsoft-sales-copilot
GitHub Login: @sbmjais
Microsoft Alias: shjais

Thanks for your feedback. For product-related feedback, visit https://feedbackportal.microsoft.com/feedback/forum/7fcacc26-460c-ed11-b83d-000d3a4d91d1. Closing this issue.


Changed example to actually work

example_change was missing a required ignore_null field.
The invocation of elastalert as a file causes the module to attempt import from the wrong location.
There were two errors in the example alerter.
Import errors were cryptic

Ship It!


@index directive without parameters works in iOS (Swift) app but not web (React) app

How did you install the Amplify CLI?
No response
If applicable, what version of Node.js are you using?
16.13.0
Amplify CLI Version
10.6.2
What operating system are you using?
Mac
Did you make any manual changes to the cloud resources managed by Amplify? Please describe the changes made.
No manual changes made
Describe the bug
Following the documentation for adding GSIs to a GraphQL schema:
https://docs.amplify.aws/cli/graphql/data-modeling/#configure-a-secondary-index
type RoomSchedule
  @model
  @auth(
    rules: [
      { allow: public }
    ]
  ) {
  id: ID!

  roomID: ID! @index

  startTime: AWSDateTime
}

Deploying a schema with an index without the optional parameters, name or queryField, seems to work in native Swift SDK Amplify app but is causing unexpected behavior in React web app.
In the web app, the GSI is being used by DataStore as the primary key but a primary key already exists.
Adding the name and queryField parameters seems to fix the issue and DataStore uses the correct primary key on the React app.
roomID being considered a primary key (perhaps mistaken for custom primary key?)

Error thrown during sync process

While debugging, it seems this if statement is being skipped over because DataStore is not auto-generating a value for the id field.

Expected behavior
DataStore uses the correct primary key
Reproduction steps

setup DataStore-enabled GraphQL API and schema with a model including an @index directive, no extra parameters
amplify push
start DataStore in a web app

Project Identifier
92c3dcf409a6854477c23599d6e4a2cc
Log output

# Put your logs below this line

Additional information
No response
Before submitting, please confirm:

[X] I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.
[X] I have removed any sensitive information from my code snippets and submission.

I was able to reproduce this issue consistently, marking as a bug.
Interestingly, the first time I save a record, I can see the graphql mutatation sent to AppSync succeed and an id was auto-generated.
  const createRoomSchedule = async () => {
    const roomSchedule = await DataStore.save(
      new RoomSchedule({
        roomID: "456",
        startTime: new Date("2023-01-30T05:30:00").toISOString(),
      })
    );

    console.log("Saved roomSchedule: ", roomSchedule);
  };

Network Activity

Record persisted to local store on first save (ID was autogenerated)

However, in indexedDB, DataStore is still incorrectly using the roomID GSI as the primary key or "key path".

And, running the same DataStore.save code again, replaces the previously "correct" record with this one where the id field is now missing altogether and the roomID is acting as the primary key.

Hey @chrisbonifacio, can you please re-try after enabling feature flag in cli.json? refer docs here

@AnilMaktala unfortunately, that flag was already enabled ☹ this is still an issue. In talking with @manueliglesias , it seems this schema should not be deployable for a DataStore enabled API to begin with. We may have to throw an error on compilation if @index is missing parameters and conflict detection is enabled.

For anyone experiencing this issue:
in the mean time you can work around this by adding a name property to the @index directive in your schema.
type RoomSchedule
  @model
  @auth(
    rules: [
      { allow: public }
    ]
  ) {
  id: ID!
  roomID: ID! @index(name: "byRoom")
}

You'll need to call amplify push --allow-destructive-graphql-schema-update after making the schema change


remove-number

Sorry for being late,
I am not sure about the logic of the code and at the same time I am just confused about the appropriate methods to use.
The exercise for me is not explanatory enough, so I had to look up how other people handled that.  Yet, I am not fully sure I understand it.
Please, see if that makes sense to you.
#7

In my opinion the logic is like this:
1- Read the array (arrOfNumbers): use for or for...of loop
2- Compare each item in the array (arrOfNumbers) with the parameter (toRemove)
3- If item in the array (arrOfNumbers) is not strictly equal to the parameter (toRemove), then push the item to the shared variable (script-varaible.js which is the variable 'numbers').
for(let item of arrOfNumbers) {

if (item !== toRemove) {
numbers.push(item);
}
}

This is what I think


We should make our config names more private to this package to avoid hydra name collisions.

E.g., add "_"s in front of them. This won't affect our code's interface, but if someone ever tries to import one of our provided configs as a default in hydra, this will make it harder to accidentally suffer from name collision which causes hydra to go into an infinite recursion loop.

E.g., add "_"s in front of them. This won't affect our code's interface, but if someone ever tries to import one of our provided configs as a default in hydra, this will make it harder to accidentally suffer from name collision which causes hydra to go into an infinite recursion loop.

Do you mean _aces.yaml, data/_sharded.yaml, data/_single_file.yaml etc.?

Yes. I spent literally hours today debugging an issue in this PR https://github.com/mmcdermott/MEDS_transforms/pull/187 because my "pipeline.yaml" configuration file in a test had the same name as a "pipeline.yaml" config in MEDS_Transforms that was imported via hydra as a default and it was really hard to debug.
For MEDS_transforms, this is problematic as if you write your file to disk somewhere, you are likely tempted to call it something like "pipeline" or "preprocess" or "extract" (all the default config names for that package). So, I moved all the configs inside the package to "_pipeline", "_preprocess", "_extract" and it should help avoid this issue. We may have the same issue with aces, so should do the same here.
Except, I'd only advocate for this with aces.yaml. Not with data/_s* b/c we need those names to match the option names in how you use them (e.g., data=sharded).

Relevant source hydra issue: https://github.com/facebookresearch/hydra/issues/1828


chore: add SourceLink to project files

Issue #, if available:
DOTNET-6926
Description of changes:
Added the properties required for SourceLink as well as the proper package reference. Once the projects are packed using dotnet pack, a symbols file will be generated alongside the NuGet package. In our pipelines, when we do a nuget push, if there is a symbols package in the same directory as the NuGet package, then the symbols package will automatically be uploaded.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

For the snupkg files do we need to update publishing code in the pipeline to publish snupgk files?
Also I'm assuming some part of the build process with the source link project captures the current commit id. Are we always running the dotnet build / dotnet pack from the context of the Git repository?

We shouldn't need to update our build/publish code since a nuget push will detect the snupkg and push it up with the regular package.
From what I;ve seen, when we do a nuget pack, we need to be in context of the .git folder for it to work.


WIP: update mysql2 gem

it has updated to a new minor release in factory
factory#bump
Signed-off-by: Maximilian Meister<EMAIL_ADDRESS>

before merging, we need to copy the new mysql gem to obs/ibs

setting to WIP because of https://github.com/brianmario/mysql2/issues/950
seems that rails 4.2 has not yet caught up with the dependency change

What's the status of this PR? Should we close it?

we should fix the tests.

velum is not in factory anymore, this is less of an issue now. i'd say we can keep it on hold until we have more time to test an update

This GitHub PR is unactive since 30. Is this GitHub PR still needed? Please close or update it accordingly.
This reminder is autogenerated by https://github.com/MalloZup/blacktango


Generating secret keys w/o sysrandom will always fail

We are using Django's get_random_string implementation in post_gen_project.py.
If sysrandom can't be imported the function will always fail since the if clause relies on the settings.SECRET_KEY to be set, see https://github.com/pydanny/cookiecutter-django/blob/master/hooks/post_gen_project.py#L42-L55

The secret key is set only for the local.py, and it must be set by user while running the project using production settings. It makes sense to simplify the secret key generation.

Since we aren't using Django's get_random_string anymore, I'm closing this issue.


Use properly formatted assert() statement for send() on server

Addresses a problem noted in #171, where an improperly formatted assert call meant that unassertify didn’t remove the function when compiled.

Interesting - I believe this should just work hey https://nodejs.org/api/assert.html#assert_assert_fail_actual_expected_message_operator

Related:

https://github.com/twada/unassert
https://github.com/twada/unassertify/blob/master/index.js

Don’t think it’s a bug in unassertify.
assert.fail expects all four parameters to be filled (none of them are surrounded with [] in the parameter list on that page), even if they’re just filled as undefined. So while assert.fail is throwing the AssertionError, meaning it works for the purposes of choo, its parameters aren’t all filled in and unassert/unassertify won’t pick up on it because it has the wrong signature.

ah yeah, fair enough - node doesn't necessarily require all 4 args to be present but this seems like a quick enough fix so let's merge. Thanks!

Awesome, thanks!


State paramenter on sprint list doesnt appear to do anything

Describe the bug

When I do the following 3 commands, I get the same output, regardless of what state the issues are in:
jira sprint list 99
jira sprint list 99 -p API --state closed
jira sprint list 99 -p API --state active

Please provide following details

JiraCLI Version:(Version="0.3.0", GitCommit="ea53355d5b72994a5b17a63e6e800ce9d8a23f4e", CommitDate="2022-01-09T19:50:19+00:00", GoVersion="go1.17.5", Compiler="gc", Platform="linux/amd64")

Are you using Jira cloud or on-premise jira server? Also mention the version for on-premise installation.Jira cloud

What operating system are you using? Also mention version.Ubuntu 20.04.2 LTS running in WSL2 on Windows 11 Pro version 10.0.22000

What terminal are you using? Also mention version.Windows terminal Version 1.11.3471.0

To Reproduce
Steps to reproduce the behaviour:
Run the commands as above. You should see the same output.
Expected behavior

It should filter the issue list with the applied filter
Screenshots

@ccmattr The state parameter is to filter sprint by its state, not to filter sprint issues. When you do jira sprint list 99 you are loading issues in the sprint 99 and state doesn't matter in that case. Valid usecase would be:
# List all closed sprints in preview display
$ jira sprint list --state=closed

# List all active sprints in table display
$ jira sprint list --table --state=active

Closing due to inactivity. Please feel free to comment to reopen the issue.