jest: breakpoints in vscode

Has anyone managed to get breakpoints to work in vscode? I have the following launch config that works fine except for the breakpoinst not being hit. Is shows the right code fragments where an exception is raised or matcher fails. So I do not think it has something to do with source maps.
        {
            "name": "ng test",
            "type": "node",
            "request": "launch",
            "program": "${workspaceFolder}/node_modules/@angular/cli/bin/ng",
            "args": ["test"],
            "console": "integratedTerminal",
            "outFiles": ["${workspaceRoot}/output/debug/**/*"]
        }

Try adding --inspect-brk to the node runtimeArgs and runInBand for jest builder options.

Thank you for your suggestion. The debugger seems to attach correctly without the extra runtimeArgs. The runInBand did not help either. The output from the launch debugger command is shown below.
cd [path to workspace root] && "C:\Program Files\nodejs\node.exe" --inspect-brk=20693 node_modules\@angular\cli\bin\ng test --watch
Debugger listening on ws://<IP_ADDRESS>:20693/bb1874a6-c540-4295-8f57-44e6681d6ea8
For help see https://nodejs.org/en/docs/inspector
Debugger attached.

I found that breakpoints do work when I'm not running the tests in watch mode. Disabling watchMan by passing the --no-watchMan cli option does not help. I'm closing the issue, because it does not seem to be specific to this builders setup.

You can use this configuration to use VSCode debugger with Jest:
    {
      "name": "Debug Jest Tests",
      "type": "node",
      "request": "launch",
      "runtimeArgs": [
        "--inspect-brk",
        "${workspaceRoot}/node_modules/@angular/cli/bin/ng",
        "test",
        "--runInBand",
        "--no-cache",
        "--env=jsdom"
      ],
      "console": "integratedTerminal",
      "internalConsoleOptions": "neverOpen",
      "port": 9229
    }

Tested with Angular 6 and Jest 23.6

Being unable to debug in watch mode is a known bug from Jest#6739


Getting your ducks together - Doc vs Git vs Code

For being a company that strives on simplicity, documentation, open source, etc.
Developers rely on your code/information to implement your service, yet it's baffling to me that your tutorials are from 2009-2012 and have completely wrong information (queue https://developers.google.com/analytics/solutions/articles/hello-analytics-api)
Your 'hello world' to analytics fails on so many levels, I don't understand how that slides. By all means bash the n00b in me for not understanding right away how to use your api; having terrible documentation for a product that you create/support is simply worse than no documentation at all.

Just another proof:
'https://developers.google.com/analytics/devguides/reporting/core/v3/coreDevguide'  - Last updated April 7, 2015.
Yet the call to the PHP analytics service is: $analytics = new apiAnalyticsService($client); :-1:

I find it absolutely pathetic that you can't even get your documentation/code samples together.

Good thing about being openSource is that people like you can contribute to get this better :)

@kesar :+1:  :100:
I'll try to keep my code clean and create a PR for an Analytics PR :P

That will be great! thanks! :+1:


Unexpected logging when running tests

Environment

Elixir version (elixir -v): 1.7.4
Database and version (PostgreSQL 9.4, MongoDB 3.2, etc.): psql 11.2
Ecto version (mix deps):  3.1.1
Database adapter and version (mix deps):  ecto_sql 3.1.1
Operating system: macos

Current behavior
after upgrading ecto 3.0 -> 3.1, i’m seeing unexpected logs when running tests, like
2019-04-16 15:32:27.472 MDT [49856] ERROR:  update or delete on table "..." violates foreign key constraint "...." on table "..."
2019-04-16 15:32:27.472 MDT [49856] DETAIL:  Key (id)=(...) is still referenced from table "...".
2019-04-16 15:32:27.472 MDT [49856] STATEMENT:  DELETE FROM ... WHERE "id" = $1

Expected behavior
These logs should be routed through the logger application, and so not printed to the console (thanks to config settings)

If they are being printed with such timestamps... then they are being routed through the logger, no? Or does it just look like Logger's?
In any case, I agree this should not happen, do you have a way to reproduce this bug? Thank you.

Seems like any sort of psql error will trigger it. Easiest repro:

clone bare-bones phx app https://github.com/novaugust/ecto-concurrent-index-bug
mix ecto.create
repeat mix ecto.create

➜  ecto-concurrent-index-bug git:(master) mix ecto.create
2019-04-16 16:19:26.798 MDT [56432] ERROR:  database "hello_dev" already exists
2019-04-16 16:19:26.798 MDT [56432] STATEMENT:  CREATE DATABASE "hello_dev" ENCODING 'UTF8'
The database for Hello.Repo has already been created

Unfortunately I cannot reproduce this:
~/OSS/ecto-concurrent-index-bug[master]$ mix ecto.create
The database for Hello.Repo has already been created
~/OSS/ecto-concurrent-index-bug[master]$ mix ecto.create
The database for Hello.Repo has already been created

Any idea why it happens locally for you? I couldn't find anywhere where we would be logging those messages as they have been formatted for you.

Possibly question: could you have started postgres as a background process attached to your current terminal and those logs are coming for postgres?

Given that I also reinstalled + upgraded psql to 11 at the same time I did this 3.1 migration, something like that seems a likely culprit. Especially given the lack of repro =)
I'll twiddle with my environment, thanks for the prompt help

@novaugust I was recently coming across the same issue. Jose's comments led me (and some friends helping me out) to look into how I was starting the postgres server. I had been using pg_ctl to start the server when I received a connection error when trying to run my tests. I shut down the server and switch to using brew services start postgresql and the errors no longer appear in my terminal when running tests. Just thought I would comment here as this issue led me toward the solution.

This is a documented behaviour, manifesting itself when starting postgres via pg_ctl without any explicit output control:
From pg_ctl docs:

On Unix-like systems, by default, the server's standard output and standard error are sent to pg_ctl's standard output (not standard error). The standard output of pg_ctl should then be redirected to a file or piped to another process such as a log rotating program like rotatelogs; otherwise postgres will write its output to the controlling terminal (from the background) and will not leave the shell's process group. On Windows, by default the server's standard output and standard error are sent to the terminal. These default behaviors can be changed by using -l to append the server's output to a log file. Use of either -l or output redirection is recommended.

The solution with brew services start postgresql works because the service definition file includes log redirection directives:
From /usr/local/opt/postgresql<EMAIL_ADDRESS>(only the relevant bits):
[Service]
ExecStart=/usr/local/opt/postgresql@11/bin/postgres -D /usr/local/var/postgresql@11
<EMAIL_ADDRESS><EMAIL_ADDRESS>
If it is desirable to still use pg_ctl, there are several solutions:

Pass the -l flag to pg_ctl, specifying the log output location:

pg_ctl -D /usr/local/var/postgresql@11 -l<EMAIL_ADDRESS>start

Redirect the log output explicitly:

pg_ctl -D /usr/local/var/postgresql@11 start > pglog.log

Use the logging_collector setting in the postgresql.conf file:

# This is used when logging to stderr:
logging_collector = on  # Enable capturing of stderr and csvlog
                        # into log files. Required to be on for
                        # csvlogs.
                        # (change requires restart)

In this case postgres should be started with a simple pg_ctl -D /usr/local/var/postgresql@11 start, and the log by default will be redirected to a file under the data directory's log subdirectory, e.g<EMAIL_ADDRESS>The destination can be configured by the nearby settings in the same file.


Error! The first release should be created manually.

> np major --no-publish --yolo && release

 ✔ Prerequisite check
 ✔ Git
 ✔ Bumping version
 ✔ Pushing tags

 wifi-tracker 1.0.0 published 🎉
✔ Checking if release already exists
✖ Loading commit history

Error! The first release should be created manually.

Why should the first release be created manually?

Looks like this an issue for https://github.com/zeit/release, not this module. 😄

Ooops! I see I should be running npm run release, not release. Thanks.


add Dependabot

https://github.blog/2020-06-01-keep-all-your-packages-up-to-date-with-dependabot/

@joel-costigliola

@sullis Thanks for your contribution


GNN metacontroller baseline

After learning options, use demonstrations and behavior cloning to train a GNN that maps state, atoms, and goal to a ground NSRT. At evaluation time, sequentially generate ground NSRTs, sampling multiple times per step. This will be a baseline for the parameterized option learning project.

closed by #755


chore: remove tactics

More tactics that are not used, found using the linter at #11308.

!bench


Fix Dockerfile

Hello, I represent a research group investigating build failures in
Dockerfiles. We executed a Dockerfile in your project and found that
it is not building. We are sending this Pull Request with a suggested
repair. The repair operation is based on the following URL:

https://github.com/rubygems/bundler/issues/6865

Please note that we are using an anonymous GitHub account because of
double-blind restrictions in the submission process of conferences.

Hey @coding-student @manaswinidas , can you check this PR?


Viewport instantiation is very slow when using GLES3

Godot version
3.3.stable
System information
Windows 10
Issue description
Each time a Viewport is instantiated, a spike can be seen in the profiler. This spike can cause a drop of a few frames. This is only the case when using GLES3.
Using a C++ profiler, I was able to track the slowdown to the texture_create method, but I don't know why it would  be slower in GLES3 than GLES2.
Steps to reproduce
Instantiate a Viewport.
Minimal reproduction project
Use the profiler to profile this project. A Viewport is instantiated every few frames. Spikes can be seen periodically when using GLES3, but not when using GLES2.
viewport_instance.zip

Related to https://github.com/godotengine/godot/issues/42726.

I noticed this too creating and instantiating a Viewport (and a Sprite to render it), there are noticeable drops in frames long before you get to add anything. I also only rendered 2D sprites with no shaders. I couldn't eliminate it or spend more time on it, so I stopped using Viewports to render small offscreen textures (😢). The best I could do was pool the viewport for later use, but the first time it was seen always stalled the fps.


Updated README.adoc: landing page for users

updated readme
more user-friendly, with marketing blurb
removed references to learning outcomes, etc.

Pull Request Test Coverage Report for Build 36

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

Totals

Change from base Build 35:
0.0%

Covered Lines:
1480

Relevant Lines:
1611

💛  - Coveralls


Added OpenMage cron example

Added OpenMage cron example

I don't use OpenMage but it looks fine to me.
Thank you for the PR!


Injecting options into handlers via DI container?

Is it currently possible to inject options via the built in DI container using source generation?

Do you mean inject options to confingure Mediator itself (e.g. namespace)? That's not possible siden source generation depends on it. So the configuration values have to be constants
But other than that Mediator doesn't impose any limitations on how you use DI

nope, sorry - I meant to close this. I figured out how to do this.

Pretty sure this is what he was trying to do Martin, which is also what I am trying to figure out as well.  If you want I can open a new ticker, or we can continue on this ticket. I really need to figure out how to do this.
@djflan I really wish you had shared your solution so that others could have benefited,

LOL, actually like @djflan I just tried it, and it just works. Like normal. Which was unexpected, and very nice. Sorry, this ticket can stay closed.

Ahh, so just injecting the MediatorOptions into some service at runtime? That should be possible yes.. Only constraint Mediator imposes is that the values put into the option properties are compile time constants (the source generator needs to see them)


Add index_col for spark IO reads.

related with #765 , I've added index_col for spark IO reads
If we know the index column already, We can prevent the creation of a default index by explicitly typing an index column as function arguments.

And If you think this way is okay, I'm going to create a PR with all the other functions.
So could you take a look at this maybe if you available??
Thanks :)

@ueshin , @HyukjinKwon Could you take a look at this maybe if you available? :)

Codecov Report

Merging #769 into master will decrease coverage by 2.34%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master     #769      +/-   ##
==========================================
- Coverage    93.9%   91.55%   -2.35%
==========================================
  Files          32       32
  Lines        5691     5699       +8
==========================================
- Hits         5344     5218     -126
- Misses        347      481     +134

Impacted Files
Coverage Δ

databricks/koalas/namespace.py
79.8% <100%> (-1.2%)
:arrow_down:

databricks/koalas/frame.py
94.7% <100%> (-1.68%)
:arrow_down:

databricks/koalas/usage_logging/__init__.py
23.14% <0%> (-74.08%)
:arrow_down:

databricks/koalas/usage_logging/usage_logger.py
50% <0%> (-50%)
:arrow_down:

databricks/koalas/__init__.py
77.5% <0%> (-7.5%)
:arrow_down:

databricks/conftest.py
90.69% <0%> (-6.98%)
:arrow_down:

databricks/koalas/plot.py
93.92% <0%> (-1.11%)
:arrow_down:

databricks/koalas/utils.py
97.24% <0%> (-0.69%)
:arrow_down:

... and 3 more

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 224cbe4...b66658e. Read the comment docs.


Optimize Dockerfile and added Git

This started as a change to add Git so that developers will have it available if they need to install a dependency from GitHub. I then took it a step further to optimize the Dockerfile a bit for size by consolodating the apt commands to a single RUN statement and clearing the apt lists at the end. I also set it to install Rebar and not output the Hex info.
Differences of various Docker image sizes:
davejlong/kitto-with-git-optimized          latest              d1d86f631f4d        7 seconds ago        408.6 MB
davejlong/kitto-with-git                    latest              44dd48c4b9ad        About a minute ago   417.5 MB
davejlong/kitto-optimized                   latest              6be10bec9067        2 minutes ago        338.7 MB
davejlong/kitto                             latest              06dc96d33395        3 minutes ago        348.5 MB

I added clean and removed the y flag.

Also #FirstPR

Coverage remained the same at 77.465% when pulling a1c6a4fd12491e88447763037e75c4e5a5870d7d on davejlong:patch-1 into 07d8497f8386c6c5faaf6dacaeaaf09e006751da on kittoframework:master.

I'm a bit concerned about the image size increase, but it may help people get started with the project more easily (considering that even the trivial demo app has github dependencies). Next steps might be to have an image based on alpine to optimize for size.


unzip.Parse() doesn't work according to docs

It seems that in node v4.1.0, unzip.Parse() does not work according to the docs.
This does not work:
res
  .pipe(unzip.Parse())
  .pipe(writeStream)
  .on('finish', () => {
    console.log('finish')
  });

However, this does:
res
  .pipe(unzip.Parse())
  .on('entry', (entry) => entry.pipe(writeStream) )
  .on('finish', () => {
    console.log('finish')
  })

Maybe the Stream API has changed?

Any update on this ? Because I have same problem

I'm using Node 6.3 and have no issues. I don't get a finish event, however, but a close event.
Are you sure you're using writeStream = fstream.Writer('output/path') from the fstream package as shown in the example? The writeStream object in entry.pipe(writeStream), on the other hand, is your standard fs.createWriteStream('output/path').


feat(acir)!: Use fixed length data structures in black box function inputs/outputs where possible.

Description
Problem*

Resolves
Summary*
This PR modifies any opcodes which have a known number of inputs/outputs to hold a tuple of these values rather than a vector.
Additional Context

PR Checklist*

[x] I have tested the changes locally.
[x] I have formatted the changes with Prettier and/or cargo fmt on default settings.

We could also do this with the pubkey + signature for ECDSA but this causes issues with serialisation.

I'm silencing the clippy warning as it will be addressed in #378


Running black code formatting 🦩

This PR addresses issue https://github.com/covid-projections/covid-data-model/issues/230
This runs black formatting on the repo.  I chatted with @erccarls and he's on board, and a lot of us have been intermittently running this.
This does not add a pre-commit hook or linting just yet - will happen in follow up PRs
Please Check

[ ] Will the current schema in api docs be updated with this PR?
[ ] Are tests passing?

lgtm, although unclear why tests are failing?

Looks like that's a separate issue?


[PALOMA] As a validator, i would like the Paloma to improve the slashing window like dydx

As a validator, i would like the Paloma to improve the slashing window like dydx.
Acceptance Criteria

And I think it would be better to remove the uptime slashing and reduce the signing window (you can see this approach for the dydx)

$ palomad q slashing params
params:
  downtime_jail_duration: 10m0s
  min_signed_per_window: "0.500000000000000000"
  signed_blocks_window: "10000"
  slash_fraction_double_sign: "0.050000000000000000"
  slash_fraction_downtime: "0.010000000000000000"

updated params.

min_signed_per_window: 0.200000000000000000
signed_blocks_window: 5000
slash_fraction_downtime: 0.000000000000000000

@taariq This needs to go through a governance vote. It should be something like:
{
 "messages": [
  {
   "@type": "/cosmos.slashing.v1beta1.MsgUpdateParams",
   "authority": "paloma10d07y265gmmuvt4z0w9aw880jnsr700jz87xyk",
   "params": {
    "signed_blocks_window": "5000",
    "min_signed_per_window": "0.200000000000000000",
    "downtime_jail_duration": "10m0s",
    "slash_fraction_double_sign": "0.050000000000000000",
    "slash_fraction_downtime": "0.000000000000000000"
   }
  }
 ],
 "metadata": "ipfs://CID",
 "deposit": "10000000ugrain",
 "title": "PIP-XX: Update Slashing Params",
 "summary": "PIP-XX: update slashing params",
 "expedited": false
}

Thanks. I will do the PIP for this.


[Task] Enhance the docer start commands

Description
The commands now like:

docker run -d -p 9095:9095 --net shenyu apache/shenyu-admin

docker run -v /${your_work_dir}/ext-lib:/opt/shenyu-admin/ext-lib -e "SPRING_PROFILES_ACTIVE=mysql" -e "spring.datasource.url=jdbc:mysql://${your_ip_port}/shenyu?useUnicode=true&characterEncoding=utf-8&useSSL=false" -e "spring.datasource.username=${your_username}" -e "spring.datasource.password=${your_password}" -d -p 9095:9095 --net shenyu apache/shenyu-admin

docker run -v ${your_work_dir}/conf:/opt/shenyu-admin/conf/ -v /${your_work_dir}/ext-lib:/opt/shenyu-admin/ext-lib -d -p 9095:9095 --net shenyu apache/shenyu-admin

I would suggest we add paramenters to make the commands more available like:

--privileged=true
-v /etc/localtime:/etc/localtime:ro
--restart=always

Are these parameters right? Any more parameters should be added?
Task List
No response

i suggest add some env

i suggest add some env

Can you provide some details?

@nuo-promise

I think these three configurations are a bit system-specific (Linux).
Considering that the systems using our products may be other systems, it
may be possible to consider not adding them. If you need these features for
your production environment, you can do it yourself.

Agree. Let's provide the minimal parameters which are required, while user can customize parameters which meet their needs.


Fix typos

These are all definitely typos, but none are mine. None of the suggested changes affect functional code, so I see no reason not to accept the PR.


update pagerank

Utilized networkx pagerank function, excluded self loops before pagerank calculation

I keep getting a convergence error from the page rank function. Were you seeing this on your other branch? I wonder what's different here.

I wasn't getting any errors when I used this code on my other branch for the GRNdb matrix, so I'm not sure what it could be. Maybe it has to do with some of the iterating that goes on after add_edges and set_edges have been called in the creation of the network. If there is some other part of the code that is expecting i x j (83x83) edges, would that cause a convergence error since self-edges are excluded in this update? I can sift through the rest of graph.py to see if there could be something like this causing an error. It's weird that the error is originating with the pagerank function though, since it should be compatible with other networkx functions and graph attributes.

I keep getting a convergence error from the page rank function. Were you seeing this on your other branch? I wonder what's different here.

I wasn't getting any errors when I used this code on my other branch for the GRNdb matrix, so I'm not sure what it could be. Maybe it has to do with some of the iterating that goes on after add_edges and set_edges have been called in the creation of the network. If there is some other part of the code that is expecting i x j (83x83) edges, would that cause a convergence error since self-edges are excluded in this update? I can sift through the rest of graph.py to see if there could be something like this causing an error. It's weird that the error is originating with the pagerank function though, since it should be compatible with other networkx functions and graph attributes.

I can see that the old pagerank gets called in the bar graph functions, I forgot to update those functions with my last commit. Do you think that editing those will solve the convergence error?

@miajeffris hmm... indeed, it would be good to update the bar graph functions so they point to the right place too. To figure out the convergence issue, could you open a PR of the branch where this is working, and tag me? I'll try and see if I can spot the critical difference.

@miajeffris hmm... indeed, it would be good to update the bar graph functions so they point to the right place too. To figure out the convergence issue, could you open a PR of the branch where this is working, and tag me? I'll try and see if I can spot the critical difference.

Just tagged you in the PR where this is working for the GRNdb network

@miajeffris I don't see a call to nx.pagerank on that other branch?

See Slack message.


Set the version to what kubelet expects

Signed-off-by: Mrunal Patel<EMAIL_ADDRESS>

@runcom PTAL

LGTM

LGTM


缓存丢失

经过多个项目的线上日志分析，发现此库有缓存丢失的现象。作者有空可以修复一下。

Excuse me. I have switched careers to not do iOS.
This library has also been unmaintained for N years.

大神现在转后端了吗

大神现在转后端了吗

前端。

哦哦，iOS确实不好混啊，是web前端吗


Check netloc in urlparse result if path is empty

Please check if the PR fulfills these requirements

[x] Tests for the changes have been added

[ ] Docs have been added / updated

[x] All CI checks are green

What kind of change does this PR introduce?

This fixes a bug where certain versions of urllib will put the results of a parsed file (e.g. file://testing/custom_filters.py::is_invalid_secret) into the netloc property of urlparse instead of the path property.

What is the current behavior?

https://github.com/Yelp/detect-secrets/issues/715

What is the new behavior (if this is a feature change)?
The custom filter parser will now check netloc if path is not populated

Does this PR introduce a breaking change?

Users should have to make no changes, as it prefers path over netloc

Other information:

@a-weiss-programmer thank you for your contribution! Could you advice me on which version have one or the other behaviour?


Question: what is right usage under Yosemite and above

Hello,
There is many formulae related to fuse that I like to use on my Mac.
From a certain time osxfuse formula is no longer supported on most recent OSX version with this message:
brew upgrade osxfuse
==> Upgrading 1 outdated package, with result:
osxfuse 2.8.3
osxfuse: Building this formula from source isn't possible due to OS X
Yosemite and above's strict unsigned kext ban.

You can install with Homebrew Cask:
  brew install Caskroom/cask/osxfuse

Then, what is the right solution now to go on using those formulae (afuse, archivemount, ext4fuse, fuse-zip, ifuse, mp3fs, ntfs-3g, sshfs...) having :osxfuse as dependency:

is Cask version fullfilling the dependency?
are the formulae adapted above Yosemite to detect and re-use the system-wide version of osxfuse installed manually from pkg (in /usr/local)?
other solutions?

Please forgive me if my question is not very clear or clever ;-)
P.S. Maybe is it worth mentioning that my Cellar and Caskroom are not in /usr/local but in a dedicated /opt/homebrew directory.

Homebrew dependencies starting with : are "special" dependencies in some way. They line up with Requirements, in this case :osxfuse == this requirement, which as you can see can be satisfied in a variety of ways.
Valid ways to meet the dependency:

The osxfuse formula.
brew cask install osxfuse
Installing the .pkg installer from the upstream website.

In that order, pretty much. So yup, you can remove the formula & install via cask or upstream .pkg and we'll happily use that. Hope this helps 😃

Great, very clear!
Thanks :-)


feat: add config - disable_default_mappings

Discussion: https://github.com/nvim-neo-tree/neo-tree.nvim/discussions/265

The plenary tests might work for me because my packer setup already has those projects cloned to the correct location. If that's not true for you, something like what I do in the github action might work:
git clone https://github.com/MunifTanjim/nui.nvim ~/.local/share/nvim/site/pack/vendor/start/nui.nvim
git clone --depth 1 https://github.com/nvim-lua/plenary.nvim ~/.local/share/nvim/site/pack/vendor/start/plenary.nvim

It's ok though because you did fix the issue.
Thanks for contributing!


Deleting password of public link share when enforce password is enabled returns 996 ocs code

Describe the bug
Removing the password of a public link share when the config OCIS_SHARING_PUBLIC_WRITEABLE_SHARE_MUST_HAVE_PASSWORD is set to true.
Steps to reproduce
Steps to reproduce the behavior:

Set OCIS_SHARING_PUBLIC_WRITEABLE_SHARE_MUST_HAVE_PASSWORD=true
Upload a file testfile.txt
create a public link share with edit permission curl -k -X POST https://localhost:9200/ocs/v2.php/apps/files_sharing/api/v1/shares -d 'shareType=3&path=/testfile.txt&permissions=3&password=1234' -u <username>:<password> -v
Try to remove the password of the public link curl -k -X PUT https://localhost:9200/ocs/v2.php/apps/files_sharing/api/v1/shares/<share-id> -d 'password=' -u <username>:<password> -v

Expected behavior
The response should return 400 ocs code.
Actual behavior
The response is returning 996 ocs code.
Actual Response
> PUT /ocs/v2.php/apps/files_sharing/api/v1/shares/OVSRqusgeRzOcPH HTTP/1.1
> Host: localhost:9200
> Authorization: Basic YWRtaW46YWRtaW4=
> User-Agent: curl/7.81.0
> Accept: */*
> Content-Length: 9
> Content-Type: application/x-www-form-urlencoded
>
* TLSv1.2 (IN), TLS header, Supplemental data (23):
* TLSv1.3 (IN), TLS handshake, Newsession Ticket (4):
* TLSv1.2 (IN), TLS header, Supplemental data (23):
* Mark bundle as not supporting multiuse
< HTTP/1.1 200 OK
< Content-Length: 227
< Content-Type: text/xml; charset=utf-8
< Date: Mon, 26 Jun 2023 07:20:26 GMT
< Ocs-Api-Version: 1
< Vary: Origin
<
<?xml version="1.0" encoding="UTF-8"?>
* Connection #0 to host localhost left intact
<ocs><meta><status>error</status><statuscode>996</statuscode><message>Error sending update request to public link provider: the public share needs to have a password</message></meta></ocs>

@PrajwolAmatya When the frontend sends such a request it also includes the "permissions" value.
If you call curl -k -X PUT https://localhost:9200/ocs/v2.php/apps/files_sharing/api/v1/shares/<share-id> -d 'permissions=3&password=' -u <username>:<password> -v the API returns 400 <ocs><meta><status>error</status><statuscode>400</statuscode><message>missing required password</message></meta></ocs>

@PrajwolAmatya But if you think it is the critical spot I'll fix it.

I think while updating the link, only the required attribute should be used, i.e., password=. Since we are updating the public link and while updating the link setting the permission to 3 should not be necessary in my opinion and only the required attribute value should be used.
Referenced this docs:
https://lukasreschke.github.io/OpenCloudMeshSpecification/#update-an-existing-share
https://docs.nextcloud.com/server/latest/developer_manual//client_apis/OCS/ocs-share-api.html#update-share
@2403905

If I'm not wrong, the current behavior of the server is that the password can be removed only by people with specific roles like Admin user and the password is enforced in links by default is this issue relevant anymore? We also have some test coverage as a part of this issue https://github.com/owncloud/ocis/issues/7823
cc @2403905 @PrajwolAmatya @ScharfViktor @saw-jan

If you are sure about the tests coverage then maybe we can close this one.
Scenario that needs to be covered: https://github.com/owncloud/ocis/pull/6465/files

If you are sure about the tests coverage then maybe we can close this one. Scenario that needs to be covered: https://github.com/owncloud/ocis/pull/6465/files

I think this is covered here https://github.com/owncloud/ocis/blob/55f3ef0aff4c2ee58e4cf7b8a38391b43c0c576f/tests/acceptance/features/coreApiSharePublicLink1/changingPublicLinkShare.feature#L136
https://github.com/owncloud/ocis/blob/55f3ef0aff4c2ee58e4cf7b8a38391b43c0c576f/tests/acceptance/features/apiSpacesShares/shareSpacesViaLink.feature#L254

I think while updating the link, only the required attribute should be used, i.e., password=. Since we are updating the public link and while updating the link, setting the permission to 3 should not be necessary in my opinion and only the required attribute value should be used. Referenced this docs: https://lukasreschke.github.io/OpenCloudMeshSpecification/#update-an-existing-share https://docs.nextcloud.com/server/latest/developer_manual//client_apis/OCS/ocs-share-api.html#update-share @2403905

this was covered and fixed as a part of this issue https://github.com/owncloud/ocis/issues/7821

I am closing this ticket as fixed.
CC @2403905 @ScharfViktor


dep: update satori/go.uuid to latest

What problem does this PR solve?
after hiding lighting's go.mod and embedded it into tidb, an error checkpoint tool will raise error like
$ ./tools/check/check-errdoc.sh
Generate errors.toml failed: exit status 2, output:
# github.com/pingcap/tidb-lightning/lightning/backend
../../../../pkg/mod/github.com/pingcap/tidb-lightning@v4.0.9-0.20201104053247-8013216a3446+incompatible/lightning/backend/local.go:486:26: multiple-value uuid.NewV4() in single-value context

What is changed and how it works?
update satori/go.uuid to latest
Check List
Tests

pass original test

Side effects
Related changes

@lance6716  please fix the failed unit test

@glorv CI pass

Shall we move to github.com/google/uuid, the same library as tidb?

Shall we move to github.com/google/uuid, the same library as tidb?

there're some uuid.NewV5 usage like
https://github.com/pingcap/tidb-lightning/blob/eb609ecfa6ca38205084843f2341cfc79cd30414/lightning/backend/backend.go#L79
and through a glance I think github.com/google/uuid doesn't support version 5.

@lance6716  uuid.V5 is not a big issue, that just generate a uniq sign to each engine. Yout can change to any other implement in google/uuid you like

CI passed @glorv

LGTM


WinUI3 Gallery becomes unresponsive when sliders are moved quickly

Describe the bug
After moving the sliders in the WinUI 3 Gallery app, it becomes unresponsive for 5-10 seconds.
Steps to reproduce the bug

Open the WinUI 3 Gallery app
Go to Basic input -> Slider
Quickly move the sliders

Expected behavior
The app shouldn't freeze like that.
Screenshots
No response
NuGet package version
WinUI 3 - Windows App SDK 1.5.5: 1.5.240627000
Windows version
Windows 11 (22H2): Build 22621
Additional context
If there is no reproduction, try to increase the system workload.
Another way is to create an app with two sliders and move them simultaneously.

I can't reproduce. Can you share a screen recording?

Do you have a server drive where I can upload a video?

Do you have a server drive where I can upload a video?

You can just drag and drop a video in github (the file needs to be <10M. You can compress/transcode/lower the bitrate it if you exceed).

I put it in a zip file:
gallery_freeze_bug.zip


Simplify C# version

Primarily: replace behavior-less wrapper objects with tuples, use var (infer types).
Because tuples are value types, not heap types, this will reduce allocation somewhat.  On my machine, the runtime reduces from 582ms to 571ms (best of several runs) - but that's with startup time; and the benchmark is so small I think you're primarily measuring that.
I retained the default random number generator - but usage of a non-deterministic seed means reproducibility isn't ideal (even if the chances of significant deviation are slim to none).

Thank you! I have updated the Linux stats in the README (the time went down from 0.82s to 0.70s).
/cc @nwoolls

Interesting that the change is so much larger on linux than on my windows machine.  Fun game; good luck with it!


Use "constexpr if" in MultiThreaderBase::ParallelizeImageRegionRestrictDirection, and other style improvements

Style improvements MultiThreaderBase::ParallelizeImageRegionRestrictDirection:

Replaced an "if" with "constexpr if", allowing to simplify the initialization of SplitDimension

Removed the two continue statements, following C++ Core Guidelines, "Minimize the use of break
and continue in loops"

Replaced the local splitRegion variable with more lightweight splitIndex and splitSize variables

Replaced the default capture [&] of the local lambda with an explicit capture list, capturing restrictedDirection by value instead of by reference

Thanks, Hans!


Move all Create overloads taking a seed to another library

In my experience, the overloads for Create and Freeze methods that take a seed as extra argument cause much confusion (see this discussion for just one example).
All extension methods that take a seed as argument should be moved out of AutoFixture and into a separate library. This removes them from the mainstream AutoFixture API, which, hopefully, should make AutoFixture easier to use.
For those users still needing this feature, the extension methods will exist in a separate library, available as a separate NuGet package.
We can monitor the download statistics for that NuGet package to see if anyone uses that feature at all, and then completely retire it if that's not the case.
Please note that this is a breaking change, so the move cannot be done until AutoFixture 4, and complete removal will have to wait until AutoFixture 5 (if ever).

@moodmosaic I'm a bit confused by the plan, so could you please clarify it? The idea is to move the Create method overloads with a seed to a standalone Nuget package like AutoFixture.SeededCreation. It's fine.
However, the point with obsoletion confuses me. If we move extension methods to a standalone lib, we will to completely remove overloads from the AutoFixture library, rather than obsolete them. Otherwise, if user installs a Nuget  package, it will have 2 methods with exactly same signature and it will be annoying.. :worried:

moodmosaic Pinging in case you missed this thread😉

IIRC, the idea was to create a new AutoFixture.Something library and move those overloads there, but keep the same namespace in that hypothetical library.

@moodmosaic Thanks for the confirmation.
As for the package name, I could advice the following ones:

AutoFixture.SeededCreation
AutoFixture.CreateFromSeed
AutoFixture.Seed
AutoFixture.SeedExtensions

Do you like any name? The last name looks the best for me. If you don't like the suggested names - do you see a more appropriate one? :wink:

AutoFixture.SeededCreation sounds great to me 👍 😃

Done! Extracted methods to the AutoFixture.SeedExtensions package in v4.


No matching version found for<EMAIL_ADDRESS>

No matching version found for<EMAIL_ADDRESS>

@adieuadieu  can you please help make 1.0.0-57 public ?


Tools

I wrote these a while ago but wasn't going to submit until printf supported nice format widths. Their output looks much better now. :)
This creates a tools subdirectory: that would be for useful tools. We should also have an examples subdirectory for short code examples, that are more focused on showing code than having a useful tool.

Hi,
Awesome! Pointer arithmetic is great thing, but scalar arrays would be better I guess.

Nice - thanks for these!


Everything is downloaded n+1 times after failing to login n times

I have failed to log in 3 times and succeeded the 4th time.
Everything is downloaded 4 times, as this screenshot shows:

It not only loads much slower, but reaches GGG-s request limit and waits for even more time.

This might be a display issue only where the code does not properly unsubscribes from the events if the authentication throws an exception.

This is a bug that seems to have resurfaced, previously the issue was due to the events not being deregistered after a failed login, I'll look into why it has reappeared.

I've done some testing and can't replicate this in the latest version, please test and let me know if it's still an issue.


Media library breaks Back End links

Describe the Bug
After opening the media library, it is not possible to navigate out of it.
Steps to Reproduce

Open the admin media library
Click Admin Dashboard
An error message An error has occurred. Please try again later. appears. The network history tells us that the browser tried to load /ajax/media/directory-path?directory=admin_dashboard as an AJAX request instead of opening /admin_dashboard in the main window.

I guess that some JS is overstepping its competencies ;)

Is this a duplicate of #877?

It is.


pam: Fix CVE-2024-10963 with patch

Merge Checklist

All boxes should be checked before merging the PR (just tick any boxes which don't apply to this PR)

[x] The toolchain has been rebuilt successfully (or no changes were made to it)
[x] The toolchain/worker package manifests are up-to-date
[x] Any updated packages successfully build (or no packages were changed)
[x] Packages depending on static components modified in this PR (Golang, *-static subpackages, etc.) have had their Release tag incremented.
[x] Package tests (%check section) have been verified with RUN_CHECK=y for existing SPEC files, or added to new SPEC files
[x] All package sources are available
[x] cgmanifest files are up-to-date and sorted (./cgmanifest.json, ./toolkit/scripts/toolchain/cgmanifest.json, .github/workflows/cgmanifest.json)
[x] LICENSE-MAP files are up-to-date (./LICENSES-AND-NOTICES/SPECS/data/licenses.json, ./LICENSES-AND-NOTICES/SPECS/LICENSES-MAP.md, ./LICENSES-AND-NOTICES/SPECS/LICENSE-EXCEPTIONS.PHOTON)
[x] All source files have up-to-date hashes in the *.signatures.json files
[x] sudo make go-tidy-all and sudo make go-test-coverage pass
[x] Documentation has been updated to match any changes to the build system
[x] Ready to merge

Summary

What does the PR accomplish, why was it needed?
Fix CVE-2024-10963 with a patch that came out of upstream issue: https://github.com/linux-pam/linux-pam/pull/854
Change Log

CVE-2024-10963

Does this affect the toolchain?

NO
Links to CVEs

https://nvd.nist.gov/vuln/detail/CVE-YYYY-XXXX

Test Methodology

Pipeline build id: https://dev.azure.com/mariner-org/mariner/_build/results?buildId=689838&view=results

Auto cherry-pick results:

3.0-dev :white_check_mark: -> https://github.com/microsoft/azurelinux/pull/11461

Auto cherry-pick pipeline run -> https://dev.azure.com/mariner-org/mariner/_build/results?buildId=693933&view=results


Activating Open Collective

This pull request adds backers and sponsors from your Open Collective https://opencollective.com/lwjgl ❤
It adds two badges at the top to show the latest number of backers and sponsors. It also adds placeholders so that the avatar/logo of new backers/sponsors can automatically be shown without having to update your README.md. [more info]. See how it looks on this repo.
You can also add a "Donate" button to your website and automatically show your backers and sponsors there with our widgets. Have a look here: https://opencollective.com/widgets
P.S: As with any pull request, feel free to comment or suggest changes. The only thing "required" are the placeholders on the README because we believe it's important to acknowledge the people in your community that are contributing (financially or with code!).
Thank you for your great contribution to the open source community. You are awesome! 🙌
And welcome to the open collective community! 😊
Come chat with us in the #opensource channel on https://slack.opencollective.com - great place to ask questions and share best practices with other open source sustainers!

First link 404's. Anybody know what this is?

Updated the first link. Our automated script picks up the default repo name and I thought it would make more sense to use the general name. We can change it easily. It looks like @Spasi signed up for Open Collective.

The LWJGL page on Open Collective is now ready and this PR can be merged. Thank you @asood123.
If you're interested in becoming a backer or sponsor for LWJGL, the plan is to use donated funds:

to cover server hosting & bandwidth expenses (currently ~$30 per month)
to cover software & hardware expenses
to offer bounties for documentation work (priorities: adding EGL & GLES javadoc, updating GL)
to offer bounties for new bindings
to offer bounties for new platform ports (priorities: ARM/Android)


Logger setup

 Here is an overview of what got changed by this pull request:

Issues
======
+ Solved 1
- Added 5

Complexity increasing per file
==============================
- src/In.ProjectEKA.OtpService/Otp/Logger/Log.cs  1
- src/In.ProjectEKA.HipService/Logger/Log.cs  1

Clones added
============
- src/In.ProjectEKA.HipService/Link/LinkPatientRepository.cs  2
- src/In.ProjectEKA.HipService/Program.cs  1
- src/In.ProjectEKA.OtpService/Otp/Logger/Log.cs  1
- src/In.ProjectEKA.OtpService/Program.cs  1
- src/In.ProjectEKA.HipService/Logger/Log.cs  1

See the complete overview on Codacy

 Here is an overview of what got changed by this pull request:

Issues
======
+ Solved 1
- Added 5

Complexity increasing per file
==============================
- src/In.ProjectEKA.HipService/Logger/Log.cs  1
- src/In.ProjectEKA.OtpService/Otp/Logger/Log.cs  1

Clones added
============
- src/In.ProjectEKA.HipService/Logger/Log.cs  1
- src/In.ProjectEKA.OtpService/Program.cs  1
- src/In.ProjectEKA.HipService/Link/LinkPatientRepository.cs  2
- src/In.ProjectEKA.HipService/Program.cs  1
- src/In.ProjectEKA.OtpService/Otp/Logger/Log.cs  1

See the complete overview on Codacy

 Here is an overview of what got changed by this pull request:

Issues
======
+ Solved 1

Complexity increasing per file
==============================
- src/In.ProjectEKA.OtpService/Otp/Logger/Log.cs  1
- src/In.ProjectEKA.HipService/Logger/Log.cs  1

Clones added
============
- src/In.ProjectEKA.HipService/Link/LinkPatientRepository.cs  2
- src/In.ProjectEKA.OtpService/Otp/Logger/Log.cs  1
- src/In.ProjectEKA.OtpService/Program.cs  1
- src/In.ProjectEKA.HipService/Program.cs  1
- src/In.ProjectEKA.HipService/Logger/Log.cs  1

See the complete overview on Codacy

 Here is an overview of what got changed by this pull request:

Issues
======
+ Solved 1

Complexity increasing per file
==============================
- src/In.ProjectEKA.HipService/Program.cs  1
- src/In.ProjectEKA.OtpService/Otp/Logger/Log.cs  1
- src/In.ProjectEKA.HipService/Logger/Log.cs  1
- src/In.ProjectEKA.OtpService/Program.cs  1

Clones added
============
- src/In.ProjectEKA.HipService/Program.cs  1
- src/In.ProjectEKA.OtpService/Otp/Logger/Log.cs  1
- src/In.ProjectEKA.HipService/Link/LinkPatientRepository.cs  2
- src/In.ProjectEKA.HipService/Logger/Log.cs  1
- src/In.ProjectEKA.OtpService/Program.cs  1

See the complete overview on Codacy

 Here is an overview of what got changed by this pull request:

Issues
======
+ Solved 1

Complexity increasing per file
==============================
- src/In.ProjectEKA.HipService/Logger/Log.cs  1
- src/In.ProjectEKA.OtpService/Program.cs  1
- src/In.ProjectEKA.OtpService/Otp/Logger/Log.cs  1
- src/In.ProjectEKA.HipService/Program.cs  1

Clones added
============
- src/In.ProjectEKA.HipService/Logger/Log.cs  1
- src/In.ProjectEKA.OtpService/Program.cs  1
- src/In.ProjectEKA.HipService/Link/LinkPatientRepository.cs  2
- src/In.ProjectEKA.OtpService/Otp/Logger/Log.cs  1
- src/In.ProjectEKA.HipService/Program.cs  1

See the complete overview on Codacy

 Here is an overview of what got changed by this pull request:

Issues
======
+ Solved 1

Complexity increasing per file
==============================
- src/In.ProjectEKA.HipService/Program.cs  1
- src/In.ProjectEKA.OtpService/Otp/Logger/Log.cs  1
- src/In.ProjectEKA.OtpService/Program.cs  1
- src/In.ProjectEKA.HipService/Logger/Log.cs  1

Clones added
============
- src/In.ProjectEKA.HipService/Link/LinkPatientRepository.cs  2
- src/In.ProjectEKA.HipService/Program.cs  1
- src/In.ProjectEKA.OtpService/Otp/Logger/Log.cs  1
- src/In.ProjectEKA.OtpService/Program.cs  1
- src/In.ProjectEKA.HipService/Logger/Log.cs  1

See the complete overview on Codacy

 Here is an overview of what got changed by this pull request:

Issues
======
+ Solved 1

Complexity increasing per file
==============================
- src/In.ProjectEKA.HipService/Logger/Log.cs  1
- src/In.ProjectEKA.OtpService/Otp/Logger/Log.cs  1
- src/In.ProjectEKA.HipService/Program.cs  1
- src/In.ProjectEKA.OtpService/Program.cs  1

Clones added
============
- src/In.ProjectEKA.HipService/Logger/Log.cs  1
- src/In.ProjectEKA.OtpService/Otp/Logger/Log.cs  1
- src/In.ProjectEKA.HipService/Link/LinkPatientRepository.cs  2
- src/In.ProjectEKA.HipService/Program.cs  1
- src/In.ProjectEKA.OtpService/Program.cs  1

See the complete overview on Codacy

 Here is an overview of what got changed by this pull request:

Issues
======
+ Solved 1

Complexity increasing per file
==============================
- src/In.ProjectEKA.HipService/Logger/Log.cs  1
- src/In.ProjectEKA.OtpService/Program.cs  1
- src/In.ProjectEKA.HipService/Program.cs  1
- src/In.ProjectEKA.OtpService/Otp/Logger/Log.cs  1

Clones added
============
- src/In.ProjectEKA.HipService/Logger/Log.cs  1
- src/In.ProjectEKA.OtpService/Program.cs  1
- src/In.ProjectEKA.HipService/Program.cs  1
- src/In.ProjectEKA.OtpService/Otp/Logger/Log.cs  1

See the complete overview on Codacy


Change end state logic

Changes I made in https://github.com/keyme/kiosk/pull/14890
It will run final state until it returns None

LGTM


Enhance scene tabs

show scene thumbnail on hover
resize if has many tabs
show full scene file name with current edited scene
can be customized EditorSettings > Interface > Scene Tab

awesome work, as alwasy :D
is the thumbnail toggable? can the delay be changed?

@nunodonato yes. it can be toggle in editor settings. but there is nothing about delay.

It would be nice to also have middle-click close and a hover effect, but that's awesome already :)

@Zylann oh, I'd thought about that too, but forgot. I will check it later.

@Zylann closing scene with mouse middle button is just added. :)
@akien-mga updated commit.

When you change the theme in the editor the tabs stay the same, you need to restart the editor.
Was this always the case or did this PR cause this?

Wow, it's awesome! Would be great if we could reposition tabs as well :D

@karroffel I will check that.
@kubecz3k I checked about re-positioning tabs, but it was too complicated.

@volzhs I would want to implement tab repositioning, would be cool if you could drop me some tips :)


Add support for asdf

Description

This adds support for the ruby version manager asdf. This follows the same method of version detection as spaceship
Motivation and Context

Closes #35
Types of changes

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

Screenshots (if appropriate):

How Has This Been Tested?

[x] I have tested using MacOS
[ ] I have tested using Linux

Checklist:

[x] I have checked that no other PR duplicates mine
[x] My code follows the code style of this project.
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[ ] I have updated the tests accordingly.

No problem! Thanks for the quick merges! 😄


Keystone auth doesn't work with a custom CA

It looks like there is a mismatch between the expectations of the keystoneauth
Helm chart: https://github.com/vexxhost/magnum-cluster-api/blob/main/magnum_cluster_api/charts/k8s-keystone-auth/values.yaml#L20 and the way it is being set up: https://github.com/vexxhost/magnum-cluster-api/blob/main/magnum_cluster_api/resources.py#L416 (ca_file vs ca_cert).
Whilst the Helm chart may work if the file contents are passed in, this seems unnecessary as the nodes should already have this file in /etc/kubernetes/cloud_ca.crt and could just mount it as in https://github.com/vexxhost/magnum-cluster-api/blob/main/magnum_cluster_api/utils.py#L136.

@okozachenko1203 when you're back, can you please have a look at this and evaluate which fix is the best?
Also, maybe we can try and figure out what kind of CI we can to avoid introducing some kind of regression.  I think long term, it would be better to start avoiding creating files on the host and rely on secrets that are mounted because those we can easily fix/change as opposed to editing files directly on disk that are host mounted.

@andrewbonney thanks for your report.
I'll just fix the key field of helm value. Helm chart renders a secret using ca_cert and mount it into daemonset already.
https://github.com/vexxhost/magnum-cluster-api/blob/main/magnum_cluster_api/charts/k8s-keystone-auth/templates/daemonset.yaml#L48-L51
https://github.com/vexxhost/magnum-cluster-api/blob/main/magnum_cluster_api/charts/k8s-keystone-auth/templates/daemonset.yaml#L63-L65
https://github.com/vexxhost/magnum-cluster-api/blob/main/magnum_cluster_api/charts/k8s-keystone-auth/templates/daemonset.yaml#L77-L80
https://github.com/vexxhost/magnum-cluster-api/blob/main/magnum_cluster_api/charts/k8s-keystone-auth/templates/secret-ca.yaml
On the other side, keeping ca crt file on node fs is a mcapi-specific implementation so it would be good to keep k8s-keystone-auth helm chart as standalone for loosely coupling.

No problem. I've closed #435 and will leave #436 for review.


feat(leadspace-with-search): update to v2

Related Ticket(s)
#10787
Description
Note: We have to merge the Leadspace v2 PR first
This PR introduces many changes to the Leadspace with Search component.
The greatest change is the removal of many of its sub-components, now just using leadspace-heading and leadspace-with-search-copy for its text content.
Changelog
New

leadspace with search also supports the heading highlight

Changed

cleaned up the scss styles

Removed

Removed <dds-leadspace-with-search-heading>, <dds-leadspace-with-search-content>,
<dds-leadspace-with-search-content-heading>, <dds-leadspace-with-search-content-copy>
No more image leadspace with search variant

On Friday Sep 30, @IgnacioBecerra and I discussed simplifying the Adjacent theme knob.
Currently we offer five adjacent theme options.

and the adopter can also change the page theme (or Carbon theme in storybook) which causes some conflicts and criss crossing of theming tokens, resulting in blue 60 text on gray 90 and mixing dark and light theme backgrounds in some cases.

In v11, we have the ability to inline theme so we only need to provide two adjacent theme options

Mono theme
Dual theme
And the adopters can then choose if the lead space theme, which will result in all the correct color values, and the remaining page can be whatever they choose, even white.


Files crashes when opening Downloads

Description
When I try to open Downloads in Files, it freezes, shows the notification below, and then closes the window.

Steps To Reproduce
No response
Expected behavior
Files should not crash and allow me to browse my Downloads
Files Version
Version: <IP_ADDRESS> OS Version: 10.0.22543.1000
Windows Version
Edition	Windows 11 Pro Insider Preview Version	Dev Installed on	2022-02-15 OS build	22543.1000 Experience	Windows Feature Experience Pack 1000.22543.1000.0
Relevant Assets/Logs
debug_fulltrust.log
debug.log

What if you turn off the option to show folder sizes?

Merging with #8413


Postgres Scanner support of Table Dee/Dum

In postgres
foo=# create database deedum; CREATE DATABASE foo=# \c deedum psql (15rc2, server 14.5) You are now connected to database "deedum" as user "benji". deedum=# CREATE TABLE dum(); CREATE TABLE deedum=# CREATE TABLE dee(); CREATE TABLE deedum=# INSERT INTO dee DEFAULT VALUES; INSERT 0 1
In duckdb
D install postgres_scanner; D load postgres_scanner; D call postgres_attach('dbname=deedum'); Error: INTERNAL Error: INTERNAL Error: Failed to bind "postgres_scan": Table function must return at least one column
Expected: Database to attach and tables dee and dum to be queryable.
I was trying to work around duckdb not allowing creation of table dee/dum natively by connecting to a postgres database containing table dee/dum.

Interesting way to work around this


[Workflow] CodeQL Analysis to detect security issues

Signed-off-by: Taewan Kim<EMAIL_ADDRESS>Description
Add a CodeQL Analysis workflow to detect security issues with respect to source code
Fixes #190
Type of change

[x] New feature (non-breaking change which adds functionality)

How Has This Been Tested?
Open PR and see Actions workflows
Result

Test Configuration:

Edge Orchestration Release: Coconut

Checklist:

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] New and existing unit tests pass locally with my changes

@suresh-lc @tdrozdovsky PTAL...

@MoonkiHong @t25kim Sorry for the delay, but I really haven't fully understood the proposal yet.
perhaps we will duplicate the search for vulnerabilities because:
CodeQL is the product that powers LGTM's community-driven security analysis. LGTM's analysis relies on queries written using CodeQL to check your code for security vulnerabilities, bugs, and errors. You can customize your LGTM analysis by writing custom queries that are specific to your project.
@t25kim Please share your thoughts, maybe I'm wrong. Overall, I like your proposal.

@MoonkiHong @t25kim Sorry for the delay, but I really haven't fully understood the proposal yet.
perhaps we will duplicate the search for vulnerabilities because:
CodeQL is the product that powers LGTM's community-driven security analysis. LGTM's analysis relies on queries written using CodeQL to check your code for security vulnerabilities, bugs, and errors. You can customize your LGTM analysis by writing custom queries that are specific to your project.
@t25kim Please share your thoughts, maybe I'm wrong. Overall, I like your proposal.

@tdrozdovsky This proposal also suggests to integrate its automated analysis per every PR, which is not yet facilitated from our community. ^^

@MoonkiHong @t25kim Sorry for the delay, but I really haven't fully understood the proposal yet.
perhaps we will duplicate the search for vulnerabilities because:
CodeQL is the product that powers LGTM's community-driven security analysis. LGTM's analysis relies on queries written using CodeQL to check your code for security vulnerabilities, bugs, and errors. You can customize your LGTM analysis by writing custom queries that are specific to your project.
@t25kim Please share your thoughts, maybe I'm wrong. Overall, I like your proposal.

@tdrozdovsky This proposal also suggests to integrate its automated analysis (any additional security vulnerability issues) per every PR before merged, which is not yet facilitated from our community. ^^

Yes, this is exactly what I like compared to LGTM when we see vulnerabilities after.

@MoonkiHong, @tdrozdovsky Thanks for the reivews!

perhaps we will duplicate the search for vulnerabilities because:

I think so. The advantage is that it checks security issues of each PR through code scanning automatically before merged. so I opened the issue to see community feedback if it is necessary or not.
How about merging this PR and seeing if it's useful?

@t25kim @MoonkiHong This is a great idea, and as I wrote earlier, I really like it. In any case, I think it is necessary to try.
Let's try)))


subscribe to logged in user changes, refresh jwt token

the flow should look like this:

sequenceDiagram
    Client-)API: Subscribe logged in user
    Client->>API: User changed
    API-->>Client: User updated (from subscription)
    Client->>API: Refresh jwt
    API-->>Client: set cookie
    Client->>SvelteKit: invalidate user
    SvelteKit-->>Client: new user details from cookie

[ ] subscribe to user changes
[x] refresh jwt
[x] invalidate user

this is currently blocked on hotchocolate not currently supporting subscriptions with schema stitching (it's supposed to be coming soon?) If it doesn't make it we can probably use Hasura for our schema federation/stitching.

Not needed anymore as we automatically refresh in many cases


Bump LossFunctions.jl

Appreciate if you can bump the version of LossFunctions.jl. It is holding downstream packages from updating.

Codecov Report

Merging #773 (403d891) into dev (75b391b) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##              dev     #773   +/-   ##
=======================================
  Coverage   85.92%   85.92%
=======================================
  Files          36       36
  Lines        3460     3460
=======================================
  Hits         2973     2973
  Misses        487      487

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 75b391b...403d891. Read the comment docs.

Thank you @OkonSamuel appreciate if you can release a new patch release.


NETOBSERV-1772: allow prom label remapping

Description

Add "remap" to FlowMetrics CRD
Add examples with DNS requests/responses
Some variables renamed for more clarity

Dependencies
FLP: https://github.com/netobserv/flowlogs-pipeline/pull/698
Checklist
If you are not familiar with our processes or don't know what to answer in the list below, let us know in a comment: the maintainers will take care of that.

[x] Is this PR backed with a JIRA ticket? If so, make sure it is written as a title prefix (in general, PRs affecting the NetObserv/Network Observability product should be backed with a JIRA ticket - especially if they bring user facing changes).
[ ] Does this PR require product documentation?

[ ] If so, make sure the JIRA epic is labelled with "documentation" and provides a description relevant for doc writers, such as use cases or scenarios. Any required step to activate or configure the feature should be documented there, such as new CRD knobs.

[x] Does this PR require a product release notes entry?

[ ] If so, fill in "Release Note Text" in the JIRA.

[ ] Is there anything else the QE team should know before testing? E.g: configuration changes, environment setup, etc.

[ ] If so, make sure it is described in the JIRA ticket.

QE requirements (check 1 from the list):

[x] Standard QE validation, with pre-merge tests unless stated otherwise.
[ ] Regression tests only (e.g. refactoring with no user-facing change).
[ ] No QE (e.g. trivial change with high reviewer's confidence, or per agreement with the QE team).

/hold
requires https://github.com/netobserv/flowlogs-pipeline/pull/698 to be merged, and vendors updated

/unhold


How to perform a North test on the EOF?

Hi,
Thanks for developing this wonderful package, I am using it for the eof analysis on europe.
I want to perform a north test on the EOF modes, and I don't know the difference between the significance test based on bootstrap from this documentation (https://xeofs.readthedocs.io/en/latest/auto_examples/3validation/plot_bootstrap.html), will they have the same effect on the significant test?
Best,
Cheng

Hi @SHEN-Cheng , in general I don't think that North's rule of thumb will give you the same result as bootstrapping. North's rule makes some (strong) assumptions of you underlying data:

Large sample size: Since it is based on the Central Limit Theorem the approximation works well for many samples which are independent and identically distributed. So take care of temporal autocorrelation when estimating the number of samples.
Gaussian distribution: The approximation is derived under the assumption that the data can be approximated by a Gaussian (normal) distribution. This simplifies the mathematics but may not always be strictly true in practical datasets (e.g. precipitation)
Stationarity: The data should be stationary, meaning that its statistical properties do not change over time. So, no trends, no seaonal cycle.
Homoscedastic noise: The rule assumes constant variance in the sampling error.

In contrast, bootstrapping does not require you to assume 2. and 4. since it is a non-parametric approach. In addition, 1. and 3. can be accounted for when using specific resampling techniques, however xeofs only provides a very simple bootstrapping scheme where 1. and 3. are assumed to be true.
Does that answer your question?

Hi @SHEN-Cheng , in general I don't think that North's rule of thumb will give you the same result as bootstrapping. North's rule makes some (strong) assumptions of you underlying data:

Large sample size: Since it is based on the Central Limit Theorem the approximation works well for many samples which are independent and identically distributed. So take care of temporal autocorrelation when estimating the number of samples.
Gaussian distribution: The approximation is derived under the assumption that the data can be approximated by a Gaussian (normal) distribution. This simplifies the mathematics but may not always be strictly true in practical datasets (e.g. precipitation)
Stationarity: The data should be stationary, meaning that its statistical properties do not change over time. So, no trends, no seaonal cycle.
Homoscedastic noise: The rule assumes constant variance in the sampling error.

In contrast, bootstrapping does not require you to assume 2. and 4. since it is a non-parametric approach. In addition, 1. and 3. can be accounted for when using specific resampling techniques, however xeofs only provides a very simple bootstrapping scheme where 1. and 3. are assumed to be true. Does that answer your question?

Hi @nicrie, thank you for your detailed explanination, I believe I will use the bootstrapping to do the significant test in my following analysis.


chore: sort packages after insert

<EMAIL_ADDRESS>does not sort packages after insertion.
As the result, @sveltejs/vite-plugin-svelte is placed in the last row.
{
  "devDependencies": {
    "@sveltejs/adapter-auto": "^3.0.0",
    "@sveltejs/kit": "^2.0.0",
    "eslint": "^8.55.0",
    "eslint-config-prettier": "^9.1.0",
    "eslint-plugin-svelte": "^2.35.1",
    "prettier": "^3.1.1",
    "prettier-plugin-svelte": "^3.1.2",
    "svelte": "^4.2.8",
    "svelte-check": "^3.6.2",
    "typescript": "^5.3.3",
    "vite": "^5.0.0",
    // Appended at the end. Not alphabetically sorted.
    "@sveltejs/vite-plugin-svelte": "^3.0.0"
  }
}

In this PR, dependencies and devDependencies are sorted alphabetically.
['dependencies', 'devDependencies'].forEach((key) => {
  if (key in pkg) {
    // Method used in the PR
    pkg[key] = Object.fromEntries(Object.entries(pkg[key]).sort());
    // Alternative
    pkg[key] = JSON.parse(JSON.stringify(pkg[key], Object.keys(pkg[key]).sort()));
  }
});

Migration Results Examples

TypeScript Template
JSDoc Template

Please don't delete this checklist! Before submitting the PR, please make sure you do the following:

[ ] It's really useful if your PR references an issue where it is discussed ahead of time. In many cases, features are absent for a reason. For large changes, please create an RFC: https://github.com/sveltejs/rfcs
[x] This message body should clearly illustrate what problems it solves.
[ ] Ideally, include a test that fails without this PR but passes with it.

Tests

[ ] Run the tests with pnpm test and lint the project with pnpm lint and pnpm check

Changesets

[x] If your PR makes a change that should be noted in one or more packages' changelogs, generate a changeset by running pnpm changeset and following the prompts. Changesets that add features should be minor and those that fix bugs should be patch. Please prefix changeset messages with feat:, fix:, or chore:.

I'd rather have it sorted to the end than reordering existing packages for people, making the diff harder to read. Can we make it so it's sorted in at the correct position but doesn't otherwise touch other packages?


search error

Does this issue occur when all extensions are disabled?: Yes/No

This problem occurs on the vscode server. Here is the version information.
Version: 1.91.1
Commit: f1e16e1e6214d7c44d078b1f0607b2388f29d729
Date: 2024-07-09T22:08:03.155Z
Browser: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/<IP_ADDRESS> Safari/537.36
Question one.
Steps to Reproduce:

Open https://vscode.dev/
Open any project
Open a file that is not in the current workspace
Open the search view and select Search only in  open Editors button
Search Keyword

Bug:

Select Search only in open Editors. No query result of other files, that is, the opened files are not queried.
Nothing Happens When the View as List and View as Tree Buttons Are Clicked

Question two.

Open https://vscode.dev/
Open any project
Open a file that is not in the current workspace
Open the search view and select Search only in  open Editors button
The edit area opens only other files, that is, other files are opened, but the files in the current work area are not opened.
Search Keyword

Bug:
No search result is displayed in the search box and an error is reported.

The edit area opens only other files, that is, other files are opened, but the files in the current work area are not opened.

This means that you open a file in the editing area that is not in the current workspace. You can refer to the file opened using the Open File... menu in the gif image.

Yes, I can reproduce both of these bugs. I'll need to see what's going on with these open files...

This might be fixed via https://github.com/microsoft/vscode/pull/224631. I will need to check once another insider's build is out.

It actually isn't solved via the above commit, it seems. Will need to investigate further.

Looking into this more, this happens because the opened file returns as !exists via the fileService.
@joyceerhl do you happen to know why this is happening?
Should this return false for out-of-workspace files in vscode.dev?
https://github.com/microsoft/vscode/blob/1f263631accb5a7edf51cfa220ae2f65d8feade2/src/vs/platform/files/common/fileService.ts#L320


Added => Maths_And_Stats => Algebra => Babylionian => Java

Assigned Issue Number ?
#1374
Language Opted ?
Java
Number of files added or updated ?
1
Name of these files ?
Maths_And_Stats =>Algebra=> Babylionian=>Babylionian.java
Checklist

[X] I've read the contribution guidelines.
[X] I've referred the correct issue number.
[X] I've fill up this entire template correctly.

Hi @ahampriyanshu, there is the change, thanks!


[GURPS] Translation Files Bug

There's a bug that's adding special characters to all the translation files.
GURPS/translation.json
Line #606
"modifier-label": "Modifier:",
When the system updates all the files under the translation folder, extra characters are added that are causing a display issue on the character sheet and the chat roll results.
Example
GURPS/translations/en.json
Line #606
"modifier-label": "Modifier:$[[3]] ",
The characters $[[3]] were added to each of the translation files.
Pull Request
#7445

Odd, so #7445 remove them, but Git Blame shows that it got added when the weekly translations script where applied to all Roll20 sheets by @oliviakristiansen in this commit. I assume this process involves pulling Translations from CrowdIn, and propagating translation changes on translation.json file to the language-specific files.
Digging a bit deeper, seems it was originally added in this July 28th commit by Olivia with the general sheet translation updates. The other thing changed on the GURPS translation in the commit was "Rad"->"Rads", so I think the $[[3]] could originate from someone updating the "Rads" word and mistakenly adding the $[[3]] as well.
I'd assume this is part of the reason translation change are recommended to be submitted through CrowdIn, after the translation keys are created.
#Suspected Cause
Regarding why it keeps getting re-added, I think it's a bug in Roll20's translation update script, as I've seen this back and forth happen previously with other sheets.
What I remember thinking the last time similar reverts happened, that it seemed to happen when you made changes to both the translations files(translation.json & all the version in /translations) & the sheet code in the same week, the "translation update" by Roll20 would partially overwrite changes to translations based on the "old" version, presumably coming from CrowdIn. I never confirmed anything, but fairly certain this general issue have been around for at least 2 years, but have been so small and infrequent that nothing have really been done about it.
If I end up digging up past occurrences and get more insight on this, I'll submit a support ticket to Roll20 so they have a proper case to look at and maybe get it fixed.

Through CrowdIn, I submitted a translation changed for English to change Modifier:$[[3]]  to Modifier:, which hopefully overrides whatever is making this thing return each week.
If that works out, I'll try to submit the changes to the rest of the languages  so it gets competently removed.
If you want to get access to the CrowdIn Translation tools for the future, send a request email to<EMAIL_ADDRESS>

Thank you @Anduh !

It seems my CrowdIn change to the translations removed the pesky $[[3]] on line 606.
If you can verify in a game that it's fixed, you could close this issue.

@Anduh  thank you! It's fixed.


Turn off colors when logging to a file

I want to collect logs from many kinds of nodes, but when I look at the log files, they're filled with unreadable ANSI escape codes!
$ ansible --become all -a "docker run -it --net host --pid host --cap-add audit_control -v /var/lib:/var/lib -v /var/run/docker.sock:/var/run/docker.sock -v /usr/lib/systemd:/usr/lib/systemd -v /etc:/etc --label docker_bench_security docker/docker-bench-security -l /tmp/docker-security.txt"

# success

# ssh into node

$ less /tmp/docker-security.txt
ESC[1;34m[INFO]ESC[0m 1 - Host Configuration
ESC[1;31m[WARN]ESC[0m 1.1  - Create a separate partition for containers
ESC[1;32m[PASS]ESC[0m 1.2  - Use an updated Linux Kernel
ESC[1;31m[WARN]ESC[0m 1.4  - Remove all non-essential services from the host - Network
ESC[1;31m[WARN]ESC[0m      * Host listening on: 35 ports
ESC[1;32m[PASS]ESC[0m 1.5  - Keep Docker up to date

Hi again @siddharthist, I believe this is a duplicate of #85 and, if possible, use more instead of less to fix the log output.

@konstruktoid Sorry, didn't see the other issue!


Report unused import when parent reference is already present

This PR fixes the issue #405

While traversing nodes and building ref,  built a set of non redundant imports which omits the imports where parent reference is already present.
Imports with aliases should contain both name and alias in the importSet
Static function call and variable have been distinguised

@sowmyav24 thanks for the PR! A couple requests:

would be great to add a few comments into the code - we're trying to slowly add comments into the standard ruleset since they make great examples for others trying to write their own custom rules
I don't know why it wouldn't work, but can you add some tests to ensure auto-formatting works properly for these unused parent imports?

@shashachu Thank you for the feedback.

Added a test to ensure auto formatting works for parent imports.
Added comments for the functions introduced. Let me know if needs to be more descriptive.

Thanks for the fixes!


Improve snippet usability

This may be pretty subjective, but as a long time user of this extension, the built-in snippets for let and with are pretty annoying in that they don't add a space to the end of the expansion and don't move the cursor there.
I believe there are two common use cases for the snippets, both of which are not very pleasant with the current version:

writing a new expression:

let<tab>

... which gets expanded to
let |;
in

... to which I add my desired bindings. Now I want to continue after the in, but I can't without manually moving my cursor there.

modifying an existing expression:

let<tab>{
    ...
}

... which gets expanded to
let |;
in{
    ...
}

... to which I add my desired bindings. Now I have to move after the in and add a space, so the code looks nice. (yeah, this is kinda a job for a formatter, but I'm not satisfied with any of the currently available for nix)
Pretty much the same applies to with.
The proposed fix makes both of these use cases much more pleasant without being too annoying for any other. The only degradation I can think of is for people who like to keep the in/with on separate lines and don't have trailing whitespace trimming on, who would now have to delete the space manually. Still, that is just one extra keypress, so it's probably not too bad.

Currently, it follow the order of assignment, one first writes the name of the variable before assigning it to a value.
Lets see if anyone is interested in setting it this way by default.

is there anything else I should change before this can move forward?

LGTM, Thanks @frantisekhanzlikbl !


Slack us feedback link closed

Describe the bug
The current linked used in the Slack us Feedback in the banner on the workflows page is now inactive
To Reproduce
Steps to reproduce the behavior. Think about:

Navigate to Workflows
Have the banner expanded
Click on Slack us Feedback

Expected behavior
Be taken to the flow channel in Slack or ask to join
Additional context
"from": "https://join.slack.com/t/boomerang-io/shared_invite/zt-f1j2szfp-90s6mAud11PxoIKeKCr2og",
"to": "https://join.slack.com/t/boomerang-io/shared_invite/zt-pxo2yw2o-c3~6YvWkKNrKIwhIBAKhaw",

Hey @tlawrie - @Okisa pointed out that the new slack join link also appears to no longer be active

Interesting. I have it set to never expire and I copied the link again and it still is using https://join.slack.com/t/boomerang-io/shared_invite/zt-pxo2yw2o-c3~6YvWkKNrKIwhIBAKhaw

@Okisa what do you get when you try that link?

@tlawrie Now the links are working, I'll update the app to use it.

@BenjaminRuby PR Opened here: https://github.com/boomerang-io/flow.client.web/pull/48


Default permissions on Dropbox folder less than ideal

Describe the bug
When setting up Maestral, the app asks for a save-location for the "Dropbox (Maestral)" folder. By default this is in the user's home directory. Regardless of whether the app creates the folder, or the user choses to create it on their own, in both cases the folder ends up with a permission set of "drwxr-xr-x", while all other top-level folders are "drwx------" by default. This means that everyone on the machine has read permissions to the Dropbox folder.
I discovered this while searching for something in another user account and files from my Dropbox showed up in their Spotlight results.
By default, I would support Maestral changing permissions to match the other top level folders in the user's home directory.
To Reproduce
Set up Maestral on a new machine. Use the default directory suggestion in the home folder. After the folder has been created, compare folder permissions between Documents and Dropbox folder for example.
Expected behaviour
The Dropbox folder should only be accessible by the current user.
System:

Maestral version: 1.6.3
Python version: 3.10
OS: [e.g. Ubuntu] macOS 12.4
Desktop environment: [e.g. Gnome 3.32]
PyQt version (for Linux GUI):

Additional context
I guess the current behavior is the default, because creating a folder manually also applies read permissions for everyone by default. But I don't remember the official Dropbox app exposing all my files to other users...

I don't like messing with permissions if a user selects an existing folder, this could lead to unintended consequences. Similarly, Maestral does not make any assumptions about where the Dropbox folder is located, it may well be deliberately in a shared location. In this case, we do want to follow the permissions set up already for that location. Therefore, respecting the default permissions for the user and the location makes sense to me.


⚠ Heritage of Faith Christian Church - Gold Coast has degraded performance

In 370d7bf, Heritage of Faith Christian Church - Gold Coast (https://heritageoffaith.com.au) experienced degraded performance:

HTTP code: 200
Response time: 28531 ms

Resolved: Heritage of Faith Christian Church - Gold Coast performance has improved in 1bde811.


Tidy up StorageManifestVHS, and error if you try to put a different record than already exists

From #3629

Done.


hope support multiple module/function filter for traces [JIRA: RIAK-1778]

for example :
{{lagger_file_backend, "a.log"}, [{module, [m_a, m_b]}], info}
and
{{lagger_file_backend, "b.log"}, [{module, ma},{function, [fa, fb]}], debug}

I don't think this is supported by goldrush.


Implement SerDes module and make adoptation of eMMC HC for SerDes module

We have to design SerDes module which will transfer eMMC Host Controller signals between the Parallella and Artix boards, where eMMC HC will be working in 4bit SDR mode. We are already started SerDes module in issue #17 where we have started transferring command line and now needed to fix the data line signals exchange in issue #19

Now eMMC HC working with 4bit SDR mode, here is linux output:

Last login: Thu Jun  1 02:54:56 UTC 2017 on ttyPS0
root@linaro-developer:~# lsblk
NAME         MAJ:MIN RM   SIZE RO TYPE MOUNTPOINT
mmcblk1rpmb  179:32   0     4M  0 disk
mmcblk1boot0 179:16   0     4M  1 disk
mmcblk1boot1 179:24   0     4M  1 disk
mmcblk0      179:0    0    15G  0 disk
├─mmcblk0p1  179:1    0 287.1M  0 part
└─mmcblk0p2  179:2    0  14.7G  0 part /
mmcblk1      179:8    0  14.7G  0 disk
├─mmcblk1p1  179:9    0  96.3M  0 part
└─mmcblk1p2  179:10   0   3.7G  0 part
root@linaro-developer:~# mount /dev/mmcblk1p2 /mnt/
root@linaro-developer:~# umount /mnt/
root@linaro-developer:~# hdparm -t /dev/mmcblk1

/dev/mmcblk1:
Timing buffered disk reads:  66 MB in  3.03 seconds =  21.75 MB/sec

In issue #23 we are going to improve this module


Loop timers

Hey guys, I was updating loop timers when right off the bat I noticed some just freeze the extension. My syntax should be correct, are there any limitations or exceptions to the system? @kylechu
https://github.com/JdotCarver/Animal-Crossing-Music-Extension/blob/Updating-loop-timers/scripts/LoopTimes.js

Which ones are freezing it? Those look like they should all work - I'll test them out when I wake up.

Simply the ones that are in commentary. As soon as I disable the commentary tags it freezes the extension and you can't play any of the music. That's why I found it weird, it affects way more than I thought it would so I don't really understand.

You might want to check the documentation for set timeout. Some of the resolutions you have set look very tight. I wonder if perhaps it's an issue with how precise your time markers are.
Harold Houchin

On Feb 15, 2016, at 7:36 AM, JdotCarver<EMAIL_ADDRESS>wrote:
Simply the ones that are in commentary. As soon as I disable the commentary tags it freezes the extension and you can't play any of the music. That's why I found it weird, it affects way more than I thought it would so I don't really understand.
—
Reply to this email directly or view it on GitHub.

Thing is they all are triple digit precision and the one that Kylechu already implemented work fine. And the first three work fine too whereas they all are equally precise.

You had a few numbers formatted incorrectly. Javascript doesn't recognize numbers with unnecessary leading zeros. For example, you can't type "00.32", you would need to use either "0.32" or ".32". Additionally, you can't structure the end time as "1.29.519" on line 44. The number represents seconds, not a timecode - you would want "89.519".
Also, "24" isn't a valid hour - the times are zero indexed and go from 0-23. You likely either mean for that to be 0, or all of your hour values are shifted one value too high.

The reason why it was killing everything is because AudioManager is making the assumption that a "loopTimes" object exists when it attempts to play a song. Since the invalid numbers were causing a parsing error when creating that object, loopTimes === undefined and AudioManager crashes when it attempts to check the attributes of the nonexistent object.
I could change it so AudioManager will play regardless and only looping will break, but personally, I feel like it's better as it is now than to have it silently fail if someone messes up a loop time.

I made a pull request with the fixes I mentioned - #19
Also, in the future if you have issues like this, I highly recommend using the web inspector for the background page. It makes it easy to track down the causes of simple bugs - that's how I tracked down what was causing this error. You can get to it through a link in the Manage Extensions page.

Thank you so much. <3
Though you didn't need to do a pull request I could've corrected it myself Haha, and these were only the first few, I am still doing the rest.

I had already gone through and corrected them so I could test whether that was the problem - doing the pull request only took about five seconds and I figured I might as well save you the trouble of redoing the work.
So this bug can be closed?


logNow not found and problem with the win32 api

Hi there is a problem with missing logNow dependencie and the win32 api

give me some  min

It's fun to occasionally look back at my old code and see how my programming skills started. Wow, that was definitely spaghetti code! xD
But hey, it still did what it had to do!

fix

fix

Awesome, thanks for fixing.
I think thats an awesome project for starting :)

Unfortunately, it no longer seems to work,
the key combination is only recognized intermittently and I can't understand exactly what the trigger is.
In addition, the messages in the chat are blocked because entries are made too quickly

Its running ;)
Only have to set the sleep time up to 4 seconds in chat messages ;)

if you code raid one base pls let me know !!


Update sbt-docker to 1.8.2

Updates se.marcuslonnberg:sbt-docker from 1.5.0 to 1.8.2.
GitHub Release Notes - Changelog - Version Diff
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "se.marcuslonnberg", artifactId = "sbt-docker" } ]

labels: sbt-plugin-update, semver-minor

Superseded by #774.


ATAC-seq vs DNaseI-seq

Dear authors,
As ATAC and DNaseI assess open regions of the genomes, would a model trained on ATAC+(other epigenetic 1D maps mentioned in the Epiphany paper) be better suited than DNaseI for the prediction of HiC contact maps?
I am very interested in using Epiphany to predict contact maps in different subtypes of B lymphocytes (which GM12878 is). However, the high DNA input required by DNaseI-seq is limiting; 10-50 million cells. Whereas, ATAC-seq needs just 50k and can also go down to scATAC-seq scalings too.
I presume the main model presented in the paper would also perform great with ATAC instead of DNase too. However, with limited computing resources, my side can generate the ATAC-seq data for GM12878 BUT cannot train it, together with the other epigenetic 1D maps, for a fine-tuned/revised model.
I was also desperate to just fit the ATAC-seq bigwig file, as a pseudo-DNaseI file, for prediction on your Google Collab python notebook too. Maybe I will go ahead with this and see if the predictions differ much from the original runs that used DNaseI-seq.
BTW, I was wondering if your side has a model trained on (ATAC,CTCF, H3K27ac, H3K27me3, H3K4me3) that is available for the community to use too. Thanks much for reading thru this lengthy post!

Hi Jingquanlim,
Thank you for your interest and sorry for the late response!
Yes using ATAC-seq instead of DNaseI is very much recommended. The major goal of Epiphany is to build a bridge between the epigenomic signals and the 3D chromatin structures, where people could explore the effects of epigenomic perturbations to the 3D structure changes, or use feature attribution with a well-trained model to identify specific region of interest for biological discoveries.
We encourage people to play with the model and retrain with various combinations of epigenomic tracks as input (as long as they're stored in the typical .bw format). In the paper we have trained the model with an example input epigenomic set, but indeed, a customized set of epi tracks could also be used to make predictions.
For the check points, we have multiple different combinations, including

original input: DNaseI + H3K27ac + H3K27me3 + H3K4me3 + CTCF
H3K27ac + H3K27me3 + H3K4me3 + CTCF
H3K37ac + CTCF
ATAC + H3K27ac + H3K27me3
ATAC + H3K36me3 + H3K27ac + H3K27me3
etc
Please let us know which ckpts could be useful for you, and we are also happy to help retrain the model with new combinations.

Thank you,
Rui


Issues while installing with laravel 5.3

When i am doing this
composer require genealabs/laravel-mixpanel
Its giving this error, i recently updated to 5.3, can anybody help me in that
Your requirements could not be resolved to an installable set of packages.

  Problem 1
    - Installation request for genealabs/laravel-mixpanel ^0.5.3 -> satisfiable by genealabs/laravel-mixpanel[0.5.3].
    - Conclusion: remove laravel/framework v5.3.18
    - Conclusion: don't install laravel/framework v5.3.18
    - genealabs/laravel-mixpanel 0.5.3 requires illuminate/routing 5.2.* -> satisfiable by illuminate/routing[v5.2.0, v5.2.19, v5.2.21, v5.2.24, v5.2.25, v5.2.26, v5.2.27, v5.2.28, v5.2
.31, v5.2.32, v5.2.37, v5.2.43, v5.2.45, v5.2.6, v5.2.7].
    - don't install illuminate/routing v5.2.0|don't install laravel/framework v5.3.18
    - don't install illuminate/routing v5.2.19|don't install laravel/framework v5.3.18
    - don't install illuminate/routing v5.2.21|don't install laravel/framework v5.3.18
    - don't install illuminate/routing v5.2.24|don't install laravel/framework v5.3.18
    - don't install illuminate/routing v5.2.25|don't install laravel/framework v5.3.18
    - don't install illuminate/routing v5.2.26|don't install laravel/framework v5.3.18
    - don't install illuminate/routing v5.2.27|don't install laravel/framework v5.3.18
    - don't install illuminate/routing v5.2.28|don't install laravel/framework v5.3.18
    - don't install illuminate/routing v5.2.31|don't install laravel/framework v5.3.18
    - don't install illuminate/routing v5.2.32|don't install laravel/framework v5.3.18
    - don't install illuminate/routing v5.2.37|don't install laravel/framework v5.3.18
    - don't install illuminate/routing v5.2.43|don't install laravel/framework v5.3.18
    - don't install illuminate/routing v5.2.45|don't install laravel/framework v5.3.18
    - don't install illuminate/routing v5.2.6|don't install laravel/framework v5.3.18
    - don't install illuminate/routing v5.2.7|don't install laravel/framework v5.3.18
    - Installation request for laravel/framework (locked at v5.3.18, required as 5.3.*) -> satisfiable by laravel/framework[v5.3.18].

Installation failed, reverting ./composer.json to its original content.

You can install the RC version like so:
genealabs/laravel-mixpanel:0.6.0-RC@dev

@mikebronner thanks man

@mikebronner is there a reason that the 0.6.0 requires PHP 7.0??? I'm toast now. I need to deploy a build of 5.3 and need to use 0.6.0 because the 5.x builds don't install. But our server doesn't have php 7.

Sorry for that @emergingdzns, but I am moving to PHP 7 with all plugins for the language advantages, as well as the performance and support. See http://php.net/supported-versions.php, PHP 5.x is no longer actively supported, only receives security fixes.


Release non-preview version of OperationalInsights

Resolves https://github.com/Azure/azure-sdk-for-net/issues/15558

@AlexGhiondea Could you please merge this PR too?


Analyser for checking that fields of disposable types are properly disposed

Added the class with proper comments.

Please write it in new format.


Catalog CSDMS Models in Hydroshare

[ ] Wrote script to pull metadata from CSDMS models and populate Hydroshare Model Programs through the REST API

[ ] Uploaded any resource files/documentation for each model (manually)

[ ] Listed correct authors for each resource, also through a script

@goodalljl Is this still relevant? If not please close.

Closing, no longer relevant as per @goodalljl .

Closing, no longer relevant as per @goodalljl .


Serenade Setup/Trial Issue

System Information
Serenade Version: e.g., v2.0.2
OS and Version: e.g., macOS 14.7 (Apple M1 Pro Chip)
Application: e.g., GoLand IDE (from JetBrains)
Issue Description
Dear Team,
I downloaded the Serenade MAC version from https://serenade.ai/download/ and want to try out this tool. But, I am not able to go past the below screen. I can confirm that I am on GoLand IDE (JetBrains), and also tried with VS Code.
System details:
Chip: Apple M1 Pro
macOS: Sonoma 14.7
Serenade: 2.0.2
I would appreciate your quick help on this.

How to Reproduce
Using above combination of Chip, OS and IDE.
Screenshots
Attached above.

Folks, providing you with an update that I have tried couple of times meanwhile. The latest time, also after upgrading to OS to Sonoma 14.7.1.
I can confirm that it's plugin for Goland (Jetbrains) is installed as well. But unfortunately, tool is still stuck.

Folks, providing you with an update that I have tried couple of times meanwhile. The latest time, also after upgrading to OS to Sonoma 14.7.1.
I tried explicitly installing its plugin for Goland (Jetbrains) is installed as well. But unfortunately, tool is still stuck.


[5.7] Fix OwnershipLiveRange for @owned values getting transformed to none values via switch_enum

Scope: Fixes possible verifier error while using switch on enums with dead ends on non-trivial paths
Main Branch PR:  https://github.com/apple/swift/pull/60101
Resolves: rdar://95039799
Risk: Very low
Reviewed By: Andrew Trick, Michael Gottesman
Testing: Added a regression test-case to the suite.

@swift-ci please nominate


Insane Corruptions On Joining World

When you join the world on minecraft while its opened in miex in the same time your pc will lag as hell, give over 10 errors, then generate broken and invisible chunks, then lag for like 20 seconds insanely, then will fix itself but invisible chunks wont get fixed unless you reload the world, thats a big problem if it even happens with a accident.

Minecraft worlds cannot be opened in two or more programs (like MiEx and Minecraft) at the same time. That's going to cause issues. MiEx does check when opening up a world if it's already opened up by another program, but I haven't been able to get Minecraft to check if MiEx has a world opened up.

Minecraft worlds cannot be opened in two or more programs (like MiEx and Minecraft) at the same time. That's going to cause issues. MiEx does check when opening up a world if it's already opened up by another program, but I haven't been able to get Minecraft to check if MiEx has a world opened up.

Bram, wheres the update for weeks bro? :( i need that dimension support for MiEx, i dont wanna use mineways!!!

Still working on Bedrock Edition support. It's just a lot of work. The goal is to have a new version out somewhere this month.
Regarding modded dimension support, that will be fixed in the next version, but for now a workaround could be to copy over the dimension's file into a new world folder where the overworld files would be, so that it essentially becomes the overworld. Then MiEx can open it up without any problems.

Minecraft worlds cannot be opened in two or more programs (like MiEx and Minecraft) at the same time. That's going to cause issues. MiEx does check when opening up a world if it's already opened up by another program, but I haven't been able to get Minecraft to check if MiEx has a world opened up.

Bram, wheres the update for weeks bro? :( i need that dimension support for MiEx, i dont wanna use mineways!!!

Still working on Bedrock Edition support. It's just a lot of work. The goal is to have a new version out somewhere this month.
Regarding modded dimension support, that will be fixed in the next version, but for now a workaround could be to copy over the dimension's file into a new world folder where the overworld files would be, so that it essentially becomes the overworld. Then MiEx can open it up without any problems.

Oh... thanks but a hot-fix would have been great lol, take your time 🔥


Add tabs to the docs where possible

Currently, we have a flat list of instructions (https://wave.h2o.ai/docs/installation) for all Unix/Windows or Pypi/Conda. It would be great if they could be cleaned up into corresponding tabs instead.
Pages that need this:

https://wave.h2o.ai/docs/installation
https://wave.h2o.ai/docs/installation-8-20
https://wave.h2o.ai/docs/tutorial-hello

and possibly others.

Hey! I am interested in this. Assign it to me

Go ahead @c00kie123!

Thanks for assigning! I am new to open-source so bear with me for a while.
I understand the requirements to build new feature of tabs.
Can I ask where should I do this change be done at in the directory?
You mentioned there are different sets of instructions for different type of software like Unix/Windows. May I know where I can find them?
Thanks for your help!!

Try looking for the pages linked in the issue description. The way I do this when joining a new project is simply a global search for a specific string contained in the page. This is usually very efficient when ramping up.

Hi @mturoci
I just wanted to confirm this is still open for me to work on, I see you made some commit to the installation doc 2 months ago but this feature still hasn't been added
I should be able to wrap it up for the 3 links provided in 2 days at least

Also the tutorial-hello is in markdown and mot mdx format
Since the tutorial provided uses a functionality that is provided for mdx only, can I save the edited file in the mdx format

Since the tutorial provided uses a functionality that is provided for mdx only, can I save the edited file in the mdx format

Sure. Thanks!

Hi @mturoci
I am having issues setting up the project for local dev
The makefiles are streamlined for linux Os and therefore I have to use wsl as a fallback and I have navigated succesfully so far following the step outlined in the readme of the my website directory but I get an error when running "make generate"
The error message says "cannot connect to wave server" and after tring to decode the python file for the process I realized that  it is an issue with go and my experience with go is limited
Any advice? as I am done with the edit to the docs but have been unable to test so far

Hi @oadeniran, did you go through https://wave.h2o.ai/docs/contributing#development-setup? It's basically just installing Node, Python and Go, then running make all. Once successful, you should be good to run make generate without problems.

Thanks for being so determined, you are probably the first one running this repo against Windows :)

a change also had to be made to the makefile for the showcase folder for the last command of make setup

interesting, is this mentioned somewhere in the Playwright docs?

12 other files were modified by the process

showcaseN.py should be only temporary and deleted automatically once the make generate in showcase finishes.
All in all, you can commit everything in the PR and we can deal with it over there. The types.py, ui.py etc. should have no changes also, but I would need to see what has changed, which can be best done on the PR.

Hi @mturoci
I think I am finally done, attached are screenshots of the tabs added to the three specified docs